►
From YouTube: OpenJS Foundation Cross Project Council 2023 02 14
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
A
B
Yeah
I
think
on
this
one.
The
thing
I
I
would
suggest
we
do
is
we
that
we
github's
helped
us
different
projects
in
various
ways
in
the
past
and
said
this
like?
This
is
a
subset
of
the
ways
they
could
help
us
and
so,
rather
than
like
kind
of
a
building
and
official
process
and
set
up
and
structure
for
this,
especially
one
that
like
gets
money
involved,
which
is
somewhat
hard,
I,
think
codifying
in
our
kind
of
there's
a
menu
somewhere.
I
forget
I
forget
what
the
document
is.
B
I
I'm
not
actually
sure
on
it,
but
there
is
a
menu
of
like
infrastructure
that
the
foundation
provides
somewhere
and
just
codifying
there
that,
like
the
get
you
know,
GitHub
and
the
foundation
have
like
some
sort
of
relationship.
Also
generally
GitHub
is
very
open
to
helping
open
source
projects,
or
at
least
some
like
subset
of
Open
Source
projects
and
generally
I-
think
the
ones
under
the
openjs
foundation
fall
under
that
umbrella.
A
B
You
know
the
like,
like
get
you
a
team
Enterprise
or
a
team
plan
on
GitHub
for
your
for
your
org.
If,
then,
that's
like
something
that
we
can
kind
of
help
work
with
GitHub
on
or
you
know
very
various
other
things
that
GitHub
offers,
we
can
kind
of
work
with
you,
I
I
I
can
try
to
find
what
document
that
is
in
PRN
I.
Think
it's
in
the
CPC
repo
but
yeah.
A
C
C
B
B
It
is
that
previously
for
to
start
a
code
space,
you
had
to
be
a
member
of
the
org
that,
like
had
like
contributor
level
access
to
that
repo
I,
don't
know
if
that's
still
the
case,
because
I
know
they
made
some
changes
around
like
it's
not
attached
to
a
repo
anymore.
So
maybe
that's
not
the
case
anymore,
like
maybe,
if
you're
a
member,
you
still
have
access
through
the
org,
but
otherwise
you
compare
yourself
I'm,
not
sure
yeah.
D
C
B
D
B
B
D
A
C
E
A
E
So
yeah
this
is
this.
Is
me
I
I
have
a
very
recently
or
not
recently
anyway,
stumbled
on
a
lot
of
different
conversations
around,
especially
on
the
web,
but
also
in
person
of
people
not
really
understanding
what
the
difference
between
a
project
like
node.js,
okay,
which
is
doesn't
have
a
it,
does
not
have
funding,
does
not
have
staff
working
full-time
for
the
project.
You
are
not
hired
to
be
part
of
the
of
the
node.js
I.
Don't
know
JS
team
essentially
versus
a
project
like
react.
E
That
is
essentially,
you
are.
You
are
hired
by
Facebook
or
versaille
to
work
on,
react,
okay
and
it's
essentially
a
company
product,
okay,
so
I-
and
this
is
a
fundamental
difference
in
terms
of
expectations
and
even
what
you,
in
terms
of
expectation
of
users,
what
they
can
expect
when
interacting
with
this
project,
what
are
their
essentially
writes
to
some
extent
on
when
contributing
to
those
projects
between,
because
there
is,
you
know
a
lot
of
things
to
consider.
For
example,
like
is
there
a
CLA?
Is
there
a
dco?
E
Is
there
what's
the
licensing
of
my
contribution?
What
would
happen
if
the
company
decided
to
take
that
code
and
make
it
all
private
like
it
happened
with
elastic
and
mongodb?
Okay,
I'm,
just
I'm
just
flagging
example,
there
was
very
recently
a
thread
with
a
Twitter.
This
was
I
created
this
after
a
Twitter
thread
with
some
folks
where
there
was
like.
E
Oh,
there
are
fantastic
commercial,
open
source
companies
and
they
were
company
in
there
that
were
listed
companies
that
are
actually
open
source
companies
like,
for
example,
confluent
with
Apache
Kafka,
and
they
were
putting
to
the
next
putting
together
with
elasticsearch
or
mongodb,
and
they
were
just
like
nope.
These
are
not
open.
Source
like
these
are
not
open
source
according
to
the
to
any
of
the
definitive
to
the
common
knowledge
of
Open
Source
in
the
in
the
public.
So
again,
I
just
I.
E
Just
think
there
is
a
lot
of
I
think
you
know
if
we
could
describe
in
some
ways
what
is
the
contribution
model
for
for
us
and
what
would
be
the
best
and
what
are
the?
What
is
the
governance?
What's
the
expectation
and
so
on
and
so
forth,
I
think
it
will
help
us
I
think
it
will
help
us
a
lot.
The
community
to
some
extent
I,
think
there's
a
massive
amount
of
Education
needs
to
be
done
in
this
front.
That's
not
being
done
at
the
moment.
A
B
E
B
B
I.
Think
being
careful
about
that,
because
that
is
a
very
big
discourse
that
if
we
want
to
do
something
on
that,
I'm
totally
for
it.
But
that
is
like
a
very
big
discourse
that
can
get
very
thorny,
because
a
lot
of
people
have
a
lot
of
opinions,
including
me.
I
have
very
strong
opinions,
unsurprisingly,
yeah
I,
just
don't
know
that
specific
slice
of
it
I,
don't
know.
B
If
we
want
to
engage
in
just
because
I
don't
know
if
we
have
the
time
and
energy
for
that,
but
I
I
totally
agree
about
like
here
is
how,
like
a
lot
of
corporate
open
source
projects,
are
going.
Here's
how
like
Community
governed
projects,
are
going
and
then
there's
also
like
this
other
slice
of
like
I.
Don't
know
it
exists,
it's
open,
you
can
use
it.
I
might
accept
all
requests
open
source
I
think
that
defining.
B
A
I
mean
I
love
this
it's
a
hook
that
I
often
use
in
my
sort
of
short
pitch
for
openjs,
but
having
it,
you
know,
elaborated
in
sort
of
more
Community
content
filled
in
I'm
happy
to
hold
the
pen
if
we
had
a
working
session
or
if
you
all
want
to
do
a
brain
dump,
that's
one
thing:
I
can
do.
You
know
is
right.
A
E
Look
for
me,
it's
I
have
seen
like
I
have
often
got
the
question
of,
but
what
the
purpose
of
having
the
an
entity
like
the
open
source
Foundation
to
all
the
projects.
Okay
and
I-
got
these
questions
so
many
times,
and
it's
it
goes
to
the
point
of
oh.
Maybe
we
should,
you
know,
write
some
of
those
things
down.
We
take,
we
understand
them
a
lot
of
the
people
in
the
project
understand
them,
otherwise
they
wouldn't
be
here,
but
we
need
to
do
something
about
it.
Okay,
so.
A
E
I
would
like
to
be
involved,
but
I'm,
not
usually
some
of
the
like
I
the
way
meeting
rotates
how
for
them
more
or
less
I
can't
so
it's
it's
Pro,
it's
too
late,
like
I'm,
if
I'm
not
stop
in
25
minutes.
So
maybe,
let's
see
if
there
is
one
that
works,
that's
great.
Otherwise
we
can
schedule
something
yeah.
B
A
A
A
A
Let's
see
I
I
was
going
to
save
the
code
of
conduct
patching
for
when
Toby
could
join.
Toby's
can't
make
it.
If
you
look
in
the
cross
project,
Council
slack,
he
just
gave
an
update,
license,
support
tooling.
We
should
be
getting
an
update
from
Joe
because
there's
been
some
work
done
on
a
tool
in
owasp
with
IBM,
that's
being
contributed
back
to
the
community,
so
that's
something
we'll
be
building
from
and
I.
Don't
think
yuggies
can
make
it.
But
if
we
can
make
progress
on
issue
910
and
all
of
the
related.
A
E
F
What's
the
current
2.1
Upstream
version
and
that
explicitly
also
documents,
what
the
differences
are
that
we
have
that
apply
to
the
code
of
conduct.
So
my
preferred
way
of
having
this
Advanced
would
be
the
first
minimize
the
difference
between
the
2.1,
then,
because
we're
starting
out
from
a
version
that
that
is
nominally
a
copy
of
the
Upstream.
F
Even
if
the
Upstream
says
change
to
to
what
is
now
known
as
the
2.0
and
then
we
say,
for
instance,
that
this
is
that
that
our
Baseline
is
2.0
and
then
2.1,
and
this
is
the
difference
that
we
are
using
and
in
that
context,
maybe
we
want
to
talk
about.
Finally,
whether
we
want
to
do
drop
the
project
where,
from
where
we
are
using
it
or
explicitly
somewhere,
include
the
language
that
we
want
about
what
the
permaband
really
might
mean.
F
E
D
I
mean
the
initial
impetus
to
do
this
with
the
technological
solution
was
because
the
Upstream
does
make
changes
without
like
explicitly
tagging
them
or
notifying
and
so
like.
We
wanted
to
have
a
way
to
make
it
really
easy
to
to
adapt
to
those
changes
without
having
to
read
the
entire
document,
the
entire
new,
updated
document
and
figure
out
like
what
our
changes
were,
what
their
changes
were,
and
so
on
and
I
agree.
D
It's
certainly
a
lot
of
work
has
gone
into
this
solution,
but
I
think
it
seems
like
the
sort
of
work
that
is
a
one-time
cost
that
will
pay
off
over
time.
If
and
when
more
more
changes
are
made
to
the
upstream
or
to
to
ours.
So
I
I
still
would
like
to
see
it
go
forward.
I
agree.
We
need
to
be
able
to
clearly
see
the
diff
and
we
need
I,
like
your
PR
that
decreases
the
the
changes
right.
D
B
B
Add
it
I'm
I'm,
not
sure,
because
it
does
look
like
output
file
path
is
go
to
conduct.md,
so
I'm
pretty
sure
that
just
like
it'll
automatically
it'll
get
pull
requested
as
soon
as
we
merge
this,
and
then
we
just
accept
that
merge
or
that
pull
request
so
like
I,
yes,
I,
agree
that
we
shouldn't
be
deleting
it
but
I,
don't
I.
Think
in
spirit.
That's
just
a
like.
The
deletion
is
a
temporary
step,
rather
than
a
we're
actually
deleting
the
code
of
conduct.
B
B
F
But
I
mean
I
want
to
say
that
the
current
one
doesn't
do
is
is
provide
us
with
any
automation
to
to
recognize
when
a
a
difference
has
been
made.
So
I
would
say
that
you
know
with
the
first
step
here,
ought
to
be
some
Crown
job
that
effectively
files
an
issue
that
hey
here's.
You
know
the
update.
Upstream
has
changed.
Here's
the
div,
that's.
B
A
one-line
addition
in
the
yaml
file:
that's
in
that
PR,
it's
you
literally
said
cron
and
then
that
this
will
run
every
every
time
and
then,
if,
if
there
is
a
change
rate,
that's
what
the
Gregor's
Creator
Creator
update,
pull
request
action
does!
Is
that
it
if
there
it
runs
through
the
full
job
and
then,
if
there's
something
different
on
that
on
disk
in
that
VM
that
it's
running
in
it
will
create
an
update
that
says:
hey,
there's,
there's
a
there's
an
update
and
like
PR's
it.
B
B
A
B
I
think
the
reason
that
we,
like
I
I,
I,
totally
understand
that
I
think
we've
had
this
human
problem
for
a
long
time,
and
it
has
not
gotten
solved
like
we've
had
this
since
amp,
and
nobody
has
nobody.
No,
no.
Nobody
on
the
human
side
has
been
able
to
solve
it
with
human
human
problem
solving,
and
so
this
is
a
you're
totally
right,
like
I
I,
agree
that
it
is
that
we
have
not.
B
B
That
is
something
that
is
very
important
for
this
group
like
reducing
how
much
we
have
to
do,
because
we
don't
output
a
lot
and
there
are
some
things
that
do
need
to
get
to
get
fixed,
and
this
is
this
is
a
pretty
good
example
of
that
specifically
I.
Think
this
is
to
like
address
concerns
from
amp
when
they
had
a
more
aggressive
COC
that,
like
I'm
totally
fine
with
us,
adopting
and
like
adopting
their
language
and
like
we
haven't
solved
that
problem
of
that,
using
adopting
that
more
aggressive
language.
F
I
mean
my
view
of
how
why
just
got
blocked
is
that
we
started
talking
about
having
an
automated
solution
and
then
all
further
discussion
got
blocked
way
too
fully
automated
solution,
rather
than
actually
talking
about
the
the
content
of
it.
So
you
know
five,
so,
whatever
solution
we
end
up
with
that,
actually
works.
Let's
just
go
with
it.
That's
fair.
A
D
B
D
So
we're
gonna
land,
Emily's
PR.
First,
that
minimizes
the
diff,
then
we're
going
to
land
this
patching
script,
which
is
972
and
then
we're
gonna,
make
sure,
and
maybe
as
part
of
972
or
or
after,
but
either
way
in
short
succession.
We're
going
to
make
sure
that
Emily's
comments
are
addressed
about
be
when
you
view
the
COC
having
a
very
quick
way
to
figure
out
how
it
was
generated
and
what
the
diff
is
for
n.
What
you
know
what
the
source
is.
Does
that
sound
writingly.
A
D
B
D
A
A
M
I
think
the
only
thing
I
think
Claudio
couldn't
make
it,
but
he
and
Roy
are
on
point
for
the
collab
Summit
this
year
and
we're
getting
space
and
all
of
those
requirements,
sort
of
sorted
out
right
now,
but
Roy
and
and
Claudio
will
be
on
point.
There
is
a
summit
repo
where
they'll
be
curating
content
with
you
all
so
stay
tuned
for
more
information
on
that
it
is
on
the
registration
page
for
openjs
world,
so
you
haven't
registered.
B
A
E
A
I
think
it's
all
up
to
you
on
how
you
want
to
use
your
travel
fund,
whether
it's
tickets,
the
folks
who
are
on
the
program
committee,
get
a
free
pass,
but
because
we're
not
taking
a
a
budget
commitment
on
the
conference
itself
or
a
micro
conference.
I
can't
sort
of
make
those
unilateral
decisions
anymore.
A
C
D
A
E
A
A
Have
a
lot
of
great
yeah
I
looked
at
the
spreadsheet,
a
lot
of
good
contributions
the
program
committee
will
meet.
They
will
also
leave
room
to
curate
content
to
take
into
account
diversity
of
topics
and
projects
and
people,
so
they
always
leave
themselves
some
wiggle
room
to
create
a
well-balanced
event.
A
A
E
C
A
A
D
C
B
E
D
A
That's
all
right,
we're
always
like
I've
got
baby
pictures.
I'll
share
those
cool,
yeah,
no
yep,
so
we
yeah
we've
been
hit
left
and
right,
but
yeah
lots
of
good
content
and
yeah.
We
do
love
a
lot
of
content
because
it
does
keep
our
our
blog
busy
for
probably
six
months
where
we
feature
some
of
that
stuff.
E
E
Okay,
like
a
lot
of
people,
have
been
pushing
hard
on
that
so
I'm
just
wanted
to
mention
also
firstify
one
of
the
first,
if
I
projects
plugins
that
have
security
list
today,
app
is
not
part
of
the
business
Foundation
data
security
list
today
and
a
lot
of
others
are
going.
Security,
listen
rise
and
later
there's
been
a
overlap
of
multiple
vulnerability
issues
submitted.
That
makes
this
big
update
cycle
for
everybody.
Openssl
did
last
week
too
so,
and
you
know
I'm
just
flagging
the
fact
that
you
know
if
you're
watching.
A
And
flag
for
Kylie,
if
you
want
something
retweeted
or
Amplified,
and
also
we
have
some
new
projects
on
Mastodon
as
well,
electron
node
us
so
checking
it
out
Sean
if
you're
interested,
let
us
know
Mastodon
yeah
for
sure,
okay,
Mateo
awesome,
all
right
thanks!
Everyone
for
joining,
see
you
next
time,
bye.