►
From YouTube: 2022-05-09 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
A
All
right
so
for
the
sig
check-in,
I
think
today,
just
given
that
we've
been
making
so
much
progress
on
metrics
and
there's
there's,
I
think
ambitions
of
doing
an
announcement
about
metrics
at
kubecon.
The
main
thing
is
we
want
to
check
in
on
the
status
of
the
metrics
releases,
so,
starting
with
java,
it
looks
like
we're:
releasing
the
stable
metrics
sdk
today,
wow
and
release
the
proto
0.1.0.17
alpha
today
for
javascript
no
update,
docs
and
examples
is
the
most
important
work
for
kubecon
metrics
rc.
At
the
moment
I
assume
daniel.
A
Python
only
one
more
issue
before
the
metrics
rc
working
on
it
right
now
aiming
for
rc.
Today,
wow,
we
are
doing
great
awesome
net.
No
major
updates,
otlp
log
explorer
border
bug,
fixes
going
in
can
one
of
the
dot
net
people
remind
me
where
we
are
dot
net
metrics.
I
remember
we
actually
already
released
it
or
or
we
just
on
the
cusp
of
releasing
it.
A
I
think
they
already
released
it
yeah
I'll,
go
quickly
scroll
through
the
notes.
When
we're
done
a
go,
has
a
metric
sdk
alpha
yeah.
We
knew
a
little
further
behind
the
others.
That's
okay,
c,
plus
the
alpha
has
14
closed
issues,
zero,
open
issues
we'll
be
discussing
the
next
community
meeting.
If
they're
ready
for
the
alpha,
great
and
logs
sdk
also
made
a
lot
of
progress,
no
updates
on
ruby
or
the
others.
A
A
A
Let
me
just
paste
it
in
here
with
sort
of
notes
and
things
of
our
plans.
A
So
please
read
through
I'm
guessing
a
lot
of
people
have
already
seen
it
so
there's
sort
of
three
things
that
that
I
guess
four
things:
there's
four
sort
of
hotel,
wide
things
that
are
planned
and
I
know
there's
other
people
who
are
doing
talks
about
hotel.
I'm
not,
but
I
think,
there's
a
couple
community
members
who
have
like
regular
cubecon
talks.
So
I
don't
know
the
details
on
those,
but
those
are
on
the
agenda
if
you're
planning
to
attend,
but
in
terms
of
community-wide
things,
we
have
a
booth.
A
The
booth
is
outlined
in
the
kubecon
plans,
doc,
and
so,
if
you
are
a
contributor
to
open
telemetry
like
honestly,
if
you're,
if
you're
involved
in
the
community
at
all
feel
free
to
help
staff,
the
booth
in
this
dock
we've
listed
the
times
that
it's
open.
I
will
be
there
basically
anytime
that
I'm
not
doing
anything
else
which
should
be
most
of
the
booth
times.
It's
a
great
way
to
meet
people
to
find
people
who
are
interested
in
open
telemetry
and
to
show
off
the
project
with
them.
A
A
To
go
meet
people
and
show
presents
at
kubecon.
We
don't
have
any
sort
of
formal
plans
for
the
booth.
Beyond
that,
I
think
a
couple
people
are
bringing
swag.
I
managed
to
get
splunk,
for
example,
to
print
out
a
bunch
of
hotel
splag.
That's
not
splunk
swag,
just
pure
hotel
stuff,
and
I
think
jurassie
and
a
few
other
people
managed
to
do
the
same
through
their
companies
as
well.
So
we
should
have
a
good
number
of
like
stickers
and
t-shirts
and
things
to
hand
out
which
is
great.
Yeah
I'll
also
have
t-shirts
awesome.
A
So
we
should
be
like
pretty
well
stocked,
then
that's
awesome,
so
yeah
definitely
try
and
like
attend
and
help
man.
The
booth
like
you
do
not
have
to
be
an
official
like
maintainer
like
if
you
contribute
a
hotel.
Frankly,
if
you're
joining
this
call
at
all
you're
more
than
qualified
to
help
out
at
the
booth.
So
so
please
join
and
yeah
we're
giving
that
slang.
A
There's
a
sign
up
link
for
the
room
booking,
so
if
you're
there
please
sign
up.
That
being
said,
I'm
we're
not
going
to
restrict
this.
So
if
you
forget
to
sign
up
it's
not
a
big
deal,
but
it'd
be
nice.
If
you
can
sign
up
just
so,
we
can
have
an
idea
of
numbers.
A
A
So
first
would
be
just
a
quick
celebration
of
the
metrics,
rc
and
ga,
and
and
also
just
sort
of
meeting
each
other
having
a
discussion
amongst
contributors
to
otel
about
what
we
can
do
better
as
a
community.
C
A
Haven't
had
a
ton
of
these
feedback
sessions,
mostly
because
we
haven't
really
met
in
person
in
almost
three
years,
so
it'd
be
good,
I
think,
for
contributors
to
brainstorm
things
we
can
do
more
efficiently
more
effectively
in
parallel
or
afterwards,
it'd
be
nice
to
also
have
an
end
user
discussion.
If
we
have
enough
end
users
who
are
there
to
talk
to
discuss
what
they
think
open
telemetry
could
do
to
be
more
successful.
A
This
is
the
main
thing
that
I
thought
we
could
do
after
those
and
then
it's
sort
of
very
quickly
brainstorming,
different
map
topics
for
the
project,
so
metrics
is
on
the
path
to
completion.
Right,
there's
been
a
huge
slog
for
the
last
year,
but
we've
got
it
in
pretty
good
shape.
Now
and
yes,
there
will
be
more
work
on
metrics
in
the
future,
but
the
big
hump
I
think,
is
over,
and
so
this
is
an
opportune
time
as
a
community
to
figure
out
what
we
want
to
focus
on.
A
Next,
we
had
a
big
focus
on
tracing
a
big
focus
on
metrics.
Obviously,
logs
are
in
the
pipe
and
that
will
be
a
focus,
but
we've
actually
made
substantial
progress,
though
already-
and
so
this
is,
should
be
it's
an
opportunity
time
to
have
a
discussion
about
like
what
we
want
to
do
next.
Do
we
want
to
collect
more
data
types
right
like
I
know,
some
companies
and
users
have
mentioned
like
hey
profiles,
would
be
nice
maybe
or
do
we
want
to
focus
more
on
breadth?
A
Do
we
want
to
focus
on
on
bringing
open
telemetry
to
more
places?
It'd
be
nice
for
us
to
just
sort
of
brainstorm
this
this
not.
This
is
like
nothing
sort
of
like
super
official,
I'm
not
expecting
anything
like
formal,
like
a
10-page
doc,
to
come
out
of
this,
but
we
should
at
least
like
give
each
other
a
sense
of
what
we
think
the
next
big
thrust
should
be
as
a
community.
A
After
that
we
can
do
a
maintainers
q.
A
if,
if
we've
enough
non
sort
of
maintainers
like
people
want
to
ask
questions
there,
and
just
we
can
just
generally
have
some
time
for
community
members
to
chat
in
person,
and
I
think
in
the
background
related
to
this,
I
know
that
shar
and
some
members
of
of
the
community
were
also
just
hoping
to
like
ask
more
detailed
questions
and
survey
questions
to
any
end
users
who
show
up
so
we
can
get
a
better
understanding
of
how
they
use
open
telemetry.
A
This
is
a
draft
if
you
think
this
whole
thing's
stupid
and
should
be
thrown
out
and
have
a
better
idea.
Please
just
write
it
in
here,
I'm
not
tied
to
this.
I
just
wrote
this
up
on
friday
because
we
didn't
have
an
agenda
at
all
so
like
if,
if,
if
anyone
wants
to
contribute
to
this
edit
to
edit
it
go
ahead,
please
please
make
whatever
changes.
You
want.
A
So
we
also
have
a
metrics
announcement,
blog
post.
This
is
one
we
shared
about
a
month
ago,
but
we
haven't
really
like
taken
much
action
other
than
putting
the
initial
set
of
comments
on
it.
So
I'll
paste
it
back
in
here.
So
please
review
this
again.
A
I
was
thinking
of
getting
this
posted,
maybe
on
tuesday
or
wednesday,
during
kubecon.
If
anyone
has
any
thoughts
right
now
about
when
we
should
post
this,
please
type
in,
but
otherwise
I
was
thinking
probably
one
of
the
first
few
days
of
cubecon.
We
could
post
this.
I
think
it's
ready
to
go.
Please
review.
Please
make
comments,
suggestions.
A
A
The
big
contributors
have
done
the
same
so
feel
free
and
we'll
converse
in
the
cncs
slack
channel
and
then
finally,
for
community-wide
things
that
at
least
I'm
tracking
there's
a
maintainer's
track
talk
that
everyone
is
invited
to
I'm
one
of
the
speakers
I
think
ted
and
alolita
and
daniel
are
the
other
speakers.
That
being
said,
if
you're
a
maintainer
like
we'd
love
to
get
you
involved
as
well.
I'll
be
blunt.
We
haven't
actually
really
started
on
this,
yet
so
tbd.
A
A
Okay,
any
other
topics
from
anyone
else
or
any
feedback
on
stuff
for
kubecon.
C
I
just
wanted
to
add
that
your
your
agenda
looks
good,
especially
the
idea
about
discussing
feedback
and
how
we
can
improve
as
a
community,
because
that's
the
the
best
way
of
having
such
such
discussions,
I
think.
A
Yeah
it'd
be
nice
to
do
there
and
and
of
course
like,
I
think,
we'll
kick
it
off
there,
but
like
obviously
not
everyone
is
going
to
be
there.
So
then
we
can
take
it
to
an
online
discussion
or
even
to
this
meeting
afterwards,
but
it'd
be
nice
to
like
jot
down
those
ideas.
B
Okay,
any
other
topics
I
think
aaron
asked
in
the
chat.
If
we
could
talk
about
the
open
source
summit
community
day
erin
did
you
have
a
specific
question
about
that.
B
Yeah,
we
definitely
do
so.
There
will
be
the
community
day
on
june
20th,
which
is
monday.
You
do
not
need
an
open
source
summit
ticket
in
order
to
join.
There
is
a
registration
link
which
I
can
get
for
you.
B
Sorry,
I
should
have
had
it
more
ready
yeah,
so
here
we
go
I'll
put
it
in
the
document.
B
B
If
that
makes
sense,
we'll
have,
I
think,
three
different
rooms,
so
three
different
tracks
to
to
go
for,
and
I
think
one
of
the
rooms
we
wanted
to
dedicate
to
like
smaller
discussions,
you
know
have
a
bunch
of
tables
that
five
or
six
people
can
sit
at
and
have
directed
conversations
essentially,
but
then
we'll
also
have
a
handful
of
like
breakout
workshop
type
of
deals
in
the
afternoon.
B
A
Okay
cool,
so
the
one
follow-up
for
people
today
is
just
for
the
blog
post.
I
will
post
on
the
hotel
slack
channel
suggestions
of
when
we
should
post
it,
and
then
we
can
go
from
there.