►
From YouTube: 2021-05-19 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
B
A
B
A
B
A
A
Really,
the
let's
see
the
environment,
not
the
the
exporters,
there's
an
exporter
section
in
there
and
they
have
grpc
export
the
http
binary,
http
json
httpg,
sip
content,
encoding.
A
A
By
the
way,
yeah
yeah,
because
I
think
that
I
would
guess
that,
maybe
that
would
be
like
the
passing
it
in
the
constructor
would
be
the
best
way,
because
I
feel
like
once
this
is
done.
It's
not
like
nobody's
ever
gonna
touch
this
ever
again.
It's
just
gonna
sit
there
in
perpetuity
until
somebody
changes
something.
A
A
All
right,
so
we
actually
don't
have
very
many
open
prs,
though,
which
is
good.
We
have.
We
have
a
new
jaeger,
udp
and
thrift,
pr
that
got
opened.
That
is
just
essentially
the
same
one.
That's
active
had
been
working
on
and
just
like
he's,
gonna
close,
the
old
one
and
open
the
new
one,
because
there
was
too
many
merge
conflicts
and
too
many
things
that
they
wanted
to
deal
with.
I
guess
so.
A
I'm
planning
on
reviewing
that
today
and
I'll
probably
ask
for
help
from
somebody
else
in
the
channel
to
get
a
second
review
on
that
there's,
a
pr
from
dec,
deki
deki
and
I'm
gonna
merge
that
right
now,
because
I
approved
it
and
finally
approved
it.
So
that
closed
the
bug.
So
that's
good!
A
And
then
we
had
abusee's
working
test
example
and
test
for
improvements.
Pr,
I
think,
he's
in
the
middle
of
getting
that
reviewed
by
d
karlovy
and
then
yeah
the
the
mutation
testing
pr
has
been
sitting
there
for
forever.
So
I'm
not
going
to
worry
about
that
one.
So
we
have
a
couple
of
pr's
open
but
nothing
crazy.
I
think
that
we
will
most
likely
do
the
release
tomorrow.
A
B
Yeah,
I
don't
think
that
release
needs
to
wait
for
that.
A
The
abuse
is
doing
he's
walking
through
the
next
release
with
me,
so
that
we
can
document
it
and
make
sure
that
other
people
understand
how
it
works
and
then
we'll
release
0.0.2
pre-release.
So
that's
kind
of
exciting
open
bugs.
A
A
A
A
A
Yeah,
I
don't
think
that
that's
what
they're!
I
don't
think
that
what
hugs
boss
boson
is
looking
for.
I
think
they're,
looking
for
like
a
way
to
easily
import
like
have
a
the
ph,
have
an
auto
instrumentation
for
php,
but
I
don't
think
I've
been
close.
Oh.
A
I
think
that's
what
I
think:
that's
what
they're
looking
for,
but
I'm
not
actually
certain
so
yeah.
It's
a.
I
do
appreciate
all
the
samples,
but
they
seem
targeted
a
small
toy
examples
and
don't
help
me
understand
best
practices
for
a
system
with
50
plus
php
library,
authors
and
tons
of
contributors
so
yeah
they.
A
Yeah,
so
I
can
talk
through
with
them
about
what
we
did
for
open
census
at
mailchimp,
which
is
essentially,
we
have
a
library
class
that
wraps
around
all
of
our
http
request
logic
and
all
of
our
like
third-party
stuff,
like
that
and
tell
them
that
that's
an
abstraction
that
they
could
use.
But
I
feel
like
this
doesn't
I
feel
like
this
is
just
somebody
complaining
like.
I
don't
think
that
there's
actually
any
action
that
can
be
taken
here.
A
I
think
they
either
don't
have
like
a
very
adequate
model
wrapped
around
how
they
make
their
requests
within
their
organization
or
they
don't
really
have
like
knowledge
of
how
you
would
wrap
this
library
in
php
and
our
small
examples
don't
sort
of
fit
the
mold
of
what
they're
trying
to
accomplish
so
they're
complaining
but
yeah.
I
don't
know
I
think,
but.
B
A
A
Right
and
then
classic
open
source
response
prs
are
welcome
if
you
want
to
come
up
with
a
little
instrumentation
for
the
p
for
php.
A
I'll,
that's
actually
I
like
that
that
fra,
that
phrasing
working
model
sounds
good,
because
I
want
to
be
able
to
let
a
lar.
This
would
be
nice
if
a
larger
organization
started
using
this
because
they
could
a
they
would
probably
give
us
some
meaningful
feedback
and
b
they
probably
would
start
opening
bugs
in
fixing
stuff
too.
A
That's
another
thing
that
I'm
glad
I
said
because
I
forgot
to
share
it:
elita
who's,
one
of
the
maintainers
of
a
bunch
of
the
languages
and
she's
like
one
of
the
core
drivers
for
aws,
mentioned
that
they
want
to
get
aws
x-ray
working
for
php.
So
they're
going
to
they're
over
the
next
couple
weeks,
theoretically
going
to
add
a
couple
new
contributors
to
this
project,
which
I'm
very
excited
for,
because
I
think
they
have
a
lot
of
really
good
visibility
into
the
telemetry
space
and
it'll
be
nice
to
get
some
fresh
eyes
cool
yeah.
A
A
See,
if
you,
if
you,
if
you
had
to
choose
between
those,
I
would
say
the
links
would
probably
be
more.
I
mean
more
single
threaded
and
siloed.
I
think
that
there
are
other
people
that
would
like
that
also
have,
like
sean,
probably
has
really
good
context
into
how
to
change
the
http
otlp
thing
so
yeah.
I.
B
A
Ask
him
to
do
it
or
I
might
have
somebody
coordinate
with
him
because
I
want
to.
I
want
to
continue
to
empower
him
with
that
change,
because
it's
something
that
he's
been
working
on,
but
if
he
doesn't
want
to
do
it,
then
I
think
that
we,
like
somebody
else
could
take.
I
feel
like
links,
are
a
little
bit
more
difficult
for
somebody,
not
quite
yet
well-versed
with
telemetry
to
understand.
So
I
think
that
your
skill
set
would
probably
be
much
more
valuable.
There.
A
At
least
so
so
I
think
links
are
one
of
the
only
things
that
are
left
for
alpha.
They
have
in
the
specification.
They
have
a
whole
list
of
like
the
release
candidate
or
like
the
releases.
But
the
problem
is
it's
like
they
did
that,
while
they
were
coming
up
with
the
specification,
so
it's
like
it
was
a
moving
target
at
the
time.
It's
not
like
a
perfect
moving
target
for
us.
A
A
The
ga
release
seems
to
be
a
pretty
common
practice
amongst
the
other
sigs,
and
they
also
some
of
the
other
sig
or
some
of
the
maintainers
also
have
volunteered
to
do.
Spec
audits
on
different
language,
sigs
and
the
other
maintainers
recognize
that
php
doesn't
have
nearly
as
many
contributors
as
some
other
languages,
so
I'm
sure
they'll
be
eager
to
volunteer
to
help
spur
us
along
a
little
bit.
So
I
think
that
the
more
of
these
release
for
release
required
for
gi
tickets,
we
can
slap
through
the
better
off
we're
going
to
be
yeah.
B
A
Yeah
it's
like
when
we
went
to
pre-alpha.
We
definitely
got
a
lot
more
engagement.
I
think
when
we
actually
make
it
to
alpha,
we
could
get
more
engagement
and
I
think
that
that's
just
the
decision
that
we
like
as
a
team
we
have
to
make
I'm
not.
I
don't
want
to
make
that
decision
by
myself,
but
I
also
don't
want
to
like
hinder
customers
from
using
this,
just
because
it's
in
a
pre-alpha
state,
when
it
really
is
in
an
alpha,
2
state.
I
actually
think
we're
probably
at
an
alpha
state
already.