►
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,
great
thanks,
everyone
for
joining
a
another
episode
of
the
openjs
foundation's
cross
project
council
meeting
today
is
the
27th
of
october
in
the
year
2020.
It
continues.
Do
we
before
we
get
into
the
agenda.
Do
we
have
any
announcements.
A
B
Yeah,
so
we
our
next
openjs
foundation,
ama,
will
be
with
the
dojo
project
and
we
are
going
to
have
that
on
november,
9th
at
10
a.m,
pacific.
So
it
is
already
on
the
public
calendar,
and
so
we
hope
that
you
will
join
us
for
that.
C
Right
cool,
I
guess
I
should
also
add
that
it's
note
14.x
is
going
lts
today.
So
that's.
A
D
D
One
more
quick
announcements
aren't
speaking
of
node.js,
our
certifications
and
trainings
are
on
sale
this
week
like
up
to
75.
A
Sale,
love
it,
I
guess
yeah
great
cool.
So,
let's,
let's
dig
into
the
agenda,
shall
we
so,
let's
see
first
up
here,
is
the
develop
growth
plan
template?
This
is
issue
658,
where,
where
I
know
where
we
have
something
started
here
right,
this
is
pull
request.
A
No,
what's
my
computer
doing
there
we
go
toby
added
something
a
bit
ago,
scrolling
scrolling,
so
I
don't
know.
Are
we
just
waiting
on
people
to
review?
Oh,
this
was
going
to
move
over
to
the
other
repository
right.
I
think
that's,
maybe
the
the
last
status
of
this
toby
are
you
on
you're
on.
E
Sorry
I
was
not
paying
attention.
Yes,
I
have
the
develop
growth
plan,
template
and
proposal
to
remove
the
growth
stage
of
both
things
that
I'm
looking
at
and
that
I
haven't
been
and
and
bro
like
three
out
of
those
four
first
ones.
I
haven't
done
work
on
them
this
week
and
I
might
be
able
to
get
to
some
work
to
it
this
week
this
upcoming
week,
but
I
can't
promise
anything
sure.
I
know
that
chris
asked
me
if
he
could
help-
and
I
frankly
haven't
had
the
time
to
answer
him.
A
Yeah,
I
think
one
action
item
if
if
chris
did
want
to
help
or
if
anybody
else
wants
to
jump
in
here,
this
just
needs
to
be
moved
over
to
the
project
status.
Repo
right,
that's
that's!
Perhaps
the
only
thing
that
needs
to
be
done
here.
I
think
on
this
one
I
know
they're.
A
But
more
space
I
mean
I,
there
was.
E
That
I
needed
to
sort
of
like
fold
then,
and
essentially
in
terms
of
like
taking
them
the
parts
of
the
growth
plan
that
are
like
that,
the
what
the
like
specific
actions
you
would
take
and
move
them
sort
of
like
below
the
plan
so
that
the
table
still
sort
of
like
fit,
and
I
started
down
that
path
and
then
like
that
and
I
ended
up
like
shaving
a
yak
and
so
so
that's
sort
of
where
I
was
at
so
yeah,
maybe
moving
it
and
then
having
this
conversation
again
in
that
space
is
something
that
could
work
too.
E
Okay,
either
way,
if
not
I'll,
have
some
time,
probably
like
early
next
week
or
mid
next
week
to
to
get
some
work
done
on
this
space
yeah
next
week.
Actually,
because
I
have,
I
have
some
commitments
as
to
actually
building
the
amp
plan
and
presenting
it
to
the
tsc.
So
I'm
certainly
going
to
get
that
to
the
end
of
the
by
the
end
of
the
week.
A
Okay,
great
great-
and
I-
and
I
I
see
in
the
notes
here-
we've
kind
of
grouped
these
three
items
together.
So
the
next
one
is
the
pull
request.
650.,
I
think,
probably
a
similar
state
there.
There
are
a
couple
of
action
items
here.
E
E
Yes,
they
absolutely,
I
think,
the
growth
stage,
the
251
on
the
651.
I
think
the
the
overall
question
here
was:
do
we
want
to
move
forward
with
removing
the
growth
stage
or
not,
and
the
follow-up
was
we
need
to
talk
to
actual
growth
stage
projects,
and
I
don't
think
that
there's
an
owner
for
that.
A
Yeah
I
I
mentioned
it
to
jory,
but
it
was
very
much
in
passing.
So
maybe
if
somebody
wants
to
drop
a
comment
in
pull
request,
650
tagging
jory
and
and
asking
if
she
would
I'll.
A
Cool
all
right,
so
that's
all
kind
of
a
work
in
progress,
and
I
encourage
folks,
though,
to
take
a
look
at
those
changes
and
make
sure
they're
aware
of
of
what's
going
on,
because
I
think
it's
important
stuff
cool
next
item
on
the
agenda
is
another
one
that
we
keep
touching
on.
A
This
is
issue
649.
My
last
comment
from
last
week
was
that
the
consensus
is
to
use
cpc
meeting
time
beyond
agenda,
to
do
some
working
session
work
and
then
to
create
a
template
with
some
of
these
items
here
looks
like
toby
had
created
the
issue
template
which
would
close
this
issue.
E
E
A
Yeah
I'm
looking
at
it
now.
This
is
pull
request
667,
so
it
looks
like
brian's
got
a
couple
things
to
do,
but
this
is
pretty
straightforward,
so
cool.
D
E
F
G
All
right,
let
me
actually
just
do
this
during
this
thing
great,
I.
A
Like
that
attitude,
cool,
well
we'll
we'll
check
back
with
you
in
a
minute,
but
we
will
move
on
accordingly
cool.
So,
let's
see
this
next
one
is
pull
request.
643.,
I
think
robin
you
added
a
few
of
them
here.
Right
was
the
what
we
were
waiting
for.
A
Amp
and
fastify
applications
are
in
this
pr.
So
I
think
that
this
is.
It
has
three
three,
you
know
approvals
and
it's
been
open
for
a
while.
So
unless
anybody
has
any
objections,
I
say
we
we
squash
and
merge
this
puppy.
A
Do
you
should
we
create
an
issue
for
that
bit
of
work
and
and
land
this
and
and
and
go
from
there.
H
A
So
if
you
are
able
to
just
take
a
moment
robin,
I
will
squash
and
merge
this,
and
if
you
want
to
just
create
a
quick
issue,
saying
that
we
want
to
make
them
more
discoverable.
That
would
be
great.
F
A
C
G
A
Great
yeah,
I
think
I
was
waiting
to
see
jordan's
changes
land
and
then
were
there
supporting
changes
we
needed
to
do
along
with
this
restructure.
The
existing
proposal
directory.
C
A
A
Great
looks
good
to
me
cool.
Well,
I
encourage
other
folks
to
take
a
peek
at
that.
We
can
get
some
reviews
on
there.
Do
the
add-on
work
and
you
know
get
that
update
to
the
proposal
process
landed.
I
think
it's
really
great,
because
the
previous
way
it
was
described
was
not
entirely
intuitive,
so
be
great
to
land
that
cool
moving
right
along
the
next
issue
here
is
issue
632.
A
G
A
Yeah,
it's
cool,
excellent
and
then
finally,
on
the
list
here
is
issue
592.
This
is
develop
annual
review
process
for
projects.
This
is
kind
of
the
I
think,
maybe
overarching
issue
that
started
all
the
growth
plan
work.
So
I'm
not
sure
we
have
anything
to
do
here.
H
A
Cool
great,
so
that's
that
is
all
that
we
have
on
the
agenda
and
we
are
only
22
minutes
in.
A
I
know
that
we
have
a
agreed
to
use
time
beyond
the
agenda
in
these
meetings
to
work
on
things
which
I
am
happy
to
do,
but
I
have
also
had
a
crazy
week,
so
I
don't
have
anything
prepared
or
would
not
necessarily
nowhere
to
dive
in
per
se.
Does
anybody
have
any
thoughts,
or
should
we
just
give
time
back
for
today.
H
I
hate
to
take
your
time
back.
The
only
thing
I
have
is
the.
I
noticed
that
rachel
sent
out
an
update
on
the
designs
for
the
supporter
program.
Is
that
correct.
H
Chance
to
talk
about
them,
yet
we
can
always
do
it
async.
What
do
you
think
are
good
next
steps
here.
B
Yeah,
the
initial
ask
was
for
folks
to
take
a
look
and
provide
feedback,
and
if
we
wanted
to
schedule
some
time
to
kind
of
go
through
everything,
we
could
certainly
do
that
as
well.
H
Yeah
we
can
either
we
can
provide
feedback,
async
over
email
and
then
kind
of
discuss
next
in
next
week's
meeting,
or
we
can
do
it
on
this
call,
I'm
happy
to
lead
it
if
people
need
to
drop
or
rachel.
Actually,
it
might
probably
makes
more
sense
for
you
to
lead
it
or
it
does.
D
C
A
I
think
you
know
whatever
time
we
had
available
to
it,
I
think
would
be
beneficial.
I
know
you
know
nobody's
had
much
time
to
prep
on
it,
but
I
don't
think
that
that's
necessarily
a
blocker.
A
And
to
for
I
don't
know
if
the
context
came
through,
but
this
is
the
individual
supporter
program
and
this
concept
of
javascript
landia
and
assets
around
that
that
we
were.
B
It
went
out
through
an
email
and
it
went
to
sort
of
the
sort
of
subcommittee
who
yeah,
who
was
initially,
who
initially
saw
the
first
set
of
creative.
G
C
D
H
Perfect
yeah
sounds
good
and
is
there
anyone
that
wants
to
see
them
that
currently
isn't
on
the
email
list?
Everyone
is
welcome.
A
H
Okay,
great
well,
then,
should
we
schedule
it
for
next
week.
H
A
A
E
F
A
Good
good
night,
I'm
gonna
stop
the
stream.