►
From YouTube: 2021-10-28 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).
B
B
B
Active
open
telemetry
is
yes.
I
was
a
little
worried
like
when
we
declared
tracing
ga.
I
was
like.
I
hope
people
stick
around
and
they
don't
just
say
like
well.
It's
done.
I'm
finished,
but
no
we've
done
so
much
this
year
and
metrics
by
the
way.
Most
of
that
thanks
goes
to
you
riley
for
driving
this
so
hard.
So
thank
you.
B
You
clearly
knew
a
thing
or
two
about
driving
a
large
cross-functional
team,
so
thank
you.
A
I
think
it's
been
three
minutes.
We
can
start.
I
know,
there's
a
parallel
work,
trying
to
update
the
overall
like
open
parametric
status
and
also
draw
the
roadmap
for
next
year.
So
a
lot
of
folks
might
be
busy
I'll
try
to
keep
this
meeting
short.
So
first
thing
the
sdk
spec
is
visual
freeze,
so
thanks,
alright
good
job
and
there's
a
feature
matrix
already
merged
and
and
I've
seen
cg
already
updated
the
donate
status.
A
So
the
ask
is,
if
you
work
on
specific
language
like
implementation,
it
is
time
to
update
the
metrics
and
just
be
aware
that
matrix
is
not
fully
up
to
date,
I'll
I'll,
do
another
review
and
and
keep
that
as
close
to
the
spec
as
possible.
B
A
No
it'll
be
next
week
because
the
feature
freeze
just
happened
this
morning.
Okay,
there
you
go
okay,
cool
yeah
and
meanwhile,
if
you're
working
on
individual
language-
and
you
have
some
good
idea
about
like
the
the
matrix
sdk
implementation
timeline,
please
go
and
help
josh
suresh
who
has
been
driving
this
effort.
So
there's
a
separate
document.
They
draw
the
picture
what
people
can
expect
as
a
user.
So
you
want
your
language,
isdk
roadmap
to
be
mentioned
there
and
moving
next.
A
So
this
one
is
specific
about
the
sdk
feature
freeze,
but
we
do
have
some
exporters
and
if
you
look
at
the
explorers,
I
I
think
the
in-memory
exporter
and
the
stood
out
or
the
console
exporter
are
fairly
straightforward.
So
we
should
be
able
to
declare
them
as
feature
freeze.
I
was
in
the
pr
today
the
premises.
One
currently
looks
too
simple.
A
A
The
console
one
is
also
simple.
The
premise
is
when
I
figure
we're
lacking
a
lot
of
details,
so
with
this
one
I
I
don't
feel
confident
or
like
it
feels
ridiculous.
If
we
just
declare
this
as
feature
freeze,
so
maybe
we
should
add
more
requirements,
and
I
know
there
are
environmental
variables
we
might
need
to
add
here,
like
the
important
those
things.
A
And
then
we
should
focus
on
the
stable
release.
So
if
folks
remember
how
we
work
on
the
stable
release
of
tracing
early
this
year
or
last
year,
I
I
think
there
are
a
couple
of
things
we
need
to
do
number
one
is:
we
need
to
continuously
monitor
the
incoming
pr
and
issues
for
metrics,
and
maybe
we
should
do
a
weekly
triage
this
time.
I
I
think
it's
a
little
bit
different
because
last
year
I
think
there's
so
many
things
going
on
and
we
ended
up
having
a
separate
friday
triage
meeting
in
the
early
morning.
A
This
time
I
I
guess
more
than
maybe
we
can
just
use
the
tuesday
meeting
to
do
the
triage.
So
we
have
20
minutes
yeah
and
I
can
cover
that
ask
is,
if
you
work
on
the
metrics
part,
you
see
a
specific
issue
or
you
open
the
issue
I
want.
I
want
you
to
join
the
tuesday
meeting
so
when
we
charge
that
you
can
represent
your
voice
because
we'll
make
hard
decisions,
whether
we
take
it
or
not,
and
all
these
issues
will
be
focusing
on
the
bug,
fixing
or
change
the
wording.
A
Further
clarification,
no
feature
will
be
taken
because
we're
already
feature
freeze
and
if
you
have
other
feature
ask-
and
you
can
also
open
the
issue
and
and
at
the
end
of
the
triage
I'll
put
that
as
the
v
next.
So
we
already
have
already
created
a
project
to
try
to
track
what
matrix
6
should
do
after
stable
release.
So
we
can
cover
that
there.
There
are
many
things
like
the
bundle
api
thing.
You
can
also
see
that
from
the
dock
from
job
storage,
and
then
I
have
a
two
small
prs.
A
They're
simple,
this
one
is
basically
a
like
a
user
from
the
community.
It's
asking
for
some
further
clarification,
because
the
original
wording
was
not
clear.
The
the
ask
is
if
the
view
is
providing
a
list
of
keys,
but
the
measurement
report
some
some
key.
That
is
not
fully
aligned.
What
should
be
the
behavior?
Should
we
drop
the
entire
thing
or
we
just
take
the
intersection
part
and
the
answer
is
we
take
the
intersection
right?
A
A
A
A
A
My
gut
feeling
is,
there
doesn't
seem
to
be
a
lot
of
asks.
Like
demons
were
already
feature
freeze
and
this
one
is
trying
to
add
something
to
permissive
exporter
that
which
is
not
feature-free,
so
we
might
be
able
to
do
it
technically.
But
given
I'm
not
seeing
a
lot
of
ask
and
and
looking
at
the
participants
here,
it
doesn't
seem
it's
very
hot
topic,
so
maybe
we
should
just
move
this
after
stable
release.
That's
my
default
answer.
A
Sounds
good,
okay,
so
so
moving
forward.
I
expect
we
do
less
of
this
kind
of
triage
here.
We
should
do
that
in
a
tuesday
meeting,
because
this
decision
will
probably
need
more
feedback
from
other
folks
and
and
for
this
meeting
I
think
we
should
keep
it
in
case.
There's
some
like
deep
dive
or
any
topic
that
requires
metrics
experts.
So
we
don't
use
the
20
minutes
to
talk
about
something
other
folks.
Don't
care
about
in
a
tuesday
meeting
sounds
good.