►
From YouTube: 2022-02-14 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
All
right
welcome
to
another
week
of
open
telemetry,
we'll
start
with
a
sig
check
in
so
specification.
We
expect
version
1.9
that
was
released
earlier
today.
Do
anyone
here
to
speak
about
updates
on
metrics?
Let
me
just
scroll
through
to
see
if
riley's
here
we
don't
have
riley
anyone
else
have
an
update
on
metrics,
maybe
josh.
B
Hi,
yes,
there
are
a
couple
of
pr's
that
are
open.
Riley
has
his
to
market
stable,
but
we
have
at
least
one
pretty
major
pr,
that's
open
of
mine
right
now.
It's
trying
to
resolve
some
questions
about
instrument,
identity
and
duplicates.
B
A
B
A
C
C
A
I
assume
no
updates
from
java
instrumentation
javascript
working
on
prototypes
for
j
macd's
async
instrument,
changes
that
includes
multi
callback,
identity.
Excellent,
that's
going
well!
So
far.
That's
good
feedback
for
what
just
talked
about
no
further
updates,
no
updates
from
pythonor.net
go
released
version
1.4.0
and
corresponding
version
0.27.0,
plus
no
updates
ruby.
The
main
focus
is
on
building
the
metrics
sdk
awesome
and
no
updates
from
swift,
collector
roster
erlang.
A
We
have
a
point.
A
discussion
point
here
is
the
last
chance
to
last
chance
to
object
to
the
instrumentation
library,
attention,
participation,
scope,
change,
I'm
assuming
that
this
is
just
t
grinds.
Yes,
okay!
A
So
yes,
for
those
of
you
who
haven't
had
a
chance
to
review
this,
it's
been
open
for
a
month
almost
a
month.
So
it's
your
last
chance
to
put
on
comments
or
review
and
otherwise
tigran
is
going
to
merge.
It.
A
And
one
update
for
me,
so
we
switched
to
this
new
zoom
format
a
few
months
ago.
There's
still
some
problems
going
on
as
a
result
turns
out.
It
just
seems
that
zoom
doesn't
like
having
one
account
used
for
a
large
organization,
so
we
will
be
reverting
to
the
older
way.
A
We
did
zoom
meetings
at
some
point
this
week,
where
we're
just
going
to
use
multiple
zoom
accounts
and
just
use
the
the
sort
of
permanent
link,
so
we'll
just
have
to
share
those
around
on
the
calendar
again,
so
that
should
be
a
bit
more
more
reliable
though
it
does
mean
when
people
are
moving
meetings
around
or
creating
new
meetings,
they
need
to
be
careful
to
not
use
the
same
link
as
something
occurring
at
the
same
time
or
before
or
after
I'm,
so
just
an
fyi.
There
may
be
some
changes.
A
There's
also
some
unrelated
issues
with
the
calendar
right
now.
We're
trying
to
get
to
the
bottom
of
that
apparently
kubernetes
was
having
some
problems
and
gcal
just
doesn't
like
having
giant
shared
calendars
at
this
scale.
Unless
you
have
it
in
a
paid
g
suite
subscription,
the
cncf
might
be
able
to
provide
that
for
us,
that's
exactly
what
they're
doing
for
kubernetes.
So
there
may
be
at
some
point
a
calendar
migration
in
the
works,
but
that
is
not
planned.
A
Yet
the
zoom
links
will
be
updated
this
week
and
carlos
fyi
new
environment
variable
for
jager
protocol.
C
Yeah,
that's
correct.
We
are
trying
to
have
a
new
environment
variable,
and
I
am
mentioning
this
because
there
was
some
pushback
in
the
past
against.
I
didn't
get
more
environment
variables.
This
one
feels
important
and
overall,
if
we
accept
that,
of
course,
implementations
have
to
actually
work
on
that.
So
please
review
that.
We
will
discuss
that
tomorrow,
probably
what
any
any
coming
from
the
maintainers
there
could
be
very
welcome.