►
From YouTube: 2022-11-23 meeting
Description
OpenTelemetry PHP SIG Meeting
A
A
B
A
B
Excellent
I'll
screenshot.
B
A
B
It
we've
also
got
one
very
simple:
pull
request
for
contrary,
which
was
just
to
change
the
dependencies,
because
it
was
trying
to
install
attacked
version
and
couldn't
do
today
or
at
least
couldn't
do
easily.
B
A
Yes,
so
I
discovered
that
there
is
memory
leak
when
we
are
trying,
you
know,
throw
exceptions
from
this
boost
post
and
I'm
currently
investigating
it.
This
is
not
related
to
my
recent
changes.
We.
B
Yeah,
that's
interesting
and
thank
you
for
pointing
it.
What
it
made
me
think
of
is
that
we
probably
really
need
a
debug
build
of
PHP.
Yes,.
A
It
was
cool,
I,
think
yeah,
because
because
you
know
on
unrealist
builds
this,
it's
not
visible.
In
fact,.
B
Yes,
yes,
yes,
which
is
not
good!
Yes,
I've,
been
putting
off
doing
anything
about
that,
because
there
aren't
any
existing
maintained.
Docker
images
of
debug
builds
of
PHP
will
have
to
build
it
from
source,
but
that's
what
we
have
to
do.
B
I
can
either
create
a
job
to
sort
of
build
and
tag
PHP
from
source
and
then
use
that
is
their
job,
but
maybe
building
PHP
from
solar
system
that
slow
I,
don't
remember,
but
anyway,
I
might
I'll.
Take
a
note
for
myself
that
that's
something
that
we.
A
B
Mind
yeah
yeah!
Well,
you
know
the
first
thing
to
do
is
test
it
out
and
see.
I
mean
I
know
come
I,
do
build
it
from
Source
locally
in
our
Docker
compose
build
so.
A
B
B
I
think
we
call
this
a
bug:
I
haven't
even
hadn't,
even
thought
about
it,
but.
B
It's
not
that
I,
don't
I,
don't
think
it's
in
it
would
stop
us
going
to
going
to
Beta
this
one
yeah
I,
don't
think
it's
going
to
be
small,
but
I.
Don't
think
that
would
stop
a
skeleton
beta
either,
but
it's
just
something
I
noticed
when
I
was
reading.
The
spec
is
that,
shall
we
accept
the
word
true
or
very
spellings
of
truth
and
not
all
of
the
other
things
that
we
currently
do,
and
it's
a
must.
B
So
we
agree
yep,
that's
a
lot
of
priority,
though
so
treasurement
did
you
did
you
have
any
updates
that
you
wanted
me
to
to
notice.
A
So
I
can
tell
you
what
I
will
be
doing
next
week.
So
now
I'm
focusing
on
this
on
this
memory
league
and
then
I
want
to
fix.
Also
the
last
unit
test
that
left
it's
about
duplicate,
hooking
into
interface
and
then
probably
I
will
also
maybe
try
what
what
is
the
I
will
check.
What
is
the
coverage
of
of
our
current
unit
test
and
maybe
I
will
try
to
add
more
tests
and
Implement
these
gaps
that
we
that
I
will
find.
A
We
will
see
if
we
will
have
some
gaps
and
basically,
probably
that's
it
for
the
extension
at
the
current
and
we
will
need
more
tests.
I
think
end-to-end
tests,
probably.
A
Also
I
was
thinking
about
trying
to
to
to
write
this
extension
in
C,
plus
plus,
as
as
I
found
that
there
is
a
library
for
that
and
I
was
thinking.
Maybe
it
would
be
easier
to
to
to
do
that
in
C,
plus
plus,
as
there
are
some
abstractions
over
a
memory
management
and
so
on,
yeah,
so
I
was
thinking.
Maybe
the
code
would
be
easier
to
maintain
with
in
C
plus
plus,
but
that's
that's
something
that
maybe
I
will
try
in
in
free
time.
B
Would
be
interesting
and
look
I
guess:
we've
got
that.
We've
got
a
good
well
fairly
good
set
of
tests
now
to
to
know
whether
it
works
or
works
or
not.
B
So
you
mentioned
unit
test
coverage.
If
you
work
at
how
to
do
that,
that
could
be
like
if
you
can
look
at
how
to
easily
generate
that.
That
would
be
really
interesting
to
be
able
to
generate
some
sort
of
output
from
as
part
of
our
local
development,
and
maybe
even
our
like,
have
it
reported
on
in
in
our
CI
pipeline
mm-hmm.
B
B
A
B
Yes,
yes,
hopefully
I'll
find
any
lots
of
small
bugs
or
use
a
building
issue.
Well,
hopefully
I
don't.
But
yes,
yes,
whether.
B
Some
confidence,
that's
all
from
me,
do
you
have
anything
else
that
you
want
to
talk
about
tonight.
A
Maybe
one
question
I
have
what
would
be
the
process
of
becoming?
Let's
say,
maintainer
of
this
C
extension.
B
Sure
so
to
be
a
maintainer
of
the
extension
I
think
you
need
to
be
a
maintainer
of
open
telemetry
PHP.
All
of
but
there
is
a
there
is
a
process.
B
You
need
sponsorship
from
existing
maintainers,
which
is
Bob
and
I.
Okay,
and
then
you
basically
need
to
point
to
your.
You
know
existing
contributions,
which
is
only
small.
It's
like
you
need
to
link
to
a
number
of
pull
requests
that
you've
made
and
issues
that
you've
raised
and
commented
on,
basically
just
showing
you
doing
things
for
the
project
which
I
think
you've
easily
done
enough
if
you're
interested
yeah
yeah.
So
so
that's,
that's!
That's
the
process.
B
Okay,
yeah,
I'll,
I'll
I'll
find
a
link
or
ask
Bob
about
it,
but
yeah
that
that
that's
that's
in
a
nutshell.
I
did
this
about
one
year
ago.
Now
so
yeah
it
was
it
wasn't.
It
wasn't
very
onerous
and
I
think
that
you
would
easily
meet
the
requirements
yeah
just
long
as
you
understand
it,
I
think
you.
B
Well,
I
think
technically,
you
you'd
have
to
be
a
maintainer
for
like
the
main
repository
as
well,
but
if
you
were
mostly
interested
in
in
the
the
extent
contain
you
know,
that's
that's
probably.
A
B
A
A
Yeah,
okay,
so
currently
I'm
mostly
involved
in
you,
know
in
this
extension,
except
the
work
that
I'm
doing
in
go
instrumentation.
Yes,.
A
Where
I
am
already
a
maintainer,
but
so
so
that's
why
I
am
interested
in
in
this
extension.
For
now,
yeah.
B
I
understand
so
it's
probably
gonna
be
easier
again
for
you.
If
you're
an
existing
maintainer
in
a
different
in
a
different
sea.
B
Okay,
all
right
leave
that
with
me,
I'll
I'll
message
both
the
other
maintainer
about
it
and
just
find
find
a
link
for
you
to
to
follow
yeah
yeah
that
that
shouldn't
be
a
problem.
I
think:
okay,
okay,
get
that
happening
pretty
quickly.
A
Okay,
thank
you,
so
you
will
send
me
some
link
or
or
I
should.
B
Yes,
I
will
I'll
send
you
a
link.
Oh.
B
B
B
B
Okay,
anything
else
from
you,
Chris
make.