►
From YouTube: 2022-12-19 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
B
All
right,
we
can
get
started,
I'm
expecting
a
smaller
crowd
than
usual,
just
given
the
upcoming
holiday,
but
we
can
still
go
through
things
fairly
quickly.
It
looks
like
in
the
spec
we
have
otlp.
Json
is
now
marked
as
stable.
That's
a
fairly
substantial
release,
no.
C
Yeah,
but
still
it's
still
proposed,
so
there's
a
there's,
a
PR
out
that
has
not
been
merged
yet
and
I.
Think
that
there's
a
conversation
about
ambiguity
around
Trace
ID
when
it's
missing
or
empty
what
that
actually
means
that
needs
to
be
resolved
for
it
to
become
stable.
So
I
think
this
is
probably
a
call
to
to
action
to
take
a
look
and
offer
opinions.
Okay,.
B
Thanks
Jack
so
looks
like
we
need
more
reviews
on
this
and
then
then
we
can
probably
take
action
on
it
in
January.
Thanks
for
calling
that
out.
Moving
on
no
updates
for
PHP
for
Java
we've
released
job
instrumentation
and
contrib
version
1.21
for
go.
We
have
release
version
0.35
for
metrics,
both
SDK
and
API.
Changes
for,
like
presumably
for
metrics,
are
expected.
The
next
release.
Release
1.12.0
is
14
of
the
way
done.
B
This
includes
a
semantic
conventions
update
for
The,
Collector
version,
0.68
releases
in
progress
for
comms
we've
releases
for
our
docs.
Now.
Oh
that's
interesting,
and
the
registry
now
has
over
600
entries.
Wow
I
haven't
looked
into
register
in
a
while.
That's
a
huge
number
now
compared
to
what
it
used
to
be.
Also
to
note
for
comms
I
believe
the
meetings
have
been
moved
to
Mondays
I
just
noticed
that
today,
so
I'm,
not
certain.
If
that's,
this
is
the
first
week
of
it
being
moved
or
it
was
moved
recently,
but
it.
B
Yeah,
so
if,
for
some
reason
you
had
a
conflict
of
the
old
time,
it's
it's
now
immediately
after
this
meeting,
it's
on
the
same
calendar
that
you
used
to
access
this.
A
D
Yes,
it's
the
first
one
right,
so
so
it's
we
we
we
decided
to
to
do
this
just
on
a
monthly
basis,
just
cut
it
off
on
the
first
or
something
like
that.
So
is
it
that
did
people
have
a
quick
overview
of
like
hey
this.
This
is
what
what
we
added
over
over
the
last
month
and
also
maybe
to
give
a
little
bit
of
recognition
to
to
the
people
that
help
with
that,
so
that
they're,
like
about
the
releases
of
the
other
projects
that
at
the
bottom
you
have
like
hey.
D
A
B
C
Perfect
thanks.
Everyone
I
have
another
quick
comment:
I
guess
on
the
this
comms
update,
so
I
was
going
through
the
registry
a
while
back
and
noticed
that
a
bunch
of
the
entries
for
Java
are
out
of
date
and
I.
Think
somebody
at
one
point
had
done
a
manual
edition
of
a
bunch
of
different
things
into
here.
C
So
you
know,
the
types
of
things
that
are
in
this
registry
are
different
pieces
of
instrumentation
and
then
different,
SDK
extension
components
like
exporters
and
Samplers,
and
things
like
that
and
just
a
lot
has
changed
since
whenever
that
manual
work
was
done
to
add
those
and
yeah
I
guess
I'm
just
curious
what
the
the
comms
group's
thoughts
are
on
keeping
those
up
to
date.
If
there's
like
any
work
that
is
expected
from
from
maintainers
to
do
this
or
if
there's
like
any
opportunities
for
automation,.
D
Okay,
yeah
I
I
can
I
can
say
a
little
bit
on
that,
so
we
we
now
have
a
little
bit
of
automation.
So
what
what
we
basically
did?
D
We
created
a
small
scanner
that
goes
through
through
a
bunch
of
the
repositories
and
tries
to
find
new
things,
but
after
that,
there's
still
a
few
manual
steps
like
cleaning
up
things
and
then
whatnot
and
the
other
thing
is
that
that
we
check,
if,
if
URLs,
are
still
valid,
so
I
think
Java
is
a
good
example,
because
things
change
very
often
that
I
don't
know.
Some
of
them
still
have
a
version
string
in
them
and
something
like
that.
D
So
we
try
to
to
do
things
a
little
bit
more
automatically
to
tap
the
registry
up
to
date,
but
it's
not
yet
a
perfect
process
and
probably
will
never
be
so.
If
there's
anything
you
see
like
hey,
there's
a
bunch
of
links
outdated
or
for
our
sake
it
makes
no
sense
to
have
it
in
this
dead
way.
Maybe
you
want
to
have
I,
don't
know
not
pointed
to
the
GitHub
repo,
but
maybe
to
some
other
places.
Then
yeah
race
is
an
issue
and
then
we
can
see
how
to
improve
that
all.
B
B
All
right,
Ted
trying
to
road
map
tying
our
roadmap
to
respect
backlog
and
product
project
management.
E
Yeah,
this
is
something
we've
been
working
on
a
bit.
E
Over
the
summer
we
developed
some
a
system
potential
system
for
managing
the
spec
backlog
in
terms
of
projects
and
being
able
to
see
the
goal
being
able
to
like
more
consciously
choose
which
spec
projects
we're
working
on
at
any
given
moment,
so
that
we
can
concentrate
our
Focus
some
of
the
feedback
we've
gotten
is,
you
know
things
tend
to
move
very
slowly
and
uncertainly
through
our
spec
process
and
looking
into
that,
it's
less
that
we
have
a
really
complicated
process
and
more
that
we
have
lots
and
lots
of
issues
open
at
any
given
moment,
and
we
tend
to
context
switch
quite
quite
a
bit
across
many
many
things
and
that
can
make
it
difficult
to
get
enough
focus
on
any
one
thing.
E
If
it's
remotely
controversial
or
tricky
I
think
the
other
issue
we
identified
is
sometimes
we
don't
feel
like.
We
have
the
subject
matter:
expertise
within
the
spec
community,
so
approvers
and
maintainers
the
spec
project
are
sometimes
reluctant
to
to
approve
something
or
or
comment
on
it
because
they
don't
feel
like
they
have.
E
You
know
the
expertise
to
to
do
so,
which
is
a
good
attitude
to
have
it's
good,
that
we
don't
rubber
stamp
things
we
don't
understand,
but
it
also
means
we
need
to
be
able
to
identify
that
early
on
and
resolve
it
one
way
or
the
other
either
trying
to
find
some
outside
expertise
that
we're
going
to
consult
with
or
having
enough
members
of
the
spec
Community
agree.
E
They're
going
to
you
know
bone
up
on
the
subject
sufficiently,
so
they
can
at
least
make
sure
this
what's
being
proposed
is
is
correct
and
also
like
works
well
with
everything
else
that
the
Telemetry
is
doing
so.
E
I
would
like
to
to
kick
off
this
in
January
when
we
come
back
so
Morgan
I
would
like
to
follow
up
with
you
and
then
also
follow
up
with
the
TC
to
perfect
to
kind
of
get
some
of
the
details.
E
B
E
E
This
I
I
think,
if
we
have
a
way
of
like
you,
know
we're
not
talking
about
PRS
that
are
like
so
small
that
they're
not
controversial,
but
we're
talking
about
things
that
are
either
a
single
Otep.
But
it's
a
doozy
like
the
columbar
encoding
for
otlp,
for
is
an
example
of
one
of
these
using
Apache
Arrow
to
get
a
very
high,
highly
compressed
version
of
otlp
that
can
like
egress
data.
Really
cheap
is
like
an
Otep.
That's
been
out
there
like
forever,
but
it
seems
really
useful,
no
one's
locking
it.
B
But
it's
not
prioritized
right,
like
there's
no
sort
of
like
project-wide
decision.
That
says
this
is
important,
and
maybe
this
other
thing
is
not
as
relative
right
like
if.
E
We
could
agree
like
okay
right
now.
This
we're
gonna
try
to
get
this
Otep
over
the
finish
line
and
the
people
who
proposed
it
are
around
and
Josh
and
whoever
else
on
the
TC
who
understands
this
are
round,
and
so
we're
gonna
just
tell
the
community
hey
like
this.
Is
the
the
feedback
period
for
this
Otep
and
then
try
to
get
it
over
the
finish
line.
E
Likewise,
we
have
the
rum,
client
working
group
who's,
trying
to
get
browser
stuff
done
and
we've
got
the
messaging
working
group.
That's
trying
to
figure
out
more
the
details
around
how
messaging
and
like
async
tracing
works
and
there's
even
still
some
like
HTTP
stuff
I,
think
that's
that's
hanging
around
plus
everything.
That's
in
the
an
open
PR
on
the
Otep
repo
and
now
that
we
have
a
high
level
strategic
roadmap.
I
think
that
that
helps
us
figure
out
which
of
these
we
want
to
clear
out.
E
I
want
to
start
up
a
number
of
working
groups
on
semantic
conventions
to
like
push
those
through,
but
I
don't
want
that
to
like
completely
swamp
attention
from
from
other
things
that
are
already
in
that
backlog.
So
I
think
we
just
need
to
have
like
a
public
place
where
we're
we're
making
the
decision.
So
any
feedbacks
welcome
now
or
you'll
see
this
stuff
happening
in
January.
Anyone
who
wants
to
participate,
please,
you
know,
let
me
know
and
I'm
excited
for
the
new
year.
B
B
B
Okay,
in
that
case,
we'll
wrap
it
up.
I
believe
the
meeting
for
next
week
is
canceled
for
the
holidays.
I
also
canceled
the
following
one,
because
I
think
it's
on
New,
Year's,
Day
or
the
day
after,
where
basically
everyone's
going
to
be
off
so
we'll
see
everybody
back
on
the
January,
16th
I
think
wait,
wait,
no
I'm
wrong!
January
9th,
we'll
see
if
we're
back
on
January
9th
have
a
great
holiday
and
we'll
see
everyone
soon.
Bye.