►
From YouTube: 2021-01-06 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
But
we're
we're
excited,
I'm
just
excited
to
not
get
junk
mail
anymore,
the
junk
mail
for
this
election.
I
was
thinking
about
just
cat
like
stacking
it
all
and
seeing
if
it
touched
the
ceiling
from
the
floor,
but
it
is
it's
been.
A
B
A
Up
we
had
to
do
a
bunch
of
like
data
store
creation
for
mailchimp
because,
like
we've
had
a
ton
of
influx
of
new
traffic,
I'm
like
this
is.
This
is
not
the
way
that
I
wanted
to
come
back
to
vacation.
It's
like
dealing
with
my
sequel
replication,
all
over
the
place,
I'm
like
no.
This
is
not
what
I
want
to
be
focused
on
right
now,.
D
D
We
came
back
and
slack
was
down
for
at
least
the
first
couple
of
hours,
which
I
didn't
realize.
How
great
that
would
be.
I
mean
seriously
back
from
vacation.
Slack
should
be
down
for
a
couple
hours,
but
I'm
glad
I
didn't
work
for
slack,
because
I'm
sure
that
you
know
they
were
completely
losing
their
minds
with
all
the
people
coming
back
and
everybody
wants
to
download
all
the
dms
that
they
haven't
been
keeping
up
with,
while.
A
I
had
to
implement
a
no
slack
day
during
my
work
week
and
it's
been
really
really
helpful.
I
just
tell
everybody
hey.
If
you
need
me
call
me,
nobody
calls
you
and
it's
nice
to
just
not
have.
I
have
an
influx
of
stuff
coming
like
coming
in
an
ad
hoc.
A
A
All
right,
I
think
we
have
everybody
that
I
expect
to
be
here
today,
so
how's
everybody
doing
we
got
anybody
have
anything
that
they
specifically
want
to
add
to
the
agenda
today
before
we
get
rolling.
A
No
news
good
news,
all
right,
so
I
pull
up
the
agenda
all
right.
So
this
the
semantic
versioning
document
that
I
created
is
still
waiting
on
somebody
to
review,
I'm
going
to
ping
the
other
reviewers
and
if
amber
and
fami,
if
you
all
still
want
to
be
your
viewers,
I
think
I'm
going
to
just
put
in
a
petition
to
let
you
all
do
it.
A
Even
though
you
haven't
met
the
criteria
because
nobody's
responding
to
anything,
and
it
would
be
nice
to
have
a
couple
more,
and
I
think
that
when
I
was
in
the
maintainers
me
on
monday,
everybody
was
concerned
about
php,
because
we
just
don't
have
enough
momentum
right
now.
So
I
will
I'm
going
to
try
and
put
in
a
petition
for
both
y'all
to
get
at
least
approve
her
access,
so
that
would
that
way
we
can
like
sorta.
I
can't
I've
mentioned
it
before.
A
I
can't
even
do
pr's
now,
because
I
don't
have
anybody
who
can
approve
them
for
me,
wow
in
like
a
reasonable
amount
of
time,
so
that
I
will
I'm
going
to
see
what
I
can
do
to
make
to
get
you
all
in
that.
Even
though
I'll
just
budget
and
say
that
you
all
did
10
10
pr's
and
if
something
comes
back
on
me,
that's
fine,
but
we
just
need
to
build
some
momentum.
A
I
think
so
that's
so
that
semantic
versioning
thing
was
very
I've,
thought
a
lot
about
it
and
talked
with
some
of
the
other
maintainers
about
it,
and
it's
just
like
a
really
you
know
using
cement.
Essentially
it's
just
using
semantic
version
to
make
sure
that
we
can
release
the
right
versions
at
the
right
time.
So
I
think
I
don't
know
if
y'all
have
seen
that
or
not.
If
you
haven't
I'm
happy
to
share
I'm
happy
to
share
it.
Let
me.
A
A
A
B
B
A
A
A
B
A
A
So
it
sounds
like
you
got
some
stuff
to
work
to
keep
clacking
through
five
year,
w3c
stuff
coming
along
all
right.
C
C
So
after
the
pr
today
that
I
put
up,
that's
going
to
be
like
the
core,
like
implementation
with
the
trace
grand
trace
state,
and
then
I
have
two
more
prs
to
put
up
one
with
the
test
service
stuff
and
then
another
pr
with
just
cleaning
up
of
edge
cases
that
come
up
from
that.
C
So
after
that,
I
think
it
should
be
pretty
much
done.
I
do
have
one
question,
though:
do
we
have
any
like
logging
implemented
or
are
we?
Is
it
something
that's
going
to
be
done
down
the
road.
A
So
the
logging
specification
is
like
it's
still
slightly
influx.
It's
not
completed
yet,
and
I
I
think
we
decided
to
de-prioritize
the
logging
bit
of
open
telemetry
right
now.
We
wanted
to
focus
on
getting
tracing
up,
to
really
like
a
sort
of
a
release,
candidate
and
and
then
start
working
on
metrics
a
little
bit.
But
if
you,
if
logging,
is
something
that
you're
interested
in
working
on,
I'm
not
going
to
stop
you.
C
Yeah,
I'm
just
wondering
because
for
the
at
least
the
trace
state
bit
like
when
you
can't
parse
a
transparent
header,
you
know,
then
the
trace
is
broken
and
there's
nothing.
You
can
do
so.
You
just
you
know,
put
a
an
exception
up,
but
for
the
trace
state.
If
you
can't
parse
it
then
and
you've
still
parsed
the
trace
parent.
Then
it
shouldn't
you
shouldn't
like
throw
an
exception.
It's
basically
like
okay.
C
We
can't
parse
the
trace
date,
which
is
the
vendor
specific
stuff,
just
keep
moving
on,
but
right
now,
there's
really
no
way
for
me
to
put
that
that
the
tray
state
wasn't
parsed
other
than
you
know
some
some
logging
bit.
So
I
just
put
some
to
do's
in
there
for
now
and
then,
whenever
we
get
to
that
point,
we
can
clean
that
up.
But
at
least
for
now
there's
no
way
of
like
when
they're
using
it
once
it's
done,
that
the
trace
state
header
can't
be
parsed.
C
A
Yeah
I
so
I
am
conflicted
here.
My
my
two,
like
my
two
slices
of
advice
here,
would
be
either
leave
it
as
to
do
that's
fine
or
the
other
thing
we
could
do
is
we
could
just
use
like
a
very
simple
monologue
to
log
those
things
for
now.
Until
we
have
the
traced,
like
the
like,
open,
telemetry,
php
logging
implementation
done,
I'm
completely
fine
with
either.
I
actually
think
putting
in
monologue
as
like
a
simple
logger
might
be
like
a
pretty
good
start
to
thinking
about
how
we're
going
to
handle
the
logging
specification.
C
Okay,
I
might,
I
might
just
leave
it
as
to
do
for
now
and
then
after.
A
A
A
You
know
it
is
sort
of
like
how
we're
like
the
permeate
like
the
prometheus
library
for
metrics.
Is
we
just
sort
of
like
bake
that
in
and
like
wrap
the
syntactic
sugar
that
we
needed
around
it
tracing
is
its
own
special,
crazy,
beast
and
that's
why
it
has
its
own
special,
crazy
implementation,
but
the
other
two
are
just
like
sort
of
well.
I
guess
we're
still
wrapping
jaeger
and
zipkin
around
tracing
so
like
it's
sort
of
like
that
same,
you
need
to
add
some
fancy
stuff,
but
really
under
the
hood.
D
A
A
All
right-
and
I
so
I
this
week,
I'm
going
to
take
on
reviewing
family's
pr
and
amber's
when
it's
done.
I'm
going
to
start
trying
to
dig
into
some
of
the
ben
benjamin
told
me
that
he
is
working
on
truing
up
the
metric
or
the
tracing
the
tracing
spec
versus
what
we
currently
have
in
our
tracing
library,
and
so
that
we
can
sort
of
make
tickets
and
work
on
changing
the
last
bits
and
pieces
to
try
and
match
the
the
general
availability
spec
for
php.
A
I
think
that
that
will
be
a
decent
amount
of
work,
but
I
think
that
we
need
to
I'll
need
to
spend
some
time
this
week,
truing
that
up
and
making
sure
that
we
have
the
right.
You
know
the
right
path
to
go
from
our
current
state,
which
is
good,
but
just
doesn't
have
everything
that
the
stack
has
in
it
too.
A
D
A
Maintainer
in
the
open,
telemetry
php
community,
which
is
levi
and
benamen
and
I'll
I'm
planning
on
paying
them
later
today.
I've
just
been.
I
didn't
want
to
bug
anybody
over
the
holiday,
because
I
know
a
lot
of
people
were
taking
time
off
levi
actually
got
covered.
He
told
me
when
he
was
out
for
a
month-
oh
god
yeah.
So
I
think
that
you
know
everybody's
had
a
scare
or
two
now
I
guess.