►
From YouTube: 2021-07-12 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
B
All
right,
I
still
need
to
fill
up
my
camera,
but
so
why
don't
we
get
started
while
I
do
that,
so
welcome
everybody.
I
hope
for
those
who
had
some
time
off,
that
it
was
fun
and
and
enjoyable,
so
we're
we're
back
in
business.
We're
gonna
start
with
the
sig
check-in
and
then
we're
gonna
go
on
to
topics
that
people
have
added
so
starting
for
the
sig
check-in
to
leave
anyone
from
the
specification.
B
Oh
okay,
then
I
will
skip
metrics
as
well.
Do
we
have
anyone
for
logs?
I
don't
think
so,
all
right,
let's
go
into
languages,
so
php,
no
new
updates!
Thank
you.
Bob
java,
1.4,
released
on
friday,
metrics
renovation
is
in
progress.
Thank
you
to
josh
cereth,
all
right
awesome.
Any
updates
from
java
instrumentation.
B
Javascript
no
new
updates
python
1.4
release
expected
tuesday,
metrics
and
logs
prototypes
are
still
in
progress.
Cool
dot,
net
1.1.0,
stable
release
is
expected
today,
cool
metrics
first
alpha
beta
release
delayed
for
one
to
two
weeks.
All
right
go.
I
see
someone's
writing
in
there.
1.0.0
rc2
required
expected
this
week.
Cool
c
plus
1.0.0
rc3
is
planned
to
be
released
today.
B
C
B
Anyone
from
ruby
don't
think
I
see
anyone.
Okay,
swift,
waiting
for
net.host.connection.type
spec
pr
to
merge
before
next
release.
We've
got
a
link
to
that
cool
collector.
I
don't
see
anyone
from
the
collector
group
here,
no
updates
and
then
erlang
no
updates
cool
so
going
into
the
actual
topics
that
people
have
added.
I
have
one
so
ben
sigelman
and
I
had
posted
a
few
months
ago
on
github
a
new
issue
for
the
community
saying
hey.
B
We
should
clarify
our
mission
and
vision
and
so
there's
a
document
that
I've
linked
to
in
our
meeting
notes
that
contains
various
proposals.
For
that
I
think
t
grant
probably
wrote
the
most
comprehensive
one
if
everyone
just
wants
to
take
a
look
at
that,
we
can
do
it
together
as
a
group
now,
if
people
prefer
or
we
can
do
it
offline,
but
it'd
be
good,
like
certainly
speaking
for
the
governance
committee
like
we.
B
If
people
have
ideas
for
mission
and
vision,
we
want
to
hear
them,
and
so
it'd
be
good
for
everyone
to
at
a
minimum
review
this,
and
just
look
at
the
things
that
that
folks
have
added
here
to
comment
if
they
agree
with
it
or
if
this
or
if
they
I
want
some
changes
or,
alternatively,
to
propose
your
own
in
this
document,
probably
not
worth
reviewing
together
now.
B
As
a
group,
I
just
recommend
you
follow
the
link
that
I've
left
there
and
go
and
review
that
or
make
changes
to
it
on
your
own
ted.
I
don't
know
I
saw
you
just
joined.
I
don't
know
if
you
wanted
to
add
anything
to
that.
This
is
the
the
link
to
the
mission
envision.
Sorry
I'll
give
the
context.
This
is
the
link
to
the
mission
and
vision
document.
B
So
it's
just
outlining
that
there's
a
thing
like
the
gc
is
looking
for
more
community
input,
and
so
I
think
tigran
had
a
really
comprehensive
proposal
there,
but
if
people
want
to
add
to
it
make
suggestions,
comments,
changes,
please,
please
do
we're
looking
for
for
more
input.
C
Yeah
yeah,
nothing
to
add.
I
like
tgrins
and
we'd
like
this
to
be
a
community
effort
and
not
just
something
that
gc
slapped
together.
So
please
provide
me
back.
D
Yeah,
so
sorry
for
adding
this
item
out
of
a
sudden,
but
I
think
it's
a
small
change.
I
just
want
to
get
an
opinion
of
everybody
here.
There
is
a
very
valid
change
on
the
el
hotel
exporter,
jager
asian
port.
So
basically
that
means
that
this
environment
variable
will
change
its
default
value.
D
I
wonder
for
everybody
to
know
that
technically
this
is
a
breaking
change.
I
think
you
can
consider
it
can
be
considered
like
that.
I
don't
know
if
anybody
has
something
against
this,
if
not
just
approve
that-
and
this
is
of
course
mostly
aimed
to
language
maintainers,
because
you
know
you
actually
have
to.
Of
course
the
change
itself
is
very
small,
but
I
don't
know
what
how
big
the
impact
will.
C
C
B
D
Yeah
yeah,
we
did
a
release
last
week,
1.5
and
that
that's
all
for
now
there
are
no
schema
changes
still
the
same
schema
so
nothing
to
backboard,
nothing!
Breaking
change!
Sorry!
C
Yeah,
okay,
I
have
one
item:
just
a
shout
out
we're
starting
up
an
instrumentation
effort
at
long
last.
We're
currently
running
that
out
of
the
afternoon
specification,
sig
meeting,
so
every
tuesday
now
there's
a
spec
meeting
in
the
afternoon
at
4
p.m.
Pacific.
C
This
is
because
honorag
is
heavily
involved
in
this
instrumentation
effort.
So
we
want
to
make
this
effort
to
be
asia.
Pacific
friendly.
C
However,
we
are
looking
for
more
people
to
provide
feedback
on
his
proposals
and
to
help
with
the
effort,
I
don't
think
instrumentation
and
managing
all
of
that
should
fall
on
the
maintainers.
C
So
obviously,
if
you
have
time,
that's
great,
but
perhaps
the
a
better
ask
would
be
to
see
if
the
organization
you
work
for
or
people
you
know
might
be
interested
in
working
on
instrumentation,
because
I
think
what
we
need
to
do
here
is
expand
the
number
of
contributors,
not
pile
more
effort
onto
the
existing
maintainer
base.
C
So
if
you
know
people
or
think
you
could
get
some
more
resources
from
the
organization
you
work
at,
please
let
them
know
to
come
to
the
afternoon
spec
meeting
and
say
hi
or
say
hi
in
the
hotel.
Instrumentation
channel
in
slack,
so
that's
my
psa
for
the
day.
C
A
B
Okay,
well,
hopefully,
that
wasn't
terrible.
C
Oh
yeah
sampling,
yeah
we're
also
starting
up
a
sampling
sig
on
thursdays
at
eight
am
pacific
had
first
meeting
last
week
and
so
that's
exciting.
The
focus
right
now
is
on
a
lot
of
making
sure
really
two
parts
one.
What
kind
of
sampling
information
do
we
need
to
be
propagating
in
band
to
in
three
parts?
C
What
information
do
we
need
to
be
propagating
in
band
in
order
to
do
better
sampling,
so
people
want
to
have
proportional
or
weighted
sampling,
rather
than
just
a
sampling
bit,
so
we
need
to
sort
that
out.
The
other
thing
we're
missing
is
out
of
band,
sending
any
sampling
related
information
back
to
back
ends
in
otlp.
C
Has
a
nice
feedback
loop
for
adaptive
sampling
that
they've
developed
and
yuri
over
at
facebook
they've
been
researching
an
improved
version
of
that
adaptive
sampling
workflow,
so
that
would
mean
adding
a
way
to
the
clients
and
the
collector
to
be
able
to
live,
update
the
sampling
rules
so
that
you
could
add
a
control
plane
to
open
telemetry
that
create
a
feedback
loop
with
the
back
end.
C
So
that's
interesting
work,
so
people
are
interested
in
any
of
those
topics.
Please
come
say:
hi
in
the
sampling
meeting
or
again,
there's
an
hotel
sampling,
slack
channel.
You
can
say
hi
there.
B
All
right:
well,
I
think
we
are
out
of
topics.
So
unless
anybody
has
anything
else
play
us
out,
morgan
pardon
play
so
yeah
I
was
gonna.
Do
that
there
you
go
ted
doesn't
realize.
I
accidentally
hit
my
sound
board
at
the
start
of
the
meeting.
I
didn't
notice
because
my
earpiece
was
working
so
here
we
go
alrighty
see
everyone.