►
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
A
All
right,
friends,
there
we
go.
Sorry,
I'm
I'm
typing
in
the
chat.
Welcome
to
another
episode
of
the
openjs
foundation's
cross
project
council
meeting
today
is
the
13th
of
april
thanks
everybody
for
joining,
and
anyone
watching
later
on.
Thank
you
folks
who
are
here,
drop
your
name
in
the
google
doc
and
we
can
get
started.
Do
we
have
any
announcements.
B
I
have
one
I
just
wanted
to.
Let
folks
know
that
the
linux
foundation,
linux
foundation,
training,
is
doing
a
program-wide
scholarship
right
now.
It
goes
through
april
30th
and
anybody
you
know
folks
are
encouraged
to
apply
if
you're
interested
in
certification
or
training.
This
applies
to
the
node.js
trainings,
but
it
applies
to
the
entire
portfolio
of
trainings
and
certifications
that
the
lf
offers
we
did
post
something
on
our
blog
and
we
posted,
and
we
tweeted
that.
B
So
all
the
information
is
out
there
and
we
encourage
everybody
or
anybody
who
feels
that
they
qualify
to
apply.
A
Great,
can
you
drop
a
little
bit
of
those
details
into
the
notes
and
I
would
be
happy
to
re-share
the
tweet
and
whatnot
so
great,
exciting.
C
Another
short
announcement,
the
standards
working
group
is
going
to
meet
this
afternoon
and
this
was
a
rescheduling
from
the
conflict
from
last
week.
So
join
us
at
2pm
eastern.
If
you
are
interested
in
in
that,
got
some
stuff
to
work
on.
A
Great
fun,
didn't
you
get
nominated
to
something
recently.
Jory
is
that
is
that
an
announcement
ac
at
w3c
or
oh.
C
Yeah
so
that
we
we
had
done
a
period
to
see
if
anybody
wanted
to
to
be
our
w3c
advisory
council
rep
and
that
that
closed
like
a
couple
weeks
ago.
Actually
at
this
point-
and
that's
me
hi,
so
if
you
have
a
community
group
or
an
interest
group
or
something
you
want
to
get
involved
with
at
the
w3c,
I
will
be
posting
announcements
and
things
like
that
in
our
standard
slack
channel,
one
of
which
was
super
cool
that
they
announced
this
morning
and
there's
going
to
be
a
new
spec
editors.
C
Community
group
that
marcos,
caceros,
is
chairing
very
excited
about
that.
Definitely
plays
well
and,
of
course,
jordan,
walks
off,
because
I'm
staring
at
jordan.
C
This
is
for
you
he's
like
I'm
out
of
here
that
anyway,
so
cool
cool
opportunities,
lots
of
things
cook
in
there
so
come
on
down
to
standards,
r,
us.
A
Nice
cool
great:
I
dropped
something.
D
A
Okay,
good
good,
I
dropped
a
couple
of
notes
in
the
meeting
notes,
but
if
anybody
can
jury,
if
you
can
flesh
that
out
a
little
further
that'd
probably
be
great
and
yeah
folks
can
help
taking
meeting
notes.
That
would
be
great.
I
don't
know
if
jordan,
if
your
child
can
type.
This
would
be
a
great
way
to
get
involved.
A
Cool,
so
we
can
jump
into
the
agenda.
I
guess
I'll
ask:
are
there
any
board
meeting
updates
any
any
board
stuff.
E
A
Okay,
great
great
we'll
do
that
excellent
cool
so
getting
into
the
agenda
the
which
is
not
a
very
long
one.
So
we'll
see
how
long
we
spend
time
together
today.
The
first
thing
here
is
from
the
summit
repo,
and
this
is
about
the
collaborator
summit.
I
know
that
this
was
talked
about
a
a
couple
of
sessions
ago.
Jory,
you
have
an
update
in
here
and
I
think
you
know,
I
think,
maybe
the
the
general
ideas.
A
That's
you
know
we
won't
do
something
around
openjs
world,
but
that's
you
know
we're
open
to
other
options,
and
I
know
in
the
tooling
group,
the
node.js
tooling
group.
We
were
talking
about
stuff,
doing
something
in
the
fall
either
virtual
or
you
know
potentially
in
person.
A
So
I
think
maybe
the
summary
is
collab.
Summits
are
great,
we're
not
gonna.
Do
it
with
this
event,
but
let's
figure
out
how
to
do
them
either
virtually
or
in
person.
At
some
point
over
the
coming
months,.
C
That
is
definitely
the
summary
one
of
the
things
that
I
think
we're
starting
to
look
at
is
whether
there's
an
lf
event
that
is
likely
to
happen
in
person
that
we
could
say
co-locate
with,
because
that's
a
cost-sharing
opportunity
for
us
and
it's
just
still
super
unclear
what
if
any
elephant
lf
events
will
be
proceeding
for
in
person
and
how
comfortable
people
will
be
traveling.
So
it's
something
we
have
to
monitor.
A
Yeah
yeah
and
I
wonder
too,
like
what
we
can
provide
as
the
cpc
and
the
foundation
to
help
groups
to
do
even
like
mini
collab
summits,
whether
it's
a
platform
or
you
know.
I
know
the
travel
fund
is
being
talked
about,
but
I'm
thinking
primarily
about
virtual
collaboration
platforms,
I'm
not
not
that
we
would
spend.
I
know
those
things
are
really
expensive,
but
ways
that
we
can
help
people
to
to
figure
out
getting
together
and
collaborating.
A
E
A
E
F
A
Yeah
and
I'm
even
trying
to
think
through,
like
in
the
node.js
community,
you
know
there
are
lots
of
groups
and
people
working
on
different
things
like
if
we
were
to
do
something
virtual.
What
would
that
look
like,
I
think
doing
it
all
at
once,
is
maybe
not
the
best,
but
you
know
coming
up
with
other
ideas
to
you
know
have
some
sort
of
collapse
on
it
would
be
great,
but
anyway
we
can.
A
We
can
keep
thinking
about
it
and
see
how
things
play
out
over
time
and
discuss
it
within
our
groups
as
well
and
see
what
makes
sense
cool
do
we
think
that
we
need
to
keep
this
issue
open,
or
I
mean
we
can
leave
it
open
if
we
want,
but
maybe
take
the
agenda
label
off,
I'm
not
sure
what
people
think.
A
I
agree
so
I
just
did
that
great,
but
if
anybody
ever
wants
to
talk
about
it,
please
feel
free
to
bring
it
up.
I'm
happy
to
discuss
it
further,
as
things
go
further
great,
so
that
leads
us
into
the
next
issue,
which
michael
mentioned
earlier:
the
travel
fund
allocation
for
2021.
E
Yeah
so
I
mean
the
update
was
we
did
have
a
good
discussion
in
the
board
meeting.
The
decision
was
that
we
needed
to
push
it
to
the
the
finance
committee,
because
the
finance
committee
is
the
one
who
reviews
the
the
budget
and
works
with
the
budget,
so
that
hasn't
happened
yet.
So
that's
the
next
step
is
it's
going
to
be
discussed
in
the
finance
committee.
E
Recommendation
goes
back
to
the
board
and
then
we'll
come
back
to
to
the
thing,
but
we
did
have
the
you
know
the
discussion
around
the
different
suggestions
of
how
it
you
know
the
funds
might
be
used
and
so
forth.
F
D
E
Need
to
keep
you
know
yeah,
it
was
like
yeah,
you
know
we,
yes
yeah.
It
was
back
to
that
yeah.
We
just
made
the
the
the
change
based
on
hey.
We
don't
think
we're
going
to
use
it,
and
so
let's
go
back
to
okay.
If
there's
proposals
for
how
to
use
it,
elsewise
then
yeah,
let's
figure
out
what
we
do.
There.
A
Okay,
the
the
generally
supportive
bit
is.
I
appreciate
that
part
yep.
D
No,
no,
and-
and
if
I
can
just
say
something
here
like
this-
is
a
great
example
of
like
the
cpc
and
the
board
working
well
together
to,
like
you
know,
do
the
right
thing
and
like
have
the
right
show
the
right
perspective
of
what
it
is
that
the
overall
organization
wants
to
do.
So.
I
think
this
is
something
to
cherish
and
applaud.
So
I'm
kind
of
I
think
this
is
great.
Thank
you.
A
Yeah
yeah
agreed
and
yeah.
Thank
you
to
michael
and
sarah
and
robin
as
well
cool
all
right.
So
we'll
leave
that
one.
But
the.
E
One
thing
I
will
add
is
you
know,
I
think
something
the
cpc
could
do
in
parallel
is
to
work
on.
You
know
the
concrete
proposals
of
how
we
might
you
know
the
other
ways
of
using
the
money.
E
So
if
we
wanted
to
get
started
on
that,
I
don't
think
there's
any
reason
to
to
wait
for
yeah.
We've
we've
changed
this
line
item
or
not
right
like
because
it
could
be
like
well
yeah.
That
makes
sense,
but
let's
create
a
new
line
item.
What
does
the
proposal
look
like
or
it
could
be?
Let's
put
this
back
or
I
don't
know
what,
but
all
of
those
would
be
supported
by
and
here's
our
proposal
for
you
know
what
would
we?
What
would
we
wanted
to
approve?
E
E
E
Think
toby
toby
had
put
some
in,
like
you
know,
we
could
potentially
use
it
to
support.
You
know
underrepresented
minorities
in
some
other
way.
E
Right,
like
you
know,
robbins
mentioned
things
like
you
know,
sponsored
certifications
or
you
know
I
think,
there's
there's
a
number
of
different
ideas
and
that's
where
I'm
not
you
know
we
don't
have
a
a
well-defined
here's,
the
ask
right,
so
I
think
the
more
we
you
know
if
we
start
thinking
about
that
and
write
up,
what
that
would
look
like
the
better
prepared
will
be
to
actually
execute
on
it
too.
A
Okay,
and
where
should
we
do
that
in
this
particular
issue
or
a
new
issue
or
or.
E
A
Yeah,
okay,
that's
great!
I
I,
the
scholarship
idea,
I
think,
is
great
other
way.
So
we
can
help
underrepresented
groups.
I
think,
would
be
fantastic
cool
all
right.
Well,
let's,
let's
get
an
issue
going
for
that
and
drop
some
ideas
in
there
and
we
can
iterate
in
the
issue
and
see
what
else
we
can
come
up
with,
and
I
also
wonder
too:
if
things
do
get
better,
I
realize
that
you
know
things
are
progressing
at
different
levels
in
different
parts
of
the
world.
Some
some
parts
maybe
aren't
even
progressing.
A
Yeah,
so
you
know,
I
hope
that
we
can
do
some
traveling,
but
I
realize
that
that
might
not
really
be
the
case.
We'll
see
cool
all
right,
so
yeah
I'd
be
happy
to
iterate
on
some
ideas
to
to
use
the
money
in
other
ways,
it'll
be
great,
excellent
reminder.
Anybody
who
can
drop
some
notes
in
the
doc
would
be
really
appreciated.
A
Jumping
to
the
next
one,
improve
diversity,
equity
and
inclusion
at
the
open,
js
foundation.
I
don't
know
if
we
have
much
here.
I
had
some.
A
D
Meeting
was
interested
parties
at
the
open.js
foundation
and
w3c,
and
for
this
I'm
still
waiting
for
one
of
the
two
vendors
I
contacted
around
the
survey
to
get
back
to
me.
They
requested
a
delay
because
they
had
some
other
things
going
on
this
week,
and
so
I
should
hear
about
them.
I
think
next
week
and
so
I'll
follow
up
at
that
point.
D
What
was
really
interesting
was
that
the
last
vendor
I
talked
to
was
suggesting
that
working
with
different
organizations
like
the
g3c
to
do
this
would
very
much
lighten
the
cost,
because
a
lot
of
the
infrastructure
to
run
the
survey
and
the
the
server
design
itself
etc
could
be
shared,
and
they
were
willing
to
work
like
that,
which
I
thought
was
really
cool.
A
Cool
all
right
well,
keep
us
posted,
I'm
interested
and
happy
to
continue
to
participate
there
moving
on-
and
this
is
the
last
one-
and
I'm
not
sure,
there's
much
here
on
this
one.
This
is
issue
632
provide
implementation,
guidance
for
dco
and
cla.
A
I
know
we're
still
waiting
on
some
folks
to
do
some
work
on
the
probot
pco
or
the
their
project
to
incorporate
some
upstream
changes.
As
mentioned
in
the
issue,
I'm
assuming
there's
no
updates.
There.
F
A
Okay,
great-
that
is
our
last
issue,
but
I
see
emily
helpfully
pasted
the
guidance
about
graduating
projects
from
incubation-
and
this
is
language-
is
very
familiar
now
that
I
see
it
there,
that's
it's
a
pull
request
that
that
functions
as
like
any
other
pull
request.
G
One
related
thought
of
that
that
I
noticed
is
that
we
actually
currently
have
some
requirements
for
moving
from
at-large
to
impact
that
we
are
not
applying
for
projects
directly
coming
in
as
impact
and
before
coming
in
at
large
in
the
requirements.
For
that,
I
noticed
that
we
have
a
requirement
for
a
presentation
of
the
project
to
the
cpc
which
I
don't
recall.
Having
happened
for
our
incoming
projects.
A
Well,
I'm
wondering:
do
we
create
an
issue
to
look
at
some
of
these
things
and
also
do
we
have
an
expectation
that
native
script
would
do
some
sort
of
presentation.
C
I
would
think
that
that
would
be
a
little
because
this,
if
I'm
reading
this
correctly,
that's
something
that
we
have
not
applied
to
any
incubating
project.
That's
that's
come
in
so
it
seems
like
this
is.
It
would
be
not
exactly
fair
to
suddenly
apply
that
that
is
my
take,
but
I
think.
E
C
Yeah,
what
I'm
saying
is
this
is
clearly
not
something
that
we
like
this
feels
like
something
we
may
have
created
as
before.
We
had
any
incubating
projects
whatsoever,
and
maybe
at
the
time
we
thought
it
would
add
value,
but
it's
clearly
not
something
that
we've
been
missing.
So
my
point
is:
does
this
ad
doesn't
seem
like
it
adds
value
to
our
process
unless
I'm.
G
I
would
in
in
general,
I
would
feel
that
having
a
new
project
actually
explicitly
present
themselves
would
be
valuable.
However,
I
feel,
as
you
do,
that
applying
this
sort
of
rule
now
suddenly
to
a
project
relatively
either
late
stage
is
kind
of
unfair,
but
we
should
at
least
get
the
language
within
that
document
to
match
itself
so
that
we
have
one
set
of
requirements
that
we
are
presenting
for
proceeding.
G
Okay,
I'll
file
an
issue
about
the
mismatch
here,
but
also
presented
in
a
way
where
I'm
saying
that
explicitly.
We
do
not
at
least
have
an
active
sense
that
we
need
to
be
applying
all
of
these
rules
to
projects
that
are
currently
in
incubating,
if
or
as
we
have
not
applied
them
to
the
previous
ones.
A
H
I
just
added
a
asynchronous
here
for
a
bit
of
an
update
on
the
cloud
space,
so
the
package
maintenance
and
vulnerability
reporting
cloud
space
that
michael
dawson
helped
me
get
kicked
off
there.
So
I
had
a
quick
meeting
with
rachel
and
jory
last
week
in
terms
of
marketing
and
cons
and
I'm
trying
to
coordinate.
H
A
A
If
not,
I'm
happy
to
give
folks
back
some
time,
and
I
guess
one
thing
to
comment
on
is
next
working
session-
is
that
where
you're
gonna
go
jory.
C
Exactly
so,
our
next
working
session
is
obviously
next
tuesday,
and
the
slated
item
is
discussion
of
actually.
This
whole
comment
about
the
incubation
process
is
super
resilient
to
that,
because
we're
gonna
talk
about
our
strategy
there
and
sort
of
how
we
onboard
new
projects,
which
projects
we
think
are
great,
fits
for
our
foundation,
etc.
C
So
do
do
tune
in.
If
that
is
a
topic
of
interest
to
you
to
you,
we've
got
a
new
issue
that
itemizes
all
of
our
meetings,
and
so
if
there
is
a
working
session
that
you
want
to
propose
that
we
cover
in
the
future,
we
can
we
can
put
that
in
in
that
list
and
give
everyone
a
heads
up
what
we'll
be
covering
in
these
different
working
sessions.
So.
A
Great
awesome,
cool
yeah,
so
that's
the
working
session
is
the
same
time
as
this
meeting
was
today
next
tuesday.
So
you
know
what
is
it
1700?
I
I'm
always
nervous
nervous,
quoting
a
time
zone
other
than
my
own,
but
same
time
as
today
in
the
week
so
yeah.
I
hope
to
see
folks
there
anything
else
before
we
sign
off
all
right.
Well,
stay
safe!
My
friends
and
I'll
talk
to
you
soon.