►
From YouTube: 2023-03-29 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
B
B
I
guess
we
can
probably
just
get
started
here.
Let's
see,
let
me
share
my
screen
foreign.
B
B
C
B
First
item
we
had
on
the
agenda
is
the
release.
Pr
should
be
used
to
the
drill
by
now.
This
does
notably
include
exponential,
histogram
support,
which
is
a
big
one.
Thank
you
to
Matt
Ware,
a
couple
of
bug,
fixes
included
as
well,
and
some
changes
in
the
experimental,
but
the
the
really
the
headline
feature
here
is
exponential,
histogram
support
which
has
been
coming
for
a
long
time.
So
please
take
a
look
at
this
review
it
so
that
we
can
get
it
out.
B
This
is
kind
of
a
nebulous
topic,
I'm,
not
entirely
sure
what
I
even
really
want
to
say
here,
Beyond,
just
the
fact
that
we've
had
some
some
changes
slowly
over
the
last
few
months
among
maintainership,
some
of
the
maintainers
have
had
a
little
bit
less
time
to
spend
on
the
project
than
than
they
used
to,
and
particularly
in
contrib.
We
have
a
lot
of
modules
that
get.
A
B
A
lot
of
attention
and
the
the
ownership
model
is
not
all
that
clear
I
just
wanted
to.
Let
you
guys
know
that
I
think
this
week,
I'm
going
to
be
spending
some
time
on
this
topic,
trying
to
clean
up
the
ownership
model
I'm.
Looking
into
what
some
of
the
other
cigs
are
doing.
I
know
the
collector
contrib
repo
has
done
a
good
job
of
sort
of
distributed.
B
Ownership
I
know
that
the
Java
Sig
is
actually
using
the
same
GitHub
action
that
we
already
can
trib
to
maintain
their
instrumentation
components,
but
I
also
think
we
have
a
lot
of
components,
particularly
in
contrib,
which
are
just
at
the
moment,
sort
of
unmaintained.
B
So
this
week,
I'm
going
to
be
spending
time
going
through
those
and
trying
to
Mark
some
of
the
the
unmaintained
ones
as
unmaintained
find
owners
for
ones
that
are
that
are
being
maintained,
but
I
don't
have
ownership
specifically
called
out
in
the
ownership
file
and
maybe
trying
to
consolidate
some
of
the
tooling
we
use
so
that
every
different
Sig
isn't
maintaining
their
own
tooling
for
this
type
of
of
work.
B
A
B
Just
me
working
on
it,
I,
don't
know
how
much
I'll
be
able
to
get
done
in
just
a
week,
but
going
to
start
trying
to
to
solidify
this
topic
a
little
bit
more.
B
Does
anyone
have
any
any
comments
here?
I
know
it's
kind
of
a
rambly
and
nebulous,
probably
not
a
lot
to
really
grab
onto
there.
D
B
B
I
also
think
we
should
consider
applying
a
similar
model
to
the
core
repo
I.
Don't
know,
I,
don't
think
we
want
necessarily
distributed
ownership
as
much
as
definitely
some
areas
of
the
core
repo
are
like.
B
People
that
that
have
more
expertise
and
familiarity
with
some
parts
of
the
code
than
others,
particularly
metrics
I
know,
is
maintained
by
mostly
a
small
number
of
people
who
really
understand.
What's
going
on
logs
I
know
has
been
mostly
maintained
by
just
a
a
small
handful
of
people.
B
I
know
Martin,
and
we
there
was
at
least
another
person,
who's
name,
I,
can't
think
of
right
now,
but
I
think
I
want
to
look
into
some
sort
of
Auto
assigning
or
at
least
Auto
tagging
of
of
people
that
are,
you
know,
subject
matter
experts
for
particular
parts
of
the
code,
obviously
not
without
their
consent
and
permission,
but
that
would
be
coming.
Probably
next
for
now,
I'm
gonna
try
to
focus
on
contrib
for
the
next
week.
B
Okay,
then
I
guess
I,
don't
know
who
added
this
first
PR
here,
1400
Sammy,
Auto,
transportations,
node.
B
Sammy
are
you
on
the
call
today
looks
like
you
know,
I
assume
you
just
added
it
here
to
to
get
reviews
on.
It
looks
like
it's
been
open
for
a
while.
Now,
though,
so
I'll
probably
try
to
review
this
today
as
well.
B
Obviously,
this
PR
hasn't
been
around
for
a
very
long
time,
but
it
is
specification
required
and
yeah.
He
just
reached
out
specifically
to
ask
for
reviews
on
this,
so
I
figured
I
would
add
it
to
the
agenda.
B
Next
item
I
have
on
the
agenda
is
kudecon,
hopefully
not
a
surprise
to
anybody.
That
kubecon
is
coming
I
added
a
couple
of
events
here
that
people
may
be
interested
in
some
of
them
have
virtual
options.
Some
of
them
don't
and
I
will
be
at
kubecon.
I,
don't
know
if
anybody
else
here
is
planning
on
attending,
but
if
you
are
I'll
be
at
the
booth
most
of
the
time
so
come
say:
hi
and
yeah,
looking
forward
to
seeing
whoever.
A
C
Oud
yeah,
so
I
have
reviewed
this
PR
a
couple
times
already.
My
focus
has
been
mostly
that
it
follows
the
spec
for
logs
and
I
think
we're
very
close,
and
what
I
would
I
would
just
appreciate
more
eyes
on
it
more
just
general,
making
sure
that
it
like
follows.
Standards
like
you
know,
from
the
from
compared
to
other
packages
and
so
on.
C
C
But
yeah
I
would
really
appreciate
more
people
to
take
a
look
at
this
I'm.
Probably
gonna
approve
it.
Okay,
there's
just
yeah,
there's
just
one
more
one,
more
thing
that
I
asked
for
to
be
changed.
One
has
changed
that
I'll
probably
approve
it.
B
That's
everything
that
I
had
on
the
agenda
short
agenda
today.
I
most
of
you
probably
know
that
I
was
out
last
week
for
vacation,
but
I
was
I've
also
been
under
the
weather
this
week
and
took
some
sick
time
off
so
I'm
still
trying
to
catch
up
on
everything.
That's
been
happening
for
the
last
10
days
or
so
I
guess
we
can
move
into
the
bug
triage
and
come
back.
If
anyone
has
added
any
agenda
items.
B
B
D
Don't
was
it
Import
in
the
middle
or
the
require
in
the
middle
one.
B
B
B
Or
is
that
the
of
course
that's
the
only
one
function
hook
then.
B
Yeah,
so
there
are
other
issues
with
this
package.
Two
things
come
to
mind
for
one,
it
appears
to
be
somewhat
unmaintained.
B
E
I
can
speak
to
that.
I
can
speak
to
that
a
little
bit.
I'm
I'm
Trent
I'm,
the
one
that
you
see
is
doing.
The
recent
commits
on
that
Our
intention
was
to
go
back
to
that
I
I
did
a
copy
to
I
need
to
get
a
couple
of
fixes
Upstream
to
require
in
the
middle
and
then
we'll
switch
back,
but
I
needed
to
move
ahead
on
our
agent.
E
So
yeah
I
agree:
it's
not
getting
a
lot
of
Maintenance,
but
it
isn't.
It
isn't
deprecated
and
not
being
dropped
so
I'm
also
pretty
typescript
ignorant.
So
if
there's
something
that
require
in
the
middle
would
need
to
do.
That
would
help
here
I'm
willing
to
do
that
and
get
a
really
support,
but
not
exactly
sure.
What's
needed.
B
Yeah,
all
we
need
is
a
named
export,
so
on
this,
where
you
have
the
the
module
exports
equals
hook,
just
module.exports.hook
equals
hook
with
you,
know,
online
nine
and
a
half
here,
just
adding
a
new
line.
I
believe
that
would
enable
us
to.
E
B
B
Yeah,
it
does
not
need
to
be
a
breaking
change,
because
a
named
import
would
allow
us
to
understand.
B
Of
importing
the
whole
module,
we
would
just
import
Hook
from
require
in
the
middle
or
require
hook
or
whatever
we
you
know,
whatever
it's
called
it
doesn't
really
matter
and.
B
E
Is
right,
yeah,
okay,
yeah
I
can
follow
up
on
this
ticket
and
get
get
something
started
for
them.
B
Perfect
and
then
I
guess,
while
I
have
you
on
the
phone
here,
there's
another
issue
this
one
here,
which
is
also
affecting
us
I,
believe
this
user
actually
had
a
fix,
yeah
and
wanted
to
create
a
fixed
PR,
but
just
hasn't
gotten
any
confirmation
that
it
would
be
you
know,
sort
of
reviewed
and
merged.
E
B
D
I
have
a
draft
BR
for
that
one
out
and
that
will
probably
be
done
soon.
So
then
we
can
cross
that
off
the
list.
Okay,
it's
not
really
a!
We
haven't
considered
those
bugs
before
we
have
considered
those
feature
requests,
but
there
have
been
quite
a
few
of
them.
I
would
change
the
labels
on
that.
B
Yeah
the
file
not
found
here
there
have
been
quite
a
few
of
them.
Okay,.
C
B
So
I
guess
we
can
just
leave
that
for
now,
I
will
add
a
priority
so
that
it
gets
off
of
our
triage
dashboard
here
key
two,
not.
B
B
B
D
B
A
Forgot
about
this
one
sorry.
B
So
all
maintainers
are
like
the
maintainer
team
is
listed
as
an
admin
on
this
project
and
I
specifically
added
you,
so
that
you'd
be
able
to
see
that.
So,
if
you
still
can't
see
it,
let's
talk
about
it
either
after
the
meeting
or
tomorrow
morning.
I
know
that
you're
your
time
zone
is,
we
can
discuss
this
offline
yeah
for
now,
I
will
say
this
is.
B
Okay,
instrumentation
postgres,
suitable
query
parameter
is
not
returned.
B
Looks
like
some
failing
tests
I'll
look
at
this
this
afternoon.
Now
the
bug
it's
self.
A
B
Thank
you,
everybody
for
your
time.
I
will
talk
to
you
next
week.