►
From YouTube: 2022-03-07 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
Hey
everybody,
I
think
we
we
can
start
a
call
in
one
minute.
I
see
that
morgan
is
not
around
this
week,
so
yeah,
let's
wait
one
more
minute
and
we
can
start.
A
A
Okay,
so
first
of
all
specification
yeah,
I
think
we
will
have
a
release
later
this
week.
We
are
just
waiting
for
some
goodies
to
land
and
then
we
will
be
doing
the
release
next,
one
metrics.
What
about
metrics
any
update,
they're,
rayleigh
or
gem
mcd.
B
A
Great
php,
one
more
release
of
the
concrete
package,
thanks
nice
to
see
that
moving
along
java,
I
think
there's
no
updates.
Okay,
javain's
instrumentation!
Likewise
javascript
metrics
work
proceeding
great
python
python.
We
use
pr
merge!
That's
great
news!
I
think
that
use
is
a
lot
of
work
or
it
has
been
a
lot
of
work
for
for
a
few
implementations.
So
it's
good
to
see
that
work
moving
along
as
well
and
a
new
release
to
be
delivered
in
the
next
few
days.
A
Thank
you
so
much
dot
net
release,
1.20
release
candidate
3,
with
more
metrics
improvements
and
histogram
performance,
optimization,
etc.
Great,
thank
you
so
much
for
that.
A
A
Ruby,
swift,
nothing
to
report
collector
nothing
to
report,
nobody
from
the
collector
team
here:
okay,
so
quiet
weak.
Likewise
for
ross
underland!
Okay!
Now,
let's
move
into
the
agenda,
can't
you
see
members
start
attending
the
spec
seek
goal.
Yeah?
Who
put?
Whoever
put
this?
Do
you
want
to
take
over.
A
C
Yeah
so
spec
we
have
a
bunch
of
suspect
groups
right
now
and
they've
had
a
little
bit
of
a
bumpy
ride
and
I
think
it's
mainly
because
there
isn't
a
tc
member
who's
kind
of
sponsoring
the
work.
C
So
we've
approved
this
work,
but
there's
no
there's
no
sponsor,
so
they
can
get
caught
up
in
the
various
submission
processes,
and
so
the
the
groups
I'm
thinking
of
in
particular,
are
the
client
instrumentation
group
so
rum,
which
meets
wednesday
morning,
and
then
there
are
two
other
instrumentation
semantic
groups.
C
So
on
tuesday
apac
friendly
time
in
the
afternoon,
one
group
meets
they're
mostly
been
focused
on
http,
probably
moving
on
to
databases
and
things
like
that
and
there's
another
group
that
meets
thursday
mornings,
an
eu
friendly
time
right
now,
they're
focusing
on
messaging,
but
there
are
general
like
spec
questions,
for
example
like
links.
How
should
links
be
used-
and
things
like
that?
So
it
would
be
really
helpful
for
a
tc
member
or
two
to
be
assigned
to
to
participate
in
these
groups.
C
I
think
the
lesson
we've
learned
is
that
doing
doing
spec
sigs
like
doing
ongoing,
spec
work
just
works
a
lot
better.
When,
when
there's
a
tc
member
directly
involved
in
it,.
A
Yeah,
that
makes
sense.
We
had
discussed
that
in
the
past
long
time
ago
and
whether
this
would
work-
and
you
know
we
were
not
sure
there
were
a
lot
of
new
things
taking
place,
and
I
think
this
is
it's
time
to
start
doing
that
yeah
in
my
case,
I'm
interested
in
the
instrumentation
a
little
bit
but
yeah.
We
have
to
talk
with
the
rest
of
the
tc
members,
but
I
think
it's
fair.
So
these
three
are
the
ones
that
you
are
thinking
about
as
a
starting.
C
There's
also
ebpf,
they
they
meet
less
frequently,
and
I
personally
have
not
been
following
that
group,
but
I
presume
likewise,
if
they
get,
you
know
kind
of
a
head
of
steam
going
around
ebpf
having
you
know
like
a
tc
member.
Helping
to
guide
them
through
that
process
would
be
good,
so
they
don't
do
a
whole
bunch
of
of
work
or
gets
particularly
set
on
a
certain
direction
only
when
they
they
finally
make
a
proposal
they
get.
A
C
I
think
I
think
the
rum
group
is
in
the
process
of
putting
together
another
otep.
I've
been
helping
to
guide
them
through.
You
know
integrating
it
with
tracing
and
like
how
to
like,
you
know,
making
sure
they're
doing
some
prototyping,
and
things
like
that.
So
I
think
they'll
have
one
coming
soon,
but
that
would
that
would
help.
It
would
be
helpful
to
have
a
a
tc
member
as
part
of
that,
for
example
like
there's
a
concept
of
sessions
and
session
management.
C
That
turns
out
to
be
very
important
for
rum,
that
we
don't
have
a
concept
of
currently
and
then
for
the
instrumentation
stuff,
how
we're
modeling
some
of
these
things
kind
of
expands
the
scope
of
how
we've
thought
about
semantic
conventions
in
the
past,
in
particular,
making
like
a
heavy
use
of
links
and
there's
no
oteps
coming
out
of
those
groups.
Necessarily
right
now,
we've
been
saying
like
these
semantic
convention.
Improvements
can
go
in
directly
as
prs,
but
it
would
be
helpful
to
to
hash
out
details
about
those
pr's
ahead
of
time.
B
For
the
record
ted
I'm
having
trouble
finding
rum
on
the
calendar
and
as
speaking
for
myself,
I
we
have
a
lot
of
early
meetings
in
the
u.s
time
zone
here
so
by
the
time
apac
comes
around,
I'm
I'm
dead.
Basically,
so
I
could
look
at
the
morning
shift
yeah
if
it's
because
but
but
and
I'd
be
glad
to.
C
Great
so
the
it's
called
client
instrumentation
on
the
calendar
yeah.
Maybe
you
can
modify
that
to
to
include
rum
and
that's
wednesday.
8
a.m
at
8
a.m.
Pacific
and
then
there's
the
instrumentation
meeting
8
a.m
on
thursday
and
there's
the
apec
meeting
4
p.m.
On
tuesday
those
are
the
three
I
would
love
to
see.
Cftc
member
at
end.
B
In
that
case
ted
I
mean
we
should
discuss
this
in
another
forum.
Perhaps
those
are
both
double
booked
for
me,
but
we
could
maybe
perhaps
get
them
to
alternate
correctly.
I
I'm
in
the
prometheus
working
group,
usually
on
the
wednesday.
Yes
a
lot
and
I'm
in
the
sampling
every
other
week.
So
if
we
could
spread
out
prometheus
a
little
bit
more,
I
can
go
to
every
other
prometheus
meeting
and
so
on.
That'd
be
great.
C
Okay,
great
yeah-
and
you
know,
there's
there's
other
tc
members,
maybe
maybe
somebody
else
can
attend
and
I'm
sure
bogdan
would
want
to
attend
at
least
a
little
bit
to
one
of
them
that
he
can
make
it
to
talk
about
links,
but
just
in
general
if
they
have,
even
if
it's
like,
I
think
tc
members
handing
it
off
just.
A
Yeah,
fair
enough,
I
will
be
providing
this
input
to
the
tc
and
hopefully
we
will
have
an
update
on
what's
planned
yeah.
We
will
try
to
cover
this
initially,
these
three.
C
C
D
Thanks
for
bringing
it
up
ted
the
the
early
input
and
the
early
feedback
definitely
makes
sense.
I
think
the
instrumentation
group
was
caught
by
by
surprise
that
that
others
are
caught
by
surprise
because
of
the
links
proposal,
for
example,
yeah,
so
that
definitely
makes
sense.
I.
C
E
C
D
We
can't
make
a
make
a
schedule
where
everyone
is
attending
the
meetings
or
or
enough
people
are
attending
the
meetings.
Then
we
can
probably
find
another
process
of
of
involving
people
earlier
before
before
the
finishing
touches
on
the
optip
add-on
and
then,
as
you
said,
it's
it's
just
being
dismantled
too.
C
Late
yeah,
I
think
the
other
reason
I
think
it's
helpful
is
having
these
groups
have
a
point
of
contact,
because
a
thing
that's
also
come
up
is
they've
gotten
stalled
for
one
reason
or
another,
like
you
know,
their
submission
just
gets,
gets
kind
of
stalled.
One
reason
is
they've,
gotten
feedback
that
they
think
is
like
blocking
feedback
and
but
then
the
the
person
who's
making
that
feedback
you
know
got
distracted
or
something
and
isn't
responding
anymore.
C
So
it's
helpful
to
have
you
know
it
it's
helpful
to
if
they
have
a
point
of
contact
on
the
tc
who's.
Like
part
of
the
group,
I
think
that
will
help
get
those
things
unstuck
when
they
happen.
The
the
other
thing
that
comes
up
is
not
stalled
because
feedback
from
a
tc
member
comes
in,
but
it's
more
like
something
gets
proposed
and
the
community
seems
a
little
split
about
what
the
right
way
to
go
is.
C
You
know
like
one
example
is
like:
should
400
http
400s
be
marked
as
errors
on
the
client
right
and
there's
like.
If
you
look
at
that
issue,
you
know
there's
some
people
who
are
like
yeah.
They
should
not
be.
This
is
like
just
noise
and
we
should
like
be
just
selectively
enabling
this
with
collector's
stuff
and
there's
other
people
who
are
like
no,
it's
it's
proper
for
400s
to
get
marked
as
errors
on
the
client.
C
So
we
should
do
it,
but
then
the
person
making
the
the
pr
doesn't
really
have
the
ability
to
to
like
make
a
decision.
You
know
so
it
needs
someone
to
to
kind
of
come
in
and
make
a
decision.
I
think
that'll
just
work
better
if
there's
like
a
tc
member
who's,
who's
kind
of
like
following
the
work,
so
so
for
all
those
reasons,
I
think
it'll
be
very.
D
A
F
Yeah,
I
think
mine
took
about
two
months.
This.
C
E
A
D
F
C
Yeah
yeah,
basically
that
it's
especially
trying
to
organize
getting
space
in
in
spain.
This
is
a
little
extra
complicated
for
us
in
the
u.s,
but
our
plan
is
to
try
to
organize
one
at
kubecon
in
a
this
year.
C
C
C
Yeah,
but
we
just
need
some.
Basically,
it
comes
down
to
someone
being
able
to
book
book
a
book
of
space.
So
if
anyone
knows
how
to
do
that
in
barcelona,.