►
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
Cool
looks
like
we're
good,
welcome
everybody
to
another
weekly,
open,
J's,
Foundation
cross-project
council
meeting
today
is
the
21st
of
January
I,
just
heard
from
Toby
he's
not
feeling
too
well.
So
you
won't
be
able
to
join
us
today,
but
we'll
check
in
with
him
soon
terms
of
that
and
progress.
There's
always
next
week,
right
cool.
B
Announcements,
yes,
so
we
have
opened
our
call
for
proposals
to
the
Open
Jazz
foundation
conference
in
June
that
was
open
on
Wednesday.
You
have
until
February
21st
to
get
your
your
proposals
in.
We
would
love
to
really
cast
a
far
and
wide
net
for
proposals
this
year.
So
please
do
share
and
tell
your
friends
and
make
sure
your
communities
are
aware
of
this,
because
I
think
it's
gonna
be
an
awesome
event.
B
The
other
thing
is
that
we
are
hoping
to
have
the
public
and
board
meeting
on
Friday
that
actual
the
the
calendar
open,
Jazz
foundation
calendar
has
that
meeting
data
in
it.
So
if
you
want
to
listen
in
to
the
public
version
of
the
board
meeting,
that's
going
to
be
on
Friday
I
want
to
also
say
a
big
thank
you
to
Tierney
and
Marshall
for
hooking
us
up
with
some
goodies
and
slack.
B
A
I
want
to
say
really
quickly
before
Ben
Mitchell
has
to
bail,
but
he
is
now
a
regular
member
on
the
cross
project
Council,
as
I
was
saying
earlier,
I'm
speaking
for
Ben,
because
he
he
thinks
as
one
of
his
children
took
his
headphones
and
and
is
that
allowed
coffee
shop.
So
he
can't
speak,
but
I
wanted
to
welcome
he's
merged
in
and
out
at
all,
the
lists
and
super
happy
to
have
him
getting
involved.
C
D
Yes,
so
Lennox
foundations
doing
a
brief
survey
of
our
projects
and
I'm
briefed
I
mean,
like
five
questions,
maybe
45
seconds
worth
of
work,
just
to
understand
a
little
more
about
what
various
folks
are
using
in
terms
of
unit
testing
and
other
testing
frameworks.
So
I
dropped
a
link
into
the
slack
on
the
info
channel.
If
you
would
be
willing
to
take
this
and
to
fill
out,
the
information
I
would
greatly
appreciate
it
again,
like
45
seconds
max
five
questions.
I.
A
A
D
Yeah
I
could
take
this
so
just
in
general,
the
board
is
looking
at
a
variety
of
things
like
Oh
2020
conference,
so
that's
obviously
coming
up
in
June
and
there's
some
discussions
around
some
of
the
logistics
and
so
forth
around
that
also
working
on
2020
budget.
We
had
some
preliminary
discussions
today
and
hopefully
we'll
have
further
discussions
on
Friday
about
getting
that
finalized
and
ready
to
go.
E
A
E
A
Thanks
for
mentioning
that,
I
wasn't
I
wasn't
sure
where
that's
done
cool,
so
we
can
jump
into
the
agenda
items
here.
The
first
one
is
issue
four,
four
five.
This
is
meta
where,
where
shall
certain
resources
live?
Jory
you
you
open.
This
up.
I
was
reading
through
it
earlier.
Do
you
want
to
give
some
context
within
chat,
yeah.
B
And
I
actually
also
were
spending
some
time.
Thinking
about
this
and
I'm
prior
to
the
meeting
where
this
came
from.
Is
this
interest
that
I
have
and
I
think
we
all
share
in
making
sure
that
our
onboarding
projects
and
our
existing
projects
have
access
to
all
of
the
information
about
things
that
the
foundation
can
can
do
to
support
it
like
from
the
inverse
of
infrastructure
of
menu
of
services
to
marketing
services?
B
You
know
that,
like
all
of
these
kinds
of
things,
and
it's
not
super
evident
where
one
would
go
to
find
that
so
the
question
of
my
mind
came
from
like
onboarding
new
projects.
Where
can
I
tell
them
hey,
you
know
if
you
need
further
info,
or
you
want
to
learn
a
little
bit
more
about
this
later,
because
I'm
brain
dumping,
a
bunch
of
stuff
at
you
right
now
go
check
out.
You
know
this
resource,
for
this
repository
or
or
whatever
and
I
also
started
thinking
about
how
that's
also
related,
just
generally
to
our
overall
information.
B
You
know
architecture
strategy
when
it
comes
to
managing
other
things
that
we
need
to
know
about
projects
such
as
you
know
where
their
project
charters
live
and
who
their
points
of
contact
are
and
like,
like
that
kind
of
thing
too,
because
it's
a
bit
of
a
two-way
thing.
So
not
that
I,
like
it
came
up
with
any
super
clever
solutions
to
that
yet
but
I
go.
This
is
a
rabbit
Bolin
falling
down.
Yeah.
A
I
mean
I
wonder
if
we
capture
some
of
the
things
that
we
would
expect
to
live
in
the
sort
of
repo
or
place
in
the
issue.
It
might
become
more
evident
because
I
think
project
resources
kind
of
make
sense,
but
then
it
starts
to
feel
like
project
guidance,
or
you
know
it
could
cover
a
variety
of
things.
So
I
wonder.
A
D
That's
right,
it's
a
pretty
common
practice
among
the
other
projects.
Basically,
it
just
provides
a
a
consistent
way
of
looking
for
certain
documents.
If
that's
what
you're
looking
for
I
mean
it's
one
way
or
another
doesn't
really
matter,
it's
not
gonna
break
anything.
If
something
helps
it's
just.
It's
a
lightly
used
convention.
D
D
It
could
be
a
place
to
hold
public
meeting
minutes,
for
example,
for
the
public
board
meetings,
which
you
know
CPC
repo
might
not
be
appropriate
for
that
it
could
be
used
for
documentation.
That's
specific
to
the
foundation
like,
for
example,
how
to
find
and
subscribe
to
the
members
mailing
lists
things
which
we
do
have
an
open,
JSF
org,
but
you
know
sometimes
it
helps
to
have
these
in
a
second
redundant
place.
So
it
really
would
be
for
foundation
specific
stuff
right.
E
D
For
for
things
like
that,
I
guess
that's
the
other
half
of
it
more
than
just
a
document
store.
It's
helpful
to
have
a
someplace
to
be
able
to
file
issues
that
would
be
separate
from
the
CPC
issues
mm-hmm
and
regardless
of
what
it
is.
You
know
whatever
it's
called
doesn't
particularly
matter,
but
this
would
be
an
appropriate
place
to
have
that
sort
of
bug
tracker
as
well.
E
B
A
A
All
right
cool:
well,
let's,
let's,
let's,
let's
kind
of
brainstorm
on
the
issue
and
see
what
what
that's
right
and
we
can
move
forward
from
there.
It's
a
good
question
cool
where
am
I
here
alright,
so
this
is
a
big
one.
The
next
one
is
the
starter
code
of
conduct.
Team
I,
don't
think,
there's
been
necessarily
a
lot
of
progress
here,
other
than.
B
Yes,
so,
following
our
conversation
after
last
CPC
meeting
I
sent
this
and
that
email
out
to
the
CPC
private
list
just
to
make
sure
we're
capturing
the
attention
of
CPC
members.
First,
two
to
weigh
in
on
that
problem
statement
that
Michael,
Dawson
and
I
think
also
Jordan
Harbin
and
myself
have
contributed
to
in
hakkim
D,
so
that
Hakim
D
link
is
on
the
issue.
So
you
should
be
able
to
click
on
the
issue
and
then
click
through
and
see
see
what
we've
come
up
with
so
far
or
just
refresher.
B
Our
objective
is
to
just
pull
together
a
group
of
people
who
want
to
finesse
that
problem
statement
and
to
a
point
where
the
CPC
is
comfortable
with
us
undertaking
that
scope
of
work
so
that
we
can
then
go
out
to
the
broader
community
and
draw
on
participants
to
actually
start
addressing
that
scope
of
work.
So
that's
essentially
where
we're
at.
We
need
to
reach
agreement
on
the
problem
statement
so
that
we
can
go.
B
A
F
A
E
G
A
Agreed-
and
we
can,
we
can-
you
know
iterate
on
this
and
get
some
work
going
and
then
how
folks,
who
are
experienced
or
have
more
context,
what
I'll
have
you
you
know,
comment
and
help
shape
as
we
go
along
cool
all
right
great.
We
won't
spend
much
time
on
that
then,
and
I'll
move
on
to
pull
requests
for
one
for
this
is
the
ad
foundation
wide
copyright
guidance
if
I
remember
correctly,
Brian
and
Toby
we're
gonna
get
together
on
this.
We
have
Brian
on
the
call
I'm
trying
to
scroll
to
the
bottom
here.
Yeah
we're.
D
D
A
A
E
Haven't
talked
to
a
mother
than
then
what's
in
the
issue
we,
you
know,
we
have
a
board
meeting
this
week.
So
it's
an
easy
time
to
do
it,
not
that
you
know
otherwise
we'll
do
it
three
mail.
What
it
really
needs,
though,
is
like
potentially
a
rebase,
but
more
than
that,
so
our
governance
says
we
need
like
half
the
voting
members
to
have
approved
it.
I
see
so
I
think
it's
that's.
That's
the
biggest
blocker
right
now
like
if
we
had
half
the
people
approving
it,
you
know.
E
E
A
E
To
take
get
to
the
board,
we
need
devoting
CPC
members
to
actually,
you
know
had
their
vote
because
that's
what
we've
got
I
mean
this
is
kind
of
a
gray
area.
Where
is
this?
Is
this
extending
the
governance
changing
extending
the
Charter
or
not,
but
we've
chosen
so
far
to
say:
let's
be
conservative,
so
I
guess
the
key
thing
that
the
key
ask
is:
can
the
voting
members
look
in-
and
you
know
maybe
say,
approve,
subject
to
rebase
or
whatever
mm-hmm.
A
A
A
E
F
E
A
A
B
A
Well,
we
can
move
on
then
or
actually
move
backwards,
I
suppose
Brian
did
you
happen
to
find
anything,
and
it's
just.
D
E
E
A
A
A
A
All
right
cool-
well,
maybe
you
know
when
that
is
found,
drop
it
into
the
issue
and
we
can
scope
it
out
and
you
know
continue
that
conversation
will
do.
Thank
you,
Brian
awesome.
Let's
see
so
next
move
COC
proposal
to
stage
three,
though
that's
blocked
on
432,
which
is
the
start,
a
code
of
conduct
team,
or
at
least
it's
waiting
on
it.
I'd
say,
but
so
we'll
do
that
we'll
jump
over
to
clarify
travel,
travel,
fund
status
and
process.
A
E
Of
that
one
one
is,
you
know,
is
the
budget
that
we
have
sufficient
and
miles
can
jump
into
here,
because
I
know
he
had
quite
a
few
quite
a
few
discussions
with
Te'o
and
so
forth.
The
other
one
is
around.
Who
get
who
approves?
There
seems
to
be
some
discussion,
starting
in
terms
of
direction
other
than
what
was
in
there,
which
was
the
CPC
doing
approvals.
So
we
should
probably
talk
about
each
of
those
separately.
Do
you
want
to
take.
F
So
we
read
the
budget,
we
had
a
Finance
Committee
meeting
for
the
board.
Today
we
were
reviewing
the
budget.
The
general
sentiment
in
the
group
was
that
we
used
half
the
budget
last
year
that
we
would
not
change
the
budget
and
having
double
the
budget
that
we
used
last
year
seemed
like
you
know,
a
prudent
first
step,
especially
when
we
try
to
keep
accurate
budgets,
but
it
was,
you
know,
pretty
widely
held.
No
one
objected
to
the
notion
that
if
we
needed
more,
that
more
would
become
available.
E
A
E
Just
on
the
point
miles
made,
is
it
sounded
like
you
know,
he'd
had
he
talked
to
Matteo
and
until
was
okay
with
that
suggestion.
Is
there
anybody
every
that?
Okay
with
everybody
here
as
well,
that
you
know
if
the
board
comes
back
with
statement
reflecting
what
miles
just
said,
you
know
we're
happy
that
that's
covered
I.
A
F
Honestly,
for
myself
and
I
don't
know
if
the
nude
project
would
be
okay
with
that,
like
there's,
no
reason
why
we
can't
take
an
iterative
approach
here
whereby,
like
we
solidify
the
CPC's
ability
of
having
a
budget
and
then
like
separately,
if
a
project
wants
to
have
its
own
budget
and
make
a
request
an
argument,
you
know
the
governance
to
support
that
I
personally
think
continuing
to
to
limit
the
fund
for
now,
like
I,
think
we
should
just
land
this
personally
and
iterate.
If
projects
would
like
to
see
their
own
specific
funds,
one.
D
Tool,
I
guess
we
call
it
which
includes
travel
fund
and
one
of
the
ways
that
this
works.
One
of
the
things
that
can
be
used
for
is,
if
you
have
a
project,
whether
it's
you
know
open,
Jas,
Foundation
as
a
whole.
Managing
a
big
bucket
of
funding
or
individual
projects
want
to
set
up
their
own
individual
funds.
You
can
receive
funding
not
just
from
the
board,
but
also
from
companies
who
want
to
contribute
directly
to
a
travel
fund
which
can
then
be
allocated
out
and
controlled
directed
by
the
project.
D
D
Be
approached
the
board
and
request
some
funding
to
go
into
it
or
approached
a
company,
that's
willing
to
support
the
project
directly
with
travel
funding,
so
there
are
definitely
ways
to
do
this.
We
have
the
tooling
to
support
that
use
case,
whether
it's
a
single
travel
fund
for
the
organization
or
this
there's
a
centralized
one
plus
you
know
one
or
two
projects
which
want
to
maintain
their
own
I.
C
E
Come
through
the
existing
channel,
no
III
guess
you
know
miles
point
of.
Can
we
get
this
landed
so
that
it's
clear
that
the
CPC
can
approve
travel
as
a
first
step
actually
makes
sense
to
me
and
then
you
know
basically
say:
okay,
all
projects.
You
know,
we've
got
this
Global
Fund.
We
will.
We
can
review
and
approve
requests
if
you
want
or
if
you
want
to
manage
your
own
for
an
event
or
whatever
else
has
proposed.
You
know
make
a
proposal
and
we'll
we'll
refine
from
where
we
are.
A
You
know
I
think
it
would
make
sense
to
have
some
sort
of
you
know
stamp
of
approval
from
the
project's
leadership.
You
know
steering
committee,
whatever
the
case
may
be,
so
maybe
we
can
squeeze
that
in
there,
but
I
think
I
agree
with
Myles.
We
should
we
should
just
get
this
sorted,
landed
and
iterate
from
there.
E
I
think
you
somebody
putting
in
that
comment,
Myles
or
somebody
to
basically
say
you
know,
yeah
the
suggestion
to
have
projects
do
approvals
themselves
make
sense,
but
can
we
treat
that
as
a
separate
extension
would
be
a
good
thing
to
get
in
there,
so
that
once
we
get
the
board
the
board
statement,
then
we've
got
everything
ready
to
say:
okay
yeah.
This
can
land.
A
Sounds
good
cool,
so
moving
on
the
next
item
is
responsible
security
disclosures
and
you
gotta
do
a
couple
of
repoed
jumps
here,
but
the
place
where
this
is
tracked,
I
believed
is
the
node.js
security
working
group
issue,
589
and
I.
Don't
know
if
there's
anything,
it's
a
report
here.
Michael
do
you
know
I.
A
E
The
issue
there's
a
couple
issues,
but
I
commented
in
one
issue.
Basically
saying
you
know:
do
you
need
anything
before
you
make
a
first
cut?
Nor
do
you
you
know,
or
do
you
want
to
take
a
first
cut
and
then
we'll
go
back
to
the
CPC
feedback
and
I?
Don't
I,
don't
remember
seeing
anything
they
said.
Hey
I
need
some
help.
First,
come.
A
E
A
Yeah
I'll
just
drop
a
comment
and
I'm
just
I'm
not
trying
to
be
pushy
and
stuff
if
I
can
be
helpful,
I'm
happy
to
be
cool
alright.
So
the
next
item
here
is
the
post
bootstrap
work
from
memory.
There
is
the
project
board
that
has
the
CLA
bot
and
I
think
e
CEO
issue
as
well
as
project
funding
issue
and
then
the
admin
policy
Docs.
As
I
mentioned
last
week,
I've
got
a
PR.
A
Rfp
are
open
for
the
admin
policy,
Docs
and
hopefully
we'll
get
that
done
soon
and
Mitchell
is
offered
to
help
me
get
that
over
the
finish
line,
but
I'm
not
sure
if
there's
anything
related
to
those
other
two
issues
around
TCO
CLA
or
the
project
plumbing
stuff
nodes
the
board
meeting
soon.
So
maybe
that's
you
know
next
week
we
can
check
in.
H
H
H
H
B
Was
realizing
I
was
talking
and
I
feel
like
it's
a
little
bit
of
a
catch-22,
because
some
of
the
projects
that
have
been
on
the
JSF
CLA
would
be
open
to
moving
to
something
else,
but
they
don't
understand
what
like
the
cost
of
conversion
is.
If
you
will,
you
know
like
what
what
overhead
might
they
have
to
incur
like?
Do
they
need
to
go,
get
everybody's
agreement
that
kind
of
stuff
so
I,
just
wonder
if
there
would
be
any
if
the
CLA
solution
is
to
sign
the
nine
I'm
curious.
D
H
D
B
D
Guess
I
would
also
ask
how
much
of
a
barrier
is
it
to
have
to
fill
out?
You
know
if
I
recall
correctly,
it's
like
five
fields,
something
like
that
and
I
understand.
The
process
is
different,
but
it
is
it.
Is
it
a
substantial
barrier?
Do
we
think,
as
opposed
to
the
typical
barrier
of
filling
out
a
CLA
I.
H
A
H
H
H
D
May
guess
the
flip
side
of
that
is
that
you
know
CLA
is
a
commitment.
You
know
it's
more
than
just
a
quick
through,
so
you
know
you
know
what
I'm
saying
like
it's
there.
There
are
some
reasons
that
you
know
the
person
would
want
to
sit
down
and
read
what
they're
doing
and
what
they're,
what
they're
agreeing
to
whether
the
whether
their
name,
first
name
and
last
name,
are
automatically
populated
or
not.
What's
really
important
is
the
content
of
the
document
itself,
so
I
mean
I,
think
I.
C
G
D
H
D
B
D
That
is
true
of
ez
CLA
as
well,
so
you
can.
If
you
have
an
organization
which
has
multiple
repos,
underneath
it
you
can
assign
one
or
more
clas
on
a
repo
by
repo
basis.
My
understanding
was
that
each
CLA
group
would
only
apply
to
a
single
organization
and
any
number
of
repos
within
that
organization.
I
wasn't
aware
that
it
could
be
apply
across
them
for
one
signature.
I
can
double-check
that,
though,.
E
H
I
could
be
misunderstanding.
The
interface
program,
but
from
what
I
saw
it
seemed
like
I,
could
have
hooked
up
well
any
of
the
orgs
that
I
actually
have
permission
to
hook
up
and
they
would've
all
been
under
that
same
group
using
the
same
CLA,
but
maybe
it
separates
them
by
org.
Behind
the
scenes.
I
don't
know.
H
D
D
A
H
A
A
H
A
A
So
that's
something
that
we
could
discuss
briefly
if
we'd
like
to
kind
of
see
if
the
admin
Doc's
that
I
was
bringing
over
I
believe
is
around
working
groups
or
is
it
working
group
requirements,
as
you
know,
laid
out
from
the
TSC
than
nodejs,
so
I'm
like
a
link,
at
least
there,
but
I
guess.
Maybe
that's
something
we'll
talk
about
next
week,
since
we
probably
have
about
16
seconds
discussing.