►
From YouTube: OpenJS Foundation CPC Meeting 2019-11-12
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
Should
be
going
live
in,
come
on
sorry,
let's
take
a
minute.
Sometimes
there
we
go,
we
should
be
live
all
right.
Welcome
everybody
to
this
Tuesday
November,
the
twelfth
edition
of
the
Open
Jazz
foundation,
cross
project,
Council
meeting
I'm,
your
host
jory
Burson.
Today,
standing
in
for
Josephine
as
we
get
started.
Let
me
ask
the
group:
are
there
any
announcements
we
would
like
to
share
with
our
community
today?
A
Usually,
that's
me,
chiming
in
with
100
things,
okay,
hearing,
none
I'll
just
make
one
more
pitch
that
we're
moving
into
collab
summit,
slash
nodejs,
Interactive
crunch
time.
So
do
please
submit
your
proposals
for
the
summit
or
for
the
community
corner
and
get
your
tickets
interactive,
because
we'd
love
to
see
you
there
all
right.
First
issue
of
the
day
is
issue
number
398,
onboarding
medic
questions.
A
Nope,
okay,
then
the
other
issue
was
on
where
things
should
live
over
the
on
onboarding
topic.
Should
they
be
moved
to
that
onboarding,
Rico
or
just
the
issue
specific
I
think
Toby
was
okay
and
Michael.
We're
raising
some
good
points.
It
seems
like
what
we
need
to
do
is
document
this
practice
of
perhaps
anything
being
specific
or
meeting
specific
CPC
interaction
to
put
that
in
the
onboarding
repot
repository.
But
if
stuff
this
stuff,
that's
more
specific
to
individual
projects
would
be
fine
to
live
on
those
and
within
the
project
repositories.
A
A
B
The
work
I'm
doing
then
this
other
issue
I,
think
it's
400
and
there's
a
question
of
like
basically
how
sort
of
like
in
general
this
whole
the
whole
onboarding
process
should
happen
from
a
perspective
of
like
communication
channels.
How
do
you
get
people
to
how'd
you
get
the
foundation
staff
to
you
involve
was
a
particular
issue.
How
do
you
get
the
CPC
team
over
this
particular
issue
and
and
I?
B
A
Think
that's
a
really
good
point
related
to
to
access
like
if,
if
certain
folks
foundation,
staff
or
CPC
members
need
to
be
interacting
with
projects
on
say,
you
know
the
CLA
or
D
Co
implementation,
or
something
like
that,
getting
them
access
to
repositories
for
just
the
single
purpose
is
probably
not
the
pattern
we
want
to
promote.
So
perhaps
thinking
about
it
from
this
pattern
from
that
pattern,
perspective
is
the
right
approach,
so
they
it's
very
good
feedback
to
me.
A
And
I
agree:
it's
related
to
number
400
so
to
move
this
forward.
I
think
this
is
one
of
the
things
that
perhaps
Brian
and
myself-
and
you
can
chat
about
also
later
this
afternoon.
If
we
get
a
chance
as
well,
okay,
cuz
I,
think.
Maybe
what
needs
to
happen
is
we
can
and
workshop
this
and
then
have
a
proposal
for
the
rest
of
the
org
yeah
I.
Think.
A
A
A
So
no,
he
did
not
I
do
think.
Probably
the
next
step
here
is
just
that.
We
want
more
input
from
the
broader
CPC
on
what
sessions
the
CPC
ought
to
run
and
whether
there
are
individuals
from
the
CPC
who
would
like
to
lead
sessions
at
collab
summit.
I
know
sindelle
is
interested
in
leading
the
session
for
for
the
standards
working
group,
and
so
please
do
weigh
in
on
that
issue.
If
you
want
to
help
organize,
they
see
pcs
presents
they're.
A
A
D
A
B
A
B
E
B
So
I'm
just
wondering
if
that's
the
plan
of
to
wait
for
this
or
if
there's
like
another
plan
or
so
maybe
having
the
minutes,
would
be
great
I.
Don't
think
that
we
have
to
talk
about
the
whole
thing,
but
maybe
having
the
minutes
and
just
like
if
there
were,
you
know
if
there's
a
plan
B-
and
this
is
not
the
pallino
if
like
this,
is
plainly
and
there's
a
plan,
B,
that's
sort.
A
A
I
just
dropped
in
the
chats.
A
link
to
those
notes
and
tyranny
was
us
on
the
call.
So
he
can
hopefully
chime
in
and
correct
me
if
I'm
wrong,
but
the
intention
was
or
the
discussion
was
about
sort
of
improving
the
upstream
CEO,
see
if
possible
and
if
that
is
not
possible
to
incorporate
changes
on
our
version
of
it.
But
like
kind
of
been
that
sort
of
spirit
of
open
source,
submitting
the
the
changes
we'd
like
to
see
upstream
and
see
if
there
would,
if
there's
a
chance
for
getting
that
landed,
yep.
C
A
C
Basically,
during
that
meeting
we
were
discussing
the
reasoning
for
having
links
to
the
COC
rather
than
actually
committing
it
and
in
that
meeting
I
during
that
I
just
created
an
issue
saying
he'd
be
nice.
If
we
had
like
translations
available
in
the
actual
course,
UFC
and
Coraline
had
responded
very
fast,
and
you
know
suggested
that
yeah,
that's
you
know
well,
she
seemed
open
to
her.
They
seemed
open
to
it
and.
A
C
C
C
Because,
like
as
a
member
of
the
node
moderation
team,
that
is
something
that's
like
relatively
important
for
me
to
know
and
for
the
other
members
you
know,
especially
given
the
you
know,
given
that
there's
32
projects
that
all
have
theoretically
agreed
to
this
to
conduct
and
a
week
may
or
may
not
be
enough
time
to
kind
of
alert
them
of
that.
So.
A
Okay,
so
I
see
see
your
what
you're
saying
so
right
now
we
have
a
floor
request
into
the
upstream
code
of
conduct
that
we
are
consuming,
and
so
whether
coralline
merges
that
in
or
not
is
not
really
something
that
we
can
necessarily
control
right
either
way.
We
do
need
to
let
the
project
communities
know
that
these
are
revisions
that
we're
we're
planning
to
take,
whether
they
land
in
the
contributor
covenant
or
whether
they
end
up
landing
in
our
version
of
it.
Yeah.
C
A
For
just
you
know,
heads
up
and
and
also
review
I
think
that's
something
worth
sending
out
also
in
our
weekly
project
email,
just
to
make
sure
that
if
anybody
has
concerns
with
these
changes,
although
I
it
doesn't
seem
like
they
will,
but
you
know:
Never
Say
Never.
You
know
that
at
least
they're
weighing
in
on
that
early.
But
but
I
take
your
point
that
we
need
to
yeah.
Let
folks
know
that.
A
C
A
C
More
more
kind
of
what
I'm
trying
to
poke
at
because,
like
I
know,
if
I
had
my
own
project
that
was
like
in
the
foundation
which
I
know
there
are
a
few
people
who
own
a
project
and
then
all
of
a
sudden.
This
CSU
is
change
out
from
under
me.
After
having
the
message
and
they're
not
saying
like
maliciously,
but
just
like
the
COC
was
changed,
I
was
not
able
to
have
you
know
time
in
a
week
or
two
to
review
it
I'd
want
to
know
so
like.
A
This
is
a
good
point
and
it
just
speaks
to
a
longer-term
system
that
needs
to
be
developed.
Where
you
know
we
have
a.
We
have
like
a
process
or
a
protocol
and
when
a
change
is
being
suggested
to
the
code
of
conduct
that
we
have
like
a
webinar
or
some
sort
of
discussion
for
projects
to
be
able
to
interpret
those
changes
and
that
kind
of
thing
so
yeah
cool,
yeah.
C
A
A
Okay,
good
good
points
and
good
questions.
So
let
me
I'll
I'll,
take
the
action
item
to
make
sure
that
message
goes
out
about
these
changes
being
considered
to
the
projects.
Tierney's
gonna
talk
to
the
moderation
team
for
node
and
we're
gonna,
try
and
see
get
a
better
assessment
of
the
likelihood
of
these
changes
being
incorporated
in
the
upstream
contributor
covenant,
yeah
and.
B
A
A
A
Tooling,
like
any
tooling
suggestions,
the
last
update
that
we
had
on
this
last
week
was
that
we
have
the
the
public
onboarding
repository
and
we
were
looking
to
create
a
private
repository
for
tracking
applications,
but
I.
Don't
think
that
can't
I
don't
actually
know
why
we
don't.
We
can't
have
a
private
repository,
Brian,
Warner,
probably
knows
and
I
think
I
I.
B
A
I
believe
we
have
that
capacity
now,
because
okay,
Brian
and
I
are
collaborating
on
a
repository
for
the
for
the
brand
and
artwork
for
projects,
and
that
is
more
private,
so
I
think
we
have
that
now
so
I'll
just
check
in
with
him.
He
had
to
drop
for
reasons,
but
if
that's,
if
I
can
just
create
that
private
repository
first
and
this
issue
may
be
able
to
be
closed.
A
A
A
C
A
E
A
Let
me
see
hold
on.
Let
me
go
super
here
waiting
at
new
zoom,
so
we
currently
have
a
zoom
account
and
a
YouTube
account
that
are
open,
Jas,
Foundation,
specific,
so
I
think
those
are
just
should
be
checked
off.
We
do
have
a
process
that
needs
to
be
documented
for
projects
who
want
their
own
project
specific
zoom
accounts,
but
the
foundation
itself
does
have
a
zoom
and
YouTube
already
set
up
for
open
beta
yeah.
So.
A
I'm,
realizing
that
this
issue
is
being
tagged
as
this
post
bootstrap
work
issues
is
what's
getting
tagged
in
the
agenda,
but
the
the
thing
we
should
really
be
looking
at,
because
it's
the
most
up
to
date
is
this
post
bootstrap
housekeeping
board,
which
object
and
to
the
chat,
really
quick,
and
this
is
really
keeping
track
of
the
the
open
issues
that
we
had
tagged
but
I
think
it's
worth
going
back
through
that
checklist
really
quick
to
Evan.
Thank
you
for
for
that
yeah.
A
So,
okay,
so
on
the
board
anyway,
on
the
project
board,
which
I
guess
we'll
start
with
that,
because
there's
fewer
things
on
it
again,
these
things
that
are
tagged
waiting
on
board.
Unfortunately,
the
representatives
CBC
representatives
who
have
been
reporting
on
those
issues
aren't
here
today,
so
unfortunately,
we
will
miss
out
on
an
update
this
week.
So
it's
moving
over
to
the
in
progress.
A
We
have
two
open
issues,
one
the
first
one
is
add
admin
policy
Docs,
and
this
is
something
that
Joe
was
working
on
and
I'm,
not
sure
where
he's
at
on
that
I
did.
I
did
assign
this
issue
to
him
earlier.
It
was
just
been
so
that's
been
at
least
assigned
I
I
would
assume
that
Joe
and
Ben
would
appreciate
help
on
this.
It
seems
like
a
largely
administer
Teva
type
task,
so
if
somebody
wants
to
volunteer
to
just
help,
get
that
done.
A
This
issue
is,
as
actually
related
to
a
few
other
of
the
live
ones.
We
have
a
issue
number
333,
which
includes
a
link
to
the
draft
in
for
services,
requests
to
get
everybody's
feedback
on
sort
of
those
minimum
services
that
we
want
the
foundation
to
to
adopt
I'm
actually
going
to
go.
Click
in
there,
cuz
haven't
seen
and
there's
been
some
some
feedback
that
needs
to
be
incorporated.
A
A
E
The
first,
the
first
ad
in
policy
dogs,
it's
as
far
as
I'm
concerned,
it's
really
tied
up
to
working
group,
so
somebody
that
has
like
at
least
part
of
the
working
group
worked
out.
People
have
been
involved
in,
so
it's
probably
better
that
these
people
are
dealing
that
I
could
say,
I'm
more
experienced
in
that
field.
A
A
There
is
the
bullet
with
the
check
marks
and
Evan
pointed
out
that
some
of
these
things
are
probably
done
so
ask
projects
to
start
updating
references
to
Docs
in
admin
repo,
so
that
is
an
issue
that
I'm
that
I
think
should
probably
just
move
on
over
to
onboarding,
because
this
is
an
on
board.
That's
an
onboarding
task.
A
A
E
A
A
A
A
A
All
right,
cool,
so
I
think
then
we
have
just
managed
to
check
off
a
couple
of
things
and
I
think
we
can
check
off
a
couple
more,
but
I
want
to
make
sure
that
others
agree
that
those
were
were
completed
there.
So
I
think
I
think
we're
nearly
done
with
that.
With
that
checklist
we
have
gone
through
the
pro
the
post
bootstrap
board.
A
B
A
B
B
That
does
imply
that
the
CPC
have
a
vote
before
then
and
I
don't
know
what
the
process
for
that
is
know
what
time
is
needed
and
I'm
just
trying
to
work
back
from
this
date
to
even
decide
whether
that
data
is
reasonable,
or
not
my
belief
as
increasingly
that
that
date
is
not
reasonable.
In
the
conversation
we
had
about,
the
CRC
before
tends
to
you
know,
push
me
further
in
that
direction,
and
so
I,
just
wanna
I
wouldn't
have
I
would
like
to
have
an
idea
of
what
this
actually
implies
on
the
CPC
side.
A
A
A
A
Because
that's
essentially,
where
we're
at
right
now
we're
working
with
and
specifically
where
we're
going
through
the
process
of
adhering
to
the
onboarding
checklist.
That's
the
stage
that
we're
at
right
now
and
then
step
eight.
The
presentation
for
final
acceptance
and
two-thirds
supermajority
vote
is
is
the
last
piece
that
doesn't
probably
give
us
the
level
of
detail
that
we're
looking
for.
Does
it
Toby
I?
Don't.
B
A
A
B
B
A
A
B
A
Well,
I,
couldn't
you
know,
say
on
behalf
of
the
CPC,
but
I
could
say
personally
I
think
that's
that's
that
feels
accurate.
It
will.
It
probably
will
it
may
or
may
come
together
on
the
10th,
but
the
probability-wise
is
no.
Unless
unless
we
come
back
and
we
get
all
of
these
questions
that
are
still
at
the
waiting
on
board
approval
to
come
back
and
we
get
you
know
significant
movement
on
the
COC
piece
really
quickly,
but
odds
are
not
like,
like
great
I.
B
There
was
a
document
describing
infrastructure
changes
that
were
going
to
be
made
to
the
EM
project,
to
disentangle
the
hosting
on
the
CDN
of
the
runtime
from
the
Google
amp
cache
and
I
mean
this
is
like
a
fairly
involved.
Technical
conversation
was
lots
of
decisions
to
be
made,
but
I
think
it's
important
that
there
is
a
direct
line
of
communication
between
folks
on
the
CPC
they're
going
to
approve
of
this
plan
and
the
people
actually
writing
the
plan.
A
A
A
B
A
A
Okay,
those
are
good
issues,
I'm,
sorry,
they
didn't
get
generated
by
the
agenda
tool.
I
think
Michael
ran
it
did
yesterday
or
something
so,
but
next
week
they
will
be
captured
in
the
agenda.
So
I
guess
that's
a
good
reminder
to
anybody
who
has
an
issue
that
they'd
like
to
see
us
address.
Please
feel
free
to
to
file
that
and
add
the
cross
project
council
agenda
tag
to
make
sure
that
we
we
take
it
up.
I
have.
E
A
question
regarding
the
communication
channel,
actually
so
Bryan
Warner.
He
suggested
that
we
started
with
the
stock.
Tyonne.
I
also
think
that
starting
the
slack
channel
is
good
to
set
up
an
agreement
between
parties
on
how
to
communicate
and
how
format
should
be,
and
then
maybe
a
mailing
list
would
be
better
in
terms
of
this
is
a
separate
like
a
separate
concern,
whereas
you
also
have
a
clear
boundary
of
of
the
two
parties.
E
E
B
I
mean
the
main
reason
they're
actually
brought
up.
The
mailing
list
thing
was
that
all
of
the
communications
during
the
application
process
was
the
CPC
was
done
through
a
mailing
list,
and
so
I
assumed
that
this
was
the
preferred
communication
channel
in
general
of
the
CPC
and
I
know
that
folks,
on
the
CPC
have
a
lot
on
their
plate
and
I'm
not
really
necessarily
focused
on
all
the
things
and
so
making
it
as
easy
and
frictionless
for
them.
We
put
on
that
conversation
I
think,
is
what
I'm
trying
to
achieve.
A
B
A
A
Okay,
well
we'll
try
and
get
that
that
feedback
collected
from
CPC
members
quickly.
So
we
can.
We
can
start
organizing
on
this
particular
issue
because
because
Toby
Toby
spoil
in
and
we
want
to
make
sure
they're
the
right
folks
are
participating.
We
are
right
at
the
top
of
the
hour,
so
respecting
everyone's
time
unless
there's
any
last-minute
or
announcements
or
anything
like
that,
and
they
just
say:
let's,
let's
close
I
actually.