►
From YouTube: Open Telemetry's Personal Meeting Room
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
D
D
E
F
Hey
I
just
saw
you
message
me.
Let
me
ask
I.
B
C
All
right,
we
are
on
the
third
minute
here.
Would
you
like
to
for
you
to
share
and.
A
C
All
right
you
remove
it,
you
had
the
thing
about.net7
and
now
I'm
curious.
Why
you
remove
it.
A
A
C
In
a
sense,
I
think
we
are
ready,
I'm,
just
thinking
kind
of
I'm
I'm
not
familiar
with
the
state
of
the
demo.
So
are
they
using.net7?
They
are
using.net6.
C
We
should
be
okay
for
that,
but
I
I'm
really
not
familiar
with
the
stage
there
and
I'm
trying
to
think
we
gain
more
visibility
as
if,
if
we
go
there
too
right,
so
there
is
a
plus
side
for
us
and
the
question
is
kind
of
do:
should
we
wait
being
closer
to
because
I
think
we
should
get
there
before
we
go
to
the
official
release?
C
But
the
question
is
right:
now,
rco1,
you
know
kind
of
I'm,
not.
C
A
F
My
only
hesitation
right
now
is
the
whole
like
dynastic
Source,
six
versus
seven.
So
if
we
don't
think
that's
going
to
be
too
much
of
an
issue,
then
we
can
go
ahead
and
do
that
now.
But
you
know
we
could
minimize
issues
if
we
solidify
that
migration
first
probably
maybe
less
trouble.
If
we
waited
till
that.
G
C
One
interesting
thing
will
be:
do
they
use
anything
that
for
now
we
just
have
byte
code
instrumentation,
because
then
we,
if
we
could
instrument
something
that
there
is
no
instrumentation
package
that
will
be
really
cool.
You
know
kind
of
right
now
we
have
graphql
that
they
don't
have
the
package
right
mongodb
they
do
have,
but
we
do
automatic
injections.
So
the
case
that
we
do
something
that's
not
available,
you'll
be
the
most
interesting
for
us.
So.
A
If
we
switch
to
one
for
all,
there
will
be
problems
on
dot
net
6..
So
if
we
do
not
change
anything,
we
are
in
the
safest.
G
C
F
B
A
Instrumentation
there,
probably
both
manual
instrumentation
I,
mean
something
all
Library
instrumentation
prepared
by
domain
Dotson
repository
and
what
we
have
in
our
site.
B
Okay
and
we
are
hesitant
because
we
haven't
validated
properly-
is
that
one,
the
gun,
sound.
A
E
A
Both
house,
the
next
stop
become
our
agenda,
is
our
polar
request.
We
have
here
the.
A
Three
of
them
are
related
to
open
Telemetry
one
for
all,
and
it
will
be
handled
later.
This
npg
SQL
is
working
thoracically
trying.
There
is
a
bug
on
on
this
library.
In
7-0
version
there
is
a
plan
to
release
701
and
for
now
we
are
not
able
to
address
this
issue
on
our
site.
C
So
so
we
are
not
instrumenting,
seven
one
or
sorry.
G
C
A
G
E
A
E
C
A
C
A
A
C
Okay,
so
this
is
a
Red
Dawn
right,
no
okay,.
E
C
C
C
Well,
Robert,
you
you
send
that
message
about
the
zero
file
and
we
already
went
for
it.
E
C
So
just
these
two
and
we
are
good
to
cut
zero
five.
C
And
then
we
have
the
the
big
upgrade
to
seven
right,
exactly
yeah,
so
yeah.
Let's,
let's
push
this
so
you
can
have
this
release
and
do
the
upgrade,
because
the
upgrade
should
bring
a
few
issues
for.
A
Just
for
the
future
releases,
I
already
dropped
support
for
3.1.
next
door,
but
in
the
future
I
would
like
I
would
ditch
the
task
in
the
opposite
way.
Just
include
support
for
the.net
8
and
then
drop
support
for
make
a
release
and
then
drop
support
for
old
things.
Yeah.
D
C
C
Actually,
no
right,
because
next
year
you
release
eight,
not
nine,
but
we
had
eight
drop
seven
afterwards,.
D
Okay
yeah,
so
let's
do
it:
let's,
let's
get
these
two
items
done
and
cut
five
and
keep
pushing
so
we
can
have
the
release
of
seven.
A
F
Yeah
I
I
started
out
on
that
I
think
I
have
all
the
Source
changes
implemented,
but
I
need
to
update
the
tests
that
go
with
them
as
well,
so
probably
need
to
spend
some
more
hours
on
that.
G
A
G
A
G
C
A
Even
if
the
tests
are
failing,
yeah,
I,
I
started
to
say,
I
would
like
to
say
thanks
to
Bureau
for
for
the
first
contribution
good
job,
and
we
are
looking
for
for
more.
B
Yeah
thanks
thanks
everyone
for
helping
me
yeah
I
mean
find
some
more
resource
and
assign
to
me.
I
I
mean
which
would
give
me
more
more
depth.
I
would
be
happy
to
contribute
tomorrow.
Okay,.
C
Sure
one
one
question:
did
you
have
a
chance
to
go
to
the
the
kind
of
design
docs
because
you're
a
fresh
eyes,
so
perhaps
you're
reading?
You
are
gonna,
find
this
stuff
kind
of
hey.
I
didn't
understood
this
understand
that
and.
C
B
B
It
down
like
how
we
can
onboard
any
any
new
new
Engineers
to
this
repo
I
think
that
would
be
anywhere.
You
can
do
improvements,
but
at
the
same
time
like
feel
free
to
assign
some
issues
so
that
I
can
I
can
do
some,
like
you
know,
like
cleaning
kind
of
like,
hence
get
my
hands
dirty
yeah.
E
Yeah
the
good
thing
about
what
Paul
was
suggesting
this
updating
design
MD
is
that
we
also
get
some
feedback
that
some
basically
I
don't
know.
Users
would
like
to
know
what
is
going
on,
how
it's
working
to
feel
safe,
that
you
know
to
feel
safe,
yeah.
B
E
E
I
suggest
updating
the
design
markdown
in
a
way
that
that
you
expect
to
read
as
a
user,
not
as
a
contributor.
So,
for
example,
I
do
not
expect,
as
at
least
as
the
first
PR
to
put,
for
example,
exact
things
like
I,
don't
know,
class
names
or,
as
I,
don't
know
the
architecture
of
the
repository
this
high
level
architecture.
What
what?
For
example,
you
know
what
Hooks
of
the.net
for
example,
time
we
are
using
to
to
instrument
things.
C
We
which
reminds
me
that
talking
about
the
design,
dark,
I,
don't
think
the
lazy
loader
is
there.
This
is
something
that
we
probably
should
add
there,
because
it's
kind
of
a
question
that
I
think
users
you
have
about
what
happens
with
those
instrumentations.
You
know.
A
C
H
Hey
Sam
I
came
as
an
observer
just
interested
in
tracking
the
progress
here.
Yeah
I
mostly
just
want
to
see
when
we
can
start
testing
that
instrumentation
here
go.
H
H
I
totally
fine
I
think
that
was
interested
in
checking
out.
You
know
in
in
the
demo.
For
a
start,
you
know,
because
we
are
trying
to
run
the
demo
locally,
see
how
it
feels
so
yeah
and
I,
guess
that
you
know,
since
Carter
mentioned,
that,
there's
interest
in
bringing
that
to
the
demo
application
to
be
fantastic,
but.
B
E
But
the
good
thing
is
that,
so
far,
all
the
issues
that
we
got
were
like
are
dedicate
indicating
that
it
is
really
working
because
usually
these
were
like
misconfigurations
or
some
very,
very,
like
maybe
not
awkward,
but
a
complex
setup
like,
for
example,
there
was
a
guy
who
was
trying
to
add
additional
instrumentation
upload
of
hours,
so
write
custom
instrumentation
in
addition
to
what
we
provide,
but
so
far
our
other
issues
were
just
solved
without
making
changes
in
the
code.
As
far
as
I
remember
and.
G
E
H
Yeah
I
saw
that
comment
in
the
demo
issue
about
the
upcoming
next
version.
It's
0.50
correct
or
zero:
five
zero,
five,
zero.
Five
there
you
are
the
Euro
yeah.
C
Yeah,
which
reminds
us
perhaps
it
it's
slow
priority
for
us
in
that
sense,
but
also
to
have
a
demo
here
on
our
repo
will
be
good.
You
know
kind
of
with
a
Docker
composer
and
put
we
have
the
example,
but
the
example
is
kind
of
running.
You
have
to
build
and
do
this
stuff
locally.
So
having
like,
we
had
I
think
we
had
this
in
some
other
repos
I,
remember
on
The
Collector
for
sure
having
a
docker.
G
E
C
B
A
one
request
can
can
one
of
one
of
you
assign
any
issues
to
me
so
that
I
can
again
what
next
thing.
A
D
A
B
C
A
A
C
Yeah
I
I
think
both
both
of
the
graphql
and
the
WCF
on
the
other
River,
but
this
one
this
one
is
gonna,
make
one
of
our
maintainers
very
happy.
Quiz
is
not
here,
but
he
was
the
one
kind
of
raising
this
issue,
so
this
one
seems
a
a
very
good
suicide.
B
Okay
sure
so
I
just
wanted
to
ask
one
question
like:
is
there
some
somewhere
we
can,
we
can
ask
general
public
like
which,
which
Library
they
want
to
be
instrumented,
I
mean.
Should
we
take
that
approach?
Will
that
helpful
for
us.
C
So
recent
relatively
recent,
both
Robert
and
Chris
kind
of
try
to
gather
data
from
the
the
real
users
that
we
have
it's
kind
of
hard
to
find
the
exact.
But
we
we
built
a
list.
There
is
an
issue
right,
Robert
I,
think
you
create
an
issue
and
and.
B
Yeah
I
mean
it
would
be
nice
if
you
can
tag
that
into
our
issues.
Right,
like
I'm,
just
telling
I
I
I
mean
you
guys
can
decide
so
for
the
core
WCF.
The
way
we
started.
Privatizing
things
is
like
we
come
up
with
all
the
features
and
we
tagged
into
our
issues
like
it
is
stacked
there
so
that
we
can
get
like
user
feedback
from
there
see.
If
we
want
to
do
something
like
that.
I
I
mean
I'm,
just
suggesting
I
I'm
fine,
with
whatever
approach
you
guys
that
want
to
take.
A
C
Yeah,
so
just
one
commented
that
we
do
have
an
writing:
I
mean
we
I
mean
dot
net
in
general,
a
bunch
of
instrumentations,
but
because
of
the
way
that.net
did
with
the
active
Source
being
part
of
their
own
time,
which
is
great
I
expect
that
as
the
time
passes
by
about
long
term,
we
basically
just
add
sources.
C
You
know,
add
activity
sources,
but
meanwhile,
you're
gonna
have
bicycle:
instrumentations,
you're
gonna
leverage
instrumentations
from
the
contribution
from
the
core
dot
net
repo
you
know,
and
whenever
we
didn't
try
the
Gap
we
tried
to
to
find
the
best
way
to
to
do
the
kind
of
instrumentations.
We
are
not
kind
of
restricted
to
do.
C
Bite
called
discrimination
because
we
had
the
instrumentation
and
the
automatic
instrumentation
you
know
so
if
it
makes
more
sense
to
do
in
the
country,
that's
what
we
should
do
and
just
use
the
lace
loader
here
you
know.