►
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
All
right:
well
thanks
everyone
for
joining
another
episode
of
the
openjs
foundation's
Cross
project
council.
Meeting
friends
today
is
the
22nd
of
November
and
we've
got
a
small
audience
for
the
holiday,
but
we
got
some
agenda
items
that
we'll
go
through
gosh
I
feel
like
I.
Haven't
done
this
in
a
long
time?
What
what's?
What
do
we
have
any
announcements?
That's
what
I'm
looking
for
do.
We
have
any
announcements.
C
Yes,
yes,
we
do.
We
have
a
a
really
cool
event
coming
up
called
openjs
in
finance.
We
are
partnering
with
the
phenos
foundation,
which
is
the
fintech
open
source
Foundation
under
the
LF,
so
they
have
the
open
source
in
finance
Forum.
They
do
it
in.
They
stagger
between
New,
York
and
London.
So
it
is
a
one-day
event
in
New
York,
December
8th.
We
have
a
lot
of
great
openjs
speakers.
C
We
have
Sarah
and
Abby
here,
as
well
as
others
speaking
from
the
node
project,
from
the
electron
project
and
from
the
board
and
CPC.
So
it's
going
to
be
a
great
event.
If
you're
interested
I
believe
you
can
still
buy
tickets,
let
us
know
if
you
need
a
discount
or
a
code
and
we'll
get
you
get
that
in
your
hands.
But
it's
gonna
be
a
great
day.
C
D
C
Big
one
and
also
I'm
gonna
be
chasing
down
the
program
committee
for
some
calendar
Bingo
to
try
to
find
a
new
time
to
meet
I
there's
a
couple
of
folks
who
can't
make
that
Thursday
regular
time,
so
I
thought
we'll
try
to
try
to
change
it
up.
So
look
look
in
your
inbox
for
that
or,
if
you're
interested
in
sort
of
helping
shape
our
events
next
year.
Just
let
us
know
and
we'll
add
you.
B
Great
yeah
next
year
should
be
fun
in
terms
of
shaping
events
being
creative,
more
than
just
the
flagship
stuff
that
we've
done
in
the
past.
I'll
also
add:
we
have
a
security
meeting,
openjs
security,
collab
space
meeting
right
after
this.
C
B
So
you
know
one
of
one
o'clock
Eastern
time,
whatever
whatever
that
translates,
but
you
know
what
49
minutes
so
feel
free
to
join
us
there
as
well.
The
meeting
is
in
the
calendar.
If
you
need
the
zoom
and
whatnot
cool
anything
else,
any
board
updates
or
anything
like
that.
B
Okay,
just
adding
some
notes
Here.
Let
me
let
me
share
the
note
stock
if
anyone
can
help
take
notes,
that's
great.
B
So
if
we're
gonna
jump
into
the
agenda.
The
first
item
is
issue
957..
B
B
You
know
Toby's
commented
about
cleaning
some
things
up,
I,
don't
know.
If
we
have
any
thoughts
about
this
or
we
should
just
add
it
to
a
list
of
maybe
some
working
session
items
where
we
can
go
back
through
and
clean
things
up
or
at
least
make
clear
what
they
are.
C
We
did
that
one
spring
cleaning
working
session
I
thought
that
was
pretty
effective,
I
think
we
that
would
be
worth
doing
again.
Yeah.
A
B
Yeah,
most
of
them
are
are
legit.
We
just
maybe
need
to
add.
You
know
comments,
or
at
least
a
good
description
about
what
they
are
and
why
they're
there,
but
that
sounds
good
we'll
do
it
in
a
working
session
sometime
soon,
not
this
upcoming
one,
because
we
have
plans
but
we'll
get
to
that
in
a
few
minutes.
B
Next
up
is
issue
953
funds
for
project
driven
initiatives.
You
know
we
talked
about
this
a
little
bit
before
we
got
the
live
stream
going.
Do
we
have
do
we
have
any
comments
or
updates
on
this
one
now
or
do
we
want
to
wait
until
we
get
more
clarity
and
Direction
on
this
particular
issue?.
D
Yeah
yeah,
so
we
discussed
this
at
our
last
board
meeting.
I
think
what
we
can
share
and
we'll
put
details
in
the
comment
is
in
the
past.
The
board
has
helped
facilitate
sponsorship
from
companies
where
member
projects
have
run
into
these
issues
of
needing
help.
So
I
think
that's
where
we
like
the
projects
to
start
right,
not
from
getting
sponsorship
from
within
the
organization
or
reaching
out
to
the
board
and
working
with
directly
with
the
board
to
get
sponsorship
from
companies
who
want
to
help
and
have
Bigger
Pockets.
D
So
we'll
be
adding
on
to
the
comment
Robin
put
together
a
draft,
but
basically
it's
not
I.
Don't
think
and
Robin
correct
me
if
I'm
wrong
I,
don't
think
it's
a
hard
no
from
the
org,
but
we
want
to
see
what
the
needs
are
and
it
is
better
for
the
org
if
we
can
put
projects
in
touch
with
companies
that
want
to
sponsor.
B
That
makes
sense,
we'll
look
forward
to
the
comments
on
the
issue,
but
I
would
imagine
we
will
outline
what
projects
you
know
what
the
process
should
look
like
for
projects
so
that
it's
clear
in
the
future.
D
B
B
B
We'll
we'll
lean
on
someone
else,
I'm
looking
at
the
dock
and
I,
don't
see
anything
so.
B
I
think
it's
basically
that
we'll
we'll
Robin
has
a
comment
that
she's
going
to
draft
that
she's
going
to
submit
soon
and
we'll
talk
more
about
it.
I
think
that's,
that's
probably
good
enough
right,
because
once
the
the
comments
in
there,
then
there'll
be
more
specifics.
B
B
So
there
is
a
essentially
a
patching
script
that
is
PR
here
and
I'm
gonna
work
with
them
yogis
to
figure
out
how
we
move
this
forward,
because
I
think
it's
not
as
simple
as
just
merging
this
I
think
when,
as
they
say
in
the
comment
here,
I
think
when
we
before
we
merge
it,
we
need
to
get
aligned
on
the
appropriate
patch
file
and
just
kind
of
get
things
sorted,
but
I
think
if
I
understand
correctly-
and
this
applies
to-
like
maybe
the
next
two
or
three
issues
that
we
have
on
the
agenda.
B
My
understanding
is
that
we
will
land
version
2.1
of
the
contributor
Covenant
code
of
conduct,
and
this
script
will
run
a
patch
we'll
apply
a
patch
to
to
that
and
whenever
it's
updated
it
will
do
it
as
well
through
I,
think,
GitHub
actions
and
I
think
that
we
just
need
to
figure
out
what
changes
we
want
to
make
to
that.
B
So
my
assumption
is,
we
will
land
version
2.1
and
this
patching
script
will
be
something
some
of
the
boilerplate
at
the
top
with
you
know
our
reporting
information
and
such
and
then
we
can
go
through
that
last
PR
that
that
I
think
Ben
opened
up
and
there's
a
lot
of
comments
on
and
just
generally
get
figured
out
what
our
modifications
are
to
the
document.
Toby.
A
Yeah,
that's
exactly
correct
and
there's
a
tiny
thing
that
we're
going
to
do
on
top
is
include
in
that
patch
sure.
A
The
thing
that's
at
the
top,
though
we
might
maybe
want
to
talk
about
the
thing
that's
at
the
top
like
in
a
separate
conversation,
because
that's
comp
that's
differently,
complicated,
because
it's
additional
content
not
like
modified
content,
but
like
the
actual
thing
that
we're
going
to
change,
is
there
were
two
versions
of
versions:
two
of
version,
two
of
the
COC
to
make
things
really
easy
right,
which
are
slightly
different
in
their
wording.
A
And
we
rely
on
the
first
version
of
coc
2.0,
which
has
this
very
small
distinction
about
project
versus
like
organization
that
we
want
to
keep
until
we
make
a
larger
thoughtful
discussion
about
this.
A
D
A
B
Okay,
so
I
I
I
was
planning
to
get
together
with
yogis
to
figure
out
how
to
merge
this,
and
what
that
would
look
like
I
I
think
that
you
should
be
a
part
of
that
conversation
too,
so
that
we
okay
yeah,
please-
and
thank
you
all
right,
good,
so
we'll
sort
that
out
and
move
that
forward
and
I'm,
hoping
that
we
move
it
forward
in
a
way
that
makes
it
easy
for
folks
to
you,
know,
comment
and
and
adjust
any
sort
of.
A
Approach
I
think
so
I
mean
the
reason
I'm
willing
to
like
help
out
with
this
is
I.
Don't
have
any
horse
in
that
race
like
I,
don't
care
and
I
think
I
have
a
really
good
understanding
of
who
cares
about
what
and
all
of
the
different
pieces.
At
this
point.
B
Sounds
good
all
right,
cool,
we'll
work
through
that
and
and
sort
through
that
confusing
stuff,
we'll
figure
it
out
great,
so
that
kind
of
puffers
issue
910,
as
well
as
the
following
one
in
the
agenda,
which
is
851
pull
request
851.
Those
two
are
related.
B
A
They
said
so
that's
mine
too,
and
they
haven't
done
the
work
that
I
thought
we're
going
to
do
on
the
last
working
session.
On
that
thing,
so
I
will
get
to
it.
Okay,.
B
If
you
want
help
or
something
if
you
want
to
pow-wow,
let
me
know
I'll
work
with
you
on
it,
so
I'll
keep
moving
on
this
next.
One
is
issue
664
code
of
conduct
missing
for
a
number
of
projects
in
the
projects
table
in
the
readme,
and
you
know,
I
see
Toby
made
a
comment
two
weeks
ago.
B
I,
oh,
you
got
your
hand
up.
Toby
go
ahead.
A
Yeah
no
I
mean
I
was
gonna,
say
that
ties
into
the
heading
of
the
code
of
conduct.
Part
essentially
I,
think.
The
idea
here
was
instead
of
like
keeping
different
versions
of
the
truth
in
different
places.
It
might
well
be
worth
keeping
one
version
of
the
truth
in
one
place,
and
it
feels
like
the
head
of
the.
A
The
top
of
the
code
of
conduct
is
like
a
logical
place
to
have
this,
and
so
we
should
probably
leave
it
there
and
then
remove
the
rest
of
like
the
references
from
like
the
readme
I
mean
that
would
be
sort
of
like
my
suggestion
here.
B
Yeah
I,
agree
and
and
I
think
we
should,
just
as
we
pull
out
that
column
in
that
table
in
the
readme.
We
should
just
make
sure
that
you
know
the
code
of
conduct
is
is
very
upfront
in
the
readme,
and
maybe
we
even
have
a
comment
if
you're
looking
for
projects
code
of
conducts
reporting
information
to
see
our
code
of
conduct
or
something
that
makes
it
very
clear,
foreign.
B
Dude
go
on
Sarah
great
if
someone
can
drop
a
comment
in
that
issue.
Just
as
that,
we
have
that
sort
of
understanding.
That
would
be
great
and
then,
as
we
move
forward
on
that
other
work,
we
can
be
sure
to
clean
this
one
up
as
well.
I'll.
B
You
Toby
awesome
so
moving
on
towards
the
end
of
the
list
here
license
check,
support
and
tooling
I
assume.
As
Robin
said
yesterday,
this
is
on
hold
looking
at
early
2023.
C
B
B
This
was
created
in
July
of
2020
I,
believe
it
was
revived
with
the
agenda
labeled
10
days
ago
and
as
Emily
I'll
read,
evenly's
comments
since
he's
not
here
unblocking
and
re-raising
for
the
CPC
agenda,
as
the
growth
plan
was
added
in
in
another
issue,
note
that
we
also
have
open
issues
676
and
677,
which
have
been
split
off
from
this
one,
but
we
should
review
the
topic
in
general.
B
Foreign
have
anything
they
want
to
say
here.
I
mean
I
think
this
is
a
good
thing
that
we
should
do
and-
and
you
know
now,
that
we're
staffed
up
but
Luke
as
well.
That's,
maybe
we
can
start
to
figure
out
what
this
would
look
like.
A
I
mean
it
would
be
good
to
do
a
work
session
on
that.
Maybe
you
know
to
actually
like
figure
out
like
what
needs
to
happen
and
also
I
mean
sort
of
vaguely
tied
to
this
is
I.
A
Think
there's
still
a
whole
bunch
of
projects
like
in
the
onboarding
thing
that
are
not
really
finished,
but
kind
of
and
I
mean
we
should
just
like
decide
what
we
do
with
this
before
we
start
reviewing
stuff
like
it
feels
like
finishing
the
other
morning,
would
be
a
good
step
or
just
something
that
we
don't
do
the
other
morning.
I
mean
that's
also
fine
like
actually
like
you
know.
A
Let's
say
that
I
mean
I
would
be
okay,
saying
well,
you
know
every
project
that
was
here
from
the
past
and
that
we
haven't
onboarded
now
well,
like
that's
fine,
like
let's
just
drop
asking
for
this
stuff.
I
mean
like,
but
like
you
know,
let's
do
something,
make
a
decision
and
then
do
it
right
are.
A
Foundation
yeah
I
mean
I,
don't
like
I
am
not
I.
I'm
I
am
not
expressing
a
judgment
about
this,
like
I
am
just
saying
we
should
either
do
it
for
those
projects
or
not.
Do
it
or
you
know,
but
make
a
decision
and
not
leave
this
thing
sort
of
like
open
and
then
maybe
actually
as
part
of
a
review.
We
could
sort
of
make
sure
that
all
of
these
things
are
in
there.
I,
don't
know,
let's
just
clean
this
stuff
up
and
make
a
decision.
C
Well,
the
JS
Foundation
projects
when
they,
when
the
foundations
merge,
we
now
have
the
trademarks
and
everything
so
they've
landed,
there's
administrative
things
that
are
probably
minor
in
those
because
I
do
I
have
been
sort
of
keeping
a
spreadsheet,
but
there
have
been
people
changes
and
things
that
I
try
to
keep
up
with.
That
needs
to
be
wrangled
a.
C
Our
other
projects,
we
have
a
couple
of
slow
ones,
Luke-
can
help
with
those
some
of
the
other,
bigger
ones.
We're
working
on
as
well.
Just
I
think
is
a
bigger
one.
Just
requires
more
paperwork,
the
other
ones
just
require
more
time
from
these
smaller
projects.
So.
B
C
Free
we've
also
done
things
that
should
help
like
when
Brian
created
the
footer
with
the
Privacy
notice
and
all
of
those
things.
Those
are
easy
things
to
drop
in.
That
will
help
clean
up
a
lot
of
that
onboarding
and
such.
A
No
totally
that
was,
that
was
great.
Your
comment
about
keeping
track
of
this
in,
like
a
spreadsheet,
no
I
mean
I
totally
get
it,
but
like
it
feels
kind
of
weird.
When
we
have
sort
of
like
a
you
know
a
whole.
A
You
know
a
GitHub
repository
to
like
track
keep
track
of
like
a
morning
on
one
end
and
then
like
staff
also
has
another
one
internally,
I
mean
I.
Understand
that
not
everything
can
be
public.
Obviously
right,
but
like
I
also
want
to
make
sure
that
we
don't
like
do
a
whole
bunch
of
extra
work.
Yeah.
You
know
by
duplicating
stuff
everywhere
for
no
good
reason
right.
That's
the
other
thing
and.
B
Yeah
that
makes
sense,
I
have
a
thought
that
I'll
propose
we're
kind
of
getting
into
the
end
of
the
year
holiday
season
and
a
lot
of
times
meetings
get.
You
know,
usurped
by
different
holiday
schedules
and
whatnot.
B
What
if
we
just
plan
that
every
every
meeting
from
here
through
the
rest
of
the
year
is
a
working
session
and
we
just
kind
of
work
on
things
because
I
feel
like
we've
got
these
agenda
items
we
can
go
through
them
and
give
updates,
but
I
think
it'll
be
more
valuable.
If
we
just
spend
our
time
spending
the
rest
of
the
year
working
on
things,
cleaning
things
up,
we
can
meet.
C
B
B
B
Well,
let's,
let's
do
that
and
maybe
we
can
go
through
some
of
the
issues
that
we
have
I
think
we
have
a
working
session
label
now
we
can
just
add
some
things
there
and
and
maybe
at
the
end
of
each
meeting
we
can
just
figure
out
what
we're
doing
next
week
and
and
come
prepared
to
tackle
that
cool.
B
That's
the
last
issue
on
the
agenda
and
we
had
already
decided
to
work
on.
We
have
a
working
session
issue
which
is
9
58..
This
is
simplify
CPC
governance,
which
I
know
we
we
joked
about
that
word
simplify
and
previous
meetings.
B
I
think
we
should
review
what
we
have
here
and
Toby
helpfully
created
five
issues.
This
created
this
list
of
issues
that
we
can
start
to
work
through.
I
know
in
the
last
working
session
we
kind
of
talked
about
some
of
these
things.
I
think
it
would
be
good
if
we
started
so
you
frame.
B
The
working
session
for
next
week
so
that
we
you
know,
have
have
a
structure
as
to
how
we're
going
to
approach
some
of
these
things,
because
there's
kind
of
a
lot
in
that
list
I
think
it
made
sense
when
we
sort
of
broke
it
into
different
specific
things
that
we
wanted
to.
B
You
know
address
question
and
address,
so
maybe
we
can
do
that
asynchronously
before
next
meeting,
maybe
Robin
Toby.
The
three
of
us
can
work
on
that.
Since
we
were
in
the
meeting,
I
can't
remember:
who
else
was
there
but
yeah?
Maybe
we
can
throw
a
doc
together
and
just
start
to
flesh
out
what
an
agenda
would
look
like
for
next
week.
B
Cool,
that's
it
that
we
have
for
this
week.
I
don't
know
if
we
want
to
call
it
early
or
or
start
to
talk
about
something
else
or
what
we
want
to
do.
A
A
B
D
B
B
Yeah
so
we'll
call
it
early
I'm
going
to
jump
into
the
issues
if
anybody
else
wants
to
as
well,
we
can
start
to
figure
out
what
working
sessions
would
look
like
moving
forward
cool
thanks
everyone
for
your
time,
if
you
have
time
in
25
minutes
and
want
to
join
us
for
the
security
meeting,
that
would
be
great,
otherwise
I
will
see
you
all
soon.
Thank
you.
Yeah.