►
From YouTube: 2020-10-21 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
A
A
C
Yeah,
it
is
scary.
I
had
like
a
covet
scare,
a
couple
I
don't
know
like
I'm
probably
a
month
ago
now
it
turned
out
fine
but
yeah.
It's
it's
a
lot
to
go
through
and
even
just
hearing
like
news
of
you
know,
infections
adjacent
to
you
or
like
any
possible
risk
of
contact.
Is
yes
it's
a
lot
to
deal
with.
A
B
A
D
A
D
A
Yeah
then
I
it
also
like
shows
us
the
need
for
like
really
that
really
the
need
for
communicating
effectively,
but
this
isn't
really
for
production,
putting
out
a
alpha
release
and
trying
to
solicit
feedback
trying
to
determine
what
other
parts
of
the
spec
we
need
to
fill
in,
to
be
able
to
get
to
a
place
where
we
can
have
people
effectively
using
it
and
like
using
that
feedback
from
the
the
public
internet
to
be
able
to
drive
development
work.
A
I
think
a
lot
of
development
work
on
this
project
is
stealth,
because
we
don't
really
know
what
people
need,
because
we
don't
have
active
users
like
a
lot
of
the
baseline
functionalities,
is
installed.
They're
they've
changed
the
specs
so
many
times
that
it's
like
getting
to
be
mind-numbing
to
try
and
keep
up
with
it
all,
but
I
think
that
they
are.
The
good
news
is
the
the
open
telemetry
governance
committee
is
going
to
put
a
freeze
on
the
spec.
A
I
believe
it's
in
a
couple
weeks.
They
have
a
couple.
They
like
classified
all
the
issues
that
they
have
for
a
release
freeze,
and
so
once
that
happens,
I
think
we
may
get
a
lot
like
fingers
crossed.
We
may
get
a
lot
more
people
interested
in
contributing
because
it's
not
a
moving
target
anymore.
Yeah.
A
That's
a
good
thing
I
wish
we
could
have
been
keeping
up
with
the
spec.
We
just
don't
have
enough
people
contributing
to
be
able
to
do
that
at
the
current
at
the
current
position.
So
I
think
what
we
have
to
do
is
we
have
to
keep
driving
what
we
can
keep
getting
people
involved
and
interested
in
working
on
the
project
and
garnering
feedback
and
looking
at
new
issues
that
come
in
from
the
feedback
from
people
using
it.
D
I
think
if
we,
if
we
can
get
a
release
out
like
what
you're
saying
right
up
up
front
and
like
tell
them
clearly
here's
you
know
here's
I
can
put
something
in
the
readme
here.
I
open
a
pr
on
the
readme
with
you
know:
here's
our
here's,
our
anticipated
timeline
and
and
and
let
them
know
you
know,
have
a
look
at
the
release
and
and
then
we
need
some
issues
that
are
like
documentation.
A
Yeah,
I
think
it's
pretty
close.
I
think
any
documentation
that
we
do
now.
It's
not
gonna
change
like
super
much
the
so
you
can.
If
you
look
at
the
issues
in
the
open,
celebratory
specification,
repo,
that's
where
they're
doing
a
lot
of
the
mm-hmm
for
lack
of
a
better
work
for
a
lack
of
a
better
phrase.
That's
where
they're
doing
a
lot
of
the
arguing.
Now
it's
like
their
bike,
shutting
pretty
hard
about
some
of
the
last
bit
last
details
which
is
fine
like
this
is
a
long-standing
spec.
A
That's
going
to
be
used
by
theoretically
used
by
billions
of
people,
so
it
should
be
done
the
right
way,
but
I
guess
we
just
need
to
like
once
that
happens.
I
feel
I'll
feel
a
lot
more
confident
in
trying
to
recruit
people
and
trying
to
get
people
more
interested
in
working
on
this
project
because,
like
I
said
there's
it's
people
have
limited
time
to
work
on
this
and,
if
you're
not
like
fully
interested
and
you're
not
being
paid
by
an
employer
to
do
it
like
me,
it
becomes
difficult
to
try
and
hit
a
moving
target.
B
Oh
sorry,
yeah,
I'm
just
going
to
ask
other
than
I
think
the
spec
compliant
matrix.
Is
there
really
a
place
that
specifically
calls
out
the
different
maturity
levels
of
the
different
projects?
B
A
B
Yeah
because
that's
what
I've
been
using
is
that
matrix
just
to
see
what
some
of
the
other
ones
are
are
at,
but
I
assume
for
someone
who's
just
looking
to
see
where
each
project
is
they're,
not
really
looking
at
that
matrix
or
they
might
not
even
really
understand
what
it
is.
Without
reading
a
full
spec.
A
A
A
A
Yeah
changelog.md
in
the
here
you
go
I'll
post
in
the
channel
here
there.
It
is
it's
like
all
the
different
versions
of
the
api.
A
A
We
don't
have
like
an
explicit
timeline
that
we
have
to
release
those
on
and
then
you'd
be
doing.
One
thing
and
then
re-implementing
it
the
way
the
next
version
of
the
spec
goes.
So
I'm
very
happy
to
hear
other
opinions
about
that.
But
that's
like
my
default
opinion
is
like.
Why
would
you
do
that
when
you
could
just
like
follow
the
release
candidates
back.
A
B
B
Yeah
so
yeah
I'm
trying
to
get
it
a
bit
more
wrapped
up,
so
hopefully
within
the
next
week
or
so,
but
we'll
see
but
yeah.
The
the
part
that
I'm
that
I'm
just
on
right
now
is
the
in
the
text
map
format
propagator.
B
I
know
someone
just
asked
about
it
in
the
in
the
channel
and
I
I
replied
in
there
that
the
pr
will
be
up
soon-ish.
So
that's
the
bit
that
I'm
working
on
because
that's
where
a
lot
of
the
validation
happens
for
the
headers
and
then
sending
it
or
propagating
it
along
so
yeah.
Once
I
get
that
wrapped
up
and
then
do
a
bit
more
testing,
then
I'll
put
the
pr
out.
A
Cool,
if
you
want
to,
if
you
want
to
collaborate,
joe
I'm
very
happy
to
like,
take
a
look
at
it
in
its
current
state
or
like
help
you
out,
I
I'm
just
trying
to
I'm
trying
to
enable
you.
However,
I
can't
so
if
it's
working
in
a
silo,
that's
fine!
If
it's
like
asking
questions
or
discussing
your
trade-offs
or
whatever
I'm
very
happy
to
review
it
or
work
with
you
on
it
or
whatever
you
need.
B
B
Okay,
cool
yeah
I'll
work
on
doing
that
in
the
next.
A
couple
of
days.
A
B
I
don't,
but
she
had
a
conflict
for
this
meeting.
There's
another
piece
of
work
she
got
pulled
into,
but
yeah
I
can
ask
her
and
then
maybe
she
can
put
an
update
in
the
test
ticket.
D
B
A
So
I
asked
in
the
channel
if
anybody
had
anything
that
they
wanted
to
say
about
it.
So
I
I
don't
think
so.
I'd
like
to
go
back
over
this,
I
can
do
that
this
week,
I'll
go
back
over
this
deck
and
make
sure
that
we
have
all
the
things
that
are
required
for
that
and
then
I'll
ask
in
the
channel
one
more
time
and
if
not
I'll
just
do
it,
because
I'm
tired
of
waiting
around
for
people
with
the
bike
about
it.
So.
C
Yeah
I'll
have
some
some
free
time
tomorrow,
designated
to
open,
telemetry
stuff
nice.
Is
there
anything
that
doesn't
have
an
assignee
yet
that
could
use
one.
A
A
So
maybe
I
think
any
of
the
I
think
yeah,
anything
that
has
good
first
issue
or
bite-sized
would
probably
be
earlier,
like
maybe
associated
that
spans
with
their
tracer
provider.
Anything
with
the
metrics
api
would
probably
be
nice
to
kyle
because
nobody's
working
on
that
now,
and
that
should
be
pretty
good
green
fields
for
you.
If,
if
you're
interested
in
doing
greenfield
or
if
you're
interested
in
brownfield,
then
associated
spans
with
their
tracer
provider
would
probably
be
good
great
sounds
good.
Thank
you.
Yeah
no
problem.
C
Yeah
tomorrow
I'll
drop
a
message
in
the
getter
or
whatever.
When
I
pick
up
and.
A
D
A
A
D
A
I
sit
so
close
to
the
problem
space
with
our
examples
that
I
don't
know
like
if
the
examples
are
thorough
enough
or
if
there's
other
things
that
people
might
like
to
add
to
the
examples
or
if
we
want
to
come
up
with
like
a
different
kind
of
example,
because
right
now
it's
just
sort
of
like
a
docker
compose
hook
that
just
sort
of
slaps
stuff
together
and
shows
you
that
the
traces
work,
but
I'm
all
ears
for
coming.
A
I'm
all
yours
were
coming
up
with
a
new
idea
for
that,
and
I
need
to
follow
up
with
what's
his
name
d,
carlo
v,
to
see
if
he
I
know
he
was
working
on
implementing
with
this
with
symphony.
But
I
don't
know
where
that
stands
because
he
didn't
make
a
ticket
about
it.
But.
A
We'll
get,
I
think
that
that
will
we'll
get.