►
From YouTube: 2021-11-11 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
few
minutes,
actually
I
should
go
mentioning
the
channel
that
this
is
going
on.
A
Oh
no
worries
you
can't
stay
long.
I
I
shouldn't
stay
long
either.
So
let
me
just
see
if
anybody
will
join.
A
Yeah,
I
guess
priority
for
me.
Sort
of
right
now
is
finding
seeing
if
anybody's
interested
in
becoming
an
approver,
especially
I
can
trip
yeah
and
then
try
to.
I
think
isaac
is
interested.
C
A
Yeah,
it
was
someone
else
who,
I
think
is
kind
of
dropped
off
yeah.
He
did
the
moving
the
examples
to
the
contributory
bow
which
needs
to
get.
I
thought
I
can
open.
Yeah
yeah
like
yeah
it'd,
be
nice
if
greg
had
more
time
because
he
would
be
a
good
fit
for
here
for
reviewing
stuff.
But
I
don't
know
that
might
happen
sometime
in
the
future,
but
right
now
not.
C
For
a
project,
so
we
have
approvers
on
the
like
on
those
the
different
project
yeah
like
in
the
file
base.
So
it's
the
getting
them
end
part.
C
C
I
think
in
that
case
it's
sometimes
it's
a
combination
right
of
they
don't
know
about
it
or
they
just
breeze
through
it,
because
it
is
like
they're
saying
like
everybody's
trying
to
like
get
stuff
done,
which
is
cool,
but
it's
like
for
it
to
be
out.
There
is
like
an
official
thing.
It
means
it
does
need
to
be
correct.
A
A
C
A
If
they're
not
specific
to
erlang,
though
those
should
be
upstreamed
because
but
there's
other
rabbit,.
C
C
On
new
ones-
and
that's
just
been
like
finding
finding
several
hours
to
do
that
and
unfortunately,
for
I
guess
indrik
that
created
the
obon
one
like
he
created
it
during
the
time
period
too,
where
all
of
the
control
priorities
were
on
getting
phoenix
and
ecto
blocked
to
the
rc
versions
and
I've
kind
of
been
in
the
mindset
of
like.
I
don't
really
want
to
do
anything
until
we
hit
ga.
C
A
C
A
Yep
so
yeah
I
can
talk,
I
can
dm
people
and
look
for
help
on
contrib
reviews
and
they.
C
A
A
A
C
A
C
C
C
But
that's
the
thing
for
me
like
if
there's
anybody
that
we
can
just
like
end
up
even
trusting
to
say,
like
you'll
review
it
the
initial
project
pr
and
make
sure
that
it
doesn't
look
terrible
that
it
matches
the
semantic
conventions
like
it's
really
fast
for
me
to
go
in
and
check
the
ci
setup
yeah
and
the
other
bits
like.
That's
really
fast.
C
A
Yeah
the
thing
I'm
yeah
on
doc's
trying
to
work
out
next
is
the
because
this
has
come
up
multiple
times,
but
that's
partner.
Well
now
this
eric
person
is
brought
up
as
recently,
but
it's
come
up
from
other
people
as
well
the
differences
in
context.
You
have
context,
and
you
have
spanking
context
yeah
and
my
difficulty
is.
A
You
want
the
docs
to
have
a
quick,
getting
started
like
you
want
to
be
users
to
be
able
to
they
go
to
the
docs
and
they
can
start
seeing
how
and
even
creating
spams
themselves
right
away,
but
you
don't
want.
But
if
you
move
that
stuff,
if
you
move
the
stuff
that
I
need
to
add
about
context
and
spam
context
to
just
some
somewhere
else,
then
they'll
just
not
read
it
and
the
same
questions
will
come
up.
A
But
you
also,
but
I
don't
want
to
like
start
off
with
terminology
all
like
boring
and
stuff,
that
they'll
just
get
upset
that
they
don't
know
how
to
start
a
span
until
they
have
to
read
all
this.
C
Could
it
be,
like
example,
based
of
just
like
examples
of
propagating
context,
because
it's
all
I
think
most
of
it's
around
I
mean
like
the
websocket
stuff-
is
like
a
whole
other
thing,
but
yeah,
I
don't
even
know
what's
going
on
there,
but
I
think
it's
mostly
for
most
people.
It's
probably
going
to
be
around
like
propagating
context
across
processes
and
non-http
clients,
server,
headers,
stuff,
yeah
like
how
do
you
propagate
it
across
kafka?
How
do
you
propagate
it
on
rabbit.
C
A
Of
the
contact
stuff,
probably
people
just
don't
know
what
a
context
is,
and
they
are
interchanging
spam
context
and
context,
and
that
blows
everything
up
and
they
don't
unders
rightly
understand
why
so
starting
off
the.
A
No
because
I
mean
ultimately,
it
should
be
available
for
anything,
not
just
spans
and
baggage.
It
should
be
just
just
like
in
go.
A
Might
start
trying
to
kind
of
piggyback
it
could
end
up
being
its
own
library
if
others
ever
start
using
it.
So
I'm
just
not.
I
guess
I'm
asking
in
the
context.
I
guess
no
telemetry,
though
you
know
so
yeah
sticking
only
in
the
context
of
open
telemetry.
Even
it's
not
completely
private,
because
people
do
need
to
take
it
and
hand
it
off
like
in
the
cross
process.
Exam.
B
C
C
Oh,
the
worst
was
there
was
a
library
for
for
open
api
stuff
and
basically
the
this
for
the
validation
stuff.
This
the
spec
got
generated
and
put
onto
the
con,
so
it
went
from
like
75
kilobytes
or
something
to
like
four
mags
or
something
I'm
like
you
know.