►
From YouTube: 2020-08-05 PHP SIG
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).
B
I
can't
complain
just
just
get
back
from
some
lunch,
so.
B
Like
four
or
five
hours,
contiguous,
so
she's
getting
better
she's
getting
better
she's
have
some
sleep.
Aggression
doesn't
keep
it
coming
in,
but
she
will
be
good.
So
thank
you
for
those
pr's.
By
the
way.
I
I
I'm
sorry,
I
didn't
notice
the
fan,
but
I
just
figured
that
you
had
put
them
in
an
ad
and
like
done
that
they
don't
know
the
pr's
in
our
repo
yet,
but
that
was
a
lot
more
force
than
I
ever
thought.
B
B
Yeah
yeah,
this
project
has
always
been
like
an
uphill
bike,
show
the
whole
time
so,
but
I
don't
think
that's
very
specific
to
our
sick.
I
think
there
that
everything
from
this
back
all
the
way
down,
but
then
everybody's,
very
opinionated,
on
metrics
and
tracing
and
blogging,
because
everybody
has
a
vested
interest
in
how
a
it
works
in
their
language
and
b,
how
it
works
for
their
company
right.
B
We'll
give
it
a
couple
more
minutes
and
then
let's
get
rolling.
A
C
I
am
yeah
and
actually
amber
is
one
one
of
my
colleagues,
so
I
work
from
over
clinic.
B
Are
you
in
oregon
too.
B
B
We're
going
to
wait
until
five
after
to
put
people
away
fair
enough.
B
C
New
relic
so-
and
I'm
here
more
that
I
I
think
I
I
might
bob-
I
might
be
able
to
help
you
on
if
you
need
help
with
more
like
project
management
kind
of
stuff.
That's
that's
not
usually
my
bailiwick,
but
I'd
like
to
try
and
contribute
as
much
as
I
can
so
you
know
anything
that
we
can
do
on
our
side
to
help
out
here.
B
That
is
music
to
my
ears,
because
I
have
tried
to
do
some
project
management
for
this
project
I
am
amber,
will
tell
you.
My
tickets
are
just
like
stream
of
consciousness,
yeah,
there's
just
so
many
things
that
we
have
to
account
for
and
if
the
spec
is
changing
frequently.
C
You're
here
yeah,
so
I'm
working
with
a
lot
of
other
people
here
at
new
relic
keeping
our
fingers.
You
know
kind
of
on
the
pulse
of
what's
going
on
and
with
us
back
and
across
the
languages,
the
language
communities-
and
you
know
it's
so
I
I
think
I
could
potentially
provide
some
value
but
I'll
I'll.
Let
you
decide
how
how
much
okay.
B
A
B
Had
made
a
branch
and
just
like
hadn't,
submitted
the
pull
request,
so
I'm
glad
to
see
that
that
is
in
the
next
thing
is
the
next
thing
and
the
biggest
most
important
thing
is.
We
have
our
first
little
bit
of
the
metrics
api
up
and
running.
It's
a
very
large
pr.
It's
number
155
it's
in
the
open,
pull
requests
section
and
I've
read
through
it,
and
I
don't.
B
I
think
that
there
are
it's
not
perfect,
but
it's
much
better
than
the
state
that
we
currently
have,
which
is
nothing
so
I
think
that
it's
a
venomous,
one
of
the
other
approvers,
is
going
to
review
it
tonight.
You
mentioned
to
me
and
I'll
probably
merge
that
in
tomorrow
I've
asked
in
the
channel
if
anybody
has
them
thoughts
on
it
and
it's
come
up
empty.
So
I'm
assuming
that
nobody
has
any
large
price.
B
After
that
happens,
then
we
can
mer.
Then
we
can
merge
in
amber's
two
prs
that
we
have
for
the
other
bits
of
the
metric
same
yeah,
and
then
we
can
continue
working
forward
with
more
of
the
metrics
agi
yeah.
Is
that
what
you're
planning
on
working
on
next
amber.
B
Yeah,
I
I
totally
agree.
I
think
that
that
is
that,
like
the
same
thing
happened
with,
the
tracing
portion
of
our
project
is
like
we
just
had
to
have
one
relatively
large
for
lack
of
a
better
phrase:
starter
pr.
We
get
like
people,
get
the
ball
rolling
and
get
people
interested
and
get
people
like.
Oh,
this
is
actually
a
viable
product
that
has
examples
that
we
can
show
to
people
and
so
on
and
so
forth.
B
So
I
I
think
that
that
will,
if
we
get
that
metrics
piece
in
that,
will
be
really
nice
to
be
at
least
like
hey
here's
something,
let's
continue
to
build
on
top.
A
B
So
we
got
that
going
jody
for
reference.
Have
you
seen
the
issues
tab
in
the
open,
telemetry
php
project
you're?
Talking
to
me.
B
Cool
all
right,
so
we
have
the
31
open
issues.
We
probably
can
close
a
couple
of
these
because
they've
been
done.
I
will
take
that
action
item
after
this
meeting
and
then
the
next
like.
If
we
want
to
think
about
this
from
a
project
management
perspective,
there
are
a
couple
of
pieces
that
I
think
we
could
focus
on
to
like
make
make
lives,
make
life
easier
for
contributors.
B
B
Okay,
so
yeah,
I
think
we
could
probably
start
working
through
some
of
the
like.
We
could
probably
start
sorting
some
of
the
issues
into
these
into
a
new
project.
We
probably
have
us.
We
should
probably
have
a
separate
project
for
each
of
the
different
pieces
of
this
back
one
for
tracing
one
for
logging,
one
for
metric
logging.
C
B
I
think
that
we
should.
We
should
validate
that
in
the
changelog
of
the
tracing
in
the
changelog
of
the
tracing
spec.
They
have
a
list
of
all
the
things
that
have
changed.
We
should
validate
that.
We
have
those.
If
not,
we
should
cut
tickets
to
try
and
pop
out
those
particular
those
particular
tasks.
Okay,.
C
B
B
B
B
B
The
the
openclementary.net
project
has
has
one,
but
it
doesn't
have
anything
in
it.
Okay,
the
python
one,
the
python
one
has
a
build
infrastructure
one
and
that
would
be
like
a
really
good.
The
catwalk
and
I'll
send
a
link
to
that
in
the
zoom
chat.
Now
yeah,
that's
not
exactly
it's
not
exactly
what
we
need
from
like
a
it's,
not
exactly
what
we
need
from
a
organization.
B
C
B
So
I
think
that
those
are
our
next
steps
amber.
Do
you
have
anything
else?
Oh
I
noticed
that
artem
had
asked
family
if
he
is
still
working
on
his
pr.
Do
you
know
if
he
is
still
working
on
that.
D
A
So,
that's
probably
why
martin
didn't
get
a
reply
yet
so
I
know
he
was
close
to
it.
Probably
when
he
comes
back
he
can
get
more
information
on
that.