►
From YouTube: 2020-11-24 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
C
D
C
C
C
C
Currently
there
is
no
good
way
for
us
to
put
vacation
plan
in
the
public
group.
I
know
there's
an
open
times,
maintainers
calendar
here.
You
can
see
like
folks
like
morgan
from
the
the
technical
committee
and
tyler
from
the
javascript,
so
they're
they're
putting
the
vacation
I'm
going
to
put
my
application
here
as
well,
but
just
for
your
information
I'll
be
gone
for
the
entire
december
and
I
think
for
folks
who
are
actively
joining
this.
E
Really
I'll
be
around
I'll,
probably
be
away
from
the
summer
like
for
one
month
and
maybe
in
april,
but
until
then
I'll
be
wrong.
All
right!
Sorry
max!
Would
you
repeat
sorry,
I
think
maybe
my
mic
is
not
good.
I
was
saying
that
I'll
definitely
be
around.
I
made
the
way
in
april
and
I
did
plan
to
be
away
for
one
month
next
summer,
but
until
then
I'll
be
around.
I
can
help
with
reviews.
F
E
F
E
Maybe
a
lolita
or
josh
somebody
who
can
be
your
backup.
C
Yeah,
ideally
I
want.
I
want
to
find
someone
who's
familiar
with
a
c
plus
class
and
also
have
been
around
for
a
while
and
also
like,
be
committed
to
like
do
the
maintenance
job
and
there's
no
there's
no
such
process
of
a
short-term,
like
maintainer
replacement
or
like
on
behalf
of
probably
need
to
nominate
a
maintainer,
and
I
think
previously
we
were
in
this
situation,
where
we
can
take
exception,
because
this
thing
is
relatively
small.
C
C
Because
I
I
plan
to
put
his
100
time
this
project
and
also
I
got
verbal
agreement
from
him
josh
I
haven't
heard,
but
I
I
remember
lily
to
mention
to
me
that
that
he
reached
out
to
josh
and
josh
expressed
a
strong
interest
in
spending
more
energy
here,
so
just
need
to
so
as
a
follow-up,
I'll
I'll
reach
out
to
them.
C
D
Few
weeks
is
just
to
get
the
two
processor
pr's
in
and
the
ostrim
explorer,
and
so
that's
like
three
pr's
that
need
to
be
sort
of
reviewed
and
looked
for
merging
and
the
elasticsearch
exporter.
We're
currently
thinking
as
a
stretch
goal,
because
we
have
like
probably
like
a
two
week
expected
like
you
know,
merge
turnaround
time.
D
So
we're
not
sure
if
that'll
be
done
by
the
end
of
our
like
before
our
internship,
so
yeah,
the
simple
processor
pr
I
was
thinking
of
discussing
with
you
guys
offline
during
tomorrow's
meeting
first
before
filing
and
since
it's
before
thanksgiving
I'm
thinking
of
filing
it
before,
like
you
know
the
wednesday
thursday
friday
everyone's
kind
of
off
and
then
hopefully
have
it
merged
by
next
week.
If
there
are
any
like
significant
changes,
then
like
I'll,
like
fix
the
batch
processor
apr
before
vring.
D
Otherwise
I
think,
like
the
batch
processor,
can
just
be
pr
like
immediately
after
the
expected
length
of
both
is
like
500
to
600
lines,
the
o
stream
exporter.
Probably
isn't
it's
less
than
that?
I
think.
C
C
Yeah
and
for
for,
like
I'm,
not
sure
like
if,
if
you
could
work
with
alolita,
to
find
some
like,
like
full-time
employee
from
aws,
to
join
the
sig
and
how
to
review
some
prs
in
the
public
report.
I
know
they
have
been
doing
that
in
like
in
the
fork
like
if
they
have
a
they
have
an
interest
in
spending
more
time
here
and
make
contributions
to
become
a
tour
or
maintainer.
I'm
I'm
happy
to
give
my
best
support
to
them.
D
C
C
C
Okay,
so
so
we
can
go
to
the
next
topic,
I
think
so
for
the
login
prototype.
I
I
think
we
have
the
like
google
krs
merged
and-
and
I
haven't
seen
another
pr-
is
that
coming
or
it's
already
there
I
just
ignored
it.
D
It's
coming
hopefully
by
tomorrow
after
our
offline
meeting
or
I
can
bring
you
a
link
just
as
a
preview
before
then
too,.
B
D
B
Sure,
yes,
I'm
also
going
through
the
api
and
sdk
that
have
already
been
merged
and
making
some
changes
to
them
like
we
discussed
how
we
want
the
log
record
to
be
on
this
on
the
heap.
Instead
of
the
stack
and
max
the
issue
filed
upstream
to
the
specifications
to
have
the
the
logger
name
inside
the
the
log
data
model,
I
saw
they
actually
approved
that
so
I'm
adding
that
to
the
log
record
too,
as
well
as
like
some
minimum
severity
things
and
other
functions.
B
Yes,
they
did.
I
can
ping
the
link.
E
It
as
long
as
it
is
there
any
exporter
like
no,
no,
no,
no
jlp
exporter
can
use
a
different
name
right.
It
only
matters
for
the
actual
oclp
protocol
stack,
however
it,
and
why
yeah
it's
like
yeah
for
some
existing
systems,
which
may
already
have
a
good
definition
for
that
it
will
be
the
job
of
the
exporter
code.
Turning
up
that
actually.
A
C
B
Yep,
but
he
left
the
message
saying
he
has
it
imported,
but
it's
just
failing,
so
I
hope
it's
going
to
be
working
pretty
soon.
Okay,
because
I
offered
karen
a
nice
elastic
search
exporter
for
the
logs,
the
json
library
that
we're
using
it
only
compiles
using
bazel
or
it
only
builds
using
bazel
and
the
hddp
client.
It
only
builds
using
cmake
right
now,
so
we
can't
get
it
to
work
because
neither
of
the
components
build
using
the
same
tool.
B
E
Yeah
yeah,
I
can
I
can
handle
this
because
if
you
guys
are
blocked
on
this,
do
this
for
brazil
only
tag
me,
and
I
will
add
it
because
johannes
told
me
that
he
also
needs
it
for
something
else
like
for
w3c
tests.
We
need
to
add
it
anyways.
I
will
handle
that
better.
E
I
also
haven't
take
that
to
do
the
same
for
z,
pages
module
because
z
pages
we're
now
building
with
bazel
testing
it
with
bazel,
and
it
does
fetch
the
enlowman
library
through
the
bazel,
but
we
we
need
to
properly
do
it
like.
Once
we
merge
my
build
tools.
Pr,
I
already
already
reserved
a
place
where
I'm
going
to
be
placing
this
library
for
the
ceiling.
C
D
I
filed
an
issue
of
this
morning
about
the
trace's
implementation
of
the
span,
processors,
force,
flush
and
shutdown
methods.
So,
like
we
discussed
sort
of
offline,
it
doesn't
currently
follow
the
spec
exactly
like,
for
example,
it
doesn't
return
the
status
of
the
fourth
question.
Shutdown
like
it
should
so
I'm
proposing
for
traces
first
that
they
should
implement
that
and
also
to
be
able
to
abort
the
fourth
question
shutdown
to
ensure
it
doesn't
like
hang
forever
and
for
the
coming
logging
processor.
D
Pr
I'm
going
to
be
implementing
these
all
of
these,
except
for
the
ability
to
abort
if
the
timeout
is
exceeded,
because
I
think
there
might
be
some
threading
involved
for
that
that
I'm
not
super
confident
in
implementing.
D
C
I
see
yeah
makes
sense
as
a
first
step,
so
just
to
confirm,
are
you
going
to
change
the
tracing
part
or
you
will
just
fork
and
do
the
login
part
only.
D
For
tomorrow's
pr,
it's
just
going
to
be
the
log
processor.
I
won't
be
changing
traces.
C
C
C
F
C
Okay,
then
we
go
to
the
next
topic,
so
tom
you
asked
about
the
release
schedule,
so
there
is
no
strict
release
schedule,
but
we
target
to
get
a
test
release
just
to
go
through
the
process
and
lightly
just
had
the
first
pr
merged.
So
we
expect
him
to
work
on
the
subsequent
prs,
just
to
clarify
some
of
the
process
and
tagging
and
the
versioning
story,
and-
and
so
I
I
think,
still
the
target
release
would
be
unknown
this
year.
C
F
F
C
So
I
I
think
your
next
question
is
like
one
two,
four
comma
master,
so
I
might
be
a
little
bit
confused.
So
I
I
I
think
the
current
way
I
would
imagine
is
when
we
do
the
release.
We
tag
the
branch,
so
the
master
or
like
we're
going
to
change
that
to
the
membrane
just
for
like
political
correctness,
and
I
I
think
for
that
man
branch
it'll
have
a
tag
which
is
saying
test
to
release
something
and
after
that
we
continue
work
on
the
membranes.
C
C
C
F
C
So
so
normally
we
only
have
a
major
version
when
we
roll
forward.
For
example,
people
use
one
point
like
1.2
and
we
notice
there's
a
major
bug
in
1.2
will
release
1.2.1
and
ask
people
to
move
to
that
version.
F
C
Okay,
so
the
the
problem
you
mentioned
will
happen
when
we
have
multiple
major
versions
out
as
the
lts
like
the
long
term
support.
For
example,
we
have
one
point
x
version
and
we
have
two
point
by
version
and
and
both
are
long-term
support-
that
that's
not
an
issue
today,
and
this
is
something
we
have
to
clarify
in
the
stack
six
and
also
with
the
maintainers.
C
F
C
And
your
you
have
a
question
like
before
the
fork:
do
we
have
any
restriction
to
merge
new
prs,
so
we
can
practice
that.
Let
me
see
if
we
have
the
wording
in
open
time,
3c
plus.
C
So
we
don't
have
that,
as
I
can
see
in
open
time,
if
you
don't
know
that
we
have
something
we
can
probably
borrow.
C
So
we're
saying
a
pr
merge
might
like
a
pr
might
not
be
merged
immediately.
If
the
repo
is
in
the
process
of
a
major
release,
okay,
I
see
there
will
be
a
lockdown
bar
and
we
can
probably
because
this
is
only
when
we
start
to
do
the
release,
and
here
we're
not
ready.
We
can
probably
borrow
some
words
from
other
like
products
that
are
in
a
better
situation
than
than
c
passed
us
today.
C
F
F
C
E
Don't
merge
it.
I
got
the
approvals.
I
will
clean
up
all
the
minor
things
like
there
are
non-essential
cleanups,
which
I
already
fixed
the
formatting
issue.
By
the
way
I
just
want
to
get
all
the
the
concerts
addressed.
I
agree
with
all
of
them.
I
got
a
conditional
approval,
I'll
reach
out
to
you
riley
when
I
clean
it
up,
hopefully
I'll
handle
it
to
there
tomorrow.
Then
you
conversion,
okay,
okay,.
E
I'll
I'll
tag
it
there
are
some
good
comments
from
johannes
a
few
from
tom
about
the
the
proper
system
directory
like
buff
I'll,
get
that
cleaned
and
I'll
notify.
You
rightly
when
it's
done.
E
Mostly
yes,
rebase
and
once
I'm
image
the
built-ins,
this
one's
going
to
be
twice:
small,
okay,
cool
yeah
and
I
removed
a
few
other
things
which
were
non-essential
to
this
sgd
conversion.
Like
I
had
other
patches,
I
reverted
all
of
them
to
make
sure
that
it
looks
in
alignment
with
which
is
approved
by
spec
I'll,
send
other
things
like,
I
believe,
we're
still
missing
a
few
features
which
might
be
relevant
later
on,
but
we
need
to
get
the
spec
work
done.
E
C
C
E
Need
to
work
with
michelle
he's
done
some
work
on
his
internal
branch,
the
basically
right
now
it's
a
fuller
implementation
of
the
sdk.
It's
a
w
thruster!
That
is
not
a
cw
exporter,
but
it's
like
some
sustain.
It's
a
w
tracer
we're
going
to
make
it
work
as
the
proper
structure,
with
the
expert
method
as
an
ecwu
exporter
and
the
same
way
as
other
exporter
subscriptions.
E
C
I
see
so
I
can
show
you
the
the
python.
C
Trip
so
in
in
python
there
is
separate
group
for
contrib,
approvers
and
maintainers
in
different
parts.
So
so
do
you
work
with
like,
I
believe,
the
way
how
you
create
how
you
create
that
contributor.
Is
you
file
an
issue
in
a
community
issue
list
right,
so
ask
people
to
give
like
you
drive
the
initial
list,
who's
going
to
be
the
maintainer
and
who's
going
to
be
the
approver.
E
Yeah
I'll
ping
him
in
person
see
if
he's
gonna,
be
willing
to
be
there,
and
I
do
have
a
few
things
like
drafts,
which
I
wanted
to
share
in
that
other
repo.
For
example,
projections
like
vlog
for
cxx.