►
Description
Panel: Best Practices for Contributing to Node.js Core - James Snell, IBM
A panel of current Node.js core collaborators will discuss the Ins and Outs of contributing to Node.js core, covering best practices, recommendations, tips and tricks.
A
Welcome
this
is
the
panel
on
best
practices
for
contributing
to
node
core
I
want
to
keep
this
rather
informal
I
kept
telling
you
everyone
that
I
was
gonna,
put
together
some
questions
and
send
them
to
them,
so
they
can
kind
of
think
about
it.
Yeah
I
never
did
that.
So
I
want
to
keep
it.
You
know
fairly
light.
A
A
B
So
it's
not
even
been
a
year
and
since
I
first
contributed
to
note
card
that
was
in
December.
I
was
working
on
a
project
and
I
like
accidentally
passed
zero
instead
of
a
function
to
set
time
out
and
like
that
kind
of
worked,
it's
just
through
an
era
when
the
timeout
was
yeah
timed
out
and
like
that
was
pretty
hard
to
find
in
our
code
base.
So
a
patch
nerdcore
made
it
throw
an
error
immediately
when
it
got
zero
or
anything
and
then
place,
and
that
helped
me
find
the
error.
I
decided.
C
I've
been
using
notes
since
about
2012
I
found
out
what
I
was
doing.
An
installation
I
wanted
to
have
my
phone
control,
the
computer,
and
it
turned
out
that
was
hard
a
that.
A
year
ago,
I
was
looking
for
a
new
job
and
I
tweeted
and
said:
hey
I'm,
looking
for
work,
and
this
amazing
individual
NDB
Smith,
who
I
had
collaborated
with
before,
was
like
hey.
D
E
Okay,
it
works
for
me
it's
a
really
long
time
ago
that
I
started
working
on
though,
but
it
worked
like
this.
This
was
2010
and
I
had
just
seen
sort
of
the
initial
J
Escom
video,
where
I
know
it
was
announced
and
I
was
like.
This
is
amazing.
We
need
this
and
you
know
I
was
working
at
a
very
small
Dutch
start-up
at
the
time
and
what
we
did
is
we
ran
Atlas
Firefox.
E
To
like
do
some
JavaScript
on
the
back
end
was
super
unstable,
I'll,
say
used
a
ton
of
memory,
so
it
didn't
really
like
the
performance
was
quite
bad
and
there
were
other
practical
things.
I
was
like
yeah.
We
need
this,
but
we
then
very
practically
speaking.
It
at
the
time
only
worked
on
OSX
and
Linux.
That
was
fine
for
us,
except
that
our
devs
were
using
Windows.
We
were
a
PHP
shop
and
so
I
was
like.
E
Well,
let
me
just
fix
that,
and
that
was
a
kind
of
hubris
is
what
they
call
I
get
really
low.
It
was
much
more
work
than
I
thought
it
would
be,
but
once
I
started
doing
that,
I
just
loved
it.
Like
it
was
really
fun
and
it
turned
out
that
some
people
had
tried
and
I
you
know:
I
started
reading
MSDN,
which
is
like
the
the
Windows
documentation.
I
found
like
you,
know,
amazing,
secret
things
that
I
never
knew
existed
in
there
and
I
was
like.
E
We
need
this
to
make
no
work
on
Windows,
anyway
kind
of
figured
it
out
then
had
to
more
or
less
wait
for
half
a
year
until
like
someone
or
like
someone
would
be
Ryan
Dahl
at
the
time.
Actually,
that
was
was
open
to
landing
my
patches,
but
when
that
happened
it
turned
out.
There
were
a
lot
more
people
and
companies
actually
interested
in
porting
node.js,
so
winners
and
one
of
the
most
wrecks
pay.
So
they
offered
me
a
job
and
it
was
like.
Well
sounds
fun.
Let
me
just
do
that.
That's
it.
F
So
I
I
started
continuity,
I
started
working
with
node
very
early
on
I,
never
contributed
to
node
till
after
the
the
fork
and
the
merge
back.
Basically,
there
was
when
I
tried
before
that
was
not
really
accessible,
so
there
was
no
way
of
getting
it.
Basically,
the
door
was
shut,
so
I
became
a
contributor
at
the
end
of
last
year
and
I've
been
landing
a
couple
of
very
nice
patches
to
this
Swim's
implementation,
which
is
something
that
very
little
bit
critical.
So
and
yeah.
That's
just
me:
okay,.
A
Go
ahead,
an
old
on
the
micrometer,
that's
another
question
and
we'll
pass
it
back
around
this
way.
Okay,
so
outside
of
Burt,
the
three
of
you
are
relatively
new
contributors
to
node
when
you
first
started
what
what
are
some
things
that
you
know
now
that
you
wish
you
knew
before
you
got
started.
That
would
really
help
someone
who
is
just
coming
to
the
project
and
trying
to
get
started
with
contributions.
A
F
For
me,
it's
a
little
bit
different
in
this
regard,
because
I
already
knew
all
the
source
code
in
and
out
and
I
just
couldn't
get
him
a
way
to
start
helping
I
didn't
see
a
way
of
from
a
community
perspective
to
right,
starting
helping
out
the
project
so
for
me,
was
more
that
what
happened
in
general
was
getting
there.
Opening
the
files
trying
to
understand
what's
going
on
that
was
really
really
important.
Most
of
the
staff
was
in
fact
the
C++
bits
and
not
the
windows.
Part.
F
Never
I've,
never
done
that,
but,
like
literally
sitting
there
trying
to
understand
what
the
code
was
doing
and
how
to
how
things
were
playing
out
and
I
recommend
everybody
to
do
this
like.
If
you
want
to
contribute
to
core
in
whatever
specific
area
you
want
to
help
and
contribute
open
the
source
file
read
what's
what's
in
there,
it's
usually
decently
documented
this
day.
F
It
wasn't
so
much
in
the
past,
but
right
now
it's
fairly
good,
documented,
all
their
pieces,
probably
and
I
think
you
can
like
start
understanding
what's
going
on
and
propose
fixes
because
a
lot
of
stuff
like
our
little
minor
that
but
they
they
will
actually
improve
the
the
user
experience
of
people
using
node.
So
that's
just
what
it
is
for
me.
D
C
C
You
install
C
cache,
and
then
you
add
it
to
your
path
and
C
cache
wraps
all
of
the
compilers
and
caches
well
compiling,
and
it
will
bring
your
compiled
town
time
down
quite
a
significant
amount
and
be
prepared
for
compiling,
but
the
other
thing
that
I
think
is
worth
putting
out
there
is,
you
can
contribute
to
note,
and
it
doesn't
necessarily
mean
contributing
to
node
core.
There
are
so
many
different
places
that
we
could
use
support
and
help
and
projects
that
have
various
levels
of
accessibility
to
them.
The
github
bot
is
an
example
of
one.
C
It's
a
note
application
that
people
are
working
on
and
adding
features
do
that's
really
helping
with
the
performance
of
the
entire
organization.
The
website
is
an
application.
That
again
is
a
note
application
that
people
can
contribute
to
the
documentation.
This
is
a
really
great
place
to
get
started.
Anna
will
know
if
we've
finished,
having
the
notes
of
all
when
all
the
docks
were
added,
because
that
was
an
effort
that
was
going
and
those
were
good.
First
contributions
and
I'll
actually
use
that
as
a
means
taken
the
makeover.
So
she
can
correct
me
or
agree.
B
Yeah,
no,
we
are
fact
we
actually
do
now
happen,
almost
all
of
her
documentation,
Marcus.
That
any
case
when
a
feature
was
added
so
yeah
that
was
some
pretty
nice
I.
First
contributions
by
people
and
yang
generally
talks.
Things
are
a
really
easy
way
to
get
familiar
with
the
process
of
contributing
to
nerdcore
I.
B
Maybe
should
have
done
that
before
I
did
my
first
contribution
because,
like
that,
that
would
have
helped
just
knowing
what
to
do
what
people
were
expecting
me
to
do
when
they
said
I
should
document.
My
change,
like
I,
really
asked.
If
that
meant
like
should
I
go
to
the
change,
look
and
edit
their
didn't
know
that
I
was
automatically
generated.
A
C
Well,
I
mean
so,
if,
if
you
are
in
my
position,
right
now
and
you're
sitting
here
and
trying
to
think
how
can
I
contribute
and
you
can't
come
up
with
an
idea-
one
thing
you
could
do
is
on
IRC
to
come
in
to
hashtag
no
dev,
it's
the
IRC
channel
that
the
collaborators
are
in.
It
is
a
very
friendly
environment
in
that
channel,
in
particular,
very
much
about
collaboration
very
much
about
getting
things
done.
If
you
were
to
come
in
and
say,
hey
I
want
to
help.
C
I
would
be
extremely
surprised
if
someone
didn't
say:
okay,
let's
talk
about
this
and
figure
it
out
if
you're,
if
you're
in
the
audience
and
you're
not
sure
where
or
how
you
could
contribute.
But
you
have
the
energy
and
drive
to
come.
Find
me
message
me
on
Twitter
find
other
people
who
are
on
stage
or
who
you
know
have
the
energy
and
want
to.
But
people
will
work
with
you
to
help.
You
figure
out
how
you
can
get
involved.
B
Okay,
so
also
rich
truck,
who
has
my
mention
here
before,
but
like
yeah,
he's
just
great
at
getting
new
people
into
the
project
and
he's
actually
put
up
a
little
project
of
Sun.
It's
called
know
to
do,
and
it's
like
setting
you
up
with
first
good
contributions
that
you
can
make
to
note
car.
So
if
you
have
no
idea
what
you
could
do
and
like
you
just
like
somebody
who
tells
you
oh
yeah,
you
could
do
that
and
that
would
be
a
perfect
place
to
go.
E
Yeah,
so
let
me
be
a
little
annoying
here.
I
think
it's
it's
kind
of
the
wrong
question
to
ask
I
think
you'd
be
better
off.
You
know,
you'd
be
better
off
having
a
mission,
something
that
you
want
to
accomplish.
Something
you
think
is
not
possible
right
now
and
really
should
be
possible,
and
then
you
ask
yourself
like
okay,
you
know
where
should
I,
you
know
where
should
I
make
changes?
What
should
I
add
to
one
and
it
could
be
you
know.
E
Maybe
it
might
be
something
you
want
to
change
about
core,
but
I
think
in
very
many
cases
it
might
be
write
a
module.
You
find
a
module
that
exists,
make
it
better,
I
would
say
in
general
if
you
want
to
contribute
to
any
open
source
project.
Well,
unless
it's
your
job,
then
you
ask
your
boss
what
to
do,
but
if
it's
not
then
like
you
should
not
expect
anyone
to
tell
you
what
to
do
like
it's
really
not
how
open
source
works
in
general,
but
particularly,
oh,
yes,
like
there's
another
global
general
sense
of
direction.
E
E
So
for
me
this
was
indeed
that,
like
Windows
thing,
I
did,
but
you
know,
you'll
find
the
door
who's
sitting
there
in
the
in
the
audience
who
like
carry
much
about
to
you
less
at
some
point
and
if
I
made
it
much
better
and
you
know-
and
so
there's
there's
just
people
around
that
care
about
something
in
very
particular,
and
they
will
fix
that
and
the
other
you
know,
advice
that
I
would
give
is
unique,
probably
much
more
patient
than
you
think
you
do
and
what
happens.
A
lot
is
like
people
drive
by
they
makin.
E
Other
examples
might
be:
we've
had
a
patch
that
had
a
multi
isolate
support
to
know
more
or
less
it
was
I,
think
80%
done
or
something
that
was
a.
It
was
actually
phenomenal
work.
But
then
the
author
decided
to
do
something
else,
and
that
means
it
never
gets
landed
because
it
is
your
pet,
even
not
someone
else's.
So
it's
very
unlikely
that
someone
else
will
actually
pick
up
your
work
and
finish
it.
That's
what
I
wanted
to
say:
yeah.
F
F
Okay
I
will
just
send
up
the
up
problem,
but
its
first
of
all,
I
will
tell
you
scratch
her
on
each,
if,
if
possible
like,
if
you
eat
something
that
can
be,
that
you
think
should
be
change
it
and
you're
passionate
about
do
that
that
this
is
the
most
simple.
That's
the
only
way
you
will
be
to
that.
You
will
follow
up
enough
to
get
your
change
land.
That's
that's
a
key
part.
So
one
of
the
most
problematic
piece
in
open-source
software
in
general
is
a
person
that
Oh.
While
I
want
this
change.
F
It
sends
a
pull
request.
Then
somebody
some
people
said
well,
you
look,
you
should
change
this
and
that
and
review
of
that
request
and
that
some
people
just
bail
out
they
just
disappear
or
they
don't
like
follow-up,
like
I,
had
to
basically
I
work
around
the
clock
to
light
the
thing
right
before
v7
was
cut
because
the
guy
he
was
like,
oh
well,
disappeared,
and
he
didn't
make
a
little
change.
That
was
require
a
comment
or
something
like
so
just
to
be
on
to
be
on
point
it's.
This
is
the
first
thing.
F
The
second
thing
there
are
I
think
that
is,
and
also
a
new
installer
coming
or
something
just
to
mention
new
areas
where
also
all
their
onboarding
in
general
user
experience
can
be
probably
done
much
better,
rather
also
all
that
stuff.
It's
really
important,
because
it's
something
that
all
of
us
that
have
been
around
for
a
long
while
we
don't
remember
how
it
is
learning
the
stuff.
So
if
you
are
new
to
node
and
join
the
bandwagon
recently,
you
probably
have
a
much
closer
experience
or
what
it
is
learning
now.
A
Definitely
I
want
to
continue
on
that
point,
because
it
is
a
very
important
point
that
those
of
us-
you
know
yeah
I,
haven't
been
around
for
a
long
time.
You
know,
but
I've
still
been
around
and
involved
enough
that
even
I
I
start
to
forget
how
it
is
for
a
new
person
coming
to
the
project
to
actually
you
know
to
learn
it.
So
you
know
the
two
of
you
before
I've
been
you
know
out
of
everyone
here,
but
around
the
longest
and
you've
seen
the
process
for
contributions,
change
gone
through
the
different.
A
You
know
the
the
change
in
governance
right
and-
and
you
know,
we've
we've
made
steps
to
make
the
the
process
easier,
more
inclusive,
more
more
friendly
to
new
people,
but
we're
nowhere
near
we're
nowhere
near
there
all
right
we're
nowhere
near
to
the
point
where
we
need
to
be
so
I
wanted
to
kind
get
some
thoughts.
I
mean
you
know.
How
is
the
evolution
been?
Are
we
heading?
Have
we
been
heading
the
right
direction
and
how
much
more
do
we
have
left
to
do
and
I
want
to
ask
both
of
you
this
question
as
well?
F
The
at
when,
whenever
I
staffs
had
to
look
into
to
contribute
into
core
I
mean
something
I
can
I
now
know
enough
of
this
to
s
pass
through.
My
inputs
have
seen
them
to
some
extent
and
I
can't
contribute
to
you
know
they
can
do
something
here.
I
can
out
the
project
grows.
As
I
said,
the
door
was
shut
like
there
was
no
way
like
I
tried
to
I.
Even
try
can
I
send
a
PM
to
send
a
couple
of
things
and
I
was
told
very
bluntly.
F
No,
we
don't
want
your
fixes,
and
that
is
definitely
not,
and
for
no
really
like
giving
me
like
very
bad
reasons
why
that
was
not
possible.
So
all
of
this
is
not
is
the
exact
opposite
of
being
inclusive
and
saying,
like
some
face,
might
not
be
good
I,
don't
it's
true,
but
like
giving
like
very
bad
motivations
that
are
not
absolutely
not
technical
and
no
nothing
it's.
F
F
One
of
the
things
that
we
are
not
great
at
is
we
provide
feedback
and
reviews
about
I'd,
say
mostly
between
ourselves,
rather
than
other
people.
Like
me,
I
try
to
reply
to
all
the
the
poor
requests
that
I
see
and
that
they
watch
very
smoothly
and
quickly,
but
we
are
still
not
fast
enough
in
providing
feedbacks
to
wanna,
be
contributors
and
new
people
that
are
joining
the
project
and.
A
F
Problem
is
because,
unfortunately,
we
are
there's
a
lot
of
traffic,
it's
a
very
high
traffic
project,
so
it's
really
hard,
at
least
it's
easier
to
keep
up
I
just
to
tell
if
I,
I've,
disabled,
all
the
notification,
I
got
notification
or
leave
it's
at
not
to
us
collaborators,
because
it's
not
it's
not
feasible
or
not
jeah
streams
or
whatever.
Now
we
have
enough
nice
pots
that
tax
that
taxes,
a
group.
B
E
Things
that
evolves
yeah,
I'm,
trying
to
remember
the
question
now.
Thank
you
well
I
mean,
obviously
the
project
got
much
bigger.
So
initially
it
was
just.
It
was
very
easy
to
coordinate
things
because
you
know
we
were
just
going.
Rc
have
our
own
like
little
private
channel
and,
like
you
know,
figure
out
what
the
next
steps
would
be
all
kind
of
obvious,
but
then,
as
a
project
grows
that
you
no
longer
scales,
it
becomes
too
noisy
too
many
people
you
know
are
around
in
the
first
place
to
you
know
and
have
opinions
about
things.
E
So
it's
not
so
easy
to
agree
on
things.
I
think
another
issue
is
like
I
mean
I.
Think
we're
all
in
agreement
that
it's
generally
better
not
to
have
like
a
dictator
or
like
benevolent
or
not,
but
the
the
I
think
in
the
early
stages
of
the
project.
It
was
really
beneficial
because
it
you
know
it
made
it
very
easy
to
like.
There
was
someone
who
had
a
vision
and
could
make
decisions.
He
could
be
like
promises.
No,
you
know
like
child
processes.
E
Yes,
I
mean
that
at
some
point
they
were
not
there
and
then
it
was
decided
they
should
be
there.
It
was
easy
enough,
I
think.
Nowadays
this
is
a
bit
of
an
issue
with
nodejs,
it's
very
hard
to,
as
a
group
have
you
know
any
opinion
at
all
or
like
make
decisions.
There's
always
someone
there's
always
a
couple
of
people
that
you
know
think
the
opposite.
E
You
know
there's
no
necessary
natural
leadership,
I'm
not
saying
there
should
be,
but
and-
and
maybe
this
is
the
biggest
problem
currently
there's-
also
not
necessarily
a
lot
of
structure
around
it.
So
it's
not
like
okay
I
would
like
to
add
this
feature
to
cork
and
I.
Ask
someone
whether
it
would
be
accepted
like
there
is
not
really
anyone
you
can
ask
like
a
best.
You
could
ask
the
you
know
the
core
techno
committee,
whether
it
could
be
done
and
the
core
technical
unity
will
usually
say.
E
We
don't
know,
and
by
the
way
there
is
no
patch
so
like
just
go
figure
it
out
on
github
and
so
I
think.
If,
as
a
you
know,
if
you
were
a
pure
outsider,
it
would
be
very
hard
to
figure
out
whether
it's
worthwhile,
you
know
trying
to
get
something
into
note
or
not,
and
it
takes
a
little
bit
of
like
I
would
say
you
know
you
need
to
know
the
community
the
way
you
know
understand
what
sometimes
people
have
mentioned
certain
directions.
E
The
projects
going
in
that
would
be
good
indications
right
now
and
yeah,
just
yeah
sort
of
understanding
the
philosophy
of
the
project
and
that's
something
you
can't
really
it's
very
hard
to
write
down
and
get
get
people
to
understand
if
they're
new,
but
it's
definitely
something
we
could
be
better
at
right.
Right.
B
So,
like
one
thing,
you
can
do
if
you're
not
sure
whether
something
is
worthwhile
or
not
is
just
post
an
issue.
That's
that's
what
I
do
like
when
I'm,
not
sure
whether
people
would
accept
the
change
I'd
like
to
propose
and
like
it
got
shut
down,
often
enough
but
like
I,
just
asked
and
I
didn't
want
to
go
to
all
the
trouble
of
making
the
coat
and
opening
a
pull
request.
B
So
yeah
I
just
asked,
and
that's
one
thing
you
can
do
you
can
take
a
look
like
we're,
not
super
good
at
documenting
the
values
we
try
to
represent
a
lot
of
people
think
that
the
core
project
should
be
rather
small,
like
anything
that
can
be
done
with
outside
of
it
should
be
done
with
that
outside
of
it.
So
that's
one
thing:
you
can
look
at
we're
trying
to
document
that
kind
of
thing:
we're
not
very
good
at
having
that
in
the
central
place
or
anything
yeah.
B
D
C
I'm
not
sure
that
we
will
ever
be
able
to
just
call
it
an
inclusive
place,
but
what
we
can
do
is
set
up
processes
and
environments
that
make
it
easier
to
get
towards
that.
I.
Don't
think
that
we
can
make
any
claims
about
where
we're
at
right
now,
but
can't
talk
about
our
things
that
we've
done
to
improve
it.
So
one
thing
I
can
think
about.
Is
the
documentation
working
group
where
we
collectively
agreed
that
we
wanted
to
make
the
process
of
landing
documentation
fixes
lower.
C
C
To
note
constantly
that's
not
really
something
you
think
about,
but
if
you're
someone
who
is
newer
to
programming
or
is
not
as
experienced
to
contributing
over
github,
simply
you
know
rebasing
or
squashing
or
commit
isn't
like
that
will
be
a
whole
day
just
to
do
that
and
that
can
really
block
people
and
stop
them
from
contributing.
So
I
think
we
figuring
out
more
processes
that
we
can
do
to
help.
Enable
and
empower
individuals
will
will
be
a
way
in
which
we
can
do
this
right.
A
A
A
E
E
Let's
say
you,
you
know,
let's
talk
about
skiing,
like
learning
to
ski
socks,
I,
don't
know
if
you
ever
tried,
if
you're
not
like
you're
kind
of
you
know
like
made
from
wood
like
myself,
like
I
will
have
just
fall
all
the
time
and
like
you'll
bruise
yourself,
it's
you
know
the
fact
that
learning
to
ski
sucks,
you
can't
really
say
skiing
is
not
very
inclusive.
That's
nothing
to
do
with
it.
It
would
not
be
inclusive
if
he
said
well,
you
know
you
know
you
have
a
different
skin
color.
So
you
know
you.
E
You
always
have
to
go
last
like
that.
We,
you
know
if
we
make
something
where
we
make
it
very
hard
for
someone
for
some
like
totally
stupid
reason,
then
we
would
say
is
not
inclusive
but
I
mean
I.
Think
we
all
recognize
that
yeah,
like
it's
software
engineering,
it
takes
scale
like
you
know,
getting
to
understand
how
open-source
works.
E
It's
like
it
takes
a
little
bit
of
effort,
and
sometimes
you
will
get
burned
and
some
people
you
know
you've
got
just
also
used
to
the
pain
and
tunes
for
an
extent
like
I
think
we
all
have
had
written
patches
put.
Ours
are
tears
and
sweat
in
it
and
it
never
they're
like
that.
Just
happens
and
I
think
we
can
recognize
that
this
is,
you
know,
sort
of
for
the
greater
good
like.
E
Ultimately,
it's
not
about
you
know,
James
can't
pee
for
say
it's
good
that
he
has
one,
and
hopefully
it
can
actually
benefit
the
project.
But
if
you
know,
if
it
turns
out
it's
not
good
for
a
project,
we
should
not
land
it
like
it.
You
know
landing
patches
is
not
legal
in
itself
and
it
takes
some
effort
and
I
think
the
only
like
it
is
a
real
issue
like
if
we,
if
we
recognize
that
well,
it
turns
out
to
be
much
harder
for
you
know
certain
groups
for
to
get
their
patches
accepted.
E
C
Half
of
them
are
docking
test
fixes
and
those
aren't
held
to
the
same
standard
as
stuff
in
core
and
I'm,
not
saying
that
they're
not
as
important
but
just
the
code
is
in
is
hot.
We
don't
need
to
be
as
rigorous
in
writing
our
test
code
as
we
need
to
be
in
our
production
code
and
our
documentation
as
well
as
like
it's
not
you
can
go
through
and
James
has
done
this
and
go
through
all
the
pros
and
find
lots
of
places
where
you
can
contribute
and
help.
C
So
I
see
no
reason
why
we
shouldn't
be
trying
to
help
enable
and
empower
people
who
aren't
even
developers
to
begin
with,
with
the
ability
to
help
and
contribute
and
I've
seen
numerous
people
who
start
that
way
and
then
can
grow
to
be
some
of
our
best
contributors
in
the
meantime,
and
so
I'd
be
worried
a
little
bit.
That
kind
of
the
way
you
were
you
were
talking
about
approaching
a
bird
like
yeah.
There
is
a
lot
of
learning
to
do
and
it
it
isn't
fun
to
ski
and
fall
down
a
hill.
E
My
point
was,
of
course,
that
inclusivity
and
like
it's
easy
to
contribute
our
different
things
and
what
you're
saying
is
well,
you
know
we
don't
you
know
you,
you
know,
we
don't
just
need
a
black
slope.
We
want
a
blue
one
whatever
and
an
orange
one
too,
and
yes
that
that's
totally
true
and
I
think
over
time.
The
project
has
needed
more
and
more
of
people
that
do
these
kind
of,
like
maybe
you
know,
I
last
part
or
things,
and
it's
actually
very
helpful
for
the
project
to
do
that.
B
We
should
like
really
get
places
to
show
that
the
work
is
valued.
I
know
that
may
be
a
bit
hard
for
when
we
have
contributed
list
of
I.
Don't
know
maybe
thousand
people
by
now,
but
we're
at
least
really
close
to
that.
But
yeah
we
are
tech
people.
There
are
ways
to
do
that
we'll
find
a
way
and
we
should
and.
F
I
just
want
to
help
me
from
with
most
of
it,
even
on
the
point
of
view
that
are
not
in
agree,
I
agree
with
with
both
sides.
Basically,
so
it's
it's,
there
is
a
lot
of
work
in
all
in
all
the
stuff.
I
just
want
to
add
one
more
thing
that
we
haven't
talked
about
to
now.
It's
it's
still
very
hard
to
contribute.
I
call
Grand,
Challenge
challenge
in
in
in
core,
like
there
are
some
piece
of
functionality
that
should
be
in
core
that
it's
not
in
core
and
it's
not
something
that
it's
done
ever.
F
F
Dtls
is
something
that
should
be
core
and
it's
not
so
it
is.
If
you
are
in
the
Internet
of
Things
word,
you
know
what
I'm
talking
about,
but
this
is
my
take
another
one
is
HTTP
to
maybe
we
see,
which
is
something
about
that
in
the
near
future,
but
I
think
one
thing
we
should
be
better
at
is
hi
lightning.
What
are
the
problems
that
the
grand
challenge
like?
Do?
F
We
want
something
that
is
big
to
land
in
a
big
chunk
of
functionality
that
maybe
a
group
of
people
can
take
together
and
how
to
do
and
how
to
support
the
type
of
collaboration,
because
the
current
level
of
contribution
right
now
is
around
the
single
ProQuest.
It's
a
single
individuals
than
send
a
little
fix,
rather
than
a
group
of
people
that
contribute
a
bigger
chunk
of
work,
or
maybe
ten
or
twenty
commits
or
summary
that
do
do
some
stuff.
So
it's.
A
It's
definitely
a
good
point.
We've
we've
had
a
when
I
first
got
involved.
We
have
this
this
thing
it
was
pretty
common
or
if
a
pull
request
was
too
minimal
right,
it
was
just
changing
a
word
and
the
doctor
changing
a
comment
or
whatever
it
was
that's
too
small
for
us
to
even
look
at
to
consider
and
a
lot
of
times.
They
were
just
rejected
outright,
I'm
very
happy
that
we've
moved
away
from
that.
You
know
to
this.
A
This
idea
that
no
no
change
is
too
small,
because
you
know
it
may
be
that
the
person
is
just
trying
to
get
their
feet
wet
and
in
in
how
to
contribute
and
getting
familiar
with
the
process.
So
it's
you
know,
I'm
very
happy
that
we're
kind
of
breaking
that
that
bottom
barrier
right
but
you're
right.
We
have
this
this.
This
block
on.
A
E
Funny
that
you
mentioned,
are
there
James
and
like
in
defense
of
the
good
old
times
like
that
was
a
time
that
there
were
literally
two
people
who
would
ever
review
pool
requests.
If
you
you
know,
if
you
get
like
you
know,
you
know
tens
or
something
like
that
per
day.
Then
it
becomes
a
lot
of
work
to
review
everything
plus
you
know
we
had
a
little
process
so
yeah,
you
know,
including
at
the
time,
checking
the
CLA
like
telling
people
like
to
fix
their
code.
E
So
if,
if
you
make
a
one
word
change,
there
was
just
too
much
overhead
before
us
to
process
nowadays,
I
think
it's
very
different
and
I
think
actually
poor
request
cannot
be
small
enough,
more
or
less
correct,
because
we
have
so
many
collaborators
that
can
actually
review
and
stuff
nowadays
and
so
like.
If
anything
we
should
probably
have
done.
That
earlier
is
what
everything
so.
A
A
C
So
I'm
gonna
repeat
the
question
and
just
give
me
a
thumbs
up
if
I
got
it
right,
but
it
was
using
es
modules
as
the
frame
and
specifically
that
in
these
very
very
large
contentious
issues
with
lots
of
conversation,
it
can
be
really
hard
to
keep
track
of
everything,
that's
going
down
happening
and
then
it
can
almost
feel
like
the
core.
Technical
Committee
is
privy
to
more
information
and
that's
not
necessarily
being
shared
in
the
best
way.
We
don't
know
either.
A
C
There's
just
there
is
so
much
stuff
and
I've
seen
it
happen
where
things
get
locked,
sometimes
or
when
discussion
gets
like
moved
and
generally
that's
just
so
like
we
can
keep
up,
but
what
I
can
suggest
for
you
is
the
core
Technical
Committee
meetings
are
weekly
and
they're
available
and
generally
what
we're
doing
in
those
meetings
is
actually
giving
updates
as
to
what's
going
on
with
a
lot
of
this.
So
anytime,
there's
like
big
things
like
async
rap
updates
on
ES
modules
updates
on
the
URL
parser.
The
change
was
doing
pretty
much
any
larger-scale
work.
C
That's
happening
has
a
weekly
update
happening
during
that
meeting
and
all
the
meeting
notes
are
available
and
marked
down
inside
of
the
repo.
If
you
go
into
documents,
the
core
technical
committee
meeting
notes
are
there
I
think
I
think
that
this
is
an
interesting
challenge
that
we
want
to
try
to
figure
out
how
to
solve
as
well,
and
this
is
perhaps
an
example
of
something
some
other
way
and
what
you
can
come
and
help
out,
which
was
some
of
the
social
problems
of
collaborating
on
software.
C
It's
tough,
yes,
modules
is
filled
with
so
many
opinions
and
thoughts.
People
are
scared.
People
are
angry.
People
are
excited,
they
it.
You
can't
wait
through
it
all.
You
almost
need
to
know
exactly
the
one
or
two
places
to
look
to
get
an
update
on
how
we
feel
about
it
today,
and
that's
the
other
thing
too,
because
it's
constantly
shifting
so
I
believe
that
the
foundation
has
actually
hired
an
amazing
individual,
gen
Turner
to
start
putting
together
newsletters
that
are
going
to
try
to
collect
some
of
this
information.
C
A
How
do
we
communicate
that
with
the
community
and
also,
how
do
we
reverse
it
in
terms
of
making
sure
that
this,
the
CTC,
the
core
technical
team,
is
getting
the
proper
input
and
feedback
from
the
community
that
we
need
right,
because
that
that's
that's
the
other
side
of
it
is
a
lot
of
this.
A
lot
of
the
decisions
are
being
made
kind
of
in
a
vacuum,
because
we
don't
know
necessarily
what
the
community
is
needing
with
these
things.
So
we
need
more
I
just.
F
Want
to
add
want
to
do
a
couple
of
things
about
yes,
modules
and
promises,
which
is
the
most
contentious
things.
First
of
all,
you
probably
not
see
me
commenting
on
those,
so
that's
the
that's
the
first
thing
most
of
most
of
the
time
you
should
like
be
careful
when
that
is
these
flames
going
on
in.
Is
there
somebody
else
that
has
already
made
your
points?
Probably
don't
add
more
noise
to
the
conversation?
That's
one!
Usually.
If,
if
you
have
some
new
points,
some
new
ideas,
fresh
ideas,
please
we
want
to
hear
all
of
them.
F
F
A
You
know,
and
I
also
just
want
to
point
out-
it's
like
in
all
the
process
that
we
do
have
you
know.
Yes,
there's
code
contributions,
we
talked
about
there's
various
ways
of
contributing
getting
involved.
Just
to
help
us
get
better
at
the
process
is
another.
If
there's
another
option,
there's
one
individual
here
at
the
conference,
William
koepcke
nano
caught
a
cable.
You
know
he
started
getting
involved
with
the
TSC
repository
just
to
help
us
keep
on
top
of
stuff
right.
He
looked
at
it
and
realized.
A
Well,
these
people
aren't
actually
maintaining
this,
so
he
he
volunteered
to
start
maintaining
it
and
his
his
help
has
been
absolutely
invaluable.
So
it's
actually
keeping
the
TSE
running
smoothly.
You
know
it
you
know
in
you
know
he
hasn't
made
a
lot
of
I.
Think
he's
made
a
couple
of
code
contributions
and
stuff
he's.
A
great
engineer.
He's
done
some
wonderful
things
out
in
the
community,
but
as
far
as
his
contributions
to
core
it's
primarily
just
keeping
us
all
on
track
that
kind
of
stuff.
You
know
if
you
want
to
come
help.