►
From YouTube: Node.js Foundation Board Panel
Description
Mikeal Rogers, Community Manager; Danese Cooper, Paypal; Bill Fine, Joyent; Todd Moore, IBM; Charlie Robbins, GoDaddy; Gianugo Rabellno, Microsoft; Rich Sharples, Red Hat
A
B
I
think
I've
probably
been
using
node
more
than
anyone
else
on
the
board,
no
offense.
In
fact,
when
I
met
you
for
the
first
time
or
in
like
early
2010
and
then
just
went
deep
and
I've
been
doing
it
ever
since,
and
we
use
it
a
lot
at
godaddy
which
I'll
actually
be
talking
about
right
after
this
panel.
A
C
You're
gonna
hear
this
over
and
over
again,
but
basically
michael
collared
me
at
bootcamp
a
couple
years
ago
to
talk
about
something
that
was
happening
in
that
node
in
the
larger
JavaScript
community.
He
was
worried
about,
but
I've
been
full-time
open-source
activist
for
going
on
19
years
now
and
note
is
a
great
project.
I'm,
it's
got
all
the
earmarks
of
greatness,
so
I'm
really
happy
to
be
involved
and
paypal
uses
node
very
extensively
for
friending
and
even
up
into
the
middleware
part
of
our
stack
great.
A
D
I
joined
the
foundation
sure
what
I'm
actually
very
proud
to
say
that
I
was
part
of
the
original
team,
two
started
playing
with
node
and
that
was
very
early
2011.
So
the
first
effort
in
porting
node
to
windows,
building
live
EV
and
the
like,
so
it's
been
a
few
years,
are
following
node
in
all
its
successful
path.
A
Ok,
so
Scott
Hammond
is
the
the
CEO
of
joint
he's
on
the
board
of
directors,
representing
giant
he's
also
the
vice
chairperson,
but
he
unfortunately
had
to
leave
last
night
sad,
but
we're
fortunate
enough
here
to
have
bill.
Fine
who's,
the
head
of
product
and
marketing
at
joint
and
he's
also,
actually,
the
the
chairperson
of
the
Marketing
Committee
in
the
node.js
foundation,
so
build.
Let
you
talk
a
bit
about
your
history
with
node
and
with
the
foundation
yeah.
E
A
F
Yeah
I'm,
probably
the
opposite
of
the
spectrum
from
Charlie
I'm,
probably
the
you
know
it
been
involved.
In
note,
the
least
my
kind
of
first
foray
was
about
three
years
ago,
as
we
were
looking
to
acquire
a
mobile
backend
as
a
service.
We
ultimately
quiet,
feed
Henry
you've
been
using
node
for
a
lot
longer.
My
background
is,
you
know,
for
last
16,
17
years,
yeah,
really
around
Java
middleware
and
open
source
and
building
businesses
around
the
technology.
So
yeah
pretty
excited
to
be
here.
A
C
We
were
laughing
about
that
earlier,
so
Geneva
and
I
both
been
involved
in
Apache
for
a
very
long
time
and
some
of
the
patterns
of
the
way
the
node
foundation
works
come
from
there,
and
one
of
our
we
feel
like
part
of
our
job
is
to
help
the
other
board
members
understand
we
do
practically
nothing
because
there's
a
very
strong
technical
committee
in
this
community.
Our
job
is
to
help
them
as
much
as
possible
by
providing
services
they
asked
for
and
generally
getting
out
of
the
way
of
the
technical
development
direction
of
node.
D
Absolutely
you
typically
see
boards
doing
three
types
of
job:
they
set
strategies
and
directions,
they
provide
oversight
and
they
are
sort
of
a
last
recourse.
If
something
goes
wrong,
we
can
and
will
do
the
last
two
to
an
extent,
but
only
as
an
exception.
We
definitely
don't
want
to
get
involved
with
the
first
one
strategy,
direction
of
node
and
other
projects
they
may
come
into.
The
foundation
belong
to
those
projects.
This
is
not
something
we
have
any
plans
to
influence
and.
A
B
Think
it's
been
a
great
year.
We're
talking
about
this
on,
Monday
is
being
I,
think
it's
been
fantastic
for
six
months.
2016
is
going
to
be
really
a
growth
year,
I
think
sort
of
we
got
it
together.
Convergys
happened
and
now
the
tsc
is
really
driving
forward
and
there's
a
lot
of
big
challenges
that
are
coming
down,
not
just
for
node,
but
for
the
language
right
like
how
is
es6
gonna
play
a
role
and
I'm
excited
to
see
what
they
come
up
with.
A
F
G
F
Know
I
think
the
the
board
has
to
really
take
the
long
view
here.
You
know
tech
technology.
I
know
it's
being
in
this
conference.
Super
exciting
lots
of
change,
lots
of
dynamism,
but
you
know
when
you
think
about
it:
technology
really
does
move.
A
glacial
pace
is
in
terms
of
your
broad
trends.
So
I
think
you
know
we
really
do
have
to.
You
know,
look
at
the
very
very
long
term
over
over
decades.
Here,
you
think
of
ecosystems.
You
know
Apache
around
jar
openjdk.
F
E
So
I
can
answer
from
a
slightly
different
perspective.
So,
as
Michael
said,
I
also
said:
I
chair
the
the
Marketing
Committee,
which
is
a
subcommittee
under
the
board,
and
I
think
that
the
role
that
the
Marketing
Committee
can
play,
as
obviously
is
not
technical,
but
you
know
how
do
we
bring
together
the
community
in
different
ways
like
this
event,
for
example,
and
other
events
that
we
might
run
like
this
going
forward?
E
You
know
how
do
we
equip
people
with
kinds
of
tools
of
note
that
they
need
not
the
technical
tools,
but
maybe
the
kinds
of
case
studies
that
they
might
use
to
advocate
for
broader
adoption
of
node
within
their
own
enterprisers,
or
things
like
that
sort
of
the
non
technical
components
that
bring
to
the
community
together
and
help
grow.
Note
and
you
accelerate
the
adoption
of
know.
So
those
are
some
of
the
things
that
we're
focused
on
from
the
marketing
committee's
perspective.
A
C
Actually,
if
you
guys
listen
carefully,
you
don't
have
to
come
to
my
keynote
cuz.
There's
the
whole
call
out
about
this,
but
one
of
the
things
that
I
I
got
interested
in,
advocating
for,
but
even
before
the
foundation
was
formally
formed,
was
more
community
involvement.
The
the
bylaws
of
the
foundation
as
written
were
about
big
companies
that
pay
to
play,
and
that's
important.
You
want
to
raise
money
because
some
of
the
stuff
that
we
need
to
do
for
node
is
going
to
cost
money,
and
it's
good
to
have.
C
You
know
resources,
but
I
don't
want
to
get
us
too
far
away
from
the
original
ownership
of
the
community
and
going
forward
and
so
making
sure
that
the
bylaws
were
modified
so
that
members
could
be
voted
in
from
the
community
without
spending
any
money.
Just
because
of
your
your
good
actions
and
your
attachment
to
the
project
is
really
important
for
me,
and
so
later
this
year
you
will
be
looking
forward
to
the
first
election
that
we
hold.
The
reason
we
haven't
done.
C
It
immediately
is:
first,
we
have
to
build
a
membership,
so
Michael
made
an
announcement
a
couple
of
months
ago.
Now
that
that
was
a
starting
thing
and
we
got
an
initial
flurry
of
the
sort
of
core
code
contributors,
but
to
really
be
representative
of
node,
we
need
to
have
membership.
You
know
that
that
includes
users
includes
people
who
are
just
hoping
to
get
involved
some
newbies
here
and
there
you
know
it
and
so
yeah.
My
talk
will
have
a
URL
that
you
can
go
directly
to
to
become
a
member.
C
If
you're
already
a
committer,
it
doesn't
cost
anything.
If
your
student,
it
only
costs
twenty-five
dollars
that
most
it
could
cost.
You
is
a
hundred
dollars,
and
that
is
a
really
good
way
to
get
involved
and
do
it
soon.
You
do
not
have
to
be
a
member
to
join
one
of
the
working
groups
and
there
are
lots
of
them.
There
are
lots
of
local
language
groups,
because
it's
a
global
project.
C
So
if
your
first
language
is
not
English,
there's
probably
a
bunch
of
other
people
that
speak
what
you
speak
in
one
of
those
groups
and
that's
a
great
place
to
go
at
the
classic
way
to
get
involved
in
an
open
source
project
always
is
to
make
a
bug
fix.
Get
work
get
working
on
documentation
there
working
groups
for
all
of
this
stuff,
so
this
is
meant
to
be
owned
by
the
community,
and
we
know
that
this
model
works
because
Apache
has
been
cooking
along
for
a
long
time
now
and
using
a
dissimilar
kind
of
involvement.
C
D
D
D
F
Can
I
just
reiterate:
I
mean
there
are
lots
of
asian
get
involved
as
then
he
said,
you
know,
don't
feel
intimidated
that
you've
gotta
be
a
dive
straight
in
and
start
committing
europe
up
in
to
fix
some
of
the
core
projects.
You
know
documentation
filing
bugs
internationalization
localization.
These
are
all
super
super
important.
You
don't
have
to
have
to
commit
Yeah
right
up
front.
You
can,
you
know,
get
involved
gradually
at
your
own
pace,
with
whatever
suits
your
your
your
tiny
available,
your
skills,
so
many
many
ways
to
get
involved.
Just.
E
Stack
or
that
I
would
say
even
taking
that
one
step
farther
beyond
committing
documentation
these
kinds
of
things.
One
thing
that
we're
actively
looking
for
our
stories
stories
of
success,
case
studies,
user
stories,
things
that
people
that
maybe
are
coming
behind
you
having
to
make
cases
within
their
own
organization
for
bringing
node
into
their
enterprise
are
considering
it
as
an
option.
We
want
to
tell
those
stories
or
the
success
stories.
C
Project
is
largely
run
through
github
and
michael
was
telling
me
earlier
that
there's
now
a
bit
of
work
called
help.
There's
that
there's
a
repository
where
you
can
pose
a
question
if
you're
not
sure
where
to
start
and
there's
something
you
want
to
get
done
and
there's
a
commitment
that
you'll
get
an
answer
there.
The
people
have
been
sending
those
kinds
of
questions
through
to
the
core,
Technical
Committee
and
they're
being
generous
to
answer
them,
but
really
we'd.
C
Rather
they
wrote
code,
you
know
so,
but
we
understand
it's
a
big
world
and
if
you're
new
to
it,
it's
a
little
daunting
and
that's
probably
the
best
first
place
to
go
and
we're
going
to
work
on
better
resources
to
on
the
website
to
help
people
understand.
You
know
where
to
dive
in
how'd
it
where
to
take
a
problem.
But
but
right
now
you
can.
You
can
put
in
a
request
at
health
I
under
github
repository,
and
somebody
will
answer
to
more.
D
Suggestions
if
I
may,
the
remit
of
the
foundation
is
on
kno
jes
core
and
a
few
projects
that
will
come,
but
notice
is
really
a
platform
and
all
those
modules
that
are
out
there
so
contributing
to
an
NPM
module
to
the
NPM
registry
means
enriching
the
new
ecosystem
as
a
whole.
So
it's
important,
don't
think
only
about
I
cannot
really
contribute
to
the
node
core.
It's
it's
outside
of
my
realms
of
expertise.
There's
plenty
of
modules
out
there
that
definitely
could
use
your
help.
The
other
part
is
everyone
is
an
evangelist
in
your
local
communities.
D
A
Okay,
so
a
lot
of
people
had
questions
about
how
the
membership
works
on
the
on
the
corporate
side.
You
know
you
have
these
levels
and
you
have
representation
and
it
gets
a
little
bit
confusing
for
an
outsider,
Charlie
you're
you're,
the
gold
rep.
Could
you
tell
me
a
little
bit
about
how
that
process
works
and
yeah.
B
A
B
Sure
ya
is
like
a
prior
art
type
thing
yeah,
so
there
are
two
levels:
well,
three,
sorry
to
that.
There
are
elections
for
my
apologies
to
levels
of
their
elections
for
silver
and
gold.
Each
one
of
those
levels
gets
to
hold
an
election
among
its
members
and
those
folks,
those
companies
forever.
The
voting
member
is
that's
appointed
by
the
company,
gets
to
cast
a
vote
and
then
I
think
it's
just
a
simple
majority.
I,
don't
actually
know
what
happens
to
be
event
of
a
tie.
It.
C
C
A
A
And
with
that
in
mind,
I
mean
there
is
a
big
separation
here
between
you
know
the
money
coming
in
and
have
that
gets
allocated
and
the
technical
resources
there's
a
bit
of
a
wall
there.
Does
anybody
want
to
speak,
you
know
specifically
to
that
wall
and
where
the
division
of
responsibilities
are
and
how
that
kind
of
charter
works.
Well,.
C
F
You
covered
it
pretty
well,
but
you
know
it's
it's.
It's
yeah,
it's
remote!
This
is
this.
Is
your
community?
The
group
of
people
here
do
not
have
a
huge
amount
of
influence
on
on
what
happens
right
at
you
guys
it's
its
membership
through
the
Tet,
various
technical
groups
and
technical
committees.
We
don't
we
don't
drive
the
technology
where
I
mean
largely
an
administrative
body.
So
just
bear
that
in
mind.
C
Like
yeah,
sometimes
the
technical
committee
asks
us
questions.
We
are
board,
proceedings
are
public,
and,
and
so
you
can
go,
see,
questions
that
we've
been
asked.
We
were
asked
to
initially
clarify
the
trademark
policy.
A
little
bit.
We
get
asked
legal
questions
once
in
a
while
part
of
the
great
thing
about
being
part
of
the
Linux
Foundation.
Is
we
share
resources
with
all
the
other
Linux
Foundation
foundations?
A
D
That,
in
doubt,
whatever
we
talking
about
is
our
responsibility
of
the
technical
committee
yeah
we're
weird.
We
are
working
on
a
very,
very,
very
adorable
white
list
of
a
few
items
that
come
to
us
and
even
those
actually
come
to
us
in
a
predigested
fashion,
so
to
speak
so
so
that
our
meeting,
mostly
about
seeking
formal
approvals,
doing
roll
calls
and
then
started
any.
C
D
E
There
as
its
delegated
to
the
Marketing
Committee,
there's,
certainly
also
other
things
that
we're
doing
you
know
outside
the
technical
realm
like,
for
example,
working
with
the
Linux
Foundation
to
organize
this
conference
conferences
that
we
might
have
in
a
future
conferences
that
we
have
might
have
more
locally
initiatives
that
we
might
engage
into.
To
tell
the
story
of
note
more
broadly
in
the
community,
to,
as
I
said
earlier,
help
accelerate
adoption
and
growth
of
the
community.
C
We're
also
we're
also
an
escalation
point.
It's
not.
It
has
happened
that
people
in
the
community
have
written
to
me
to
attack
question
about
something
they
were
wondering
about.
If
it's
a
technical
question,
I
probably
am
not
going
to
be
able
to
answer
it
and
I'll
be
sending
it
to
the
technical
committee,
but
since
this
is
a
new
foundation,
understanding
the
roles
and
in
if
something
is
bothering
somebody
getting
to
the
bottom
of
that
quickly
and
apparently
is
something
that
we
very
much
do
own,
and-
and
so
you
know,
I
would
engage.
E
So
the
market
is
a
subcommittee
of
the
that
axis
got
a
representative
from
different
members
and
we
get
together
every
other
week
and
we
talk
about
you
know
what
should
we
be
doing
to
help
note
from
a
marketing
and
awareness
perspective
from
a
building
the
community
perspective
outside
the
technical
room?
There's
a
certain
budget
that
comes
to
the
marketing
committee,
that's
generated
as
a
percentage
of
the
membership
dues,
and
then
we
get
together
and
we
try
to
talk
to
different
people
in
the
community.
A
A
C
Really
looking
forward
to
getting
community
members
on
the
board
and
getting
the
board
used
to
the
idea
that
the
community
has
a
voice,
the
technical
committee
has
always
been
on
the
board
by
design,
but
their
concerns
tend
to
be
technical
and
I
feel
like
we
need
to
have
community
involvement
at
all
levels.
So,
looking
forward
to
that
election,
a
lot
right.
D
To
me,
objective
number
one
for
every
open
source
community
should
be
finding
more
contributors.
Much
like
companies
are
about
finding
customers,
open
source
communities
are
about
finding
new
contributors,
ensuring
long-term
sustainability
and
ensuring
diverse
driving
projects.
I'm
hoping
this
would
be
a
key
focus
in
2016
looks
like
we
reached
a
point
where,
from
a
technical
standpoint,
there
are
challenges
ahead,
but
there
is
a
vision.
D
So
we
need
to
execute
on
that
vision
and,
at
the
same
time,
make
sure
that
we
stay
as
inclusive
as
we
can
and
we
involve
as
many
people
as
we
can,
both
within
node
and
around
node.
So
again,
it's
not
just
about
core,
don't
think
of
it
as
a
spectators
game
for
way.
We
only
get
to
see
people
who
are
super
experts
in
managing
events.
Loop,
there's
much
more
to
it.
E
B
E
That
I'm
excited
about
our
focus
on
is
the
next
million
or
the
next
two
million.
How
do
we
engage
them?
How
do
we
get
them
excited
about
note
in
this
community?
How
do
we
bring
them
into
the
community?
How
do
we
make
it
easier
for
them
than
it
was
for
the
first
three
million?
So
that's
something
that
I
think
you
know
certainly
from
a
marketing
committee
that
we're
focused
on
I'm
also
interested
in
expanding
this
notion
of
community
beyond
events
like
this
to
something
we
call
note
on
the
road.
E
So
it's
something
that
we've
done
in
the
past,
looking
to
do
that
more
or
I
sort
of
helping
the
local
meetup
groups
by
bringing
maybe
some
of
the
tsc
members,
or
you
certainly
users
and
different
locales-
to
create
some
of
these
places
for
people
to
go
to
learn,
not
to
get
to
know
the
folks
in
their
own
local
communities
that
are
working
on
node.
So
that's
an
area
of
focus
for
me,
certainly
going
forward
next
year
and.
F
I'm,
finally,
you
know
so
a
red
hat,
open
source
collaboration
is
in
our
DNA,
so
I'm
really
looking
forward
to
too
many
more
of
my
colleagues
over
the
next
year.
Getting
involved,
you
know
technically
and
wherever
they
can
to
help.
You
know,
keep
pushing
note
forward
and
you
know
bring
bring
our
20
plus
years
of
open-source
collaboration
experience
to
bear
to
keep
driving
note
forward.
A
Okay
and
I'm,
going
to
I'm
going
to
come
the
other
direction
this
time
as
I
have
something
first,
the
movie
you
know
wherever
I
go
in
that
direction.
Sorry
Riss
riffing
to
go
twice,
but
so
we've
been
talking
a
lot
about
supporting
the
community
and
sort
of
staying
staying
out
of
the
way,
but
in
a
supportive
role.
What's
something
that
you've
been
very
impressed
with
this
community,
in
particular,
if
you're,
comparing
it
to
other
communities
and
other
projects,
what's
something
that's
gone
really
well.
A
F
Again,
I'm
pretty
new
here,
I'm
still
still
very
much
observing.
This
is
actually
the
first
note
conference
I've
been
to
you
know.
One
thing:
that's
that's
amazing.
You
know
this
is
a
relatively
small.
You
know
gathering
and
I'm
sure
it's
going
to
be
double
sized
next
year
and
triple
year
after,
but
there's
there's
just
a
huge
amount
of
energy
and
excitement
lots
of
people
talking
together.
F
You
know
one
thing:
I've
seen
it
many
other
conferences,
you
get
little
clumps
of
people,
lots
of
people
not
talking
to
each
other,
but
every
time
I
walk
out
into
you
know
the
the
hallways
here
you
know,
there's
just
a
huge
amount
of
discussion.
Impassioned
discussion-
that's
that's
great!
That's
just
the
energy
level
at
this
conference
is
as
be
as
good
as
anywhere
I've
encountered.
Any
other
conference.
I
got
a
lot
of
tech
conferences,
so
trust
me
this
is
this
is
some
good
energy
here.
E
One
thing:
that's
that
certainly
struck
me:
is
the
community
tackle
on
that.
So
when
I
really
became
familiar
with,
node
was
a
year
and
a
half
year
ago
right
and
it
was
a
different
moment,
a
sort
of
a
crucial
moment
in
the
history
of
note.
You
know
giant
had
been
the
corporate
sponsor
Stewart
for
known
for
going
on
six
years
and
clearly
began
to
grow.
You
know
the
community
had
grown
beyond
the
capacity
for
joy
to
manage
it
as
a
single
sort
of
benevolent
dictator
model.
E
We
saw
the
fork
friction
that
a
move,
the
you
know
that
was
in
the
community
that
really
grew
out
of
passion
and
I
say
that
all
to
say
the
thing
that
that
has
amazed
me
the
most
is
that
the
the
ability
of
the
community
to
come
back
together,
so
I
know
at
Giants.
Our
sort
of
mantra
became
what's
best
for
node
and
that's
how
we
that's
how
we
thought
about
what
really
was
a
hard
decision
to?
E
Let
something
so
wildly
popular
go
right
to
a
certain
extent,
and
then
I
saw
that
same
attitude
among
really
everyone
right
as
they
looked
at.
What
did
they
want
to
do
going
forward
sort
of
what
was
best
for
the
broader
community
and
I?
Think
that's
pretty
rare.
You
don't
see
that
a
lot
in
these
kinds
of
communities,
so
that's
that's.
What
I've
been
most
impressed
with
is
really
the
that
characteristic
of
the
community
itself.
D
Now
so
to
me,
I
have
been
23
years
now
in
open
source,
so
that
that's
quite
a
long
time.
The
one
thing
that
I
find
very
refreshing
about
note
about
this
conference
about
the
community
in
general
is
that
it
brings
me
back
to
that
hacking,
mindset
and
culture
that
we
used
to
have
and
nineteen
ninety
nineteen,
oh
seven
I
mean
those
were
the
years
where
there
was
a
lot
of
creativity.
D
Now
you
show
up
with
a
lot
of
open
source
events,
and
you
see
a
lot
of
users,
a
lot
of
enterprises
and
things
to
seem
to
be
moving
at
a
slower
pace
in
many
places,
but
here
and
you
see
people
doing
genuine
hacking
of
of
stuff
that
you
wouldn't
have
imagined.
This
is
one
of
the
most
creative
communities
around
I
think
that
thoroughly
the
language,
the
architecture
it
lands
very
well
to
that,
and
it's
it's
really
really
really
a
welcome
way
for
me
to
do.
Engage
with
a
community
yeah.
C
I
have
to
say,
and
of
course,
I'm
going
to
say
this
because
I'm
the
girl,
the
diversity
of
this
community,
is
really
inspiring.
I
have
been
in
an
awful
lot
of
places
where
I
was
the
only
woman
and
that's
just
not
true
in
this
community
there's
room
for
everybody,
it's
a
very
big,
tent
and-
and
that
is
super
exciting
for
me,
because
back
in
the
day,
as
he's
discussing,
everybody
was
super
juiced
and
moving
forward.
C
But
there
were
very
few
women
in
that
super
juiced
group
and
and
to
walk
into
a
conference
full
of
every
stripe
of
people.
You
can
imagine,
but
all
really
juiced
node
and
doing
super
interesting
things
with
it.
The
demos
are
always
very,
very
exciting
at
one
of
the
core
developer
meetups
so
so
anyway.
I
think
that
diversity
is
going
to
be
a
huge
strength
of
this
community,
it's
sort
of
where
open
source
needs
to
go
anyway.
I
would
say
that
notice
leading
that.
B
G
B
B
I
know
like
every
every
single
week:
rogue
would
break
something
and
then
you'd
have
to
rewrite
all
your
modules,
and
then
we
move
to
NPM
one,
and
so
you
stopped
having
global
modules
and
then
now,
in
the
last
six
months,
npm
three
completely
changes
most
directory
trees.
You
have
a
ton
of
new
language
features
that
in
many
other
languages,
has
totally
fractured
communities
and
they
look
at
Python
3
and
those
types
of
things,
whereas
we're
just
rolling
with
the
punches
and
like
moving
forward.
B
A
Great
yeah
I'll
just
put
this
to
the
whole
panel.
Anybody
who
wants
to
chime
in
but
the
the
project
has
gone
through
a
lot
of
huge
changes
lately
and
it
also
uses
a
lot
of
more
modern
tools.
At
the
same
time
has
taken
a
lot
of
influence
from
prior
generations,
but
is
there
anything
that
you
think
that
future
open
source
projects
are
going
to
learn
from
node
or
changes
that
we've
been
able
to
institute?
That
is
going
to
direct
a
kind
of
future
of
open
source.
B
A
C
The
ideas
they
become
top-level
projects
over
time,
they're
sitting
in
incubation
for
a
few
reasons,
one
typically
as
getting
the
intellectual
property
rights
cleared
up
so
that
the
foundation
has
clear
ownership
over
that
stuff
for
the
purposes
of
enforcing
licenses
and
things.
But
another
one
is
is
making
sure
that
the
people
understand
how
this
community
likes
to
work
and
I.
Think
Michael
and
the
I
ojs
team
did
an
amazing
job
documenting
how
this
community
likes
to
work
may
be
fresher
than
the
Apache
did
this.
C
C
B
C
The
top-level
projects
at
Apache
are
called
out.
This
Apache
has
a
regular
reporting
requirement,
we're
still
working
this
out
for
node.
By
the
way
we've
we've
agreed
to
do
an
incubator.
We've
borrowed
a
lot
of
stuff
from
Apache,
but
until
we've
done
it
a
couple
times,
we
won't
really
know
what
works
for
this
community.
Interestingly
enough,
the
state
of
the
Apache
Incubator
at
this
moment
is
sort
of
interesting
it
was,
it
was
created.
C
Originally,
there
was
no
incubator
and
projects
would
come
in
and
they
were
immediately
tough
level
projects
and,
as
the
Apache
brand
became
valuable,
we
saw
people
dumping
projects
in
order
to
get
a
press
release
out,
saying
that
they
now
with
Apache
and
then
never
showing
up.
So
the
big
emphasis
of
the
Apache
Incubator
is:
you
must
build
a
community
and
it
has
to
be
a
diverse
community.
C
You
have
to
produce
a
release
as
an
incubator,
and
you
have
to
be
able
to
show
that
you've
got
at
least
three
organizations
contributing
to
that
release
so
that
in
our
history
of
at
Apache,
when
a
major
contributor
decided
to
leave
a
project,
often
the
project
would
become
a
ghost
town,
so
we're
trying
to
make
things
a
little
more
fault,
tolerant
and
again
create
participation
across
the
community.
So
you
don't
get
one
company
pushing
an
initiative
and
then
running
away
from
it
or
you
know
you
want
everybody
to
work
together.
C
The
model
that
Apache
created
I
like
to
put
a
slide
up
about
dinosaurs
around
a
watering
hole,
they're
angry
dinosaurs.
They
want
to
eat
each
other.
So
this
is
the
big
companies
that
work
around
node,
but
because
they
see
that
there's
a
broader
goal:
getting
water
they're
willing
to
be
peaceful,
at
least
for
this
work,
and
that's
that's
sort
of
what
we're
going
for
in
every
single
incubator.
Let's
make
sure
that
everybody's
working
together
on
this
so
kind.
F
Of
the
way,
in
a
little
bit,
yeah
I
applaud
the
foundation
for
making
the
decision
to
really
leverage
the
Linux
Foundation
yeah.
Building
their
kind
of
year
structure
for
a
large-scale,
open,
collaborative
consensus,
driven
development
is
actually
really
really
hard.
I
mean
trust
me,
it's
not
easy,
but
the
node
foundation
is
leveraging
your
links,
foundation,
apache,
others
that
come
before
it
and
hit
these
problems.
F
So
we
actually
focus
on
on
the
task
at
hand
which
is
about
building
great
community
building
great
technology
and
not
have
to
worry
too
much
about
structuring
licenses,
so
that
was
that
was
a
very,
very
smart
move
that
doesn't
always
happen
with
with
new
open
source
projects
and
I.
Think
yet
many
of
the
failures
failure
you
see
with
open
source
projects,
it's
rarely
the
technology,
it's
really
the
adoption.
It's
often
the
governance
and
the
structure
that
rakes
it.
So
I
think
that's
that
was
a
great
move.
E
One
thing
that
I
think
node
has
the
possibility
to
be
is
a
model
for
balancing
the
tension
between
innovation
and
stability
and
I.
Think
that
one
of
the
things
this
made
not
so
popular
is
its
ability
to
bring
speed
and
speed
to
innovation
within
enterprises,
and
you
know,
I
think,
that
there's
a
model
been
put
forth
by
the
board
in
the
foundation.
Now
that
gives
us
a
way
to
balance
those
you
know,
as
as
node
grows
up
in
some
ways
right
and
and
needs
to
begin
to
serve
needs
and
areas
of
stability.
E
F
Work
with
other
open
source
communities,
your
two
examples,
there's
the
you
know
that
the
long-term
support
initiative
and
that
that's
it
that's
a
very
sophisticated,
very,
very
mature
delivery
model.
It
took
other
open
source
communities
literally
decades
to
get
to
get
to
that
level
of
maturity,
and
here
in
no
job
late
in
the
first
five
years,
was
pretty
amazing
and
also
the
reaction
to
to
security.
Embargoed
security
fixes
again
very
very
tough
process,
coordinating
lots
of
people
you
know,
and
within
the
first
five
years
the
no
GS
foundation
is
able
to
do
that.
F
You
know
without
having
to
your
break
into
too
much
work,
I'm
sure
there
was
lots
of
sweat
and
sweat
blood
and
tears
over
that.
But
you
know
most
people
wouldn't
see
that.
So
you
know
I
thinking,
you
know
credit
to
those
that
made
that
choice
of
leveraging
in
true
open-source
fashion
you
know
building
on
the
shoulders
of
giants.
So
that's
great.
D
But
we
don't
think
these
considerations
I
mean
and
considering
the
state
of
the
community
and
the
fact
that
again,
it
seems
to
be
a
very
creative,
very
active,
very
vibrant
community
I
think
that
this
foundation
has
what
it
takes
to
provide
the
print
for
others
to
follow,
become
a
sort
of
an
Apache
two
point
O.
In
a
way
the
moment,
apache
is
doing
fine,
it's
thriving,
there's
lots
of
projects
over
there.
The
model
that
we're
seeing
here
is
no.
This
slightly
different.
D
Very
fascinating
to
see
and
buy
cherry
picking
some
key
features
from
organizations
like
Apache
by
leveraging
the
logistic
support
of
the
Linux
Foundation
and
by
building
on
the
very,
very,
very
peculiar
community
that
no
Jas
has
in
the
vast
ecosystem.
I
think
that
yeah,
it
is
entirely
possible
that
the
node
foundation
becomes
a
blueprint
for
for
future
projects
that
follow.
A
A
B
Okay,
yeah
I
mean
like
I
sort
of
opened
with
I've,
been
involved
with
nodes
since
2009.
So
really,
since
the
first
six
months
of
the
project
and
the
the
story
of
note
sort
of
follows.
The
story
of
javascript
and
java
script
has
done
exceptionally
well
in
the
last
few
years
and
as
such,
so
as
node,
and
it's
really
hard
to
point
to
any
project
that
really
tackles
the
the
verticals.
That
note
does
right.
I,
remember
the
first
time
where
someone's
like
they're
building
robots
with
JavaScript
folks,
like
that's
happening,
like
a
pay.
B
You
know
now
there's
like
oh
there's
this
IOT
thing.
Oh
yes,
of
course
that's
going
to
be
node
so
seeing
what's
next
and
what
that
what's
next,
for
no
to
be
pretty
interesting
from
the
technical
side.
Obviously
we're
not
involved
with
that,
but
I
just
like
to
have
you
know
my
popcorn
and
my
drink,
ready
to
you
know,
take
up
and
watch
the
movie.
C
I'd
like
to
say
that
everything
we've
been
talking
about
should
be
pretty
transparent
for
people
that
want
to
learn
about
it.
So
if
you
have
interest
in
this,
you
should
be
able
to
find
our
minutes
from
our
board
meetings.
You
should
be
able
to
find
the
statement
about
where
the
next
board
meeting
is
happening.
C
They
happen
virtually
so
you
can
join
too
and-
and
you
should,
you
know,
be
able
to
find
pretty
much
everything
and
if
you
can't,
you
should
definitely
let
us
know
if
something's
not
not
straight
forward
to
you,
because
transparency
is
one
of
the
secrets,
classes
of
open
source
and
we
have
to
work
hard
to
maintain
that
transparency,
even
in
the
longest
standing
open
source
projects.
This
is
a
constant
thing,
because
it's
really
easy
to
have
a
hallway
conversation,
so
at
Apache
we
were
able
to
eventually
institutionalize
the
idea.
C
If
you,
if
we
didn't,
have
a
conversation
and
we
decided
something.
The
last
thing
we
would
say
is:
okay,
who's
going
to
write
the
email,
and
here
it
would
be
who's
going
to
write
the
pull
request.
That
explains
this
to
the
rest
of
the
world,
and
so
the
conversation
can
happen
so
you
know
hold
us
to
that:
hold
hold
the
both
the
board
and
the
technical
committee
to
that
commitment,
because
that's
what
we're
here
for.
D
It
doesn't
really
matter
think
of
it
as
a
platform
that
we
need
to
grow
as
a
platform,
and
the
other
request
is
keep
on
evangelizing
keep
on
going
out
there
and
talk
about
note
find
more
people,
because
again
we
need
more
contributors.
We
need
as
many
as
we
can
get
and
I
hope
that
next
year
we
can
come
back,
and
I
have
another
board
panel
where
hopefully
we
will
be
able
to
say
yeah.
We
did
pretty
much
nothing
this
year,
yeah.
C
E
Well
I
said
earlier,
as
we
were,
making
the
decision
earlier
this
year
to
create
the
node
foundation
and
move
it
into
the
Linux
Foundation
and
step
back
to
a
certain
extent
from
node.
You
know
our
mantra
was
what's
best
for
node
and
that
it
was
easy
for
us
to
say
that,
because
our
company
is
really
built
unknown
right,
so
we
have,
if
you
don't
know
us
work
with.
You
know
a
cloud
provider
and
we
have
a
platform
called
Triton
that
provides
cloud
infrastructure
and
it
is
a
micro
services
architecture.
E
That's
built
on,
though,
just
distributed
across
multiple
data
centers.
So
well,
we
bet
our
company's
future
on
note.
It
is
the
core
fiber
of
the
product
that
we
take
to
market
and
beyond
that,
the
customers
have
come
to
us
to
run
their
applications
on
top
of
our
platform
are
predominantly
note
base
about
half
of
the
workloads
that
run
on
our
platform,
our
node
base.
So
if
you
check
the
news
today
on
your
mobile
device
or
on
your
on
your
browser,
you're
probably
checking
it
on
a
property
that
runs
note
that
runs
on
our
platform.
E
If
you
did
some
holiday
shopping,
when
you
went
back
to
your
room
last
night,
there's
a
good
chance,
you
were
doing
it
on
site
that
runs
node
and
runs
on
our
platform
to
us,
and
our
customers
are,
depending
on
node,
to
grow
and
grow
vibrantly
in
the
future,
and
so,
as
I
look
back
sorta
now,
six
months
later,
I'm
really
excited
about
what
we've
seen
the
kind
of
growth
that's
been
in.
The
community
has
been
phenomenal
just
in
terms
of
the
number
of
contributors,
the
number
of
users
really
excited
about.
F
You
know
the
most
important
people
in
the
room
here
you
guys
right.
You
have
an
important
role
to
play
here.
When
you
get
back
to
work
on
Monday
or
Friday,
you
know,
do
a
quick
blog
post,
you
know
tell
your
your
colleagues,
your
friends,
your
cool
tech
community,
what
you
learn
here
this
week,
what
got
you
excited
and
yeah
come
back
next
year,
but
bring
bring
two
more
people
with
you?
How
about
that
for
a
challenge.