►
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
B
A
few
and
announcements
that
will
also
be
coming
out
in
the
project
email
tomorrow,
but-
and
this
is
super
exciting-
the
call
for
proposals
for
our
event
in
June
tomorrow,
and
so
that
be
on
the
lookout
for
that
link
and
start
thinking
about
your
talk,
ideas
and
tell
your
friends,
of
course.
Along
with
that,
we've
argued
about
the
sponsorship
perspective,
but
perspectives
put
together
so
be
thinking
about
whether
you
or
your
company
would
be
interested
in
supporting
the
the
event.
That
would
be
great,
there's
a
lot
of
cool
opportunities,
other
good.
B
A
Great
cool,
thank
you
for
for
sharing
all
of
that
information
and
updating
and
yeah
I
agree.
I
started
to
draft
a
message
to
the
slack
channel.
Any
public
meetings
that
get
on
the
calendar
would
be
great,
I
subscribe
to
the
calendar
and
get
alerts,
and
it's
nice
to
be
able
to
pop
into
things
and
just
be
aware
of.
What's
going
on,
definitely
cool
what
else?
There's
there's
a
standards
meeting
today
at
2:00
p.m.
B
C
A
That's
one
of
the
few
that
are
on
the
calendar.
It
looks
like
the
board
meeting
the
CPC
and
the
standards
meetings
are
the
ones
that
are
on
the
calendar.
We
should
make
sure
which,
by
the
way,
is
calendar,
dot,
open,
JSF,
work,
I'm
speaking
as
I'm
typing
here
and
just
want
to
look
really
quickly.
The
February
5th
AMA
is
not
on
here
and
that
so
that's
one
thing
that
could
be
added
as
well.
So,
let's
the
if
you
go
to
the
nodejs
calendar,
it's
like
crammed
full
of
also
all
sorts
of
stuff.
A
What
have
you
kick
off
starts
today:
okay,
cool,
so
let's
jump
into
the
to
the
agenda.
The
first
item
here
is
start
a
code
of
conduct
working
group.
This
I
believe
is
then
I
open
this
one
I'm
opening
it
now
yeah.
So
so,
let's
see
there
hasn't
been
much
commentary
in
the
last
week
or
so,
but
we
should
definitely
get
this
team
up
and
running.
A
B
I
was
just
gonna,
say:
I
remember
we
were
excited
about
this
just
prior
to
the
holiday
break
and
elected,
not
to
really
do
a
big
call
for
participants
because
of
that
break
kind
of
possibly
stymieing-
and
you
know
momentum
so
I
think
what's
what's
wanted.
Here
is
perhaps
a
call
out
to
the
broader
community
with
some
proposed
and
you
times
to
kick
off
a
you
know,
an
a
working
group
initial
meeting,
and
we
can
maybe
organize
that
on
the
on
the
thread
and.
D
One
question
was:
is
it
to
like
I
think
we
have
a
bunch
of
open
questions
today
there
there's.
The
first
question
is
like
for
the
what's
in
the
current
proposal.
Is
that
controversial
not
agreed,
or
is
that
agreed
and
we
have
extra
new
things?
We
want
to
talk
about
an
add-in
but
I
guess.
My
question
is
like
in
the
longer
term,
like
is
this
a
long
term
group
that
will
continue
and
like
we
see
it
going
on
or
is
it
to
basically
answer
those
specific
questions?
Yeah.
A
A
D
Yeah
that
makes
sense
to
me,
and
it
I
mean
it's
even
that
you
could
bootstrap
with
a
minimal
set
of
things
that
are
supported
like
that
in
terms
of
process,
and
then
the
team
could
continue
to
discuss
things
that
might
take
longer
to
get
in
place.
So
I
could
see
it
going
on
for
a
little
while,
but
I
didn't
know
what
it
would
do
like
long
long
term.
So
what
you
described
makes
sense
yeah.
A
E
D
D
Was
just
trying
to
those
typing
a
comment
which
is
trying
to
cast
that
the
two
key
questions
in
my
mind,
are
like,
first
of
all,
what's
the
minimal
minimum
viable
COC
process
and
is
what
we
have
proposed
that
I'm
and
then
separately
from
that
you
know
what
additions
to
that.
Do,
we
think
make
sense.
D
So
you
know,
there's
been
discussion
of
you
know:
cross
project
cooperation
in
terms
of
the
code
of
conduct
and
so
forth,
but
I
think
most
of
that
could
be
a
follow
on
step
to
the
minimum,
viable
process
and
I
kind
of
would
like
us.
If
we
can
I
think
would
be
good
to
separate
them
out
is
in
that
we
don't
have
a
process
and
we've
been
operating
for
quite
a
while.
So
we
should
get
something
in
place
and
try
and
keep
it
simple
to
make
it
so
that
that
doesn't
stretch
it
too
long.
A
Yeah
I
wonder
I'm.
You
know
part
of
my
my
comment
here
in
opening
this,
which
I
think
was
born
out
of
our
discussion
was
that
to
begin
we
would
create
a
repo
and
I
wonder
if
we
should
do
that
and
then
have
some
issues
that
kind
of
capture
like
what
the
expectation
of
an
MVP
is
and
what's
further
issues
about
what
needs
to
be
built
out.
On
top
of
that,
what
were
some
of
the
concerns
based
on
our
discussions
at
the
collapse
on
that.
A
D
F
B
Okay,
well
then,
I
think
on
this.
Maybe
you
know
one
thing
that
the
small
group
of
us
can
do
is
just
write:
a
nice
clean
problem
statement
to
to
kind
of
encapsulate
the
like
what
it
is
that
this
group
is
going
to
work
on,
and
then
we
can.
We
can
send
out
a
invitation
via
our
projects
list
and
also
on
github.
Later
this
week
to
cap
start
casting
that
neck,
and
then
we
can,
all
you
know
tell
her.
Tell
her
friends
tell
her
projects
that
and
we
we
want
to
help.
A
I'm
sure,
once
we
like
are
at
the
point
of
having
meetings
and
discussing
the
the
details,
we'll
get
a
lot
of
folks
involved,
at
least
that's
the
impression
I
get
from
the
conversations
we
were
having
at
the
collapse
summit
and
and
all
the
you
know,
work
that's
been
done
in
the
notes
base
in
the
past
and
such
will
have
some
voices
at
the
table
and
you
know
well
amp
an
electron
as
well.
You
know
they're
party
of
projects
for
Camilla.
D
A
I
just
dropped
coming
in
there
as
well-
maybe
not
perfect
notes
but
I
think
just
to
capture
what
we're
discussing
great
so
I
think
we
can
move
on
from
from
here
and
Jory
and
Ben
and
I
can
you
know?
Maybe
we
should
even
create
a
slack
channel
in
public
one
and
just
start
using
that
to
interface
a
little
bit
and
so.
A
In
progress
here,
cool
excellent,
so
the
next
issue
on
the
agenda
or
item
is
the
pull
request
for
14.
This
is
add
foundation
wide
copyright
guidance
if
I'm
not
mistaken,
Brian
and
Toby
we're
gonna
get
together
and
work
on
this
I'm,
not
sure
if
any
things
happen
or
Brian
and
Toby,
either
on
the
call
Brian.
B
D
A
Okay,
cool
so
we'll
kick
that
one
down
the
road
and
maybe
I'll
ping
them
to
see.
If,
if
there's
been
any
progress
there,
cool
next
on
the
agenda
is
kicking
off
an
open,
jazz,
Foundation
project
landscape.
Do
we
want
to
discuss
this
any
further,
or
what
do
we
think
are?
Like
kind
of
the
next
steps
I
know
there
was
some
conversation
Tierney
raised
some
valid
points,
Dan
Cohen
who's
offered
to
do
some
of
the
work
to
get
it
started,
responded
to
some
of
those
points,
but
then
it's
kind
of
languished
here,
I,
don't
know
Brian.
D
A
A
B
So
this
is
a
pretty
I
think
this
one
can
be
merged
in
close
I'm,
not
the
kind
of
sounds
a
little
presumptuous.
It's
my
PR
I
think
it
can
be
course
I
do,
and
but
this
just
clarified
and
some
details
around
like
how
we
are
going
to
review
charters
when
they
come
in
we've
done
two
in
this
fashion
and
it
just.
There
was
some
outstanding
comments
related
to
synthesizing
and
linking
to
information
elsewhere,
as
opposed
to
repeating
it
I
think
I
addressed
those
and
got
the
thumbs
up
from
Michael.
B
B
B
B
A
All
right,
bingo,
great
I,
love
doing
that
stuff,
add
posts.
So
the
next
item
is
pork,
west
386,
which
is
a
post,
graduation
checklist
I.
Think
the
first
question
is
you
know:
where
should
this
live
I'm
trying
to
look
get
caught
up
here?
Yeah
smile
said
I,
think
kind
of
over
the
holiday.
The
things
have
moved
to
the
new
repo.
D
Right
the
conversation
we
had
there
was
like
there's
two
pieces,
one
which
goes
in
our
governance
that
will
require
some
approval,
another
one
which
goes
into
the
like.
It's
a
check
into
the
checklist
project,
onboarding
checklist
and
I.
You
know
my
question
was
just
like:
is
it
easier
to
land
this
and
then
move
it,
or
vice
versa
and
Toby
said
it
would
be
easier
just
to
land
and
then
move
it
right
and
I?
Don't
think
we
need
any
approvals
to
move
it.
So
yeah.
A
D
A
A
Boys
I,
don't
forget
to
add
yourselves
to
the
meeting
notes.
I'll
drop
that
in
here.
While
we
have
a
pause
in
the
action
cool,
so
I'm
just
gonna,
add
an
approval
for
me
for
386
pull
requests.
A
Yeah
all
right
cool.
Well,
let's,
let's
double
back
on
this
one
and
if
folks,
who
are
on
the
call,
can
go
check
it
out.
That
would
be
great
put
your
thumb
on
it
or
major
concerns.
What
have
you
and
we'll
try
to
move
this
forward
in
the
very
near
future
right
on?
Let's
see
where
am
I
so
moving
on
move
COC
proposal
to
stage
3.
F
A
A
All
right
great
now
we're
to
this
one.
This
is
issue
377,
clarify
travel
fund
status
and
process,
I'm
glad
that
this
is
on
here,
because
there's
been
some
chatter
on
pull.
Requests
for
401
I
will
drop
this
into
the
chat
here
for
folks,
the
discussion
is
around
finalizing
the
travel
fund
process
and.
A
A
There
was
discussion
in
the
past
about
just
moving
forward
with
the
same
amounts
and
elevating
the
travel
fund
up
to
the
open,
Jas
level
and
and
I
think
in
those
discussions
it
made
sense,
considering
the
the
amount
that
we
have
used.
Typically,
in
my
experience,
you
don't
ask
for
more
money
if
you
haven't
used
it
up
to
the
mill
previous
year.
That
being
said,
though,
I
put
some
thought
into
it
last
night
and
made
a
comment
on
this
issue.
That's
we
in
that
initial
conversation.
A
We
perhaps
did
not
know
that
we
were
bringing
on
amp
and
electron
a
couple
other
large
projects
that
also
have
their
own
collaborators
summit,
and
so
there
is
now
discussion
about
what
this,
what
the,
how
we
should
move
forward
on
the
budget
and
if
I'm
not
mistaken,
there
is
a
budget
meeting
happening
in
a
week
or
two
anybody
else
got
more
add
to
that.
I.
H
E
Another
possibility
and
I
drafted
something
that
I'm
hoping
I
can
get
some
consensus
over
at
the
board
at
is
you
know.
The
board
makes
a
clear
commitment
that
the
budget
will
be
extended
if
necessary,
if
that
would
be
sufficient
as
well.
My
biggest
concern
here
is,
you
know
our
budget
was
sixty
thousand
last
year
we
used
thirty
of
it.
E
I
understand
you
know
Joe,
Jets
and
math
with
an
estimate
of
ninety
which
was
estimating
that
the
other
two
projects
amp
an
electron,
would
use
a
similar
budget
to
no
js',
but
it
would
bring
us
up
to
290
K
I'm,
just
not
like
personally
super
enthusiastic
about
increasing
the
budget,
for
what
to
me
seems
like
primarily
optics
I,
do
understand.
Being
careful
I
mean
we
could
even
make
a
commitment
to
halfway
through
the
year
reviewing
in
and
extending
it
if
necessary,
but
I
personally
am
not
super
enthusiastic
about
asking
for
a
budget
increase.
G
B
I've
been
working
with
the
amp
team
for
onboarding
I
haven't
reached
out
to
electron
one
of
the
things
on
you
know.
Amp
is
just
trying
to
figure
out
their
events
for
the
year
and
they
do
have
you
know
they.
They
were
curious
about.
Will
this
be
available
to
us,
but
they
also
want
to
figure
out
their
own
system
for
verifying
that
and
people
who
are
applying
for
that
those
funds
actually
are
you
know,
project
contributors
and
so
and
that's
just
I
think
they
intend
to
use
it.
B
E
When
you
know
when
nodes
travel
fund
was
set
up,
the
intent
was
that
if
you
work
for
a
member
company
or
even
a
large
company
in
general,
and
that
company
was
able
to
and
willing
to
pay
for
your
travel,
that
you
would
not
use
the
fun
and
there's
quite
a
few
number
of
people,
myself
included,
who
well
they're
technically
eligible
to
utilize.
The
fund
do
not
they,
you
know,
have
their
organization
pay
for
it.
E
So
I
would
like
to
make
sure
that
we're
still
a
all
on
the
same
pages
about
that
and
be
that,
like
you
know,
when
we're
going
and
talking
to
different
groups
about
this,
that
they're
aware
of
that
intent
with
the
fun,
because
you
know
in
the
in
the
case
of
Anthony,
say
this
is
a
Googler.
Amp
is
a
Google
project.
A
disproportionate
number
of
their
collaborators
are
Googlers
and
I
still
very
much
believe
that
Google
should
be
covering
to
travel
for
them
to
attend.
So
I
just
want
to
make
sure
that
that's
communicated
you.
B
You
say:
mine's
just
spread
up
her
a
really
good
point,
which
is
we
don't
necessarily
know
why
some
of
our
collaborators
haven't
used
the
travel
fund.
So
this
may
be
an
opportunity
for
us
to
do
and
some
user
research.
If
you
will
this
year
and
ask
our
project
communities,
you
know,
have
you
used
it?
If
so,
you
know
when
and
why,
if
you
haven't,
why
not
that
kind
of
thing
so.
A
D
A
A
F
E
It
yeah
I
just
want
to
like
push
back
a
little
bit
on
over
optimizing
here,
because
if
the
concern
is
that
the
fun
can't
be
increased,
then
we
can
appease
that
concern
either
with
a
statement
saying
that
it
will
be
increased
or
with
an
increase.
But
I
think
the
best
survey
would
be
literally
seeing
who
uses
the
fund
yeah.
F
D
D
E
Don't
know
that
we
should
do
that,
though,
because
like
this
is
just
we
already
have
so
many
things
that
we're
asking
people
for
I
guess
like
us,
knowing
that
we're
gonna
be
able
to
support
projects
when
they
come
in
is
it
is
a
good
thing
but
like
if
a
project
doesn't
exactly
know
how
they're
gonna
estimate
something
like
that?
Unless
you
make
that
an
optional
thing,
it
seems
like
the
kind
of
thing
that
could
stop
people
from
filling
out
an
application.
E
A
D
A
Cool
well
we'll
leave
it
there.
You
know,
take
to
the
issues,
pull
requests
and
leave
your
comments
and
thoughts,
and
you
know,
like
I,
said,
there's
a
meeting
I
think
in
one
week
and
we'll
try
to
revisit
this
and
moving
forward
because,
like
Michael
said,
we've
already
had
to
be
one
a
doc
and
we
need
to
yeah.
A
D
A
A
Jo
specific
and
the
other
two
I
need
to
update
been
has
offered
to
help
me
get
that
over
the
finish
line,
so
hopefully
we'll
have
that
wrapped
up
pretty
soon.
The
other
two
things
on
this
project
board
our
project
directed
funding
and
update,
move
JSF,
CLA
bots
for
new
foundation.
I,
don't
know
if
there's
I
know
Brian's
not
on
the
call,
so
I'm
not
sure
if
there
really
any
updates
on
either
of
those
two
I.
Don't.
B
Think
that
we
can
really
update
on
on
either
of
those
without
Brian
I
know
that
they
were
looking
at
some
other.
This
was
blessed
in
the
last
quarter
circuit
board,
looking
at
other
CLA
tools,
because
with
the
current
JSF
she
only
bought
is
the
CLA
assistant
and
so
I
think
there
was
some
analysis
of
other
options
out
there,
but
we
don't
have
anything
to
report.
Yeah
cool.
A
E
E
So
other
organizations
nonprofits
can
not-for-profits
are
able
to
join
the
OSI
as
an
affiliate
member
other
organizations
that
are
kind
of
similar
to
ours
that
are
already
affiliate.
Members
include
the
FreeBSD
Foundation
the
Debian
project,
the
Drupal
Association,
the
Eclipse
Foundation
I,
think
the
Python
Python
Software
Foundation
is
a
member.
The
software
freedom
Conservancy,
the
Perl
foundation.
You
can
see
a
bit
of
a
you
know
a
pattern
here.
We
rely
on
open
source.
We
rely
on
the
definition
of
open
source.
E
I
think
would
be
a
very
good
idea
for
us
to
participate
as
an
affiliate
member
in
the
OSI.
That
would
also
give
us
the
ability
to
run
to
have
someone
from
the
open,
J's
foundation
run
for
an
affiliate
board
seat
and
they
are
having
an
election
start
soon.
I
believe
that
the
process
is
well
documented,
I
believe
we
fit
all
of
the
requirements
as
a
nonprofit
organization,
so
I
think
the
next
step
is.
E
I'm
not
sure
if
there
is
AC
or
not,
it
wasn't
super
clear,
but
in
general
you
know,
I
think
that
this
would
be
a
good
thing
for
us
to
participate
in
and
if
no
one
from
the
CBC
has
any
concerns,
and
no
one
from
the
standards
meeting
has
any
concerns.
Today,
I'd
like
to
make
an
ask
to
Robin
and
the
board
and
foundation
staff
to
kind
of
move
forward.
With
this
affiliate
membership,
yeah.
F
D
E
D
B
Being
able
to
take
part
in
and
provide
our
community's
perspective
on
the
evolving
definition
of
the
evolving
open
source
definition,
and
it's
obviously
you
know
a
live
topic
and
one
that
many
of
our
constituencies,
like
you,
know,
care
quite
a
bit
about
this,
would
kind
of
give
us
a
forum
to
do
that
in
a
more
official
way
and
I
think
that's
pretty
pretty
exciting.
There's.
E
E
How
does
you?
How
do
you
become
when
it
says
like
the
steps
why
affiliates
OSI
is
transitioned
from
its
original
governance
model
of
volunteer
and
self-appointed
directors
to
undriven
by
our
membership,
our
high-level
objectives
and
doing
sort
of
pry
the
provide
a
broad
meeting-place
communities
of
all
kinds
which
depends
upon
and
implements
the
mission
of
OSI,
but
continuing
aim
of
stewarding
the
license
list
and
the
open
source
definition
safely
beyond
undue
influence
by
special
interests
and
in
the
longer
term
of
creating
serendipity
among
communities?
So
software
freedom
flows
and
grows?
E
Why
should
you
join
the
OSI
reached
a
significant
milestone
in
its
history,
as
well
as
the
benefit
of
associating
organization
with
the
OSI?
Your
affiliate
membership
allows
your
organization
to
participate
in
the
process
of
defining
the
future
means
by
which
OSI
achieves
its
mission,
both
by
joining
in
discussion
about
proposed
changes
and
buy-in
policies
and
by
guiding
the
selection
of
members
of
its
board
of
directors.
E
The
commitment
of
an
affiliate
is
to
express
your
public
support
for
open-source
and
for
the
OSI
to
appoint
a
delegate
to
act
on
behalf
of
the
group
and
OSI
business
and
give
direction
to
that
delegate.
While
delegates
will
welcome
to
also
participate
in
working
groups,
we
anticipate
this
delegate.
Rule
involves
a
minimal
time
commitment
to
make
annual
contributions
towards
the
running
of
OSI,
where
possible,
so
that
makes
it
sound
like
there
isn't
an
explicit
contribution,
but
you
contribute
where
you
can
and
you
have
a
delegate
who's.
E
A
member
of
your
organization
participates
that
kind
of
leads
into
something:
that's
not
on
the
agenda,
but
I'll
just
kind
of
plant.
The
seed,
which
is
the
standards
group,
is
working
on
potentially
trying
to
become
a
chartered
working
group
to
oversee
the
open
JSA's
engagement
in
standards
organizations.
So
it
is
my
belief
and
there's
a
number
of
people
on
this.
E
Call
who
participate
in
the
standards
group
that
the
standards
group
would
be
willing
and
able
to
take
on
the
responsibility
of
being
a
delegate
and
managing
who
that
delegate
would
be
in
ensuring
that
that
delegate
is
representing
our
organization
in
general.
I
think
you
know,
when
our
meeting
today
will
we'll
discuss
a
little
bit
more
of
timelines
there.
But
you
know
just
quickly
to
the
room.
Does
anyone
see
any
problems
with
kind
of
a
long-term
plan
of
spinning
up
a
standards
working
group
who
would
oversee
those
kinds
of
things.
A
A
A
Communication
channel
between
CPC
and
amp
infrastructure
infrastructure
working
group,
I'll
drop.
The
issue
in
the
chat
here.
I
know
that
you
know
we
have
a
slack
channel
I
believe
that
Brian's
spun
up
some
sort
of
mailing
list.
I,
don't
know!
If
there's
any
thing
here
to
discuss,
I,
don't
think
Toby
or
Brian
are
on
the
call
Jory.
What
do
you
I.
B
Am
and
I'm
gonna
double-check
with
and
with
the
Toby
and
and
and
curse
and
some
others
that
this
can
be
closed,
but
we
did
discuss
this
at
our
amp
in
for
a
working
group
meeting
at
the
collab
summit
and
the
group
there
kind
of
got
on
the
same
page
about
you
know
connecting
and
our
plan
for
work.
So
I
think
that
we
have
this
identified.
A
A
I
will
without
being
rude.
I
will
encourage
folks
to
you
know
if
you're
coming
in
this
meeting
and
you're
interested
in
you're,
not
a
CPC
member.
It
really.
You
know
it's
not
a
high
bar
to
cross
activity
in
a
project
for
three
months
and
a
PR
to
add
yourself.
So
the
folks
who
are
not
CPC
members,
please,
you
know,
consider
that,
but
otherwise
we're
gonna
do
in
a
private
session.