►
From YouTube: 2022-08-10 meeting
Description
OpenTelemetry PHP SIG Meeting
A
C
B
B
B
F
Yeah
yeah,
I
think
enough.
People
have
it
now.
B
Let's
see
amber,
it
looks
like
you
had
span
processor
incorrect
calls
screen
exporter
for
slash.
You
want
to
talk
about.
E
Those,
oh
yes
bob.
These
has
had
changes
in
two
files:
simple
spam,
processor
and
backspan.
So
I
made
the
changes
in
simple
spanning
parts.
That's
van
gogh,
but
I
think
tobia's
ticket
was
also
had
changes
in
bat
span.
So
I
think
he
also
made
the
changes.
So
maybe
I
have
to
revert
my
changes
on
bad
span.
E
So,
let's
see
means
if
tobias
ticket
is
first
reviewed
and
then
I
will
update
my
changes
and
then
again
push
the
changes.
B
Context
waiting
on
this
person
to
sign
the
design,
the
documentation,
some
psoriasis
to
metrics
exporters
in
progress
kashan
near
b3
propaganda
for
b3
single
header,
this
one's
taking
a
while.
D
Yes,
yeah
the
guys
that
made
a
comment.
I
have
some
doubts
in
that
so
after
submitting
I'll
sync
up
with
him
and
get
this
vr
get
that
doubt
resolved
and
I'll
update
the
pia.
Hopefully
we
will
merge
it
today.
B
Perfect,
that
would
be
wonderful.
I
know
I
know
that
one's
been
no
one's
been
a
slog
for
you.
So
thank
you
for
sticking
with
it
and
thank
you.
You
have
the
pr
with
the
most
comments
I've
ever
seen,
which
is
awesome.
You
have
enough
context
here.
A
Yeah,
actually
I
have
a
few
doubts
about
this,
so
I
have
asked
the
question
on
the
sphere:
can
you
just
go
a
little
bit
up
yep
here
only
so
they're
saying
that.
A
Yeah,
so
I
have
two
doubts,
so
one
is
for
the
status
fail,
retirement
the
status
variable
that
I
use
in
the
should
retry
method
and
another
is
for
whether
we
should
implement
the
logic
in
span,
exporter,
trade
or
the
exporter
itself.
A
B
C
C
C
A
Okay,
actually
I'm
getting
some
problem
with
the
network.
Can
we
can
we
connect
after
the
segmented
person,
yeah?
Okay,
thank
you.
B
C
C
The
test
could
need
some
refactoring
and
it
needs
to
implement
the
cancellation
stuff
that
I
added
for
the
twice
upgrader,
but
that
can
be
done
at
later.
Point.
B
All
right,
yeah
that
sounds
good.
We
so
I'm
happy
to
merge
this
today
and
we
can
just
continue
iterating
on
it.
If
that
works,
for
everybody.
B
All
right
is
that
is
that
everything
I
think
that's
everything
in
the
regular
repo
and
then
the
contrib
repo.
We
just
have
this
one
was
being
worked
on
for
symphony.
It
looks
like
it's
still
a
draft
and
this
one
has
been
sitting
for
a
couple
months.
So
let's
read
on
that.
B
But
is
there
any
open
books
now,
tobias,
you
have
a
bug
open
for
span
exporter
for
slush.
B
Amber
you
said
you
wanted
to
work
on
this.
One.
E
B
Yeah
actually
yeah,
that's
that's
the
one
that
you
had
and
put
the
pr
in
for,
and
I
think
you're
syncing
up
with
tobias
after
this
meeting
for
about
that.
B
B
F
B
F
Was
talking
about?
Do
we
need
the
configuration
interface
we
did?
We
did
put
it
on
hold
a
while
ago,
because
someone
upstream
was
going
to
tackle
configuration,
but
it
ended
up
being
a
mechanism
for
you.
Have
it
having
a
process
receive
remote
updates,
as
opposed
to
an
interface,
for
this
is
what
configuration
object
looks
like
and
which
is,
I
think,
what
we're,
what
our
issue
is
asking
for.
B
I
understand
so
you
think
that
we
should
are
you
you're
of
the
opinion
that
we
should
punt
on
this
for
beta
or
you're
of
the
opinion
that
we
should
try
and
fit
and
finish
it
for
a
beta
release.
F
I'm
not
sure
so.
Teemo
has
some
work
that
he
was
showing
me
maybe
a
month
ago.
They
can
do
this,
but
I
don't
know
where
that's
at
it's
a
useful
thing
to
have,
but
yeah
I
don't
know
if
we
have
to
have
it
for
beta.
B
Okay,
you
made
a
comment
there.
What's
all
right,
that's
those
are
all
of
our
open
pr,
zip
and
bugs
and
required
for
beta
bits
and
pieces.
Does
anybody
else
have?
Does
anybody
else
have
anything
they
would
like
to
add
to
the
agenda
today.
A
So
we
decided
to
have,
can
you
please
give
me
a
little
bit
of
context
and
then
so
we
would
like
to
work
on
this.
One.
B
Absolutely
so
one
of
the
core
tenets
of
open
telemetry
is
that
it
would
have
backwards.
Compatibility
with
both
of
the
previous
open,
open
source,
tracing
libraries,
open
census
and
open
tracing,
and
these
tickets
are
to
make
sure
that
we
have
a
compatibility
layer
that
works
with
with
each
of
those
libraries.
B
So
grunette
made
some
comments
here
about
how
they
handled
the
shim,
and
he
mentioned
that
he
was
going
to
take
a
crack
at
it,
but
like
maybe
he
maybe
he
forgot
about
this
I'll.
I
will
make
a
comment
and
see
if
he's
still
interested
in
working
on
this
one,
but
the
open,
the
open
census,
one
is
definitely
available.
If
you
want
to
work
on
it.
B
B
Making
sure
that
I
make
a
comment
on
this
one,
the
other
the
open
tracing
one
to
see
if
it's
pretty
supply,
I'm
working
on
this.
B
F
I
think
should
we
put
out
another
dot
release
soon.
How
are
we
feeling.
B
F
Are
do
we
think
maine's
in
a
in
a
working
state?
Do
we
want
to
maybe
get
there
were
a
couple
of
things
we're
about
to
merge?
Should
we
get
those
out
first
and
most
tomorrow
or.
B
I
will
how
about
this
we'll
we'll
see
if
anybody
screams
today
and
then
we'll
do
it
tomorrow.
If
nobody,
it's
screams,
good
plan,
all
right,
I
like
it
too,
okay!
Well,
if
no
one
has
anything
else,
then
we'll
we'll
catch
you
all
on
the
internet
next
week.
D
Yeah,
I
just
had
one
thing
to
add,
so
I
have
started
working
on
that
instrumentation
part
and
I'm
using
this
framework,
not
framework
exactly
it's
a
project,
php
cpp.
That
makes
it
easier
for
developers
to
convert
their
cpp
code
as
a
php
extension.
So
I
was
able
to
build
it
and
link
it
with
hotel,
php
sdk
now
I'll
see
if
I
can
set
up
instrumentation
of
any
framework
or
you
know
even
a
simple
scripts,
if
so,
probably
by
next
week,
I
can
have
something
to
present
as
well.