►
From YouTube: 2016-10-31 Node.js Foundation Board of Directors Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
D
So
the
directors
online
Brian
from
groupon
Colleen
from
Microsoft
for
us
from
individual
membership
rod
from
notes
or
Scott
from
joy
and
Charlie
from
godaddy
Justin
from
google
Denise,
obviously
paypal
and
be
up
to
grove,
is
council
on
the
line
and
then
from
the
linux
foundation's
as
Todd
Benzies.
Also
michael
rogers
and
Traci
Hines
are
on
the
line.
A
A
A
Right,
let's
get
going,
and
this
is
the
meeting
information
you
have
it
because
you're
on
antitrust
compliance
notice,
this
is
really
really
important.
If
you
don't
understand
it,
please
ask
our
counsel
Andy
up
to
Grove
about
the
details.
Number
directory.
As
you
can
see,
we
don't
have
gold
members
anymore,
so
it
makes
this
slide
a
little
bit
nicer.
We
we
have
more
on
the
platinum
side
now.
A
So
that's
looking
good,
but
no
new
members
announced
since
our
last
meeting
last
month,
all
right
first
resolution
that
the
meetings
of
the
public
session
of
the
September
2016
meeting
the
board
of
directors
in
the
form
here
too
attached,
as
exhibit
a
are
hereby
confirmed,
approved
and
adopted,
can
I
get
a
motion
in
a
second.
F
E
G
G
A
Okay,
so
another
resolution
welcome
to
Daniel
and
Charlie
are
no
plans
to
get
a
resolution
here
to
acknowledge
the
appointment
of
these
directors.
The
board
hereby
acknowledged
as
the
appointment
of
platinum
directors,
Charlie
Robbins
from
godaddy
and
Daniel
Shaw
from
node
source
can
I
get
a
motion
in
a
second.
G
D
A
Acid
unanimously,
all
right
great
to
have
you
all
on
whoo-hoo,
exciting
stuff,
all
right
so
FYI
the
board
secretary
position
is
still
not
filled.
Oh,
we
do
have
two
new
board
directors
on
so
I'm,
hoping
that
we
can
get
a
resolution
to
this
like
right
now.
So
are
there
any
directors
that
would
like
to
fill
the
secretary
position
for
us
I.
A
A
A
H
A
H
A
Welcome
to
Anna's
bird
secretary
awesome
all
right
well
moving
right
along
nodejs
in
the
media,
so
we've
seen
a
decline
since
about
march
in
general
media
coverage.
It
seems
to
be
kind
of
flattening
out
and
we've
seen
Java
kind
of
bounce
around
a
bit
again
I.
A
E
A
I'll
ask
about
that
and
get
it
in
from
the
marketing
team.
I
think
one
reason
was
mainly
just
so
that
we
track,
along
with
the
same
job,
at
enterprise
line,
for
reasoning
that
as
a
baseline,
but
you
know
no
jst
has
less
problems
in
terms
of
like
Java
is
a
more
general
term
than
nodejs.
So
I
think
that
we
actually
would
get
something
out
of
line,
even
if
it's
not
comparable
to
the
Java
line,
so
yeah
I,
don't.
A
A
J
E
So
yeah
I'd
like
to
see
general
general,
no
Jess
added
to
that
and
you
know
Michael
when
you're
saying
you
know,
we
don't
have
said
its
end
up
and
added
cinnamon
else
added
to
this
mix.
Are
you
saying
that
we
know
it's
in
the
pipeline
that
we're
going
to
have
sentiment
analysis?
Do
we
want
to
add
you
know
that
sentiment
analysis
into
this
mix?
Would
we,
you
know,
be
enriched
if
we
we
had
more
sentiment.
A
So
that
this
these
numbers
come
off
of
a
general
product
that
the
Linux
Foundation
uses
kind
of
internally
to
track
media
coverage.
I
will
I
will
ask
what
it
would
take
to
get
sentiment
analysis
in
there
and
see
if
this
is
something
that
we
can
improve
upon
that
way
or
if
maybe
we
have
to
do.
You
know
something
on
our
own
or
even
maybe
cut
out
some
budget
in
order
to
get
that
and
I
can
see
what.
E
I
C
A
That's
a
much
more
difficult
one
I
mean
we.
We
know
that
analyst
coverage
is
up
because
whenever
they
put
out
a
report
they
send
it
to
us.
The
problem
is
that
because
we
don't
subscribe
to
those
reports,
we
can't
talk
about
them
publicly.
So
in
our
executive
session
later
I
will
actually
be
telling
you
about
one
of
them,
but
I
can't
say
it
on
this
public.
Oh
ok,
we
would
violate
our
terms
with
that
particular
analysts.
Next.
E
I
mean
not
really
media,
but
you
know
I've
a
bit
of
a
bone
to
pick
with
with
our
coverage,
and
you
know
sort
of
getting
the
no
dias
brand
out
everywhere.
We
got
a
little
bit
of
stickers
and
you
know
I
think
there's
a
lot
more
interest
in
intent
to
sort
of
embraced.
Node
is
a
brand,
then
we're
fulfilling
to
the
market.
So
you
know
something
that
we
could
do
that's
going
to
drive.
You
know
this.
E
A
E
A
And
and
obviously
we're
lining
up
a
lot
of
press
over
the
next
month
around
the
event,
so
the
more
that
every
member
can
get
coordinated
around
the
the
press
and
announcements
that
we're
lining
up
for
that,
the
better
and
we'll
get
you
know,
a
very,
very
big
bump
I
mean
the
largest
bump
we've
ever
had
in
terms
of
coverage
was
in
non-interactive
North
America
last
year.
So
we
would
like
to
replicate
or
even
go
beyond
that.
E
A
B
A
Okay,
great,
let's
move
along
so
in
december
I'll,
be
starting
to
put
together
all
of
the
numbers
and
kind
of
metrics
for
us
to
do
a
very
pretty
kind
of
2016
report
that
that
is
incorrect.
2017
report
will
not
be
until
the
end
of
next
year,
but
a
nice
report
for
sort
of
what
node
did
in
2016,
all
of
our
kinds
of
accomplishments
and
stuff,
like
that
I
would
love
input
for
everybody
here
on
the
kinds
of
metrics
that
we
would
like
to
see.
A
E
Yeah
I'd
like
to
see
jobs
numbers.
You
know
some
thinking
of
the
numbers
that
we
cover
last
year
and
kind
of
the
Delta
between
those
numbers.
So
if
we
could
tap
into
real-world,
hiring
around
know
Jess-
and
you
know,
presumably
with
an
increase
their
yeah-
that
would
that
would
be
a
meaningful
new
metric.
That
I
would
like
to
see.
That's.
A
G
A
I
A
But
can
we
capture
something
like
this
last
year?
Yeah?
The
problem
is
that
we
don't
get
any
absolute
numbers
from
that
right
like
we
get
right.
B
B
A
H
K
Michael,
this
would
Sarah
Conway
with
lf2.
This
wouldn't
be
in
time
for
growing
up
results
for
reporting
my
next
board
meeting,
but
chance
you
have
to
starting
to
do
ongoing
surveys
with
people
that
have
registered
for
their
to
convent,
so
I,
don't
know.
If
there's
a
possibility
of,
we
need
something
note
specific
into
the
future
report
a
survey
we're
going
to
be
doing
them
several
times
throughout
the
year.
K
A
Yeah
definitely
also
we,
we
should
talk
with
the
container
con
cube
con
people
about
what
they're
doing
in
their
post.
B
A
E
You
know
so
one
of
my
favorite
numbers
from
last
year
is
the
you
know
the
number
of
contributors
to
the
project.
I
think
that's
fantastic.
You
know
I'd
like
to
see
us
capture
and
I.
Don't
know
exact
how
to
go
about
doing
this,
but
you
know
something
that's
important,
something
that
we're
going
to
be
discussing
is
our
efforts
around
inclusivity
and
I.
E
A
Only
interrupting
because
that's
a
very
good
transition,
so
I
just
want
to
make
sure
that
nobody
else
has
any
ideas
about
about
this
particular
slide
and
then
wait
and
then
we
can
actually
use
that
as
a
great
transition
point.
So
anything
else
that
people
would
like
to
see
in
that
the
27th
2016
report.
E
Have
a
thought
in
this
area:
if
I
can
continue,
there
oh
come
on:
where
are?
Are
we
getting
this
from
our
member
companies
or
are
we
only
relying
on
data
sources
like
no
Jess
org,
and
you
know
other
folks
that
offer
up
the
data?
So
you
know
what
are
we
thinking
of
in
terms
of
what
data
sets
we
could
possibly
bring
to
bear
so.
A
We
we
can
get
that
we
try
to
pull
in
data
from
multiple
sources
right,
so
we
use
any
analyst
data
or
analyst
reports.
We
really
love
a
lot
of
the
red
monk
data.
For
instance,
it
comes
out.
We
tend
I,
we
tend
to
pull
that.
We
pull
numbers
that
we
get
from
NPM.
We
have
a
model
of
data
that
we
also
put
that
into
that
has
stuff
like
the
download
metrics
from
of
core
from
the
website.
A
We
have
the
google
analytics
on
the
website
as
well
yeah,
so
we
have
a
big
bunch
of
numbers
that
we
can
draw
on
plus
all
of
the
github
data
and
all
of
that
kind
of
stuff.
But
you
know
for
certain
things
that
we
may
want
to
get
like
like,
for
instance,
dr.
Tanner
stuff.
We
would
definitely
need
to
ask
members
about
their
data
for
that.
So.
E
A
That's
a
really
good
point:
yeah
I'll
talk,
I'm
Jacob,
groundwater
just
started
managing
that
team.
So
I'll
talk
with.
E
E
Lawson's
lesson
books
could
could
would
be
interested
in
willing
to
contribute
their,
but
yeah
I
really
taught
me
the
new
bus,
true
good.
A
I
So
I
was
unfortunately
unable
to
share
this
link
prior
because
we
had
a
couple
docs
flying
around
with
different
groups
and
I
didn't
want
that
to
be
the
document
that
you
all
would
get
to
look
at,
because
those
were
different
perspectives,
a
bit
of
a
mess,
a
lot
of
commenting.
So
this
is
the
final
it's
in
the
chat
for
a
gotomeeting,
so
that
was
unfortunate.
I
I
I
C
I
I
Okay,
all
right!
Well,
that's
unfortunate,
so
I
should
have
I've.
Never
had
this!
Oh
that's
why?
Okay,
let's
do
this!
Oh.
I
It's
because
it's
gating
it
to
the
Linux
Foundation
I
apologize.
Okay,
sorry
I'm
doing
it
now,
because
this
is
important
to
be
able
to
see
that
all
right,
so
I've
gotten
a
lot
of
input
from
various
folks
in
the
community.
We've
also
had
some
meetings,
but
we
were
continuing
to
have
meetings.
I
The
idea
behind
this
link
is
that
by
having
that
or
by
having
this
document
and
I
looking
at
these
options,
this
is
not
the
be-all
end-all
of
inclusivity
for
node,
but
this
is
our
starting
point
and,
and
I
was
really
trying
to
make
sure
that
we
included
a
number
of
folks
for
that.
So
that's
that's
an
apology
for
why
it
took
so
long.
For
me
both
do
this.
On
top
of
the
other
things
that
we
were
doing,
but
let's
try
that
one
more
time
third
time's
got
to
be
a
charm.
Okay
exists.
D
I
Right
yeah
see
so
what
what
we
talked
about
here
is
sort
of
the
the
crux
of
all
of
this
to
me
and
something
that
I've
talked
to
with
a
number
of
folks
in
the
tsc
and
the
CTC
is
sort
of
why
the
inclusivity
working
group
was
such
a
misfit,
where
it
was,
and
and
not
that
it
wasn't
well
intended,
but
that
we
need
to
regardless
of
who
owns.
The
organ
is
a
sorry,
regardless
of
me
and
Michael
and
other
folks,
as
leaders
in
this
project,
trying
to
help
improve
inclusivity.
I
I
Think
somebody
within
the
exact
you
know
part
of
the
foundation
such
as
myself
should
be
able
to
participate,
but
I,
don't
think
that
I
should
own
it
as
well,
and
there's
always
a
chance
that
the
priority
of
the
next
person,
if
that
were
to
happen
with
the
education
community
manager,
would
not
quite
have
the
same
priority
or
perspective
in
that.
So
I
think
that,
ultimately,
what
should
happen
and
there's
a
drawing
that
I
can
do
for
that,
but
did
not
create
the
diagram.
I
Is
that
I
think
that
there
should
be
a
community
organization
alongside
the
tsc
under
the
node
foundation
and
I
know
that?
That's
a
really
that's
a
massive
ask,
so
that
would
that
I'm
happy
to
answer
lots
of
questions
about.
But
ultimately,
what
I
see
you
over
and
over
again
is
that
there
are
a
ton
of
organizations
that
aren't
necessarily
code
specific,
such
as
node,
school,
node,
BOTS
and
all
of
meetups.
I
So
I
see
something
like
the
community
organization,
alongside
the
tsc
being
a
good
place
for
a
lot
of
these
things,
that,
from
an
idea,
standpoint
that
don't
belong,
go
to
the
tsc
but
absolutely
need
help
and
support
in
some
way
and
there's
people
who
want
to
help
do
that.
I
think
that
the
inclusivity
would
be
the
inclusivity
working
group
would
be
an
excellent
fit
under
that
organization
and
that
would
still
again
be
community
owned.
I
So
that's
the
first
thing
that
I
would
recommend
I'm
happy
to
email
or
discuss
this
further.
The
second
is
the
diversity
training
which
I
know
I
talked
about
with
a
few
of
you,
I've
talked
to
a
number
of
consultants,
I
think
ash
Dryden
is
the
consultant
that
I,
I
would
recommend
for
us
to
help
with
their
I've
talked
with
another,
wherever
the
consultants
who
quite
honestly
liked
the
idea
of
what
I
was
talking
about
them.
Helping
us
with
but
didn't
feel
comfortable
taking
that
on
themselves.
I
I
was
a
little
bit
outside
of
their
domain
experience
and
I
also
thought
that
it
would
be
helpful
for
with
that
that
other
leaders
from
the
node
foundation,
such
as
parts
of
the
tsc
or
other
working
groups,
would,
if
interested,
would
also
benefit
from
participating
in
that
I
am
meeting
with
ash.
Next
week,
it's
been
incredibly
difficult
to
schedule
these
meetings
to
get
the
quote
as
all
of
these
folks
are
awesome
and
really
busy.
So
ash
had
availability
next
week,
I'll
talk
to
her
and
have
the
actual
number
for
that.
I
Another
thing
that
I'd
recommend
and
have
experienced
myself
is
the
idea
of
peer
mediation,
so
documents
as
a
resource
online,
but
also
the
option
of
having
more
people
who
are
facilitators
to
be
able
to
do
this
sort
of
thing
at
meetups
or
workshops,
and
that
helps
encourage
better
style
of
communication
for
folks,
both
in
person
and
online
I.
Think
that
that's
something
that
you'll
sort
of
see
on
the
you'll
see
is
like
a
non-technical
talk
at
a
conference
that
a
lot
of
people
actually
attend
and
benefit
from.
I
They
really
appreciate
and
then
there's
more
champions
within
the
community
that
are
helped
leading
that
help
their
conversation,
because
a
lot
of
what
I've
seen
is
not
actually
inclusivity
or
diverse.
It's
not
let's
say
it's
not
an
inclusivity
issue,
or
it's
not
a
diversity
issue.
It
is
making
people
feel
welcome.
So
it's
more
of
the
inclusivity
problem
that
we're
not
able
to
communicate
sort
of
on
a
level
playing
field
and
because
of
that
people
get
emotional
and
passionate
and
can't
communicate
well.
I
I
A
B
I
I
So
it's
part
of
that
I've
indicated
that
will
have
to
refactor,
so
the
IRC
channel.
If
the
challenges
of
us
refocusing
our
energy
on
IRC
as
the
medium
and
official
like
chat
channel,
is
that
we
have
to
refactor
those
policies
and
make
sure
that
the
people
who
are
currently
participating
in
the
project
are
happy
with
this
and
feel
comfortable,
acting
and
moderating
with
those
those
guidelines.
So
the
other
option
is
sort
of
the
the
nuclear
option
and
some
would
say
less
open,
and
that
would
be
slack.
I
So
the
idea
would
be
to
create
a
new
central
slack
organization
by
doing
that,
you
do
have
a
gating
and
the
only
gating,
because
I
want
to
make
sure
that
it's
opened
I've
by
default.
Is
them
signing
up
and
agreeing
to
the
code
of
conduct
as
part
of
the
sign
up
by
them
signing
up
they're
saying
they
are
in
participating
that
they
have
to
follow
the
code
of
conduct?
I
And
by
doing
that,
then
we
have
a
much
easier
I
think
we
have
an
understanding
from
the
get-go
as
opposed
to
sort
of
grandfathering
in
the
code
of
conduct
into
channels
that
people
may
have
existed
in
on
IRC.
For
quite
some
time.
There
are
downsides
to
slack
one
of
them
being
if
we
use
the
non
paid
version
which
we
absolutely
have
to
do
for
cost
reasons.
I
There
is
not
a
persistence
of
conversation,
so
we
would
have
to
set
up
its
turtle
mechanisms
for
logging,
which
I
also
think
we
need
to
do
for
IRC,
but
I
think
that
it
I
don't
know
what
the
cost
differences,
if
any
would
be
for
that.
So
that
needs
to
be
discussed
and
I.
That
won't
be
able
to
happen
without
the
TSE
for
sure
being
on
board
with
either
of
those
options,
because
there
are
so
many
existing
places
where
those
conversations
happen
that
that
buy-in
is
just
absolutely
essential.
I
The
next
is
prioritizing
seeking
a
diverse
range
of
candidates
for
hiring
and
vendors.
That's
simply
that
you
know
moving
forward
if
it
wasn't
already
considered.
Most
of
our
member
companies
are
doing
a
very
similar
thing
where
they
just
try
and
make
sure
that
they
have
a
diverse
pool
of
candidates,
anytime
they're,
considering
a
candidate
for
hire
or
for
contracting.
So
that's
something
I
think
that
that's
just
another
way
of
our
leadership
being
able
to
say
we
believe
in
this
and
we're
doing
this.
I
We're
sharing
we're
sharing
that
by
showing
our
actions
as
well
as
our
words
and
then
another
one,
which
is
what
Dan
had
brought
up
earlier
and
is
absolutely
essential
to
all
of
this
and
was
my
biggest
challenge
in
this
was
that
we
have
to
measure
and
set
reasonable
goals
for
diversity
and
inclusivity
and
I
don't
have
those
numbers,
so
we
need
to
in
order
to
be
able
to
increase
representation
from
our
global
community.
I
have
to
know
some
of
our
numbers
to
begin
with
and
I.
I
Don't
really
think
I
got
that
from
the
survey
last
year,
so
Greg
and
I
are
working
on
building
a
much
more
comprehensive
survey.
We're
also
going
to
be
releasing
it
at
node
interactive
on
top
of
trying
to
build
up
a
much
larger
network
to
share
this
with
in
order
to
get
a
better
representation
of
where
we're
at
who
are
our
users?
Why
are
they
using
node?
Why
are
they
using
the
tools
connected
to
node
and
would
love
input
on
that?
I
A
I
I
C
E
I
Today,
I
think
Dan
may
have
missed
the,
but
the
sort
of
the
context
of
why
I'm
giving
this
update
in
the
first
place.
So
the
tsc
came
to
the
board,
with
a
request
for
us
to
investigate
how
the
inclusivity
working
group
responsibilities
could
change,
and
this
is
sort
of
the
report
on
that.
So
once
I
go
from
here,
because
some
of
this
does
require
sort
of
boards
participation
in
then
we
would
go
back
to
the
tsc
to
share
like
what
we
think
should
happen.
Good
thanks.
A
Moving
along
a
tsc
update,
so
first
of
all,
I
know
that
we've
been
getting
tons
of
question
from
the
community
and
including
when
we
do
these
on
the
state
of
es6
modules.
We
I
went
down
to
the
tc39
meeting
last
month
and
actually
got
a
lot
of
you
know
really
positive
feedback
got
things
moving
in
a
pretty
positive
direction.
We
all
think,
and
all
the
stakeholders
were
we're
pretty
happy
and
excited
about
it
towards
the
end.
Bradley
still
did
the
majority
of
like
the
real
kind
of
technical
work
it
was.
F
Okay
in
my
own
yep,
thank
you
so
very
productive
month
october
got
three
major
events.
The
first
one
is
version
6
transition
to
our
second
LTS
line.
Codename
boron.
We
had
a
lot
of
coverage
around
that
I'm,
really
happy
with
the
synchronization
between
the
technical
team
and
the
the
marketing
team
for
October.
It
took
a
little
bit
to
get
there,
but
it
was
a
really
good
launch.
F
A
B
Is
I
guess
I'll
have
throw
in
one
question:
I
know
that
there
were
some
challenges
in
the
module
ecosystem
around
v7.
I
would
off
that
you
want
to
weigh
in
on
that
or
you
know
we
could
take
it
offline
I.
Looked
it
around.
F
Graceful
there's
always
challenges
when
we
do
these
new
ones,
because
it's
there
there
are
these
small
edge
cases
that
that
catch
a
few
users
and
they
and
it
tends
to
become
noisy.
So
there
will
be
an
ironing
out
period
to
make
sure
that
we
have
made
the
right
compromises
on
these
changes
that
we're
trying
to
make
and
not
break
too
many
people,
so
the
I
would
I
would
expect,
within
the
next
couple
of
months,
to
see
resolution
to
some
of
the
well.
F
Actually,
I
think
there's
only
a
couple
of
really
contentious
things
that
people
are
making
a
noise
about
and
I
really
personally,
I.
Don't
think
that
big
that
big?
So
that's
that's,
sort
of
to
be
expected
with
the
version
with
the
current
release
lines,
because
we
do
introduce
a
batch
of
breaking
changes
and
then
we
suddenly
find
out
that
they
break
edge
cases
that
we
weren't.
F
Even
aware
of
so
it's
a
way
of
discovering
you
know
all
these
different
corners
of
the
ecosystem
and
also
lots
of
opinions
that
we
didn't
know
existed
in
the
first
place.
Ok,.
F
B
No
I
know
it's
six
did
the
same
thing
I,
just
it's
sort
of
the
orders
of
magnitude
for
how
bad
we
think
they're
going
to
be.
Obviously
the
LTS
life
cycle
has
done
us
a
lot
of
favors
in
this,
because
most
big
companies
don't
adopt
us
for
another
year,
so
you've
got
that
that
window
to
make
those
changes.
So
thanks
that
answers
my
question.