►
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
All
right
looks
like
we
are
live
thanks.
Everybody
for
joining
another
episode
of
the
openjs
foundation's
cross
project
council
meeting
today
is
the
19th
of
january
new
year.
2021.
Do
we
have
any
announcements
before
we
get
into
the
agenda
and
such.
B
I
have
one
I
know
jory's
not
here
today,
but
last
monday
we
did
open
up
the
call
for
speaker.
Submissions
for
openjs
world
open
js
world
is
june
9th,
so
speaker,
submissions
are
open
through
about
mid-february,
so
go
jump
on
our
website.
You'll
find
the
links
and
submit
some
great
talks.
B
C
Any
announcements
or
anything
sure
just
one
quick
one
we
are,
we
have
started
to
gather
responses
for
a
node.js
user
survey.
You
can
find
that
link
on
the
nodejs
webpage
on
there's
a
there's,
a
banner
for
you
to
go
ahead
and
take
that.
So,
if
you're
using
node.js
and
you've
got
some
feedback,
we
would
love
to
hear
from
you.
A
A
A
Cool,
so
I
will
jump
into
the
agenda.
The
first
item
is
issue
699.
This
is
improving
diversity
and
inclusion
at
the
open
jsf
at
open.js.
We
had
talked
about
maybe
using
a
working
session
to
try
and
dig
into
this
further
I
mean,
of
course,
I
encourage
folks
to
chime
in
on
the
issue.
If
they
have
anything,
they
want
to
add
to
this
issue.
You
know
to
get
the
conversation
started,
but.
A
I
don't
know
how
much
we
want
to
discuss
here
if
we
just
want
to
save
the
conversation
for
a
working
session,
other
people's
thoughts.
A
I'm
sure
there
are
lots
of
ideas
and
thoughts
and
everything,
but
maybe
we
could
save
it
for
something
where
we
can
really
dig
into
it
and
yeah
move
it
forward.
There.
B
A
B
All
right,
definitely
so
I'll
circle
back
with
toby
and
see
how
his
week
looks
next
week.
A
Okay,
great
yeah,
I
mean
ideally
well.
I
guess
not
ideally,
but
we
do
have
the
you
know
working
sessions,
and
I
guess
you
know
what
why
don't
we
I'll
move
this
up,
even
though
I
close
this
issue,
I'm
gonna
move
it
up
thing,
so
we
can
just
talk
about
it
now.
So,
though
we
could
use
a
working
session
for
this,
the
idea
was
that
working
sessions
would
be
at
the
same
time
in
the
off
week.
You
know
the
following
week
for
cpc
meetings.
A
A
So
the
thought
was
that
you
know
in
each
cpc
official
meeting
we
could
talk
about
if
we
want
to
use
the
following
working
session
and
then
kind
of
create
the
meeting
and
put
together
an
agenda
if
need
be,
and
so
I
guess
the
if
I
am
to
jump
ahead
a
little
bit.
Do
we
want
to
try
and
use
next
week's
meeting
time?
You
know
1700
utc,
we
could
we
could
pencil
it
in
and
see
if
toby
and
sarah
are
available
at
that
time.
I
guess.
A
And
then,
if,
if
that
doesn't
work
out
for
whatever
reason,
I'm
open
to
other
ideas
for
that
time,
slot
as
well,
there's
lots
of
things
that
we
could
move
forward
on
and
make
progress
on.
So
so,
let's
just
do
that
we'll
pencil
in
this
issue
and
diversity,
inclusion
and
if
not,
then
we'll
figure
something
else
out
so
cool
all
right
great.
So
that's
that's
the
first
agenda
item
I
kind
of
touched
on
the
second
one.
I
think
I've
already
closed
this
issue
number
680..
A
I
just
commented
on
the
details
there.
The
calendar
is
updated
for
the
bi-weekly
cadence.
The
standards
team
meeting
is
not
moved.
It
will
conflict
with
a
working
session
once
every
four
weeks,
but
we
decided
that
was
you
know
we'll.
If
that
becomes
a
problem,
we'll
figure
it
out
later,
not
a
big
deal
cool.
So
those
are
the
first
two
items.
A
The
next
item
on
the
agenda
is
issue
687.
This
is
prepare
to
open
nominations
for
the
second
board
seat.
I
think
we're
gonna,
start
kind
of
you
know
surfacing
this
and
socializing
it.
My
comment
from
two
weeks
ago
was
that
the
new
term
starts
on
the
first
day
of
march.
We
should
have
the
vote
open
the
vote
on
february,
2nd
and
close
it
on
the
9th
of
course
eligible
candidates.
Our
current
cpc
members
and
the
people
who
vote
are
cpc
voting
members
and
it
looks
like
here
we
have
michael.
A
A
Cool,
that's
great,
then
we'll
get
that
ball
rolling,
maybe
yeah.
Maybe
maybe
once
you
open
that
up,
you
could
ping
it
in
the
cpc
slack
channel
or
something
and
yeah
makes
sense,
keep
it
keep
it
hot.
E
I
also
just
real
quick
just
want
to
add.
I
it's
probably
been
obvious
by
my
inability
to
be
at
meetings
a
lot
that
my
availability
is
dropping
immensely
because
of
work.
So
I
don't
intend
on
running
again
if
anyone
was
like
hesitating
because
they
were
like.
Oh,
I
don't
want
to
unseat
somebody
that's
already
there
or
something
like
that.
So
please,
if
you're
interested
I'm
happy
to
chat
with
you,
but
I
just
don't
think
I
can
give
the
appropriate
amount
of
time.
So
I
don't
want
to.
I
don't
want
to
keep
filling
that
spot.
A
Yeah
that
thanks
thanks
for
you,
know
speaking
up
about
that
and,
of
course
appreciate
the
time
that
you
have
been
able
to
put
in.
So
thank
you
for
all
the
future.
A
Definitely
appreciate
it
cool
all
right,
so
we'll
we'll
move
that
process
forward
and
the
list
of
eligible
nominees
is
only
the
cpc
members.
So
we
don't
have
a
a
vast
pool,
so
we
can
just
let
everybody
know
and
kind
of
move
forward
there
great.
If
anybody
can
help
with
notes
too,
I
haven't
been
able
to
do
anything
not
that
there's
that
much
that's
been
happening
here,
but
a
little
bit
of
notes
he's
great.
A
So
thank
you
next
on
the
agenda
here
and
I'm
happy
to
see
brian
is
on
the
call.
Is
the
google
summer
of
code
2021?
Do
you
want
to
chime
in
here
brian.
F
Yeah,
so
the
dates
have
been
announced,
it's
not
open
yet,
but
as
with
last
year,
it
would
be
nice
to
submit
an
application
again
to
be
able
to
have
some
students
come
on
the
recommendation
I
have
on
this.
One
is,
if
you
are
planning
to
apply
as
a
project-
and
you
know
you
have
the
the
plans
to
do
this
as
a
project
the
infrastructure
to
to
handle
supporting.
F
You
know
a
mentee
as
a
project,
then
definitely
go
ahead
and
do
that
the
goal
of
the
foundation
doing
this
is
not
to
stand
in
the
way
of
that
at
all
or
anything
like
that.
But
if
you're
a
small
project
and
are
you
know,
looking
to
maybe
have
a
little
bit
of
help
with
this
process
and
we're
certainly
happy
to
help.
As
I
recall,
in
the
past,
foundations
are
allocated
a
few
extra
slots
or
umbrella
projects
are
allocated
a
few
extra
slots.
So
there's
that
possible
consideration
as
well.
F
The
main
thing
I
would
just
encourage
everybody
to
keep
in
mind
is
that
if
we
are
doing
this,
you
know
applying
as
a
foundation,
then
it's
a
shared
slot,
and
you
know
if
we
have
more
projects
that
are
interested
in
having
students,
then
we
have
slots
available.
Then
we'll
just
have
to
figure
out
among
us
how
to
allocate
those,
whether
it's
a
coin
toss
or
something
else
in
the
past.
We
have
run
it
right
up
to
the
deadline
in
terms
of
putting
in
the
submission
or
the
application.
F
I
would
like
to
avoid
doing
that
this
time,
as
I
recall
that
I
think
the
deadline
is
february
19th,
let's
maybe
try
and
get
our
application
in
sometime
in
you
know
the
first
two
weeks
of
february,
so
we
have
a
little
bit
of
buffer
time,
just
in
case
that
sound
good.
A
Yeah,
I
I
wonder
you
know
we
should
maybe
surface
this
into
the
slack,
maybe
the
general
channel
or
something
and
maybe
send
an
email
out
to
projects
and
such
and
and
encourage
them
and
give
them
some
guidance
and
such
yeah.
A
Great
great
great
excellent,
all
right
cool
thanks,
keep
us
posted.
Let
me
know
how
I
can
help
and
all
that
stuff
cool
moving
along.
Then
the
next
item
on
the
agenda
is
pull
request
650..
A
This
is
something
toby
opened
up
a
while
ago
and
was
you
know
in
draft
state
for
a
long
time?
I
think
that,
as
we've
moved
forward
on
some
of
these
details,
yeah
toby
changed
it
from
draft
to
open
pull
request
last
week.
A
Does
anyone
have
any
comments
on
this
or
anything
they
want
to
discuss?
Toby's?
Not
here,
so
I
won't
speak
for
him,
but
I
see
like
emily's,
responded
and
michael
any
thoughts.
Folks.
A
Here
all
right:
well,
I
know
I
know,
we've
talked
about
this
a
bunch,
so
you
know
maybe
just
folks
take
a
look
at
this
pull
request.
Add
any
additional
comments.
If
you
have
any
and
then
we
can
try
to
move
this
forward,
I
know
some
of
the
other.
Supporting
work
has
been
done
as
well
in
terms
of
growth
plan
templates
and
like
moving
some
things
over
to
project
status
and
such
so
yeah
check
it
out.
Please
moving
on.
F
I
have
an
update
this
week,
so
over
the
weekend
I
submitted
a
fairly
massive
pull
request
against
probot
dco
to
add
the
support
that
we'd
be
talking
about
here
on
the
the
sorry,
the
dco
implementation
guidance.
If
you
remember
this
is
the
remediation
commit
support
which
basically
makes
it
easier.
F
If
somebody
has
you
know,
the
project
is
using
the
dco
and
their
sign
off
hasn't
been
accepted
on
a
particular
commit.
It's
an
alternate
way
to
fix
the
issue,
hopefully
making
it
easier.
So
we
don't
have
people
abandon
poor
requests
that
have
failed
the
dco
check.
This
is
kind
of
an
integral
part
to
this
guidance
of
of
actually
implementing.
You
know
dco
versus
cla,
because
it
does
address
really
one
of
the
key
pain
points
that
we've
heard
from
the
projects
I
had
talked
with
with
bex
briefly
over
the
weekend.
F
Bex
is
the
robot
dco,
maintainer
and
they're
going
to
have
a
look
at
it
here
in
the
next
week
or
so
so,
hopefully,
once
this
is
in
place,
we'll
have
some
really
kind
of
cohesive
and
comprehensive
guidance
as
well,
and
that's
kind
of
that's
the
third
pillar
of
the
guidance.
So
first
pillar
was:
what
exactly
are
these
two
things
and
what
you
know?
How
would
a
project?
F
How
should
a
project
think
about
it?
The
second
pillar
is
the
actual
cla
support
which
we've
got
in
place
and
then
the
third
one
is
this:
this
guidance
on
using
probot
dco
and
implementing
the
tooling
for
projects.
So
that's
it.
A
Cool,
so
we
will
wait
for
that
to
land
and
all
those
things
to
move
forward
and
otherwise
keep
this
issue
open.
A
Do
you
want
to?
Where
did
I
find
that
maybe
drop
a
comment
in
su
632
brian?
Let
me
have
a
moment
just
so
that
the
issue
is
updated
with
the
progress.
I
can
do
that.
A
Thank
you
so
much,
and
there
are
some
notes
in
the
meeting
notes,
if
that's,
if
you
wanna
just
copy
and
paste
or,
however
you
wanna
do
it
cool
moving
on
the
last
item
on
the
agenda
is
a
pull
request
in
the
project
status
repository,
and
this
is
one
that
I
had
opened
and
I
think
that
there
were
a
couple
of
check
boxes
in
the
description
here
that
I
believe
toby
has
completed,
but
I
will
check
with
him
and
check
with
the
status
of
these
things
before
we
land
this
before
we
land
this,
this
particular
pr.
A
So
if
anybody
wants
to
take
a
look
at
it,
add
any
comments.
That's
just
adding
the
growth
plan
template
to
the
project
status,
repository
cool,
that's
all
that
is
on
the
agenda.
A
We've
talked
about
what
we
might
do
for
next
week.
We've
got
a
few
minutes
carved
out
at
the
end
of
this
meeting
for
some
private
session,
but
is
there
anything
that
we
want
to
discuss
in
the
bit
of
time
that
we
have
available?
You
know,
maybe
maybe
20
minutes.
A
We
could
also
just
jump
into
the
private
session.
You
know.
One
thought
I
I
had
is
just
the
sort
of
process
of
the
working
sessions.
I
I'm
not.
I
wondered
about
like
using
any
labels.
If
somebody
wanted
to
say
hey,
this
would
be
a
good
candidate
for
a
working
session
or
something
we
could
maybe
use
some
github
labels.
I
guess,
but
I
guess
we'll
just
figure
it
out
as
we
go.
A
I
think
that
that's
fine
yeah,
so
if
we
don't
have
any
other
business,
we
can
just
jump
into
a
private
session,
so
speak
now
and
forever
hold
your
piece
at
least
for
a
couple
of
weeks.
A
No
all
right
great!
Well,
you
know.
Let
me
actually
look.
I
feel
like
there
was
something
in
the
issues
that
I
wanted
to
at
least
raise
awareness
of.
Let
me
see,
hang
on.
A
One
thing
that
I
think
people
could
think
about
and
comments
on
this
issue
if
they,
if
they
would
like
this,
is
issue
700
in
the
cpc,
reboot
self-help
channels
for
projects
in
slack.
This
is
something
that
we
talked
about
in
the
node.js
community
committee,
and
I
think
it
would
be
interesting
for
us
to
think
about
and
maybe
have
some
plan
for
how
to
best
use
slack
channels
in
our
openjs
slack
org.
A
The
node.js
group
has
has
built
out
a
bunch
of
channels
for
their
like
teams
and
working
groups
and
initiatives.
We
prefixed
them
all
with
node.js
dash,
and
I
think
that
that's
been
good.
What
this
conversation
was
born
out
of
is
there
is
a
node.js
channel
and
people
are
dropping
in
there
and
asking
questions
which
I
think
is
great.
A
In
terms
of
you
know,
people
being
engaged
and
wanting
to
you
know
be
a
part
of
the
slack,
but
it's
been
unclear
as
to
is
that
what
that
channel
is,
you
know
best
use
for,
and
should
we
kind
of
develop
some
sort
of
a
plan,
for
you
know,
project
related
slack
channels
and
perhaps
like
a
help
channel
of
sorts.
A
So
we
don't
have
to
necessarily
make
any
decisions
here,
but
I
I'll
just
add
that,
like
you
know,
one
of
the
things
that
michael
and
I
had
commented
on
is
that
ibm,
which
of
course
is
a
big
company.
You
know
we
have
a
node.js
at
ibm
channel
and
there
are
lots
of
good.
You
know
engagement
there,
including
questions.
Obviously
there's
a
lot
of
people.
It's
sort
of
like
a
self
community,
help
sort
of
place
where
people
ask
questions
and
other
users
comments
and
that's
great.
A
There
isn't,
like
any
expectation
of
you,
know
node
contributors
to
be
answering
the
questions
per
se.
I
don't
know
if
we
have
that
you
know
amount
of
no
developers
there
yet
to
really
kind
of
support
that
and
then
also
you
know
there
is
the
node
slackers
slack
org,
that
is
sort
of
informal
unofficial,
but
a
lot
of
people
are
there
as
well
so
anyway,
something
to
think
about.
You
know
whether
we
have
project
related.
A
You
know
electron,
ask
me
anything
or
electron
help
or
or
you
know,
fastify
or
express,
or
what
have
you
so
something,
I
guess
to
think
about.
There's
an
issue:
that's
open!
There
and
we
can
talk
about
it
there
or
slack
or
I
mean
or
what
have
you,
but
I
thought
plant
that
seed
for
people
to
think
about.
D
Yeah,
especially
like,
is
it
going
to
be
useful
to
have
the
context
or
like
the
purpose
of
the
channels,
well-defined,
because
I
think
the
one
that's
there
for
node?
We
didn't
necessarily
think
it
was
a
place
for
people
to
ask
for
help,
but
in
absence
of
sort
of
having
documented
and
having
channels,
it
just
will
be
used
for
whatever
right.
F
D
And
then
a
pattern
might
help
to
make
it
easier
for
projects
to
say:
okay,
yeah,
you're
you're,
a
project
you've
joined
the
openjs
foundation.
One
of
the
things
you
can
get
is
here's
a
template.
We
use
for
our
slack
channels,
so
you
can
get
like
a
help.
One.
If
you
want
one,
you
can
get
like
a
core
contributor
one
you
can
get
whatever
makes
sense,
but
having
some
structure
would
probably
help
new
projects
too.
A
A
Agreed-
and
there
might
be
some
things
too,
that
we
can
take
from
like
you
know
the
ibm
internal
one
other
folks
might
have
internal
slack
channels
as
well
similar,
but
we
might
want
to
do
some
more
integrations
there
too,
like
you
know,
when
there's
a
new
release
that
comes
out
it
pops
up
in
our
slack
channel.
A
You
know
a
variety
of
things
could
be
implemented
there
so
stuff
to
talk
about
think
about
whatever,
but
I
think
it
would
be
good
to
kind
of
flush,
some
of
that
stuff
out
all
right
cool.
I
will
not
take
up
any
more
of
y'all's
time.
We
will
drop
into
a
private
session
for
a
few
and
and
then
call
it
a
wrap,
so
anyone
who's
watching.
Thank
you
appreciate
it.