►
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).
B
B
B
Nice,
that's
a
good
time
cool.
So
if
we
are
moving
ahead,
what
do
we
have
any
announcements
or
anything
before
we
get
into
our
agenda
here?.
A
Announcements,
wise
and
I
think
we're
we're
fairly
so
this
afternoon
we've
got
a
nice
fun
standard
strategy
or
standards
working
group
meeting
where
we're
going
to
focus
on
sort
of
the
2021
strategy.
We
sent
out
a
survey
to
the
maintainers
and
to
get
some
more
just
input
on
that
conversation.
Of
course,
everyone
is
invited
to
come,
participate
we're
not
going
to
record
it
because
a
it's
going
to
be
a
two-hour
meeting
and
b
we're
just
going
to
throw
spaghetti
at
walls.
So
you
know
please
do
do
come.
A
That
link
is
on
the
public
calendar
and
just
as
a
heads
up
and
if
that's
something
that
we're
interested
in
also
this
week
we
are
organizing
our
next
jslandia
discussion
meeting.
So
that's
ours,
our
our
supporter
program
idea
and
I
think,
we're
trying
to
target
wednesday
or
friday.
For
that.
I
don't
think,
we've
exactly
settled
on
the
time
and
then
we've
got
the
the
program
committee
meeting
also
on
thursday.
So
if
you're
interested
in
getting
involved
with
the
the
event,
then
please
please
do
come
to
that.
B
Thank
you
good
stuff,
great.
If
there
are
no
other
meetings,
are
there
any
like
board
updates
or
anything
that
we
need
to
share?
Is
there
a
board
meeting.
D
B
Should
we
be
planning
for
another
board
seat
election?
I
feel
like
those
always
creep
up
on
us,
but
I
just
thought
about
it.
It
was.
A
I
feel
like
it
was
after
the
first
of
the
year,
because
our
other
one
was
it.
B
Okay,
all
right
cool.
Well,
let's
keep
that
in
mind.
Maybe
we
should
even
open
an
issue
just
to
have
it
there,
so
we
start
to
figure
out
what
we're
doing
there.
B
Rock
and
roll,
so,
let's
get
into
the
agenda
the
it's
a
short
agenda
looks
like
what
six
six
things
on
here.
If
anybody's
got
anything
else,
they
want
to
raise.
Definitely
let
me
know,
but
the
first
one
here
is
moving
the
cpc
meetings
to
a
bi-weekly
cadence
issue.
680..
B
I
think
we've
got
consensus
on
doing
this.
Just
to
kind
of
recap.
The
idea
is
to
essentially
go
to
every
other
week,
but
perhaps
to
keep
the
off
week
as
like
a
working
meeting.
If
we
want
to
use
it
for
something
specific
or
to
just
get
together,
I
mean
I'll.
Probably
just
plan
to
you
know
either
do
a
specific
thing
or,
if
there's
nothing
going
on,
then
I'll
use
that
time
to
focus
on
any
issues
or
things
that
need
to
be
dealt
with.
B
So
the
thought
was
that
we
would,
you
know,
have
that
working
meeting
at
the
same
time.
So
essentially-
and
I
could
paste
this
into
the
chat-
because
it's
probably
easier
but
like
you
know,
say
week-
one
is
at
1700
and
then
the
next
week
would
be
the
working
meeting
at
1700
and
then
the
third
week
would
be
at
1900
and
then
the
official
meeting,
and
then
the
fourth
week
would
be
like
a
1900
working
meeting
like
I
said.
B
If
we
are
to
go
forward
with
this,
the
one
thing
we
need
to
work
out
is
that
it
would
end
up
conflicting
with
standards,
meetings,
board,
seats
and
last
day
of
february
and
august.
Okay,
perfect,
thank
you
chris.
So
maybe
that's
something
we
can
talk
about
today
and
the
standards
meeting,
jory
and
others
and
see
what
we
want
to
do
about
that.
B
I
was
thinking
about
this
this
issue
this
morning
and
I'm
wondering
if
we
should
just
not
make
any
changes
until
the
first
of
the
year
and
then
we
don't
have
to
worry
about
any
of
this
and
we
can
kind
of
sort
out
the
standard
side
of
it
and
move
forward
along
those
same
lines.
I'm
wondering
what
people's
feelings
are
for
the
cpc
meetings
for
december,
I'm
working
this
week
and
next
week,
but
then
we'll
be
off
the
rest
of
december.
B
So
I
don't
know
you
know.
If
anybody
has,
I
don't
know
if
we
have
an
issue
for
like
december
meetings
and
what
we
want
to
do,
but
I'll
I
won't
be
around
for
some
time.
A
I
think
it's
probably
prudent
to
to
start
that
cadence
after
the
start
of
of
2021,
just
because
I
think
it
will
be
easier
for
people
to
adjust.
I,
but
I'm.
I
am
happy
either
way
joe.
I
can
carry
on
these
in
your
absence.
I
don't
mind.
I'm
volunteering
myself
to
to
chair,
I'm
not
a
very
good
joe,
but
I'm
a
okay
jory.
B
F
G
F
B
All
right,
I'm
just
gonna
kind
of
throw
this
issue
in
there.
It's
pretty
lightweight,
but
you
know
it's
there,
so
we
can
talk
about
it,
I'll
drop
it
in
the
chat.
B
I
will
also
just
drop
something
in
the
bi-weekly
meeting
issue
that
we
will
start
this
in
january,
2021,
the
newest
year,
that
I
can't
get
to
soon
enough
cool
all
right
great,
that's
that
next
up
is
the
this
issue
for
review
individual
supporter
program
designs.
I
don't
know
if
we're
there
yet,
if
we
want
to
do
anything
with
this
today
or
if
we
want
to
wait
until
after
this
week's
meeting.
C
I
posted
a
comment.
Our
graphic
designer
was
really
swamped
with
another
linux
foundation
event
and
then
we
had
the
holiday,
so
we
did
get
it
over
the
holiday
and
we
have
so
many
choices
that
we
still
need
to
narrow
them
down
with
the
meeting
that's
happening
later
this
week,
and
then
we
can
share
next
tuesday,
great
yeah.
B
Cool
moving
along,
we
have
this.
This
issue,
658
develop
growth
plan
template.
This
is
the
issue
to
track
the
development
of
a
growth
plan
template
as
discussed
in
592..
I
don't
know
why,
but
my
brain
always
kind
of
just
breaks
on
this.
F
Issue
we
need
to
close
this
and
I'm
going
to
close
it
because
you've
actually
opened
the
clone
of
that
one
and
project
status.
Okay,
because
we
were
moving
it
and
you
did.
F
You
did
the
move,
and
so
now
it's
in
project
status,
where
it
belongs,
and
there's
actually
some
comments
that
christian
just
added
recently
on
that
issue,
which
is
a
project
status
56
which
we
could
discuss
if
we
wanted
to
right
now,
real
quick,
essentially
christian,
was
suggesting
changing
some
of
the
language
in
ways
that
I
would
agree
with
would
be
better.
F
However,
they're
changing
the
requirements
that
are
described
in
the
project
project
progression.md,
which
is
in
the
root
of
the
cpc
repository,
and
so
I'm
not
sure
that
that's
the
right
place
to
do
that,
like
you
know
we're
getting
into
this
problem
when
we
have
recommendations
on
one
side
and
templates
on
the
other
again
right,
and
so
you
know
maybe
figuring
out
what
we
want
to
do,
there
would
be.
We
can
do
this
offline.
We
don't
have
to
do
this
now.
H
H
F
And
if
people
are
cool
with
me
closing
six
four
seven
in
favor
of
project
status,
56
and
I'm
just
gonna-
do
that
right
now.
D
F
A
Yeah,
that
sounds
good.
I
think
that'll
reduce
some
confusion
in
terms
of
you
know
where
we
should
be
commenting
as.
B
A
F
We're
waiting
for
the
outcome
of
the
questions
that
joey
asked
the
different
maintainers
of
the
existing
growth
project
to
make
a
decision
about
this.
I
know
that
I
owe
georgia
response
from
the
am
perspective
and
I'm
having
conversations
about
this
later
today.
So
I
don't
know
if
jordan
you've
gotten
responses
from
other
folks
that
our
growth
project
and
what
those
responses
were.
A
We've
just
had
a
couple
and
the
responses
that
I've
received
on
this
so
far
are
come
from
the
architecture
project
and
also
from
webdriver,
and
they
are
in
favor
of
of
this,
and
they
see
the
sort
of
prudence
of
simplification
and
are
happy
to.
A
B
I
know
chris
hiller
is
on
the
call
here
and-
and
you
brought
up
a
couple
of
comments
here,
do
you
feel
like
your
comments
were
addressed,
or
do
we
have
anything
open
that
that
we
should
discuss
further
here.
H
Yeah
I
gotta
get
back
to
that
issue
and
I
know
jory
replied,
I'm
not
sure
if
anybody
else
did
but
yeah.
I
I
I
wouldn't
say
that
I'm
necessarily
in
favor
or
against
this
idea,
but
yeah.
I
think
I
just
need
some
some
clarification
and
you
know
basically,
I
just
need
to
go
back
and
revisit
it
and
and
come
further
and
jory.
I
hope
that
not
hope
hope
is
not
the
word.
H
I'm
I'm
tired,
it's
what
I'm
trying
to
say
is
jory.
I
did
not
respond
to
your
email
because
I
responded
in
the
issue.
Instead,
yeah.
C
B
And
should
we
dig
into
it
at
all,
or
I
mean
or
even
just
kind
of
explain
what
some
of
the
thinking
is
here
so
that
chris
has
a
better
idea
or.
E
H
Many
words
so
yeah
yeah.
I
I
think
I
I
I'd
like
to
do
that
in
the
email
or
the
issue,
and
then
maybe
maybe
we
can
discuss
if
we're
gonna
if
we're
gonna
have
one
of
those
meetings.
That's
about
two
hours
later
than
this
one
next
week
discuss
that.
Okay.
B
Yeah,
if
you
want
to
chat
it
all
offline
too,
just
ping
me
we
can
discuss
that's
helpful,
all
right
cool,
so
we'll
leave
this,
as
is
for
now
talk
more
about
it
in
the
issue
offline
next
meeting
and
go
from
there.
B
Cool
anything
else
on
any
of
this,
like
removing
growth
and
growth
plan,
template
and
any
of
that
stuff
that
we
want
to
talk
about.
C
F
F
B
The
brain
yeah-
and
I
think
you
know
just
to
reiterate
and
close
this
conversation
up-
you
know
the
the
thinking
is
that
this
will
improve
things
and
make
them
simpler
and
yeah.
We,
we
are
hoping
for
no
negative
impacts
but
more
positive
impacts.
B
All
right
cool,
so
the
next
issue
and
the
final
item
on
the
agenda
is
issue.
632
provide
implementation
guidance
for
dco
cla.
You
know
brian
is
offline
right
now,
so
maybe
there's
no
update
on
this.
I'm
guessing.
C
B
Rock
and
roll,
that's
that's
our
agenda.
Is
there
anything
else
that
anyone
wanted
to
bring
up
or
discuss
before
we
drop
into
a
private
meeting.
I
I
just
wanted
to
flag
that
the
linux
foundation,
along
with
openjs
foundation,
is
running
their
cyber
monday
sale,
which
includes
all
of
the
node.js
training
and
certifications.
So
if
that
is
something
that
you
are
interested
in
looking
into
now
is
a
good
time
to
consider
purchasing.
B
Great
thanks,
yeah
there's,
there's
been
some
blog
posts
and
social
media
and
that
stuff
out
there
too.
If
you
want
to
help
promote
it,.
J
I
just
have
a
quick
question
about
that,
if
like,
if
we
want
to
direct
people
to
it,
is
there
links
or
anything
or
where
should
we
direct
people,
because
I
know
I
had
a
few
people
reach
out
to
me,
so
I'm
just
confirming.
I
So
we
do
have
a
blog
post
on
the
node.js
medium,
which
has
all
of
the
kind
of
the
bundles
of
the
links.
We
really
tried
to
point
people
to
the
most
direct
page,
so
it's
easy
and
they
don't
have
to
kind
of
sort
around.
So
I
can
drop
that
link
into
the
chat
and
then
this
sale
goes
on
through
december
8th.
I
So
in
my
excuse
me
in
my
cpc
email
I
can
send
out
information
and
tweets
and
things
like
that,
if
that's
helpful
for
everybody,
but
let
me
drop
in
the.
I
A
A
It'd
be
great
to
go
ahead
and
get
us
a
heads
up
that
if
you
need
signal
or
want
signal,
boost
or
posting
or
anything
from
openjs
found
from
our
website
or
twitter
accounts,
I
know
amp's
got
something
we'll
probably
publish
you
know,
and
we
want
to
share
with
the
broader
community
if
we
can
get
those
on
the
calendar
early
this,
since
it's
december
it'd
be
helpful.
B
Cool
I'll
just
add
two
that
you
know
looking
through
the
open
issues
that
we
have
like
some
things,
that
if
anyone
is
wanting
to
work
on
something
the
create
annual
review
process
for
cpc
and
the
foundation,
is
one
issue
and
create
annual
review
process
for
non-growth
projects.
B
F
G
Yeah
cool,
if
I
made
there.
F
Were
two
pull
requests
that
are
just
like
really
small
tiny
changes,
one
from
joey
one
for
myself,
which
would
be
good
to
just
merge
to
clean
up
at
some
point
and
one
of
them
raises
the
question.
Well,
mine
raises
the
question
of
sort
of
editorial
changes
to
things
that
the
board
should
technically
approve,
which
seems
kind
of
like
something
we
should
have
faster
like
a
fast
pass
focus.
It
doesn't
really
make
sense.
D
Yeah
I
had
I
had
ping
brian
about
that.
We
should
either
document
like
for
those
kinds
of
things
what
the
policy
is,
and
I
think
my
first
take
would
be
like
asking
if
it
really
needs
board
approval
or
not,
but
we
need
to
write
it
down
one
way
or
the
other,
and
I
think
maybe
it's
good.
If
brian
takes
the
first
cut
based
on
the
current
bylaws,
if
we
think
it's
needed
or
not,.
B
C
D
D
B
Right
cool
anything
else
before
we
drop
into
private
session.
B
No
all
right
cool.
Actually,
let
me
just
peek
at
the
recording
and
nobody's
there
cool.