►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Cool
thanks,
everyone
for
joining
the
inaugural
2022,
open
js
foundation,
cross
project
council
meeting
just
grabbing
the
link
here
from
the
video
I'll
also
say
in
the
chat
here.
My
friends.
B
A
C
There
are
announcements-
great
yes,
openjs
world
still
moving
forward.
Of
course,
you
know
we're
always
checking
with
conditions.
The
linux
foundation
also
consults
with
the
epidemiologist
to
give
advice
as
well
and
we'll
keep
all
that
data
updated,
but
we've
updated
our
website
with
some
of
our
confirmed
featured
speakers
to
date.
So
that's
pretty
exciting
registrations
are
open.
So
if
you
would
like
to
buy
a
ticket,
we
have
for
in-person
and
virtual
virtuals
free
sponsorship.
There's
a
link
for
sponsorships
as
well.
C
C
So
if
you
think
about
june
6th
through
10th,
so
we'll
be
following
up
with
projects
on
how
they
would
like
to
shape
their
experience
for
collab
summits-
and
I
know
our
event
team
would
like
to
have
some
space
requirements,
sort
of
nailed
down
in
the
next
month
or
so,
and
then
the
next
thing
is
cfp's
will
open
next
week.
So
we'll
do
a
big
communication
blast
about
that.
C
Great
just
another
couple
of
things
just
that
from
a
linux
foundation
perspective
the
open
source
security
foundation,
open
ssf,
announced
a
great
mfa
project.
That's
multi-factor
authentication
where
they
handed
out
free
tokens
for
projects,
so
go
check
out
the
great
mfa
project.
C
I
know
they
provided
free
tokens
to
amp
electron,
node.js
and
webpack
as
long
as
many
more
so,
if
that's
something
your
project's
interested
in,
there
is
a
there's,
a
blog
on
the
open,
ssf
site,
it
links
to
github
and
then
there's
instructions
on
how
to
take
advantage
of
that,
and
you
may
have
saw
an
article
in
bloomberg.
There
is
a
white
house
meeting
next
week
with
the
tech
industry
on
security
and
the
linux
foundation
will
be
participating
in
that
as
well.
A
A
I
guess
I
sort
of
have
an
announcement,
but
maybe
it
doesn't
matter
because
they're
not
here,
but
I
think
that
we
have
a
new
cpc
member
that
I'm
supposed
to
welcome
and
it
happened
a
while
ago,
but
now
I'm
not
seeing
it
is,
it
still
is
the
meetings.
Is
the
issue
still
open?
A
No,
I
thought
I
oh.
It
was
a
pr
of
course,
so
I
will
say
it
now,
but
we
should
do
it
when
mike
samuel
is
actually
on
the
call.
But
mike
samuel
is
now
a
regular
cpc
member
yeah,
mike
yeah
cool
anything
else.
Anyone
wants
to
share
before
we
move
on.
A
What
is
this
all
right
cool?
So
if
I
jump
into
the
agenda,
the
first
thing
that
we
have
here
is
issue
815..
This
is
license
check,
support,
tooling,
michael.
You
opened
this
issue
around
november
26th.
Do
you
want
to
share?
What's
going
on
here.
D
C
Yeah,
I
have
an
update
from
brian.
He
couldn't
be
here
today,
but
he
let
me
know
that
the
lfx
tool
we
don't
have
anything
quite
in
place
just
yet,
although
I
think
it's
on
the
roadmap
there's
other
tools,
I
think
that
you're
all
familiar
with,
which
is
the
fossa
tool,
the
fossology,
which
is
free
and
what
are
those
tools?
C
Yeah,
but
I
think
some
people
had
maybe
some
thoughts
on
that,
but
I
think
the
guidance
I'm
sort
of
hearing
is
that
there's
it's.
It's
really
not
there's
really
not
like
a
silver
bullet,
and
there
are
some
sort
of
low
power
tools
that
help
and
some
are
free
for
open
source.
Some
of
the.
D
C
Of
paid
tools
that
you
may
you
know
have
been
familiar
with
in
the
past,
we
don't
have
subscriptions
for
it
currently,
but
I
think
that
the
general
gist
of
it
is
is
that
yeah
use,
maybe
some
of
those
load
power
power
tools,
but
don't
put
all
your
eggs
in
one
basket,
because
it's
hard
to
trust
a
lot
of
those
sort
of
low
power
tools.
D
Sorry,
I'm
still
not
clear
what
those
low
power
tools
are
like
in
this
case,
I
was
really
just
asking
for
something
simple.
You
could
point
at
an
org
and
say:
do
all
my
repos
have
licenses
or
not,
and
are
they
ones
that,
like
we've
said,
are
okay
right
because
we've
got
the
policy
that
says
this
is
what
you
should
have
and
if
you're.
C
F
D
I'm
just
asking
about
the
repos
right,
like
we've
got
a
bunch
of
repos
in
our
org,
and
we've
got
a
list
of
acceptable
licenses
as
per
foundation
policy,
and
it's
we
we
create
like,
especially
in
the
note
org.
We
create
lots
of
new
or
new
repos.
We
transfer
reposies
in.
So
it's
just
too
easy.
I
think
that
we're
going
to
miss
one
and
it
won't
have
a
license,
or
maybe
it
has
a
license
that
we
don't
think
is
on
our
list.
F
D
D
D
G
I
mean
you:
could
you
could,
but
what
you'd
want
to
do
is
set
it
up
as
like
a
cron
job
on
the
dot
github
repo
of
your
org,
because
you
don't
the
whole
point.
Is
you
don't
want
to
have
to
touch
individual
repos
right?
Exactly
github
actions
is
primed
for
that
you
certainly
could
make
a
github
action
in
the
dot
github.
C
G
G
You
certainly
wouldn't
want
to
like
automatically
send
a
pr
file,
an
issue
on
each
project,
but
the
other
thing
is
by
putting
in
the
dot
github
repo
you're
also
only
confining
it
to
your
own
organization's
repos,
which
means
there
wouldn't
be
a
single
place
to
put
it
for
all
of
the
open,
js
foundation
projects.
G
You
know
you
could
configure
it
that
way,
but,
like
you
would
sort
of
like
nvm
has
its
own
github
org
I'd
put
one
there
and
it
would.
You
know
I'd
use
the
action
there
and
then
it
would
tell
me
right
if
you
wanted
to
do
something
that
covered
all
opengs
foundation
projects.
You
also
wouldn't
need
permissions
or
courtesy.
I
think
it's
but
like
it
would
be
a
different
configuration
because
you'd
have
to
supply
that
list
of
repos.
D
H
Something
that
we
want
like
is
this
an
audit,
or
is
this
a
moving?
Is
this
something
that
we
want
would
want
as
a
permanent
part
of
the
github
like
this?
Is
a
ci
cd
thing
or
an
audit.
D
My
ask
was
from
the
as
a
maintainer
of
a
project
with
lots
of
repos
it'd,
be
nice
to
have
an
easy
way
to
tell.
If
there's
any
that
we,
you
know,
don't
have
a
license
to
chase
down
on
right,
and
you
know
I
could
see
we.
We
have
some
other
requirements,
like
you
know,
having
you
know,
links
to
the
code
of
conduct
to
you
know
that
stuff.
That
could
be
an.
D
G
G
It
is
designed
for
me
and
it
scans
every
repo
that
I
have
access
to
on
all
of
github
and
for
you
know
or
where
I
is,
the
user
right
who
provides
the
github
token.
Major
league
hacking
is
mlh
yeah,
it's
a
fellowship
program
and
the
and
it
sort
of
report
gives
you
a
dashboard
on
your
in
your
terminal
of
metrics
across
the
repo.
So
I
can
like
sync,
my
branch
protections
and
things
like
that.
An
easy
metric
to
add
would
be.
G
G
Well
across
because
then
it
doesn't
care,
it's
like
my
personal
workflow,
never
is
confined
to
a
single
user
or
a
single
org.
It's
spread
across
everything,
and
so
I
built
it
for
that.
So
if
that
would
help
I'd
be
more
than
happy
to
work
with
you
offline
on
that.
D
Yeah,
I
would
be,
I
think,
it'd
be
interesting
to
add
that
in
and
I
you
know,
I
opened
it
in
this
repo
in
terms
of
it
seems
like
something
useful
across
projects
and
even
across
like
foundation.
So
just
got
me
thinking
like
how
do
we
start
to
get
the
infrastructure?
That's
needed
across
the
foundations,
be
something
that's
provided
by
the
foundation
versus
having
to
be
reinvented
every
time
or
by
the
by
the
the
linux
foundation
umbrella
be
provided
so
that
you
know
the
foundation's
enough
to
reinvent
it
for
every
project
but
yeah.
A
Awesome
great,
so
what
do
we
can?
Can
I
don't
know,
michael
if
you
want
to
summarize
something
for
the
issue
itself,
so
next
time
we
come
around,
we
kind
of
you
know
it's
captured
in
the
issue
itself.
That
would
be
great.
D
A
All
right,
I
will
move
along
then.
The
next
item
on
the
agenda
is
pull
request,
804,
track
issues
outside
of
dates
and
reminders,
which
I
think
we
kind
of-
should
sort
of
review.
This
whole
conversation
again,
and
I
don't
know
why
we
don't
maybe
we
haven't
merged
this
just
because
we
should
talk
more
about
it.
A
I'm
not
sure,
but
I
think
you
know
the
the
the
reason
why
we
created
this
document
was
a
sort
of
stopgap
measure
to
help
us
to
check
on
dates
that
that
come
up
which
oftentimes
surprise
us
like
voting
term
ending
and
stuff
like
that.
A
And
the
thing
that
was
taken
out
was
the
check
on
progress
of
building
stronger
ties
between
at-large
maintainers
and
their
cpc
rep,
which
is
funny.
I
want
to
check
on
that
too.
So
yeah,
I
don't
know
what
to
do
with
this.
We
can
certainly
just
merge
this
pr,
but
I
think
coming
back
to
this
sort
of
what
do
we
do
about
dates
and
things
that
we
want
to
you
know
not
let's
slip
through
the
cracks
is
maybe
something
we
should
discuss
further.
F
Any
thoughts
we
do
have
a
dates
and
reminders
file
that
you
created
last
year
that
you
know
looking
through
it.
Now
we
do
have
february
28th
director
one
election
happening.
There
is
no
data
on
the
cbc
chair
election
and
the
31st.
If
this
is
just
like
a
heads
up
of
like
you
know,
we
want
to
make
sure
we're
on
top
of
things.
Oh
yeah,
that's
what
this
is
for.
That's
I
yeah.
A
A
Labels,
okay,
so
I'm
just
kind
of
trying
to
grog.
It
looks
like
toby
reopened,
issue
761,
which
was
the
one
that
he
was
pulling
out
of
that
dates
and
reminders
file.
D
I
think
I
think
it
was
that
maybe
he
pulled
some
things
out
because
he
meant
them
to
be
quarterly,
and
this
thing
just
changes
them
to
be
quarterly
like
once
this
lands
we
need
to
have
that.
I
mean
we
need
to
look
at
this
periodically,
hopefully
that'll,
if
we
forget
looking
at
it
for
like
the
elections
and
all
that
we'll
also
miss
the
cpc
ones.
But
if
we
remember
that
we'll
remember
this
one,
I
would
just
say
if
you
added
a
added
to
the
agenda
for
this
cpc
meeting,
they
check
the
dates
and
reminders.
A
I'm
going
to
do
it
yeah
I'm
going
to
merge
this
pr,
and
then
we
should
create
a
new
issue
to
add
the
dates
and
reminders
to
the
to
the
meeting
template
how's
that
sound.
A
And
I
will
assign
it
to
myself
and
create
the
issue
and
I'll
try
to
get
that
done.
I'm
going
to
put
the
agenda
label
on
it
too.
Just
so,
if
I
forget
it
doesn't
totally
drop
off
my
radar.
C
A
A
C
We
do
need
sort
of.
We
do
need
a
little
bit
better
process
to
check
with
the
projects
I
know
alex
is
new,
so
she'd
like
to
get
ahead
of
some
of
the
you
know,
project
milestone
news.
We
have
the
event
coming
up
and
just
general
two-way
sharing.
You
know
information.
We
just
need
to
figure
out
the
best
way
to
do
that.
A
Sounds
good
yeah!
Well,
I
have
a
meeting
with
alex
tomorrow,
we'll
start
working
on
some
of
that
great
all
right.
Where
am
I?
What
am
I
doing
so
moving
on
the
next
item?
The
agenda
is
clarify
requirements
around
coc
violation.
This
is
opened
august
3rd
by
toby.
A
Currently,
there
are
no
requirements
beyond
adopting
the
foundation.
Coc
for
projects
seems
we
would
need
additional
requirements
for
projects.
There's
a
lot
of
comments
here,
as
well
as
a
list
of
next
steps.
C
I
believe
we
were
going
to
have
a
working
session.
I've
done
the
audit.
I
believe
the
action
item
was.
We
would
have
some
language
to
put
in
for
some
folks,
because
some
people
just
will
drop
a
link
a
few
without
any
information.
So
I
think
we
just
need
to
provide
some
language
just
like
we
provide
footers
and
things
like
that,
but
we
probably
need
a
little
preamble
to
explain
why
so.
C
A
A
I
I
Middle
of
moving
between
new
jersey
and
colorado,
so
you
know
yeah
no
worries!
Congratulations
on
escaping
new
jersey!
Sorry.
A
Cool
welcome
and
welcome
joining
cpc
as
well
I'll
reiterate
that
so
robin
you
mentioned
a
working
session,
I'll
mention
that
there
are
none.
There
are
there's
no
calendar
entries
for
the
working
sessions,
so
I
was
going
to
recreate
those
soon
this
week.
A
I'll
just
follow
the
same
pattern
as
last
time,
assuming
that
we
want
to
just
you
know,
have
them
on
the
calendar
and
we
can
cancel
if
we
don't
do
anything,
but
maybe
this
would
be
a
good
thing
to
do
on
the
next
working
session
kind
of
explore
this
this.
This
particular
issue,
which
I
will
copy
and
paste
into
the
chat
for
mike
or
anyone
else
there
we
go.
H
A
A
Yeah,
let's
keep
that
moving
forward,
I'm
going
to
just
in
the
notes
here
next
working
session.
B
A
Great,
so
I
will
take
these
two
working
sessions
and
maybe
add
them
to
whatever
issue
we
were
using
to
track
the
schedule,
or
maybe
we
need
a
new
one
for
2022.
nope
tori
already
made
one.
Of
course
she
did.
A
She
has
the
january
11th
working
meeting
as
repo
cleanup
michael.
Do
you
think
that
that
is
the
same
thing
that
you're
talking
about
or
is
that
something
different
that
would.
D
A
C
A
Okay,
so
I'll
just
move
the
repo
clean
up
to
the
25th,
you
know
push
it
off.
Do
the
tech
strategy,
one
for
the
11th
and
then
this
coc
one,
the
one
after
that.
A
Okay,
so
that
is
captured
in
this
issue
just
for
everyone.
They
want
to
know-
and
let
me
make
sure
that
is
a
pinned
issue
as
well,
so
we
can
always
get
to
that
easily
great,
all
right
cool,
so
we
touched
on
that
agenda
item
but
also
touched
on
the
working
session
stuff.
The
last
item
on
the
agenda
is
the
create
proposals
for
the
community
fund,
which
is
sort
of
something
new.
C
Yeah,
we
will
we'll
need
some
more
clarity
on
this,
for
how
much
you
want
to
allocate,
because
we
would
like
to
allocate
obviously
travel
fund
budget
for
collab
summits
and
the
event
and
also
diversity,
scholarships
for
the
event
as
well.
So.
A
Okay,
I'm
adding
community
funds
to
the
list
here,
but
just
so
we
know
the
the
next
open
slot
is
february
22nd,
which
feels
already
pretty
far
into
the
year.
For
for
that
sort
of
work,
I
don't
know,
I
guess
I
guess
it's
all
right
any
thoughts.
We.
H
H
Like
is
the
community
fund
currently
blocked,
given
what
we
have.
C
A
D
A
A
A
That's
the
hackmd
file,
michael
robin
everyone.
This
is
from
a
meeting
a
working
meeting
on
november
30th
tourney
right
there
as
well
and
yeah.
Yes,
this
was
a
good.
This
was
actually
a.
We
did
great
work
in
that
meeting.
I
think
there
was
still
work
to
be
done,
but
we
did
really
kind
of
try
to
break
things
out
more.
D
Yeah,
I
think
we
were
like
again
like
thinking
of
like
having
a
repo
separate
repo
for
it.
These
were
like
some
of
the
the
headings
that
we
would
see
in
the
repos
and,
like
the
eligible,
you
know,
writing
out.
The
eligibility
criteria
are
guesstimate
budgets,
how
you
apply,
who
the
approvers
are
yup,
so
we
just
put
in
some
numbers
right
like
you
know,
but
it
would
be
good
at
the
beginning,
the
good
time
at
the
beginning
of
the
year
to
say:
okay,
let's
actually
close
on
what
we
think
those
will
be
right.
C
D
A
A
D
D
C
D
A
Cool,
I
added
the
schedule,
the
updated
schedule
to
the
meeting
notes
here
too,
so
community
fun
will
be
next
schedule.
Next
working
session
tech
strategy
will
be
the
one
after
that
on
the
25th
of
january.
Clarify
requirements
around
coc
violation
would
be
the
one
after
that
on
february,
8th
and
then
repo
cleanup
will
be
february.
22Nd.
A
D
A
I
was
listening
to
some
band
rehearsal
recordings
recently
and
realized.
We
had
worked
on
a
song
and
it
sounded
great
and
if
we
hadn't
recorded
it,
I
would
have
forgot
everything
anyway.
That's
that's
our
whole
jam.
That's
our
agenda
and
our
working
session
stuff.
We
have
17
minutes
left.
Do
we
want
to
continue
hanging
out
and
and
work
on
repo
cleanup
or
any
any
other
things
any
prep
for
any
of
those
working
sessions
or
anything.
C
C
A
Is
it
also
an
opportunity,
the
program
committee
meeting
to
perhaps
discuss
like
collab
summit
thoughts.
C
Absolutely
because
it's
been
a
while,
since
we
had
an
in-person-
and
I
was
pretty
new,
so
just
thinking
about
what's
the
best
way
to
tackle
that
is
it's
going
to
be
big.
C
C
Yeah,
so
they
have
their
designated
space.
We're
also
having
the
cd
foundation
and
graphql
foundation
are
co-locating
with
us
and
they
have
their
own
space.
Although
we'll
be
sharing
the
thought,
leadership
keynotes
as
well,
but
the
cool
thing
about
the
conference
is,
you
can
buy,
you
can
buy
one
ticket
and
you
can
go
to
any
event
that
you'd,
like
so.
A
So
my
question
is,
though,
how
does
tc39
overlap
with
the
the
week's
events?
Is
it
on
the
same
week?
Is
it
during
the
same.
C
The
team
had
decided
that
that's
what
they
would
do,
I'm
not
sure
exactly
what
hours,
they're
structured
but
definitely
they'll
be
able
to
take
advantage
of
the
social
activities
in
the
evening
hallway
tracks
and
things
like
that.
F
G
C
A
C
Believe
it
begins
on
monday,
we
also
have
training.
On
monday
we
have
confirmed
node.js
training
with
dave
plymouth
and
then
native
script
training
as
well
on
day
zero
on
monday.
A
A
C
Yeah
and
I
think
we're
thinking
that
the
project
collab
summits
would
be
thursday
cpc
collab
summit
friday
morning,
so
so
people
can
leave
by
noon
and
fly
home.
A
F
I
I
also
like,
usually
like
the
node
collapse
summit,
has
been
two
days
itself
and
we
have
taken
the
full
two
days
like
very
like
you.
Usually
there
is
a
person
or
two
who
will
fly
home
by
noon,
but
that
is
not
the
structure
that
the
project
has
used
really.
C
F
I
I
I
would
have
to
look
at
the
schedule,
but
I
mean
I
like
I
know.
Node
can
fill
two
full
working
days
just
doing
node
and.
A
One
of
the
things
that
was
nice
about
the
sort
of
open
js'ing
of
the
you
know,
node
interactive,
was
that
tc39
and
the
collab
summit.
You
know
at
the
at
the
node.js
cloud
summit.
We
got
more
tc
39
people
there,
and
I
thought
that
was
great.
So
the
fact
that
tc39
is
happening
until
thursday.