►
Description
To learn more about critical open source JavaScript projects like Appium, Dojo, jQuery, Node.js, and webpack, and 27 more checkout The OpenJS Foundation: https://openjsf.org/
A
B
Anyone
yep,
hey
cfps,
are
open
for
open
JS.
World
deadline
is
February
5th,
so
it's
sneaking
up
on
us.
So
if
you
have
a
great
topic
across
the
JavaScript
ecosystem,
your
project
or
topic
doesn't
have
to
involve
any
of
our
projects.
Please
submit
everyone's
welcome.
A
Great
yeah
and
that
deadline's
going
to
come
up
fast.
B
A
Got
an
action
item
to
figure
something
out
cool
anything
else.
A
Nope,
your.
A
Yeah,
that's
a
good
point.
There
are
a
couple
of
meetings
that
I
need
to
get
back
onto
the
calendar.
I
think
the
working
session
meeting
isn't
on
the
calendar,
so
I'll
recreate.
That,
additionally,
is
the
security
meeting
which
I
was
planning
to
create
before
today,
because
it
would
be
at
after
this
meeting,
but
I
haven't
made
much
progress
on
anything.
So
I'm
going
to
use
the
next
two
weeks
to
to
get
that
security
collapse,
baseball
rolling
again
and
we'll
recreate
the
next
meeting
for
two
weeks
from
today.
A
So
I
hope
to
see
folks
around
for
that
and
I'll
try
to
maybe
drop
an
update
into
slack
before
then
as
well.
So
people
have
a
little
time
to
prepare
and
whatnot
get
get
familiar.
B
A
The
first
thing
here
is
this
is
issue
982
determine
what
a
realistic
Foundation
CPC
review
process
could
look
like
I
know,
we've
talked
about
this
a
bit
about
like
NPS
survey
and
stuff
I,
don't
know
if
there's
really
any
update
here
or
what
what
we
think
next
steps
might
be.
A
C
B
Yeah
I
think
one
thing
that's
been
on
this
too
I
think
we
have
some
projects
that
are
sort
of
in
maintenance
mode,
or
maybe
you
need
to
wind
down
and
go
to
you
know
Emeritus
status,
so
I
think
it's
it's.
These
two
things
will
probably
have
to
happen
in
tandem,
I
mean
I,
know,
I,
think
almost
most
of
the
projects
where
they
are,
but
again
some
of
them
have
not
been
very
active
for
a
while.
So
it's
maybe
a
two-part
thing.
How
do
we
do?
B
D
Yeah
I'm
just
curious
what
the
goal
of
like
the
survey
is,
and
so
what
which
you
know
what
we
would
want
to
get
out
of
actually
doing
some
I'm,
not
I,
mean
I.
Think
it's
great
that
we
do
something
like
that.
I'm
just
wondering
exactly
what
the
purpose
of
it
would
be
and
sort
of
like
what
would
be
the
outcomes
of
the
information
we
would
get
out
of
it.
A
E
Also
I
should
mention
from
just
researching
quickly,
because
I
remember
had
heard
this
before
I
think
MPS
is
usually
like.
Very
short,
it's
only
like
two
questions.
A
Well,
we
can,
we
can,
you
know,
see
what
kind
of
questions
we
come
up
with
and
and
then
kind
of
go
from
there,
whether
we
have
a
smaller
handful
or
a
larger
handful.
It's
like
Toby,
you
still
have
your
hand
up,
or
is
that
fresh,
no.
A
Yeah
I
think
that
sounds
great
and,
and
maybe
you
know
hack
on
on
some
like
goal
language.
What
do
we
expect
out
of
this.
A
A
You
appreciate
it
great
so
then
maybe
we
can
drop
a
link
into
that
issue
with
the
doc
and
then
you
know,
maybe
just
a
quick
note
that
says
you
know
hack
on
questions
and
goal
language
in
there.
A
That'd
be
great
all
right
unless
we
want
to
talk
about
it
more
I'll
move
on
and
if
anybody
can
drop
any
notes
in
the
meeting
minutes.
That
would
be
great
next
up
on
the
agenda
is
issue
957.
This
is
Ben
asking
about
repos
whether
we
should
use
like
badges
or
anything
I
know.
You
know
we
went
through
and
dealt
with
some
of
them.
I'm
gonna
look
right
now
and
see
what
we
really
have
here.
A
That
doesn't
tell
me
how
many
there
are
I
mean.
We
only
have
one
page
of
repositories:
that's
not
crazy,
I
guess
it
wouldn't
be
bad
to
make
clear
what
the
descriptions
are.
You
know
what
the
repos
are
in
the
description
and
then
you
could
make
sense
of
them
a
little
bit
easier.
A
Yeah
I
think
so
too,
and
most
of
them
have
them,
although
some
of
them,
we
probably
can
you
know
archive
still
going
through
here,
like
there's
the
user
feedback,
repo,
which
I
think
you
know
we're
trying
to
use
to
make
it
a
little
more
self-serve
but
I
think
we'll,
probably
you
know,
go
on
a
case-by-case
basis,
working
with
the
foundation.
F
It's
important
that
there
be
a
way
to
figure
out
who
that
who
you
should
talk
to,
but,
generally
speaking,
we
might
have
a
thousand
repos
and
nobody's
going
to
be
browsing
them,
trying
to
figure
out
what
they
all
do
they're
going
to
be
like
they
have
something
they
need
to
do
and
they're
going
to
try
and
find
the
repo
for
it.
So
like
the
the
thing
that
might
be
more
important
to
solve
is
given
a
need.
A
Yeah
yeah,
that
makes
sense
to
me
Jordan,
I,
agree
and
I.
Think
we
should
you
know.
I
can
put
a
comment
into
this
issue
and
close
it.
But
I
don't
know
if
it's
widely
known
that
there's
a
foundation
channel
in
slack
I
mean
that,
would
that
would
be
the
place
I
would
go.
A
You
know,
there's
sort
of
the
grab
bag
of
ask
anything
but
I.
You
know
I'm,
not
sure
what
what
else
we
should
do
regarding
that.
A
Well,
I'm
gonna
I
want
to
leave
a
comment
here.
Leave
comment
later:
okay,
so
I'll
do
that
later
bull.
A
Unless
anybody
has
anything
else,
I
will
move
on
I'll
get
back
to
that
issue
and
put
a
comment
in
and
close
it
next
on.
The
agenda
is
issue
953,
which
is
the
funds
for
project
driven
initiatives
issue.
A
You
know
last
time
we
talked
about
it
and
my
comment
has
it
here.
You
know
we
had
some
understanding
of
what
this
should
look
like
request
should
be
made
on
an
ad
hoc
basis.
Requests
should
come
to
the
CPC
for
evaluation.
Request
should
then
be
forwarded
to
the
board
for
approval
and
dollar
amounts
will
be
turned
on
an
ad
hoc
basis.
Post
Cap
isn't
necessarily
how
we
will
operate.
A
I
think
the
goal
is
to
put
this
into
a
dock,
and
so
maybe
the
project
resources
directory,
but
otherwise
I'm
not
sure
you
know
but
open
the
floor.
If
there's
more
to
talk
about
here
or
what
we
want
to
do.
C
A
You
know
I,
we
just
need
to
get
the
stock
in
there,
I
think,
which
I
can
try
to
look
at
doing
I'm,
just
not
sure
all
the
time
in
the
next
week
or
two.
So
if
anybody
wants
to
take
a
stab
at
it,
that's
that'd
be
helpful.
A
Cool
I
will
keep
moving
on.
The
next
issue
is
910.
This
is
the
patching
scripts
for
the
COC
modifications.
A
And
it's
got
some
comments
on
it:
yogis
I,
don't
know.
If
you've
had
a
chance
to
look
at
this
anytime.
G
Yeah,
so
that
blue
request
is
blocked
by
the
blue
Quest
991
991.,
so
I
like
10
minutes
before
this
meeting
I.
D
G
Pushed
the
changes
and
when
this
podcast
gets
merged,
then
we
can
merge
the
build
script
for
the
COC
template.
G
So
there
are
some
comments:
I
I,
don't
know
if
we
should
all
address
them
right
now,
because
there
there
are
small
changes
to
the
the
baseline
or
should
we
use
a
different
pull
request
to
keep
track
of
these
changes,
but
I
recommend,
like
I
I,
did
some
of
the
some
of
the
fundamental
gym
things
that
are
required
from
this,
but
I
think
we
should
merge
it,
so
it
unblocks
other
people
requests
and
then,
when
the
time
comes,
we
can
change
it
and
update
it
as
much
as
we
want,
but
yeah.
G
D
Yeah
go
ahead.
Sorry,
no
I
just
wanted
to
second
that
my
understanding
is
like
we're
just
moving
a
document
across
the
repository
and
doing
a
small
bunch
of
changes,
and
so
we
shouldn't
discuss
the
content
of
that
document.
G
Conduct
mentions
that
this
is
like
it.
It
gives
a
specific
link
inside
the
same
readme
file
and
it
it
doesn't
work
anymore
because
we
don't
have
that
like
and
in
order
to
fix
this
problem.
What
we
basically
did
is
that
I
will
just
change
the
single
line
and
change
the
wording
of
it
and
that's
it.
G
I
I
might
be
bad
at
like
because
I'm,
not
a
native
speaker,
I,
might
have
some
grammar
issues.
Please
tell
them
and
I
will
act
fast
and
let's
get
the
ball
rolling.
I
guess.
D
Just
to
be
clear,
my
comment
was
an
approval
of
your
comment,
not
trying
to
disagree
with
you.
It
was
just
like
there
was
a
whole
bunch
of
like
comments
on
that
thread
and
I.
Just
think
that
it's
important
to,
as
you
said,
move
all
of
those
comments
outside
and
have
a
conversation
about
the
content
of
that
file
elsewhere.
If
we
want
to,
and
in
the
meantime
just
like
the
moving
of
that
document
and
the
adaptation
of
the
content
of
that
document
in
relation
to
it
being
moved.
G
Right
now,
yeah
there's
two
different
comments.
One
of
them
is
moving
the
file.
The
second
one
is
changing
the
the
words
because
it
will
be
easier
to
track
in
the
future.
What
kind
of
videos
to
the
original
document.
G
A
So
so,
if
I
understand
correctly,
this
pull
request,
991,
like
Toby
was
saying
is,
is
just
essentially
moving
some
things
around
so
number
one
Toby
you've
got
a
block
on
this,
so
assuming
you're
good.
Well,
you
can
release
that
and
then
Tierney
I
think
has
a
block
as
well,
but
if
I
understand
correctly,
this
is
on
some
content
related
stuff
that
we
should
ask
to
move
to
a
different
pull
request
or
issue.
Is
that
correct?
D
Yes,
my
block
is
precisely
on
the
fact
that,
because
the
pull
request
doesn't
show
a
move,
but
it's
like
a
it's
a
block
on
the
pull
request
itself,
not
its
content.
The
fact
that,
like
we
don't
see
it
like,
we
should
have
like
two
or
three
commits
in
there
that
like
show
the
move
and
then
show
the
changes
on
that
move,
so
that
so
that
we're
not
having
the
rest
of
the
conversation.
Does
that
make
sense
like
right
now
how
sorry
yeah.
G
Yeah,
so
that
completely
makes
sense,
but
the
thing
is
we
can't
move
the
file
right
now,
because
if
we
move
the
file
we
will
lose
to
data
and
so
I
just
moved
to
First
portion
of
the
code
of
conduct,
not
the
everything,
because
with
the
build
script
that
comes
the
changes
that
we
are
going
to
apply
and,
according
to
those
patch
script
that
we
will
have
in
the
other
pull
request,
the
changes
will
be
made
and
the
only
the
first
part
will
be
constant
and
non-mutable
in
the
opengs
foundation,
and
this
was
one
of
the
feedbacks
from
Jordan
I
guess
and
that's
that's
why
we
did
it
like
that.
G
A
baseline
for
the
the
first
introduction
part
of
code
of
conduct
and
then
the
rest
of
the
code
of
conduct
will
come
from
the
code
of
conduct
template
from
the
internet,
and
then
we
will
contact
them
and
then
the
script
that
I
wrote
will
automatically
apply
the
changes
and
then
generate
it.
Okay,.
D
That
is
super,
clear
and
I
understand
why,
and
it
would
be
good
if
you
essentially
wrote
that,
in
the
body
of
the
of
the
comments
for
the
pull
request,
so
why
this
is
happening.
That
way
is
perfectly
clear
for
everyone,
and
then
we
can
just
like
pull
that
in
I'm.
Sorry,
this
is
super
technical
and
a
little
annoying,
but
we
want
to
make
sure
that
where
we
have
like
a
track
where,
like
this
stuff
is
clear
and
like
we
don't
have
a
whole
bunch
of
long
conversations
on
a
regular
basis
about
this.
G
G
D
Super
you
know
super
specifically
what
this
one
is
and
why
it
is
being
added
and
not
moved
and
maybe
explain
like
when
it's
all
going
to
make
sense.
You
know
like
essentially
what
you
said
there,
but
like
in
in
the
thing
I
think
that
would
be
super
helpful.
D
A
Okay,
all
right
great,
so
then,
once
we
get
that
we
can,
we
can
look
at
moving
that
Claudio.
A
Which
one
is
that
sorry?
Let
me
get.
A
Yeah,
so
we
just
need
to
get
a
doc
into
the
project,
resources
directory
and
the
CPC
repo
that
outlines
that
that
further
elaborates
on
the
comment
that
I
have
in
there
that
we
discussed
last
time.
A
It's
open
to
anyone
at
least
to
get
it
rolling.
We
put
I
put
like
four
bullet
points
into
the
last
comment,
or
one
of
the
last
comments
on
that,
and
so
that
would
be
a
good
place
to
start
and
we
can
kind
of
work
on
it
as
a
group.
If
we,
if
we
need
to
on
a
PR.
A
Cool,
so,
interestingly,
let's
see
so
that's
I'm
trying
to
work
my
way
backwards
here.
So
we
were
talking
about
issue
910,
but
that
one's
resolved
with
the
one
we
were
just
talking
about.
Oh
this
is
the
prefix
text,
but
there's
also
the
other
patch
okay,
so
I
feel.
Like
you
know,
these
two
issues
are
related.
A
A
You
know
make
this
PR
unnecessary,
so
that's
the
next
one
on
the
agenda,
which
I
don't
think
we
need
to
talk
about
unless
anybody
has
any
more
anything
more
out
there,
yeah
I
just
added
rich
goal
thanks
for
joining
rich
thanks,
sorry
I'm
late,
but
you
know
how
it
is
glad
to
be
here:
yeah,
cool
cool,
great.
So
then,
if
we,
you
know
kind
of
Move
Along
there.
A
A
Know
I
was
going
to
say
really
quickly
the
license
scanner
I
think
just
landed
in
a
wasp,
oh
good,
yeah,
so
that
that
could
be
helpful.
Let
me
just
ask
really
quickly:
Claudio.
Do
you
have
your
hand
up
or
no.
B
B
A
Yeah
and
I
wonder
too,
because
I've
been
meaning
to
meet
with
Matt
more
about
some
of
the
security
collab
space
work
that
we
wanted
to
do
and
I
know
that.
There's
a
document
developing
in
the
security
working
group
on
the
node.js
side
as
well,
so
I
want
to
kind
of
figure
out
how
that
all
fits
together.
But
anyway
my
my
thinking
was.
A
Maybe
this
is
even
something
we
could
talk
about
in
a
security
collab
space
in
terms
of
you
know,
I
think
I
can
get
mad
into
that
column
and
figure
out
what
things
look
like
and
and
how
we
might
be
able
to
move
forward.
C
A
Okay,
so
I
will
try
to
remember
to
create
an
issue
in
the
security
clap
space
that
references
this
as
well
and
we'll
keep
it
going.
But
I
agree:
Michael,
we'll
we'll
get
this
off
soon,
we'll
figure
out
what
the
path
forward
is
and
then
we
can.
C
D
A
Yeah
and
I
think
there's
even
a
label.
We
might
have
now
too
for
that
sort
of
thing.
So,
but
let's,
let's,
let's
give
it
another
session
another
whenever
you
call
it
round
and
then
we'll
figure
it
out
cool
and
then
the
last
one
here
on
the
list
at
least
is
clarify
requirements
around
COC
violation.
Toby
opened
this
a
really
long
time
ago,
oh
and
I.
A
Think
oh
yeah,
so
this
one
is
you've
got
some
some
bullet
points
here
which
would
be
cool
to
to
work
on
once
we
get
some
of
that
other
stuff
done
too
I.
Imagine
I,
don't
know
if.
D
You
have
anything
Toby,
I
I,
don't
I,
don't
it
was
holidays
and
oh
yeah.
It's
no
longer
holidays.
D
A
Yeah
I
wonder
that
too
I
think
we
did
kind
of
touch
on
some
of
this
and
I
think
there
is
even
more
that's
waiting
to
land
that
might
further
pull
this
out.
So
I
I
think.
That's
sorry.
D
A
You
know
what
we
want
to
do
for
for
next
working
session.
I
mean
I,
think
we're
making
progress
on
the
code
of
conduct,
stuff
and
I
think
it
would
be
great
to
continue
to
focus
on
that
or
we've
had
some
things
here.
Lingering
I
think
it
would
be
great
to
keep
pushing
that
forward.
If
folks
agree.
A
You
know
yogis
and
and
I,
or
whoever
else
can
help
kind
of
move
some
of
these
PRS
forward.
But
then
we
can
button
up
some
of
the
details
that
have
been
lingering.
A
Cool
all
right,
I'll
put
that
down
on
the
on
the
list
on
the
agenda
for
for
next
week.
A
Great
great,
that's
cool,
that's
exciting
and
I.
Guess
along
those
lines,
I
don't
know
we
we
have
a
program
committee
meeting
tomorrow.
Is
that
right
we.
B
A
A
Yeah.
Is
there
I
guess
what
I
did
we
didn't
talk
about
this
at
all,
but
is?
Was
there
any
anything
to
report
from
last
week's
working
session,
so
that
was
that
was
on
COC
in
moderation
as
well
right.
B
We
spent
a
little
time
on
that.
We
spent
most
of
our
time
talking
about
a
collab
Summit.
B
Claudio
has
volunteered
helped
lead
that
Waleed
can't
do
it
this
year,
so
Claudio
and
the
openjs
team
are
going
to
support
him
and
anyone
else
actually
who
probably
wants
to
participate
in
Nets
great
got
a
lot
of
work
done
a
lot
of
work
done
in
that
space.
Excellent.
A
Thank
you
cool
all
right.
Well,
we
can
work
more
on
COC
and
moderation,
and
the
panel
and
I
hate
that
word,
but
you
know
the
the
moderation
team
and
all
the
little
sort
of
details
that
we
need
to
flesh
out
for
for
that
in
the
next
working
session.
I
suppose,
but
I
encourage
folks
to
take
a
look
at
some
of
the
open,
PRS
and
issues
and
see
if
there's
anything,
we
can
keep
moving
forward
on
anything.
We
want
to
work
on
today
still
or
should
we
just
give
back?
A
If
I,
if
I
give
you
back
25
minutes,
you
gotta
spend
a
few
of
those
minutes.
Looking
through
PRS
and
issues
I'm
just
kidding.
A
Good
cool
all
right,
well,
we'll
call
it
a
wrap.
Then
I
will
see
you
all
around
and
yeah
thanks.
Everybody
cheers.
Thank
you,
cheers
cheers.