►
From YouTube: Board Panel
Description
Board Panel
A
Welcome
everyone.
Can
you
hear
me
thanks
for
joining
us
here
today?
One
of
the
things
that's
really
well
documented
in
this
community
is
the
history
and
the
lure
of
nodejs
the
project,
its
rapid
growth,
who
started
it
when
it
started.
Everyone
knows
that
story,
I
think.
What's
a
little
less
well
known
is
no
Jas
foundation
and
what
is
the
foundation?
When
did
it
start?
A
So
we've
assembled
some
panelists
here
today,
who
are
representatives
of
the
nodejs
Foundation
Board
of
Directors
I'm
Sarah
Conway
I
work
for
the
Linux
Foundation
working
very
closely
on
the
node.js
foundation
project
and
we're
going
to
invite
our
panelists
today
to
discuss
the
start,
the
rise,
the
purpose
of
the
foundation,
so
with
that
I'd
like
to
just
let
them
I'll,
do
some
brief
introductions.
Charlie.
You
want
to
start
us
off
hi.
B
C
D
E
C
F
A
C
How
can
I
help
this
community
and
he
invited
me
to
a
meeting
which
was
being
convened
by
IDM
in
San
Francisco
a
little
bit
later
and
in
that
meeting
it
was
crystal
clear
to
me,
but
not
so
much.
It
seems
two
representatives
from
join
that
the
community
was
gonna
fork.
If
something
didn't
change
very
clear,
and
so
we
started
working
with
the
new
CEO
of
giant,
he
was
actually
not
or
he'd
just
arrived.
He'd.
C
C
C
C
We
had
just
introduced
him
to
the
Linux
Foundation
when
the
I
ojs
split
happened
and
that
definitely
accelerated
his
consideration
to
get
us
back
to
a
place
where
we
could
heal
that
fork
and
personally,
I'm
really
honored
to
been
part
of
that
heal,
because
it's
a
rare
thing
there
in
a
history
of
open
source.
There
aren't
that
many
high
value
high
velocity
communities
that
fork
and
then
come
back
together,
so
notice
unusual.
C
That
way
and
I'm
really
pleased
that
that
is
working
out
as
well
as
it
has,
and
a
lot
of
that
had
to
do
with
people
like
me
and
Todd.
Helping
helping
joint
understand
how
to
play
in
this
new
arena-
and
you
know,
get
credit
for
being
the
good
guys
and-
and
they
really
were
the
good
guys
I
want
to
stress
that
they
didn't
have
to
make
it
happen.
This
way,
we
could
still
be
dealing
with
a
fork,
but
they
got
it
that
that
was
important
to
fix.
So.
D
So
so
that
was
sort
of
the
impetus
to
start
working
closely
with
giant
as
well
as
bringing
everybody
together
in
a
sort
of
neutral
place
and
just
having
a
frank
dialogue
about
what
the
community
needed
and
why
and
why.
Everybody
felt
the
way
that
they
felt,
and
it
was
folks
like
known
source
and
Microsoft
and
others
who
came
to
this
and
stores.
C
C
D
That
and-
and
so
those
folks,
you
know,
all
had
the
same
goal,
but
they
were,
you
know,
making
a
good
business
out
of
what
was
happening
with
know
that
they
understood
the
importance
of
it.
We
had
seen
the
uptick
in
the
community.
It
was
going
much
beyond
just
being
something
that
people
did
on
their
weekend
tonight.
It
was
happening
as
an
enterprise.
You
know
very
useful
tool,
though
many
of
the
shops
that
you
know
we
talked
to
the
enterprise's
there's
CIOs
didn't
know
that
it
was
going
on.
Actually
it
was
kind
of
hidden.
D
C
Truth
wasn't
because
they
didn't
have
a
product
based
on,
though
they
were
node
consumers,
but
they
weren't
selling
a
node
product.
It
was
hard
for
them
as
a
small
start-up
to
properly
resource
it
for
the
kind
of
growth
that
node
was
seeing
and
and
he
got
that
right
away,
and
you
know
then
figuring
out
taking
the
the
huge
leap
to
Stefan.
Open
source
was
just
a
matter
of
Education
yeah.
D
You
know
we
could
raise
a
number
of
companies
to
come
together
and
form
a
foundation
around
it
so
that
it
had
a
life
of
its
own
for
an
extended
period
of
time,
and
once
we
got
through
that,
that
was
really
the
crucial
part.
And
then
you
know
folks,
like
ourselves,
my
company
and
others
put
resource
in
and
expanded
the
contributor
base
and
that
that
helped
and
then
others
came,
and
you
know
it's
that
sort
of
snowball
effect
and,
of
course,
the
foundation
helped
a
lot.
A
B
The
board
exists
separate
from
the
technical
management
of
the
project,
so
people
here
have
probably
heard
phrases
like
tsc
and
CTC.
They
operate
completely
independently
of
the
board,
so
we
have
no
say
in
what
happens
technically
and
that
was
by
design
because
for
I
don't
know
about
the
rest
of
you,
but
I
don't
really
want
to
make
those
decisions,
I'm
not
as
informed
as
everyone
who's
on
the
tsc.
B
Beyond
that,
there
are
working
groups
underneath
the
tsc
for
various
individual
concerns
from
a
technical
standpoint
like
if
you
want
to
get
involved
in
the
tracing
working
group,
or
you
want
to
get
involved
in
the
post-mortem
working
group.
Those
all
exist
and
those
are
sort
of
self
forming
groups
of
Engineers
that
want
to
work
on
a
particular
problem,
and
then
you
can
make
proposals
or
push
those
back
into
node
and
I.
B
A
E
Mainly
focused
on
the
business
structure
and
the
framework
to
make
sure
that
all
the
technical
groups
can
do
what
they
need
to
do.
You
know
kind
of
I.
Guess
we
smooth
the
way,
and
we
that
we
look
at
things
like
licensing
like
you
know,
understanding
the
finances,
making
sure
that
everything
runs
smoothly
and
events
like
this
can
happen.
So
it
you
know,
I,
guess
just
the
division.
F
So
three
and
a
half
years
ago
we
started
transitioning.
You
know
an
awful
lot
of
our
applications
over
to
node.
You
know,
and
we
just
gotten
through
that
transition-
and
oh
here
comes
a
fork
this.
This
is
not
good,
and
so
it
really
is.
We've
made
a
strategic
investment
in
node
and
in
our
internal
node
expertise
and
building
out
on
it,
and
we
want
it
to
be
as
healthy
as
effective
as
both
stable
and
rapid
moving
we've
just
bite
that
those
sometimes
conflict
as
we
can
so
that
we
can
continue
to
build
on
it.
F
And
that,
honestly,
is
that,
like
a
number
of
us,
including
myself,
have
a
long
history
with
open
source
and
a
strong
foundation
with
a
good
set
of
legal
policies
and
a
good
way
of
managing.
You
know
the
sort
of
responsibilities
of
a
serious
project.
If
we
can
contribute
to
that,
and
so
that
we
can
continue
to
invest
in
use
node,
then
we
win
and
that's
really
that's
brass
tacks.
What
it
comes
down
to
and
then
there's
also
just
the
you
know
we
use
it.
We
care
about
it.
F
A
Great
job,
maybe
you
can-
you
are
involved
with
several
Linux
Foundation
projects
and
several
boards
beyond
node
as
well,
and
you
know
with
so
many
different
types
of
companies
and
involved
how
do
decisions
get
made
at
the
board
level?
Knowing
that
you
have
different
companies
coming
to
the
table,
yeah.
D
Some
boards
are
really
very
interesting
and,
having
been
on
a
number
of
them,
you
see
that
in
general,
their
unanimous
and
their
decisions
in
the
end,
it's
it's
very,
very
rare
that
a
board
gets
together
and
doesn't
actually
come
up
with
a
decision
that
everybody
can
live
with.
I
would
say:
open
source
open.
D
But,
but
actually
boards
in
general
of
business
boards
will
go
out
to
be
that
way
to
the
research
suggests
that
as
well
too.
So
you
know
it's
it's
a
discussion
process.
You
know
we
follow
general
rules
of
order.
We
make
motions,
we
second
them.
We
actually
work
through
a
dialogue
in
a
discussion
about
them
and
and
then
after
you
know,
we
get
to
consensus,
we'll
get
to
a
vote.
D
It's
it's
a
it's
generally,
a
fairly
friendly
process
because
we
all
have
the
same
common
goal
is
to
make
note
great
and
and
just
because
we
represent
companies,
that's
not
how
we
actually
represent
ourselves
on
the
board.
Weird
here
for
the
good
of
the
foundation
right,
that's
our
fiduciary
responsibility
to
the
foundation
so
well,
I
am
from
IBM
the
point
of
view
that
I
bring
is
what
is
best
for
the
community.
What
will
allow
us
to
grow
and
and
and
do
the
best
for
our
members
who
are
here
working
with
us
so.
A
D
C
C
D
C
C
So
most
of
the
foundations
that
the
Linux
Foundation
has
created
are
what
are
called
pay-to-play
boards
and
what
that
means
is
they
use
the
board
participation
as
a
way
to
raise
money
for
the
project
for
all
Linux
Foundation
projects?
Well,
not
all,
but
almost
all
so.
This
one
was
set
up
that
way.
So
companies
at
the
highest
level
of
sponsorship
are
spending
a
quarter
of
a
million
dollars
a
year
to
support
node,
in
addition
to
whatever
engineering
resources,
they're
also
lending
to
the
project,
and
that
puts
us
in
a
you
know
certain
bucket.
C
At
this
point,
in
known
to
be
the
chair
of
the
tsc,
it
means
that
you
have
to
probably
be
paid
to
work
full-time
on
node.
It's
not
a
requirement
of
the
bylaws
but
effectively.
If
you're
going
to
put
that
much
time
in
a
node.
It's
probably
the
case
that
you
work
for
a
company,
and
so
you
represent
a
company
in
your
in
your
presence.
Sort
of
we
wanted
another
way
for
people
who
maybe
don't
live
node
quite
that
fully
to
have
an
opportunity
to
be
part
of
the
board.
C
So
every
year
we
will
have
a
community
election
for
one
seed,
one
voting
seat
on
the
board
from
the
membership
at
large,
and
in
order
to
qualify
for
that,
you
have
to
first
be
a
member
and
there
are
different
member
levels,
but
it
basically
costs
25
bucks
a
year.
It's
pretty
cheap.
It
can
cost
nothing
a
year.
If
that's
a
hardship
for
you.
So
there's
a
way
to
do
that
and
then
there's
a
nomination
period.
You
can
self
nominate.
C
You
can
write
your
platform,
you
know
what
it
is
that
you
hope
to
do,
while
you're
on
the
board
and
there's
an
election
and
the
elected
representative
joins
the
board
for
two
years.
So
every
year
we
vote
for
one
and
we
always
have
two
on
the
board.
The
first
year,
which
was
last
year,
we
actually
voted
for
two,
because
we
were
bootstrapping
and
and
the
two
are
Ashley
Williams
and
and
froze
what
is
froze
his
last
name
very.
C
You
guys
know
for
us
right
so
so,
for
us
was
the
second
place
winner
in
the
election.
Therefore,
he
got
a
one-year
slot,
but
from
now
on,
every
new
elected
person
will
get
two
years
two
full
years
and
that's
because
in
our
experience
it
takes
almost
a
year
to
really
become
an
effective
board
member.
If
you've
never
served
on
a
board
before
you
have
to
get
used
to
the
rhythm
of
it
and
how
things
are
done,
and
you
have
to
figure
out
what
you
want
to
work
on
and
how
you're
going
to
approach
it.
C
It
really,
as
he
says
most
boards
are
not
very
contentious,
they're,
pretty
collaborative,
and
it's
often
the
case.
The
community
elected
people
come
in
with
a
kind
of
contentious
platform
and
we
have
to
sort
of
affection
train
them
to
the
point
where
we
can
all
work
together.
But
we
feel
very
strongly
as
a
board
that
this
is
an
important
component,
especially
for
node,
because
the
community
is
so
vibrant
and
we
really
want
to
grow
people
into
all
levels
of
the
product.
And
so
there
you
go.
That's
the
story:
hey.
A
B
One
of
the
first
things
that
the
tsc
started
working
on
post-merge
was
the
LTS
working
group,
and
so
you
know
I,
don't
know
about
everyone
up
here,
but
you
know
we
run
node
for
next
month
we're
going
to
run
node
6.
So
having
that
stability,
where
you
know
that
the
same
people
are
going
to
be
managing
this
release
cycle
and
that
releases
are
going
to
essentially
marinate
for
up
to
six
to
eight
months
before
you
start
running
them
in
production
is
pretty
great
if
you're
a
large
company
so
great.
F
There
were
people
talking
about
like
oh
well,
that
was
fun,
but
unfortunately
you
know
it's
going
the
way
of
all
the
BS
DS,
not
that
the
bsd
is
there
a
problem:
I
love,
freebsd,
the
other
ones,
it
anyway,
okay
on
node,
and
so
the
the
biggest
positive
thing
is
that
the
community
has
in
fact
really
come
back
together,
and
you
know,
as
Denise
was
saying.
That
is
not
something
that
happens
very
often,
you
know
and
pretty
much
everything
else
that
has
happened
dwarfs
in
comparison
to
the
importance
of
regen,
actually
really
building
a
gelled
community.
F
That
is
progressing
at
a
fabulous
rate.
That
is
doing
great
things
that
has
the
LTS
releases,
which
we
also
are
on
the
exact
same
schedule
and
I
really
believe
that
moving
responsibility.
You
know
the
legal
responsibilities
and
the
policy
responsibility
into
a
foundation
is
what
has
allowed
for
that
to
happen,
and
so
yes,
that's
by
far
the
most
important
thing.
That's
happened
in
the
last
year.
Okay,.
C
There
was
another
important
component
that,
though,
which
was
while
the
I
ojs
fork
was
active.
The
meticulous
documenting
of
how
to
work
together
was
so
helpful
when
we
created
the
foundation,
because
we
just
adopted
that
stuff
whole
cloth,
because
it
was
so
clear
that
that
was
how
the
engineers
wanted
to
work
and
open
source
is
about
that.
It's
about
self-determination
from
the
doers
in
the
community,
so
that
to
me
that
the
fact
that
the
fork
happen
made
that
meticulous
documentation
possible.
We.
A
E
There
are,
there
are
a
couple
committees
and
boards
subcommittees,
so
there's
a
legal
subcommittee
and
marketing
subcommittee
of
finance
of
committing
each
of
them
kind
of
brings
different
things
and
not
a
regular
rhythm
of
business,
and
then
that
you
know
where
the
TSU
will
raise
issues
to
us
so
based
on
what's
being
fed
in
from
the
technical
side.
You
know
all
the
different
problems
that
we're
looking
at
or
concerns
that
they
have,
that
they
want
board
positioning
on
or
help
with.
You
know
we're
looking
into
some
of
the
inclusivity
issues
that
have
come
up
here.
E
We
were
asked
by
the
tsc
and
and
other
groups
to
look
at
that
and
I
think
there's
a
another
session
going
on
right
now
that
Ashley
and
Tracy
are
in
talking
about
that.
So
those
are
kind
of
some
of
the
big
things
you
know
the
sum
is
a
regular
rhythm.
Others
are
issues
that
are
brought
to
us
by
either
other
groups
or
board
meetings.
Where
we
raise
issues
that
we
discover
ourselves
great.
A
C
B
B
F
B
Ryan
was
paid
by
giant
for
note,
I,
don't
know
how
much,
but
he
was
and
then
at
a
certain
point
he
decided
that
he
wanted
to
work
on
other
things.
I
think
he
lives
in
the
Bay
Area
now
again
who's
in
Brooklyn
for
a
while.
Then
he
was
back
in
the
bay.
He
is
primarily
working
on
I,
think
machine
learning
stuff.
So
he.
B
He
you
know
saw
the
opportunity
to
bring
it
into
a
company
like
join
I
mean
this
was
a
long
time
ago.
This
was
2009
late,
two
thousand
nine
so
note
had
existed
for
less
than
a
year.
I
think
at
the
point
that
he
started
at
joint
and
joint
took
over
ownership
of
the
project.
It
was
right
before
the
first
node
comp,
so
actually
it's
2010
and
yeah.
I.
C
B
It
was
you
know
something
that
he
wanted
to
do
and
then
I
think,
over
time
he
decided
he
didn't
want
to
work
on
the
project
anymore,
which
is
why
something
like
the
foundation,
something
like
the
tsc,
is
so
important,
because
you
can't
really
expect
that
one
person
is
going
to
work
on
a
project
for
their
entire
life.
I
mean
some
people
do,
but
it's
in
it's
not
the
average
reception
right.
H
H
A
C
E
C
So
I
work
for
a
bank
right,
I
work
for
paypal
and
there's
a
lot
of
recordings
of
bill.
Scott
who's,
the
executive
that
brought
node
into
paypal
and
there's
also
case
studies
that
have
been
published
about
that
effort
and
one
of
the
things
that
we
do
is
sponsor
the
foundation
to
put
up
new
fresh
case
studies
about.
C
You,
know,
sort
of
excellent
node
clients
who
are
really
seeing
a
quantifiable
benefit
and
in
our
case,
at
PayPal,
we
used
to
front
end
our
product
in
Java
and
when
bill
came
in,
he
came
from
netflix
where
they
were
using
node
and
he
saw
an
opportunity
to
to
teach
the
very
change
resistant
and
careful
engineers
at
PayPal.
That
node
could
really
accelerate
the
velocity
on
the
front,
ending
that
they
do
and
even
into
the
middleware
part
of
the
stack
and
what
he
did
and
he's
from
Texas
he's
a
very
humble
guy.
C
He
very
famously
denied
that
he
had.
He
had
ambitions
to
run
this
in
production.
So
he
went
through
a
whole
series
of
meetings
where
people
were
trying
to
stop
him
with
his
very
small
team.
Ian
15
people
that
were
prototyping
the
same
front-end
that
the
45
job
engineers
were
trying
to
write,
but
they
were
making
a
lot
more
progress
on
the
node
side,
because
it's
easier
right
and
every
time
he
got
into
a
meeting
where
somebody
would
say
what
are
you
doing?
C
He'd
say
you
don't
have
to
worry,
we're
just
prototyping
we're
just
prototyping,
don't
worry
about
it
right
and
because
he
knew
that
at
some
point
those
Java
engineers
would
get
frustrated
because
the
node
guys
were
getting
there
so
much
faster
and
they
would
start
as
hitting
from
inside.
So
when
the
flip
happened
and
they
and
node
was
our
new
production
front
end,
he
would
he
acted
surprised.
I'm
the
most
surprised
that
this
is
happening.
But
of
course
he
knew
the
whole
time
that
that's
what
was
going
to
happen.
C
D
And
a
lot
of
us
go
out
and
talk
about
this,
so
you
know
two
or
three
times
a
week.
It
seems
I
talked
to
a
client
who
has
these
kinds
of
questions
and
is
looking
for
examples
and
how
to
get
going
and
that's
how
I
learned
a
lot
of
how
cios
don't
know
the
fact.
How
much
of
note
is
actually
happening
in
their
shop
when
you
sit
down
with
a
major
airline
and
we've
got
his
CTO
and
the
CIO
and
you're
having
a
chat,
and
you
say
yeah,
you
probably
got
some
of
this
going
on.
D
D
A
B
I
think
I
can
probably
hit
it's.
It's
a
general
question.
It's
probably
better
answered
by
the
tsc
folks,
but
you
know
how
is
the
node
project
working
with
the
v8
team
and
other
external
organizations?
Tc39
would
be
a
good
example
as
well.
Stability
has
been
a
major
boon
to
that
right.
I
mean
the
idea
that
the
project
itself
wasn't
healthy
is
going
to
be
a
turn-off
to
a
team
like
v8,
and
I
know
for
a
fact
that
the
amount
that
been
going
on
between
v8
and
node
has
improved
a
lot.
C
Of
the
first
things
that
we
did
in
setting
up
the
foundation
was
scan
the
code
because
there
was
a
rumor
which
I
actually
heard
from
google,
that
there
was
some
code
in
there.
That
was
licensed
under
the
a
GPL
which
they
have
chosen
not
to
mix
with,
and
we
were
able
to
do
a
scan
using
the
Foundation's
resources
to
prove
that
that
wasn't
the
case.
And
then
it
was
easier
for
google
to
come
in.
C
Well
is
it
might
be
a
controversial
answer
given
given
the
mood
here
this
week,
but
I
actually
I
spend
a
lot
of
time
in
open
source
communities
and
I
serve
on
a
lot
of
boards,
and
actually
this
community
is
more
inclusive
than
any
other
community.
That
I
know
of
in
the
sense
that
there
are
people
that
that
are
leading
all
walks
of
life
and
making
life
choices
and,
being
you
know,
visible
in
their
choices,
more
prevalently
in
this
community
than
any
other
community
that
I'm
involved
with
so
there
we
have
work
to
do.
C
There's
definitely
work
to
do
on
inclusion
here
so
that
everybody
feels
comfortable
and
wants
to
participate,
but
the
for
whatever
it's
worth.
The
project
has
already
attracted
a
very
large
population
compared
to
all
other
projects
that
I
work
on
of
people
who
want
that
and
and
are
living
that
way,
and
I
think
that's
a
strength
of
this
community.
It
makes
it
modern.
C
So
when
I
look
at
some
of
the
things
that
the
I
ojs
community
wanted
in
the
way
that
they
were
working,
we're
closer
to
open,
open
than
open
source
open
open
is
the
idea
that
there
are
too
many
constraints
and
open
source
too
many
barriers
to
entry,
it'd
be
nice
if
it
was
more
frictionless
and
we
adopted
some
of
those
ideas
because
again
it's
a
fresh
community.
That's
you
know
trying
to
revolutionize
how
they
work
in
optimized
for
contribution,
rather
than
some
of
the
other
possible
optimization
dials.
C
You
can
turn
in
an
open
source
project
and-
and
that's
really
exciting
to
me-
I
my
peers,
people
that
have
been
involved
in
open
source
as
long
as
I
have.
Many
of
them
are
having
a
hard
time
with
the
kids,
the
wave
of
kids-
and
I
actually
gave
a
talk
at
oz
con
in
north
america
in
May
that
you
can
probably
find
online
where
I
talked
about
sustainability
of
open
source
and
the
things
I
think
we
need
to
pay
attention
to
now.
C
20
years
in
that,
you
know,
might
bite
us
going
forward,
because
the
new
wave
of
people
are,
for
instance,
fatigued
about
the
licensing
conversation.
They
don't
want
to
have
that
conversation
anymore,
and
so
often
they
will
choose
no
license,
rather
than
have
to
figure
that
out.
That's
dangerous
and
my
advice
to
the
larger
open
source
community.
B
Think
that's
the
ethos
of
the
larger
JavaScript
community
I
mean
you
look
back
at
you
know,
talk
about
lore
and
history
of
node
right
node
was
announced
at
JS,
conf,
EU
2009,
that's
really!
When
most
people
caught
its
attentions
when
it
caught
my
attention
and
the
larger
JavaScript
community
that
focuses
a
lot
more
on
front.
End
I
think
gets
a
lot
of
people
that
don't
have
traditional
computer
science
backgrounds.
You
know
if
you're
going
to
be
interested
in
design
and
front-end,
you
don't
necessarily
need
to
have
a
PhD.
B
C
D
Growing
the
population
of
other
folks
takes
a
while,
you
know,
evolved
an
OpenStack
I
said
on
that
board
as
well
too.
We
started
out
with
this
very
small
fraction
of
the
population.
That
was,
you
know,
from
women
or
other
other
groups,
and
and
we've
grown
that
into
double
digits
and-
and
it's
taken
considerable
effort
to
go
and
do
that.
But
we've
set
up
the
opportunities
we've
done.
D
The
outreach
we've
actually
had
listed
folks
from
the
outside
to
come
in
and
help
us
figure
out
what
what
we
needed
to
do
and
that's
the
kinds
of
things
that
we're
doing
here.
So
you
know
you
can
do
it
it
just
it
doesn't
happen
overnight.
You
don't
legislate,
it.
You've
got
to
get
folks
involved
and
engaged
and
show
that
you
are
that
friendly
place
to
come
and
be
part
of
them.
E
Mentioned
there's
a
public
component
to
all
of
our
board
meetings
and
I,
just
really
encourage
people
to
dial
in
for
that.
If
you
have
questions,
suggestions,
concerns
and
I'd
almost
like
to
turn
your
question
around.
What
what
are
you
in
the
community
think
is
special
and
very
different
about
about
this
open
source
foundation?
Are
there
things
that
you
know
you
have
concerns
about
because
we're
hearing
a
lot
of
good
questions
but
I
think
your
opinion
I'd
really
be
valuable.
Some
feedback.
C
C
E
C
There
were
people
who
got
it
than
left
know.
What
was
your
favorite
talk?
We're
almost
done
with
with
the
meeting
now.
Who
can
tell
me
what
their
favorite
talk
was?
Ok,
it
helped
this
one.
Now,
there's
probably
another
one
you
liked
I
suppose
I
saw
Sarah
in
last
hour.
She
was
pretty
great.
That
was
a
with
the
bobble-headed
sachcha.
It's
a
pretty
great
little
deal
the
machine
learning
guy.
C
The
first
I
went
to
node
confi
you
last
summer,
just
before
I
got
elected
and
there
was
a
guy
who
was
showing
how
many
processes
you
could
spawn,
and
he
had
it
was
like
I
can't
be
a
thousand
thousand
24
videos
going
at
the
same
time
and
as
it
was
kind
of
amazing,
it
was
a
cheap
trick,
because
it's
not
something
you
would
ever
do,
but
it
was
interesting
and
the
guy
who
makes
the
heck's
that
the
hex
shaped
stickers.
That
was
a
pretty
cool
wind.
C
D
C
C
A
C
So
it's
important
that
people
be
able
to
learn
and
we're
definitely
all
supportive
of
that.
But
I
was
actually
suggesting
that
we
that
we
turn
your
question
just
a
little
bit
and
and
have
Todd
talk
a
little
bit
about
the
certification
working
group,
which
is
more
about
the
modules
and
whether
they're
going
to
break
things,
which
is
another
important
piece.
We're
sort
of
more
working
on
that
level,
because
the
truth
is
those
opportunities
to
learn
are
proliferating
pretty
quickly.
C
C
F
C
E
C
C
So
one
of
the
first
conversations
we
had
was
about
packages
and
how
to
do
something
about
the
quality
of
packages,
and
so
that
consumers
could
know
with
confidence
that
a
given
package
was
actually
going
to
perform
as
advertised
and
was
fresh
and
was
all
those
things
right,
and
we
continue
to
sort
of
noodle
on
that
as
a
board.
So
there's
a
working
group
looking
at
that
a
question
for
instance,
so
that
when
people
are
learning,
there
are
fewer
things
to
run
into
that
are
out
of
their
control.
Yeah.
D
One
of
the
first
problems-
people
have
is
theirs
three
hundred
thousand
modules
out
there
yeah.
What
do
I
pick
right
do
I
know
the
quality
of
it
and
helping
people
get
through
that
and
moving
that
long,
so
that
you
as
a
developer,
know
what
you
can
count
on
is
really
important.
So,
hence
why
the
importance
of
going
and
doing
that
you
know
Java
had
some
good
things.
Obviously
they
were
looking
to
have
multiple
independent
implementations,
so
they
had
T
CK's
test
cases,
essentially
to
go
with
it,
a
specification
and
a
reference
implementation.
D
So
we
don't
need
the
spec
we
can
put
the
spec
aside.
The
code
is
the
de
facto
standard
and
specification
for
this,
and
now
we
need
to
improve
the
stability
of
the
codebase.
Hence
all
the
testing
that
we've
done
and,
of
course,
stability
of
the
module
system
and
the
modules
that
we
have
and
the
security
of
all
of
that,
because
that's
that's
very
important
if
we
do
have
weak
security
again,
will
will
eventually
fail
as
well
too.
So
all
those
things
are
important
in
all
of
those
things
are
things
that
we
worry
about
and.
C
E
I
I
B
The
the
tsc
is
talking
to
folks
about
the
registry.
Obviously
there
is
concerns
I've
heard
it
from
a
lot
of
different
people.
That
is
something
that's.
You
know
outside
of
our
our
scope
as
a
foundation,
but
there
are
a
lot
of
efforts
out
there.
I
think
the
note
security
projects
a
good
one
that
finds
a
number
of
vulnerabilities
and
reports
them.
B
There
are
other
efforts
out
there
to
secure
all
of
it,
but
at
the
end
of
the
day
it
is
sort
of
a
bizarre
one
of
my
favorite
quotes
about
this
is
that
by
depending
on
something,
you
are
implicitly
saying
that
you
will
eventually
maintain
it
one
day
if
the
maintainer
goes
away.
There's
no
way
around
that
you
know.
Even
if
we
did
run
the
registry,
there's
no
way
that
one
organization
could
maintain
three
million
door,
three
hundred
thousand
different
modules,
it's
just
not
the
way
that
it
would
would
work.
B
I
B
Mean
that's
true,
but
I
mean
not.
Everything
has
a
standard
library
right
I
mean
like
not.
Every
other
language
has
a
standard
library.
Also,
a
lot
of
other
things
take
go,
for
example,
goes
a
great
use
case
here.
Go
has
no
package
manager
right
go,
you
can
depend
directly
on
urls
from
github,
and
the
same
problem
arouses
right
I'll.
You
know
to
imagine
that
you
could
just
put
in
a
github
URL
and
you
could
get
it.
You'd
still
have
that
same
problem
right
it
would.
B
It
would
no
longer
be
a
registry
problem
because
there
wouldn't
be
a
registry,
but
the
meta
problem
still
exists,
and
that
is
a
if
you're
writing
software,
you
sort
of
have
to
go
out
and
evaluate,
and
there
I
would
love
to
see
an
open
effort
to
make
that
better.
But
that's
not
something
that
I've
seen
beyond
a
few
small
projects
like
node
security,
I,
think
David
DM
does
it
I
know
sinker
snick
is
another
private
company
that
does
it
for
security
purposes,
back.
C
In
the
day,
open-source
got
a
lot
of
criticism
from
the
traditional
software
community
about
the
potential
for
lack
of
security
and
I.
Think
you
know,
20
years
on,
projects
like
Apache
have
been
able
to
prove
that
they're
actually
much
better
at
responding
to
security
issues
than
the
average
proprietary
project
and
we're
starting
to
see
proprietary
projects.
Try
to
copy
some
of
the
methodologies
that
open
source
uses
to
deal
with
their
issues
around
some
of
this
patching
that
happens
right
and.
C
Of
code
base
is
key
to
to
this
being
better
you're
right.
It's
a
potential
vulnerability
of
this
architecture,
but
we're
not
the
only
community.
That's
got.
The
vulnerability
will
definitely
all
be
collectively
trying
to
figure
out
what
to
do
about
it.
I
can
think
of
a
few
possible
ways
to
attack
that
problem,
but
I'm,
not
the
tsv.
You
know
so,
but
I'm
sure
that
the
security
group
is
thinking
about
it
all
the
time
they
have
to
be.
B
New
user
onboarding
problem
has
been
a
pretty
common
thing
right,
like
you
go
and
you
look
and
you
use
downloads
as
a
proxy
for
VIP
for
quality
right
and
that's
worked
relatively
well.
I
don't
see
many
people
who
do
a
search.
Take
the
thing.
That's
the
most
downloaded
and
regret
that
decision
for
the
most
part,
so
the
new
user,
their
search
problem,
you
know
they
can
get
better
at
it
over
time.
They
can
get
more
nuanced.
Okay,
I'm
going
to
read
the
code.
B
Okay,
this
has
the
badges
for
the
CI
is
there
are
the
badges
that
all
its
dependencies
are
up
to
date,
but
downloads
as
a
proxy
to
quality
and
value
is,
is
pretty
good
and
I.
Think
that's
why
new
users
keep
coming
on
right.
I
mean
if
this
was
a
challenge
for
them,
then
the
community
wouldn't
be
doubling
you
over.
B
C
What
we
did
at
PayPal
was
we
created
a
sort
of
bumper
room
with
our
framework
with
crackin,
so
we
give
the
individual
developers
some
choice
in
what
they
want
to
use,
but
they
have
to
live
within
our
framework,
because
that
supplies
us
with
some
certainty
that
you
know
the
choices
they're
making
can't
be
two
disasters
to
us.
That's.
B
A
great
example
because
in
crack
and
there's
a
middleware
that
it
does
a
lot
of
web
security,
things
right
so
take
Express
Express
is
stable.
Doug
is
going
to
give
a
talk
on
it
later
today.
It
has.
You
know,
no,
no,
no
vulnerabilities
that
I'm,
aware
of,
but
it's
still
a
web
server
right.
So
if
you
don't
use
this
other
middlewares
that
say
set
your
content,
security
policy
or
other
web
HTTP
things
you're
by
definition,
letting
people
write
in
secure
web
servers.
B
So
it's
it's
a
challenging
problem,
but
at
the
end
of
the
day,
it's
again
downloads
as
a
proxy
to
value
people
figure
it
out
and
search
for
it.
And
then
you
know
your
average
novice
is
not
necessarily
looking
to
write
the
most
secure
enterprise-focused
web
server,
they're,
probably
making
sure
that
they
can
write
anything
at
all
for
the
first
time
and
so
they'll
they'll
work
through
that
and
they're
their
third
or
fourth
projects
is
where
they'll
start
to
pay
attention
that
stuff.
C
So
let
me
tell
you
what
happened
with
Apache
this
he's
asking
if
the
flavor
the
open
source
flavor
of
node
is
going
to
disappear
now
the
big
companies
care.
So
let
me
tell
you
what
happened
with
Apache,
so
patchy
was
a
project
for
five
years
before
the
foundation
was
formed,
and
in
that
so
it
started
with
13
guys
that
were
just
patching
because
they
were
hobbyists
and
by
the
time
we
formed
the
foundation.
They
were
all
suing
each
other
because
they
all
had
business
interests.
C
They
were
small
companies,
but
they
were
already
at
each
other's
throats
and
setting
up
the
foundation
was
a
way
to
kind
of
cause,
a
ceasefire
to
happen
so
that
the
project
could
go
forward.
What
they
said
at
the
time
was
God.
We
wish
we
could
just
get
back
to
how
it
was
when
we
started-
and
we
were
all
friends
and
we
were
working
in
the
same
direction
and
the
apache
software
foundation
proved
to
be
very
successful.
At
helping
the
web
server
become
super
successful,
IBM,
wrapped
it
as
web
server.
C
It
became
the
de
facto
standard
and
web
servers
at
one
point.
Almost
eighty
five
percent
of
all
web
traffic
ran
through
an
Apache
server,
but
if
you
went
and
talked
to
the
guys
that
wrote
it,
they
feel
like
they're
in
a
community,
they
love
each
other.
They
go
on
vacations
together,
they
hang
out
together.
They
work
in
all
different
companies.
They've
changed
jobs
over
the
years.
They
help
each
other
get
jobs
there
they're
all
friends
still,
and
so
it
might
be
a
magic
ingredient
of
open
source
that
you
get
to
have
both.
D
In
the
transition
to
cloud
it
has
become
a
language
that
everybody
wants
to
use,
and,
and
so
it's
not
a
dependency
for
the
business,
but
it's
something
that
our
customers
just
expect,
and
we
see
that
more
and
more
and
more
so
so
it's
it
just
makes
sense
to
be
part
of
and
fostered
as
a
community
and
do
it
all
together,
because
it's
not
something
we're
individually
making
money
on
per
se.
It's
something
that
we're
enabling
so
everybody
else
who
wants
to
go
and
build.
D
C
C
E
C
E
A
It
was,
it
was
almost
a
nice
way
to
wrap
things
up.
So
thank
you.
Everyone
for
joining
us
here
today
and
as
Colleen
and
others
have
mentioned
there
is
the
the
public
portion
of
that
board
meeting
and
feel
free
to
drop
in
whenever
you
want
and
keep
the
the
conversation.
The
dialogue
going,
membership.