►
Description
KEYNOTE: The Road Forward - Tracy Hinds, Node.js Foundation
A
A
The
next
thing,
I
do
have
to
say
is
an
apology,
because
when
I
created,
these
slides
I
always
have
ice
cream
on
the
brain
and
so
I'm
cutting
out
these
ice
cream
people,
and
then
I
was
warned
once
I
showed
people
the
deck
that
you
get
really
really
hungry
for
ice
cream.
So
the
surprise
is
not
ice.
Cream,
I'm
gonna
spoil
that
ahead,
yeah,
so
hi
I'm,
Tracy
Hines.
As
Michael
said,
we
work
together
at
the
node
foundation.
A
I'm
the
education
community
manager
I've
also
been
working
on
some
of
the
inclusivity
efforts
as
of
more
recently
so
Jeff
a
sniff
I,
don't
know
if
any
of
y'all
have
heard
of
that
term.
It's
JavaScript
is
fun,
and
so
note
is
fun.
If
you
try
and
reverse
that
it's
really
hard
to
pronounce.
But
I
do
think
that
note
is
fun
and
so
javascript
is
fun.
So
note
is
seven
years
old
and
the
Foundation's
celebrated
a
birthday.
We're
gonna
take
a
look
at
how
the
node
community
came
to
be.
A
How
the
fork
was
great
trust
me
how
flawed
we
are
as
humans
and
a
lot
of
our
efforts
and
how
inclusivity
has
anything
to
do
with
all
of
this
rest
retrospection
as
well
as
future
planning.
So
back
when
I
first
started,
programming
I
was
enjoying
my
cook
community.
Like
nothing
else,
I
lived
in
Portland
Oregon
and
there
was
a
new
meetup
in
town
starting
every
week.
People
were
chomping
at
the
bit
for
the
latest
technologies,
including
node,
and
they
were
happy
to
share
it
with
others.
A
So,
when
I
found
a
group
that
was
starting
that
I
had
been
keenly
interested
in
starting
myself,
it
was
not
node
I
offered
support
I,
emailed
I
deemed
the
folks
that
were
gonna,
be
starting.
That
effort
and
I
got
no
response.
So,
okay,
you
know
I'm
pretty
new,
maybe
I
just
don't
know
the
right
path,
so
they
connected
people
so
I
messaged
them
on
meetup
and
still
no
response.
A
So
I
started
tending
the
events
more
and
more
and
getting
their
trust
and
they're
still
not
really
letting
me
in,
and-
and
so
maybe
you
know
it's
just
out
of
them,
seeing
an
overeager
beaver.
But
you
know,
I
was
really
excited
to
help
out,
and
my
mentor
had
also
suggested
that
it
would
be
a
great
way
to
get
involved
in
starting
your
own
group
as
a
newer
person
in
programming
or
even
in
a
city
is
a
really
tough
thing
to
do
and
he's
trying
to
set
me
up
for
success.
A
So
it
turns
out
that
they
did
not
want
my
help
and
they
made
that
pretty
clear.
But
after
I
found
a
niche
which
was
the
weekend
hack
times,
you
needed
to
show
up,
and
that's
all
you
needed
to
do.
You
didn't
need
to
be
an
expert.
You
needed
to
be
a
person
they're
representing
pie,
ladies
to
welcome
people
and
make
sure
that
they
had
somebody
else
to
talk
to
you
and
I
wrote
Python.
It
just
wasn't
great
at
it,
and
that
was
enough.
So
you
know
I.
A
A
It
was
a
really
cool
space
and
I
went
I
was
really
excited,
especially
because
I
just
started,
writing
JavaScript
full-time
at
my
day
job
and
we
were
starting
to
pick
up
node
and
my
mentor
was
as
well
and
it
was
really
exciting
because
I
had
this
local.
You
know
this
new
local
thing
that
was
going
to
help
support
me
and
learning
that
and
so
I
showed
up
and
the
energy
was
really
incredible.
A
There's
over
a
hundred
people
and
in
Portland
that's
really
rare
for
a
meet-up
in
general
and
especially
around
a
technology
that
was
not
as
big
at
the
time
such
as
node,
and
so
everybody
was
really
excited.
We
stayed
way
after
the
meetup
was
supposed
to
end
and,
as
I
do
I
approached
the
organizers,
Merlyn
and
Ben
and
told
them
how
excited
I
was
about
the
group
and
all
the
cool
things
that
we
could
do
just
because
I
was
really
excited.
Attendee
and
and
Ben
saw
my
excitement.
A
I
was
just
like
whoa
like
he
doesn't
have
enough
energy
by
himself
to
do,
and
you
know
they
both
had
family
and
he's
like.
Why?
Don't
you
help
like?
Why?
Don't
you
help
organize
and
I
can't
pauses
like
this
dudes
like
what
is
he
thinking
he
doesn't?
He
did
not
know
me.
That
was
the
first
time
he
had
met
me,
and
so
I
said
yes,
because
that
was
awesome.
A
Even
if
it's
just
local-
and
you
know,
there's
nothing
better,
really,
honestly
for
a
new
person
in
a
community
than
to
be
valued
right
to
be
asked
for
help,
and
and
so
for
me
that
was
really
powerful.
You
know
asking
for
help
and
making
the
space
or
getting
out
of
the
way
for
those
who
have
the
energy
and
enthusiasm
to
help
I.
Think
that's
a
huge
legacy
of
node
and
its
community
I
think
that's
a
story
that
we
have
to
protect.
I
know
a
lot
of
people
who
have
similar
stories
and
I.
A
Think
that's
what
you
know
that
makes
people
feel
wanted
and
supported
to
do.
The
work
that
they're
excited
to
do
so
how
does
node
fit
into
this
larger
jeaious
landscape?
This
is
something
that
I
have
to
I
hang
out
in
the
Lord
of
JavaScript
community
and
wall.
Node
can
feel
really
big.
Sometimes
it
can
also
feel
really
small
in
some
of
the
fights
that
we
end
up
having,
but
no
no,
no
tis
a
platform.
Most
of
you
know
this.
A
It's
a
set
of
api's
for
JavaScript
to
do
things
that
JavaScript
was
not
necessarily
intended
to
do
and
without
having
a
context
which
it
can
lower
the
barrier
to
writing
full
stack.
So
you
know
why
should
other
programmers
care
about
node
at
all
and
I?
Think
a
lot
of
people
have
covered
that
over
the
past
few
days.
You
know
think
about
things
like
NPM,
all
the
front-end
folks
using
it.
A
You
know
that
relies
on
node,
that's
what
I
think
5
ashle
of
the
numbers,
but
it's
like
5.7
million
people,
and
you
know
anyone
using
WordPress,
which
runs
4.5
percent
of
the
Internet.
These
are
important.
There
are
open,
important,
open
source,
technological
and
community
lessons
to
be
learned
here.
We
saw
an
exciting
project
of
node
that
a
lot
of
people
have
invested
and
had
invested
their
work
at
one
point
into
the
brink
of
real
trouble.
Two
years
ago,
our
global
project
was
down
to
four
node
core
maintainer
x'.
A
A
So
there's
this
idea
that
our
ability
or
stalled
ability
to
get
things
done
as
individuals
working
towards
a
larger
goal,
such
as
maintaining
and
improving
the
node
project.
It's
called
community
capacity.
So
this
is
our
ability
to
promote
or
sustain
the
well-being
of
the
community
and
its
components,
and
that
means
individuals.
That
means
organizations.
It
means
social
interactions
and
the
code
base
that
we
all
rely
on.
So
what
I'd
like
to
introduce
as
part
of
this
is
the
idea
of
the
tyranny
of
structure
lessness.
A
So
bear
with
me
a
lack
of
heavy
organizations
in
process
early
on
was
pretty
integral
to
node.
Excuse
me
to
note
code
and
community
events
happening.
Many
declared
the
lack
of
structure
a
way
to
keep
contributors
from
being
bogged
down
in
process
and
approval.
The
fallacy
here
is
that
a
lack
of
organization
or
structure
is
not
structure.
Lists
implicit
structure
grows
from
friendships.
A
It
grows
from
accidental
elitism,
which
is
just
it
son
intention
and
then
also
good
intentioned
offensiveness,
to
protect
the
quality
of
the
code
base,
these
silent
imbalances
of
power,
something
I'm
going
to
explore
a
little
further.
When
we
talk
about
privilege
and
inclusivity,
we
couldn't
fool
ourselves
into
thinking
that
node
was
going
to
continue
to
grow
without
having
some
structure
in
place.
So
we
started
growing
heavy
by
the
burden
of
our
own
booming
project
and
development
slowed
to
a
crawl.
A
A
It
was
also
under
an
open
governance
model,
as
opposed
to
corporate
stewardship
and
around
that
time,
Rod's
open,
open
source
policy
paved
the
way
for
a
much
friendlier
model
to
getting
contributors.
You
know
contributions
merged
and
becoming
a
collaborator
in
open
source
projects,
which
was
really
really
powerful
and
I.
Think
we've
heard
a
number
of
stories
for
that
as
well,
so
February,
the
very
next
month
join
the
corporate
Stewart
of
the
project
at
the
time
and
then
owner
of
the
node
IP
announced
the
formation
of
the
node
foundation
at
node
summit.
A
It's
like
that's,
really
quick.
It's
only
a
month
later,
but
foundation
formation
is
not
quick
and
joint
had
been
working
with
the
community
through
the
meeting
of
an
advisory
board
for
several
months
to
try
and
alleviate
the
pressure
for
the
community
around
governance
by
March,
the
bylaws
were
drafted
and
being
circulated,
and
that
was
also
an
interesting
mix
of
companies
and
community,
but
it
took
until
May
for
the
I
OTC
to
vote
to
enter
the
node
Foundation
and
merge
with
node
and
that's
not
a
bad
thing.
A
That's
that's
a
lot
of
consideration
and
back
and
forth
and
making
sure
that
we're
all
doing
the
right
thing
right.
So
in
June
we
see
the
official
launch
of
the
node
foundation
with
founding
corporate
members,
followed
by
the
Board
of
Directors
being
established.
The
first
ever
node
collaborator
summit
occurred
and
that
joined
many
of
the
collaborators,
including
back
from
the
fork
in
one
place.
So
the
results
of
these
months
of
tough
conversations,
diplomacy
and
pull
requests
was
the
release
of
node
v4
in
September
2015,
and
that
was
the
convergence.
A
So,
in
order
to
do
that,
it
means
we're
all
collaborating
and
we
need
to
feel
the
agency
and
safety
to
contribute.
We
have
millions
of
people
in
the
node
community
who
are
essentially
unfamiliar
co-workers,
walking
the
halls
of
github
and
we've
had
very
little
prior
interaction
with
one
another.
So
we
are
humans
and
we
can
have
very
different
motivations,
and
this
can
add
up
to
an
energy
tense
environment
that
we
have
to
tread
very
thoughtfully
through
with
care
and
respect.
A
We,
as
community
members,
drive
the
values
of
the
node
project
forward
and
that's
through
the
ways
we
interact
with
one
another
in
person
and
online,
so
we're
a
global
community
with
colliding
cultures
and
belief
systems
and
ultimately
we're
interacting
because
we're
all
trying
to
get
our
jobs
done
or
follow
through
with
our
passions.
It's
that
simple.
But
none
of
this
is
easy.
So
for
many
of
us
privilege
is
an
invisible
thing.
We've
been
socially
programmed
to
remain
unconscious
of
in
the
US
and
many
parts
of
the
world.
A
This
privilege,
though
you
did
not
ask
for
it,
could
be
being
white
or
being
male
or
being
born
to
a
family
with
money.
So
for
others
who
are
not
advantaged
it
can
make
daily
work
or
just
existing
in
our
community,
pretty
tiring
or
even
painful.
It
is
silent
imbalances
of
power,
there's
a
great
anecdote
from
Franchesca
Ramsey
of
it's
often
when
we
talk
about
privilege,
a
common
rebuttal
is
I,
can't
be
privileged.
I
grew
up,
poor,
but
being
disadvantaged
in
one
area
doesn't
negate
privilege
and
others.
A
So
then,
the
question
to
ask
for
all
of
these
imbalances,
as
we
become
aware
of
them,
is
what
will
I
do
personally
to
lessen
or
end
it.
By
acting
on
our
awareness
of
these
imbalances
and
continuing
to
grow
the
positive
efforts
of
collaboration
in
our
ecosystem,
we
can
build
an
even
more
concrete
foundation
to
which
node
will
be
a
more
awesome
place
to
code.
A
So,
as
you've
heard
over
the
last
two
days,
the
foundation
is
a
number
of
groups,
collaborating
to
grow
and
maintain
the
health
of
the
node
project,
ecosystem
and
community.
It's
the
TSC,
along
with
countless
numbers
of
working
groups,
the
board
execs
in
the
community,
so
within
each
of
these
groups,
our
responsibilities
to
improve
node
leverage
by
the
expertise
of
them
participating
a
few
months
back.
Some
of
these
groups
began
to
do
a
new
dialogue
around
the
inclusivity
working
group
and
what
it
means
to
be
working
on
inclusivity
and
diversity
in
node.
A
The
same
process
that
allowed
the
technical
side
of
our
project
to
grow
and
thrive
was
seemingly
stalled
for
cultural
safeguards.
Maybe
that
process
didn't
quite
fit
so
I
was
tasked
with
investigating
the
migration
of
the
inclusivity
working
group
responsibilities
potentially
to
the
node
foundation
or
the
executives
board
from
the
TSC.
It
was
simply
an
investigation.
It
wasn't
a
mandate
to
do
that.
A
With
these
struggles,
I
looked
to
other
projects
for
the
struggles
they
had
seen
and
how
they
tried
to
help
unite
collaborators,
but
we
don't
always
get
the
luxury
of
someone
else
setting
precedents
so
I'm,
going
to
start
by
laying
out
a
few
definitions
and
I'm
gonna
walk
into
the
inclusivity
proposal
that
I
came
up
with
as
a
result
of
this
year,
so
inclusivity
in
this
context
means
feeling
supported
and
heard.
It
is
the
intention
and
policy
of
including
people
who
might
otherwise
be
excluded
or
marginalized,
to
create
a
productive
work.
A
Climate
of
trust
and
respect
and
diversity
means
background.
You
know
diversity
of
background
of
thought
of
perspective,
for
everyone
who
wants
to
take
part
or
maybe
don't
know
yet
that
they
want
to
take
part
but
should
feel
that
they
want
to
when
they
discover
it.
So
the
first
strategy
that
I
came
up
with
was
the
addition
of
a
top-level
community
organization
alongside
the
TSC.
So
that
means
that
there
are
a
number
of
organizations
that
have
absolutely
contributed,
as
I've
already
mentioned,
to
the
growth
of
node.
A
There's
note
school,
there's
no
BOTS,
there's
a
thousand
of
individual
meetups,
there's
conferences.
This
is
a
not
an
exhaustive
list.
It's
clear
that
the
community
activities,
such
as
events
fall
outside
of
the
realm
of
the
code,
the
TSC
oversees,
and
these
are
vital
to
the
life
and
energy
that
we,
you
know,
we
feel
as
we
grow
the
project.
So
alongside
this
you
know
someone
and
or
this
is
giving
this
is
giving
a
voice
to
our
community
members.
This
is
a
challenge
because
we're
not
we're
not
saying
we're.
A
Gonna
take
over
all
of
these
amazing
organizations
that
exist
in
the
community.
This
is
very
different
than
what
the
TSC
ends
up
representing.
So
what
we're
doing
here
is
giving
voice
and
representation
to
all
of
these
community
projects
and
that
voice
would
then
be
carried
through
by
the
individual
members
ship
directors
sitting
on
the
board,
so
they
would
represent
the
community
organization
on
the
board,
so
that
was
what
I
felt
was
necessary
in
order
to
sort
of
get
these
get.
A
This
first
idea
off
the
ground
and
one
being
that
inclusivity
working
group
needs
to
move
over
to
that
newly
established
organization.
So
draft
charters
been
made
as
being
worked
on
the
next.
The
next
step
in
this
is
educating
our
leadership,
so
I
looked
into
diversity,
training
and
we
talked
to
a
number
of
consultants
embedded
them
in
order
for
the
board
of
the
node
Foundation
and
potential
other
leaders
of
the
node
foundation
to
set
the
bar.
A
The
next
one
is
peer
mediation,
so
many
conflicts
in
the
communities
are
members
facing
with
faced
with
a
lack
of
perspectives
as
much.
It
is
folks
who
are
not
educated
in
managing
a
resolving
conflict.
Peer
mediation
documents
provided
as
resources
to
encourage
healthier
communication
for
collaboration,
can
help
alleviate
much
of
the
stress
we
see
in
our
github
and
chat
channels.
A
The
power
of
peers,
resolving
conflict
cannot
be
underestimated,
providing
workshops
alongside
other
community
events
has
been
requested
and
it
would
be
a
great
model
to
set
forth
in
open
source
and
even
in
most
workplaces
the
next.
The
next
strategy
would
be
to
look
at
our
communication
channels
as
they
exist,
so
we
have
to
ensure
that
we
have
a
trusted
moderated
space.
We
can
send
new
folks
to
and
currently
when
I
am
asked
for
anyone
within
our
group.
That's
asked
where
to
go.
A
A
Irc
has
been
around
for
a
really
long
time
if
you've
ever
participated
in
the
hashtag
nodejs
channel.
You
know
that
there
are
a
lot
of
people
in
it,
so
that
the
proposal
there
is
to
clean
it
up.
So
we
know
that
our
community
exists
and
knows
to
go
to
IRC,
but
we
need
to
be
able
to
do
things
like
list
them
out
on
node.js,
org
and
part
of
listing
it
out
on,
though
JSTOR
is
that
we
have
to
feel
that
the
code
of
conduct
is
being
applied
there.
A
Joined
with
our
code
of
conduct,
and
then
we
would
also
need,
as
part
of
those
channels
being
listed
out,
we
would
need
them
to
agree
to
applying
those
rules
to
their
channels,
so
we
have
to
make
sure
that
those
faces
are
actually
being
protected
by
the
code
of
conduct.
That
is,
that
is
listed
there
and
there
are.
A
There
are
problems
around
that
as
well,
so
we
would
want
to
make
sure
that
logging
is
also
happening
for
those
channels,
so
that,
if
somebody
does
report
that
the
folks
who
are
moderating
will
have
the
means
to
exercise
on
that,
the
other
option
here
is
slack
and
they're
already
also
existing
slack
channels.
The
problem
is
discoverability
there,
so
it's
really
hard
to
find
those,
and
sometimes
they're
private
and
that's
fine
slack
can
be
really
welcoming
I've
seen
a
lot
of
communities
that
never
felt
comfortable
existing
in
IRC
joining
slack
and
having
a
really
rapid
growth.
A
A
The
flipside
of
that
is
that
it
also
allows
you
to
know
who's
signing
up
so
something
like
IRC.
You
can
cloak,
although
I'm
sure
people
can
tell
me
ways
around
this
later
and
it's
harder
to
track
people
down
when
there's
bad
actors,
so
there's
things
to
look
into
there
and
then
the
another
one
we
have
is-
and
this
is
more
from
the
foundation
side.
But
it's
prioritized
seeking
a
diverse
range
of
candidates
for
both
hiring
and
vendors,
so
we
have
to
lead
in
prioritizing
inclusivity
and
diversity
in
every
facet
of
the
organization.
A
A
Finally,
the
last
strategy
that
I
find
really
exciting
and
means
I
can
do
a
lot
more
in
the
future
and
we
all
can
is
set
reasonable
goals
and
in
order
to
do
that,
we
have
to
have
data.
So
in
order
for
us
to
you
know
increasing
representation
and
demographics
and
backgrounds
that
are
underrepresented
globally,
we
have
to
know
what
is
underrepresented.
We
can't
know
where
we
stand
without
knowing
where
we're
at
so
moving
forward.
A
A
That
said,
all
of
this
is
open
for
discussion.
These
were
the
findings
from
my
investigation
and
there's
a
lot
of
work.
That
needs
to
be
done,
so
we
still
need
input
and
it's
going
to
be
published
and
all
of
the
implementation
details
still
need
to
be
put
put
to
forth.
So
we're
gonna
be
talking
about
this
during
collaboration
summit
during
the
inclusivity,
working
groups,
session
and
I
hope
you'll
join
me
there.
Why
am
I
explaining
all
of
this?
A
All
of
this
is
because
we
need
help
and
so
much
help,
there's
so
much
work
for
the
node
project
and
it
benefits
us
all.
It's
really
awesome
to
get
to
celebrate
where
we're
at
so
far
and
in
order
to
welcome
more
people
in
we've
got
to
clean
up
what
we've
got
so
to
say.
We
feel
grateful
for
the
things
that
we
do
have
you
know
that's
great.
It
also
means
we're
aware
of
our
blessings.
A
It
does
not
discount
the
problems
that
we're
facing,
but
we
do
want
to
say
thank
you
to
the
working
groups
and
core
and
node
school
and
node
bots
and
know
together
and
all
these
community
conferences
in
the
community
for
the
hard
work
that
they're
doing
and
they're
learning
through
these
experiences.
What
works
and
what
doesn't
a
community
can
mean
the
difference
for
maintainer,
ship
stabilization
and
new
innovation
and,
like
so
many
an
open
source
I
find
myself
needing.
A
You
know
help
for
all
of
the
things
that
I
can
dream
up,
so
we're
doing
a
lot
of
work.
Alright,
we're
each
doing
a
lot
of
work
for
one
person.
There's
got
to
be
room
to
ask
for
help
and
that's
where
I
were
doing
that
now
we
must
create
the
space
for
others
to
help
so
that
user
group
in
Oregon
it's
grown.
It's
changed,
there's
other
awesome,
JavaScript
and
node
meetups
happening
to
the
organizers,
went
on
to
work
at
NPM
at
node
Foundation
at
New
Relic
at
the
Apple.
A
You
know
I
totally
messed,
that
up
the
Fruit
Company
or
is
that
sorry
I
shouldn't
have
said
that
many
of
our
attendees
were
finally
able
to
also
get
jobs
in
node
for
the
first
time,
and
that
was
that
was
really
exciting
for
them
and
it's
been
really
empowering
and
that's
just
one
story.
You
know
it's
been
repeated
across
the
world.
I
sat
on
conference
talk
panels
where
every
single
person
had
had
their
start
or
early
awesome
experiences
with
node
bots
and
it
had
kept
us
going.
A
We
ran
our
first
international
node
bots
day
in
Portland,
and
we
saw
how
people
how
excited
people
got
about
hanging
on
Hardware
long
before
they
knew
that
that
was
even
a
thing.
In
JavaScript
we
ran
countless
node
schools,
talk
nights
and
hack
nights,
people
joked
about
cat
herding,
and
you
know
it
was
stressful,
but
it
was
also
always
fun
and
I
wouldn't
be
here
today
on
stage
if
it
wasn't
for
Ben,
Acker
and
I
wouldn't
have
this
job.
A
If
someone
having
haven't
given
me
its
space
to
help
and
support
it,
a
super
friendly
environment
for
all
of
us
to
grow
in
so
I
look
forward
to
growing
the
community
that
was
so
welcoming
to
me.
I
hope
I
can
provide
the
same
southern
welcome
that
been
afforded
me
and
I
think
that's
a
great
legacy
to
protect
and
grow.
Thank
you.