►
From YouTube: 2019-10-09 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).
A
A
C
A
A
A
It's
good,
okay,
I
think
we
need
to
get
hit
Ted.
How
are
you
hey,
Harley,
you're,
not
I,
think
we
are.
We
need
to
figure
out
a
better
engagement
model.
I
think
we
I
set
up
a
bunch
of
tickets
and
a
bunch
of
issues
and
stuff,
and
we
are
the
elite
reason.
One
is
really
like
been
doing
any
pushing
forward
myself
included.
I
just
wanted
to
make
like
I
didn't
wanted
to
start
going
down
a
stupid
rabbit
all
without
talking
out
for
it
with
everybody.
D
A
F
C
A
A
A
E
A
Our
last
meeting,
I
set
up
all
of
the
I,
did
a
little
bit
of
work
with
the
github
repository
I
added
a
bunch
of
issues
there
in
the
meeting
the
issues
and
the
I
have
see.
There
are
two
open
PRS
in
the
github
repository
right
now,
so
the
issues
I
open
based
on
the
spec
that
we
had
been
that
Chris
had
been
kind
of
messing
with
us
last
week.
A
So,
based
on
that
spec
I
tried
the
segment
things
out
and
I
got
them
segmented
into
twelve
tickets,
which
eight
so
I
think
sort
of
eight
are
very
actionable
and
some
of
them
build
on
top
of
each
other.
From
there
I
opened
up.
Another
friend
I
went
back
to
the
beginning
of
your
the
Python
repository
Christa,
trying
to
get
some
inspiration
I'm,
like
hi,
you
guys
went
from
zero
to
hero
and
so
I
opened
up.
The
PR,
like
y'all,
had
for
the
first
publication,
with
the
issue.
A
Generator
and
I
also
opened
one
with
an
initial
come
and
commit
the
initial
code.
Commit
is
the
code
that
Maitreya
has
been
working
on
lightly
formatted
for
one
of
the
formatted
for
to
work
in
this
repository,
rather
than
in
basis
companies
I'm
kind
of
concerned
about
that
a
little
bit,
because
it
just
feels
like
he's
going
down
a
path
of
just
yellow
developing
it
not
following
I,
don't
say
he's
not
following
the
spec,
but
he's
not
following
the
patterns
that
the
other
that
the
other
repositories
have
been
following.
A
C
Think
we've,
you
know,
we've
largely
taken
the
approach
that
if
somebody
cares
enough
to
write
something
and
everybody
else
in
the
sig,
hopefully
cares
enough
to
spend
the
time
reviewing
it
and
try
and
get
it
merged
in,
but
it
it's.
You
know
we
don't
have
like
a
great
working
model
for
this
in
in
general,
because
you
know
we
especially
don't
want
to
turn
people
away
if
they
want
to
volunteer
to
do
some
work.
So
I
don't
know
I'm
looking
through
this
now
and
I.
A
A
E
B
E
And
like
they'll,
be
like
things
like
that,
we
have
to
go
be
like
actually
we
for
the
following
reasons:
we
don't
put
this
here,
but
that
can
be
hard
if,
like
everyone
in
the
sig,
is
kind
of
like
starting
from
scratch,
you
know
it
can
be
hard
for
anyone
to
want
to
be
like
assertive
in
that
nature
or
even
know
what
the
what
the
know
knows.
Our
reasons.
A
For
them,
so
yeah
I
totally
see
that
as
being
not
a
showstopper,
but
it's
something
that
we
have
to
sort
of
figure
out
the
way
ID
I
think
once
we
get
a
little
bit
of
operational
velocity,
we'll
be
in
good
shape.
Just
like
you
know,
pushing
the
boulder
out
from
from
its
resting
place
and
getting
it
going
down
that
you're
getting
it
just
start
going
down
the
hill
yeah.
E
Yeah
we
have
not
I've,
never
encountered
a
situation
where
someone's
like
I
really
want
this
to
be
the
official
Oklahoma
tree
thing,
but
also
I,
don't
want
to
like
listen
to
you,
people
it
take
direction
like
no
one's.
No
one's
ever
like
showed
up
with,
like
both
of
those
things
at
the
same
time,
so
you
know
probably
gonna
be
fine.
I
will.
C
Say
that,
like
we've
seen
that
we've
got
a
bunch
of
different
contributors
and
they're
all
they
all
represent
different
parties
and
so
everybody's
kind
of
trying
to
scratch
their
own
itch.
So
we'll
especially
see
you
know,
people
like
with
a
specific
export
or
show
up
and
put
a
lot
of
work
in
there,
like
one
exporter
and
I,
found,
what's
really
helpful
for
this
more
an
open
census
than
open
telemetry
is
to
have
a
set
of
test
cases
first
and
I
mean
I,
know.
C
I,
know
that,
like
a
lot
of
people
are
big
on
test
drone
development
in
general,
but
I
think
there's
like
like
one
specific
use
case
where
it's
really
good
and
that's
if
all
you
have
is
a
spec
and
you're
trying
to
implement
it,
and
you
know
that
the
spec
kind
of
it's
it's
not
fully.
It's
not
so
well
defined
that
you
can
only
have
a
single
implementation
right.
Everybody's
gonna
have
a
different
idea
about
how
it
should
work.
C
F
E
Managers
where
it
just
seems
like
it's
a
tricky
problem
and
like
trying
to
iterate
over
all
the
requirements
in
English
can
be
difficult,
but
if
you
can
get
people
writing
like
test
case,
if
someone's
like
really
arguing
hard
that
something's
important
you
know,
switching
to
like
tests
and
code
in
scenarios
like
simple
scenarios,
I
found
it's
like
very
effective
way
to
get
everyone
to
see
everyone
else's
requirements,
at
least
as
legit,
which
then
usually
leads
to
the
actual
design
converse
not
being
too
complicated.
I.
F
A
You
I
I,
don't
know
for
sure
that
you
want
to
but
possible
I,
don't
think
so.
I
think
I
looked
at
this
yeah
I
think
it's
an
org
wide
setting,
I
I
was
I.
Think
they
changed
that
and
get
we
did
it
get
a
couple
of
github
Enterprise
updates
this
week
actually
and
I
think
that
they
changed
that
in
one
of
the
tweets
like
one
of
the
more
recent
versions
of
github,
yeah
I.
E
I
think
there's
an
org
wide
setting
for
open
telemetry,
at
least
how
it's
been
set
up
for
better
or
worse,
there's
been
a
desire
to
really
keep
all
of
the
repos
kind
of
in
lockstep
and
to
to
have
certain
amount
of
control
locked
down,
which
sometimes
has
felt
kind
of
like
bureaucratic
or
onerous
from
the
stage
we're
at
but
I
think
some
of
it
was
also
maybe
a
reaction
to
open
census
project
feeling,
like
every
sick
kind
of
like
ran
in
its
own
direction
or
something
like
that.
I,
don't
know:
I
wasn't
there
for
that.
E
A
E
Had
an
early
issue
with
like
spec
work
happening
like
that
where
people
from
the
same
word
we're
just
al,
you
being
each
other's
things,
so
one
person
would
like
posts
like
I'm,
changing
the
spec
and
then
another
person
from
same
org
would
just
hit
the
merge
button
an
hour
later,
and
so
you
had
to
be
like
timeout
wait,
let
it
sit
for
at
least
a
day,
I'm.
Definitely
stealing
a
looping.
D
E
A
All
right
cool,
so
it
sounds
like
we
know.
We
know
our
limitations
now
we
know
which
direction
we
need
to
go.
We
just
need
to
like
I
guess,
push
forward
on
this
implement
like
on
how
to
do
this
implementation.
Perhaps
the
best
thing
to
do
is:
is
there
anybody
else
in
this
meeting,
or
that
is
involved
that
we
feel
like
needs
to
be
a
maintainer
or
a
contributor,
because
then
I
could
start
tagging
people
for
PRS
if
I
had
like,
if
I'm
happy
to
make
them.
B
So,
for
example,
for
reviewing
I
mean
I've,
helped
design
components
in
PHP,
but
you
know
it
isn't
my
day-to-day
language,
but
I
will
be
working
on
the
agent
part,
so
I
work
on
the
agent
and
so
that
component.
That
brings
in
open
sorry
open,
open,
open,
telemetry,
PHP
metrics
to
the
agent.
That's
what
I'll
be
working
on?
Okay,
I'm,
not
I'm,
not
proficient
in
PHP.
Nobody.
E
B
A
They
they
I
actually
have
a
bunch
of
X.
That's
see,
they
call
themselves
Etsy
alumni
that
worked
with
me
at
MailChimp
and
I'm
gonna,
see
if
I
couldn't
recruit
some
of
them,
maybe
I
can.
Maybe
I
could
do
that.
The
other
thing
that
I
was
planning
I,
followed
up
with
people
from
slack
that
they
are
technically
using
hack
now
and
not
PHP.
A
So
they're,
like
not
interested
in
the
meeting
note,
which
is
like
such
a
that's
such
a
cop-out
to
me,
but
whatever
and
then
not
interested
than
they're
interested
and
I
think
that
some
of
them
I
have
a
follow-up
meeting
with
some
of
the
with
some
of
the
Etsy
people.
I
think
it's
actually
later.
Today.
We
want
to
sort
of
wanted
to
have
like
a
venting
session
about
tracing
and
which
PHP
as
it
pertains
to
open
census.
E
E
A
It's
just
like
I
think
you're
gonna
stop
the
sentence
earlier.
I
think
it's
just
getting
enough
people.
We
don't
have
enough
people
that
feel
like
they
are
probably
owners
that
their
own
owning
and
being
accountable
for
this
I
think
everybody
wants
the
sausage,
but
nobody
wants
to
make
the
sausage
also.
E
It
feels
just
maybe
like
like
a
bold
move
and
like
I,
don't
know.
I
haven't
found
computer
engineers
to
necess
the
Venn
diagram
of
people,
egotistical
enough
to
be
like
yes,
I
will
run
this
random
project
on
the
internet,
and
the
people
I
would
like
prefer
to
be
running
a
project
on
the
Internet
is
like
not
necessarily
like
a
lot
of
overlap.
You
would
have
landed
in
in
the
overlap
Bob.
It's.
A
It's
a
sample
size
that
well
I'm
I'm,
not
perfectly
apt
to
handle
this
myself.
I'd
recognize
that
and
I'm
trying
to
trying
to
work
through
that,
because
I
feel
like
this
is
important
for
our
community.
Yeah
I
agree
with
you
I
think
that
there's
a
lot
of
introverted
PHP
developers
that
are
not
actively
interested
in
hopping
on.
Let's
do
meeting
with
people
from
other
companies
and
talking
about
how
to
properly
implement
this
I
think.
A
E
A
Why
so
much
time
making
all
those
tickets
last
week?
Maybe
if
I
did
that,
then
we
could
get
some
external
I'm
thinking.
I
might
also
reach
out
to
the
PHP
IRC
vroom
I
think
that
we
might
find
some
really
happy
hippos
there
and
maybe
I'll
try
and
reach
out
to
some
other
like
people
that
I
could
possibly
think
of
and
if
any
of
y'all
buddy
you
can
think
of
them.
You
know
yeah.
E
I
think
that's
great
by
the
way
Oh
minor
point
about
the
the
backlog.
It
looks
super
awesome,
there's
some
like
I
was
just
trying
to
find
the
actual
instructions
for
this
damn
thing
and
realizing
they
may
not
be
posted
anywhere,
but
in
a
PR,
but
there's
this
project
status
we're
trying
to
get
going
on
the
website.
Oh
yeah,.
E
E
There
I
believe
if
you
make
a
PR
against
this
this
this
page
in
the
github
repo
for
a
website,
there's
a
way
to
add
PHP
here
and
then,
if
you
have
like
actual
milestones
that
are
labeled
alpha,
0.2
0.3,
as
opposed
to
like
labels,
then
it'll
automatically
track
progress
as
those
milestones
get
closed
or
something
like
that.
Okay,.
E
C
E
And
that'll
raise
some
awareness
for
PHP
I'm
gonna
try
to
up
our
game
on
this
project-
Status
page,
hopefully
in
the
next
couple
of
days
as
well.
So
we
can
start
showing
like
the
actual
milestones
there,
maybe
if
we
can
start
using
github
releases.
So
it's
like
the
latest
release
for
each
cig.
There,
so
it'll
be
like
a
kind
of
one-stop
shop
for
people
to
look
at
and
get
a
sense
of
like
where's
the
code.
What's
going
on,
okay,.
E
A
A
A
C
But
we'll
see
yeah,
so
you
know
this
this
little
quip
that,
like
the
fastest
way
to
get
a
correct
answer
on
the
Internet,
is
to
post
the
wrong
answer.
I
do
think
when
you
like,
when
you
start
contributing
like
working
code
to
the
repo
like
there
are
gonna,
be
a
lot
of
people
but
I
think
you're.
Looking
at
this
right
now
and
you
know,
don't
want
to
contribute
to
repo
that
doesn't
have
anything
already
running
in
it.
C
So
we
saw
this
in
the
Python
setting
but
like
as
soon
as
we
had
a
like
just
the
context
propagation
that
working
in
the
API,
it
was
there's
a
lot
easier
to
get
contributors
and
so
I
think
any
case.
You
got
this
the
scammers
in
and
also
when
you've
got
a
description
in
the
readme
of
like
how
to
actually
run
this
thing.
B
C
B
C
A
A
So
is
there
any?
Are
there
any
other
actions
that
we
want
to
talk
about
here
and
I
want
to
just
like
going
circles
just
because
they're?
How
do
you?
It
was
like
kumbaya
time
here,
I'm
very
happy
to
let
everybody
go,
and
we
can
pick
this
back
up
next
week
after
we
accomplish
some
of
the
action
items
we
have
I
think.
E
A
F
C
A
C
A
A
C
E
C
A
C
A
C
E
E
A
Other
thing,
I'm
realizing
is
that
I,
don't
think
I
think
that
he's
actively
not
signing
exhausting
about
that
too,
and
he
just
disregarded
it
so
that
I'm
like
again,
it's
not
that
I'm
concerned
about
it.
I
just
think
it's
worth
noting
that
it
feels
like
he's
actively
trying
to
he's
actively
trying
to
be
involved,
but
then
his
active
trying
to
actively
trying
to
also
not
be
involved,
which
just
feel
it
feels
very
red
flag.
Ii
to
me.
Well,.
E
I'm
happy
to
help
facilitate
a
conversation
there
about
if
it
if
it
starts
to
go
sideways
but
yeah
it.
Certainly
we
don't.
We
don't
want
to
end
up
in
a
situation
where
we're
starting
from
a
code
base
where
the
primary
maintainer
that
code
base
is
on
my
being
like
whoa
I,
don't
want
to
sign
a
CLA
or
like
Hannah's
over
to
the
CN
CF
that
that
would
definitely
be
a
red
flag.
We
have
to
resolve
that
before
we
go
forward
to
this.
E
A
That's
what
I'll
do
I'll
take
ownership
of
that
today,
I'll
put
in
an
initial
PR,
not
using
his
repository
as
a
baseline,
and
then
my
my
gut
feeling
is
that
when
I
do
that,
he
will
recognize
that
there's
other
contributions
besides
his
own
and
he
will
try
and
you
know
either
sign
the
CLA
or
we'll
find
out
that
he's.
Actually,
he
has
some
sort
of
other
underlying
principle
that
he
doesn't
want
to
contribute
that
way.
So
I
think.