►
From YouTube: 2021-06-30 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
B
B
A
Looks
looks
fine,
okay,
good
excellent,
I'm
not
sure
if
amber
is
going
to
be
joining
yeah.
C
B
She
said
she
mentioned
that
she
she
mentioned,
that
you
all
have
are
super
short
steps
and
you'll
probably
won't
be
able
to
contribute
as
much
as
you
have
them.
A
Yeah
yeah,
it's
yeah.
It's
been
a
bit
strained
lately,
so
yeah.
That's
probably
why
if
you've
noticed
we've
kind
of
been
a
little
less
engaged,
but
hopefully
that
will
change
over
the
next
few
weeks,
nice
you
y'all
working
on
hiring
some
new
people,
yeah.
A
Yep,
I
think
oliver.
A
Yeah
yeah,
he
had
a
couple
questions
about
the
the
w3
choice
context
work.
I
think
it
created
an
issue
about
it
as
well,
where
the
parsing-
oh
there,
he
is
look
at
the
devil.
A
Yeah,
I
was
just
basically
yeah
about
that.
Actually,
you
brought
up
oliver
that
you
created.
Have
you
started
working
on
it
yet
or
should
I
pick
it
up
and
get
going
on
it.
C
I
have
not,
but
I
I
have
it
like
in
my
project
board
to
do
so.
I
can
pick
it
up
or
unless
you
you're,
like
especially
inclined
to
do
it
like
I,
I
basically
did
the
same
thing
in
in
for
the
aws
thing
where
you
just
get
invalid,
essentially
where
you
just
return
it
in
valid
span
context.
C
Instead
of
throwing
an
error,
so
I
can
totally
take
that
on
yeah.
A
Okay,
yeah
sure
yeah,
if
you
already
kind
of
have
it
in
your
mind,
yeah
go
for
it.
I
was
also
thinking
this
might
be
a
good
time
to
add
logging
as
well.
I
know
it's
one.
That's
one
thing
that
we've
kind
of
been
talking
about
for
a
while,
I'm
adding,
except
like
monologue
in
there,
because
I
mean
it's
perfect
for
the
situation.
A
You
know
return
invalid
span,
but
you
know
just
log
can't
parse
the
transparent
header,
for
whatever
reason,
so
that
might
be
a
natural
thing
that
we
do
after
this.
B
That
sounds
good
to
me
and
then
maybe
we'll
just
by
default
log
to
standard
error,
and
then
we
can
like
have
an
environment
variable
that
flags,
the
log
somewhere
else,
because
you
know
a
lot
of
people
won't
give.
I
won't
care
at
all
about
those
logs
and
it'll
just
be
extra
noise,
but
for
debugging
it
might
be
really
nice.
That's
probably
our
best
way
to
make
sure
that
the
logs
are
consumable,
but
not
overwhelming.
A
C
I
have
a
one
thing
to
ask:
you
bob:
is
there
any
like
links
or
directions?
You
guys?
C
You
can
point
me
to
to
like
set
up,
because
I
finished
my
id
propagator
and
generator,
and
I
already
got
it
reviewed
internally
at
here
in
aws,
but
I
was
just
wondering
if
you
guys
have
like
a
kind
of
as
like
a
sample
app,
something
that,
like
like
a
hello
world
kind
of
deal
where,
like
you,
just
send
a
trace
to
a
server
or
you
send
you
sound
like
you
request
something
to
it
from
a
server
just
so
you
can
see
that
trace
just
so,
I
can
test
the
id
generator
and
propagator.
B
There
there
are
a
couple
examples:
we
have
there's
an
examples
directory
in
the
root
of
the
open,
telemetry
php
repo.
That
has
a
couple
examples,
all
with
different,
all
different
sorts
of
things,
and
then
there
is
also
a
symphony
and
laravel
implementation
guide.
So
you
could
always
just
like
make
a
very
simple
cruddy
app
using
those,
and
that
is
like
your
baseline
template.
But
if
you
have
trouble
with
that,
I'm
happy
to
help.
C
Yeah
yeah,
so
I
just
finished
those
once
I
do
the
changes
they
asked
me
to
which
I
already
did.
I
just
have
to
update
the
pull
request.
I'm
gonna
push
it
upstream
so
that
you
guys
can
review
that.
C
But
I
feel
like
I
should
probably
test
like
the
full
kind
of
pipeline
deal
or
like
I
test
like
from
a
sample
app
all
the
way
to
x-ray
and
make
sure
I
can
see
it
on
on
either
end.
Just
before
adding
any
kind
of
code
to
the
main
repository.
B
C
B
A
A
Yeah
just
pop
in
because
I
know
I've
been
here
in
a
few
weeks
so.
B
That's
okay!
I
don't
have
anything
else
further
to
talk
about
all
right
now,
there's
a
couple
open
pr's
where
we're
just
waiting
on
the
committers.
I
think
we
should
cancel
our
meeting
next
week
because
of
the
fourth
of
july
observed
holiday.
I
think
a
lot
of
people
are
taking
off
so
I'll
cancel
for
next
week
and
then
we'll
pick
it
back
up
in
two
weeks.
C
Awesome,
when
are
you
out
of
the
office
this
week,
bob.
C
B
B
All
right,
gents,
we'll
we'll
catch
you
in
two
weeks.