►
From YouTube: CPC Meeting - 2019-08-13
Description
The OpenJS Foundation is a member-supported non-profit organization that provides a neutral home for some of the most important project in the JavaScript ecosystem.
Learn more and join us at https://openjsf.org
A
A
B
A
B
A
A
There
are
some
items
that
are
that
we
may
discuss.
If
we
have
time
that
are
not
in
that
auto-generated
list
for
the
agenda
we
get
to
them,
they
put
the
link
in
for
hope
and
issues
and
PRS
that
are
going
up
to
the
cross
project
council
agenda
so
but
jumping
into
the
agenda
as
it
is
laid
out
in
the
issue,
the
first
one.
The
first
issue
is
to
85.
A
C
C
319,
so
there's
been
lead
just
two
or
three
people
who
have
been
supplying
most
of
the
help
over
time
and
they're
overloaded,
and
not
really,
you
know
not
necessarily
experts
and
in
the
work.
That's
that
needs
to
be
done
here.
So
I
don't
know.
If
there's
a
way,
we
can
have
a
pool
of
people
who
are
really
good
at
you
know
setting
up
some
of
these,
especially
CIO
CD
type
systems.
You
might
be
doing
it
and
be
able
to
whip
these
things
out
real
quickly.
A
Yeah,
that's
thank
you
for
leading
that
issue
and
you
know
bringing
up
someone's
attention
I'm
looking
through
for
an
issue
that
I
think
has
created
a
long
time
ago.
That
is
about
infrastructure
in
general
and
I,
wonder
if
we
should
start
considering
something
of
an
infrastructure
working
group
that
can
start
to.
B
We
I
was
gonna
time
in
to
add
that
we
did
start
like
an
infra
channel
in
slack,
also
ostensibly
for
folks
who
might
be
interested
in
either
getting
in
for
a
support
or
providing
him
for
support
to
projects.
So
you
know
that's
another
place.
That
would
maybe
attempted
some
kind
of
conversation
here
and.
C
B
C
Actually
have
people,
we
have
the
resources
we
need.
As
far
as
like
servers,
you
know
we
don't
have
problems
there,
it's
really
more
the
expertise
to
configure
and
set
them
up
and
then
over
time
to
maintain
them.
Mm-Hmm
everything
seems
to
get
security
vulnerabilities
in
it,
and
sometimes
the
updating
is
a
little
bit
tricky
I
mean
there's
other
ways
we
can
try
to
handle
that
we
can
handle
it
more.
C
Like
a
you
know,
teach
someone
to
fish
type
of
situation
if
we
can
get
some
assistance
from
who
are
experienced
in
infrastructure
and
want
to
provide
a
tutorial
advice
to
projects
and
I'm
trying
just
thinking
in
terms
of
how
we
can
avoid-
and
maybe
that's
too
far
down
the
road
at
the
moment,
but
trying
to
think
of
how
we
can
avoid
having
you
know
two
or
three
infrastructure
people
that
are
totally
overloaded.
Mm-Hmm.
A
F
You
know,
in
my
experience,
how
things
have
gotten
in
other
areas,
not
with
this
group
but
like
with
others.
So
do
you
think
that's
something
that's
doable
for
this
group
of
like
have
a
goal
of
you
know.
We're
gonna
figure
out,
have
a
proposal
for
the
CPC
to
have
this
level
of
infrastructure
support,
or
you
know
whatever
the
actual
goal
is
and
then,
if
that
group
can
achieve
that
awesome.
If
not,
we
also
know
have
an
indicator
that
and
that
we
need
to
approach
it.
A
G
Just
a
small
thing,
I
want
to
caution
against,
like
it
seems
to
be,
and
I
could
be
wrong,
that
the
resources
aren't
the
issue,
it's
people
to
do
the
labor
and
to
carry
the
water
yeah.
So,
even
if
we
spin
up
a
group
that
has
the
best
of
intentions,
if
the
people
in
that
group
aren't
the
people
who
are
planning
to
do
the
work,
we
do
have
the
risk
of
spending
a
lot
of
time.
Talking
about
it,
we're
not
doing
anything.
C
That's
definitely
a
risk.
I
think
it's.
If
it
was
easy
to
find
these
people,
their
work
could
be
done
already.
I
suppose
so
part
of
it
is
finding
finding
those
folks
that
might
be
interested
in
doing
this
kind
of
work,
but
also
I
think
it
would
be
good
from
a
foundation
standpoint
to
come
up
with
some
sort
of
policy
about
how
we
would
like
when
people
come
asking
for
these
things.
How
do
we
you
know?
What
should
our
response
be
so.
H
I
can
just
touch
on
that
quickly.
Dave
I
know
the
board
is,
is
currently
discussing
infrastructure
in
in
for
projects
and
kind
of
wrapping.
Our
heads
around
exactly.
What's
already
there,
everything
that
came
in
from
the
jsf
and
then
also
yeah
figuring
out
what
what
can
be
offered
to
projects
coming
forward,
because
it's
been
mentioned
a
couple
times
that
resources
aren't
an
issue,
but
that
may
not
be
the
case
forever.
H
I,
don't
think
we
need
to
wait
for
the
board,
because
yeah
I
mean
I.
Think
if
I'm
understanding
the
conversation
and
I
think
this
group
I
mean
part
of
it
may
depend
on
the
board
in
terms
of
what
they
can
allocate
from
a
budget
standpoint,
or
things
like
that.
But
I
mean
I.
Think
the
other
side
of
it
is
just
figuring
out.
G
The
node
projects
perspective-
this
is
a
conversation,
that's
gone
back
and
forth
quite
a
bit
trying
to
see
if
anyone
else
is
on
the
call
who's
been
part
of
those
to
maybe
frame
it
in
a
way
other
than
I
would.
But
our
build
team
over
a
note
is
definitely
one
of
the
places
where
we
we
don't
have
as
many
volunteers
as
we'd
want,
and
even
if
we
did
have
them,
it's
not
not
always
fair
to
expect
volunteers
to
be
on
call.
G
So
so
there
definitely
has
been
conversation
about
whether
or
not
we
should
be
bringing
in
hired
labor
to
handle
managing
infrastructure,
the
biggest
risk
of
which
would
be
kind
of
you
know,
pushing
away
people
who
are
interested
in
doing
it
as
volunteers,
making
them
feel
like
they're,
not
valued.
If
we're
gonna
go
ahead
and
just
like
go
pay
another
organization,
the
flipside.
G
H
C
Ideally,
it
could
be
volunteer
where
the
employers
are
providing
some
subsidy
there
for
for
in
that
person's
time,
and
maybe
there's
a
way
we
can
get.
You
know,
folks
from
from
some
of
the
companies
that
provide
the
software
to
do
it
in
return
for
some
recognition,
I
don't
know,
but
it's
definitely
something
that
is
going
to
accumulate
over
time
and
the
more
projects
that
we
get.
G
David
I
personally
I
mean
to
build
on
that.
I
think
that
if
we
think
about
paying
people
but
paying
people
to
kind
of
keep
the
lights
on
to
be
there
on
call
that
could
free
up
our
volunteers
to
focus
on
moving
things
forward.
Another
thing
we
talked
about
was
like
using
the
volunteers
to
design
the
roadmap,
but
then
like
using
a
contractor
to
just
like
execute
and
get
it
done.
G
But
I
do
I
am
I'm,
not
super
optimistic
that
we're
going
to
be
able
to
find
a
whole
bunch
of
volunteers
that
were
unaware
of.
Perhaps
this
is
even
something
we
could
bring
up
to
the
LF.
Maybe
there
are
people
in
the
cloud
native
compute
foundation
have
these
skills,
and
maybe
they
need
some
help
with
something
like
a
website.
I
don't
know,
maybe
there's
a
way
we
can
collaborate
with
existing
yeah.
C
C
B
So
I,
happily
volunteered
to
organize
like
a
first
call
and
maybe
do
some
preliminary
just
agenda
making
with
with
Dave
and
Chris,
and
maybe
somebody
from
the
node
build
side
I
want
to
also
just
check
in
with
Dave
and
find
out
like
a
little
bit
more
about
that
urgency
from
your
steam.
From
your
point
of
view,
like
is
there
like
regarding
the
testswarm
issue?
Is
there
is
there
a
real
timeframe?
How
urgent
is
this
need.
C
It
does
prevent
us
from
from
doing
testing
in
an
automated
way.
So
it's
slowing
our
ability
to
you
know
put
out
our
new
release.
For
example,
mm-hmm
and
we've
had
a
few
situations
where
we
got
several
commits
down
the
road,
not
realizing
like
we're
so
used
to
seeing
test
failures
on
some
of
these
that
we
just
are
like.
C
A
Great
alright
great
well,
thank
you,
I
think.
It's
important
and
I
look
forward
to
progress
on
that
particular
issue
and
infrastructure
of
all
the
the
next
item
on
the
agenda
is
pull
requests.
279.
Excuse
me,
this
is
adding
a
draft
charter
templates.
It's
got
a
few
approvals
enjoy
I'll.
Let
you
jump
in
here
and
see
that
you
commented
a
couple
hours
ago
and
yeah.
B
So
had
just
a
ton
of
any
additional
comments.
From
last
week,
I
wanted
to
await
review
from
Chris
and
and
Michael
Dawson
I
saw
crisp.
Fortress
was
able
to
give
a
review,
and
so
now
I'm,
just
waiting
on
Michael
I
thought
that
would
be
prudent,
given
that
there
are
board
reps
to
the
community
assuming
there's
not
much
else.
You
know
to
address
from
a
comment
or
edit
standpoint,
then
I
think
the
next
step
is
that
we
decided
is
that
we'll
send
this
over
to
Mike,
Dolan
and
Andy
to
you
know,
get
their
eyes
on
it.
A
A
Great
Oh
excellent,
thank
you.
Joey.
Moving
on
the
next
item
on
the
agenda
is
the
pull
request.
275.
This
is
really
kind
of
you
know
pretty
minor.
This
is
a
pork
roast
I
opened
for
updating
words,
acronym
TAC,
2
CPC
and
the
Charter,
unfortunately,
is
the
change
the
Charter
I
don't
know
if
this
has
been
approved
by
the
board
at
all.
Yet
so
it's
blocked
so
I
guess
I'm,
just
raising
it
to
to
you
know,
get
it
on
the
board's
radar
or
perhaps
I,
don't
know
if
miles.
A
G
This
is
the
Arado
just
like
changing
the
references,
PR
yeah,
exactly
there's
already
been
an
email
to
the
board
about
it.
There's
been
no
word
Mike
a
question
for
you:
I
know
that
when
we
merged
we
changed
some
of
the
by
laws
to
allow
decisions
to
be
made
by
email.
What
kind
of
action
do
we
need
for
the
board
to
you
know,
make
a
decision
towards
charter
changes
if
we're
making
those
decisions
and
emails
are.
G
A
I
I
A
I
Yeah
great-
and
we
can
also
discuss
what
it
would
be
most
useful
in
order
to
address
these
changes
in
the
future,
to
if
there's
a
better
interface
to
the
board
that
we
should
construct.
Let's
just
talk
about
what
that
processor
should
look
like
and
then
get
it
in
front
of
the
board,
so
we
can
use
it.
A
B
That
was
one
that
I
and
I
was
trying
to
mention.
I
forgot
to
mention
right
before
the
call.
So
last
week,
Chris
Hill
her
head
and
shared
that
his
concerns,
or
his
questions
had
been
addressed
on
that
issue.
We
still
have
the
open
and
issue
about,
and
people
request
to
adopt
a
draft
charter
and
we
determined
that
we
could
close
it
last
week.
It
just
didn't
get
done
so
I
did
it
this
time,
but
Oh
reopen
it.
A
Great
thank
you.
So
we
have
discussed
early
on
in
the
meeting
that
before
we
get
into
reviewing
project
boards,
that
we
will
take
a
look
at
open,
pull,
requests
and
issues
that
have
a
agenda
label
on
them.
Jori
went
through
earlier
today
and
flagged
a
few
things
that
were
not
picked
up
by
the
automation.
So
unless
anyone
objects
or
has
something
else,
they
want
to
touch
on
I'll
jump
into
this
list
and
I'll
share.
A
The
list
with
the
group
here
is
in
chat
kind
of
pop
through
these
and
see
what
needs
discussing
so
the
first
one
that
I
see
is
this
is
issued
to
89
maintainer,
x',
verse,
verses
governing
body.
This
was
opened
by
toby
and
since
I'm
unfamiliar
it
was
open.
Six
hours
ago
I
will
read
the
short
description.
The
CPC
charter
defines
the
concept
of
maintainer
as
a
collaborator
elected
to
represent
the
project
in
an
official
decision-making,
making
role
yet
project
progressions
out
and
be
more
appropriately
talks
about
governing
bodies.
A
It
would
be
good
to
have
the
Charter
use
governing
body
or
similar
more
generic
name.
Containers
throughout.
You
can
eventually
add
requirements
with
regard
to
representation
of
main
Tina's
and
the
governing
body
if
you
feel
like
that's
necessary
to
formalize,
rather
than
to
leave
as
a
cultural
norm.
A
B
This
struck
me
as
something
kind
of
similar
to
just
clarifying
or
it's
not
like
it's
kind
of
errata.
It's
kind
of
just
a
clarification
and
perhaps
really
excellent
feedback
from
Toby.
Who
is
his
projects?
Aren't
members
of
the
foundation,
but
you
know
they
very
well
might
want
to
be
some
someday.
So
this
me
was
good
potential
user
feedback
that
I
thought
warranted.
You
know
discussion,
oh.
C
E
A
B
B
Architects
to
start
tracking
that
they
are
there
that
we're
getting
through
the
onboarding
steps,
so
I
would
say
like
if
we
were
to
have
like
a
new
project-
one.
That's
not
already
a
Jas
found
open,
Jas
Foundation
project
that
once
they
pop
out
of
the
quiet,
slash
you
know
quite
period
and
into
the
incubating
stage.
We
would
generate
this
checklist
for
them.
So.
G
From
a
different
angle,
right
now,
if
I
go
to
create
an
issue
inside
of
the
cross
project
council,
repo
I'm
now
presented
with
the
project,
onboarding
checklist
or
I-
have
to
click
a
link
below
to
open
a
regular
issue.
It
does
seem
to
be
creating
a
little
bit
of
friction
for
creating
issues
that
have
anything
to
do
with
something
other
than
that.
G
Considering
that
we're
likely
to
only
you
know
like
open
these
issues
fairly
regularly.
Do
we
have
the
intent
of
making
like
alternative
issue
templates,
to
simplify
that
or
is
I
guess,
I'm
kind
of
erring
towards
like
do
we
need
that
issue
template
or
is
it
a
little
overkill
right
now?
It's
kind
of
getting
in
the
way
of
other
issues
as
well.
B
Well,
I
mean
I'm,
finding
it
helpful,
but
I
think
I
might
be
the
only
one
using
them.
So
if
it's
causing
friction
for
other
people,
I
don't
mind.
Taking
a
few
extra
steps,
I'll
point
out
that
we
had
kind
of
decided
that
this
would
be
a
good
thing
a
few
weeks
ago,
and
so
it
feels
a
little
bit
like
we're,
not
sticking
with
original
decisions.
B
B
To
keep
track
of
because
we
have
30-something
projects
that
need
to
make
sure
that
we
go
through
like
the
onboarding
checklist
for
each
of
them
that
they
all
get
their
charters
if
they
don't
get.
Everything
updated,
doesn't
know
and
I'm
just
finding
it
very
useful
too,
for
that
board
and
for
those
issues
to
exist
to
keep
track
of
everybody's
state.
So
I
know
right
now,
for
example,
that
mocha
and
our
what
state
mocha
an
architecture
in
and
that
I
have
now
32
projects
that
haven't
gone
through
that.
Yet
so
that's.
H
A
Yeah
but
I
think
that
it
makes
sense
there
on
the
template
in
terms
of
guidance,
but
I
guess
it
depends
on
who's
going
to
be
opening.
These
are
projects
themselves.
We
we're
not
expecting
them
necessarily
open
them,
because
they'll
go
through
the
quiet
stage.
First
I'm
kind
of
thinking
out
loud
now,
but
I
wonder
about
taking
the
checklist
out.
But
having
a
link
to
the
checklist
and
saying
you
know,
this
is
the
checklist
that
we
should
paste
here,
because
I
agree
having
duplicate
you
know,
data
is
good,
I
mean.
F
So
it
does
Dre,
it
does
sound
like
the
value
you're
getting
is
not
necessary,
the
value
that
seems
to
that
other
people
seem
to
have
an
issue
with.
It
seems
like
specifically,
they
like
the
github
UI
and
how
that's
structured
is
not
working
for
other
people
and
that
that
specific
part
doesn't
seem
to
be
the
value
that
the
value
that
you're
getting
out
of
it
so
woods,
filling
it
out
into
its
own
file.
B
I,
don't
honestly,
you
know
no,
this
is
just
like
I
I,
don't
honestly
know
I
it's
it's
it's
something
that
again
that
I've
been
this
is
working.
For
me.
This
is
valuable
for
me,
but
if
it
is
causing
problems
for
others,
then
a
different
approaches,
certainly
I
can
check.
I
can
just
keep
a
copy
locally
and
copy
and
paste
every
time.
I
need
to
open
an
issue.
That's
fine!
Go.
J
G
And
joy,
if
you
find
it
useful,
while
there's
like
a
whole
bunch
of
different
tools
that
we
can
have
in
place
to
do
it,
this
is
the
way
that
you
find
it
useful.
We
totally
can
stick
to
it.
We
can
even
update
the
template
to
have
a
link
if
that
simplifies
it.
But
to
me
it
wasn't
so
much
saying
like
it's
not
useful
to
have
that
template
it's
more
like
if
it's
the
only
template
that
introduces
friction.
So
we
should
just
add
another
template.
G
That's
like
basic
issue
or
add
a
couple
templates
for
the
few
things
that
people
might
be
making
issues
for
so
like
requesting,
I
think
like
requesting.
Regular
membership
might
be
one
we
might
want
a
template
for,
and
maybe
it
would
just
make
sense
outside
of
the
context
of
this
meeting
in
the
future,
meaning
we
could
just
brainstorm
like
what
are
the
handful
of
things
that
we
want
to
make
it
easy
for
people
to
know
when
they're,
making
an
issue
and
and
just
make
a
couple,
more
templates,
yeah.
A
I,
am
I
close
through
a
link
to
the
user
feedback.
We
call
a
node
and
I
created
a
few
issue
templates
there
and
there
is
like
a
generic
one
and
it's
I
think
it's
handy
because
it
has
like
a
little
thank-you
note
for
you
know
getting
involved.
So
maybe
that's
the
the
way
forward,
like
Miles,
said
having
multiple
issue
dunkels.
B
First
off
this,
these
issues,
I,
think,
are
just
kind
of
a
temporary
thing.
Right,
like
once.
Focus
on
boarding
process
is
done.
For
example,
like
the
issue
was
closed
and
if
something
changes-
and
we
end
up
needing
different
data
or
we
need
there's
a
policy
change,
we
need
you
know
to
make
sure
MOCA
is
following
them.
We
would
open
a
new
issue
and
so
I
unless
there's
a
change
to
the.
H
A
So
I'm
just
gonna
jump
in
here
and
since
it
is
kind
of
I,
feel
like
it's
in
a
way
minor
and
could
be
easily
addressed.
I
have
two
action
items
here
to
just
create
multiple
issue
templates
and
then
in
doing
so,
my
plan
was
to
update
the
new
project
application
to
simply
linked
to
the
issue,
template
and
say
you
know
this
is
where
we're
keeping
the
checklist
to
reference.
Does
that
make
sense?
You
know
you
know
word
it
well,
but.
A
All
right,
cool,
I
I
want
to
move
on
because
the
next
issue
is
the
proposal
to
lift
no
Jess's
code
and
learn
events
so
to
be
an
open
phase,
cross
project
initiative
and
I
think
you
know
we
have
13
minutes
left
and
this
issue
could
very
easily
heat
that
up
so
I
think
Menil
had
to
drop
if
I'm,
not
mistaken,
I
don't
see
him
in
the
call
and
I
haven't
been
in
on
the
discussions.
If
someone
on
the
call
has
been
in
on
discussions,
please
feel
free
to
jump
in.
J
So
we
have
discussed
in
the
code
and
learn
meetings,
some
new
ideas
about
what
we
can
do
regarding
the
code
and
learn
at
the
node.js
and
active,
and
we
made
a
proposal
in
this
summit.
We
pull
from
noches
and
now
we
want
to
I
reached
out
in
the
infer
slack
Channel
together
to
get
in
repository
for
the
code
ender
and
photo
PJs
Foundation
and
from
there
we
could
start.
You
know
formalizing
the
idea
and
inviting
or
asking
people
for
proposals
based
on
this
new
idea
of
code
under.
F
It's
their
thing
and
I
want
to
make
sure
that
we're
actually
respecting
the
time
and
will
work
that
they
put
into
it
and
I'm
not
trying
to
assert
that
we
haven't
done
that,
but
I
wanted
to
make
sure
that
they're,
the
ones
actually
being
able
to
kind
of
make
the
calls
on
that,
because
it's
not
even
at
node
project.
It's
not
an
official
working
group
or
project
of
No
at
all.
It's
something
that
we've
worked
very
heavily
with
them
on,
but
I
also
don't
want
to
appropriate.
Their
work
got.
C
B
Think
Matteo
had
proposed
that
we
move
move,
that
repo
up
to
the
CPC
level
as
well,
so
I
could
I
wanted
to
I
kind
of
was
looking
at
both
of
these
issues
together
as
being
very
similar
and
I
just
wondered
if
we
wanted.
Maybe
it
would
want
to
take
another
look
at
2:42
and
see
if,
if
that's
an
action
we
can
take
as
well.
A
Already
good
yeah
I
agree,
and
this
may
kind
of
supersede
the
previous
issue.
The
collaborator
summit
has
been
functioning
more,
at
least
the
last
one
as
an
open
jazz
initiative.
So
it
makes
sense
to
me
that
we
take
it
up
a
level.
A
A
A
Things
both
of
these
issues
can
kind
of
happen
over
the
next
week.
Let's
see
the
next
calm
calm
meeting
is
in
two
weeks
on
the
22nd,
but
at
least
we
can
open
the
issue
and
tag
the
relevant
groups
and
start
having
a
discussion
and
make
sure
that
within
the
next
two
weeks
we
have
these
conversations
and
can
visit
both
of
these
issues.
A
A
A
So
the
first
item
in
the
in
progress
column
here
is
the
new
process
for
CPC
reps
to
share
responsibility
for
the
treble
fund.
I've
been
trying
to
keep
an
eye
on
this
I
highlighted
it
in
the
most
recent
calm,
calm
meeting
you
know,
I
I
highlighted
it
for
folks
to
comment
on
the
the
issue
itself.
We
didn't
really
have
too
much
discussion
in
the
calm,
calm
call
and
I
am
NOT
trying
to
find
the
admin
issue.
A
A
A
A
And
this
is
just
the
weeding,
so
that
has
a
low
bar
okay
great
once
you
have
anything
else,
I'll
move
on,
because
we
have
two
minutes
document:
slash
defying
initial
process
for
human
reports
to
report
at
open
JSF.
This
is
issue
number
160,
and
this
has
been
kind
of
working
through
the
proposal
flow
as
a
part
of
the
CSC.
The
next
step
is
to-
and
this
was
comments
in
27
days
ago
to
PR
as
you
go
from
there.
A
A
And
I
I
agree
with
Chris
here
that
you
know
in
general,
it
looks
good
for
stage
one
so
scrolling
back
to
the
top.
We've
got
a
few
approvals
as
folks
want
to
take
a
look
at
it
and
put
their
thumb
on
it
as
well.
I
think
it
makes
sense
to
since
we're
adding
us
to
a
stage
one
proposal
that
they
can
kind
of
move
this
for
objections.
A
We
are
at
the
top
of
the
hour.
Does
anyone
have
anything
else?
They
want
to
comment
on
this
particular
pull
request.
I!
Think
it's
an
important
one.
So
if
you
don't
still
please,
you
know,
put
your
eyes
on
the
pull
request
and
keep
your
eyes
out
for
future
updates
for
CLC
work,
but
if
there
isn't
anything
else,
I
think
we
can
call
it
around
and.
B
B
A
A
giri
asked
for
a
link
to
the
meeting
in
the
chat,
but
that's
not
going
to
last
very
long
because
I'm
about
to
shut
it
down
thanks
everyone
for
joining
and
check
over
in
the
flack
channels
for
any
links
or
what
have
you
I
appreciate
everyone
and
their
time.
Thank
you
for
joining
and
I'll
talk
to
you
next
week
already.