►
From YouTube: 2022-07-13 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
B
B
Just
to
gather
your
thoughts,
what
do
you
think
about
the
approach
of
using
the
markdown
document
to
discuss
the
different
instrumentation
priorities.
A
I
think
it's
probably
good.
It's
pretty
visible,
I
think
as
long
as
we,
if
we
spend
time
during
a
sig
meeting
to
kind
of
lay
out
the
first
draft
of
laying
out
the
priorities
and
then
just
incrementally
update
like
every
now
and
then
I
think,
that'll
be
good.
It
is
kind
of
hard
to
like
change
things,
because
you
have
to
go
through
a
pr
or
stuff
like
that.
But
if
we
do
the
legwork
of
just
at
the
beginning
figuring
out
our
priorities
there,
then
that
should
make
it
easier.
B
Yeah,
I
kind
of
like
how
it
keeps
the
discussion
in
the
open
a
bit
more
as
opposed
to
using
some
other
doc,
because
the
the
comments
eventually
go
away.
C
B
Yeah,
I
don't,
I
don't
know
about
you,
but
I
I
mean
I
had
access
to
the
raw
list
of
libraries
and
their
accounts
like
like
how
often
we've
seen
them.
A
B
A
C
B
Yeah,
I'm
imagining
that
we'll
grow
our
support
over
time,
not
necessarily
all
in
a
big
release.
C
So
I
think
we
can
only
four
of
us,
I
believe
today,
it's
already.
C
A
B
C
Now
I
like
this
simplified
approach
and
I'm
sure
we
might
need
the
other
approach
at
a
later
point
in
time.
I
just
went
ahead
and
looked
at
all
the
other
instrumentations.
They
just
have
a
reference
to
open
telemetry
as
the
api
preference
or
sdk
reference.
They
don't
have
anything
to
the
other
libraries
at
this
point,
so
so
this
would
be
the
safest
approach
for
now
and
I
think
it's
going
in
the
right
direction.
I
already
see
here
two
approvals
over
here
yeah.
C
So
in
that
way
we
can
get
the
other
one
closed
and
get
merged
to
this
one
and
and
chris
this
is
a
bigger
discussion.
It's
not
a
very
simple
thing
so
and
just
want
to
see
how
you
want
to
like
go
about
it.
B
Yeah,
so
I
see
this
as
something
that
will
work
through
over
time,
but
I
just
wanted
to
get
something
out
there
to
start
the
discussions
for
what
libraries
we
want
to
support
out
of
the
box
and
so
I've
kind
of
gone
through
looked
at
surveys
online
about
things
being
used
in
the
dot
net
community.
B
I
did
not
pour
through
nougat
trends,
but
I
did
look
at
the
data
that
new
relic
had
available
to
try
to
order
some
of
these
things.
B
With
that
being
said,
I've
generally
seen
a
bias
towards
older
libraries
and
frameworks.
I
don't
know
if
that'll
be
the
case
with
other
vendors
as
well.
C
So
to
track
this
chris,
like
it's
very
difficult
to
know
like
what
are
supported
currently
in
this
one,
and
what
is
spending?
Should
we
have
a
table
or
something
like
that,
where
the
checkbox
enabled
that
this
is
supported
at
this
point
or
not
like
even
I
don't
even
know
like
with,
we
might
have
a
support
out
of
the
box
through
the
act
like
the
activities
created
itself
for
a
few
of
them.
B
So
one
thought
that
I've
had
for
tracking,
that
is
to
put
a
statement
next
to
it,
which
contains
a
link
to
our
documentation
for
that
instrumentation
library.
B
C
B
A
Chris,
what
do
you
think
about
taking
this
straight
bullet
point
list
and
changing
it?
So
each
section
so
like
each
like
database
section
or
like
rpc
or
whatever
has
a
table
that
way
we
could
have
like
a
column
of
milestone
or
like
supported
or
milestone,
and
then
you
can
put
like
a
markdown
link
in
a
separate
column.
What
do
you
think
of
that?
Yeah.
A
C
But
but
I
love
the
idea
of
putting
it
all
together
over
here
and
tracking
it
with
the
issue
so
I'll
move
on
to
that,
and
I
will
let
the
further
discussion
it
looks
good
for
me.
I
looked
at
this
vr.
This
looks
good
for
me
at
this
time,
because
this
is
a
going
to
be
a
rough
draft
at
any
point
in
time.
It's
not
going
to
be
something
final
next,
so
I
don't
think
we
need
to
find
stream
or
do
anything
over
here.
C
A
Do
we,
I
just
saw
pretty
quickly
that
you
were
mentioning
a
custom
propagator
chris.
What
would
that.
A
B
A
B
B
A
We
we
do
have
a
hook
already
that
they
could
potentially
plug
in
a
propagator.
B
At
the
very
least,
I
believe
we
have
a
hook
where
you
can
do
your
own
bootstrapping.
A
C
C
C
C
B
I
I've
played
around
with
a
lot
of
them.
Okay,
I
wouldn't
say
I
have
production
experience
with.
C
C
In
microsoft,
we,
like
my
sequel
and
all
the
spine.
There
are
a
few
things
in
the
list,
so
we
don't
have
those
supports.
I
mean
I
never
played
with
that
and,
for
example,
postgre
and
all
is
something
new
to
me.
B
Yeah
and
postgres
there's
a
few
different
modes
that
it
operates
in
I
mean
you
can
use
it
as
a
traditional
relational
database,
but
you
can
also
use
it
as
a
document
store.
So
there's.
C
C
I
think
that's
all
we
have
from
the
project
board
because
it's
going
to
change
in
a
week
after
the
pr
merge
a
lot
by
next
week.
At
that
point,
in
the
time
we
can
find
the
people
who
can
help
on
each
one
of
the
individual
tasks
and
we
could
assign
it
and,
as
per
that,
so
it
will
make
it
will
help
us
make
the
progress
that.
A
For
the
open,
pull
requests,
are
we
for
erasmus?
Pr?
Are
we
now
looking
at
the
simplified
one?
Is
that
the
one
we
should
be
evaluating
and
looking
to
merge.