►
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
Have
a
few
so
the
first
announcement
are
about
upcoming
meetings.
We
do
have
a
summit,
a
collab
summit
planning
meeting
today,
which
begins
immediately
after
this
one
on
a
different
SIM
call.
You
can
get
the
link
to
that
either
by
going
to
the
summit
repository
and
looking
at
the
issue
for
today's
meeting
or,
of
course,
by
subscribing
to
the
foundation
calendar,
which
also
includes
that
information,
then
immediately
after
that
at
2:00
p.m.
B
Eastern
and
I
apologize
I,
don't
remember
the
UTC
time,
for
that
at
the
moment,
is
the
standards
working
group
meeting
and
that
information
is
also
in
and
the
issue
on
the
/
standards,
repo
and
again
in
the
calendar.
So
those
are
two
upcoming
meetings
this
week
for
the
foundation.
I
also
wanted
to
share
that.
We
added
a
new
integration
to
the
slack
channel
which
I'm
excited
for
us
to
test
out.
B
It's
called
thanks
bot
and
it's
a
way
to
leave
your
colleagues
and
the
foundation
a
note
of
appreciation
and
share
that
with
everyone
on
a
regular
basis,
so
give
that
a
try,
if
you
don't
mind
and
let's
let
me
know
what
you
think
and
then
last
but
definitely
not
least,
Rachel
had
shared
this
last
week,
but
I'll
say
it
again.
We
have
call
for
different
kinds
of
content
for
the
open,
J's
foundation,
blog
and
social.
B
If
your
project
has
releases
or
technical
content
or
you
know
really
anything
newsworthy,
and
we
want
to
be
able
to
support
the
reach
of
that
content.
So
please
do
share
it
in
our
PR
marketing
channel
on
slack
so
that
we
can
help
you
get
the
word
out
and
I
think
that
is
it
at
the
moment
for
announcements,
I'm
sure,
I
able
to
think
more
later.
This
is.
C
C
At
the
same
time,
we're
narrowing
down
choices
for
a
virtual
platform,
so
we
will
likely
move
forward
with
a
virtual
event,
assuming
that
things
don't
come
together
in
Austin
and
I.
Just
have
to
say
that
the
program
committee
is
doing
an
amazing
job.
You
all
did
an
amazing
job,
submitting
CFPs.
We
have
some
great
folks
interested
in
keynotes.
So
that's
on
track.
C
A
I'm
looking
at
the
calendar,
I
have
an
open,
Jas
open
office
hours.
This
Thursday
that
all
highlights
and
I'm
meeting
with
a
friend
of
mine
from
eslint
Kai
later
today
to
discuss
having
eslint
at
the
open
office
hours.
So
that's
Thursday
at
1:00
p.m.
Eastern,
Time
and
then
I
don't
know.
If
anyone
else
wants
to
give
any
information
on
this,
but
I
also
see
a
board
meeting
the
public
session
on
Friday.
Is
that
right?
A
Cool,
so
just
checking
back
here
going
over
to
the
agenda.
It
looks
like
the
first
item
is
the
those
are
the
announcements
where
are
we
here?
The
first
item
is
from
the
summit's
repo,
and
this
issue
is
around
trouble.
Fun
questions
which,
as
I
mentioned
earlier
divvy,
created
a
PR
in
the
cross
project,
Council
repo
to
try
and
integrate
those
comments
and
requirements,
I
guess
you'd
say
into
the
documentation.
A
There's
been,
you
know
some
some
commentary
here
that
I
think
we
need
to
just
kind
of
go
through
and
clean
up
and
yeah
some
some
like
formatting
and
stuff.
We
need
to
review,
but
it
looks
like
this
is
almost
ready
to
go.
So
if
anybody
has
any
time
and
can
give
it
a
one
more
month,
sober
great
otherwise
I
think
we
can
move
forward
on
it.
A
Thank
you,
my
pleasure.
Also
moving
on
the
next
issue
in
the
agenda.
Is
the
nomination
sought
for
2020
2021
voting
CPC
membership,
the
folks
who
are
nominating
or
self
nominating
are
sending
emails
to
me.
I've
got
a
few
of
them
in
my
inbox.
When
does
this
wrap
up
in
terms
of
nominations
and
such
today.
B
B
F
Have
a
quick
question-
and
this
is
Dylan
from
dojo
and
wee-wees.
Dojo-
have
been
very
inactive
in
terms
of
CPC
membership,
so
I
feel
a
bit
reluctant
to
nominate
anyone
from
our
project,
because
we've
only
been
to
a
few
meetings
each
just
because
of
life
and
other
craziness
in
the
past
year.
So
I'm
wondering
if
that's
okay
or
if
you
want
us
to
still
nominate
people
accepting
that
we've
been
less
active
than
we'd
like
to
be
and
that
might
change
or
what
you
would
recommend
there.
I.
F
A
A
G
F
Yeah
I,
just
I,
didn't
want
to
just
submit
people
and
then
have
it
be
the
same
situation
where
we're
fairly
inactive.
If
work
I
mean
the
truth
is,
were
just
fairly
heads
down
on
dojo
itself
and
I
expected
to
have
more
time
over
the
past
year,
but
I
had
a
lot
of
personal
stuff
come
up,
so
I
expect
that
I
can
be
more
active,
but
I
also
don't
want
to
nominate
myself
after
having
made
it
to
maybe
four
or
five
meetings
over
the
past
twelve
months.
F
H
Don't
believe,
also
like,
with
the
way
that
we've
set
up
these
meetings,
that,
like
it's
not
accessible
to
folks
who
want
to
participate.
So
to
me,
like
almost
the
only
reason
to
be
an
impact
project
at
this
point
and
feel
free
to
if
anyone
disagrees
is
because
you
are
like
saying
that
you
will
show
up
and
participate
in
these
meetings
and
help
with
the
running
of
the
foundation.
So,
in
my
personal
opinion,
Dylan,
if
you
know
you
all,
are
super
heads
down
and
just
don't
have
time
to
focus
on
foundation.
Wide
governance.
B
F
B
Yeah
I'm
totally
happy
to
follow
up
with
you,
Dylan
and
and
actually
any
project
that
may
be
evaluating
whether
they're
at
where
they
need
to
be
stage
wise
so,
and
we
can
also
simultaneously
work
on
that
review
process
with
the
CPC,
and
maybe
that's
an
action
we
should
do
is-
is
file
an
issue
to
start
on
that.
What
I.
C
E
Also
to
note
I:
don't
think
you
necessarily
need
to
make
any
decision
on
the
right
level
that
you
think
you
should
have
in
the
foundation
like
right
away
as
in
you
can
actively
not
nominate
anyone
now
and
then
later
decide
that
yeah.
Indeed,
you
don't
have
that
it
doesn't
feel
right.
You
continue
as
an
impact
project
and
then
make
a
proposal
for
a
change.
Yeah.
I
Hey
quick,
just
a
Mississippi
I
just
joined
so
I
just
wanted
to
find
out
this
from
my
knowledge
or
anyone
else,
who's
new.
A
For
folks
who
are
new
and
I
know
that
you
know
this
is
a
common
practice
and
node
as
well,
but
the
we
trade
you
as
much
as
we
can
in
github
and
in
public.
So
you
know
we
try
to
document
all
these
things
as
well
as
we
can
and
conversations
and
issues
and
PRS,
and
things
like
that.
So
usually,
if
you're
looking
for
something
github
is
probably
the
first
place
to
go.
Yeah.
J
L
G
L
A
Thank
you
cool
all
right,
so
so
so
that's
good
I,
just
wanna!
You
know
to
wrap
up
that
last
comment.
Conversation.
You
know
we're
always
looking
for
more,
like
new
voices
in
the
conversation
with
diverse
set
of
folks
in
the
conversation.
So
if
anyone
in
the
project
is
in
able
to
to
do
as
much
as
they'd
like,
but
they
see
someone
else
who
might
have
an
interest
and
hasn't
done
this
kind
of
work
or
whether
they
have
or
haven't
you
know,
definitely
reach
out
to
them.
G
N
G
M
A
Thank
you,
I'm,
just
making.
You
know
really
quickly
to
send
so
voting.
Reps
nominations.
Okay,
all
right
great!
So
now,
I
have
an
actual
alarm
on
my
phone
to
post
that
stuff,
great
so
neck.
I
added
this
I
think
last
week
just
to
make
sure
it
was
on
everybody's
radar.
This
is
the
issue
for
a
and
the
cross
project
council
repo.
This
is
the
web
hints
project
charter
review.
A
G
G
I
think
that
would
be
just
an
issue
in
the
project
like
an
issue
in
the
CPC
repo
saying
you
know,
here's
here's,
the
the
proposed
within
charter,
and
then
you
know
the
CPC
members
can
chime
in
I'd
have
to
go
back
but
I
think
it's
this
the
voting
members.
Maybe
it
may
just
be
all
the
members.
Let's
take
a
look.
Okay.
A
G
A
O
A
G
G
A
Great
yeah,
why
don't
we
just
update
this
one
Anton?
If
you
wouldn't
mind,
maybe
just
commenting
in
there
and
saying
this
this.
You
know
we're
looking
for
official
review
of
this
an
approval
of
this
of
our
Charter
and
we'll
take
it
from
there.
Okay,
good!
Thank
you!
Excellent
Thank,
You
Anton
great,
so
you
know
if
any
voting
members
on
the
call
when
you
get
a
moment,
please
review
and
thank
you
great.
So
next
up
on
the
agenda
is
the
open
days,
collaboration
network.
This
is
issue.
474,
I
know,
Michaels
done
some
work
on
this.
A
G
G
Yeah,
this
is
basically
the
concept
of
collaboration
spaces
as
kind
of
a
formal
thing
within
the
the
foundation.
Slash
CPC,
where
groups
that
want
to
come
together
and
collaborate
on
areas
that
are
important
to
the
JavaScript
ecosystem
can
make
proposals.
You
know
to
form
where
these
collaboration
spaces,
the
application,
is
reviewed,
reviewed
by
the
CPC.
Just
like
you
know,
applications
for
projects
to
join,
and
you
know
once
approved
the
collaboration
spaces.
You
know
we've
listed
some
resources
which
they
can
draw
on
from
the
foundation.
G
Like
you
know,
a
repository
using
the
slack
mailing
lists
and
so
forth
and
kind
of
like
projects.
There's
two
levels
outlined,
one
which
is
kind
of
the
first
stage
of
well
we're
we,
you
know
people
are
just
coming
together,
we're
gonna,
try
and
start
to
ramp
it
up,
and
then
one
where
it's
like
yeah.
This
is
this
has
been
you
know,
running
showing
results
has
significant.
You
know
reasonable
number
of
people
collaborating
in
an
ongoing
way
and
it
can
kind
of
be
promoted
to
it
to
another
level
where
they
could.
G
That
group
could
take
advantage
of
additional
resources,
and
it's
it's
up
to
us
as
we
go
through
what
resources
should
be
available,
but
each
each
level,
but
like
just
as
a
starting
point.
I
put
the
travel
fund
resources
to
be
in
the
second
level
versus
the
first
level
as
an
example,
yep
and-
and
the
goal
you
know
is
for
people
who
haven't
read
it
yet
is
is
to
you
know,
provide
a
little
bit
more
formalize.
The
concept
of
being
able
to
bring
together
groups
have
them
collaborate
under
the
foundation
and
support
that
that
collaboration.
G
You
know,
we've
done
similar
things
in
the
know,
jas
project
a
few
times
and
there's
always
been
questions
like
who
can
start
one
of
them's.
How
did
we
get
repos
and
so
I
think
doing
it
at
the
the
foundation
where
we
have
a
good
document
to
process,
hopefully
will
make
it
easier
and
more
obvious
for
how
people
can
can
do
it
and
I'm
hoping
that
you
know,
encourage
and
support
the
collaboration
that
we
want
to
have
to
take
place
here.
G
A
N
L
G
L
C
C
C
F
D
F
D
A
B
B
A
G
Certainly,
on
the
like
us
that
there
were
you
know,
representatives
from
non
impact
and
impact
I
think
sending
one
last
email
to
the
impact
project.
Saying
hey
you
know,
do
you
have?
Do
you
have
somebody
you
want
to
nominate?
It
is
listed
as
optional
and
I
think
even
throughout
the
year
somebody
said:
okay
from
this
impact
project,
we
found
somebody's
interested.
We
should
accept.
You
know,
welcome
them
in
for
the
non
impact
projects.
If
we've
had
volunteers,
you
know,
as
opposed
to
you,
know,
looking
or
working
harder
to
find
other
volunteers.
R
D
R
The
code
of
conduct
I
just
had
I,
had
a
chat
with
Coraline
about
the
open-toe
request
that
Nina
from
the
amp
project
had
filed
against
the
contributor
covenant
and
sort
of
like
to
close
the
loop
on
that
open
issue
of
her
reaction.
Caroline's
reaction
was
basically
to
say
that
she
thought
that
the
requested
changes
were
too
specific
to
be
worthwhile
of
streaming
at
this
point
and
that
sort
of
like
the
with
the
kind
of
culture
she
was
creating
around
the
code
of
the
contribute.
R
Covenant
was
the
idea
that
different
communities
would
want
to
adapt
the
code
of
conduct
to,
like
you,
know
their
preferences
and
that
this
was
fine
and
that
this
should
be
the
way
to
proceed
going
forward
and
not
really
to
treat
it
like
a
regular
open
source
project.
We
want
to
upstream
as
much
as
you
as
you
possibly
can
I.
L
Had
a
few
thoughts
about
that,
the
first
one
is
that
I
lecture
I
looked
at
the
PR
after
that
comment
and
like
some
of
them
at
least
one
of
the
paragraphs
seems
like
maybe
it's
project
specific,
but
the
rest
of
it
seems
very
generic
and
like
something
in
the
full
spirit
of
the
the
code
of
conduct.
So
I'm
I'm
surprised
to
hear
the
coralline
wouldn't
want
to
upstream
some
of
those
things.
L
But
then
the
other
comment
is
that,
regardless
of
the
core
lines
intention
to
have
it
not
be
treated
like
a
regular
open
source
project
effectively,
then
we're
being
asked
like
we're
both
being
asked
to
inline
the
text
and
then
also
to
float
patches
on
top
of
it,
which
makes
pulling
down
future
updates
to
it
very
burdensome.
Whereas
if
we
didn't
inline
the
text,
then
it
would
just
be
this
link,
but
here's
some
changes
and
if
we
up
streamed
as
much
as
we
could
then
floating
the
patches
would
be
less
burdensome.
L
R
Agree,
I
do
personally
think
that
a
smaller,
more
focused,
PR
or
set
of
peers
would
have
had
more
chances
of
landing
and
I
also
believed
that
a
coralline
doesn't
have
a
lot
of
resources
to
work
on
this,
and
so
you
know
de
facto
sort
of
limits,
the
you
know
amount
of
like
external.
You
know
well,
I,
think
she's,
just
having
a
hard
time
to
follow
up
with
all
of
the
requests
around
this
and
basically
wanted
to
close.
R
A
A
J
L
L
G
R
Sorry,
what
I
wanted
to
do
was
just
I
had
this
conversation,
I
wanted
to
bring
it
back
to
the
CPC
so
that
the
CPC
had
an
understanding
of
what
the
situation
was
in
I
agree
with
Zuri
that
we
should
then
bring
this
conversation
of
the
outcome
of
like
this
new
information
into
a
specific
issue
and
have
a
conversation
there.
Yeah.
A
Okay,
great:
let's
do
that
all
right,
so
yeah
we
have
like
eight
minutes
before
we
wanted
to
drop
into
seven
before
we
wanted
to
drop
into
a
private
session.
So,
let's,
let's
move
on.
Let's
have
maybe
a
new
issue
for
this.
This
challenge
with
the
upstream
and
and
keep
moving
forward
on
the
code
of
conduct
panel
Toby,
since
you
were
on
the
mic,
we've
got
two
more
issues
that
you
were.
You
were
working
on,
I
actually
looks
like
Michael
may
be
moved
forward
on
one
of
them.
A
R
Was
able
to
update
one
of
those
the
one
around
post,
graduation,
post,
graduation
on
boarding,
Prost,
graduation
list,
sorry,
and
so
that's
fairly
ready
at
this
point
and
I
haven't
been
able
to
tackle
the
other
one
which
have
all
tackle
this
week.
Okay,
but
I'm
actually
set
up
to
work
now
on
these
issues
and
have
like
a
functioning
Devon
where
I
moved
again
so
I
can
up
stream
stuff
and
it's
it's
a
lot
easier.
Excellent.
A
A
G
G
A
P
We
don't
really
have
a
single,
consistent
way
of
doing
that,
and,
aside
from
this
wonderful
spreadsheet,
that
joy
is
maintaining.
At
the
same
time,
we
were
also
thinking
it
might
be
useful
to
have
maintainer
mailing
lists
and
I
wrote
a
github
action
that
parses
through
a
yeah
mo
file,
maintained
and
github
repo.
It
creates
a
maintainer
directory
out
of
that,
but
then
also
syncs
it
against
groups,
dot
io,
so
that
projects
can
maintain
their
own
lists
become
self
manageable.
It
becomes
transparent,
so
just
wanted
to
suggest.
This
is
a
potential
solution.
P
G
P
P
A
That
is
issue
501,
which
I
dropped
into
the
chat
cool
anything
else
before
we
jump
into
a
private
session,
no
all
right.
Well
then,
let's
do
it.
I
will
stop
the
stream
and
I
will
kindly
ask
folks
who
are
not
members
of
the
cross
project
Council
to
exit
the
room
and
will
go
to
a
private
session.
Thanks
everybody,
a
really
good
shift.
You
saved
people
ready.