►
From YouTube: 2022-02-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).
A
A
A
Okay,
let's
start,
I
will
try
to
try
the
first
part
of
this
call.
Let
me
try
to
share
my
video
having
some
internet
problems
here,
but
hopefully
everything
will
work.
Fine,
okay,
thanks
for
joining.
Okay,
let's
go
over
the
agenda
items.
The
first
one
is
specification,
as
we
are
doing
monthly
releases.
A
We
will
release
latest
week
or
early
next
week,
depending
on
the
metrics
effort,
well
actually
independently,
probably,
but
I
think
that
the
plan
had
been
so
far
that
metrics
will
be
marked
at
this
partially
stable,
at
least
some
of
the
core
components.
A
That's
on
the
specification
part.
There
is
somebody
from
the
matrix
group
around.
A
C
A
Good,
okay,
moving
forward
job
instrumentation,
no
updates,
it
seems
trust
I
saw
you
here,
but
no
notes.
I
am
guessing.
There's
no
nothing
important
this
week
to
report
correct.
Thank
you!
Yeah,
okay,
javascript,
likewise
python
last
big
metrics,
pr,
adding
news
on
the
review.
That's
that's
very
good!
Thank
you
for
that
dot
net!
Yes
individual.net
here!
A
Okay,
I
will
do
that.
Yeah
donald
will
be
doing
a
release
candidate.
Third
one
with
some
metric
improvements,
changes
based
on
recent
spec
updates
and
otlp
fixes
great
go
metrics
api
work
going
and
also
a
new
release
most
likely
this
week,
any
anything
specific
to
us
on
the
go
sides.
A
No,
that
about
covers
it.
Sweet,
simple,
plus,
matrix
sdk
work,
ongoing
yeah.
I
see
that
matrix
is
a
prototype
milestone.
That's
that's
very
good.
A
A
Okay
and
okay.
Moving
to
the
actual
agenda
items,
you
know,
aside
from
the
sega
plates,
the
first
one
is
warning
on
the
otp
protochange.
You
know
I
this
is
from
renaming
instrumentation
library
to
instrumentation
scope.
A
D
It's
going
to
impact
more
than
just
json
as
well,
though,
because
it's
going
to
impact
the
identifiers
in
generated
code
for
languages
that
are
using
protobuf
and,
to
some
extent
they
it
may
be
encapsulated.
But
not
always,
you
know
at
least
go
exposes
a
grpc
client
to
end
users
that
use
these
types.
We've
done.
Some
basic
searching
haven't,
found
anybody
implementing
their
own
producers
to
that
type.
Everything.
B
D
To
be
just
using
that
type,
as
you
know,
constructing
an
exporter
and
using
our
code,
but
there
is
potential
for
breakage
here
and
I
think
that
we
need
to
probably
better
discuss
in
the
specs
sake,
but
we
need
to
reconsider
our
stability
guarantees
for
p
data,
because
I
don't
think
it's
very
reasonable
to
have
a
statement
that
p
data
or
not
sorry,
not
p.
Data
otlp
is
is
stable
for
traces
and
metrics,
but
we're
going
to
reserve
the
right
to
change
identifiers.
You
know
that's
not
very
stable.
A
A
D
Bogdan,
it
is
mentioned
clearly
what
is
stable.
I
think
that
is
old
and
no
longer
appropriate.
Even
if
it's
clearly
stated
it
needs
to
change.
It's
also
clear
that
it
we
knew
it
needed
to
change
by
stating
that
when
json
was
stable,
we
were
going
to
revisit
the
stability
of
field
names.
I
think
we
need
to
do
that
sooner
than
later.
That's
all
I'm
saying
yeah.
A
Totally
yeah
totally
yeah.
Let's
discuss
the
actual
technical
details
tomorrow,
yeah.
I
think
that,
for
today
is
yeah.
The
important
point
is
to
have
all
maintainers
and
reviewers
probably
will
review
this,
and
tomorrow
we
will
have
a
deeper
technical
discussion
there
on
the
impacts
here
and
there.
Thank
you
for
raising
this.
The
next
point
is
psa
maintainer
repository
permissions
yeah,
who
wants
to
take
on
this
one.
B
B
So
what
we
did
was
we
updated
the
community
docs
to
reflect
the
fact
that
some
maintainers
do
have
admin
permissions
to
give
the
tc
time
to
come
up
with
a
more
long-term
permission
strategy
in
the
maintainers
channel.
In
slack,
I
started
a
thread
asking
maintainers
which
admin
permissions
they're
using
if
they
are
using
admin
permissions
in
their
normal
workflows.
B
B
I
can
post
a
link
to
the
actual
thread
here
in
the
dock.
A
B
A
Okay,
let's
wait
for
feedback,
then
that's
all
in
the
agenda
for
today
do
we
have
anything
else
to
discuss
anybody.