►
From YouTube: 2021-02-10 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).
B
A
A
Plants
and
like
your
senses,
like
you
know,
you
naturally
get
like
congestion
and
like
a
slight
cough
because
you're
like
oh,
my
body's,
not
used
to
a
40
degree
delta
in
a
couple
days.
So
then
it
just
sucks,
but
hopefully
we
only
have
a
couple
more
weeks
of
cold,
I'm
a
hot
weather
person.
So
hopefully
we'll
only
have
a
couple
more
weeks
of
cold
and
then
off
the
real
thing.
A
So,
anyway,
all
right,
so
let's
get
we
can
get
rolling.
With
our
conversation,
I
had
a
couple
talking
points
today
and
then
I'll
open
the
floor
up.
The
first
talking
point
is
the
user
research
that
darlabor
did
a
couple
weeks
ago.
The
maintainers
asked
me
to
write
a
blog
post
about
how
that
process
went
so
that
we
can
use
it,
and
so
I
wrote
a
blog
post
and
it
got
accepted
by
the
group
and
they'll
publish
it.
A
I
think
they'll
publish
it
probably
in
a
couple
of
days,
I'll
share
I'll
share
that
with
y'all
here,
just
in
case
you
want
to
see
it.
I
don't
know
if
it's
not
it's
really,
not
even
that.
It's
not
that
important,
but
it's
just
something
that
I
wanted
to
share
that
work
like
open,
telemetry
php
will
have
a
little
bit
of
exposure
there.
So
that's
a
good
thing:
we
have
the
general
availability
for
some
of
the
open
telemetry
things
is
going
to
happen
next
week.
A
They
said
the
15th
is
when
this
the
the
15th
is
when
the
tracing
spec
is
going
to
be
finally
frozen,
which
I
think
that
that's
also
a
good
thing
that
should
give
us
a
little
bit
like.
None
of
us
have
had
the
ability
to
follow,
along
with
all
of
the
implementation
steps
as
the
rest
of
the
sigs
have
gone
through
the
languages
just
because
of
lack
of
time.
A
So
having
a
concrete
spec
will
hopefully
will
help
to
drive
more
people
to
contribute
to
the
project
because
they
won't
be
trying
to
hit
a
moving
target
anymore,
which
is
a
good
thing
in
my
mind,
but
I
wish
we
could
be
a
little
bit
further
along
than
we
are.
But
you
know
here
we
are
the
we're
going.
I
think
that
we'll
be
very
quickly
able
to
fast-track
both
of
y'all
being
approvers
after
you
open
the
issue
for
that
I've
got.
A
A
What
do
they
call
like
your
liaison
or
your
mentor
or
your?
I
don't
know
they
ask
you
to
list
somebody
who
who
will
vet
you
and
I'm
obviously
I'm
happy
to
do
that
and
you
can
list
either
the
other
two
approvers
and
though
I'm
sure
that
they
will
also
be
happy
to
have
that
off
of
their
a
little
bit
of
that
off
their
plate.
A
Yet
so
those
are
the
things
that
I
had
on
my
agenda.
We
have
a
couple
other
prs
that
are
open,
that
I'm
trying
to
push
through
there's
a
thrift
udp
pr,
that's
really
cool.
I
don't
know
if
you
all
have
gotten
to
check
that
out
yet,
but
that's
cool
the
otlp
grpc
pr
has
been
languishing
forever.
I
followed
up
with
the
with
our
old
intern
that
just
never
completed
it
if
he
doesn't
complete
it
soon.
A
We
do
have
another
open
wreck
for
an
intern.
So
if
y'all
know
anybody
who
might
be
interested
the
paid
internship,
those
are
the
things
that
I
have.
A
C
Yeah
that'd
be
great
yeah
yeah
I've.
I
have
a
professor
at
my
old
school
university
that
I
still
keep
in
touch
with,
so
I'm
sure
he'll
be
able
to
find
an
intern
pretty
easily
to
come
in
and
help
out.
If
that's.
A
That
would
be
absolutely
wonderful.
The
problem
we've
had
is
a
lot
of
the
applicants
are
very
under
qualified
to
perform
the
tasks
and
actions
that
are
associated
with
this.
It's
it's
been
a
lot
of
like
international
undergrad
students
that
don't
actually
have
a
grasp
on
programming
yet,
which
is,
I
don't
know
why
this
project
attracts
those
people.
I
think
it's
because
it's
tied
to
the
cncf
and
the
cncf
links
people
to
that.
A
So
I'm
not
sure
why
that
is,
but
if
we
could,
if,
if
you
have
somebody
that
has
even
like
the
faintest
grasp
of
that
program,
it'd
probably
be
much
more
likely
than
some
of
the
candidates
that
we've
received.
So
if
not
this,
and
if
not
for
this
time,
the
next
time
around,
they
do
them
fall
and
spring.
I
think
so
good
to
know.
C
Oh
no,
I
was
just
going
to
ask
about
that
that
customer
issue.
I
know
that
when
we
looked
at
it
briefly,
it
ended
up
being
a
pretty
small
fix
and
I
haven't
really
looked
at
the
ticket
since
did
that
not
work
for
them?
Did
it
end
up
being
something
else
or.
A
Yeah,
so
essentially
what
happened
was
the
I
can't.
I
can't
remember
the
guy's
name,
we'll
just
call
it.
Customer
customer
has
a
double
linked
process
so
like
they
have
a
java
process
that
runs
first
and
that
passes
the
trace
id
and
the
spam
id
to
the
php
process.
That
does
something
else
and
the
php
process
or,
like
you,
can't
close
the
initial
one,
two
three
spans,
because
the
php
process
runs
independently
of
the
java
process
and
I
don't
know
exactly
how
that
works
right
now.
A
I
think
that
the
parent,
like
the
parent
span-
I
don't
know
I
actually
need
to.
I
need
to
do
some
research
on
how
this
works,
because
I
don't
know,
I
think
the
parent
span
is
supposed
to
be
able
to
be
left
open
in
order
to
be
for
the
child
to
be
able
to
talk
to
the
parent
process,
but
I'm
not
exactly
certain
so
I
need
to.
I
think
I
need
to
do
some
more
research
into
that
unless
somebody
else
wants
to,
but.
C
If
it's
going
across
service
boundaries-
and
I
think
that's
where
the
the
trace
context
stuff
comes
in-
because
that
should
be
able
to
maintain
the
the
trace
when
it
crosses
to
a
different
service
boundary
or
when
it
comes
back
yeah.
So.
A
I
think
that's
that's
missing
it.
That
is
my
biggest
fear
is
that
we
have
to
implement
the
trace
context
piece
more
than
we
currently
have
it
implemented,
and
that
might
be
like
the
underpinning
of
why
it
doesn't
work
across
across
product
project
boundaries
or
across
service
boundaries.
A
C
B
Boundaries,
but
the
one
I
think
we
have
implemented
right
now,
that
is
that
I'm
still
working
on
that's
like
almost
finished,
is
the
traits
the.
C
W3C
trace
context,
so
that
has
to
be
kind
of
configured
in
a
way
in
in
the
script,
and
I
I
haven't
looked
at
how
that
might
might
be,
but
once
the
pr
that
I'm
working
on
right
now,
the
the
test
service
once
that
that
is
wrapped
up,
that
should
confirm
the
functionality
of
the
trades
context
stuff.
That's
in
there
is
working
correctly
so.
A
A
If
not,
we
can
make
the
appropriate
fixes,
so
that
doesn't
work.
That
would
be
really
great
exactly
just.
Could
you
just
throw
like
a
one
or
two
line
comment
on
that
ticket
like
hey
we're
working
on
this
we'll?
Let
you
know
when
it's
done,
because
I
think
that
even
just
telling
the
customer
our
customer
here
that
we
have
like
there's
something
in
the
works,
but
we
have
no
eta
for
it,
it's
better
than
just
radio,
silencing
them
for
a
month.
A
C
B
A
But
I
also
don't
want
to
like
try-
and
I
don't
want
to
spend
two
weeks
of
my
life,
trying
to
figure
out
why
their
bespoke
java
and
php
enterprise
inter-service
process
doesn't
work.
The
way
that
we
exactly
expect
we
have
to
develop,
for
we
have
to
develop
for
the
mass,
not
for
the
individual
use
case
right.
C
Yeah
yeah.
No,
I
totally
agree
okay,
I'll
I'll,
try
and
put
in
a
comment
in
there,
probably
tomorrow
or
something
I
have
some
time.
A
B
I
just
wanted
to
close
that
loop
on
that
pr,
I
think,
putting
the
extra
exceptions.
In
I
mean
it
might
be
useful
when
debugging,
but
I
think
for
end
users.
It
might
make
it
a
lot
more
difficult,
and
at
this
point
I
think,
trying
to
work
on
dev
mode
versus
trying
to
work
on
functionality.
I
feel
like
functionality
is
a
higher
priority
than
trying
to
get
dev
mode
working
so.
A
B
Yeah
yeah,
so
I
kind
of
feel
like
that's
where
the
dev
mode
stuff
is
happening
so
yeah,
but
anyway
I'm
just.
I
think
this
one
is
probably
a
lower
priority
at
this
point
and
we
can
like.
I
don't
know
what
flags,
what
tags
are
there,
that
we
can
put
it
like?
Maybe
prototype
or
something
or
just
or
even
a
dev
mode
tag
for
when
we
eventually
get
there
so
that
it
maybe
goes
off
the
radar
but
doesn't
disappear,
and
we
can
go
back
to
it
later.
At
some
point,
I.
A
A
A
B
Totally
muted
thanks
mommy
yeah,
I
was
saying
we
can.
B
I
don't
know
we
can
close
it
if
you
want
or
is
there
like
a,
I
don't
know
something
to
indicate
that
it
doesn't
need
active
reviews
right
now,.
B
A
A
A
C
A
B
B
A
A
It's
true
all
right,
so
these
are
the
here's,
the
jaeger
or
the
udp
and
thrift
pr.
I
was
talking
about
here's,
the
grpc
one
that
I
was
talking
about,
that
riddick
was
working
on
and
then
dollar
board
started
working
on
infection
and
mutation
testing.
But
I
don't
to
be
frank:
I
don't
care
about
that
one
right
now
because
it
doesn't
seem
like
he's
prioritizing
that
and
it's
not
something
like
that's
a
nice
to
have
it's
not
like
a
general
availability
release
requirement
like
some
of
the
other
things
that
we
have
to
do.
A
B
A
C
Yeah,
I'm
working
on
fixing
some
of
the
like
test
failures
that
have
come
up
from
it.
I
don't
have
it
running
like
as
just
a
one
make
command,
because
right
now
you
have
to
have
two
services
running,
so
I
just
I
have
it
like
kind
of
manually.
You
know
spin
the
test
service
up
and
then
in
another
terminal,
spin
up
the
the
application
and
then
have
them
talk
to
each
other,
then
get
the
results.
C
So
I
have
that
working
and
there's
a
few
test
failures
that
I
want
to
fix
first
and
then
I'll
try
to
wrap
it
all
up.
So
it's
just
a
one.
Quick
may
command
type.
A
C
A
Make
it
super
nice
with
that,
because
you
can
have
multiple
things
in
the
back
in
a
background
like
running
in
a
background
or
foreground
process,
and
they
are
able
to
talk
to
each
other
still,
especially
if
you
use
like
docker
compose,
might
be
a
good
example
for
that
the
metrics
and
the
tracing
examples
both
use
docker
compose
to
do
those
kinds
of
things,
and
those
might
be
a
really
good
litmus
test
for
you
to
implement
the
test
service.
D
D
C
I'll
have
a
look
at
that
when
I
get
to
that
point,
but
yeah,
I'm
I'm
basically
80
of
the
way
there
with
this,
so
yeah
I'll
try
to
have
that
pr
for
the
test
service
and
then
a
pr
for
the
fixes
for
whatever
comes
up
from
that
and
then
yeah.
I
think
that
should
be
it
for
the
trace
contact,
stuff.
A
C
A
B
So
I
was
thinking
I
might
just
look
in
the
tracing
project
board
and
see
what
is
still
there.
Since
you
said
the
tracing
spec
it's
anyway
about
going
to
be
done
so
see
if
there's
anything
which.
A
A
B
A
One
caught
exception
in
child
span,
one
kind
of
show
shows
during
the
child
span,
is
not
currently
recorded
as
a
span
error.
No,
I
don't
think
that
that
one's
a
dev
mode.
I
think
that
that's
like
a
real
production
facing
error
mode
right
like
if
you
have,
if
you
have
a
parent
span
and
a
child
span,
and
the
child
span
reports
a
span
error.
A
A
A
Okay,
so
anything
in
the
to
do
columns
like
an
exporter
factory,
this
one,
I
think,
is
done
context.
Interaction
span
context,
which
is
what
family's
working
on
standard
span.
Attributes
might
be
a
really
nice.
One
record
exception
is
what
we
were
just
talking
about.
Default
span
status
is
also
an
important
thing,
and
this
one
also
it
probably
goes
along
with
what
font
I
was
just
talking
about
so.
C
A
C
Yeah
and
then
the
the
spam
context
doesn't
conform
to
the
hotel,
spec
yup
yeah.
I
think
this
one
there's
about
four
or
five
bullet
points
on
there
and
I
think
basically,
the
top.
The
bottom
four
are
all
done.
It's
just
the
top
one
that
needs
to
be
wrapped
up.
Yeah.
A
A
A
Nice
so
amber
d,
so
you
could
work
on
any
of
those.
The
other
thing,
the
other
place.
You
could
certainly
look
to
find
something
cool
to
work
on.
Is
the
user
research
feedback
improvements?
There's
a,
I
think
pretty
much.
All
of
these
are
are
things
that
you
that
might
be
easy,
like
they're,
they
have
less
dependencies.
I
think.