►
From YouTube: CPC Meeting - 2019-11-05
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
Couple
of
things
we
should
definitely
be
encouraging
everyone
from
the
project
community
to
register,
to
attend,
node,
plus
jeaious,
interactive
and
also
to
submit
sessions
for
the
collab
summit,
we're
just
a
maybe
five
six
weeks
away
from
the
event
so
and
it's
gonna
be
really
awesome,
we'll
want
to
see
as
many
people
as
possible
there
in
Montreal,
not
only
because
it's
all
warm
if
we
can
huddle
together.
So
please,
please
tell
your
friends.
B
The
thing
I
want
to
share
is
that
per
our
conversation,
the
onboarding
issues,
which
were
quite
filling
up.
Our
CPC
issues
list
have
all
been
moved
to
the
new
project,
onboarding
repository.
So
if
you
happen
to
be
going
to
navigate
to
look
for
your
project,
onboarding
issue,
that's
now
in
the
project
onboarding
repository
and
not
in
not
in
the
CPC
repository.
A
Thank
you
and
I'll.
Add
to
you
know,
as
we
were
talking
earlier
before
we
went
live.
Is
that
I
created
a
cross
project
council
agenda
label
in
that
repository,
and
it
should
be
that
if
you
apply
it
in
that
repo
it'll
still
pick
up
in
the
cross
project,
Council's
agenda
so
feel
free
to
use
that
label
there
and
we
can
cross
them
from
the
eCos
and
I'm
not
leading.
B
Oh
one
more
thing:
sorry,
we
are
doing
a
AMA
for
the
nodes
Hong
Kong
tomorrow
morning,
first
social,
so
and
if
you
want
to
support
your
colleagues
on
Kham
Kham
or
just
encourage
people
to
participate
in
the
AMA
tomorrow
morning,
great
you.
A
All
right,
great,
thank
you
cool,
so,
let's
get
into
the
issues.
Here
are
the
agendas,
as
they
were,
the
first
one
agenda
items
is
issued.
390
I
opened
this
up
a
few
days
ago,
based
on
some
discussions
with
jewelry,
actually
about
things
that
we
may
want
to
have
at
the
collab
summit
in
in
Montreal
at
know,
Jeff's
interactive,
note,
plus
PS
I
was
thinking
that
we
could.
A
You
know,
try
to
just
have
a
slot
for
across
project
council
and
we
could
either
break
out
into
corners
of
the
room
for
different
areas
that
you
know
we
may
want
to
focus
on
or
wondering
if
we
should
have
separate
sessions
on
different
topics
here.
The
things
I
have
listed
our
transition
process
and
support
emeritus
project,
something
that
that
Joey
had
voiced
standards,
working
group
infrastructure
and
overall,
like
project
progression,
acceptance,
rejection,
sound
process
on
boring
off
warning
those
sorts
of
things
we
were
all
together.
C
My
first
thought
is:
these:
are
all
good
sort
of
the
very
specific
thing
was
to
work
on
together.
The
other
thing
I
thought
we
might
want
to
have
scheduled
some
time
for
is
like
the
blue
sky
thinking
or
whatever
you
know.
We've
got
the
you
know
good
start
on
getting
the
application
process
and
all
that
running.
Should
we
now
start
thinking
about
other
things
that
we
think
we
want
the
CPC
and
the
foundation
to
champion
in
terms
of
pushing
forward.
You
know
we're
there
other
working
groups,
we
think
we
should
be
spinning
up
or
other.
A
Good
suggestion
I
actually
dropped
within
my
issue
here,
as
well
as
the
minutes.
Do
we
think
that
these
should
be
separate,
collab
summit
submissions,
or
should
we
just
try
to
block
out
a
little
time,
and
you
know
we
can
work
on
these
in
that
time
flock
together.
B
A
C
Guess
the
other
thing
to
think
about
is
you
know,
do
we
want
working
sessions
or
is
do
we
want
to
like
have
a
session
such
that
you
know,
new
people
could
join
and
we'd
be
kind
of
marketing
to
them
that
they
should
get
involved,
or
does
that?
Would
that
might
reflect
whether
we
want
one
or
two
or
the
flow
that
kind
of
stuff.
C
A
E
F
F
C
A
A
C
Only
the
only
thing
I
think
that
we
want
to
have
in
advance
is
like,
if
it's
purely
a
working
session,
where
it's
like
hey
it's
existing
members
of
the
CPC
or
you
know,
people
who
want
to
be
involved
and
we're
gonna
get
together
and
work
on
like
a
working
session.
Or
is
it
any
Oris
or
is
you
know
if
they're
people
who
haven't
been
involved
and
don't
necessarily
want
to
be
involved
ongoing,
but
I
want
to
have
an
update?
C
A
A
I
think
would
be
ideal
to
have
a
you
know,
ten
minutes
spot
on
the
community
corner
to
highlight
the
work
of
the
CPC
and
point
people
to
a
couple
of
different
things.
Number
one
jewelry
and
I
have
a
talk
at
the
conference
on
you
know
with
the
CPC
and
the
foundation
and
whatnot
and
I'd
also
like
to
try
and
have
maybe
an
open
office
hours
at
the
community
corner.
A
After
our
talk,
which
I
think
is
on
the
second
day,
so
I
could
point
people
to
that
open
office
hours,
and
we
can
also
use
that
from
the
talk
stage
to
say.
If
you
have
questions,
you
want
to
talk
to
us
more
we're
having
no
post
office
hours.
You
know
this
afternoon
or
what
have
you
and
then
also,
you
know,
promotes
a
collapse
on
a
working
session
that
would
be
open
to
you
know,
folks,
the
oh.
C
A
C
A
All
right,
well,
I,
you
know
unless
anyone
has
any
objections
or
wants
to
discuss
it
further.
My
plan
is
to
reach
out
to
Eva
and
the
team,
the
collab
summit
and
try
to
kind
of
you
know
execute
on
that
idea.
Those
those
a
succession
of
ideas-
and
you
know
see
all
we
can
do
I-
will
try
to
arrange
for
some
time
at
the
collab
summer.
That's
a
block
of
time,
and
they
can
you
know
craft
an
agenda.
A
A
This
was
opened
by
Brian.
This
relates
to
email
addresses
that
new
projects
proposals
are
sent
to
it's
a
concern
for
many
of
us.
That's
when
we
hit
reply
on
those
new
project
proposals
discussing
things
that
are
private,
that
the
proposer
might
be
on
the
email.
So
the
idea,
if
I'm
capturing
the
brightest,
is
that
we
excused
operations,
email
and
then
Brian
would
send
it
along
to
the
internal
list.
A
B
A
Can
I
suggest
that
you
know
we
perhaps
choose
a
manager
at
that
point
as
well?
You
know
you're
gonna
put
the
temperature
until
we,
you
know
people
give
it
a
thumbs
up
to
move
forward.
B
Think
that's
a
good
idea
and
I
would
also
say
then,
because
we
we
also
had
this
goal
of
being
able
to
reply
within
a
certain
time
frame
to
a
project
that
has
submitted
to
the
new
projects
list.
So
even
that
we're
now
possibly
creating
you
know
more
of
a
gap
between
the
CPC
responding
to
the
project's
application,
then
whoever
takes
the
operations
at
email
should
be
responsible
for
acknowledging
receipt
of
the
message.
In
my
opinion,
yeah
agreed.
Okay.
G
E
D
A
A
A
A
So
moving
on
the
next
agenda
item
is
to
review
the
community
committee's
charter
update
notes,
as
community
committee
attorney
open
this
up
a
week
ago,
and
I
was
you
know,
reviewed
this
at
the
kumkum
number,
but
I
encourage
folks
to
take
a
look
at
this,
make
sure
there's
nothing
that
stands
out.
I,
don't
know
how
we
are
capturing
like
approval
for
this
I'm
Michael.
How
did
we
do
this?
For
the
TFC.
C
C
Yeah
I
think
we
just
we
just
did
something
like
what
we've
had
there.
We
opened
an
issue
saying
here
it
is
over
here
and
if
people
could
+1
in
the
issue
itself,
that's
what
I
did
I
think
we
can.
Then
just
you
know
once
it's
been
open
for
a
certain
amount
of
time
and
we
think
we
have
enough
plus
ones.
Although
there's
no
fixed
number,
we
should
be
able
to
then
say:
go
ahead.
C
C
C
B
H
C
I
C
It's
not
like
we're,
not
gonna,
have
a
vote
or
anything
like
that.
It's
just
purely
the
FYI.
Let
us
know
if
there's
any
concerns,
otherwise
it'll
land.
You
know,
and
we
should
choose
I.
Think
for
the
assist.
We
should
basically
say,
you
know,
add
your
plus
ones
or
your
objections
or
discussion
there.
Otherwise
we
don't
it
can
land,
and
we
should
just
choose
that
like
a
week
from
now
two
weeks
from
now,
whatever
we
think
gives
people
enough
time
to
to
review
and
see
if
they
they're
not
there.
Okay.
C
B
A
A
A
If
anyone
wants
to
drop
that
little
bit
of
context
of
the
issue,
that
could
be
helpful.
Excellent.
Thank
you.
So
the
next
agenda
item
is
to
move
the
COC
proposal
to
stage
three.
This
is
full
request.
379,
the
amp
team
is
working
through
some.
You
know
their
their
incubation
and
different
aspects,
and
you
know
one
of
the
things
that
they're
working
on
is
their
conduct,
you
know
or
as
a
I
guess
in
terms
of
how
they're
is
aligned
to
the
foundations
and
such
I.
A
A
D
I
agree:
we
have
a
meeting,
was
the
working
the
incubation
working
group
later
today,
so
I
can
bring
that
up
at
that
point,
but
I
do
agree
that
if
it
doesn't
feel
like
this
conversation
should
block
moving
that
PR
and
I
think
it
should
be
moved.
Its
own
issue
I
think
it's
an
important
conversation
to
have,
but
like
I
shouldn't
blocked
it
I.
Don't
think
you
should
block
that
PR.
C
D
A
A
E
A
So
yeah
I
mean
I
think
we
can
keep
this
open
until
we
get
that
sorted
out
and
thank
you.
Joy
from
moving
tickets
over
today,
like
I,
said
I.
Think
the
label
will
pull
them
into
our
agenda
and
then
once
we
feel
like
we've
got,
you
know,
process
shaping
up
around
onboarding
and
applications.
Then
we
can
probably
close
this
issue.
I'm
I'm
thinking.
C
You
know
consensus
building
once
that's
in
place,
then
you
know
marsan,
we'll
look
at
using
it
to
do
something
that
would
be
like
specific
recommendations
for
the
open,
Jas,
Foundation
project
members,
okay,
great
and
then
some
package,
maintenance
or
security
working
group
I
know
it's
in
the
no
GS
package,
maintenance,
repo,
the
PR,
okay.
I-
can
probably
dig
that
up.
While
we
talk.
A
C
C
A
A
E
So
I
think
I
can
maybe
help
on
this
one.
So
this
was
a
general
just
generally
available
information
that
if
a
project
needs
a
mailing
list
on
the
open,
JSF
org
domain,
that
I
am
certainly
happy
to
set
that
up,
not
a
problem
at
all
and
the
one
of
the
other
discussions
that
Joey
and
I
have
been.
Having
is
on
a
much
broader
sense.
You
know
where
should
we
be
having
our
were,
should
be
storing
and
maintaining
the
lists
of
people
who
should
be
on,
for
example,
maintainer
mailing
lists.
E
E
E
Gonna
say
separately,
if
we're
not
looking
for
mailing
lists,
if
we're
just
looking
for
an
alias
like,
for
example,
whatever
project
maintainer
x'
at
open,
JSS,
org
I
can
set
that
up
as
well.
That's
not
actually
a
mailing
list,
that's
just
an
alias,
for
that
is
also
something
we
can
set
up.
If
we're
just
looking
for
a
single
email
to
be
able
to
reach
all
the
maintainer
x'
on
a
project
that
the
dependency
there
is
a
needs
of
the
project,
so
tell
me
here
their
maintainer
czar
and
to
keep
this
lists
up
to
date.
So.
F
E
J
E
I
C
So
in
that
is
interesting,
so
basically
it
can
be
delegated
to
the
project
to
maintain
the
list,
because
I
know
like,
for
example,
in
the
node
project.
We
currently
maintain
those
in
our
own.
You
know
we
have
a
list
of
a
list
as
we
push
and
they
were
managed
through
through
github
versus
having
to
say,
ask
to
remove
or
add
people
that
kind
of
stuff
yeah.
E
So
I
think
it
depends
largely
what
interest
being
used
if
we're
using
the
group's
IO
infrastructure
I,
can
create
a
mailing
list
and
then
delegate
moderation
responsibilities
to
somebody
in
the
project.
So
then,
if
it's
you
know,
for
example,
if
it's
the
maintainer
slist,
that
might
be
an
invitation-only
list
in
case
there's,
discussions,
maintainer
x'
need
to
have
amongst
themselves,
but
at
the
same
time
the
maintainer
somebody
in
the
list
probably
would
want
to
maintain
it
themselves
to.
A
A
All
right,
excellent
moving
on
I
just
commented
I
will
now
close.
Let's
see
where's
my
tab.
The
next
agenda
item
is
ad
impact
and
consumers
of
the
project
new
project
templates
this
morning,
I
fixed
the
conflict
and
pings
miles.
He
added
his
plus-one.
He
said
it
looks
good
enough
and
they
can
iterate
on
it
later
if
need
be,
and
so
I
think
he
was
sort
of
the
only
lot.
The
last
one
we
were
looking
to
get.
You
know
who
looks
good
to
me.
Approval
from
the
previous
comments,
so
I
think
we're
good
to
merge
this.
A
A
Looking
at
the
board,
the
admin
policy-
Docs
I,
still
am
almost
done.
Work
amounts
in
progress
will
be
foundation,
infrastructure
and
rethink.
How
we
manage
it
is
in
progress
to
think
you
know
will
remain
for
now
until
we
make
further
progress
on
infrastructure
conversations,
and
then
there
are
the
three
items
that
are
waiting
on
the
board:
slash
foundation,
project,
practic
funding,
update,
moved
to
SF
CLA
BOTS
to
find
a
document
style
guide.
I
know
we
had
some
progress
on
some
of
those
things,
though,
is
there
any
sort
of
updater?
Should
we
be
closing
anything
I'm.
E
E
It's
having
a
standard
footer
that
has
links
to
these
documents
as
the
appropriate
notices
and
that
sort
of
thing,
so
just
so
that
everybody
knows
this
is
on
its
way.
We've
been
working
on
this,
getting
it
all
put
together,
so
that
it's
easy
for
projects
to
pick
up
and
drop
in
place
as
need
be
so
we're
getting
close
on.
It
just
have
to
get
a
few
more
documents
approved.
So.
E
There's
this
I
think
it's
I,
don't
know
that
I'm
qualified
to
answer
this
question
so
I.
You
know
it.
Certainly
it's
a
question
that
we
can
ask.
We
do
still
need
to
go
back
to
legal
with
this.
How
would
we
modify
it,
for
example,
for
a
project
that
just
uses
a
github
repo
as
its
homepage,
so
there
may
be
some
notices
that
we
should
put
there.
G
F
C
K
Correct
yeah
we've
got,
we
do
have
a
draft
plan
on
how
we
kind
of
scale
some
of
those
marketing
programs
for
the
projects
and
if
there
are
specific
questions
around
how
that
works,
things
haven't
been
100%
solidified
yet
but
I'm
working
with
Robin
to
to
get
those
done.
But
in
the
meantime,
if
there
are
things
that
are
interesting
that
are
happening
within
your
project,
please
reach
out,
because
you
know
I'm
happy
to
assist
and
you
know
amplify
all
the
great
things
that
are
going
on.
E
J
B
I
was
just
gonna.
Add
the
one
really
quick
way
to
get
that
support
and
lift
and
be
it
through,
Twitter
or
blog,
or
something
like
that
is
to
jump
in
the
PR
marketing
channel
in
slack
and
ping
and
Rachel
or
just
you
know,
pinging
at
here
there,
so
that
but
I
mean
usually
Rachel's
like
super
lightning,
fast,
retweets
and
stuff,
like
that.
E
C
A
A
Okay,
all
right
great,
so
yeah,
of
course,
let's
and
the
live
stream
thanks
folks
for
tuning
in
see
you
next
week.