►
From YouTube: Node.js Community Committee Meeting
Description
A
We're
life,
okay,
so
welcome
everyone
to
today's
community
committee
meeting
for
it's
the
meeting
for
January
25th
2018
I
am
going
to
quickly
run
down
the
list
of
panelists
or
the
list
of
members
and
attendees
just
because
it
can
be
time-consuming
to
go
down.
14
members,
so
I'm
here,
I'm
Tierney
siren
I'm,
co-chair
of
the
community
committee.
We
have
mark
Hinkel
idea
of
the
DOJ's
foundation.
A
We
have
Maurice
Howard
Hayward,
who
is
a
observer
I,
believe
we
have
Olivia,
who
is
a
calm,
calm
member
tobyh
Farley,
who
is
in
a
observer
who
is
I
believe
at
the
point
where
they
can
become
a
member.
We
have
been
Michelle,
who
is
a
community
member?
We
have
Benjamin,
who
is
an
observer.
We
have
fat
fatty
I'm,
not
sure
if
I'm
pronouncing
that
right,
I
don't.
B
B
A
Who's
a
super,
first-time
observer,
we
have
Gregor,
who
is
a
member.
We
have
Jim,
who
is
a
member.
We
have
Menil,
who
is
a
member.
We
have
Rachel
white
who's,
a
member.
We
have
Toby
Farley
I.
Think
I
already
said
that
I
think
the
list
moved,
it
was
in
good
standing
and
can
now
become
a
member.
We
have
a
lead,
is
am
I
saying
that
right.
C
A
Awesome
and
then
we
have
zippy
Keaton,
who
is
works
at
the
node.js
Foundation
and
we
have
Sara
Conroy,
who
also
works
at
the
nodejs
Foundation
awesome,
so
that
was
much
faster
this
time.
So
first
thing
on
the
agenda
this
week
is
doing
a
report
from
the
initiatives
so
going
down
the
list
of
initiatives.
I,
don't
believe
we
have
anyone
from
user
feedback
present
other
than
myself
and
I
haven't
been
involved
in
the
past
two
weeks.
So
I
don't
know
if
we
can
get
an
update
from
that.
A
D
Sure
yep,
so
we
current
status,
is
that
we
have
our
proposal
out
and
it's
on
the
nodejs
medium
collection
seems
like
it's
been
getting
read,
which
is
great.
We
are.
We
have
our
official
working
group
when
they
post
that
in
here
just
pulled
in
our
official
working
group
and
we're
getting
more
active
with
that.
Adding
new
members
like
Samuel,
mashita
and
Richard
lit
our
and
yeah.
So
it
seems
like
there's
some
good
momentum
going
next
steps.
We
are
seeking
the
approval
of
localization
groups
for
our
proposal,
I'm
thinking
that
we
just
need
to
email.
D
The
members
representative
members
of
those
groups,
I
can
definitely
write
the
copy
for
that.
If
there's
in
an
official
foundation,
template
or
something
I
could
use
I'd
like
to
know-
and
the
biggest
thing
for
me
is
how
we
would
like
to
receive
feedback
on
something
like
this.
Should
we
send
out
a
poll-
or
you
know
just
request,
they
respond
to
the
email,
I'm,
not
sure,
because
I've
never
done
something
like
that
before.
So,
if
anybody's
I
advise
on
that,
that
would
be
great
and
beyond
that.
D
If
the
approve,
if
we,
if
we
are
approved
by
our
groups,
then
we'd
like
to
move
forward
with
the
internationalization
module
development
that
I
proposed
last
time
and
we
can
make
a
module
unsink,
it
was
crowded
and
get
a
doodle
going
for
the
next
working
group
meeting
to
cover
a
scaffolding
that
and
make
sure
that
we
bring
in
people
like
Zeke,
who
offered
to
consult
and
help
with
it,
as
well
as
members
of
the
site
redesign
project.
So
our
projects
are
syncing
nicely
and
then
also
be
present
for
the
upcoming
website.
D
A
E
E
F
Bet
so
you
know
a
few
things
to
tune
into
with
user
feedback.
We
have
been
meeting
tomorrow,
organizational
meeting
where
we'll
be
finalizing
the
details
of
our
9th
of
February,
first
public
user
feedback
meeting.
Where
we'll
be
engaging
the
individuals
who
have
gone
through
and
raised
their
hands,
we
sent
out
emails
and
requested.
F
F
F
A
Some
I
will
also
be
going
I,
don't
know
if
anybody
else
is,
if
anybody
else
is
going
to
feel
free
to
gregor's
planning
to
be
there
as
well.
Oh
I
paste,
oh
yeah,
my
lead,
maybe
I,
for
the
members
that
are
in
observers
that
are
in
the
chat
right
now
or
in
the
meeting
right
now,
I
pasted
an
issue.
It's
no
js'
admin
issue
44.
That
is
the
discussion
of
no
Gaea
space
available
for
no
GS
at
a
tax,
so
I
just
want
to
make
sure
we
connect
to
that
dot.
A
A
Awesome
so
it
doesn't
seem
like
anyone
else
is
anything
to
engage
with
in
that
so
I'm
gonna
move
on
to
the
agenda
items.
I
don't
have
a
show.
So
the
first
agenda
item
is
issue
163
and
actually
the
two
after
that
are
also
related.
I
wanted
to
include
these
because
they're
things
that
have
people
have
asked
of
the
community
committee
and
we've
not
given
them
a
solid
answer.
A
Yet
specifically,
163
is
a
very
interesting
one,
because
it's
the
Diagnostics
working
group
they're
looking
for
some
input
and
help
on
codifying
how
to
get
a
technical
writer
or
helping
get
someone
more
people
involved
to
help
document.
The
processes
of
that
and
they've
been
pretty
engaged
with
it
and
written
a
lot
about.
You
know
exactly
what
they're
looking
for
so
I
really
do.
Think
we
should
try
to
push
on
getting
some
answers
to
these
that
issue
and
then
also
the
other
two.
A
So
I
don't
really
know
where
we
want
to
go
with
this.
If
we
want
to
say
you
know,
this
is
this
is
what
we're
gonna
do
if
we
want
to
say
no,
if
we
want
to
say
yes
or
if
we
want
to
have,
you
know,
one-on-one
meeting
with
that.
Well,
one-on-one,
like
a
live
streamed
meeting
was
that
to
see
if
you
know
how
we
can
help
totally
open
to
anything
there
and
I
just
think
we
should
try
to
push
on
an
answer
for
them.
C
F
So
yeah,
whenever
I
hear
Technical
Writer,
especially
in
the
context
of
open
source,
my
spidey
senses
can
kind
of
go
off
that
you
know
worried
that
they're
not
taking
responsibility
for
documenting
the
things
that
need
to
be
documented
and
want
someone
else
to
do
that
heavy
lifting
or
is
this
polish
on?
You
know
context
that
content
and
context
that's
already
been
established
that
just
needs
to
be
organized
a
bit
better
since.
F
A
I
can't
really
tell
it
seems,
like
maybe
the
former
but
yeah
it
does
they're
looking
for
someone
to
help,
do
better
documentation,
basically
yeah
and
that's
that's
kind
of
where
it
lies,
and
so
I
think
you
know
this
has
been
open
since
November.
Second,
and
you
know,
I've
tried
to
engage
with
them
a
few
times
on
it
and
raise
it.
The
meeting
but
I
think
this
is
something
we
definitely
need
to
get
some
kind
of
answer
not
leave
it
open-ended,
and
there
is
a
lot
of
kind
of
thick
context
in
this
issue.
A
F
So
it
was,
you
know,
pretty
much
several
months
of
effort
and
aligning
that
and
you
know
getting
a
representative
from
the
benchmarking
working
group,
Michael
Dawson
engaged
with
user
feedback
to
to
be
able
to
do
that,
and
you
know
I
I,
don't
know
you
know
maybe
Olivia
in
the
website
redesign
like
who
could
what
group
could
be?
You
know
diving
into
that.
C
C
Is
maybe
the
suggestion
that
they
that
we'd
like
to
start
with
what
we
can
start
with
what
what
makes
sense
like
I
saw
in
that
issue?
There
was
some
comments
about
some
some
documentation
that
had
been
sort
of
started
on
the
side.
They
weren't
sure,
if
that
it
was
complete,
yeah
just
go
with
what
works
for
now
and
can
always
be
revised
after
yeah.
A
And
I
think
it
may
be.
You
know
something
that
we
that
could
be
helpful
and
kind
of
going
into.
That
matter.
Thing
is
giving
them
setting
them
up
with
a
baseline
of
okay,
it's
okay,
to
revise
your
documentation
and
have
that
kind
of
documented
and
and
enable
them
to
have
a
place
to
refer
to
when
people
want
to
compromise
or
update
or
help
give
a
document
to
that
or
change
the
broader
project
and
kind
of
have
that
be
what
they're
looking
for
cuz,
it
does
seem
like
they're.
They
want
a
person.
A
It
also
seems
like
this
is
a
way
that
would
be
a
way
to
help
is
documenting
it.
Does
that
make
sense
of
as
I
super
unclear
vague
in
that
yeah.
F
Yeah,
that's
good
yeah.
They
need
to
set
up
essentially
for
how
the
project
works.
They
need
to
set
up
a
baseline,
so
folks
can
begin
pyaari
against
it
right.
Even
if
it's
you
know
incomplete
or
you
know
not
well
formed,
starting
with
your
something
is
better
than
nothing,
and
you
know,
they're
gonna
have
to
do
that
anyway.
That
work
anyway
to
get
a
technical
writer
up
to
speed.
You
know,
if
that's
the
eventual
solution
anyway,
could.
A
Gm
could
could
you
know
market
to
do
in
there?
That
is
even
create,
create
an
issue.
I
don't
were
to
create
a
documentation,
baseline
documentation,
template
or
something
like
that.
I
think.
That's
a
good
way
to
start
and
I
can
take
that
if
no
one
else
wants
to
raise
their
hand
for
that,
but
I
do
think.
That's
a
good
way
to
start
have
a
discussion
about
that
and
then
push
forward
from
there
and
provide
resources
for
the
the
project.
The
technical
side
of
the
project
to
continue
to
drive
itself
refresh
wave
itself.
F
E
A
F
A
You
very
much
so
next
on
so
the
next
two
issues
are
very
similar:
they've
been
open
for
a
long
time
and
I
think
we
should
probably
again
either
decide
to
address
them,
close
them
and
B
wrap
them
up
or
act
on
them.
So
the
next
one
is
explaining
clue
civilly
better,
which
it's
a
very,
very
long
thread
that
has
a
lot
of
context
and
I
don't
know,
did
there's
a
lot
of
good
suggestions
from
Benjamin
in
there
I
don't
know
if
there's
anything
explicitly
actionable
at
this
point
in
it.
I.
E
And
that
note,
maybe
funnily
enough
I,
think
no
source
project
that
comes
fairly
close.
This
is
the
other
fork
that
was
made
some
time
ago,
which
has
a
value
stock,
which
I
think
explains
some
concepts.
Why
we
care
about
inclusivity
I,
think
it's
fairly,
like
the
values
expressed,
are
pretty
much
the
same
as
here.
So
maybe
we
can
take
a
look
at
that
and
see
if
we
can
maybe
kind
of
explain
some
things
in
our
space
that.
F
And
and
there
back
back
this
summer,
I
did
some
outreach
to
neo
Linux
foundations
and
stuff,
and
you
know
that
the
context
they
have
is
really
quite
rudimentary.
You
know
there,
you
perhaps
a
step
or
two
behind
us
in
terms
of
you
know.
Prior
type
is
in
this
and
as
not
as
I
think
they're
sort
of
abstract
discussing
about.
But
as
the
thing
that
is
in
our
particular,
you
know
core
values
in
how
they
operate
right.
I
think
that's
the
Delta
of
what
we're
trying
to
do
to
really
make
their
yeah.
A
B
B
A
D
A
A
On
the
board
of
their,
this
was
me
just
wondering
if
you
know
to
help
continue
to
grow
the
community
committee
and
people
engaging
in
it.
We
should
automatically
invite
observers
when
they
submit
a
PR,
the
distinct
the
thing
I
think
I've
recognized
is
people
don't
submit
PRS
unless
they're
already
an
observer
or
a
member
and
I
I
I'm,
sad
that
that's
the
case,
but
I
don't
know.
If
codifying,
this
is
beneficial,
but
I
don't
think
I'm
opposed
to
it.
E
A
A
F
You
know,
get
invited
as
an
observer,
and
so
you
know
I
think
we
could
invite
folks
and
you
know
to
become
a
member
and
then
the
observer
concept
is
a
bit.
You
know
rough
to
digest
as
someone
coming
in
from
the
outside
right.
What
am
I
observing
one
of
my
expectations?
So
you
know
I
expect
individuals
that
come
in
to
have
you
know
some
challenges
there.
So
just
you
know
helping
them.
You
know
get
invited
and
inviting
them
to
come
and
take
part
of
meetings.
A
D
Have
a
quick
thought
on
that,
too?
Being
that
this
is
the
community
committee,
we
all
represent
a
lot
of
different
communities
and
we
have
different
meetup
groups
and
places
that
we
go
to
I.
Think
just
making
a
mental
priority
of
being
able
to
ask
individuals
that
we
know
would
be
an
awesome
addition
to.
This
would
be
a
good
place
to
this.
C
I'm
I'm,
a
newer
member
so
and
and
I
definitely
haven't
been
as
engaged
as
I'd
like
to
have
been
so
definitely
I.
Think
some
of
this
feels
like
it's,
maybe
a
little
block
done
some
of
that
other
discussion.
That
should
happen
in
addition
to
that.
I.
Don't
necessarily
know
this.
This
could
just
be
me
if
we,
if
we
need
to
invite
everyone
who
participates
with
a
PR,
if,
if
we
make
it
known
in
other
ways
how
they
can
get
involved
in
joint
meetings,
so
yeah.
G
Yeah
I
agree
with
what
you
said:
Tierney
about
this
needing
to
be
like
a
bigger
discussion,
because
I
feel
like
also
like
not
just
making
the
meetings
of
requirement
is
a
lot
difficult
for
people
that
get
further
away
from
this
time
zone.
So
I
mean
I.
Think
that
that
just
is
like
a
discussion
that
we
need
to
have
in
order
to
discuss
what
does
being
a
member
mean
and
what
level
of
engagement
and
participation
and
how.
A
A
D
A
Okay
issue
has
been,
or
just
resolved,
at
least
in
terms
of
agenda,
okay,
current
strategic
initiatives
review.
So
this
is
an
issue
it's
issued
to
to
to
the
repo
the
community
committee.
Repo
I
opened
this
yesterday.
This
is
something
I
stated:
I
wanted
to
try
to
do
when
we're
appearing
in
these
strategic
initiatives
as
a
base
document.
There
are
several
current
initiatives
that
aren't
very
active,
specifically
community
events
and
notice
of
vandalism,
and
we
should
probably
review
those
just
in
terms
of
and
are
the
possibility
of,
continuing
them
or
closing
them.
F
A
Yeah
and
so
I
nominated,
you
know
two
or
three
I.
There
was
another
one
that
was
kind
of
tangential
the
office
hours
one,
but
you
know
I
I,
definitely
think
other
people
should
go
through
the
list
or
review
it
and
share
any
kind
of
feedback
on
the
different
initiatives.
We
have
either
the
need
champion
ones
or
the
the
current
initiatives,
and
you
know
it
thoughts
on
them,
because
I
should.
This
is
probably
just
a
hygiene
thing.
A
We
should
do
where
we
review
our
initiatives
to
make
sure
they're,
healthy
and
moving
forward
and
put
them
on
hold
if
they're,
not
yeah.
So
I
don't
know
if
there's
any
explicit
duze
in
here
other
than
review
that,
but
I
definitely
would
like
to
journey
and
put
our
feedback
from
the
from
everyone
on
this.
E
A
And
I
mean
there:
there
are
some
like
the
the
DOJ's
collection
that
don't
really
have
a
ton
of
activity
github,
they
have
activity
elsewhere.
I
know
Zippy's
gonna
call
right
now,
but
you
know
they
have
activity
through
the
email,
their
cooperation
with
the
foundation.
Things
like
that,
and
so
you
know
going
through
a
review
process
of
okay.
Is
this
working
outside
of
the
medium
we
normally
work
on?
Is
that
acceptable
is
probably
a
good
thing
to
do
for
everything?
F
I
I
have
a
you
know:
I've
been
since
interactive,
you
know
really
pushing
on
establishing
expectations
and
trying
to
document
in
particular
those
things.
I
have
an
expectation
with
your
something
like
an
initiative
where
you
know
I
would
expect
at
least
two
or
three
individuals
involved
in
the
initiative
for
it
to
be.
You
know
a
calm,
calm,
supported
thing,
I.
F
A
F
Right,
I,
don't
necessarily
think
that
it
needs
to
be.
You
know
at
the
you've
achieved.
Obviously,
if
it's
three
kaam
kaam
full
members,
yeah
yeah
we're
all
the
way
there.
But
you
know,
even
if
it's
a
you
know,
calm
calm
champion
with
a
couple
other
active
members
in
a
group,
then
we
have
a
group
that
back
that's
kind
of
the
minimum
baseline
for
TV
group,
and
you
know
the
evangelism
sorry.
These
are
all
slightly
starts.
A
H
Yes,
Ari,
oh
yeah,
there's
several
engaged
editors
to
it.
I
think
node.js
collection
is
a
little
bit
different
too,
because
we
have
our
engaged
editors,
but
then
we
also
have
a
lot
of
people
contributing
to
it
that
are
maybe
members
of
the
TSC.
They
might
be
members
of
the
no
GS
Foundation
they
might
just
be
even
outside
of
that
scope.
H
So
it's
maybe
a
little
bit
different
than
other
community
initiatives,
because
we're
getting
people
in
and
out
both
those
that
are
contributing,
as
well
as
editors,
I'm,
always
trying
to
find
more
editors,
just
because
I
think
that
ends
up
being
the
last
on
people's
to-do
list.
But
we've
been
getting
a
steady
stream
of
good
editors,
helping
us
with
some
of
the
submissions
that
come
in
so
I
see
that
actually
being
as
a
fairly
active
and
project
within
come-come.
H
But
you
know
I'm
always
willing
to
hear
feedback
on
how
we
can
make
the
documentation
of
that
activity
a
little
bit
more
visible.
I
think
we
originally
decided
to
go
with
Google
Docs.
So
when
people
are
writing,
it
can
be
a
personal
thing.
So
edits
can
be
a
little
bit
more
privatized,
but
if
you
want
to
have
people
post
their
submissions
on
a
github,
then
I'm
happy
to
do
that
to
you.
H
D
I've
thought
to
share
on
that
I
think.
There's
a
lot
of
priority
I
mean
any
any
kind
of
priority
revolving
around
teams
and
working
groups
like
I
think
mostly
compound,
including
myself,
are
just
not
aware
of.
What's
going
on
in
those
teams
and
working
groups
and
to
keep
them
up
to
speed
and
to
keep
activity
within
those.
Those
groups,
I
think
we
might
be
advantageous
to
add
a
quick
update
during
our
meetings
on
those.
A
D
I
was
just
gonna
say
in
inactive
groups,
or
you
know,
partially
active
groups
or
whatever,
sometimes
being
able
to
have
a
the
opportunity
to
have
it
on
the
agenda
to
share
it
makes
you
think
it
makes,
makes
the
active
members
think
about
it
and
be
able
to
push
something
for
something
out
before
they
have
to
share
about
it.
So
I
think
yeah,
I,
hear
you
and
I
think
that
it's
just
a
it's
a
double-edged
thing.
Yeah.
A
A
Yeah-
and
you
know
the
other
one
I
identified
it-
there
was
no
js'
the
community
events
which
has
had
zero
activity
since
it
was
created,
but
it
was
it's
for
me.
It
was
like
the
first
initiative
we
did
or
something
an
individual
now,
two
or
three
people,
but
one
person
took
on
and
then
they
did
not
continue
so
yeah.
That's
definitely
a
good
thing
in
like
we
should
have
a
definition
of
okay.
A
I
A
F
A
A
This
is
also
something
that's
been
discussed
in
the
past,
run
like
the
hex
stickers
for
each
individual
working
group
and
team,
and
things
like
that.
So
this
is
definitely
something
this
is,
you
know
a
lighter.
It's
lighter
sets
of
things.
It's
a
nice
kind
of
community
building
tool,
and
you
know
I
think
it'd
be
a
good
thing
for
the
project
to
do
at
you
know
something
like
no
interactive
or
the
collaborator
summit
have
for
a
percentage
from
each
of
the
working
groups
and
teams
and
committees
sharing
their
stickers.
D
A
D
A
F
A
And
I
know:
Rachel
raised
her
hand
and
Benjamin
also
raised
their
hand,
okay
cool,
so
do
someone
raise
your
hand
in
the
actual
meeting
not
used
to
that?
Okay
Maurice
did
you
want
to
say
something
I.
I
A
A
I,
do
I
have
a
kind
of
smallish
thing,
but
it
was
similar
to
one
of
the
issues
that
was
raised
earlier
today,
so
I
think
we're
ready
to
end
the
livestream.
So
thanks
everyone
for
coming
today,
and
we
will
see
you
all
two
weeks,
members
please
stay
on
the
call.
We've
got
some
stuff
talkback
awesome.
Thank
you.
Bite.