►
From YouTube: 2021-03-29 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
A
D
A
A
E
E
Besides
that,
I
don't
know
what
else.
Okay.
E
House
there
were
only
there
were
a
couple
of
pr's
merged
for
that,
but
I
think
I
think
riley
will
be
a
better
person
to
give
you
an
update
for
that.
C
Right
yeah,
so
so
we
already
clarified
the
meter
provider
and
meter
interface,
and
it
seems,
like
most
other
folks,
are
happy
currently
we're
working
on
the
synchronous
instrument.
We
start
with
counter
and
I
hope
we
can.
We
can
address
the
asynchronous
instrument,
something
like
a
gauge
I
end
of
this
week
and
after
that
we
should
have
a
like
a
reasonable
set
of
apis
to
start
with
and
we'll
do
the
prototype
within
a
small
list
of
selected
languages.
We
don't
try
to
do
that.
C
Broadly
and
after
that,
we'll
work
on
the
sdk
stack
and
we
target
end
of
may
for
the
experimental
release.
So
anything
else
that
can
be
added
later
will
not
be
in
the
in
in
the
scope
for
now
and
people
talk
about.
Can
we
have
a
like
transactional,
metrics
api?
Those
things
are
something
nice
to
have,
but
we
won't
add
that
before
we
have
a
reasonable
set
of
api
and
sdk
at
the
beginning,.
A
Okay,
thank
you
all
right.
Php
do
we
have
bob.
A
B
D
Other
updates
yeah
just
a
couple
of
new
just
a
couple:
new
instrumentations
fixing
some
old
instrumentations
and
smoke
tests
on
windows,
containers,
which
I
thought
was
cool
and
nikita
nikita
did
all
of
that
work.
Cool.
A
G
Yeah.
Okay,
sorry
for
python,
I'm
not
a
maintainer,
but
I
saw
that
they
did
release
1.0.
E
C
Oh
yeah
looks
like
cereal
is
not
here
so
for
donut.
There's,
no
major
change
folks
had
the
1.1
video
release
and
I
I
think
they
still
try
to
bake
it.
Last
time
we
updated
there
will
be
one
one
month,
big
time.
So
now
it's
like
a
couple
weeks.
C
A
F
Yeah
yeah,
that's
just
for
the
specification
audit.
It's
kind
of
we're,
probably
gonna,
just
like
reassign
those
this
week
to
get
that
complete
and
then
overall,
the
rc
project
is
the
one
that's
actually
tracking
our
release
candidate,
that's
down
to
21
issues,
down
three
issues
from
last
week
and
I
think
the
more
important
thing
is
like.
Last
week
we
had
kind
of
mentioned
that
we
could
definitely
use
some
help.
F
Aleda
and
anthony
have
unleashed
a
hoard
of
aws
interns
our
way,
although
this
time
it
looks
very
structured
and
I
have
anthony
there
to
help
corral
them-
I
guess
or
hurt
them
so
that
plus
we
have
a
returning
approver
to
the
project.
So
hopefully
the
velocity
should
increase
excellent.
The
next
few
weeks,
yeah.
H
C,
plus
plus
yeah,
so
we're
still
working
on
the
there's,
no
change
from
what
we
have
been
planning
coming
as
last
week.
So
we
did
alpha
release
vita
release.
We
are
planning
for
april
and
and
then
release
candidate
for
may
end
that,
based
on
that,
we
have
consistent
contributions
coming
for
next
two
months
I
mean
we
have
definitely
asked
for
marinata
to
get
some
resources
and
based
on
those
assumptions
that
we
are
going
to
get
enough
contribution
for
next
two
months.
I
We're
we're
still
working
towards
our
sea.
We
still
have
two
open
issues
I
feel
like
we
had
two
officially
open
and
one
unofficially
opened
that
kind
of
was
holding
up
our
rc
and
that
unofficial
one
has
merged
in
and
is
causing
some.
I
don't
know
the
some
of
the
current
powers
need
to
resolve
some
some
conflicts
as
a
result
of
that.
But
the
the
two
issues
that
we
need
to
resolve
have
open
prs.
They
just
kind
of
need
to
be
finished
up
so.
J
Let's
see
yes,
so
nacho
got
a
first
pass
of
the
network
instrumentation
in
its
own
branch
on
the
repo
and
carlos
reviewed,
a
bunch
of
stuff
and
added
a
bunch
of
tickets
to
get
things
in
line
with
the
spec.
So
that's
really
great
thanks
carlos.
E
I
added
some
some
text
there,
but
essentially
we
are
tracking
phase
1g.
You
can
look
at
our
documents
of
how
we
plan
to
to
stabilize
the
collector
we
are.
We
were
promising
to
have
this
by
the
end
of
the
month,
but
I
think
we
are
behind
the
schedule.
I
mean
I'm
pretty
confident
we
are
behind
the
schedule.
We
have
probably
around
20
items
left.
We
got
some
good
help
from
datadog
and
from
from
amazon
thanks
thanks
for
that,
but
we
we
still
have
work
to
do.
A
All
right,
any
other
sig
updates
that
we
didn't
capture.
I
think
we
ran
through
the
gamut,
but
there's
always
a
chance,
no
okay.
So
to
grant.
I
see
you
crossed
out
your
request
for
help
from
governance
council
from
for
getting
mpl
licensing.
Do
you
need
anything
else
to
get
that
unblocked.
A
All
right
and
ted
we've
got
fyi
pushing
back
the
convenience
api
project
feels
like
there
are
not
enough
resources
to
focus
on
this
and
instrumentation.
Okay,
fair
enough.
We
will
continue
to
work
on
user
studies
and
acquire
feedback.
If
someone
else
wants
to
lead
a
resource.
This
then
take
it
on
by
all
means.
Okay
is
ted
on
the
call
yeah
I'm
here.
Oh
there,
you
are
oh
great
sorry,
yeah.
K
K
Matt
mccleary's
doing
some
awesome
work,
getting
user
studies
like
user
research
for
this,
and
so
we
can
continue
to
collect
feedback
and
put
it
back
on
the
schedule
when
it
feels
like
our
plates
are
a
little
less
full.