►
From YouTube: 2022-03-21 meeting
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
C
E
B
Let's
get
started
so
for
the
specification.
We
have
a
release
coming
up
soon,
waiting
a
little
bit
more
for
metrics
for
metrics,
so
we
have
riley
and
if
so,
do
you
want
to
give
an
update?
F
Hi
the
latest
on
metrics
is
we
have
merged
one.
I
believe
we
call
it
the
final
pr
that
we
think
is
blocking
there's
a
few
out
there
that
are
welcome
additions,
but
not
necessarily
blockers
that
we
think
are
nice
to
haves.
Thank
you
all
for
your
work
on
it.
I
think
this
is
a
nice
stable
point.
B
B
B
We
can
now
continue
to
focus
on
implementation
and
then
actually
be
in
a
really
good
spot,
so
congrats.
Similarly,
we
have
an
update
on
logs
about
declaring
the
log
data
model
stable
tigran.
I
know
you've
briefed
this
group
on
the
contents
of
that,
but
if
you
just
wanted
to
do
like
a
one
minute
summary
now,
it's
probably
yeah.
D
D
I
can
just
go
ahead
and
merge
this
today,
so
I
will
see
if,
if
there
is
anyone
else
who
do
wants
to
do
to
have
their
their
stump
put
on
on
the
on
there
and
then
I
can,
I
can
merge
the
pr
so
we're
good
with
the
log
data
model,
so
good
news
there
as.
B
Moving
on
so
no
updates
for
java
or
java
instrumentation
javascript,
we
have
metrics
nearing
our
alpha
release,
currently
updating
prometheus,
no
tlpx
orders
for
the
updated
metrics
sdk,
I
think
the
github,
or
that
this
spec
issue
is
currently
blocking.
So,
let's
open
that
and
let's
see.
G
Really
just
a
clarification
actually
josh
already
commented
to
give
us
some
guidance
on
what
to
do.
There's
just
a
pending
pr.
That's
not
merged
yet
perfect
looks
like
you're.
Unblocked,
though,
like
you
don't
need
this,
you
don't
need.
B
At
this
point,
I
believe,
okay,
perfect.
Let's
keep
that
open,
so
we
can
note
that
down
later,
okay
cool,
any
other
sort
of
notes
you
want
to
make
daniel
now
that
the
metric
spec
is
effectively
merged.
Like
do
you
see
anything
blocking
you
on
the
horizon
or
you
think
it's
going
to
be
clear,
sailing.
G
No,
I
think
it's
everything's
fairly
clear
from
here
nice
awesome.
B
Okay,
moving
on
python,
more
metrics
work
on
the
way.
Of
course,
no
major
updates,
otherwise.net
fixing
one
metrics
bug
that
was
introduced
in
the
previous
release.
Candidate,
we'll
be
doing
the
next
release
candidate
this
week
go
version.
1.5
was
released
last
week,
metrics
api
revision
has
been
merged
to
main
planning
on
experimental
release,
plus
metrics
implementation
is
ongoing.
B
Six
open,
prs
and
six
closed
ruby,
matrix
sdk
is
ongoing,
great
and
also
splitting
out
of
contrib
repo
and
erlang.
No
major
updates.
Okay,
first
discussion
topic,
t-grind,
neat
opinions
about
telemetry
and
semantic
convention,
stability.
D
Yeah
this
is
this
was
open
for
a
while
now
and
it's
it's
an
area
in
our
version
again
stability
document
that
was
to
be
defined
for
a
while
now.
I
think
this
does
the
right
thing,
but
I
need
more
more
more
reviews,
more
opinions
from
the
maintainers,
in
particular,
regarding
how
we
mark
the
stability
of
instrumentations.
D
So
please
take
a
look.
It's.
I
think
it's
important
for
for
all
of
the
for
all
of
the
sigs
to
to
see
and
have
an
opinion
on
this,
because
it's
going
to
be
impacting
virtually
all
of
the
implementations,
all
the
sdks
that
have.
B
Okay,
next
topic,
cubecon
presence,
so
kubecon
eu
is
coming
up
in
may.
We
have
a
number
of
talks
that
that,
like
just
looking
at
the
schedule
that
have
been
accepted
so
just
the
core
project,
there's
a
maintainer's
track,
talk,
that's
being
hosted
by
myself,
daniel
alita
and
ted.
B
If
you
would
like
to
join
that,
please
just
let
any
of
us
know-
and
we
can
add
you-
I
don't
think
we
can
add
more
than
four
speakers
to
the
like
official
notes
on
it,
but
we
can
just
make
sure
we
have
enough
chairs
at
the
front
of
the
room,
and
we
can
talk
about
the
open,
telemetry
roadmap
and
and
and
the
status
of
the
project
for
anyone
who's
interested.
B
We
also
have
a
four
hour
room
booking
in
a
large
private
room
where
I
was
thinking
for
those
who
were
there,
we
could
do
an
in-person
community
or
maintainers
meeting.
We
could
also
do
breakouts
for
the
various
things,
and
so
we
could
even
have
multiple
meetings
at
the
same
time
in
different
parts
of
the
room.
I
don't
have
details
on
like
the
exact
size
of
the
room.
B
Yet
cncf
is
still
getting
that
for
me,
but
they
assure
me
that
it's
large
and
big
enough
to
do
whatever
we
want
with
and
finally
there's
oh
yeah
and
we
have
a
booth.
So
we
have
a
booth.
We
don't
have
the
exact
times
yet
from
the
cncf,
but
there's
the
projects
at
cubecon
often
have
booths.
There
is
one
reserved
for
us.
I
have
no
other
details
beyond
that.
I
don't
know
if
we
need
to
bring
like
imagery
and
things
with
us
or
not.
B
B
And
that
is
it
for
the
topics
today.
Is
there
any
other
discussions
that
people
want
to
have.
B
I
guess
then,
I'll
probably
just
for
the
before
we
wrap
up
for
the
for
the
maintainers
other
than
daniel,
because
I
already
asked
him
this
just
now,
for
the
containers
of
like
go
and
c
plus,
plus
and
other
languages
were
implementing
metrics.
Can
we
just
get
like
a
quick
like
just
if
you
just
want
to
speak
like
a
thumbs
up
thumbs
down
like
are
things
looking
unblocked?
Are
things
looking
clear
for
our
metrics
implementations
or
do
we
have
any
concerns
on
the
horizon?.
E
The
go
implementation
is
pretty
reliant
on
registering
metric
callbacks,
which
is
still
a
work
in
progress,
but
other
than
that
it
looks
like
we
have
a
path
forward.
B
Any
other
languages
have
people
want
to
pipe
up.
C
H
B
This
is
really
good.
Okay.
Well,
if
there
are
no
other
topics,
then
I
think
we're
done
for
the
day.
Thank
you
very
much
everybody.
We
got
two
big
milestones,
so
we've
achieved
a
lot
as
a
community
and
a
lot
for
people
who
use
open
telemetry.
So
fantastic
work
see
you
later.