►
From YouTube: OpenJS Foundation AMA with Node.js CommComm
Description
The OpenJS Foundation is a member-supported non-profit organization that provides a neutral home for some of the most important project in the JavaScript ecosystem.
Learn more and join us at https://openjsf.org
A
Okay,
we
are
live
on
YouTube,
hello,
everybody,
okay
and
well.
We
are
live
on
YouTube.
Are
you
getting
the
feedback?
I
am
I.
Just
I
just
needed
us.
Sorry
about
that.
Y'all,
okay,.
A
Okay,
awesome
hi
everybody.
We
are
live
right
now
with
the
node
J
s
community
committee,
for
the
open,
Jas,
Tanisha
and
series
on
AMAs,
and
today
again
we
will
be
talking
to
the
nodejs
community
committee.
My
name
is
Rachel
romoff
and
I
support
the
open,
jazz
foundation
for
marketing
communications
and
before
we
get
started
with
these
questions,
I
think
it
would
be
good
to
jump
in
and
do
some
introductions
with
the
folks
who
are
joining
us
today.
So
I
don't
know
who
wants
to
kick
us
off,
but.
B
A
B
B
C
Previously,
it
was
serving
as
the
chairperson
for
the
community
committee
until
journey
took
over
about
how
long
have
been
tyranny
two
months,
some
like
that
also
involved
with
an
assortment
of
other
open
source
projects.
Block
vapid
Brendan
is
the
the
name
of
the
game.
Here,
I
yeah
excited
be
talking,
yell,
Neil,
bigger
way.
D
D
A
Thank
you
all
so
much
for
joining
us
this
morning.
We
can
jump
right
into
questions,
but
before
we
do,
for
those
who
have
questions
for
the
calm,
calm,
please
feel
free
to
drop
those
in
our
YouTube
chat
and
we
will
get
to
those
questions
and
so
jumping
right
in
the
first
question
we
have
is:
what
is
the
community
committee
no
js'?
What
is
its
relationship
to
the
open,
j/s
foundation
and
what
purpose
does
it
serve?.
B
I'll
start
off
this
one,
so
the
community
committee,
no
js',
so
I'm
gonna
kind
of
answer,
the
first
one,
the
last.
At
the
same
time,
the
community
committee
is
intended
to
help
address
community-focused
things,
so
outward-facing
efforts.
So
typically-
and
you
know
my
perception-
the
TSE
is
typically
the
technical
steering
committee,
the
big
body
that
governs
the
a
lot
of
the
technical
internal
sides
of
node,
whether
that's
core
or
the
various
I,
think
160
repos.
Some
of
those
are
ours,
but
you
know
100
100's
repos
that
they
govern.
B
You
know
those
are
typically
internal
facing
things,
whereas
the
community
committee
typically
focuses
on
more
external
facing
things.
So
this
is
like
you
know,
mentorship
and
that
initiative
or
the
which
they
redesign
initiative
or
the
outreach
initiative.
You
know
various
various
other
things
they're
intended
to
be
outward
facing
and
then,
in
terms
of
its
relationship
with
the
open
J's
foundation,
the
noches
community
committee
was
very
active
and
participating
in
the
transition
from
noj's
foundation
it
to
the
open,
J's
foundation,
specifically
in
terms
of
community
and
ecosystem
impact.
B
That
was
something
that
myself
and
many
other
folks
who
are
on
the
kumkum
care
a
lot
about,
and
that's
the
area
that
we
generally
focus
in
already,
and
so
it
was
a
natural
kind
of
fit
for
us
to
be
able
to
participate
in
that
way
in
the
formation
of
the
new
foundation.
And
then
on
top
of
that,
we
currently
participate.
B
I
believe
two
members
myself
as
a
regular
member
and
then
giuseppe
as
a
voting
member
from
the
you
know,
JS
project
on
the
CPC,
so
the
cross
project
Council
for
the
foundation,
and
so
you
know
our
goal
generally-
is
to
help
empower
the
developers
who
are
you
know
in
the
GS
or
who
would
use
those
GS.
So
that's
you
know,
according
to
the
NPM
statistics,
11
million
developers,
but
you
know,
empower
every
single
one
of
those
to
kind
of
come,
find
more
success,
JavaScript
and
with
node
yeah.
C
In
my
mind,
is
there's
something
there
to
help
assure
that
sure
that
community
through
to
fruition
is
the
wrong
word,
but
some
with
some
degree
of
clarity,
and
so
all
the
projects
associated
with
it
are
very
focused
on
the
people
that
are
are
engaging
with
the
project,
whether
it
is
as
a
consumer
of
it,
somebody's
using
node
for
their
work
or
for
their
side
projects
they're
just
fun.
D
If
any
of
that
sounds
good
to
you
like
here,
and
you
mentioned,
the
car
come
was
heavily
involved
in
the
transition
from
the
nodejs
foundation
to
open
Jess
and
a
lot
of
the
spirit
of
what
Kham
Kham
like
to
bring
into
the
community.
Well.
Well,
it's
transferred
as
part
of
that
process
and
the
continued
involvement
of
some
people
in
kumkum.
Like
turn
you
mentioned
earlier,
he
continues
to
see
that.
B
Again.
However,
there
are
a
few
things
that
we're
getting
to
do
be
open.
Jess,
you
know
know
just
joining
the
yes
Foundation
gave
us
an
opportunity
to
kind
of
tweak
and
clean
up
some
of
our.
You
know
existing
infrastructure
and
governance,
so
we're
going
through
and
doing
a
lot
of
that
right
now.
Additionally,
we're
introducing
or
I'm
hoping
we're
introducing,
but
we're
working
forward.
B
Specifically,
you
know
we're
one
of
the
discussions
that
I
proposed
is
okay,
ours
for
the
Comicon,
which
is
inspired
by
what
electron
it
does,
but
yeah
we're
kind
of
moving
toward
being
a
little
bit
more
lean,
a
little
bit
more
goal,
and
that
includes
you
know
that
will
trickle
down
to
every
single
aspect
of
every
initiative,
whether
it's
you
know
website,
redesign
or
mentorship,
or
you
know
social
media
stuff
that
we're
doing
or
you
know,
various
aspects
of
the
work
we
are
already
doing.
Yeah.
C
What
might
be
a
good
way
to
approach
this
and
just
go
through
the
list
of
working
group
initiatives
we
have
in
the
comm
come
because
there
is
a
you
know.
We,
the
con
column
itself,
meets
once
every
other
week
for
about
an
hour
Thursday's
that
I'm
not
gonna,
give
it
time
to
grow
on
different
different
time
zones,
but.
A
C
C
How
can
we
clear
the
pipes
for
individual
contributors
for
working
groups
in
the
calm
calm
once
you
get
beyond
that
and
go
down
into
the
individual
working
groups
and
initiatives,
you
get
some
very
granular
projects
that
have
very
well
scoped
goals
and
serial
of
that.
Okay,
our
idea
for
forgetting
in
ordinary.
C
B
B
C
Only
in
the
Eisen
and
working
group,
it's
not
only
actually
translating
content,
which
is
always
needed.
We're
using
a
service
called
crowdin
crowdin.
Thank
you
to
actually
provide
the
translation
infrastructure,
but
it's
also
all
the
all
the
pipes
around
that.
So
how
do
we
actually
deliver
those
translation
up
to
the
website,
and
so
I
will
talk
about
website
redesign
in
the
moment,
but
I
am
working
closely
with
ice
and
then
to
make
sure
that
infrastructure
actually
works.
B
The
next
one
that
we're
kind
of
working
on
is
mentorship,
so
this
is
an
initiative
where
we
are
trying
to
mentor
folks
to
be
able
to
contribute
to
node,
so
people
have
signed
up
independently
and
then
from
there
we've
assigned
them
mentors.
We
have
a
very
large
pool
of
mentees
and
perhaps
not
enough
mentors,
because
the
pool
is
so
large
but
yeah.
B
This
is
basically
focusing
on
enabling
more
folks
to
contribute
to
node
and
getting
kind
of
a
little
bit
more
hands
up
like
rather
than
being
thrown
to
the
Sharks,
and
you
know
just
kind
of
go
figure
it
out
with
the
documentation
that
we
have
more
approaching
it
as
we're
good.
You
know,
I'm
gonna
sit
down
with
you
and
no
I
is
a
generic
person.
Who
is
a
mentor?
Not
not
me
explicitly,
but
you
know
a
mentor
will
sit
down
with
someone
and
kind
of
help
them.
You
know
get
cork
nontrivial
core
contributions
in.
C
D
D
That
would
be
very
helpful
to
have
more
chip.
People
chomping
at
the
bit
would
be
user
feedback
and
relays
it
to
that
enterprise
user
feedback.
Although
I
believe
that
enterprise
user
feedback
is
far
more
active
than
the
currently
the
user
feedback
is.
The
purpose
of
those
groups
are
to
well
focus
on
the
process
of
bringing
infrastructure
and
collaborators
for
more
than
just
individual
user
feedback
to
the
project.
I
think
I
I
believe
the
champion
for
that
was
D
sha.
Although
that
may
have
changed
recently.
C
Yeah,
it's
a
it's
kind
of
a
like
most
most
things:
the
hierarchy
structure.
We
have
the
calm,
calm,
which
has
active
sitting
members
on
it,
which
focus
on
governance
and
again
clearing
the
bytes
and
then
individual
working
groups
have
a
member
on
them
who
are
tapped
with,
let
me
know
said
assuring
them
certain
urban
issues
through
and
providing
updates
the
larger
larger
group
but
yeah.
The
user
feedback
initiative.
B
B
So
some
of
the
other
initiatives-
sorry
going
down
the
list,
social
media
delegates,
that
this
is
a
very
new
one
that
Rachel
and
myself
have
been
working
on.
Basically,
you
know:
we've
talked
about
it,
a
bit
public
place,
I!
Guess
it's
it's
talking
about
significantly
public.
So
it's
fine
yeah!
So
you
know
it's
to
be
announced
program,
basically
focusing
on
enabling
more
folks
to
access
and
help
out.
You
know
different
ways.
B
You
know
directly
on
a
official
social
media
channel.
You
know
in
the
form
of
a
long-form
blog
post,
so
yeah,
that's
the
collection.
We
do
have
a
bunch
of
work.
There
that's
happening
so
we're
kind
of
again
for
a
finding
it
a
bit
in
in
various
ways
right
now
that
work
is
being
done
in
a
PR
in
the
repo
which
you
can
find
linked
from
the
noches
community
committee,
repo,
which
is
at
github.com,
slash,
nodejs,
slash
community
committee.
B
You
can
find
all
this
also
and
what's
that
we
shoulda
led
with
that
one
we
probably
should
have
yeah.
So
you
can
find
you
know
all
the
kumkum
repos
in
the
noches,
github
org
I.
Think
community
committees
actually
also
pinned
there
so
yeah
you
can.
You
know,
find
all
of
this
stuff
there,
but
yeah
that's
know.
Jess
collectin
specifically,
is
one
that's
currently
in
progress
and
if
anyone's
interested
in
kind
of
helping
out
with
that
we'd
love
that
help
specifically.
C
Kind
of
work
involved
with
the
the
collection
is
betting
submitted
blog
posts
through
media.
So
you
submit
a
request
to
an
email.
Yes
for,
like
a
long
form,
content
I'd
love
to
share.
It
goes
through
a
round
of
editing
and
vetting.
Some
folks
who
signed
up
to
ensure
the
content.
There
is
up
the
stuff
to
be
a
broadcast
out
on
the
official
mode
channel
and
then,
after
a
round
of
editing
and
feedback
I,
it
gets
they
get
pulled
in
and
actually
published
under
the
node
name.
With
attribution
to
the
author
and.
C
B
Sorry,
additionally,
we
have
at
the
outreach
initiative
which
I'm
switching
between
Windows
and
Mac
recently
and
I
cannot
get
any
more
shirt.
That's
right,
so
the
outreach
initiative
is
largely
focused
on
helping
kind
of
introduce
consistent,
workflows
around
different
avenues
of
community
engagement,
specifically
like
events,
content
and
contributions.
You
know
various
ways
to
basically
enable
more
folks
to
contribute.
B
So
you
know
we
have
a
fine
set
of
goals
around
this,
so
you
know
one
for
each
of
the
set
of
goals
for
each
of
those
specifically
and
then
from
there.
You
know
we'd
love
to
have
more
folks
involved
in
this,
but
you
know
that
would
basically
mean
getting
involved
in
helping
build
out
these
systems
for
outreach,
so
not
necessarily
well
possibly
doing
the
outreach
itself,
but
helping
build
out
the
systems
and
then
executing
on
those
systems.
So
yeah
we
and.
C
C
Was
there
to
help
help
broadcast
the
efforts
of
local
local
organizers,
who
are
looking
to
make
meetups
happened,
level
node
users
and
give
them
resources,
so
they
can
succeed
whether
that's
actually
helping
the
broadcast
the
existence
of
their
their
Meetup
and
document
that
or
give
them
resources
for
how
to
host
the
meetup
or
axon
or
mini
mini
local
conference,
where
everyone
to
call
it.
And
how
does
a
book
back
crack's
deserve
to
organize
that
and.
D
B
Yep
exactly
and
they've
recently
kind
of
expanded
it
a
bit
and,
in
addition
to
the
events
they've
disgusting,
how
they
can
do
the
same
kind
of
work
for
for
content
and
for
contributions
as
well
yeah-
and
you
know
very
much
too
what
my
Noah's
saying
these
you
know
these
are
folks
who
reached
out
to
comic-con
member
and
asked
how
can
I
get
involved
and
they
are
now
involved
both
directly
and
initiatives,
and
one
of
them
is
a
community
community
member,
a
mod
so
yeah.
This
is.
B
You
know
this
initiative
specifically,
is
a
very
good
illustration
of
how,
if
you're
interested,
if
you
want
to
help,
could
we
do
the
community
committee
in
kind
of
the
loose
community
efforts
around
nodejs
or
you
have
an
idea
or
something
that
you'd
like
to
do
to
help.
You
know
the
node.js
community
or
ecosystem,
and
it
doesn't
necessarily
have
to
be
to
help
it
grow,
but
just
to
help
it.
C
I
emphasize
that
point
open-source
is
made
and
running
created
by
those
who
show
up,
and
so,
if
you,
if
you
want
to
get
involved,
if
you
think
this
is
exciting,
if
you
think
contributing
to
know
to
be
amazing,
it's
then
coming
to
one
of
the
meetings.
They're
all
open.
These
are
doing
jobs
like
this.
You
just
go
download
the
client.
It's
free
and
you
can
use
them
come
and
get
engaged
and
honestly
system
started
at
the
hardest.
Part
is
the
calling
to
your
first
meeting,
but
I
have
not
met
somebody
in
the
community.
D
B
Would
respond
by
saying
you're
more
than
welcome
to
join
that's
you're
more
like
well,
regardless
of
whether
or
not
you
have
something
you
contribute
your
more
than
welcome
to
come
and
sit
in
on
the
meetings
you
can
talk
or
not.
It's
fine
either
one.
We
would
love
to
have
you
one
come
or
one
request
that
I
will
make.
We
do
have
a
weekly
issue
or
sorry
every
bi-weekly
issue
that
goes
up.
That
gives
kind
of
all
the
details
about
the
meeting
I'm,
just
commenting
in
that
and
saying
you're
joining,
because
we
have
two
links.
B
You
have
the
livestream
link
and
the
zoom
link
that
people
sometimes
get
confused
which
one
they
like
if
they
want
to
watch
which
one
they
should
be
using.
So
just
commenting
in
that
issue
so
I
know
to
kind
of
add
you
to
the
meeting.
I
got
a
call
that
adding
you
to
this.
Knowing
that
I
can
add
you
to
the
meeting
that
you're
interested
in
participating.
That
would
be
super
helpful
and
just
commenting
that
once
I
will
know
from
then
on
to
add
you
or
whoever
is
running.
The
meeting
will
know
from
then
on.
B
To
add
you
so
yeah
just
you
know,
feel
free
to
join,
listen,
give
feedback,
you
don't
even
have
you
don't
have
to
talk
in
the
meeting,
but
you
know
we'd
love
your
feedback
on
the
meetings,
whether
it's
during
or
after
or
you
know,
offline
or
whatever
and
yeah
come
participate,
and
let
us
know
how
we
can
help
you
kind
of,
engage
and
contribute
it.
If.
C
You
think
you
don't
have
anything
to
contribute
I'm
a
homily
propose
that
you
are.
You
are
wrong.
C
C
D
We'll
go
check
before
we
do
website
redesign
yeah
tyranny
mentioned
bi-weekly
issues.
That
issue
is
an
issue
that's
created
in
the
committee
community
committee
repository
in
the
node.js
organization.
That's
an
issue
that
we
use
as
an
anchor
for
meetings,
so
that
will
usually
be
your
source
of
truth
for
anything
that
you'd
like
to
refer
to.
When
trying
to
find
a
meeting,
it
will
have
the
zoom
link.
It'll
have
the
YouTube
livestream
it'll
have
details
about.
C
C
You
can
find
the
links
to
the
meeting
calendar
believe
it's
in
the
calm,
calm,
reading
right
in
the
root
and
these
meeting
issues
get
generated
on
the
Monday
before
the
meeting
doesn't
my
believes
and
it
automatically
pulls
in
content,
tags
of
github
labels
or
generating
that
meeting
agenda
so
wonderfully
automated,
because
you
know
we're
all
engineers
at
the
end
of
the
day.
Most
of
us
are
engineers
at
the
end
of
the
day,
and
if
we
can
automate
a
problem,
we'll
find
a
way
to
do
it.
So
quite
the
Buddhism.
C
Each
side,
let's
do
I,
can
I
can
dive
in
on
that
so
website.
We
redesign
is
near
near
to
my
heart.
It
is
exactly
what
it
sounds
like.
We
are
redesigning
the
website
and
it's
actually
how
I
got
involved
in
the
community
kidding
committee
over
a
year
and
a
half
ago
now
Wow
time
flies
the
yeah.
So
it's
another
great
example
of
a
way
you
can
just
show
up
and
make
me
impact.
You
want.
C
I
was
at
a
one
of
the
node
known
posted
a
has
interactive
meetings
a
long
time
ago,
I
thought
wow.
This
documentation
will
rough,
let's
fix
that
sort
of
come
in
meetings
and
go
figure
started.
Helping
them
actually
be
a
champion
for
the
website
redesign
initiative.
So
again,
open
source
was
made
by
those
who
show
up
so
come
and
join,
but
the
what
thirty
design
is
exactly
what
sounds
like
we
are.
C
We
are
rebuilding
website
from
the
ground
up,
making
it
more
approachable
for
both
new
engineers
and
useful
experience,
their
folks
who
are
heavily
experienced
in
in
node
and
to
meet
all
those
use
cases.
So
we
have
an
awesome
design
that
we're
working
off
of
Thank
You
Oscar
Gonzales
shout
out
and
we
are
actively
rebuilding
it
in
that
website.
We
design
repo
caveat
on
the
repo
names
website,
readers
that
we
split
between
two
one
was
where
we
were
building
the
site.
One
was,
we
were
doing
admin
stuff.
C
C
Are
building
out
in
Gatsby,
so
giant
static
site?
It
is
all
getting
all
the
documentation.
Content
is
getting
pulled
from
markdown
files
that
are
actually
committed.
Most
of
them
are
committed
to
the
core
proper
and
get
built
out
using
remark
for
more
like
learn,
page
documentation.
Those
are
committed
wreckers,
a
repo
at
the
moment,
yeah.
So
I,
it's
a
it's
an
awesome
place
to
contribute.
If
you
love
node
are
more
of
a
you
know,
front-end
engineer,
not
a
lot
of
experience
and
server-side
dress
code,
but
still
want
a
way
to
dive
into
the
community.
C
D
C
Yes,
it
is
we're
just
kind
of
think
architect,
ways
to
get
translated,
content
quickly
and
easily
into
the
Gatsby
project
and
to
point
out
in
the
way
that
is
sensible
and
reasonable.
So
things
are
changing.
The
internationalization
pipeline
will
have
to
change
a
little
bit
from
how
it's
been
I've
been
up
five
years.
However
long
it's
been
I,
and
we
are
just
react
to
that.
Bringing
that
solution
right
now,
so
another
awful
place
to
jump
in
and
help
contribute.
B
That
one
working
groups
are
a
concept
in
the
TSC:
they
exist
solely
in
the
TSC.
In
calm
calm.
We
only
have
initiatives.
This
was
done
intentionally
because
working
groups
working
groups
have
their
own
governance
and
they
can
be
their
self
govern
so
basically
to
spin-up
or
spin-down
working
groups.
They
have
to
self
D
tarter,
so
they
have
to
basically
implode
themselves
and
into
non-existence
which
for
calm
calm,
we
initially
thought
that,
would
you
know
just
copy
pasting,
that's
what
makes
sense
for
the
work
that
we
do.
B
Having
that,
like
long
term,
longevity
of
specific
initiatives
governed
by
the
initiatives
themselves
didn't
really
make
sense.
So
we
we
went
down
the
path
I'm
just
having
initiative,
so
in
initiatives
are
still
a
part
of
be
calm,
calm.
The
calm,
calm
is
kind
of
the
overseeing
body
and
its
goal
is
to
kind
of
never
never
need
to,
or
you
know,
directly
engage
with
the
initiatives.
However,
it
will,
you
know,
do
whatever
it
needs
to
when
the
initiatives
asks,
or
you
know,
to
enable
the
success
that
the
initiatives
we
are
basically
in
an
administrative
body.
B
C
C
Unless
you
are
a
governance
nerd
and
you
are,
you
know,
you
want
to
go
like
get
into
the
nitty-gritty
of
how
open-source
governance
works
and
and
how
a
service
body
can
can
help
unblock
contributors
I.
Then
you
don't
want
to
be
on
the
community
committee.
You
want
to
be
diving
into
one
of
these
individual
initiative
I,
because
that's
where
the
actual
work
on
on
content
happen.
A
D
Jeff,
just
to
use
an
a
recent
example,
a
recent
example
of
a
contributor
or
a
person
who
was
for
the
most
part,
an
observer
I
believe
in
several
come
come
meetings
or
several
months
of
Conca
meetings.
But
it
was
quite
interested
in
a
certain
aspect
of
the
work.
They
eventually
proposed
something
via
an
issue
which
they
opened
I
believe
in
the
kumkum
repository
and
that
has
taken
more
and
more
of
a
life
and
eventually
I
believe,
could
spin
off
into
an
initiative
of
its
own,
although
I
don't
believe
it
has
yet.
D
But
that
is
an
example
of
a
person
who
started
off
being
an
observer,
not
a
member
of
the
calm,
calm,
an
observer
who
attended
meetings,
asked
some
questions
to
clarify
certain
things
and
eventually
open
an
issue
which
they
then
brought
back
to
the
kumkum.
And
this
time
said:
hey
I
have
opened
this
issue.
Can
we
discuss
this,
and
that
was
only
the
first
of
several
times
that
they
then
proposed
discussing
the
subject,
a
comma
Club
meeting
so
as
an
observer,
they
were
able
to
open
an
issue.
D
B
Yeah
so
I
mean
basically
the
kind
of
way
to
get
involved
with
calm
coming,
you
know,
creating
an
initiative
you
know
at
that
level
would
be
to
go
ahead
and
create
an
issue.
That's
step,
one
in
that
issue,
right
out
kind
of
a
detailed
explanation
of
what
you're
proposing
what
you'd
like
to
see
the
kind
of
things
outcomes
you'd
like
to
see
are,
and
then
you
know
how
you
propose.
B
We
could
achieve
that,
and
you
know
what
you'd
like
to
see
in
both
contributors
to
it
and
the
results
that
the
community
or
kaam,
kaam
or
XYZ
target
audience
that
you're
interested
in
helping
would
get
out
of
it.
So
that's
that's.
The
main
thing
is
just
documenting
that
well,
and
you
know
documenting
that.
Well
can
be
a
paragraph.
It
could
be.
You
know
ten
pages
it
the
length,
isn't
necessarily
quality.
B
C
C
C
D
Think
we
mentioned
before
the
initiatives
are
pretty
much
self-governing.
Kumkum
doesn't
get
involved,
except
only
to
unblock
and
by
that
it
means
that
the
initiative
was
somehow
the
participants
and
the
champion.
In
this
that
initiative.
They
were
somehow
unable
to
come
to
consensus
around
something.
So
they
then
elevated
that
particular
disagreement
or
point
of
discussion
up
to
the
calm,
calm
at
which
point
of
calm
calm,
probably
provide
us
some
sort
of
guidance
to
also
help
come
to
consensus,
which
is
basically
how
we
resolve
most
disagreements
or
discussions
at
all.
D
One
of
way
that
I
see
the
calm,
calm,
probably
help
out
or
get
involved,
would
be
if
something
were
proposed,
but
the
people
who
were
getting
involved
in
necessarily
have
the
context
to
move
that
forward.
Then
people
on
the
kumkum,
who
tend
to
have
more
than
like
more
experience
being
involved
in
the
node
project,
then
a
new
participant.
They
would
then
add
some
context
or
say
like
at
historical
context
or
an
initiative
saying
hey.
D
Maybe
this
had
been
tried
out
in
a
different
forum
sometime
before
or
hey
other
people
you
might
want
to
reach
out
to
because
they
would
be
interested,
but
don't
have
the
time
to
necessarily
like
kick
this
off.
You
should
reach
out
to
those
folks
that
might
be
one
way
where
the
calm
calm
could
add
value
or
they.
C
Exactly
how
the
website
redesign
initiative
got
kicked
off
as
I
started,
engaging
it
had
been
started
and
shut
down
a
couple
times.
You
know
in
spurts
before
I
before
and
I
at
the
at
the
node
nodejs
interactive,
and
that
was
a
few
members
chatted
with
him
on
the
side
thing.
One
Twitter
found
the
black
whatever
and
you
know,
opened
up
a
proposal
to
get
it
started
again
in
in
calm,
calm
in
existing
calm,
calm
member
at
the
time
was
like
that's
a
good
idea
and
I
got
spun
up
again.
C
So
it's
a
you
know
there
there
may
be
prior
art
to
base
what
you're
doing
off
of
there
could
be
an
entirely
new
and
novel
idea,
but
that
all
comes
from
just
communicating
it
openly
on
github
everything
that
we
do
nearly
everything
that
we
do.
We
try
and
do
in
the
open
so
that
anybody
can
dive
in
and
contribute
so.
Github
issues
are
the
lifeblood
of
organizing
in
the
project
here,
where
all
the
members
lived
for
the
part
and
I
yeah
dive
in.
A
Awesome
super
helpful,
so,
on
the
comm
come
read
me,
there
are
multiple
like
levels
of
participation.
Can
you
give
an
overview
of
each
sort
of
level
of
park
patience?
Oh
you
talked
about
observers
and
members
and
all
that
stuff
and
then,
potentially
you
know
rough
estimate
of
like
time,
commitment
just
so
that
you
know
for
folks
who
may
want
to
dive
in
can
kind
of
have
some
context
around
what
it
would
look
like
for
their
day-to-day
yeah.
B
So
just
coming
in
and
joining
the
meetings,
that's
you
know
an
hour
a
week,
well
not
an
hour.
Well,
we
have
a
new
thing
this
week
that
we're
starting-
but
you
know
an
hour
for
the
other
week-
is
the
time
commitment
for
coming
and
joining
the
meetings
and
like
listening
in
and
participating
in
that
way.
So
that's,
hopefully
a
low
low
barrier.
Those
meetings
happen
every
Thursday
at
noon,
Eastern,
9
a.m.
Pacific
and
then
there's
a
timetable
in
that
that
issue
they
were
talking
about
earlier.
B
That
kind
of
it
has
a
more
said,
diverse,
set
of
time
zones
other
than
the
ones
I've
memorized,
but
you
know
coming
and
joining.
That
is
the
kind
of
lowest
barrier
commitment
in
terms
of
time.
Additionally,
you
know
ramping
up
from
that.
You
know
you're
starting
to
scale
out
into
a
synchronous
communication
where
you
know
you're
participating
in
issues
and
things
like
that
participate,
participating
in
initiatives
which
is
you
know
how
much
time
you
want.
That
can
be
five
minutes
or
that
can
be.
B
B
Involved
in
a
lot
of
things,
so
we
were,
you
know
for
an
example
when
we
were
doing
the
open,
jeaious
foundation,
merger.
That
was
a
lot
of
time
that
a
lot
of
people
spent
on
that
that
was,
you
know
on
like
the
averaging.
The
highs
and
low
is
probably
about
five
to
ten
hours
a
week.
I
guess
over.
You
know
eight
to
ten
weeks,
so
it
was
a
non-trivial
amount
of
time.
Some
people
spent
30
or
40.
Some
people
spent
one
or
two,
but
it's
still,
you
know
a
non-trivial
commitment.
B
When
things
come
up,
we
do
often
have
you
know
it's.
It's
not
consistent.
It's
a
fluctuation
there's
times
when
we're
doing
like
governance
work
that
has
to
be
done
and
that
in
you
know,
ends
up
being
a
little
bit
more
of
a
time
sink.
There's
other
times
where
we
have.
You
know
a
little
bit
of
a
you
know,
relaxed
timeframe,
I
guess
you
could
say
and
yeah
that's.
Maybe
you
know
for
an
average
member
2-3
hours
a
week.
So
it's
really.
B
It
really
is
a
scale
and
it
still
is
kind
of
how
much
you
can
and
want
to
put
into
it,
but
there
is
kind
of
a
minimum
level
of
commitment
to
becoming
a
member
and
becoming
a
member
that
is
probably
like
I'd,
say,
maybe
on
average,
for
five
hours
a
week
and
largely
I.
That
does
is
a
little
bit
high
I
mean
that's.
You
know
like
an
eighth
of
a
workweek,
so
you
know
it's
worth
putting
it
a
little
bit
higher,
because
there
are
times
when
it
gets
a
little
bit
more
intense.
C
And
there's
there's
three
distinct
words
that
are
often
turnarounds
out
subscribe,
a
lot
of
these
levels
of
participation,
some
with
actual
implications,
unlike
being
able
to
commit
directly
to
the
project.
You
know
some
ones
that
are
my
little
well
as
fuzzy
three
levels.
The
three
words
often
turn
around
to
describe
those
levels
are
observers,
contributors
and
collaborators.
C
So
observers
are
what
it
sounds
like.
Like
you
come
show
up
you
you
hang
out
in
the
meeting
you
you
get
to
feel
for
it,
but
it's
you
know
you
haven't
necessarily
committed
any
code
or
any
documentation
or
or
I
have
have
created
something
and
contributed
it
to
the
to
the
project.
Proper
you're
there,
mostly
as
just
a
thought
on
a
contributor,
is,
is
literally
anybody
who
contributes.
C
So
if
you
have
any
bit
of
code
that
has
landed
in
the
repository,
if
you
have
any
occupation
that
you
haven't
even
of
anything,
your
congrats
or
your
contributor
and
I
and
collaborator
is
somebody
who
has
been
around
for
a
while.
I've
actually
started
getting
known
in
the
in
the
community
in
the
organization,
and
you
are,
you
are
added
as
a
member
to
one
of
these
one
of
these
repos,
so
there's
an
initiative
or
column
itself
I.
Those
are
you
know.
C
Three
words
often
turn
around
and
Jimmy
reminded
me
kindly
in
the
chat
that
observer
technically
doesn't
exist
anymore,
but
we
still
often
use
the
word.
So
it's
good
to
have
you
know
vestigial
word
from
from
old
old
governance,
but
you
know
they
have.
A
classification
still
has
still
has
meaning
in
a
lot
of
members
Minds
that
we
use
good
nom
terminology.
D
D
Those
are
requirements
that
are
meant
to
help
the
project
shepherd
along
its
initiatives,
because
another
thing
is
know:
Jess
is
it's
a
product,
but
it's
not
a
product,
that's
a
business,
so
you
can't
have
leadership
dictating
goals.
Then
everyone
like
jumps
to
it
and
makes
it
happen.
It's
the
community,
create
those
goals
forceps
for
itself
and
tries
to
live
up
to
it,
based
on
the
amount
of
time
that
the
community
members
can
put
towards
those
goals
and
because
that
bandwidth
is
subject
is,
is
subject,
subject
to
so
many
other
factors.
D
C
Thinking
personally,
you
know,
early
on
I
was
I
was
personally
able
to
dedicate
a
long
time.
I
helped
run
an
organize
a
lot
of
stuff
on
the
community
committee.
More
recently,
literally
the
past
two
months,
I
had
a
lot
of
other
product
work
going
on,
so
I
had
to
step
back
and
yet
I
feel
like
there's
because
of
this
governance,
and
because
of
accommodation
for
not
only
the
natural
Ivan
flow,
the
project
itself,
but
they
haven't
slowed
of
individual
contributors,
I
I.
C
It
is
accommodated
for
in
how
the
entire
project
operates,
and
so,
as
a
contributor
I
you
are,
you
are
able
to
kind
of
choose
your
own
adventure
for
how
you,
how
you
contribute
and
the
the
project
will
will
accommodate
the
to
make
it
happen.
A
Awesome
so
we
are,
we've
got
about
seven
more
minutes
left
I.
Think
the
of
time
to
get
through
these.
These
last
few
questions.
So
the
next
question
is:
why
would
I
participate
and
contribute
to.
B
B
Just
like,
as
a
personal
thing,
I
started
contributing
to
note
in
when
I
ojs
forked
out,
as
because
of
a
blog
post
that
Michael
Rogers
wrote
where
he
said
you
know
non
non
technical
contributions.
Welcome
and
that
made
me
come
and
contribute,
which
is.
You
know
why
I
got
a
job
in
this
and
a
bunch
of
other
things,
long
story.
B
Additionally,
I,
you
know,
III
think
that
there
are
certain
people
who
are
interested
in
community
and
we're
interested
in
events
or
who
are
interested
in
you
know.
Different
aspects
of
technology
that
aren't
a
slightly
just
community
and
the
community
is
in
node
is
a
codification
of
the
project's
value,
valuing
that
kind
of
work,
and
so
it's
a
good
place
for
people
who
are
like
that
to
come
and
participate
in
the
project
at
a
higher
level.
In
that
way,.
C
Very
very
much
depends
on
your
personal
priorities
like
I.
There
are
there.
I
do
fit
that
to
two
prong
split
like
either
you
a
lot
of
people
who
are
in
it
because
they
love
they
love.
No,
they
use
a
day-to-day
it's
there.
You
know
it's
both
professionally
and
in
their
passion
project,
their.
You
know
the
foundation
that
the
gold
on
and
they
want
to
give
back
in
some
way.
C
Those
are
a
lot
of
people
who
have
just
in
love
and
and
dedicated
with,
creating
these
these
open,
inclusive
and
in
productive
spaces,
and
see
see
node
in
this
project
and
the
infrastructure
that
we've
built
and
codified
around
how
to
how
to
make
that
happen
and
how
to
iterate
on
how
to
make
that
happen.
It
see
that
as
a
great
platform
to
scratch
that
itch
as
it
were,
to
help
build
those
types
of
opportunities,
I
yeah.
So
if
either
those
resonates
with
you,
then
then
you're,
probably
a
good
fit
for
for
diving
in
somewhere.
A
And
really
like
that,
that's
awesome.
So
in
the
final
few
minutes
here
you
know
this,
is
you
know
what
what
are
the?
What
are
the
areas
where
the
calm
calm
could
use
more
involvement?
And
you
know
what
are
the
avenues
for
folks
to
get
involved
which
I
know?
We've
talked
about
a
lot,
but
you
know
one
more
for
involvement.
It's
always
a
good
thing.
So.
B
So
one
thing
on
the
involvement:
if
you
are
interested
in
getting
involved,
but
still
like
you
know,
you
provided
a
bunch
of
avenues
to
do
it,
but
still
aren't
sure.
If
you
please
feel
free
to
reach
out
to
us,
any
of
us
I
think
would
be
willing
to
talk.
But
you
know:
I
have
opened
EMS
on
the
open,
J's
foundation.
B
Slack
Twitter,
you
can
reach
out
to
me
publicly
or
I,
have
opened
EMS
again
feel
free
to
reach
out
to
us
in
any
way
that
you
are
comfortable
and
we'd
be
more
than
happy
at
least
I
I
would
be
and
I
don't
want
to
speak
criminal
Adam,
but
I
have
a
strong
feeling
that
they'd
be
okay,
that
you,
you
know
we're
happy
to
help
you
get
involved.
However,
you're
interested
and
it's
you
know,
I'm
having
to
spend
time
helping
you
get
involved
in
the
ways
that
you're
able
and
interested.
D
C
D
A
good
way
to
reach
out
my
name's
are
typically
open.
They're
closed
for
unrelated
reasons
right
now,
but
they're
typically
open
and
I'm
definitely
willing
to
help
guide
people
in
the
right
direction.
Also,
the
nodejs
the
twitter
handle
itself
tends
to
tweet
out
opportunities
for
people
to
jump
in.
So
that's
very
helpful
because
it
watches
a
lot
of
contributors
or
community
members
who
are
and
amplifies
their
voice
about
saying,
hey,
hey,
come
join
us
we're
doing
some
work
here.
Yeah.
C
I
will
add
a
third
I
guess
my
DMS
are
open
on
Twitter
come
after
to
me,
I
will
caveat
that
with
I
am
occasionally
bad
at
responding.
Please
please
DoubleTap
with
the
with
the
messages.
It
is
nothing
personal
I
want
Dock.
You
send
me
a
reminder
if
I
don't
get
back
right
away,
and
that
goes
for
all
of
us.
You
know,
but
yeah.
We
will
be
happy
to
help.
C
You
know
triage
you
to
where,
where
your
interests
are
best
suited,
either
in
calm,
calm
or
elsewhere
in
the
project
and
also
just
come
show
up,
you
know
we
can
sit
off
a
bunch
of
working
groups.
They
are
listed
in
the
main
reading
of
the
calm,
calm
Rizzo.
We
leaked
out
directly
to
the
repositories
where
those
sorry
not
working
initiative,
loose
terminology
where
those
initiatives
are
actually
doing
their
active,
active
work
in
that
readme
I
and
if
you're
still
unsure
about
where
to
start
open
up
an
issue
say
you're
excited
to
contribute
and
we
can.
C
We
can
help
you
get
get
going
there
and
we'll
be
happy
now,
although
you
know,
try
and
find
the
you
know,
do
some
do
some
due
diligence
find
the
repo
that
you
think
you're
going
to
be
interested
engaging
with
read
through
the
existing
issues
drink
from
the
higher
for
the
the
drink
from
the
fire
hose
for
a
seconds
of
contents
on
get
up
come
fast,
but
there's
a
lot
of
valuable
I.
Existing
craziest
thing
work
and
again
it's
done
by
the
people
to
show
up
so
come
and
make
yourself
known
and
come
join
up.
A
A
Thank
you
all
so
much
for
for
your
your
time
and
your
expertise
in
this
area
and
thanks
everyone
who
tuned
in
we'll
get
this
posted
on
the
open,
J's,
Foundation,
blog
and
we'll
get
it
tweet
it
out.
So
for
folks
who
maybe
didn't
have
a
chance
to
catch.
This
live
you'll
have
a
chance
to
rewatch
it
and
yep.
So
everyone
have
a
awesome
day
and
thanks
so
much
for
joining
us
I'm
going
to
stop
the
livestream.