►
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
I
didn't
do
it
this
time
and
it
seems
like
it
works.
So
that's
great
cool
all
right,
I
believe
we
are
live,
looks
like
in
Zoom.
We
are
and
YouTube's
loading
up
for
me
say
hello
to
the
world
thanks
everybody
for
joining
yeah,
like
Toby
said
we
got
a
great
group
here
today,
happy
to
see
so
many
faces.
A
A
So,
let's
start
with
announcements.
Is
there
anything
we
need
to
announce
check
in
my
notes.
B
Oh
I
think
they
speak
the
acceptance,
acceptance
or
rejection
confirmation
for
open
source
Summit
Dash
openjs
word
were
sent
this
last
weekend.
So
if
you
have
not
received
one
and
you
have
some
outstanding
slots
around,
you
should
probably
check
your
spam
or
anything
so
that
you
don't
lose
your
notification
because
you
need
to
accept
it
in
case
you
have
been
selected
so
otherwise
you
will
lose
your
slot.
So
just
bear
in
mind
that
that
is
that.
C
Also
make
another
call
out
for
the
collab
Summit
to
Claudio's
doing
a
great
job
planning
that
cfps
are
open.
That's
happening
on
May
9th,
which
is
the
day
before
open
source,
Summit
and
openjs
World.
So
so
make
your
talk
for
the
collab
Summit
and
we
hope
to
see
you.
There.
A
Great
thanks
anything
else.
C
We
just
published
the
March
edition
of
the
node.js
security
report,
so
that's
live
lots
of
good
Updates
this
month,
big
shout
out
to
Raphael
for
always
helping
us
with
those
right.
D
C
C
Don't
think
I've
announced
this
in
the
in
one
of
the
cpcs
lately,
so
if
I
did
apologies
but
we're
on
Mastodon
now
we
have
a
openjs
handle
and
a
node.js
handle
and
then
jQuery
and
electron
are
also
on
Mastodon.
So
we
were
super
excited
to
get
those
launched.
A
D
A
And
thanks
to
whoever's,
taking
notes,
I
greatly
appreciate
it
cool.
So
we
wanted
to
throw
something
at
the
front
of
the
agenda
real
quickly.
Just
to
make
sure
everybody's
aware
of
it.
The
node.js
TSC
Charter
changed
it's.
It
says:
pull
request
13!
Oh,
that's
a
TSC
pull
request
13.50,
but
there
is
an
openjs
Foundation.
Sorry,
a
crosstalk.
F
Issue
1028.
Thank
you.
There
Link
in
the
chat,
perfect
and
everybody
here
who
is
a
voting
member
has
already
weighed
in,
except
for
sorry
to
call
you
out,
Sean
Larkin,
but
everybody
else
who's.
A
voting
member
who's
here
today
has
weighed
in
so
I'll.
F
A
Appreciate
it
yeah.
Thank
you.
I'll
just
add
this
to
the
thing
here:
10
28.,
great,
all,
right,
cool.
H
H
A
Awesome
awesome
all
right
cool
so
touched
on
that
so
moving
on
the
next
agenda
item
is
issue:
1009
Sean
you
added
this
enabling
payments
for
GitHub
code
spaces
for
projects-
I,
don't
know
if
there's
any
I
mean
there's
been
a
lot
of
comments,
but
anybody.
G
G
So,
as
far
as
I
didn't
take
time
this
last
week
to
investigate
what
we
want
to
do
in
terms
of
exploring
the
opportunity
for
adding
the
open
JSF,
be
a
billing
manager
on
a
GitHub
account.
So
that's
what
I'm
going
to
pursue
and
I'll
reach
out
to
one
of
you
all
sometime
this
week,
if
I
have,
if
I,
have
a
cycle
to
explore
that
and
then
maybe
we'll
use
webpack
as
the
pilot
program
in
case
we
get
to
that
point,
but
yeah
so
for
right.
I
A
Great
awesome.
Thank
you.
The
next
item
on
the
agenda
is
issue
1003.
This
is
create
some
documentation
web
page
to
describe
the
collaboration
model
of
openjs
projects.
A
H
B
You're
unmuted
part
of
the
reason
why
I
opened
that
discussion
was
because
I've
recently
seen
quite
there
is
quite
a
lot
of
confusion
between
different
ways
in
in
a
different
governance
model
of
Open
Source
projects
and
the
fact
that
what
is
essentially
the
style
of
or
that
openjs
promotes
or
what
you
would
expect
from
the
most
prominent
or
projects
at
at
open,
JS.
B
Okay,
this
is,
and
part
of
this
is
because
people
seems
to
confuse
the
fact
that,
like
you
know,
for
impact
projects,
okay,
so
that
we
have
multiple
companies
involved
is
not
one
single
dictator
that
makes
all
the
decisions
and
all
sorts
of
things
and
currently
and
because
there's
a
lot
of
confusion
there,
especially
in
junior
developers
and
people
that
have
not
been
in
the
industry
for
a
long
time,
and
they
see
that
oh
react
is
open
source,
okay,
reactive,
open
source.
B
Of
course
it
fills
all
the
questions,
ticks
all
the
boxes
for
being
open
source.
However,
it
does
not
have
open
governance.
Okay,
I
think
it's
striving
towards
it
right
now,
because
right
now,
it's
at
least
two
companies
involved
into
the
decision
making
or
react.
So
it
I
see
good
progress
on
there
on
the
progress
on
their
end,
but
for
a
long
time
it
has
been
single
like
you,
you
were
hired
to
the
react
team.
B
Okay
like
if
you
are
hired
to
be
on
the
on
a
team,
then
you
are
probably
that
you
probably
don't
have
I,
don't
know,
there's,
probably
not
an
open
governance
model,
so
this
is
essentially
the
type
of
stuff.
That's
this
I
think
it's
missing
right
now
on
on
the
good
side
of
this
I'm,
probably
going
to
work
on
it.
A
little
bit.
B
I
can
probably
disclose
this,
so
it's
not
not
putting
too
many
other
people
on
the
spot,
but
I
proposed
the
session
on
this
topic
at
open
source
Summit.
So
we
are
going
to
present
on
this.
B
B
This
is,
and
it's
totally
fine,
you
know
it's
fine
to
have
a
Company
open
source
which
is
open
source,
but
with
a
close
governance
like
V8,
typically
like
V8
or
chromium
typical
example
of
projects
that
are,
they
are
probably
they
are
essentially
close,
governance
OKAY
model,
but
on
the
other
side
there
is
projects
like
all
the
impact
projects
of
openjs.
Have
this
model
of
openness
and
open
governance,
and
the
way
things
are
handled
are
completely
different
and
multiple
people.
B
Multiple
companies
are
involved,
and
it's
a
it's
a
good
place,
okay,
on
of
collaboration
across
across
people,
so
it's,
which
is
something
that
we
should
strive
for
from
my
point
of
view,
but
it's
also
okay,
not
to
like
it's
okay.
To
be
honest:
it's
okay,
to
have
corporate
open
source,
open
governance,
it's
okay
to
have
proprietary
software,
like
everybody,
has
to
be
honest
as
a
it's
a
good
place,
it's
just
what
I
don't
like
is
the
confusion
between
the
values.
B
What
people
would
expect
of
the
value
style
of
projects,
and
this
is
essentially
something
that
I
I
find
a
little
bit
more
romantic.
So
that's
why
I
think
we
should
try
to
communicate
this
clearly,
also
on
the
level
of
support
that
people
can
expect
when
interacting
with
those
projects.
So
it's
different,
though
it's
a
company
open
source.
So
maybe
there
are
employees
working
on
it
versus
oh,
it's
just
volunteers,
open
source
and
then
the
people
on
the
person,
on
the
other
hand,
expect
the
same.
Oh
I,
why
the
hell?
B
A
That
all
makes
sense,
Mateo
and
I
think
you
and
the
panel
discussing
it
is
great
if
you
maybe,
if
we
could
start
a
document
and
start
hacking
on
stuff
I'd
be
happy
to
add
to
it
at
IBM.
We
typically
don't
just
say
open
source.
We
say
open
source
and
open
governance
kind
of
in
the
same
phrase,
so
yeah
that's
important.
Oh.
B
E
A
I'll
go
check;
okay,
great!
Thank
you
cool
all
right!
Well,
we'll
we'll
we'll
work
on
this
I'll
try
to
get
something
started!
I
think
I
have
some
stuff
drafted
already.
F
Cool
I'm,
sorry,
Sean,
I
think
you're
sending
your
comments
that
are
in
the
chat
or
going
only
to
me.
D
G
Yeah
no
I
was
just
gonna,
suggest,
yeah,
I'll,
ReChat
or
paste
it,
but
I
was
just
saying
I
think
we
just
need
to
I
think
the
best
impact
for
this
is
to
talk
about
the
trade-off
of
the
models
right
so
like
even
a
closed
governance
system
is
going
to
have
some
upsides.
Like
you
mentioned
Mateo,
you
know,
hey,
there's
people
paid
to
support
this
project
currently,
but
I
have
less
control
over
the
direction
of
this
project.
G
I
think
a
lot
of
people
just
don't
understand
the
trade-offs
and
I
think
that's
gonna
have
a
lot
of
impact
by
by
documenting
those,
and
you
know
I
suggest
like
if
we're
gonna
get
started.
We
have
to
just
like
really
simple
lists
right,
like
and
name
of
the
type
of
model.
D
J
Just
as
a
comment
on
that
last
one
I
have
a
hard
time
understanding.
When
really
you
would
be
balancing
the
benefits
and
trade-offs
of
these
bottles.
It's
more
like
the
situation
and
circumstances
around
a
project
lead
to
different
sorts
of
governance
models,
and
they
then
end
up
with
different
sorts
of
attributes,
but
maybe
this
is
more
getting
into
the
details
of
this
discussion,
which
ought
to
happen
Elsewhere
on
this
call
sure.
I
I
agree,
I
think
it's
also
important
to
think
about
where
the
open
source
project
came
from
because
I'm
working
with
some
companies
now
who
had
only
closed
source,
and
they
have
something
now
that
they'd
like
to
try
to
open
source
and
they
want
to
learn
so
I
I.
Think
if
it's
originating
from
a
corporation,
it
may
need
a
different
kind
of
governance
model
than
something
that
really
comes
from
the
community.
To
begin
with,
I'm
interested
in
that
discussion.
A
Yeah
or
even
the
journey
from
one
or
the
other,
which
I've
seen
a
few
times
cool
all
right
great
well,
we'll
continue
that
either
in
a
doc
or
a
working
session,
or
something
in
the
near
future.
A
Unless
anybody
has
anything
else,
they
want
to
discuss
there
I'll
jump
to
the
next
issue,
which
is
issue
910.
This
is
the
patching
scripts
for
COC
modification
I'm
going
to
where
is
this?
Yagiz
has
been
working
on
this,
and
this
is
pull
request.
972
I
know,
Emily's
been
adding
helpful
updates
here.
A
I
use
the
term
helpful
in
parenthesis
and
air
quotes
I'm
just
kidding.
Are
they
blocking
it?.
A
But
I
see
within
the
last
24
hours
a
couple
more
comments
and
and
yagis
is
trying
to
address
some
of
these
things.
So
I'll
keep
working
with
yogis
to
to
move
this
forward,
and
hopefully
I
think
the
expectation
and
we'll
talk
about
this
more
at
the
end.
But
I
think
the
expectation
is
that
we'll
work
on
this
some
more
in
the
working
session.
A
Next
week
we
found
the
doc
from
the
moderation
team
discussion
we
had
with
Joanna
Lee
from
cncf
and
so
we'll
try
to
take
some
of
that
into
the
conversation
as
well.
So
we'll
my
expectation
is
that
the
working
session
will
be
partly
around
this
sort
of
infrastructure
work
to
to
manage
the
code
of
conduct
and
then
also
the
moderation
team
discussion
that
we
have
and
try
to
make
some
more
progress
on
these.
A
Progress
we're
just
kind
of
near
the
finish
line
on
some
of
them
and
just
need
to
get
over
the
the
last
few
yards.
So
cool
I,
don't
know
if
there's
anything.
J
Oh
the
script
itself
as
far
as
I
know,
it's
now
just
hinging
on
one
or
two
technicalities
where
effectively
there
was
a
very
recent
first
push
that
rebased
it
to
work
on
the
2.0
Upstream
patch,
whereas
everything
previously
had
been
set
up
to
work
based
on
the
2.1
and
then
in
a
diff,
effectively
undoing
sort
of
unrolling
the
content
back
to
where
we
actually
started
from.
So
if
we
can
just
return
to
to
the
2.1
basis,
then
effectively
I
think
we're
completely
sorted
on
that
one.
Finally,.
A
Great
thank
you
for
your
help.
Emily
appreciate
it
your
eyes,
cool
and
then
the
next
one
pull
request.
851
is
basically
waiting
for
this
other
stuff
to
land,
and
then
we
will
likely
just
close
that
issue
as
we
will
be
incorporating
the
the
changes
that
were
born
out
of
that
so
I'm
going
to
jump
to
the
next
issue
then,
which
is
8
15..
This
is
license
check,
support
and
tooling.
Oh
sorry,.
A
A
Maybe
so
we
might
ping
lfit
about
it,
make
them
aware
of
it
and
see
about
incorporating
into
LFX
tooling,
but
I'm,
going
to
double
back
with
Michael
who
opened
this
issue
and
see
if
this
is
something
that
we
should,
you
know
be
incorporating
into
the
opengs
Foundation
here
in
terms
of
just
you
know,
regular
checks
on
what
we
have
here.
A
Great
the
next
one
is
clarify
requirements
around
code
of
conduct
violation.
This
has
been
around
for
a
while
I
think
that
essentially
here
we've
got
a
a
an
old
checklist
that
we're
kind
of
waiting
to
land.
Some
of
these
things
that
we've
been
working
on
and
then
double
back
on
this
one
to
make
sure
we've
got
everything
covered
so
that
one's
kind
of
just
sitting
around
at
the
moment.
A
So
unless
anybody
has
anything
on
those
previous
items,
we
can
move
on
to
the
other
items
that
we
kind
of
added
at
the
at
the
end
of
the
agenda
here.
A
The
first
one
listed
is
the
Grace
Hopper
open
source
day.
I
know:
we've
we've
participated
to
some
extent
in
the
past
Paula.
Do
you
want
to
give
us
an
update
on
on
the
live
stream
here.
I
Sure
the
call
for
proposals
and
projects
is
open
on
the
website
now
and
I.
Just
wanted
to
ask
for
advice
and
discussion
from
this
group
as
to
whether
we
should
have
a
coordinated
effort
to
nominate
projects
or
just
make
that
information
available
to
all
the
projects
and
they
can
self
nominate
and
I'm
also
happy
to
support
any
of
the
projects
who
want
to
engage
in
that
activity.
A
Sounds
good
I
know
in
the
past,
with
some
of
these
things,
like
Brian
Warner,
with
the
open
source.
What
was
it
I
can't
remember
what
it
was
called,
but
there
was
like
one
for
docs
and
stuff
I
think
it
was
a
Google
open
source
day
thing.
He
would
maybe
open
up
issues
on
different
projects.
Main
repos
I
know
Claudio
just
did
that
exercise
for
the
collab
Summit
I,
don't
know
if
we
want
to
just
kind
of
do
that
sort
of
approach.
I
I
I
can
I
can
take
that
on
and
work
with
Claudio
to
get
an
example,
and
thank
you.
G
A
Four,
all
right,
quick
next
here
we
have
the
collab
Summit
discussion.
Mateo.
You
brought
this
up
around
the
open
source
Summit
in
Europe,
but
I
don't
know
if
there's
also
anything,
we
need
to
talk
about
or
want
to
talk
about
here
about
North.
A
B
Oh
I
just
wanted
to
say
that,
because
people
completely
missed
that
a
lot
of
people
missed
the
deadline
for
applying
to
speak
at
open
source
submit
openjess
word
in
North
America.
If
you
want
to,
if
you
plan,
to
apply
that's
kind
of
the
time
to
apply
for
the
one
in
Europe,
so
they
I
think
the
cfp
ends
at
the
end.
At
the
beginning
of
May
before
the
next
one
starts,
which
it's
a
little
bit
unfortunate,
but
I'm
not
making
those
times
so
I
can
probably
get
to
to
comment
on
them.
B
Okay,
it's
a
little
bit
unfortunate,
but
that's
how
I
understand
why
they're
doing
it
and
I
will
they
probably
need
to
do
it
even
sooner
probably,
if
it
was
me,
I
would
probably
do
it
even
sooner,
but
the
end
result
is
you
need
to
apply
before
that,
so
yeah
just
make
that
happen
essentially,
and
then,
if
we
plan
to
have
an
open
source,
a
collaborative
Summit,
we
should
start
vehicleating
that
idea
to
the
per
tour
project.
B
So
because
I
don't
think
it's
in
it's
it
I,
don't
think
it's
a
lot
of
people.
Radar
I
was
in
not
gstsc
convo.
Last
last
week
and
I,
don't
think
anybody
had
a
clue
essentially
so
on
on
that
one
specifically
so
we're
we
need
to
do
some
some
work
and
spreading
that
info
essentially.
E
A
B
Know
the
dates
are
different,
though.
So,
if
you
look
at
open
source
Summit
and
if
you
look
at
it
I
think
the
dates
are
slightly
different.
So
we
are
doing.
We
are
doing
the
one
in
May
in
in
Vancouver
before,
because
the
conference
is
10,
12,
10,
11
and
12th
of
May,
and
we
are
doing
it
on
the
9th.
So
people
can
essentially
travel
in
on
the
eighth
and
then
travel
out
on
the
12th.
B
It's
kind
of
saying
the
full
week,
essentially
for
the
one
in
Bilbao
it's
the
conference
is
19
to
21st.
So
it's
a
full
week
essentially.
So,
if,
if
we
want
to
keep
some
doing
something
similar,
it
will
even
need
to
be
because
if
it's
on
the
18th
the
day
before
people
need
to
travel
in
on
the
Sunday
which
I
don't
know
if
it's
good
or
bad
for
you,
but
it's
it
is
what
it
is.
Okay
and
on
the
22nd.
There
is
a
reverse
problem,
which
is
people
will.
B
A
A
All
right
interesting:
well,
we
have
time
and
and
Robin
the
open
source.
Summit
EU
cfp
is
already
open,
but
I
expect
that
openjs
world
cfp
is
further
down
the
line
not
anytime
soon.
E
I
E
A
Okay,
so
we
should
let
people
know
and
I
I
promise
not
to
miss
that
one.
A
Anything
else
you
want
to
talk
about
about
collab,
Summit
Claudio
in
North,
America
or
anything
we
want
to
discuss
or
raise
or
whatever
nothing
aware
so
far.
Okay,
great.
A
F
D
F
Especially
if
there's
a
not
you
know
two
weeks
worth
of
nominations,
I
think
a
week
to
decide
on
your
vote
is
probably
plenty,
especially
if
you
especially
people
who
might
not
be
around
for
that
week,
are
able
to
get
their
vote.
You
know
cast
their
vote
early.
A
Yeah,
that
makes
sense,
so
we
think
two
week,
two
weeks
open
for
Nations.
A
A
Is
there
anything
else
we
need
to
like
discuss
about
this
see
Sarah
is
online.
So
that's
good.
This
is
for
the
position
that
Sarah's
in.
A
If
not,
then
I'll
just
I'll
get
an
issue
open
and
we'll
accept
nominations.
I
think,
last
time
we
may
have
used
a
form
in
the
past.
People
messaged
me,
but
that's
kind
of
messy,
so
I
think
a
form
would
be
great.
D
I
think
last
time,
Jory
put
the
form
together,
I'm
happy
to
put
the
form
together,
but
it's
kind
of
a
conflict
of
interest,
though.
A
Yeah
sure
I
I
ping
jewelry
a
week
or
so
ago
and
she
said
she'd
help.
So
hopefully,
if
I
just
get
her
some
of
the
details,
she
can
just
put
a
form
together
and
then
I.
A
So
I'll
get
that
rolling
and
we
should
circulate
it,
but
I'll
work
with
Jory
and
Robin
on
what
we
need
to
do.
There
send
out
emails
and
stuff
we'll
get
that
rolling
cool
anything
else
that
we
need
or
want
to
talk
about.
A
You
know
I'll
just
reiterate
that
on
the
working
session
next
week,
we'll
we'll
work
on
this
code
of
conduct,
stuff,
the
infrastructure,
the
patching
and
whatnot
and
then
the
moderation
team,
stuff,
I,
updated.
The
meeting
schedule
issue
already,
which
has
some
links
to
the
specific
issues
and
PR's
that
we'll
look
at.
E
A
Yep
yeah,
please
join
if
you're
interested
there's
a
calendar
entry
with
the
the
zoom
link
and
everything.