►
From YouTube: 2020-11-18 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
A
They
live
in
kenya,
oh
that's
where
that
that
is
far
yeah,
that's
where
I'm
from,
but
we
usually
do
something
around
the
holidays,
but
this
year
it's
a
bit
different.
Obviously,.
C
Yes,
slightly
different,
I
didn't
realize
that
you
were
from
kenya.
How
long
have
you
lived
in
the
united
states.
C
C
A
C
A
C
I
got
rid
of
I
got
rid
of
my
my
northeastern
used
guys
pretty
quickly.
A
I
think,
as
far
as
our
star
team,
it's
only
today,
I
think
amber-
has
the
doctor's
appointment
or
something
okay,
no
pros.
C
I
think
we,
I
think
we
can
be
kind
of
brief
today,
because
I
know
some
people
are
at
kubecon
and
I'm
planning
on
attending
I'm
attending.
So
I'm
planning
on
going
to
the
conference
talk,
but
I
think
your
pr
is
ready
to
merge.
I
don't
think,
there's
any
blockers
now,
I'm
happy
to
merge
it
whenever
you
want
me
to.
A
C
Cool
I'm
merging
yours
as
we
speak,
just
so
that
I
don't
forget,
because
I
will
and
then
it'll
be
like
friday
and
I'll
be
oh
yeah.
I
meant
to
do
that
all
right,
so
that's
merged
to
master,
which
we
have
to
change
that
to
main
eventually,
but
they
open,
telemetry
people
said
to
wait
until
github
has
that
automatic.
So
I
don't
think
that
that's
a
huge
I
haven't
heard
any
huge
complaints
about
that
yet,
but
I'm
planning
on
doing
that
one
that's
possible!
A
Yeah
yeah,
so
the
other
half
trace
state
headers
bit,
because
I
think
right
now,
all
that
we
do
is
is
the
following.
We
have
in
there
is
just
to
add
to
the
trace
date
headers
to
an
array
in
the
span
context,
but
I
think
we
yeah
I'm
adding
like
the
ability
to
you
know
actually
take
those
out
and
put
in
what
you
want
so
give
whoever's
using
it
a
bit
more
control,
because
that's.
A
Specific
piece
here-
that's
that's
more
important
to
the
folks,
rather
than
that
trace
parent,
which
is
just
the
actual
propagation
bit.
C
A
Yeah
it's
funny
because
we
did
this
work
for
our
agent
and
our
agents
written
in
c,
but
it's
it's
a
php
extension
and
it's
completely
different.
The
way
that
we
did
it.
The
way
that
it's
done
here,
which
is
yeah,
which
was
interesting.
It
was
cool.
C
C
Yeah
I
saw
when,
when
you
had
that
yoda
style
syntax,
I
was
like
yep,
he
wrote
this.
Is
he
wrote
something
similar
to
this
and
seen
before.
C
Same
yeah,
I
started
as
a
c
programmer
too,
so
I
I
feel
you're
straight.
I
haven't
done
it
in
probably
a
decade,
so
you
probably
have
it
more
recently
than
I
do,
but
anyway,
okay
cool,
so
that's
good
riddick's
pr
with
the
generation
of
the
protobufs
for
php
is
in
which
I'm
really
excited
about
that.
We'll
have
those,
and
so
I
think
his
next
step
will
be
to
start
sending
traces
using
the
pro
using
the
protobuf
method
for
the
otlp
export.
C
I
guess
we
probably
eventually
have
to
do
that
for
a
zip
code
and
yeager
too,
but
I
think
that
the
otop
bit
is
probably
the
easiest
and
probable
that
we'll
do
first,
I
am.
I
did
some
validation
for
php8
support.
We
have
to
we'll
have
to
update
some
libraries
and
make
some
changes
the
php
8
take.
The
actual
release
is
on
the
27th,
so
I
figured
that's
when
I
will
be
able
to
like.
C
I
don't
want
to
do
pre-release
stuff
right
before
the
release,
because
I'm
sure
that,
like
a
lot
of
these
libraries,
will
change
shenanigans
around
really
quickly
right
at
the
end.
So
I'll
probably
pick
that
back
up
on
the
after
phva
it's
released,
I
think,
let's
see
what
else.
Oh
dog,
foodie
and
user
research
is
something
that
we're
I'm
looking
through
the
issues
as
we're
talking
now,
dog,
fooding
user
research
is
something
that
we
need
to
figure
out
how
to
do.
C
But
I
don't
know
if
I
don't
know
who's
going
to
be
the
right
person
to
do
that.
I
think
that's
going
to
be
somebody
that
doesn't
work
on
the
project
right
now.
The
idea
behind
that
ticket
number
206
is
to
get
somebody
that
is
familiar
with
php,
but
not
with
open
telemetry
php
to
implement
the
the
implement
the
open,
telemetry
php
client
in
something
that
they
have
and
give
feedback
based
on
the
implementation
strategy.
C
If
anybody
has
any
ideas
of
people
that
people
are
projects
that
might
be
interested
in
that
I'll,
probably
post
again
about
that
in
the
open,
telemetry
php
channel,
see
if
I
can
get
anybody
to
give
some
feedback,
I
know
dar
labora
was
doing
so.
Maybe
he
can
give
us
that
feedback
if
he
has
it
so
that'll
be
nice.
C
C
C
I
guess
I
understand
it
because
it's
a
huge
spec,
that's
going
to
be
living
forever,
but
we've.
You
know,
there's
probably
some
things
that
we'll
have
to
go
back
and
change,
but
that's
on
my
list
of
things
to
do
too.
C
So
I
think
that
that
that
covers
pretty
much
everything
the
mutation
testing
I
think,
what's
his
name,
onyoumom
is
working
on
and
then
I
think
that
covers
all
the
issues
that
we
have
open
right
now:
amber's
pr
got
merged
so
that
one's
that
associated
spans
with
tracer
provider
yeah.
So
I
think
that
we're
we're
like
on
track
to
cover
all
of
these
issues
at
least
somewhat
soon,
but
so
that
means
I
probably
need
to
go
back
and
make
some
more
based
on
the
knowledge
that
I
have.
A
Cool
yeah,
I
think
the
next
thing
I'm
going
to
work
on
is
trying
to
integrate
that
test
service
for
the
w3c
triggers
actually
like.
A
Yeah
because
that's
a
bit
different
from
the
issue,
what
we
have
in
there
for
the
fb3.
A
Cool
cool
and
I
think
I
think
for
that
one.
I
wonder
if
we
should
make
it
something
that
runs
in
the
ci
or
just
something:
that's
there
where
you,
let's
see
like
the
just
run,
a
make
command
and
it
does
it.
But
it's
a
local
type
of
thing,
because
I
it's
one
of
those
things
where
no
one's
really
going
to
be
doing
a
lot
of
work,
then
it
will
break
the
trace
context
propagation.
C
I
think
yeah,
at
least
from
my
experience,
what
we've
done
so
far.
That's
actually
seemed
to
work
out
pretty
well.
Is
we
come
up
with
the
make
definition
first
and
then
we
add
it
to
the
ci
when
we
feel
like
something's,
going
to
actually
break.
If
you
make
a
change
to
code-
and
you
know
whatever,
but
I'm
you
know,
I'm
open,
I
don't
really.
It
doesn't
bother
me
if
you
wanted
to
add
that
test
into
ci.
C
Just
know
that
that
oh,
no
probably
if
it's
got
a
separate
service
and
it
has
to
do
a
bunch
of
validation,
checks
or
whatever
that
might
just
be
more
annoying,
not
annoying,
but
it'll
take
longer
for
the
ci.
So
maybe
we
can,
I
think,
having
a
make
file
that
handles.
That
would
probably
be
sufficient
for
now
we
could
and
then
we
can
add
it
to
github
actions
later
when
we
deem
that
it's
it's
something
that
could
potentially
cause
huge
problems.
A
Yeah
no,
I
agree
yeah
because
it's
one
of
those
things
where
it
just
has
a
bunch
of
stuff
to
do
to
spin
it
up
and
then
actual
running
of
the
test
is
really
quick,
but
that's
annoying
to
do
every
time
tr
has
put
up
so
yeah,
okay
I'll
just
make
it
like
a
manual
runnable
thing
first,
and
then
we
can
decide
later
on
yeah.
That's
a
good
plan
works
for
me.