►
From YouTube: 2020-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
A
A
I'm
on
cloud
nine
because
I
had
monday
and
tuesday,
monday
and
tuesday
off.
That's
why
yeah
yeah
my
my
wife,
my
wife,
gave
me
my
christmas
present
seven
weeks
early,
which
I
was
very
excited
about.
She
got
me
a
smoker
for
outside,
like
a
grill,
smoker
yeah,
because
she
wants
me
to
smoke
a
turkey
for
christmas
or
for
thanksgiving
so
she's
like
I'm.
Getting
you
this
early
for
good
reason
and
I
have
been
smoking
up
a
storm.
A
B
B
A
Okay,
so
I
think
this
is
the
quorum
that
I'm
expecting
today,
so
we
can,
I
guess
we
can
get
rolling.
So
does
anybody
have
any
updates?
I'm
trying
a
different
format
today,
because
I
feel,
like
I'm
always
doing
the
same
one
and
trying
different
things.
Does
anybody
have
any
updates
that
they
want
to
share
or
talk
any
things
that
they
want
to
talk
about
today
before
we
get
rolling
with
our
normal
agenda.
A
Emerge
red
x,
otlp,
json
work
and
we
are
working
working
together
on
trying
to
figure
out
the
right
way
to
handle
the
grpc
implementation
of
the
same
thing.
A
There's
a
grpc
proto
proto
like
there's
a
jrpc
protocol,
definition
that
is
set
by
the
specification
team
and
they
that's
what
we're
going
to
use
to
create
the
right
methodology
for
doing
grpc
calls
from
telemetry
php,
where
we
were
discussing
earlier,
where
to
place
those
generated
proto
net
protobufs
and
how
to
use
them
effectively
in
our
code
base.
So
we're
going
to
continue
working
through
that.
A
Delbor
worked
on
doing
a
bunch
of
php
standards,
some
static
analysis
fixes,
which
is
really
nice,
because
it
gives
us
a
little
bit
more
coverage
on
static
analysis
with
salm
and
php
stand.
That
goes
along
with
our
php
unit
tests
and
our
code
coverage
tools.
So
that's
really
nice.
I
started
validating
the
like
the
work.
That's
going
to
be
necessary
to
ensure
that
open,
telemetry
php
can
run
on
php8.
A
For
those
that
don't
know,
php
8
is
set
to
be
released
november
26th,
I
believe
so,
I'm
doing
a
bunch
of
the
leg
work
that
is,
that
needs
to
take
place.
In
order
for
that
to
happen,
there
are
a
couple
libraries
that
we
might
have
to
upgrade
and
most
notably
guzzle
six.
It
doesn't
seem
like
it's
going
to
have
support
for
php
8
and
guzzle
7.
I
think
will
so
I
think,
since
we
have
such
a
wonderful
smattering
of
tests,
we
should
be
able
to
test
that
pretty
effectively.
A
A
Other
things
that
we
have
in
play
are
the
open,
telemetry
exporter,
which
is
done.
Family
you're
stuffed
with
the
w3
c
tracing
contacts
back
then
averages
with
with
associating
expansive
third
tracer
provider
and
then
infection
for
mutation
testing.
So
tommy
you
want
to
talk
about
your
w3c
bets
and
then
ambry.
You
can
talk
about
your
association
expands
with
tracer
provider.
C
Yeah
sure
I
actually
just
put
up
the
pr
the
first
pr
for
the
trace
parent
propagation
yeah,
so
it
just
grabs
a
header
adds
it
to
the
span
context
and
then
does
the
injecting
to
the
when,
when
it's
being
exported
as
well,
so
I've
I've
added
that
bit
and
some
tests
there's
still
a
bit
more
validation
that
I'm
gonna
add.
But
that's
gonna
come
in
another
pr.
C
I'm
gonna
probably
put
up
another
pr
soon
for
the
trace
state
header,
okay,
I've
already
yeah
started
on
that.
It's
mostly
done
just
doing
the
last
bit
of
testing
and
then
after
those
two
I
think
the
basic
functionalities
there
and
then
there's
just
other
edge
cases
and
some
more
testing
that
I
need
to
add
and
follow
on
pr's.
A
C
C
Sure
yeah
and
then
also,
I
think,
once
I
wrap
like
the
actual
functionality
and
all
the
testing.
C
I'm
gonna
do
somehow
try
to
figure
out
some
integration
tests
for
this
and,
like
I
mentioned
a
while
back
that
the
w3c
has
their
own
trace
context
type
of
integration
test
service,
where
you
just
call
into
it
or
use
that,
and
then
you
pass
in
a
little
test
service
using
your
own
implementation,
and
it
just
throws
a
bunch
of
you
know
valid
and
valid
headers
in
there
and
and
tells
you
whether
or
not
you're
handling
it
properly.
A
I'm
also
more
than
happy
to
help
you
with
that.
If
we
want
to
step
some
time
to
do
that
together,
because
that
sounds
like
we
could
use
some
of
like
our
existing
docker
compose
strategy
to
do
some
of
that
testing.
I'm
sure
I
don't
know
if
they
have
do.
You
have
a
link
to
that
repo
or
wherever
they
store
all
the
information
for
that
testing
bit.
C
Yeah,
let
me
just
find
it
real,
quick
I'll
put
it
in
the
chat,
cool
but
yeah.
I
think
it
will
have
to
be
a
kind
of
like
a
docker
type
thing,
because
you
just
create
your
own
test
service
and
then
you
pull
in
their
repo
and
run
it,
and
you
talk
to
whatever
port
that
you
set
and
then
that's
how
the
the
testing
works.
C
So
the
actual
test
service
on
our
site
is
relatively
simple,
but
just
having
everything
talk
to
each
other
is
going
to
be
the
the
difficult
bit
and
doing
that
in
a
non-intrusive
way
in
the
repo
in
our
repo,
very.
B
Cool
and
then
yeah,
I'm
still
working
on
the
associates
bands
with
our
trace
provider,
one
I'm
hoping
to
get
the
pr
up
this
week
for
that
too.
A
At
least
for
me,
I
don't
know
about
everybody
else.
What
does
anybody
have
it?
I
guess
I
should
ask
that.
Oh
thanks,
fami
I'll
make
sure
to
read
that
later
too.
Does
anybody,
speaking
of
blockers
is
any?
Is
anybody
currently
blocked
on
anything?
Is
there
anything
that
we
see?
That's
completely,
that's
outstanding
that
we
need
to
handle
so
on
so
forth.
A
The
other
thing
that
I
am
planning
on
doing
this
week,
the
maintainers
have
all
a
lot
of
the
maintainers
of
other
languages,
have
offered
to
review
the
code
of
other
languages
sort
of
like
a
cross-pollination
thing.
So
I'm
going
to
request
that
our
repository
gets
reviewed
this
week,
or
maybe
probably
next
week,
based
on.
We
have
some
pr's
in
flight
and
we
have
some
other
things
that
we
want
to
do.
But
they're
going
to
like
check
our
you
know,
they're,
just
like
doing
a
large
sweep
of
logic
through
the
prs
or
through
the
repository.
A
A
I
probably
will
wait
until
we
do
the
grpc
one
opening
a
pr
to
that
repo
for
one
plus
mark
plus
one
plus
mark
is
really
annoying
because
they,
it
comes
up
with
all
sorts
of
merge
dependencies
very
quickly,
because
lots
of
people
are
updating
it.
So
I
will
probably
do
that
when
we
have
more
implementation
completed.
A
All
right,
so
everybody
have
ever
it
sounds
like
everybody
has
something
to
work
on
and
don't
have
anybody
blocked.
So
I
guess
that's
that's
it
for
us
for
today
we'll
catch
you
all
next
week.