►
From YouTube: 2021-08-23 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).
C
B
D
Hey:
hey
everybody:
let's
wait!
Two
more
minutes.
I
see
nine
people
now,
but
I
suspect
more
people
may
be
joining
soon.
So
let's
wait
two
more
minutes.
Meanwhile,
please
think
about
anything
important
in
case
you're,
forgetting
about
something
now
it's
your
time
to
think
about
that
and
include
that
in
the
agenda.
D
Okay,
let's
start,
I
see
only
11
people
today
I
don't
know,
maybe
people
are
on
holidays
or
having
meetings.
In
any
case,
thanks
for
joining
just
for
the
record,
I
changed
the
notes
to
point
to
a
new
document.
As
you
can
see,
only
the
entries
for
august
are
included
yeah.
Basically,
we
don't
want
to
have
any
problems
with
the
sluggish
documents.
D
Okay,
agenda,
so
specification,
we
will
be
having
a
release
in
two
weeks
for
your
information,
so
in
case
there's
something
important
that
you
want
to
do
you
think
it's
important
includes.
Do
you
still
have
time
to
do
that?
That's
about
it.
I.
A
D
That's
a
great
question:
I
was
asking
that
to
tigran.
He
hasn't
told
me
what
he
thinks
about
this.
I
think
yes,
we
will,
even
if
it
gets
slightly
delayed
because
of
those
changes.
So
actually
it's
a
good
reminder.
I
don't!
Oh
no.
I
don't
see
it
I'm
here,
but
it's
a
good
reminder.
Let
me
add
a
note
there
for
myself.
I
noticed
in
the
document.
A
This
one
might
be
a
little
bit
strange
because
some
of
the
constants
that
were
put
in
there
were
kind
of
invalid
constants,
and
so
there
might.
The
mapping
might
be
a
little
bit
weird
to
figure
out
how
to
deal
with,
but
yeah
totally
we're
we're
trying
to
figure
out
in
java
whether
we
should
go
use
1.6
or
just
skip
it
all
together
and
wait
for
1.7
for
cement
conventions.
A
So,
just
due
to
those
kind
of
strange
issues
on
those
constants.
D
Yeah,
that's
a
very
cool
yeah.
Okay,
so
we'll
be
talking
to
tigran,
we'll
let
you
know
but
yeah.
Thank
you
for
the
call.
D
E
D
E
D
F
F
F
D
Okay,
php.
B
G
And
hi
everyone-
this
is
alita
just
to
add
to
bob's
update.
We
are
trying
to
assign
some
a
couple
of
contributors
to
the
php
repo
so
that
we
could
actually
they
could
actually
make
some
progress.
There's
a
really
nice
backlog,
but
our
interns
who
are
working
on
it
this
week
summer
have
finished
so
we'll
continue
with
other
full-time
engineers.
A
Yeah,
as
I
commented,
metrics
work
is
continuing
other
than
that
just
small
additions
and
normal.
D
Great
pretty
good
to
see
that
coming
javascript.
F
F
So
I
know
in
the
past,
I've
talked
about
how
we
have
many
components.
In
the
same
repository,
only
some
of
them
are
going
to
1.0
as
part
of
the
sdk,
and
some
of
them
will
be
held
back
as
zero
dot.
You
know
something
and
the
tooling
changes
that
we
made
to
allow
the
the
versions
to
be
different,
like
that
uses
a
bot
that
runs
through
github
actions
and
when
it
makes
the
pr
it
fails.
The
cla
check.
D
Makes
sense
yeah,
let's
keep
that,
hopefully
that's
resolved
soon,
so
we
can
get
an
actual
release.
Let's
talk
offline,
if
needed
as
needed.
Okay,
perfect
python.
D
Great
looking
very
good,
thank
you
for
that
c,
plus
plus
I
suffers
that
lalit
is
not
around
today,
but
I
see
some
notes.
So
whoever
is
writing.
Maybe
you
want
to
talk
about
the
progress.
E
D
Nice
pretty
sweet.
Thank
you
for
the
update,
collector.
J
J
J
I
hope
we'll
have
that
done
today
in
the
interim
we've
frozen
prs
coming
into
either
of
the
repos
just
to
make
sure
that
the
history
doesn't
diverge
too
much
while
we're
working
on
it
and
anybody
who
has
a
pr
outstanding
against
either
repo
may
need
to
update
their
prs
once
we're
done
with
this.
But
we
will
communicate
that
in
the
slack
channel.
G
G
J
Yeah
there
were
actually
two
releases
last
week.
Point
32
did
not
include
all
of
the
changes
necessary
for
the
0.9
labeled
attribute,
renaming
and
metrics,
so
that's
been
redact
or
retracted.
Hopefully,
go
shouldn't
pick
that
up
if
anybody
tries
to
do
a
build
and
all
of
the
the
collector
repos
have
been
updated,
but
just
know
0.32
is
not
a
good
release.
To
try
to
use
0.33
is
where
you
want
to
be.
D
Make
sense,
thank
you
for
that.
I
added
a
note
for
that
as
well.
So
people
know
that
there's
a
new
release:
okay,
tyler
there's
a
point
about
golang
meeting
notes.
Please.
I
Yeah,
I
don't
know
if
it's
actually
worth
breaking
up,
I'm
looking
at
the
attendees
list
and
nobody
here
is
from
google,
so
maybe
I'll
ping,
somebody
in
slack,
but
we've
lost
right
access
to
the
doc.
At
least
I
did,
and
so
I
need
to
get
that
result.
I
don't
see
anybody
on
here
from
google,
I'm
pretty
sure
it's
still
owned
by
somebody
from
google,
so
we
may
also
just
need
to
update
the
doc
and
make
a
new
one
but
yeah.
I
guess
no
big
deal.
D
I
I
remember
we
kind
of
talked
about
this
last
time.
Is
there
like
a
a
cncf
account
that
can
own
these
or
have
there's
any
movement
movement
on
that?
Like
I
don't
understand
who
should
own
the
docs,
I
guess.
G
I
think
tyler
I
also
brought
this
up,
and
the
discussion
in
the
gc
was
that
there
is
an
account
for
open
telemetry,
except
that
you
know
all
documents
obviously
are
not
associated
with
it
and
maybe
going
forward.
We
could
do
that,
but
so
far
the
documents
have
been
individually
owned.
As
you
know
so,
yeah
we
could
totally
and
should
use
it.
I
guess.
I
Okay,
cool
and
then
please
just
ping
me
a
few
yeah
windows.
G
G
In
the
meantime,
tyler
did
you
want
to
just
open,
create
another
doc
just
to
make
progress.
I
G
G
D
Thank
you
lolita
for
taking
on
this.
I
really
appreciate
it.
Okay,
before
we
move
on,
we
lost
a
small
update
on
the
airline
side.
Tristan
do
you
want
to
mention
what's
happening
there.
K
Oh
yeah,
it's
just
been
getting
a
lot
more
user
feedback
in
the
coming
in
the
recent
weeks.
So
getting
some
good
bug,
fixes
and
convenient
stuff
and
docs
worked
out
new
release
coming
soon
and
I'm
still
hoping
that
I'll
be
able
to
dedicate
my
time
to
metrics
soon.
D
Perfect
nice,
thank
you
for
the
update.
Finally,
there's
an
item.
I
put
there
myself,
it's
about
otp
transport
configuration
environment
variables
to
basically
configure
what
do
you
want?
How
do
you
want
to
use
otlp,
including
the
transport
and
other
stuff?
Well,
no!
Actually,
it's
only
the
protocol
this
time.
This
is
something
by
the
way
that
we
left
out
of
1.0,
and
there
is
this
pr
anything.
D
I
think
it
looks
great,
but
we
need
some
actual
approvals
from
from
all
the
maintainers,
because
this
is
going
to
impact
whatever
you
have,
so
we
don't
have
to
discuss
it
now.
We
can
discuss
it
tomorrow,
but
probably
since
I
have
enough
maintainers
here
today,
we
can
get
some
initial
review
on
that
and
let's
discuss
that
tomorrow
in
more
depth.