►
From YouTube: 2023-01-10 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
B
B
C
Looks
like
Aaron's
got
a
mic
today,
so
we
might
actually
have
an
apartment
a
little
bit.
C
C
Cool
I
guess
we're
three
minutes
past,
so
we
probably
are
at
Quorum
double
checking.
Here
we
go
okay.
C
Yeah
we'll
jump
in.
Let
me
start
sharing.
My
screen
looks
like
it's
a
pretty
thin
agenda,
but
let's
jump
in
so
prison.
You
have
this
PR
for
the
introgen
implementation.
A
Yes,
that's
right,
so
that's
a
huge
pull
request
it.
It's
almost
forty
five
and
I
made
a
lot
of
cleanup
recently
and
also
improved
the
quality
of
code
and
now
I'm
waiting
for
approvals.
So
so
my
goal
would
be
to
to
you
know
to
merge
this
as
soon
as
possible
and
then
maybe
start
working
on
some
bug
fixes
and
extensions
too
for
this
project.
C
Unfortunately,
you're
not
the
first
person
to
put
a
3000
line
PR
in
front
of
my
eyes,
but
yeah
I
I
think
we
can.
We
can
dive
into
some
of
this
stuff.
C
Yeah
I
haven't
I,
haven't
looked
through
this
yet
this
is.
This
is
ready
to
review
those.
What
you're
saying
right?
Yes,.
A
C
One
of
the
things
that
I
do
notice
is
that
there's
no
versions
entry-
this
is
just
like
high
level
for
this
project
issue
here.
So
how
we
maintain
versions
in
this
project
is
there's
this
versions
yellow
file,
so
I
would
probably
recommending
creating
your
own
section
for
like
an
Insurgent.
Essentially
any
module
for
the
estrogen
is
going
to
get
tagged
with
this
version.
A
C
There
don't
tag
it
with
1.12,
it's
not
stable
yet,
but
yeah
like
something
like
experimental
Samplers
we
did
on
here.
I
would
just
do
something
similar
to
this
so
tag
it
with
like
a
v0
0.1
or
something
like
that.
So
it.
C
Independently
in
the
sub
version,
that's
how
we
do
like
these
multi-mod
in
this
repo,
but
yeah
otherwise
code
base
I'll
have
to
I
have
to
read
through
this
okay
anybody
else,
wanna,
I,
guess
Aaron
can't
talk
about
this,
we'll
be
able
to
chat,
really
quick,
just
to
make
sure
I'm
not
missing
something.
C
Okay,
yeah
cool,
all
right!
Well,
I'll
put
that
on
my
list
of
things
to
to
get
after
is
this:
are
these
all
different
modules?
These
different
directories
thank.
A
So
that's
the.
A
C
Usually,
we
try
to
use
modules
to
isolate
dependencies.
So
if
there's
like
a
you
know
a
strict
dependency
where
somebody's
going
to
import
one
of
these
packages
without
needing
the
dependencies
from
another
one
that
makes
sense.
But
if
that's
not
the
case,
the
package
is
just
fine
like
there's
really
no
need
to
make
it
another
module.
C
Does
that
make
sense?
Yeah,
okay,
yeah
other
than
that
I'll
have
to
I'll
have
to
look
through
this.
A
A
C
Yeah,
okay,
excuse
me
so
the
yeah
this
has
to
do
I.
Think
with
like
the
whole,
what
do
we
actually
want
out
of
the
code
under
structure
that
we
were
trying
to
set
up
I?
Don't
man
Aaron's
on
here
I
thought
he
was
handling
this,
but
he
can't
talk
so
yeah
I.
Think
I
think
we
need
to
look
at
I,
don't
know
if
the
intent
was
to
have
you
to
have
merge
access
here.
I.
Do
won't
think
that
the
intent
that.
A
C
Yeah
I
I
think
that's
the
point.
We
want
to
make
sure
that
you're
automatically
added
to
any
PRS
to
this
or
this
package
and
anything
that
goes
through
it's
more
to
notify
you
because
I
don't
think
that
the
or
the
maintainers
of
the
projects
are
going
to
merge
anything.
Unless
you
have
approved
things
that
can
think
is
the
yeah.
A
C
Take
away
from
that
so
yeah
I
think
that's
a
good
point.
Unfortunately,
you
created
this
PR,
so
I
don't
think
you
could
be
your
career,
oh
and
so.
I
do
think
that
we
already
added
you
as
a
code
owner.
C
Yes,
okay,
yes,
Aaron
also
says
he
should
have
to
be
an
approver.
So,
okay,
we'll
we'll
work
that
out
I,
don't
know
if
we
wanted
it
to
have
a
separate
group
be
for
the
approver,
but
I
also
don't
know
if
you
need
to
be
in
the
approver
group.
C
I
actually
don't
know
what
other
permissions
they
have
in
the
repo.
What
I
am
looking
for
is
the
code
owners.
The
code
owners
itself
should
be
linked
with
a
PR
Branch
protection,
so
it
requires
that
these
code
owners
actually
have
approved
this,
so
you
should
be
included
in
each
one
of
these.
C
So
I'm,
not
too
sure.
If
we
need
to
add
you
to
the
group,
if
we
do
I
mean
we
can
I,
just
don't
know
what
it
does
other
than
puts
people
in
this
group.
That
gets
the
approver
notification
so
you're
already
here
so
I'm,
not
too
sure
what
else
that
would
do.
If
we
find
something
I
we
can.
We
could
definitely
resolve
that
at
that
point.
Does
that
make
sense.
A
C
Okay,
well
I
mean
so
everyone
has
permissions
to
approve
this
changes.
Just
just
to
be
clear:
I,
don't
think
that's
what
you
meant,
but
I,
your
your
approval
will
have
weight.
I
guess
is
to
what
I
would
say
there,
and
so
it's
one
of
the
things
that
would
be.
You
know,
Branch
protection,
blocking
issue
and
I.
Think
you're
already
set
up
to
do
that.
So
I
think
we're
actually
done.
If
that's
the
case.
C
But
yes
to
anyone
else,
also
on
the
call
you
also
have
approver
abilities
for
this
PR.
So
if
you
wanted
to
go
review
it,
you
can
go
review
it,
which
would
be
helpful,
so
yeah
I,
think
I
think
you're
all
set.
There,
though,
does
that
make
sense.
C
Okay,
cool
all
right,
so
period
review
here,
DG
this
specifically
Tanish
status
on
this
VR.
D
It's
finished,
yeah
I've
been
talking
with
Aaron
offline
and
we
have
been
discussing
it
over
going
over
this
issue
for
people
who
are
not
aware
he
got
us.
His
company
got
selected
in
the
Y
combinator,
so
he's
in
San
Francisco
next
three
months,
I,
don't
know
how
feasible
for
him
to
join
the
thing,
but
he
is
in
San
Francisco
last
I
spoke
with
him.
I
think
he
was
trying
to
fly
out,
so
he
must
be
there
here
that
so
we
were
able
to
reproduce.
D
It
I
shared
a
lot
of
Stack
traces
with
Adam,
but
he
said
he
will
give
it
a
thought
and
how
to
come,
get
back
on
the
issue,
but
we
are
able
to
consistently
reproduce
it.
We
are
able
to
consistently
follow
the
instructions
and
reproduce
it
on
my
Ubuntu
Linux
kernel.
So
that's
kind
of
like
it's
more
of
a
status
update,
nothing
there
but
yeah.
Those
are
the
things.
C
Okay,
I
gotcha,
thanks
for
status,
update
as
well
as
providing
all
this
information
I.
Think
that's
helpful
is
Eden
the
only
one
who
can
address
this,
or
is
he
just
best
suited
for.
D
It
yeah
I
think
he's
best
suited
one
thing
he
like
from
our
last
call
was:
he
was
planning
to
do
like
a
session
on
a
Code,
walkthrough
I
think.
Once
we
had
that
Code
walkthrough,
we
would
have
been
easier
for
us
to
debug
if
that's
not
happening,
and
he
is
busy
next
three
months.
I
think
we
should
come
up
with
an
alternative
plan.
I
will
reach
out
with
him
if
he
can
do
it
next
in
our
next
meeting.
If
we
cannot
present
it
I
think
it
would
be.
D
We
should
start
like
you
know,
coming
up
with
a
different
plan
and
something
else.
C
Yeah
I
I
definitely
feel
that
if
we're
going
to
have
people
on
the
call
be
collaborators
in
the
project,
we
should
all
feel
comfortable
to
contribute
to
this
and
understand
the
code
flow
I.
Think
that's
one
of
the
downsides
of
accepting
a
PR
of
the
size
that
we
did
without
actually
having
full
understanding
of
it.
C
So
yeah,
I,
I,
don't
know
of
I
know
a
few
ways
we
could
address
that,
but
I
think
a
Code
walkthrough
could
be
a
good
first
step.
So,
like
you
said
Dinesh,
if
you're,
if
you're
in
contact
with
Eden
that
maybe
that's
that's
a
good
way
to
start
yeah.
D
Reach
out
to
him
and
ask
if
he
can
do
it
in
the
next
Sig
meeting,
if
not
I,
think
we'll
see
what
we
can
do.
C
E
I
think
a
big
thing
for
that
is
that
you
know
the
issue
is
sort
of
separate
from
the
original
instrumentation
that
was
merged
in
that
now
we
have
this
launcher
code
that
we
don't
really
understand
how
it
works
and
that's
what
we're
trying
to
yeah.
D
There
are
two,
so
there
are
three
pieces
to
it,
my
launcher,
and
then
there
is
other
directory
which
actually
updates
like
the
offsets,
which
is
the
whole
Json
blog
and
the
third
is
our
code.
So
we
only
accepted
the
third
part,
which
is
like
the
actual
instrumentation
code
and
the
other
two
are
like
blinded
from
us
and
that's
the
reason
I'm
little
hesitant
to
like
run
just
the
examples
he
provided
because
the
examples
were
like
you
don't
understand.
C
Right
and
so
your
your
proposal
is
at
a
Code
walkthrough
of
these
other
two
sections,
or
these
other
two
components.
D
Okay,
I'll
talk
with
Eden
what
what
are
the
thoughts,
because
right
now,
we
are
not
helpful
as
a
Sikh,
because
most
data
physiologic
is
is
in
head
in
his
head
and
he
is
busy
with
his
right
establish
his
own
company.
I
guess.
C
C
Yeah,
okay,
just
reading
your
comments,
Erin,
sorry,
okay,
cool
I,
think
that's
the
end
of
the
agenda.
I
think
we
can
pause
here
and
see
if
anybody
else
has
something
else.
They
want
to
talk
about
foreign.
C
People's
holidays
were
but
I
know,
I'm
just
getting
back
into
things.
So
I
don't
have
too
much
to
say
at
this
point.
C
If
that's
the
case,
then
I
think
we
can
pause
here,
maybe
prioritize
over
the
next
45
minutes
for
viewing
some
PRS,
particularly
one
of
the
contribute
repositories,
3108
and
then
yeah
I
think
we
can
plan
on
just
meeting
next
time,
I'm
going
to
put
down
as
an
accident
you're
going
to
read
a
shot
to
Eden
for
the
code
review
right
for
next
time.
Yes,.
D
Yeah,
one
of
our
goals
is
to
be
like,
like
simple
app
running
on
a
Ubuntu,
or
something
like
that,
which
we
can
see
rather
than
the
docker
compose,
which
he
demonstrated
or
like
gives
us.
Drought
as
an
example,
I
think
that
somehow
works.
But
when
we
try
to
do
it
like
our
Simple
app,
it
doesn't
work.
D
E
Evident
from
the
first
code
that
we
emerged
was
the
like
memory,
access
requirements
that,
like
it,
it
kind
of
implied
from
the
first
that
stuff
that
we
merged
at
this
would
just
work
with
any
go
Application,
but
it
needs
to
have
this
memory
on
the
Heap
allocated,
which
wasn't
very
clear.
You
know
it
doesn't
stand
out.
B
C
Well,
hopefully
we
figure
that
out
in
the
meantime
and
then,
if
not,
we
can
ask
them
directly
on
the
next.
In
two
weeks,.
B
C
Okay,
if
there's
nothing
else,
we
can
edit
here
yep
cool
all
right.
Well,
thanks!
Everyone
thanks
for
joining
we'll,
see
you
all
virtually
or
in
in
two
weeks.