►
Description
Agenda is at https://github.com/nodejs/community-committee/issues/87
A
All
right
heroin
Oh
welcome
to
the
July
6th
meeting
of
the
nodejs
foundation
community
committee.
We
have
quite
a
few
people
in
a
sense
say,
which
is
awesome.
My
name
is
Brian
Hughes
I'm
neveress
on
get
up
and
I'm
the
community
committee,
a
chair
person
and
let's
go
and
go
around
and
have
I
want
to
choose
themselves
and,
let's
start
with
Gregor.
F
G
A
H
A
J
A
A
Yes,
so
we're
looking
at
adding
a
Jin
Tierney,
Michael
Dawson
Olivia
in
Richard,
who
we
all
have
here
at
this
meeting.
So
adding
members
is,
you
know
an
actual
official
thing
called
out
in
the
Charter,
and
this
is
something
that
we
need
to
fill
up.
This
is
not
passed
by
a
consensus.
Now
we
don't
have
to
vote
all
at
once
in
a
single
sitting.
We
don't
have
to
reach
quorum
inside
of
this
meeting.
That's
a
specific
technical
thing.
We
do
need
to
vote
on
it
and
see.
A
I
A
So
all
right
so
I
actually
need
to
cross-reference
this
with
the
list
of
missing
members,
because
remember
specifically
to
vote
on.
Of
course.
We
you
know,
we
love
everyone's
a
yes,
so
obviously
we
want
to
round
away
n,
but
as
far
as
the
actual
counting
votes
is
concerned,
we
need
to
make
sure
that
everyone
is
a
member
and
so
we're
gonna
have
to
reach
1
2
3
4,
5,
6,
7,
8,
yes
votes,
and
so
we
are
short
of
that
right
now
the
vote
wrangling
process
takes
a
while.
A
A
I
I
was
gonna,
say,
I
think
we've
got
a
number
of
the
people
we're
trying
to
vote
in
attending
today,
which
is
awesome,
but
the
big
members.
We
also
this
reminds
me
not
to
tangent,
but
that
I
think
we
have
one
or
two
people
on
the
list
of
members.
That
was
from
that
when
this
was
kicked
off
in
charter
as
support
who
have
not
attended
any
of
the
meetings,
so
I
think
we
also
need
to
look
at
finally
tripping
because
I
think
we're
at
the
three
month
mark
well.
A
C
A
A
B
C
A
I
A
A
G
I
also
add
an
action
item
of
thanking
those
who
want
to
step
down
for
their
service
and
being
in
the
committee.
I
know
that
it's
a
natural
part
but
having
a
formal
recognition
of
time
and
having
spent
on
the
committee,
is
really
nice
just
to
like
bookends
people
deciding
that
they
don't
want
to
be
on
anymore
and
just
that's
also
going
forward.
A
Yeah
we
kind
of
did
something
like
that
for
the
inclusivity
working
group
now
I
think
about
it.
We
had
you
know
the
lists
of
members
in
the
readme
and
I.
Don't
remember
where
it
was
then
one
of
the
documents
we
actually
had
a
list
of
when
everyone
was
added
as
a
member,
you
know,
even
if
there
was
no
longer
where
so,
there
was
a
bit
of
a
recognition
there.
Like
past
members,
I
know
it
was
everyone
think
about
that
as
that's
something
you
might
be
interested
in.
Having.
A
All
right,
I'm
gonna
go
a
little
bit
out
of
order,
if
that's
all
right
with
everyone
and
we're
going
to
talk
about
us,
so
no
jst
SCO
request
number
276.
The
reason
for
doing
this
is
number
278.
Our
other
agenda
item
is
very
open-ended
and
you
know
I
could
definitely
see
it
taking
up.
You
know
the
rest
of
the
available
time
and
I
want
as
much
time
as
we
can,
but
I
just
wanna
make
sure
we
get
to
276
as
well
as
that,
okay,
whatever
all
right
so
number
276.
A
A
All
right
I'll
go
and
give
just
a
quick
overview
of
what
is
in
this
PR,
so
this
PR
affects
both
the
TSE
and
us.
It
makes
a
number
of
changes.
So
currently
the
way
moderation
is
done
in
the
node.js
community
is
we
have
a
repository
called
the
moderation
and
posits
worry,
I
believe
everyone
here
should
have
access
to.
It
is
if
you
have
access
to
any
part
of
the
org
you'll,
have
access
to
this
repo
and
I
do
miss
repo
I'm.
A
A
I,
thank
you
Michael
yeah
yeah,
so
we
have
this
private
moderation
Aleppo,
and
the
idea
with
this
is
we're
trying
to
empower
all
the
collaborators
to
participate
in
moderation.
So
if
anyone
sees
something
going
on,
you
know
a
thread
that
either
is
going
off
the
rails
or
is
at
risk
of
going
off.
The
rails
will
open
an
issue
in
this
private
repository
in
basis
I.
You
know
we
should
check
out
either
this
issue.
This
poor
request
this
user
and
we'll
use
that
to
have
internal
discussions
about
how
we
want
to
handle.
E
A
And
it's
proven
really
effective.
Actually,
we
kind
of
stumbled
on
it
a
bit
accidental
a.m.
it's
a
whole
bunch
of
history
there,
but
it
worked
very,
very
well
at
de-escalating
situations.
You
know,
because
this
isn't
public
there's
a
lot
of
less
like
a
shaming
aspect
to
it
allows
us
to
really
just
kind
of
talk
about
like
how
we
can
you
know,
lower
tensions
and
things
like
that.
However,
it
does
have
some
limitations.
Still
the
biggest
limitation
we
have
is.
A
There
is
no
escalation
policy,
so,
for
example,
if
two
collaborators
disagree
on
something
or
especially
upset
each
other,
we
can't
come
to
a
resolution.
We
currently
don't
have
a
way
of
working
through
that.
So
this
pull
request
addresses
that
issue
and
then
primarily
or
that's
one
of
the
big,
the
big
impetus
for
opening
this
is.
It
now
has
an
escalation
policy
and
we're
still
working
on
the
details
now.
A
Another
thing
that
this
pull
request
does-
and
this
is
where
it
really
affects
us-
is
that
it
changes
ownership
of
moderation
from
being
the
TSC
only
to
having
joint
ownership
between
kaam
kaam
and
the
TSE.
So
that
means
that
you
know
this.
Will
become
part
of
our
responsibility,
so
this
is
something
that
we
need
sign-off
from
kaam
kaam
as
well
on.
So
I
definitely
strongly
urge
everyone
to
go.
Take
a
look
at
it
read
through
all
of
the
details
on
and
give
your
feedback.
A
You
know
anything
that
you
think
is
lacking,
something
that
need
to
be
clarified
or
something
that
you
don't
think
will
work
well.
You
know
we
definitely
want
to
get
all
of
that
input
together
and,
if
anyone's
not
comfortable
posting
directly
to
that
PR,
you
can
also
talk
to
me
or
some
of
the
others,
and
we
can
post
in
your
bath
but
I.
Do
you
think
this
is
really
really
important
and
I
really
want
to
make
sure
that
we
get
this
right.
H
A
You
know
that's
actually
a
really
good
question.
I
think
that's
part
of
this.
That
is
so
pretty
baby.
Honest,
we're
not
exactly
sure
like
it
would.
What
I
would
guess
that
it
would
be
a
team,
not
a
working
group,
I
think
and
I
will
somehow
be
jointly
owned
by
the
TFC
and
Kham
Kham,
not
exactly
sure
how
that
works
out.
If
there's
a
lot
of
mechanics
that
I
think
needs
to
be
fleshed
out.
Okay,
obviously
yeah.
A
So,
where
we
are
right
now,
I
want
everyone
just
to
take
a
look
at
it,
give
feedback,
that's
what
we
need
to
be
doing.
You
know.
That's
our
first
ever
need
stake
now,
once
we
need
to
have
a
consensus
going
then
I
think
this
may
require
a
vote
I'm.
Actually
not
certain
on
that
it'll
depend
on
it
if
it
touches
our
Charter
and
or
the
TSA
charter,
then
that
will
definitely
wear
a
vote
and
board
approval.
A
A
A
All
right
so
with
that
I
think
we'll
go
on
ahead
on
to
the
next
item
and,
like
I,
said
those
more
of
a
heads
up,
I'm,
just
sort
of
an
ass.
So
an
action
item
for
everyone
coming
out
of
this
is
to
go
review
that
PR
and
hopefully,
once
once
we're
a
lot
closer
than
we
can
have
a
more
formal
discussion.
Maybe
we
can
even
have
a
joint
meeting
with
the
TST
to
discuss
it
as
a
group.
A
All
right,
so
the
last
item
on
our
agenda
is
number
278.
Once
again,
this
is
an
issue
on
the
TSC
repo,
and
so
this
is
very
much
a
broad
meta
issue
and
that's
basically
the
finding
candidate
areas
for
the
TSC
and
community
committee
Michael.
Do
you
want
to
talk
about
this
one?
Since
you
know
you're,
gonna
get
sure
I.
E
Just
you
know,
I
think
it
would
be
nice
if
we
as
a
community.
Somehow
you
know
sort
of
tracked
all
the
things
that
were
important
to
the
success
and
you
know
then
at
least
did
whatever
was
appropriate
to
make
sure
we're
comfortable
that
the
right
things
are
happening
in
those
different
areas.
You
know
and
I
think
a
bunch
of
that's
happening.
You
know
already
it's
just
a
matter
of
sort
of
making
sure
that
you
know
as
the
TSC
or
kaam
kaam
committee,
who
are
sort
of
the
ones
directly
under
the
board.
E
We
make
sure
that
we've
got
coverage
across
the
board
and
you
know
things
just
don't
kind
of
slip
through
the
cracks.
So
I
put
this
issue
together,
as
kind
of
in
my
first
cut
at
like
here
the
different
areas
that
we
might
consider.
As
you
know,
key
things
that
we
should.
You
know
maybe
periodically
just
review
and
say:
hey,
for
example,
how's
our
testing
going
is
is:
do
we
think
that
you
know
pretty
everything
we
have
in
place
is
doing
the
job
or
there's
some
major
gaps
that
you
know.
E
So
I
guess
I'm
looking
at
you
know
for
feedback
on.
Are
there
things
that
are
missing
here
and
then
you
know
that
yeah.
We
think
it's
a
good
idea
and
ideas
how
we
would
actually
make
that
happen.
You
know
people
have
pointed
out,
it's
a
it's
an
open
source
community.
So
it's
not
like
a
regular
organization
where
we
can
assign
people
responsibility
or
anything
like
that.
We
got
to
look
for
volunteers
and
see
if
we
can
fill
the
gaps.
I
B
I
I
But
the
travel
was
generally
for
purposes
that,
like
empowered
members
of
the
TSC
right
so
through
collab
summit
or
attending
tc39
meetings,
things
like
that.
So
last
community
committee
meeting
we
had
approved
going
to
the
board
to
request
that
we
could
do
a
travel
fund
because
that's
something
the
board
has
to
approve,
as
well
as
providing
money
so
that
the
community
committee
could
also
have
a
travel
fund
and
what
the
board
came
back
with,
which
is
very
reasonable.
Is
that
they
would
prefer
for
us
to
take
these
tribe.
I
H
I
Have
that
in
the
travel
fund
issue
that
I
updated
but
I'm?
Actually
for
the
sorry,
we
have
a
community
committee,
travel
fund
issue
open
and
I
updated
it
with
that
information
in
much
shorter
form,
but
it
was
mostly
that
we
need.
We
can't
really
do
anything,
Travel
fun
wise
until
the
to
coordinate
and
that's
the
big
problem
for
me
is
that
we
need
to
get
these
travel
funds
ready
to
go
and
we
can't
get
that
money
approved
until
we
work
together.
C
I
Yeah
on
that
and
I
looks
like
that,
one
was
not
created
separately
and
I
didn't
want
to
muck
up
this
candidate
areas.
Issues
so
should
I
just
file
a
new
one
and
then,
in
that
case,
I
have
to
file
it
in
one
of
the
repo
like
I'll
likely
file
in
the
TSC
repo
and
then
need
to
call
it
back
to
the
community
committee
right.
C
I
B
A
There's
actually
discussion
about
this
going
on
in
the
moderation
PR,
specifically
now
that's
much
more
focused,
but
there's
a
discussion
going
on
yeah
vote
on
this
stuff,
especially
since,
like
updating
the
moderation
policy
role,
I
think
the
way
it's
written
right
now
would
require
a
vote.
There's
discussion
on
whether
or
not
a
vote
should
require
it,
but
there's
also
this
question
of
how
does
that
work?
So
there
was
the
idea
of
crates
were
like
a
super
committee.
We're
just
like
all
the
individuals
would
have
come
together
and
vote
as
a
single
group.
A
As
far
as
I
can
a
simple
majority
of
each
separately,
which
is
a
little
bit
different
like
the
numbers,
are
gonna,
be
a
little
different
on
how
that
plays
out.
So
those
are
all
things
to
just
kind
of
think
about
like
how
we're
got
to
work
with
that
now.
Another
thing
I
remember
is:
there
is
a
repo
we
could
resurrect.
It's
called
the
collaboration
repo,
it's
yeah
github.com,
slash,
nodejs,
slash
collaboration
drop
in
the
chat.
This
was.
A
For
a
similar
purpose,
but
a
little
at
a
lower
level
is
created
to
help
facilitate
between
working
groups.
It
ended
up
not
being
or
end
up
being
an
unnecessary
cuz.
I.
Think
those
discussions
end
up
just
happening
in
the
CTC.
Is
the
CTC
got
more
established,
so
a
very
old
idea,
but
it
might
be
worthwhile
to
resurrect
that,
but
instead
for
facility
collaboration
between
Kham,
Kham,
CSE,
I
thought.
A
A
Okay,
so,
based
on
this
discussion,
it
sounds
like
we
should
probably
open
an
issue
either
on
for
now,
either
in
calm,
calm
or
the
TSE
repo
about
creating
a
place
for
us
to
collaborate,
which
means
a
bit
see
like
to
get
this
question
solved
for
answer
first,
and
then
we
can
start
using
that
to
actually
Clowry.
We
can
even
use
the
travel
fund
as
sort
of
like
the
the
pilot
issue
of
whatever
we
decided,
but
I.
I
See
this
is
one
of
the
things
that
we're
struggling
with
right
is
that
the
travel
fund?
This
is
kind
of
an
All
Hands
at
this
point
like
in
terms
of
fires,
and
it's
not
a
fire
so
much
as
we
really
need
to
have
this
done
by
the
next
board
meet
like
a
week
before
the
board
meeting.
So
we
have
essentially
two
weeks
because
otherwise
it
is
another
entire
month
before
we
can
get
that
approved
and
that's
more
time
that
our
collaborators
are
unsure
whether
they
were
going
to
get
assistance
to
travel.
To
note
interactive
yeah.
I
E
H
Earlier
there
is
some
discussion
about
a
joint
meeting,
I
think
that
might
also
be
like.
We
could
try
to
plan
that
either
after
the
next
TSE
meeting,
which
would
be
a
week
from
today,
which
is
about
what
you're
suggesting
on
the
timeline
or
something
else
like
a
joint
meeting,
because
it
seems
that's
come
up
twice
now.
Yeah.
E
I
F
I
F
I
Exactly
so,
that's
yeah
now
that
I'm
talking
this
out,
we
need
to
PR
that
existing
travel
fund,
but
it
would
likely
need
to
be
pulled
out
under
the
TSE
repo
so
that
t-that
reap
that.
The
writing.
The
document
is
good.
It
just
needs
to
be
changed
from
the
scope
of
the
TSE
to
adding
calm,
calm
and
that's
with
the
TSE
and
then,
of
course,
we
probably
want
to
be
more
explicit
about
how
that
money
is
being
like
approval
of
funds
and
then
how
it
like
reimbursement
works.
I
I
A
Yeah,
so
just
to
be
clear,
on
kind
of
like
next
types
of
things
like
this,
that
the
fund
itself
is
good.
What
we
need
to
update
is
like
how
to
administer
it
and
who
is
in
charge
of
approvals,
at
least
to
make
it
a
little
more
explicit
that
you
know
this
covers
all
individual
members,
which
includes
people
here
in
teams
and
working
groups
under
calm,
calm
and
not
just
teams
and
working
groups
under
the
TSE.
Well
I
mean
maybe
so
it's
just
it's
more.
I
Yeah
I
think
that
it's
it's
fine
to
say
like
try
and
keep
it
relevant
to
the
parties
that
you're
most
participating
in
like
if
you're
in
both
committees,
then
like
yeah,
I,
probably
shouldn't
be
like
chiming
in
on
TSE
members
requesting
right.
Actually,
no
that
doesn't
matter
I'm.
Sorry
I
just
negate
it
myself,
because
it's
individual
members,
not
TSE
er
yeah,.
E
I
I
So
that's
nice,
because
then
it
ends
up
being
the
way
that
we
can
account
for
it,
so
that
that's
part
of
needing
the
joint
repo
so
that
we
just
have
that
in
one
place,
but
yeah
I
think
that's
great
like
unless
you
know
either
group
can
object,
but
otherwise
it's
you
know
trusting
that
people
are
doing
the
relevant
work
and
it
gets
approved.
Yeah.
E
I
I
E
That
would
make
sense
if
you
could
PR
cuz,
like
you'd,
already
been
looking
at
the
numbers
right.
So
if
you
have
the
numbers
to
say
you
know,
we
need
to
increase
the
fund
by
these
two
numbers,
because
you
know
one
is
well.
We
I
think
we
want
to
increase
it
for
the
TSE,
but
then
also
increase
it
for
the
comp
obsolete.
You
know
p.m.
for
those
two
numbers
and
then
I
guess
the
other
part
is
the
PR
to
the
change
for
the
the
governance
right
right.
E
I
You
know
providing
input
which
I
don't
again
well,
I,
don't
think
that'll
be
a
problem
cool
all
right.
I've
got
that
down
yeah
because
I
agree
Michael,
it's
much
more
important
for
us
to
get
that
travel
fund.
Coordination
between
our
two
groups
done.
First
I
think
trusting
that
we
can
open
a
new
repo
with
joint
scope,
soon,
all
right,
it's
great,
but
not
necessary
to
skidding
this
joint
travel
phone
through
yeah.
B
E
I
F
G
A
A
link
and
the
chat
this
goes
to
the
summit
repository
there's
a
the
issue,
a
link
to
specifically
for
this
club
summit.
So
there's
like
some
organizing
stuff
going
on
in
there,
but
it's
also
a
place
where
you
can
just
kind
of
indicate
that
you're,
interested
and
I
think
we
might
have
some
more
information
on
I
actually
know
the
thing.
We
don't
have
information
on
how
to
request
funds,
but
I'll
make
sure
that
that
yeah.
I
And
we
should
yeah.
Everyone
in
the
community
committee
should
be
watching
that
not
literally
watching
the
repo,
but
they
it's
great
to
give
input
for
the
summit.
It's
a
really
good
time
for
us
to
all
get
to
engage
and
if
you
plan
stuff
ahead
of
time
and
let
them
know
that
we're
gonna
be
talking
about
things,
people
get
really
excited.
We
had
really
good
engagement
at
the
may
collaborators
summit,
even
considering
how
small
it
was
so.
E
A
So
getting
this
back
a
little
bit
broader,
so
this
issue
is
candidate
areas.
I
start
out
going
back
to
that
issue,
you're
number
278!
So
there's
another
thing:
I
recommend
everyone
take
a
look
at.
We
don't.
You
know
we're
kind
of
running
out
of
time,
so
we
won't
discuss
it
here
in
detail
with.
The
idea
is
that
you
know
the
node.js
project
there's
a
whole
bunch
of
moving
pieces
and
parts
to
it.
A
The
idea
is
that
this
should
help
prevent
things
from
falling
through
the
cracks
which
an
open
source
is
easy,
it's
easier
to
happen
enough
to
sources
in
the
company,
because,
as
I've
mentioned
earlier,
you
know,
I
can't
hire
people
to
fill
roles
or
assign
people
of
projects,
and
this
this
Canada
areas
is
not
just
technical
and
Wake
Tech,
most
of
my
part
of
it.
But
you
know
evangelism
and
things
like
that,
and
you
know
our
activities
also
fall
into
it,
see.
A
Let's
just
give
it
a
thought,
if
there's
anything
that
you
think
Ethan
just
might
be
possible
with
Canada
area,
you
don't
definitely
drop
of
them,
and
you
know,
let's
think
of
this
as
like
brainstorming,
because
you
know
we
want
to
get
as
much
coverage
as
we
can
over
what
the
project
actually
is.
Can
you
can
you
define
what
a
Canada.
A
H
F
E
Like
in
the
perfect
world,
we'd
end
up
with
a
full
list
of
all
the
things
we
think
are
important
and
somebody
who's
kind
of
like
taking
ownership
of
making
sure
the
right
things
happen.
I,
don't
think
we'll
end
up
assigning.
You
know
it's,
you
can't
necessarily
assign
them
all
or
anything
like
that,
but
I
think
it's
good
to
have
the
list,
at
least
to
think
about
yeah
and
I.
E
Think
we
want
to
think
about
well,
which
one's
kind
of
fit
under
the
community
committee
as
those
are
ones
that
you
know
this
group
may
want
to
say.
Okay
now
you
know
here's
the
list
of
things
and
are
we
doing
all
the
right
things
that
we
want?
We
think
should
be
happening
on
on
in
that
list.
It's
kind
of
like
the
the
checklist
that
we
can
use
is
a
periodic.
I
A
And
another
thing
I'd
mention
in
the
last
TSE
meeting
on
this
topic
is:
this
is
also
information
that
could
be
useful
for
the
board.
So
now,
because
we
can
say,
like
you
know,
these
are
the
areas
that
we
currently
have
gaps
and-
and
you
know
the
board
can
then
take
a
look
and
decide.
Now.
Is
this
something?
That's
really
really
really
important?
We
need
to
get
done
and
since
we
can't
find
people
do
we
need
to
look
at
other
ways
of
making
sure
that
work
gets
done.
E
E
This
you
know
say
hey,
this
is
a
gap,
do
you
guys
have
any
where
they
can
help
or
we
can
like
evangelize
it
by
saying
hey,
you
know
we
really
could
use
somebody's
help
in
this
area,
like
I,
think
just
making
sure
that
it's
like
if
people
are
looking
to
help
out
some
way
and
there's
something.
We
think
the
mote
is
the
most
important
that
awareness
to
help
direct
the
effort
in
the
right
place.
E
Yeah,
no,
no,
absolutely.
This
is
just
sort
of
the
top
level
headlines.
You're
right
that
really
you
know
we
should
have
a
deeper
understanding
and
description
of
or
what
are
all
the
things
we
want
to
be
doing
them
to
these
things
like
some
are
obvious
like
and
maybe
even
you
know
not
totally
but
like
travel
funding.
The
you
know
we're
talking
about
the
that
one
fund
to
fund
travel
and
the
the
mandate
for
that.
E
You
know
if
that's
the
only
thing
that
it's
a
matter
of
documenting
that,
if
there's
something
else,
though,
then
maybe
you
know,
there's
even
deserve
some
thought
there.
Some
of
the
others
are
much
fuzzier
and
bigger,
though
so
I
agree,
they
needs
a
lot
more
refinement
before
you
actually
say
hey.
Can
you
come
help
with
this
right?
So.
A
And
I
would
say
if
you're
not
certain
if
it
fits
or
not
just
go
and
mention
it
anyways.
Okay,
now
I
have
a
discussion
on
whether
or
not
it's
but
I'd
rather
have
that
discussion
and
decide.
You
know
that
maybe
this
doesn't
fit
on
the
list,
then
to
not
have
the
discussion
and
it
actually
doesn't
need
to
be
on
the
list.
Yeah
I
think
we,
like
brainstorming,
yeah.
E
H
C
H
I,
just
I
asked
a
little
while
ago
and
again
there
had
been
no
kind
of
updates
because
they
were
having
the
person
having
to
do.
It
was
working
on
a
thing
for
work
and
they
had
to
push
that
over
and
it's
been
going
on
for
a
while
now
so
I
wanted
to
see
if
there's
kind
of
what
we
can
do
to
kind
of
get
a
website
new
website
thing
going
and,
of
course,
I
would
have
to
involve
the
website
working
group
and
whatever
the
entire
process.
But
I
know.
C
I
My
understanding
was
that
Michael
was
not
leading
the
charge
on
that,
but
was
unfortunately
yes,
the
person
who
held
a
lot
of
the
context,
because
I
think
that
the
people
from
the
website
working
group
and
anyone
from
that
group
who's
listening
where
it
gets.
These
notes
can
correct
me,
but
it
was
my
understanding
that
a
lot
of
the
people
who
were
spearheading
that
was
kind
of
like
dropped
away
a
little
bit
and
there's
not
the
same
amount
of
energy
moving
forward
and
I
was
actually
that's
one
of
the
things
that
I.
I
H
Also
talked
to
many
many
individual
people
who
haven't
really
gotten
involved
in
the
project,
but
they
saw
that
as
a
way
to
like
they
would
love
to
get
involved
with
that
and
like
that's.
How
I
myself
got
involved
with
nodejs
and
all
everything
I'm
doing
so
like
I,
have
a
passion
for
those
people
and
enabling
them
to
go.
Do
that?
And
you
know
it
keeps
that
repo
is
kind
of
the
fallback
that
you
know
we're
waiting
for
this
and
it
seems
like
can't
keep
waiting
for
it.
Yeah.
C
F
Have
wait,
who's
talking,
I
think
that
there
was
there
is
sort
of
right
now.
In
this
whole
thing,
a
big
bottleneck,
weather
well,
I
think
the
main
point
was
the
initial
design
and
I
think
once
that's
done,
we
can
take
steps
to
ensure
that
everything
moves
kind
of
smoothly,
because
we
can
actually
like
to
you
know,
development
and
set
up
some
open
source
thing
or
whatever,
like
yeah.
The
design
was
gonna,
be
handled
by
only
one
person,
which
kind
of
kind
of
sucks
wait.
H
I
I
mean
at
that
point.
This
is
the
sort
of
thing
where
the
foundation
helps.
Is
that,
but
part
of
that
would
mean
a
call
right
like
it
ends
up
being
for
like
a
request
for
submissions,
because
then
you
would
have
you
are
paying
someone
to
work
on
that
to
get
it
done
in
a
much
shorter
timeframe.
Unfortunately,
like.
I
A
So
with
that
we're
right
at
time,
so
let's
go
ahead
and
move
on
to
the
Q&A
see.
Looking
at
that,
we
have
one
question
from
max
SSH,
saying
hi:
what
do
you
think
about
p.m.
so
I?
Don't
know
if
this
is
necessarily
the
best
group
to
really
answer
that
question.
I
could
say
personally
I
used
it
for
a
long
time,
but
it
moved
a
way
for
from
it
in
favor
of
just
doing
shape,
systemd
services.