►
From YouTube: Node.js Community Committee Meeting 2020-05-14
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,
we
are
alive
thanks
everyone
for
joining
another
edition
of
the
nodejs
community
committee
meeting
we
meet
every
other
week
today
is
the
14th
of
May
in
the
year
2020
the
issue
that
has
the
agenda
and
all
the
details
is
issued.
Six
one
zero
in
the
community
committees,
repo
and
the
nodejs
org
and
in
there
you'll
find
a
link
to
the
Google
Doc,
for
you
know,
minutes
and
for
folks
to
add
themselves
to
the
attendees
and
of
course
we
published
our
meeting
minutes
two
to
github
after
the
fact
so
yeah.
A
B
A
Yep,
you
know
I'll
try
to
quickly
see
if
I
can
get
that
repo
up
I,
believe
it's
open,
Jas
foundation,
slash
summit
and
I'll
pop
it
into
the
chat
any
of
the
initiatives
here
or
any
of
the
you
know.
Folks,
in
the
project
you
know
feel
free
to
you
submits
sessions
for
the
Clapp
summit.
We
are
working
on
gathering
those
and
figuring
out
what
a
schedule
look
like
right
now.
I'll
just
add
the
the
plan
is
to
have
the
week
of
the
open
Jas
world
events.
A
That
event
is
Tuesday
and
Wednesday.
Monday
is
a
collapse
summit
plan
day
that
will
be
focused
on
new
contributors.
So
you
know
anybody
who's
new
to
the
project
or
wants
to
get
started.
That's
kind
of
like
the
data
really
focus
on
that
and
then
Tuesday
Wednesday
is
the
open,
Jas
world
event
and
then
Thursday
and
Friday
are
the
traditional
collab
summit.
Events
where
we
focus
more
in
on
some
of
the
issues
and
the
work
that's
happening
so
yeah
anything
else
in
terms
of
announcements.
C
I
can
do
the
mentorship
one
right,
so
probably
the
biggest
one
is
we
put
together.
A
blog
post
ideally
will
be
coming
out
soon.
Just
that
AJ
just
wrote
up
a
great
one
that
covers
some
of
the
differences
from
the
that
have
happened
since
the
last
blog
posts.
How
our
initiative
has
changed
focus.
What
we're
looking
for
call
to
action
is
for
a
mentee
for
the
mentorship
team
and
yeah.
So
that's
probably
the
big
one
salad
did
you
did
you
have
anything
you
wanted
to
add.
A
Great
great
I
mentioned
this.
You
know,
and
some
slack
but
I'll
mention
it
here.
I
have
a
biweekly
open
office
hours,
that's
part
of
the
open
jazz
foundation,
and
so,
if
any
of
the
initiatives
want
to
do
a
session
on
bringing
people
into
the
initiative,
whether
I
think
initial
internationalization
may
go
next
week,
which
is
great,
but
that
and
the
website
redesign
are
usually
popular
places
that
people
ask
about.
Mentorship
might
be
a
good
initiative,
so
you
talked
about
in
the
open
office
hours
too.
A
A
So
if
anybody
wants
to
see
more
oops,
no
that's
actually
the
Google
minutes,
which
reminds
me
folks,
add
yourselves
to
the
to
the
attendees.
There
I
think
we've
only
got
a
couple
people
out
of
there
and
then
I
just
paste
it
in
a
link
to
the
open
office
hours.
So
people
can
see
what
I
am
referring
to
cool
any
other
initiative
updates.
Saul.
Are
you
on
know?
If
there's
anything
from
internationalization
or
divvy?
Do
you
want
to
give
any
sort
of
update
on
website
redesign
or
anything
anyone
mod
Bueller,
hey.
D
D
D
E
D
They
thought
it
would.
It
would
be
beneficial
because
of
you
know
it's
easier
for
the
developers,
as
well
as
the
members
engaged
in
solving
issues,
as
well
as
adding
new
features
to
close
those
issues
faster.
Also,
we
can
get
a
working
session
more
quickly
if
it's
every
week
or
if
it's
every
two
weeks,
and
it's
like
you
kind
of
have
to
track
back
to
the
two
weeks,
what
happened
and
then
discuss.
Okay.
What
do
you
think
now
and
also
there's
so
much
development
that
is
happening
every
week?
D
I
feel
because
you're
getting
new
and
new
members
almost
every
day
that
it's
pretty
hard
to
try
keep
track
of
okay.
What
do
we
think
of
this
by
because,
by
the
time
we
finish
figuring
out
week,
one
one
week's
issues
there's
already
like
so
many
more
for
week.
Two
we're
closing
them
is
like
not
as
fast
so
things
are
being
slowed
down
then,
and
that's
another
reason
why
so
I
did
open
up
an
issue
about
that.
I
can
share
it
with
you
in
the
web.
D
It
was
one
of
the
things
that
also
was
brought
up,
and
and
but
we
wanted
to
make
sure
that
if
it
was
okay
because
we
didn't
wanna
because
I
brought
up
I
mean
we
also
brought
up
at
the
point
that
you
know
there's
just
so
many
meetings
and
there's
a
pretty
nice
schedule
with
everything
going
on
that
and
we
use
the
same
zoom
account.
So
you
don't
want
things
to
clash
and
also
then
making
sure
that
everyone
is
able
to
attend
like
please
the
core
members
at
the
same
exact
time
so
also
having
that
bandwidth.
A
A
D
A
So
you
might
want
to
think
about,
like
you
know,
if
folks
are
working
on
it
from
you
know
over
in
Asia
or
Europe,
or
what
have
you
you
know
you
might
get
more
people
involved
if
you
have
a
time
zone
that
is,
or
you
know
a
time,
that's
more
friendly
to
other
time
zones.
So
that's
something
to
consider
okay.
A
D
Plausible
for
for
you
to
actually
comment
on
the
issues
just
so
that
you
know,
everybody
knows
that
I
spoke
about
this
and
we
discussed
because
I
don't
want
to
take
I
will
take
it
back,
but
you
know
I
think
would
be
beneficial
to
have
that
on
record.
So
we
know
that
okay,
we
did
speak
about
it,
that's
okay!
It's.
B
Really
a
choice
of
the
team.
How
often
you
want
to
meet
the
only
thing,
as
you
mentioned,
that
you
should
take
take
a
look
at,
is
look
at
the
public
calendar
and
you
just
got
to
find
a
time
that
doesn't
conflict
with
the
other
meeting
so
that
you
can
use
the
streaming.
That's
that's
the
only
real
coordination
that
we've
done
so
far
between
the
different
teams
and
scheduling.
Okay,.
E
A
D
One
more
thing:
sorry,
we're
working
also
on
file
restructure,
and
all
of
that,
so
we
are
kind
of
stopping
all
new
development
for
features,
because
there's
just
so
many
updates
with
old
file
structure
and
new
file
structure
that
if
we
do
go
to
merge
everything
at
once
is
going
to
be
really
big
of
a
chaos.
But
you
already
had
a
lot
of
those
issues
where
things
were
overlapping
things
got
deleted
and
features
were
missing,
and
things
like
that.
So
that
is
one
big
thing
that
we
are
going
to
be
working
on.
D
E
In
an
outreach
initiative,
we
have
actually
been
talking
about
the
you
know,
committee
guideline
community
page
and
give
actually,
you
know
kind
of
completed
that
and
we
were
hoping
to
put
it
back
and
at
a
PR
into
the
node
J
star,
dev
in
website
design
initiative.
So
that's
that
of
that
there
was
an
initiative
to
kind
of
have
a
hackathon
around
building
meetup
in
our
box.
E
A
Know
cool,
let's
see
from
across
project
console
standpoint.
You
know:
we've
been
busy
code
of
conduct,
process
and
procedures
fleshing
that
out
further.
You
know
there
there's
we
want
to
have
things
in
place
for
the
projects
to
use
those
guidance
and
to
and
to
use
in
their
projects
and
also
to
have
some
processes
around
any
sort
of
escalation,
or
things
like
that.
A
A
B
A
B
I
added
that
one
basically,
the
the
team,
the
napi
team
is
had
did
some
workshops
and
we'd
like
to
move
the
content
for
the
workshops
to
the
Nodine
examples.
Repo
and
the
you
know.
The
best
way
we
think
to
do
is
deliver
that
through
the
github
pages,
we're
looking
at
using
gatsby
to
be
consistent
with
what's
going
on
in
the
website
redesigned.
But
you
know
the
thought
is:
that's
a
good
way
to
deliver
it
to
start
with.
B
We
don't
really
have
a
documented
in
in
our
guidance,
what
you
need
to
do
if
you
want
to
do
that
as
a
team,
so
I
opened
the
issue.
There
was
some
discussion.
The
TSC
meeting
earlier
today
and
I
think
the
the
most
of
the
people
were
saying
it's
good
that
we
we
asked
for
a
an
admin
issue.
You
know
something
where
you
open
it
amiss.
You
know
objection
70,
two
hours,
just
like
asking
for
repose.
B
A
A
A
So
yeah
I
encourage
folks
to
take
a
peek
at
that
see
if
they
have
anything
to
add
there
and
and
maybe
we'll
see
what
lead
next
week
can
update
cool,
and
perhaps
this
is
the
next
agenda
item
is
related.
This
is
pull
requests
37
in
the
node.js
collection,
repo
and
I.
See
oh
so
well,
lead
open
this
in
July
of
last
year.
A
A
D
So
we
have
kind
of
put
it
on
the
back
burner
for
now,
because
we
don't
know
a
lot
of
the
core
members,
but
we
don't
have
a
lot
of
people
from
the
core
team
actually
come.
So
we
wanted
to
do
like
a
vote
like
a
constant,
like
a
team
wide
vote,
trying
to
see
like
what
way
can
we
actually
do
the
mock-ups
and
redesign
for
that
portion?
D
But
since
we
didn't
have
a
lot
of
people-
and
there
was
just
it
wasn't
going
anywhere
and
like
the
discussion,
because
it
was
just
a
lot
of
back-and-forth
and
we
thought
that
it
was
good
to
put
it
to
rest.
So
we're
gonna
bring
it
up
on
the
next
meeting
and
get
it
solved.
Hopefully,
people
that
are
on
the
team
to
join
and
we
can
actually
get
it
done.
Okay,.
A
D
A
F
Before
I
finish,
I
have
some
doubts
about
the
process
to
label
agendas
in
the
community
community
I
open
it
up
request
last
week,
two
weeks
before,
and
there
is
a
ProQuest
open,
though
the
community
community
it
607
I,
would
like
to
know.
What's
the
process
true
to
put
in
the
agenda
for
the
kong-kong?
Yes,
it's
just
I,
don't
know,
I
don't
like
to
bother
and
ask
so
I
was.
F
A
Sure,
let
me
let
me
first
I
will
add
a
label
to
this
pull
request
and
you
know
feel
free
to
ping
the
calm,
calm
team
in
in
a
comment
to
ask
about
that
in
the
future.
But
you
know
considering
your
work
and
the
community
committee.
You
know
I
feel
like
number
one.
We
do
need
to
update
the
readme
and
for
you
know
the
members
and
everything-
and
you
know
if
you,
if
you
wanted
to
be
a
part
of
the
community
committee
members,
that's
that's
something
you
could
explore
as
well.
A
A
F
F
Champion
as
David
sorry
I
just
found
some
buds
that
I
wish
to
fix
together
with
this
commit.
But
if
you
guys
thinking
that
you
should
do
work
with
different
group
s
for
address
different
issues,
even
if
it's
the
same
file,
it's
no
problem
for
me.
I
can't
just
undo
the
changes
and
let
only
the
Dave
determine
as
a
champion
for
this
ProQuest
and
open
up
later
ProQuest
to
fix
that
those
feeling.
A
A
No
I
totally
understand
I
used
to
work
on
a
team
where
we
had
a
very
strict
rule
about
that,
so,
but
but
yeah
okay.
So,
let's
see
I'll
look
at
both
of
those
PRS.
When
we
conclude
the
speeding
and
we'll
see
how
we
can
move
forward
on
those
great
anybody
have
anything
else
they
want
to.
They
want
to
add
or
ask
or
talk
about.