►
From YouTube: 2022-05-02 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
C
A
A
Okay,
apparently
morgan
can't
make
it
today.
So
let's
go
over
the
the
room.
Do
quick
updates
on
the
on
the
sigs
for
the
specification.
I
think
it's
time
for
the
monthly
release.
I
didn't
see
the
pr
carlos
you
usually
do
that
you
know
where
we
are.
C
Correct
yeah,
so
basically,
I
think
that
in
in
previous
times
we
delayed
the
release
started
the
amount
because
metrics
now
we're
fine,
so
only
is
there's
a
certain
reason
not
to
do
it
we'll
do
it
today
sounds
good.
A
Metrics
any
updates.
We
have
riley
josh
anyone
anything
new.
B
I
don't
think
we
have
anything
new
today.
I
know
riley's
trying
to
get
the
exponential
histogram
spec
merged
other
than
that.
I
think
we're
just
heads
down
on
the
stable
sdks.
A
Thank
you
for
logs.
We
are
done
with
looking
at
what
else
we
may
need
to
be
doing
for
otlp
logs,
so
we're
preparing
to
declare
them
stable.
A
A
Okay,
python
five
issues
for
metrics
rc,
five
issues
remaining-
I
guess
that's
what
it
means:
okay,
dot
net,
nothing
there
go
metric,
sdk,
alpha,
release,
31
open
it
closed,
31,
open
remaining!
Is
that
what
it
means.
A
Okay
release
1.7
last
week,
good
c
plus
plus
metric
sdk,
alpha
12,
close
to
remaining
nice
contributor
required
for
log
sdk
work
to
make
it
compliant
with
the
specs
on
c
plus,
plus,
okay,.
A
If
anyone
is
interested,
please
get
in
touch
with
the
c
plus
plus
sig,
ruby,
no
new
status,
metrics
and
contribute
split
are
still
the
main
focuses
with
no
news.
There
collector
0.50
released
last
week,
rust
erlang,
nothing
new
community
demo
application.
The
first
meeting
happened
or
is
about
to
happen.
I'm
not
sure
what
the
update
means
there.
A
Happened:
okay,
cool
gathering,
personas
and
requirements;
okay,
and
we're
done
with
the
sig
updates.
I
have
posted
a
link
to
the
otep
that
adds
attributes
to
the
scope
and
it
would
be
great
to
have
maintainers
review
the
proposal
because
it
impacts
all
the
languages
and,
if
possible,
please
give
an
answer
to
two
questions:
can
this
be
done
without
breaking
the
existing
implementations,
the
apis
and
and
if
yes,
can
be
done
in
a
way
that
is
reasonably
efficient?
A
We
can
yeah,
we
can
do
that.
I
mean
I
don't
know
we
can
do
that
now
as
well,
but
I
I
wonder
if
people
are
prepared
for
the
discussion,
probably
let's
give
everyone
a
bit
time
to
read
the
whole
tap,
and
maybe
we
can
dive
a
bit
deeper
tomorrow
if
that
works,
and
the
offline
discussion
is
fine
as
well
right,
if
you,
if
you
want
to
commenting
on
the
ottap,
that
that's
that's
great
as
well.
C
A
Possibly
we
could
do
that.
I
guess
the
prototypes
unless
we
go
ahead
and
do
the
changes
that
we
need
to
do
on
the
otlp
as
well.
It's
going
to
be
difficult
to
have
functioning
prototypes.
I
mean
they.
We
can
show
what
the
api
is
going
to
look
like,
but
not
have
the
full
implementation
that
actually
ends
up
emitting
the
the
attributes
in
the
in
the
protobufs
later.
A
So
I
it
depends
on
how
how
elaborate
we
expect
the
prototypes
to
be
right.
If
it's
just
to
demonstrate
the
api,
it's
probably
easy
to
do.
Relatedly.
Maybe
I
could
do
one
for
go
I'm
a
bit.
I
guess
I
know
the
code
base
a
bit,
not
so
much
for
the
other
languages,
but
if
the
maintainers
feel
comfortable
like
they,
they
can
actually
confirm
that
this
is
doable.
A
A
C
Yeah
that
makes
sense
yeah,
I
think,
in
the
past
we
have
rotated
for
one
or
two
languages.
Only
so
only
is
it
something
very
political
context:
propagation
yeah
yeah,
because
I
saw
that
you
already
have
some
changes
for
the
otlp
part
so
for
the
protocol,
so
that
that's
fine,
I
think
that's.
A
That's
the
easy
part
I
mean
that's
that's
I
mean
I
feel
confident
about
that
part,
the
apis,
the
sdks
in
the
languages.
That's
the
part
that
I
I
don't
know
right.
I
hope
everything
is
fine,
but
the
maintainers
are
the
the
experts
in
their
their
languages,
so
they
need
to
tell
whether
it's
doable
or
not.