►
From YouTube: 2021-08-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).
A
Hey:
hey
everybody.
Let's
start
in
one
or
two
minutes.
Please
add
yourself
to
the
agenda
as
usually
and
yeah
anything
you
want
to
discuss
to
the
agenda.
A
A
Okay,
yes,
we
can
start.
Thank
you,
everybody
for
joining
yeah,
let's,
let's
get
on
with
the
with
agenda.
Okay,
actually
it's
morgan
here
or
probably.
B
I
think
splunk
has
what
they
are.
According
to
the.
C
No
prob
already
so
first
things,
first,
just
going
through
the
updates
anything
from
the
spec
spec
meetings.
D
One
quick
thing
from
my
side:
the
the
matrix
api
should
be
good
to
go
for
the
next
release
for
feature.
Freeze,
sdk
is
making
progress.
We
unblocked
the
the
view
pr
now
it's
already
merged.
I
I
think
we
have
two
other
issues
to
work
on
the
sdk
before
we
can
call
that
experimental
awesome
so
far,
good
progress.
C
C
Great,
I
see
otlp
there's
changes.
A
Yeah
I
put
that
one
there.
This
is
just
for
you,
information
for
maintainers.
A
We
will
be
changing
the
default
port
for
otlp
http
http,
basically,
because
it's
just
not
a
good
idea
in
general
to
have
both
ports,
both
hddlp
and
otp,
over
grpc
in
the
same
port,
so
we're
changing
them,
and
this
will
be
the
default,
as
I
said
just
for
your
information,
if
you
think,
if
you
have
anything
to
comment,
just
please
please,
let's
do
the
please
do
that
in
the
issue,
or
we
can
discuss
that
tomorrow,
other
than
that,
I
think
we're
good
to
go
with
that
one!
Okay!
E
Things
are
moving
along
a
little
bit,
we've
been
working
on
the
contributor
and
we've
gotten
aws,
doohickey,
all
wired
up
and
stuff,
and
we're
going
to
get
some
more.
Some
more
aws
engineers
engage
with
the
projects.
C
Yeah
all
right,
nice
js
things
are
chill
python.
Things
are
chill
net,
just
prototyping
the
sdk.
It
looks
like
yep
nice
go
release
candidate,
two
coming
along
stable
release,
project
yeah
anthony
sounds
like
you
guys
are
getting
getting
close
to
1.0
there.
F
I
hope
we
are
yeah,
we
shipped
an
rc2
just
to
get
because
we
had
a
bunch
of
things
that
we
fixed
after
rc1,
but
we
weren't
sure
when
we
would
be
done
with
this
project.
So
so
we
got
an
rc2
out
just
to
get
more
feedback
on
the
things
we've
fixed,
there's
about
a
half
dozen
tasks
that
are
remaining,
some
of
which
are
we
just
need
to
like
build
out
tests
or
proof
of
concept
to
say.
No.
F
This
is
not
a
thing
we
want
to
do,
but
there
are
probably
three
or
four
things
that
we
we
still
absolutely
need
to
get
done
before
we
hit
an
rc
and
we're
hopeful
that
1.0
might
happen
this
month
if
we
can
get
an
rc3
out
with
all
of
these
address
for
the
next
couple
weeks.
Awesome.
C
Awesome
I'll
check
I'll
check
it
out
this
week
and
see
if
I
can
provide
some
feedback,
but
that's
great
to
hear
cool
c,
plus
plus
just
chillin.
C
Anyone,
I
think
we
don't
have
anyone
from
ruby
here.
Anyone
from
swift
here,
I
think,
no
and
likewise
collector
no
collector
updates.
How
are
things
going
on
the
collector.
F
Point
31
was
released.
I
know
we
did
contrib
at
least
last
week.
I
I
think
that
the
core
had
been
released
slightly
before
that.
I
think
we
are
very
close
to
finishing
out
the
last
tasks
on
the
trace
stability
phase,
one
milestone
and
we'll
continue
on
with
phase
two
of
that
awesome.
C
Also
russ,
I
have
not
checked
in
on
the
rest
group
in
a
while,
and
I
kind
of
wonder
how
they
are
doing.
Has
anyone
else
here
checked
in
on
rust?
Recently
you
have
some
few
prs
and
we
start
working
on
the
road
map
to
the
ja.
C
Okay,
great,
so
is
there
a
weekly
rest
meeting?
Is
that
still
happening?
C
It
hasn't
been
happening
for
a
while,
because
the
last
time
we
have
it
doesn't
really
much
like
people
show
up,
but
I
will
try
to
get
that
stop
again
yeah
if
it's,
if
it's
useful
to
you
guys
great
thanks
for
the
update
all
right,
riley's
got
some
donations.
D
Yeah,
so
we
have
a
small
component
in
esp.net
repo
that
has
been
sitting
there
for
about
10
years
and
recently
we
have
some
integration
working
in
open
time
trade.net.
So
we
start
to
realize
it
will
help
the
community.
We
can
move
that
report
because
all
the
logic
there
is
wind
agnostic,
nothing
specific
to
microsoft
and
it's
just
a
glue
code.
D
C
D
And
the
challenge
is:
if
that
report
sits
in
the
asp.net
repo
it.
The
release
cycle
is
a
little
bit
tight
with
the
aisp
all
night.
One
well
open
time
trading
is
moving
faster
and
we
do
have
some
maintainers
trying
to
contribute
back,
although,
like
the
pr
got
merged
very
quickly,
but
they
were
notified.
That
release
will
wait
for
a
bigger
trend,
which
makes
us
a
little
bit
slow
down
yeah
and
in
general.
C
That
makes
a
lot
of
sense
to
me.
This
doesn't
seem
like
a
kind
of
donation
that
needs
a
huge
amount
of
oversight.
The
way
things
like
flowmill
or
something
like
that
might
might
need
oversight.
So
right
yeah
definitely
poke
the
tc
about
it,
but
but
it
seems
if
it's
not
going
to
modify
the
spec
or
or
anything
like
that,
then
I
would
say
just
go
for
it.
A
D
C
Cool
awesome
awesome,
awesome:
okay,
thanks
yeah,
all
right
bob
soliciting.
E
Yeah,
so
this
I
just
wanted
to
ask
everybody,
so
we
could
get
sort
of
like
a
group
consensus
on
this.
I
got
solicited
to
talk
at
some
san
francisco,
observability
meetup.
I
probably
don't
want
to
do
it,
but
I
didn't
know
if
other
people
are
getting
solicited
by
outside
agencies
to
talk
about
open
telemetry.
I
don't
know
what
our
official
stance
is
on
that
and
I
don't
know
if
there's
a
way
we
wouldn't
handle
that,
like
maybe
I'd,
say
hey,
I
don't
want
to
do
this.
E
C
C
So
if
you
want
to
go,
give
a
give
a
talk
feel
free
bob.
As
for
like
when
someone
reaches
out-
and
you
don't
want
to
do
it
because
you're
just
not
available
yeah,
you
could.
You
could
maybe
just
point
point
them
at
the
open,
telemetry
slack
or
something
like
that.
Is
there
a
maintainer's
mailing
list.
C
We
barely
use
our
our
main
open,
telemetry
mailing
list,
but
there
there
is
the
maintainers
slack
channel
that
might
be
a
place
to
direct
people,
cool.
E
C
Yeah
yeah
or
just
sending
them
on
to
individuals
that
you
know.
That's
that's
usually
what
I
do.
If
I
don't
want
to
take
something,
is
I
just
think
about
someone
who
might
be
interested
in
it
and
hand
them
off
to
them
by
email
yeah
if
they're
a
good
organizer
they'll
find
somebody
else,
so
I
wouldn't
worry
about
them
too
much.
C
Okay,
alex
one
password.
B
Yeah,
I
just
wanted
to
bring
attention
to
everybody
that
this
is
a
thing
that
we
have
access
to.
Now
we
have
an
open,
telemetry
organization
account
if
you
have
credentials
that
you
need
to
share
as
maintainers
feel
free
to
reach
out,
and
I
can
get
you
added
to
their
organization.
B
Currently,
there's
only
me
and
laden
one
of
the
other
maintainers
on
the
python
group
in
the
org,
but
if
folks
have
need
for
this,
just
feel
free
to
reach
out
or
whatever.
C
I
think
I
I'm
having
a
vague
memory
around
documentation
right.
There
is
some
kind
of
code
trigger
that
has
to
happen.
Oh.
B
C
C
Cool
beans,
so
yeah
sounds
like
a
good
thing
for
all
maintainers
to
go
ahead
and
get
access
to,
because
you
don't
want
to
be
scrounging
around
trying
to
set
this
up
the
moment
you
realize
you
need
access
to.
A
C
B
C
They
might
have
them
everyone
on
the
call.
Do
you
mind
just
dming
alex
your
preferred
email
address
for
one
password
in
slack
as
soon
as
we
have
45
minutes
left.
F
Yeah
relatively
there
was
discussion
recently
of
the
maintainer's
calendar
for
for
vacations,
but
I
couldn't
find
a
link
to
that.
B
Hey
did
the
the
issues
with
github
actions
get
resolved.
I
know
there
was
some
instability
last
week
and
I
think
you
had
mentioned
that
you
knew
who
to
reach
out
to
so
there's.
We
had
two
issues
last
week.
B
One
is
that
still
going
on
just
started
on
friday,
the
easy
cla,
and
so
I
was
gonna-
ask
if
anybody
knows
who
to
who,
if
there's
any
specific
contacts
we
can
reach
out
to,
because
I
posted
I
posted
on
friday
to
the
ezcla
channel
on
in
slack,
and
they
did
do
something
they
did
reply
on
friday.
They
thought
they'd
fixed
it
and
it
did
once
the
easy
cla
check
is
no
longer
stuck.
B
It
was
just
stuck
before,
but
now
it's
failing
for
half
of
the
contributors
across
a
bunch
of
repos
have
reported
it
in
open
telemetry.
B
The
other
issue
is
the
queueing
of
github
action
builds
and
for
that
sarah
novotny
and
I
have
reached
out
to
the
github
folks
to
see
if
we
can
increase
the
number
of
concurrent
github
action
runners
we're
currently
at
the
50
concurrent.
So
what
the
free
tier
is
20
concurrent
runners
and
the
open,
telemetry
org,
it's
an
org
wide
limit
is
at
50.,
but
we're
definitely
seeing
at
times
some
large
queue
times
backlogging
and
so
we're
seeing
if
we
can
increase
that
further.
C
Is
this
something
that
we
can
throw
money
at?
Is
that
basically,
what
we're
looking
for
more
time
to
get
donated,
or
is
it
a
more
fundamental
limit.
B
I
don't
know
we're
trying
to
find
out
which
which
of
those
it
is.
I
know
that
there
is
a
tier
above
50
concurrent,
so
it
may
be
a
money
thing.
It
may
be.
You
know
yeah,
okay,
thanks.
B
We
did
get
an
ack
back
from
them
that
they
were
going
to
look
at
it,
but
I
don't
have
anything
more
yet.
C
Okay
for
the
easy,
cla
problem,
if
that's
continuing,
if
there's
a
place
to
post
an
issue
for
that,
if
there
isn't
a
place
on,
I
think
probably
the
place
to
post.
That
is
on,
like
the
cncf
github
organization,.
B
H
B
B
Because
yeah,
it
seems
consistent
with
certain
people,
but
it
works
and
certain
people
that
it
doesn't.