►
From YouTube: 2023-03-01 meeting
Description
OpenTelemetry PHP SIG Meeting
A
A
C
A
C
B
C
B
B
C
A
B
B
A
B
A
B
Yeah
I
don't
have
I,
don't
have
an
M1
Mac,
yet
that'll
be
my
next
computer,
but
we
can
like
we
can
get
Gravitron
or
gcp
arm
instances.
If
we
want
to
I.
Should
probably
you
know
I'll
do
that
this
weekend,
I'll
try
I'll,
try
my
experiments
again.
That
I
don't
know
why
it
was
so
finicky.
Last
time
it
could
have
been
a
number
of
things,
but.
A
A
B
A
B
B
A
A
A
Get
split
packages
but
also
Associates
them
back
to
the
Upstream
one,
because
that's
where
the
documents
and
the
pull
requests
are
yes
effectively
find
the
date
and
the
of
the
last
release.
So,
for
example,
the
objects.
Will
we
released
beta
4,
then
search
but
commits
that
are
newer
than
that,
and
then,
if
there
are
any
propose
a
new
release.
A
So
yeah
so
effectively
read
this.
Follow
this
link
to
create
the
new
link.
Sorry,
the
new
release
brought
this
bit
into
the
release,
notes
and
change
this
to
whatever
the
new
version
is
to
generate
the
diffs
yeah.
So
now
that
we've
got
that
I
feel
significantly
I'll
stop
sharing
now
significantly
more
confident
that
that
we
can
sort
of
manage.
C
A
A
B
A
So
this
one,
if
you
haven't,
looked
at
it
yet
so
so
we've
got
two,
and
these
are
traditionally
the
two
big
you
know
every
it's
like
the
kitchen
sink
open,
Telemetry
repositories
that
we've
told
everybody
to
download
I
guess
what
I'm
trying
to
say
is
that
I
it
doesn't
make
as
much
sense
to
to
have
that
digital
sync
repo
anymore
with
versioning,
because
the
versionings
there's
not
a
consistent
thing.
We
can
version
it
out.
That's
going
to
be
consistent
with
all
of
the
other
individual
packages.
C
B
A
B
A
A
A
B
C
A
B
Do
everything
the
part
of
the
process
to
get
to
General
availability
is
review
from
another
TC
at
Committee,
Member
and
they'll
review
our
repository.
It's
not
always
somebody
that
has
full
PHP
knowledge
they're,
trying
to
find
somebody
that
has
at
least
a
cursory
understanding
of
the
language,
but
like
for
structure
and
idioms
and
just
like
catching
things
so
that
that
will
have
to
happen
before
we
go
to
General
availability,
but.
B
Oh
I
wish
that
would
be.
That
would
make
things
a
lot
easier,
but
yes,
I
also
do
like
having
the
outside
third
party
eyeballs
too.
That
probably
will
help
us
to
find
a
bunch
of
stuff,
especially
since
we
haven't
had
as
much
engagement
with
beta
as
we
probably
expected
to
yes,
so
yeah.
We
should
ask
about
this.
There.
B
A
My
next
point
about
release
candidates
is
probably
redundant
because
we've
been
talking
about
it
a
bit
but
yeah
I,
just
think
we
should
yeah
it's
time
to
push
on
fix
those
last
couple
of
required
for
GA
things
and
and
push
out
an
RC
and
get
that
going.
I
feel
like
we've
had
probably
three-ish
monks
now
of
betas.
A
A
A
A
C
A
B
My
the
thing
I
wanted
to
bring
up
was
the
logging
signal
I
just
wanted
to.
Let
you
you
all
know
they
were
talking
about
finalizing
the
logging
spec
relatively
soon.
They
had
a
couple
like
outstanding
things,
and
a
lot
of
things
have
started
working
on
it.
I
don't
expect
any
of
us
to
like
drop
everything
and
start
working
on
the
logging
signal.
I
just
wanted
to.
Let
you
all
know
that
it's
probably
it's
probably
getting
pretty
close
to
being
ready
to
work.
B
B
A
C
A
C
So
what
you
see
now
is
you
know,
list
of
branches
that
this
a
PHP
extension
is
dumping.
So,
in
order
to
get
something
like
that,
we
have
to
use
PHP
with
this
D
extension
switch
and
with
the
name
of
the
dll
here
and
then,
of
course,
normal
script
that
we
would
like
to
run
and
this
extension
will
dump
something
like
that.
C
As
you
can
see
here,
this
is
dump
for
very
simple
Pro
PHP
script,
as
you
can
see
here
on
this
on
this
on
this
screen,
and
from
that
we
can.
We
can
merge
this.
This
set
of
branches
that
we
have
in
this
file
and
generate
generate
a
kind
of
call
graph,
so
yeah
and
this
program
also
generating
httml,
which
looks
like
that.
C
C
Of
course,
I
and
I
can
show
you
some
more
complicated.
Oh
sorry,
more
complicated
examples,
for
instance,
I
have
also
dumps
for
a
slim
framework.
I
believe
no
did
no.
This
is
for
laravel,
so
that's
the
one
from
the
laravel,
so
the
goal
graph
here
is
is
huge
wow,
for
instance,
we
have
this
kernel,
handle
method
that
we
are
currently
hooking
into.
C
Yes,
so
this
extension
is
cooking
in
every
every
methods
that
is
called
and,
of
course,
this
is
because
I'm
using
I'm
overriding
this
zent
executex
function,
which
is
not
a
very
good
performance
from
for
the
production
environment,
but
this
can
be
I,
think
used
as
a
def
for
developer
purposes
and
to
get
the
whole
dump
like
like
that
and
then
generate
this
course.
Of
course,
the
we
can
only
generate
the
common
things.
So
whenever
you
have
something
that
is
not,
that
is
specific.
C
A
C
A
C
C
A
C
A
A
C
B
C
B
B
B
A
Oh
I
do
have
more
updates.
Sorry,
I
didn't
want
to
see
who
request
against
I've
been
Telemetry
IO
documentation
which
just
got
merged
today
a
couple
of
hours
ago,
just
added
a
bunch
more
stuff,
because
I
guess
that
was
one
of
our
required
for
GA,
really
start
documented
exporters.
So
context,
propagation
and
resources.
A
A
Hello
and
one
more
thing
of
being
just
amazing
about
today
or
over
the
last
couple
of
days
is-
and
this
is
actually
a
post
GA
thing,
but
once
we
do
get
a
version
1.0
out
of
the
door,
I'm
Keen
to
drop
support
for
php7.
For
but
I
do
understand
that
that
people
want
it
so
I'm
wondering
whether
there's
a
way
we
can
once
we've
got
a
1.0
out
just
Branch
off
for
a
1.1
and
drop
support
for
some
PHP
versions
in
1.1
and
sort
of
had
new
features.
There.
A
A
B
B
B
B
B
B
So
my
I
get
four
months
of
fraternity
leave
at
work,
but
I
have
a
feeling
that
I'm
gonna
get
very
bored
and
want
to
still
contribute
to
open
Telemetry
PHP,
because
I
won't
have
to
contribute
to
my
day
job
and
it's
more
a
little
more
async,
but
I
will
I'm
just
I.
Probably
I
probably
will
do
my
best
to
make
maintainers
meetings
and
seg
meetings
and
do
you
know,
do
work
on
the
project
when
I
can,
but
I
probably
will
be
a
little
bit
more
asynchronous.