►
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
Excellence
all
right,
I
believe
that
we
are
live
so
thanks.
Everyone
for
joining
another
episode
of
the
openjs
foundation's
Cross
project
council
meeting
today
is
the
28th
of
March
2023,
and
we
can
get
things
started.
Do
we
have
any
announcements.
B
Not
a
real
announcement
but
I'll
remember
and
we're
approaching
the
you
know
the
end
of
the
applications
for
the
collaboration
standards
Summit
offer
sessions,
but
I
will
try
to
you
know,
send
another
email
to
this
PC
private
list,
another
memo
Aussie
to
some
of
the
organizations.
If
anybody
needs
more
time
and
be
more
than
happy
to
send
a
little
bit,
otherwise
they
would
start
you
know,
planning
the
time
and
etc
for
each
session
or
created
the
actual
schedule
for
the
summits
yeah.
That's
it.
A
Yeah
and
that
thank
you,
Claudio.
That
reminds
me
I'm,
going
to
add
something
to
my
to-do
list
to
figure
out
there.
Any
CPC,
collab,
Summit
stuff,
but
I
think
definitely
want
to
do
a
security
related
one.
So
I
will
make
a
note
of
that.
Any
other
announcements.
C
C
So
it'll
be
a
lot
of
fun
a
lot
of
folks.
There
Vancouver
is
equal,
City
and
then
you'll
see
we'll
be
in
Spain
in
September,
and
it's
maybe
a
little
confusing.
But
cfps
will
open
for
that
in
the
next
few
weeks,
but
make
sure
you
yeah
you
get
those
sessions
to
Claudio
on
GitHub
for
the
collab
Summit
May
9th
in
Vancouver
we're
still.
We
still
have
a
few
slots
that
were
putting
some
speakers
in
for
openjs
World,
but
it's
coming
together
nicely.
A
I'm
going
to
see
a
P4
this
world,
like
I,
can
write
openjs,
World,
EU
and
that's
cool,
then
sometime
soon,
okay,
cool
all
right.
There
are
a
couple
of
notes
great.
If
there
aren't
any
other
announcements,
I
guess
I'll
ask
if
there
are
any
board
updates,
Sarah
Robin.
A
No
we'll
take
a
few
minutes
in
private
session
to
review
the
board
meeting
slides
cool.
So
if
we
get
into
the
agenda,
oh
sorry,
go
ahead.
Robin
I.
C
Think
I
I
don't
know
if
we
covered
on
a
board
update
but
I,
don't
know.
If
many
of
you
knew
that
Todd
Moore
left
IBM,
he
was
the
president
of
the
openjs
board
and
Todd
is
now
at
the
Linux
foundation,
and
so
we
have
a
new
IBM
director,
Max
Maximilian
at
IBM.
So
that's
great!
So
just
some
changes
there
and
you'll
see
Todd,
probably
more
visible
at
the
Linux
foundation.
So.
A
Great-
and
that
does
remind
me-
we
have
another
announcement
that
we
should
make
about
Ben
joining
as
well.
Yes,.
C
A
D
Amazing,
maybe
this
is
telling
you
but
I'm
not
sure
I
may
have
been
on
my
first
week,
but
the
little
bit
of
a
meeting
overload
currently
so
yeah,
maybe
but
I,
don't
think
I've
met
a
lot
of
you
before
so
anyway,
I'm
one
week
week
and
a
couple
days
in
so
working
really
closely
with
Robin
currently
and
yeah.
It's
it's
great.
D
A
couple
meetings
with
some
folks
on
on
this
call,
including
Joe,
just
to
get
to
know
the
work
a
little
bit
better,
but
yeah
really
happy
to
be
here.
There's
a
lot
I,
don't
know
still
so
if
I'm
missing
anything
like
I
won't
feel
bad.
If
you
call
me
out
that's
how
I
learned
so,
please,
let
me
know
Robin.
C
A
Yeah
happy
to
have
you:
Ben
will
not
fault
you.
If
you
don't
know
something
our
our
documentation
is
sometimes
in
weird
places,
yeah
cool,
great
excellent,
all
right.
Well
with
that,
we
will
jump
into
the
agenda.
The
first
item
I
have
on
the
list,
is
10
29
issue,
10,
29.,
Ben
Hutton,
opened
this
a
couple
of
weeks
ago.
Is
a
project
okay
to
use,
I.
Think
the
the
contributor
Covenant
code
of
conduct
2.1
before
openjs
foundation.
A
Does
this
shouldn't
be
a
Blog
Toby
says
this
should
be
a
blocker
to
onboard
you
can
be
resolved.
A
You
know,
I,
think
that
our
goal
is
to
get
to
2.1
and
I
think
that
we're
really
really
close.
So
while
I
think
this
is
a
good
question,
I
think
it
could
be
moot,
hopefully
in
the
not
too
distant
future,
but
I
mean
maybe
the
question
Still
Remains.
If
the
contributor
Covenant
increases
you
know,
do
we
have
any
restrictions
on
projects
to
adopt
the
newest
one
before
we
get
around
to
you
know
officially
adopting
it
as
well.
A
Would
too
I
would
say
maybe
a
case-by-case
basis,
but
in
general
it'll
be
fine,
I
mean
I,
guess
I
would
expect
that
there.
If
there
was
some
issue,
we
would
bring
it
up
and
talk
about
it,
but
otherwise
the
expectation
is
that
it
should
be
fine.
B
Is
there
any
possible
issue
the
code
be
brought
because
of
a
project
adopting
the
New
Covenant
code
of
conduct,
while
the
rest
of
the
foundation
is
not
yet
under
the
same
umbrella?
Just
wondering.
A
I'm
sure
that
there's
something
that
I
can't
think
of
anything
you
know
I
think
just
yeah
I
mean
I,
can't
think
of
anything
specific.
C
A
That's
what
I
was
thinking
about
too,
but
I
think
the
changes
that
we
end
up
trying
to
work
on
are
specific
to
our
situation,
where
we
kind
of
sit
above
the
projects,
but
projects
themselves,
probably
I,
wouldn't
expect-
would
run
in
through
such
issues,
so
yeah
I
think,
generally
speaking,
it
would
seem
fire
cool
if
anyone
wants
to
comment
further
on
that
issue
feel
free
I'll,
if
not
I'll,
try
to
remember
to
put
something
in
there
as
well
and
we'll
keep
moving
on.
A
A
I
see
some
comments
at
the
end
here,
I,
don't
know
Ben.
If
you
have
any
yeah.
D
I
can
speak
to
this.
We
implemented
spandex
I'm.
A
Sorry
I
see
Sean
is
waiting
actually
in
the
in
the
in
the
waiting
list
too.
So
we
can
all
talk
more
about
it,
but
go
ahead.
Ben!
Oh.
D
Yeah
so
I
think
we've
got
a
decent
solution
for
this
using
spendesk,
which
allows
you
to
have
virtual
credit
cards
that
have
limits
in
it.
The
the
funky
part
here
right
is
we're
trying
to
enable
billing
on
an
organization-
that's
not
under
open.js,
and
so
it's
detailed
in
there,
but
I
basically
had
to
be
at
it
as
a
billing
manager,
and
we
use
that
virtual
credit
card.
So
I
think
the
things
that
are
outstanding
here
is
one,
maybe
two
things
on
my
side.
D
One
is
just
making
sure
that
this
is
accounted
for
internally
and
on
our
budgeting
to
the
right
code,
so
that
we
track
that
properly
and
the
second
is
figuring
out
how
to
have
not
my
email
address,
be
the.
E
D
Contact
and
have
it
be
one
that
is
more
than
one
person
has
access
to
so
that,
if
you
know
something
happens
to
me
in
the
future
right
that
those
things
don't
get
messed
up.
So
that's
we're
using
me
for
now,
so
that
doesn't
work
but
I
have
those
two
other
tasks
to
sort
out
and
Sean
nice
to
see
you
in
person,
yeah.
F
A
All
right
cool,
so
that
makes
sense
Ben
thanks
for
clarity
there
and
Mateo
comments
too,
that
no
jsword
might
need
a
similar
setup
too.
So
this
is
good
that
we're
making
progress
here
and
figuring
things
out
cool
excellent.
If
there's
nothing
else
to
add
there,
I'll
move
along.
F
Yeah
I
think
everything's
short
up
on
my
side.
If
there
is
like
a
like
a
shared
GitHub
account
that
needs
to
get
added.
I
can
do
that
as
well.
Instead
of
just
an
email,
so
feel
free
and
let
me
know
right.
A
Cool
and
again,
if
anybody
can
drop
any
notes
into
the
meeting
minutes,
that
would
be
really
helpful
and
then
I
can
just
keep
moving
on
here.
Issue
1003
is
next.
This
is
create
some
documentation
around
the
collaboration
model
of
openjs
projects.
We
talked
about
this
a
couple
of
weeks
ago.
C
And
I
volunteered
to
help
Mateo,
he
I
think
he
has
a
couple,
some
speaking
gigs
as
well,
but
I
think
we'd
all
love
to
have
something
drafted
and
sometimes
having
a
speaking
session
helps
Drive
deadlines
for
us,
so
I'll
work
offline
with
him.
Okay,
great.
A
Teo
and
Robin
on
this
about
speaking
sessions
too
cool
all
right,
that'll
be
great
next
on
here.
Yogi's
is
our
patching
script.
This
is
issue
910,
yes,
go
ahead.
E
So
all
of
the
issues
are
resolved.
Emaily
just
approved
the
plural,
quests
I
think
we
can.
A
Merge
it
great
Claudio,
it
looks
like
you
added
yourself
to
review,
but
I,
don't
think
that
you
have
reviewed.
So
if
you
want
to
take
a
look
at
that,
that
would
be
great.
A
Otherwise
we
got
a
bunch
of
reviews
here.
We
need
to
just
maybe
get
it
up
to
date
with
the
brace
the
base
branch
and
then.
B
Sorry
about
the
the
the
pr
com
yards
yeah,
that's
what
we
talked
about
I
think
he
added
actually
me
as
a
reviewer,
but
okay,
probably
yes,
either
way.
That
sounds.
B
C
E
A
Yeah,
so
why
don't
you
and
I
can
find
some
time
to
to
look
at
what
next
steps
are
and
I'm
happy
to
yeah,
of
course
sounds
good
looks
like
we
lost
Claudio,
but
they
are
joining
back
cool.
A
Great
and
that's
once
we
get
that
done,
we
will
be
able
to
move
forward
on
the
next
issue
as
well,
which
is
update,
contributor
covenants
to
v
2.1,
which
is
basically
just
waiting
for
us
to
get
some
of
this
other
stuff
in
place,
and
then
we
can.
We
can
move
forward,
I
think
that's
a
PR
that
will
probably
close
since
we'll
have
other
stuff
in
place
that
will
supersede
it,
so
no
need
to
get
into
that.
The
next
item
is
815.
A
This
is
license
check,
support
and
tooling.
I.
Think
the
last
thing
I
remember
talking
about
this
was
that
I
was
gonna.
Talk
to
you,
Michael
Dawson,
to
see
if,
if
this
is
something
that
would
satisfy
the
original
thoughts,
which
was
a
long
time
ago,
November,
26,
2021
and
I
think
the
LF
is
looking
at
integrating
it.
A
But
just
in
terms
of
like
our
use,
you
know
it's
just
something
that
we
would
want
to
just
adopt
as
an
individual
tool
or
think
about
the
LF
implementation
or
what
we
want
to
deal
so.
A
Sorry
this
is
a
license:
scanner,
IBM,
open
sourced
it
to
oasp.
It
finally
went
public
I
think
a
couple
of
weeks
ago,
and
so
it
is
a
license
and
legal
scanner,
and
so
it's
something
that
we
could
build
into
the
openjs
foundation.
At
least
you
know
for
our
projects,
so
I
don't
know
if
you
want
you
and
I
can
take
a
look
at
it
later
and
sure.
A
Income
and
it's
the
thought
like
like
new
projects
coming
in
or.
G
Yeah,
we're
always
creating
new
repositories
right,
and
so
you
know
yes,
scanning
deeply
for
licenses
might
might
be
nice,
but
less
complicated
is
just
hey.
We've
just
created
a
new
repo.
G
Did
we
create
a
license
for
it,
and
you
know
right
now
that
happens
several
times
a
month
and
do
we
have
a
license
every
time?
Well,
if
people
happen
to
think
about
it
or
not,
is
the
the
really
simple
the
the
simple
idea
I
had
is
like
if
we
had
something
that
just
says
do
our
do
our
repos
have
the
basic
requirements
that
we
have
for
projects
or
not,
and
it
would
be,
it
would
help
maintainers
know
if
there's
any
problems.
A
Yeah
interesting,
and
so
that
could
be
something
that
we
run
across
all
of
our
projects
on
some
sort
of
time
schedule
just
to
check
orgs
and
repos
not
too
deeply.
But
but
you
know
to
see
if
everything
lines
up.
G
Yeah,
it
would
just
be
a
a
you
know
as
a
project.
The
note
project
could
run
that,
like
you
said
on
an
interval,
and
it
would
tell
us,
oh
by
the
way
you've
got
these
three-
that
don't
have
licenses
right
and
you
could.
You
could
expand
that
I.
Think
like
the
Deep
license.
Checking
is
a
much
more
complicated
thing
right
like
that
comes
out
with,
like
hey,
you've
got
these
licenses
and
those
licenses,
and
then
you
got
to
figure.
G
Is
that
okay
or
not,
and
is
it
a
false,
is
a
duplicate
like
and
then
there's
different
names
for
all
sorts
of
license?
So,
but
whether
but
not
having
one
at
all,
is
a
pretty
simple
check
that,
like
somebody,
should
action
right
away
and
say:
oh
well,
if
we
have
none,
we
you
know
we
really
should
have
one
right
same.
You
could
make
the
same
thing
for
like
well,
we
need
to
have
a
code
of
conduct.
G
A
So
I
can
see.
This
is
like
two
separate
things.
You
know
one.
We
could
use
it
at
the
foundation
to
just
kind
of
every
once
in
a
while
survey
and
see
what
what
things
look
like
and
I
think
it
would
be
good
to
expand
the
code
of
conduct
as
well
and
just
make
sure
that
things
haven't
changed
without
us
noticing,
and
then
you
know
we
we
have
some
issue,
but
then,
additionally,
maybe
another
benefit
could
be.
A
We
could
develop
some
guidance
in
our
project,
Resources
directory
about
projects
using
these
scanners
and
how
you
know
some
some
cursory
instructions
on
how
to
use
it
and
say,
for
example,
the
node.js
or.
G
That's
really
why
I
opened
it
here
is
like
the
project
could
come
up
with
something
LJ
said
he
had
a
tool
yeah,
but,
like
my
thought,
was
the
foundation
should
be
interested
in
care
enough
about
these
minimal
helping
with
these
minimal
checks
that
like
we
could
encourage,
we
could.
We
could
increase
the
chances
significantly
by
doing
something
that
each
project
didn't
have
to
figure
out
themselves.
A
A
Great
all
right
cool.
Well,
we
have
the
tool
we
can
look
and
see
how
it
serves
either
of
those
purposes
and
see
about
moving
forward.
A
Great.
The
next
item
here
is
786
issue:
76
clarify
requirements
around
code
of
conduct
filing
this
one's
just
been
open
for
a
while
there's
a
checklist,
a
few
comments
down
that
we're
basically
going
to
review
once
we
get
the
patching
script
in
place
and
the
code
of
conducts
sort
of
stabilized
and
then
we'll
go
through
this
checklist
and
see
if
there
are
things
that
we're
missing
and
kind
of,
maybe
build
some
issues
out
of
that.
A
So
this
is
kind
of
just
staying
open
for
the
time
being,
but
I
expect
we'll
be
able
to
close
it
sometime
soon
and
then
I
added
that
in
the
wrong
spot,
I'm
going
to
put
that
there,
but
we'll
leave
that
board
slide
review
for
private
session.
But
there
is
an
issue
in
the
standards
repo
issue
213
jewelry
created
this.
This
is
secure.
The
web
forward,
Workshop
call
for
papers,
I.
C
C
It's
June,
7th
and
8th
in
London
at
the
Microsoft
reactor
space
and
openjs
and
openssf
and
OAS
are
partnering
with
w3c
on
this.
So
April
24th
is
the
cfp
deadline.
Essentially
to
get
your
papers
in
space
is
limited,
so
we'll
be
looking
at
at
that.
So
when
you
do,
if
you
do
want
to
come,
you'll
be
sent
a
little
form
that
asks.
Why
do
you
want
to
come
because
they
are
really
interactive
discussions
again,
a
little
bit
different
than
in
a
typical
conference,
so
our
capacity
is
about
120.
A
And
so
what
is
the
ask
then,
for
this?
Is
this
for
attendees
or
actual
like
Workshop
submissions.
C
A
A
Usually
at
this
point
we
try
to
figure
out.
What's
what's
on
for
the
working
session,
I
think
last
week,
I,
don't
remember
what
happened,
but
I
think
maybe
I
was
busy
and
stuff
was
going
on
and
we
didn't
do
a
working
session
if
I
remember
correctly,
but
oh
yeah,
we
did
like
kind
of
an
async
working
session
and
so
yeah
geese
has
made
more
progress.
A
I
expect
that
that
maybe
he
and
I
can
find
some
time
before
the
next
working
session
get
some
of
that
stuff
in
place,
and
then
what
I
propose
is
that
we
figure
out
the
remaining
items.
That's
on
the
kind
of
code
of
conduct
stuff,
which
includes
like
the
moderation
team
and
and
and
start
to
kind
of
document.
A
What
that
would
look
like
and
and
just
make
sure
we
kind
of
are
buttoning
up
our
code
of
conduct,
issues,
outstanding
issues
and
and
concerns,
and
that
we
kind
of
wrap
up
that
that's
a
chunk
of
work
which
I
feel
like
has
been.
You
know
a
box
in
our
garage
that
we
keep
wanting
to
go
through,
but
we're
there
we're
we're
really
close.
A
So
that's
great
any
objections
to
that
for
the
working
session
for
next
week
or
any
other
thoughts
or
anything
not
I
will
I
will
book
that
in
the
issue.
That's
has
the
schedule
and
I'll.
Add
it
here
as
well,
so
cool
that
kind
of
wraps
up
the
agenda
and
whatnot
I
guess
the
one
thing
I
should
mention,
because
there
is
the
regular
review,
our
dates
and
reminders.
Sarah's
board
seat
expired
a.
E
A
Or
more
ago
about
a
month
ago,
and
so
we
still
need
to
get
that
election
going.
So
that's
that's
top
of
mind
and
then
I
think
the
CPC
chair
ends
at
the
end
of
April.
So
we'll
want
to
start
to
work
on
that
as
we
start
to
approach
April
as
well
so
and.
A
A
Not
I
will
end
the
stream.
Thank
you,
everybody
for
joining
us
and
we
will
see
you
next
time
around.