►
From YouTube: CPC Meeting - 2019-07-23
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
Jory's
not
on
so
I'm
sure
she'd
have
something
to
say
if
she
were,
if
you're
interested
in
her
announcements
and
updates
the
there's
an
email
list
that
you
can
find
and
I'm
going
to
kind
of
jump
into
the
agenda
items,
because
there
is
number
260,
it
is
creating
a
page
with
links
to
slack
channels
and
sign
up
linked
on
slack
as
well
as
mailing
lists
and
other
assorted
items,
so
jumping
right
into
the
agenda.
Brian.
Do
you
wanna,
listen
up.
A
C
C
B
D
C
New
I,
probably
fat-fingered
that
it
should
have
been
in
the
slack
channels
to
have
the
information
where
those
repos
are
in
a
pin
to
post.
So
basically,
what
I'm
saying
here
is
that,
for
you
know,
for
example,
the
the
standards
working
group,
it
probably
makes
sense
to
have
a
pinned
post
inside
that
slack
channel,
that
has
links
off
to
appropriate
repositories
and
things
like
that.
What
I
want
to
avoid
here
is
the
information
on
on
the
foundation.
One
like
getting
stale
and
I
also
want
to
avoid
myself
being
me.
You
know
the
gatekeeper
on
that.
C
D
A
D
More,
like
you
know,
a
one-line
description,
but
if
that's
really
easy
like,
if
you
basically
say
okay,
I've
connected
to
slack
and
I'll,
see
the
pin
things
that
you
suggested
automatically,
then
that
that
may
be
better
right,
I,
just
it's!
How
many
steps
would
it
take
to
get
to
them
was
my
only
concern
it.
C
Should
be
two
clicks
so
when
you,
when
you
connect
to
a
workspace
in
slack,
there's
the
channel
list
on
the
left,
there's
a
plus
button
I!
Believe:
oh
no
I'm!
Sorry!
That's
where
you
create
a
channel
joining
a
channel
click
on
channels
and
you
can
browse
to
whatever
public
channel
you
want
to
get
to
I.
Think.
A
I
think
maybe
the
question
is:
how
do
we
best
surface
the
most?
You
know
important
channels
and
I
think
that
you
can
I,
don't
know
about
slack
admin
too
much,
but
sometimes
I
go
into
a
channel
and
it's
suggest
channels
I
wonder
if
we
can.
You
know
when
someone
joins
the
org
and
they
go
to
their
first
channel
if
we
can
have
a
little
copy
that
says
you
know
these
are
some
of
the
most
important
channels
you
may
want
to
consider.
Yeah.
C
D
Might
be
we're
having
the
description
there,
it's
just
like
I,
looked
at
it
and
said:
okay,
there's
these
five
different
channels,
which
one
should
I
pay
attention
to
and
I.
You
know
I
could
guess,
but
it
I
think
like
a
paragraph
but
I
don't
want
to
have
to
like
click
on
each
one,
to
see
it's
kind
of
like
to
get
the
summary.
But
your
suggestion
of
having
that
in
the
general
channel
I
think
is
a
good
one.
Yeah.
C
E
E
D
B
I've
seen
select
channels
where
the
but,
like
I,
said
that
that
channel
selection
is
all
mixed
up.
So
you
get
like
you
know
like
the
fun
random
or
like
cat
pictures
channel
mixed
in
with
the
absolutely
critical
upcoming
meetings
channel,
and
it
turns
into
a
large
delusion
channels
and
it's
hard
to
figure
out
like
which
otherwise,
people
really
care
about.
B
But
another
I
think
we're
saying
I
think
there
might
be
a
feature
where
you
can
modify
the
slack
bot
like
the
default
slack
held
bot
to
give
you
like
an
intro
message
like
we're,
saying:
I
think
it
does
it
through
a
DM
or
it
does
it.
It
gives
you
like
a
hidden
message
in
the
general
channel
that
only
you
can
see
and
I
think
it
can
suggest
channels.
There.
A
C
How
about
in
the
meantime,
how
about
I,
just
kind
of
post
and
then
we'll
see
if
that
works?
And
then,
if
there
are
additional
features
that
we
want?
We
can
look
into
some
of
the
alternative
tools.
But
if
the
pinned
post
is
enough
with
some
summaries
that
you
know
they
can
be
updated,
as
as
new
groups
spin
up
and
and
you
know,
grow
active
slack
channels.
D
I'm,
plus
one
on
that,
because
I
think
that's
that's
just
it's!
It's
simple,
it's
kind
of
equivalent
to
having
them
listed
in
the
like
the
original
page,
but
just
a
more
effective
way
of
doing
that,
and
so
I
think
I,
just
a
long
way
of
saying,
plus
one
to
your
idea
of
like.
Let's
keep
it
simple
to
start
and
then
do
something
else.
If
we
think
we
need
to
okay.
B
A
Great,
so
do
we
do
we
have
this?
Do
we
consider
this
issue,
you
know,
result
and
can
close
it
and
remove
the
label
I.
A
All
right
moving
on,
unless
anyone
has
anything
else
to
add
cause
for
a
moment.
The
next
agenda
item.
My
favorite
agenda
item
is
issued
number
129
review
meeting
times.
I
think
that
this
is
good
to
go
for
now,
I
feel
like
we
should
close
this
issue
and
remove
the
label,
and-
and
you
know
we
want
to
make
any
tweaks
to
the
time.
You
know
another
issue
can
be
opened
and
or
from
their.
A
A
A
Yeah
I
know
these
things
take
time,
especially
looking
at
Council
and
one
indeed,
all
right,
cool,
we'll
check
back
on
that
next
week.
The
next
again.
Thank
you.
The
next
agenda
item
is
the
post
bootstrap
work
managed
by
CPC,
which
is
the
way
that
leads
us
to
the
project
board.
However,
I
wonder
if
we
should
jump
to
jewelry's
comment
yesterday,
which
highlights
a
few
issues,
they
aren't
on
the
agenda,
but
I
think
are
worth
going
over.
Does
anyone
object?
A
Sounds
good
great.
So
if
you
go
to
the
agenda
issue,
you'll
see
at
the
bottom.
Joey
has
a
few
quick
updates
here
and
I
can
read
them
out
for
folks
who
are
on
the
phone
or
what
have
you
and
then
I'll
also
add
that
she
mentions
that
Chris
Chris
Porter.
She
was
on.
The
call
can
also
give
some
context
and
answer
any
questions.
Perhaps
so.
A
The
first
item
here
is
issue
261,
and
she
says
there
appears
to
be
some
bug
or
issue
with
github,
preventing
me
from
committing
change
to
the
PR
and,
as
she
mentioned,
we
had
a
similar
issue
on
a
different
PR
that
that
I
was
trying
to
help
her
update
and
merge
in
so
the
the
issue
that
she
points
to
issue.
261
is
add
entry
point
for
projects
wanting
to
join
on
readme
and
review
project
progression.
A
A
The
next
item
she
has
here
in
her
comment
is
issued,
262
have
created
and
the
issue
she's
referencing
his
creation,
template
and
new
board
to
track
applications
to
join
the
foundation.
She's
created
a
project,
onboarding
issue
template
and
met
with
Chris
and
Chris
Borchers
and
Chris
Hillier
started
filling
out
the
South
for
architect
and
mocha,
though
perhaps
the
WebSphere
for
each
of
those
projects,
there's
a
new
project
board
and
she's
triage
some
stuff
into
it.
So
I
will
open
up
issue.
262
here,
Michael
created
this
last
week
from
our
discussions.
A
There
is
the
template
file
which
looks
like
it
was
already
merged
in
four
days
ago,
so
this
is
be
put
through.
It's
it's
a
github
issue
templates,
which
has
a
checklist
of
the
expectations
that
a
new
project
should
be
meeting
at
least
that's
the
bare
minimum
for
now
and
then
additional
to
that
is
the
project
board.
So
Chris
fortress.
Do
you
want
to
comment
at
all
on
these
items
here,
I.
E
D
The
only
one
I
wondered
about
on
that
one
was
the
last
one,
which
was
the
COC
escalation
path,
because
I
think
we
have
that
defined.
In
terms
of
the
external
view.
We
don't
necessarily
have
the
internal
view
like
once
somebody
reports
something
to
they
address.
We
may
we
still
need
to
figure
out
in
document
what
we're
gonna
do,
but
I
don't
know
that
the
projects
need
that
to
start
adopting
the
COC
and
integrating
with.
D
E
A
E
C
Yeah,
so
the
what
we
discussed
previously
was
putting
together
a
starter
charter
and
I
think
maybe
I
did
have
that
action.
I
do
apologize,
I
forgot
about
it
just
know
you
can
definitely
get
on
that
I
think
yeah.
In
terms
of
order
of
operations.
We
can
get
started
on
that
now.
It's
something
that
we'll
need
to.
Maybe
we
might
want
to
get
for
some
of
these
things
review,
possibly
from
from
legal
just
to
make
sure
that
we
have
everything
correct,
but
I
think
we
can
get
started
on
that
now
and
I'll.
E
E
D
It
was
that
either
there
was
some
confusion
over
whether
like
Brian
or
mike
boland
had
volunteered
to
doing
a
template,
or
if
that
wasn't
the
case,
then
she
would
just
create
a
template
based
on
the
node
charter
right,
but
I
think
it's.
The
key
thing
is
to
clarify:
maybe
an
answering
that
one
to
say:
yeah,
okay,
Brian's
gonna
create
a
template.
We
can
start
from
that
or
you
know,
maybe
you
know
create
one
from
the
node
charter,
but
it
sounds
like
Brian
was
volunteering
to
do
that
so
yep.
E
E
Don't
think
Michaels
for
me,
I
think.
For
the
most
part,
the
issue
template
seems
to
be
working,
Jory
and
I
went
through
it
and
it's
before
she
finalized
it.
It
seems
either
either
everything
we
want
is
covered
or
we
have
those
couple
of
outstanding
things
that
are
already
attracting
issues.
So
unless
anybody
has
other
questions
or
if
Chris
Hiller,
if
you
have
anything
to
add,
feel
free.
A
Great
well
well,
thank
you
both
all
of
you
and
just
to
kind
of
add
some
context
here
for
folks
who
are
following
along.
It's
great
that
architects
and
Milcah
to
projects
that
are
already
in
the
foundation
are
helping
us
dog
food.
This
this
process,
I
think
in
so
I
believe
that
that
covers
jewelry's
comments
here
and
the
many
issues
he
references.
If
anyone
has
any
more
to
add,
please
let
me
know
otherwise,
we
will
move
on
and
and
I'm
just
quickly,
jumping
over
to
the
project.
Onboarding
board.
E
C
C
So
that's
we
should
hopefully
have
this
reasonably
soon
right
now.
What
I
have
are
the
raw
documents
and
what
I
want
to
do
with
them
once
we've
gotten
agreement
from
everybody
is
that
the
raw
documents
are
what
they
should
be
turn
them
into
plain
language
that
we
can,
then
you
know
put
on
the
put
out
as
guidance
for
for
projects.
So
yes,
so
this
is
another
update.
Is
that
it's
in
progress?
There's
forward
motion
we're
not
quite
at
a
point
where
it's
makes
sense
to
give
a
comprehensive
update,
but
it's
coming
cool
thanks.
A
Yeah
great
well,
thank
you
and
thanks
for
bringing
that
up.
Chris
I
just
promoted
Manila
into
the
group
here
as
a
panelist,
and
so
maybe,
if
we
double
back
I,
just
posted
a
link
to
the
pull
request
into
the
chat
here.
This
is
pork
plus
number
271.
This
is
adding
the
process
for
handling
reports.
G
G
Yet
that's
in
a
section
near
the
end,
and
the
final
section
is
what
we
might
look
forward
to
that
we
can
incorporate
into
our
process.
There
are
two
possible
projects
that
are
in
flight
that
are
not
exactly
related,
they're,
quite
tangential,
to
open
Jess,
but
we
would
be
able
to
bring
in
some
of
their
findings
and
some
of
their
process
once
they
put
some
material
out
there.
D
D
G
Thanks
for
pointing
that
out,
Michael
this
definitely
needs
to
be
integrated,
I
think
so
for
the
code
of
conduct
it
seems
like
that
is
well.
If
we
think
of
the
code
of
conduct
as
the
rules
that
we
are
following,
then
the
report
handling
process
is
the
process
by
which
we
enforce
those
rules.
Yes,
exactly.
D
So
that
yeah
I
saw
I
was
kind
of
thinking,
as
the
second
dog
should
be.
Here's
how
we're
implementing
what
we've
said
is
the
external
view
of
it.
I
say
like
once:
we
receive
something
on
COC
escalation
at
and
I
see
that
we
have
to
do
a
PR
to
update
to
the
that
to
have
the
right.
You
know
foundation
org,
but
then
it's
like
when
something
comes
into
that
what
gets
kicked
off
off
right.
G
D
D
Think
that
the
separation
I
would
see
is
the
foundation
code
of
conduct
like
that's
the
governor
conduct
requirements
like
that
one
I
could
see
being
like
here's,
how
it
explains
how
it
works
to
annex
somebody
outside
and
then
the
other
one
would
be
like.
Okay
and
here's
how
we're
gonna
handle
things
that
are
reported
through
that
external
view.
D
E
D
A
D
D
G
D
D
G
G
Michael
you're
listed
as
the
champion
for
this
particular
proposal.
Would
you
be
okay
with
what
we've
discussed
so
far?
Absolutely
then
I
can
take
the
action
to
implement
whatever
we've
discussed,
bring
that
into
this
and
extract
whatever
relevant
sections.
There
are
into
the
read
me
and
tie
them
together.
A
Excellent,
so
moving
on
the
last
agenda
item
is
basically
to
go
over
the
post,
bootstrap
housekeeping
project
board,
which
I
will
post
again
in
the
into
the
chats
and
we've
been
making
great
progress
on
this
board
recently
having
been
going
through
it.
So
I
will
just
go
through
the
list
of
things,
starting
with
the
in
progress
column.
Here.
A
B
A
B
There
is
a
pull
request
set
up
for
this
stage,
0
proposal
for
moving
the
current
nodejs
and
compound
travel
fund
into
the
Jas
Oregon
target,
so
I'm
on
mobile
right
now.
So
if
someone
else
could
post
that
PR
into
the
chat
for
me,
that'd
be
great,
but
it
should
be
really
referenced
in
the
issue
at
this
point.
B
Yeah,
so
I
put
it
up
a
couple
days
ago,
there's
already
been
some
small
amount
of
of
comment
just
changing.
You
know
some
of
answering
some
of
the
questions
changing
just
being
clarifying
some
of
the
language
and
what
the
intention
is.
One
of
the
issues
is
basically
because
people
are
very
sensitive
as
to
how
the
current
TSC
and
Kham
Kham
members
might
have
opinions
to
react
to
this.
Definitely
we
want
to
garner
like
as
much
feedback
as
we
can
early
in
the
assess,
so
I
think
I've
been
asking
if
I
should
mention
specific
people.
B
It
looks
like
the
recommendation
is
to
add
mentioned
both
of
those
teams
which
github
you
can
I
do
from
inside
that
board.
So
I
was
thinking
of
creating
an
issue
in
the
admin
repo
that
talks
about
the
travel
fund
and
managing
those
teams
and
adding
the
link
to
this
proposal,
and
my
question
for
today's
meeting
would
be.
A
Think
that's
a
very
good
question
to
me.
It
feels
like
we
could
wait
until
stage
zero
and
then
ping
the
admin,
an
admin
issue
and
then
perhaps
folks
from
the
different,
the
compound
and
TSC,
the
two
two
groups
that
we
want
to
make
sure
this
is
clearly
surfaced.
You
can
mention
it
in
their
upcoming
meetings.
As
you
know,
an
additional
kind
of
thing.
B
B
A
D
Thinking
like
it,
you
know
it
definitely
needs
to
get
buy-in
from
you
know
or
like
we
need
to
raise
awareness
in
the
TAC
in
calm,
calm
before
it
moves
to
stage.
Three
I
was
just
thinking
what
my
preference
would
be
in
terms
of
you
know
now
versus
later
I.
Don't
you
know,
I,
don't
object
to
like
moving
to
stage
zero
and
then
doing
notification,
but
I
also
don't
know
you
know
it's
not
so
complicated
or
so
long
that
you
know
that
it
would
hurt
that
much
if
we
actually
just
did
the
FYI
now
as
well.
D
D
D
You
know
sometimes
I
can
see.
There's
some
value
in
terms
of
you
know
the
the
CPC
working
through
the
issue
and
clarifying
things
and
all
that,
but
I
just
don't
know
that
there's
going
to
be
enough
for
that
that
it's
and
to
prevent
us
from
just
saying
yeah,
let's
not
mention
the
TSC
and
come
come
now
and
often
earlier,
is
better
than
later
right.
That's.
A
Yeah,
my
my
only
thinking
was
get
get
some
of
these
basic
people's
kind
of
fleshed
out
and
then
almost
have
it
be.
Something
of
you
know,
proposals
not
a
great
word,
but
at
least
like
it's
a
little
more
clear
for
people
just
just
coming
at
it
and
looking
at
other
than
having
to
parse
through
what
state
of
saying
and
more
questions
are
open
and
things
like
that.
How
about.
B
After
we
get
the
next
couple
of
questions,
I'll
settle
and
there's
no
activity
for
a
couple
days.
I
can
rebase
all
of
the
commits
and
revisions
into
a
single
commit
and
then
send
as
a
new
PR
basic
closing
the
current
one,
opening
the
new
one
with
basically
the
same
starting
comments
and
the
same.
You
know
from
the
same
branch,
but
then
we
can
start
a
fresh
conversation.
D
A
Yeah
I
agree
and
then
I'll
just
comment
on
your
previous
question.
To
me.
That
seems
like
it's
a
general
pull
request
and
it's
not
clear
in
terms
of
a
proposal
process,
but
the
requirements.
The
conditions
for
that
are
no
outstanding
objections
to
approvals
by
CPC
members
and
the
PR
has
been
open
for
at
least
72
hours.
D
Clarify
that
you
know,
if
we
want
to
leave
that
as
our
you
know,
for
all
stages
or
but
first
not
to
say,
we
should
do
anything
different,
I
think
for
stage
0.
That's
perfectly
fine,
I,
just
wonder
if,
like
for
stage
3,
we
should
have
some
where
it's
like.
Well,
no,
if
it
needs
a
board
review,
then
or
or
CP
anyway.
A
A
A
All
right
cool,
so
then
the
plan
for
this
then,
is
to
work
through
the
questions.
You
know
secure
some
some
approvals
and
it's
been
open
a
little
bit
amongst
a
few
hours.
We
can,
they
can
merge,
merge
it
in
and
go
from.
There
alerts
the
TSE
and
calm,
calm
and
I'll
be
sure
to
plan
its
1
1
x,
medium
as
well,
and.
D
A
A
D
A
A
D
E
A
E
A
A
Great
and
then
the
last
one
in
this
list
is
the
document
and
define
initial
process
for
handing
reports,
which
we
discussed
the
proposal
process
that
the
PR
that
Manila
has
opened
and
we'll
work
through
the
proposal
process
on
adding
it
to
the
COC
stage.
One
proposal
great
moving
over
to
the
to
do
column
here
improve
governance
for
regular
members
miles
open
this
six
days
ago.
The
comment
here
is:
we
likely
want
to
draft
better
governance
for
on-boarding
and
off-boarding
regular
members.
How
long
does
this
TR
need
to
be
open?
A
A
D
F
A
D
So
far
like
what
I've
tried
to
do
is
either
add
into
the
PR
like
for
tyranny,
I
added
into
the
PR
that
you
know
we
know
he's
part
of
the
project
of
no
project,
so
I
added
that
in
and
for
somebody
else,
I
just
asked
that
they
add
that
in
beyond
that,
I
think
we
said,
we'd
notify
the
projects.
That's
our
probably
our
one
exposure,
but
we
can
probably
do
that
once
we
get
it
to
find
and
and
notify
all
the
projects
right.
A
A
Though,
all
right
great
welcome,
Trini
who's
on
the
tc39
news,
great
so
moving
on,
then.
The
next
item,
in
the
to-do
column
here
is
asked
projects
to
start
updating
references
to
Docs
in
the
CPC
Depot,
for
example
the
COCs
etc.
Michael
you
opened
this.
Would
you
like
to
comment
or
that
context,
yeah.
D
I
think,
last
time
we
talked
about
it,
maybe
being
a
little
bit
premature
and
the
next
step
was
to
get
the
projects
that
had
volunteered
to
start
going
through
the
list
which
is
taking
place
so
I
think.
Maybe
we
need
to
give
a
little
more
time
for
that
process
to
complete
and
then
once
we're
happy
there
see
if
there's
anything
that
needs
to
be
tweaked
before
we
go
back
and
ask
like,
do
the
more
of
a
bulk
asked
all
the
projects
that.
A
Make
sense,
I,
wonder
Chris
and
Chris
workers
and
hillier
if
in
going
through
this
process,
do
we
expect
all
of
the
projects
that
are
already
in
the
foundation
to
also
dog
through
this
process,
or
are
we
trying
to
identify
things
that
are
you
know,
requirements
that
we
need
to
double
back
on
for
existing
projects?
Is
that
something
you
discussed?
I.
A
D
A
Yeah,
either
way
it's
fine
I
think,
once
we
figure
out
what
what
the
process
is
and
then
we
know
how
we're
going
to
take
the
projects
to
you
they're
more
work
through
it,
so
we
can
leave
it
as
is
for
now
and
touch
one
of
those
we,
as
we
have
our
weekly
meetings,
so
great
moving
on
then
review
foundation
infrastructure
and
we
think
how
we
manage
it.
We
talked
about
this
briefly
last
week
with
you
know,
Myles
when
he
was
on
the
call
and
I
think.
As
he
said
last
week,
we
continue
to
be.
A
D
E
A
I
wonder
if
we
should
that
this
should
be
changed
to
like
capture
foundation,
infrastructure
from
from
the
node
side
and
the
gas
side
and
at
least
have
a
place
where
it's
all
surfaced,
because
some
people
might
have
you
know,
needs
but
not
realize.
Oh
well,
there's
this
other
bit
of
infrastructure.
That
would
help
us
in
this
other
way.
D
D
A
C
Yeah
so
where
we
landed
on
this
was
this
is
a
very
complicated
topic
and
it's
something
which
is
being
actively
discussed
at
the
board
level.
There's
probably
not
much
that
they
just
specie
level
just
yet,
because
it
is
fairly
there's
some
hefty
policy
considerations
that
come
along
with
this,
so
I
mean
for
now,
I
see
just
tabeling
it,
that's
probably
the
most
effective
use
of
it
and
then
it'll
be
it'll,
be
revisited
soon
enough.
I
think.
D
What
would
be
useful
is
a
comment
that
says
something
like
you
know,
hey
this
like
what
you
said
this
being
looked
at
by
the
board,
and
you
know
we
should
revisit
this
in
like
whenever
you
think
the
board
may
have
something
you
know
is
in
September
or
October
or
whatever
one
just
so
that
if
somebody
looks
at
this
says,
okay
I
understand
the
next
step.
It's
on
basically
we're
waiting
for
whatever
the
board's
working
on
and
we
think
that'll
be
ready
around
this
timeframe.
C
C
D
A
Right
well,
I!
Guess,
if
you,
if
you
have
a
some
sort
of
comment
to
that
issue,
that
would
be
helpful.
I,
even
wonder
if
we
should
have
like
a
label
for
things
that
are,
you
know,
sitting
with
the
board
and
we'll
wait
until
we
hear
from
them
or
if
we
should
have
another
column.
That
is
like
kind
of
waiting
on
the
board.
I
I.
A
Okay,
I,
don't
know
if
it's
Brian,
that's
cutting
out
or
if
it's
me
but
I
think
I
got
what
you're
saying
do
we
think
we
should
have
a
label
or
a
column
or
both
I
like.