►
From YouTube: 2017-01-30 Node.js 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).
B
A
C
A
Okay,
all
right:
this
is
the
dial-in
information.
You
would
have
seen
it
if
you're
on
the
call
antitrust
compliance
notice
same
as
always.
If
you
have
any
questions
about
this,
please
contact
our
council
Andy
up
to
grove
for
any
clarifications.
Our
member
directory
hasn't
really
changed
or
actually
oh,
we
need
to
get
snick
into
this.
My
bad
nick
is
now
a
member,
oh
well,
we'll
get
that
into
the
next
one.
A
D
A
E
D
A
Alright,
well
we'll
get
to
that
when
we
get
to
that
slide.
Okay,
all.
D
B
A
B
A
A
A
A
In
favor
aye
I'll,
any
post
in
the
abstaining
motion
passes
unanimously.
Daniel
Straus
odisha
won
the
gold
coin
toss
so
he's
sticking
around
this
year
as
well.
We
need
to
refi
ratify
his
position
on
the
board
as
well
for
the
gold
director
membership
so
resolved
at
the
board.
Hereby
acknowledges
at
the
appointment
of
dan
shaw
as
the
gold
membership
director
can
I
get
a
motion
in
a
second
motion
to
approve
dragon.
C
A
G
B
G
E
A
I
All
right
just
pulling
over
my
car,
okay
gsi's
got
a
couple
of
things
going
on
just
quickly.
With
regard
to
releases,
we
have
a
security
release
going
out
this
week.
Just
it's
fairly
minor,
openssl
update.
The
impact
to
note
is
pretty
low.
So
that's
that's
coming
out
this
week.
He
and
that
scene
that
we
didn't
I
think
24
hours.
I
should
be
going
up.
So
that's
that
that
the
last
of
the
second
last
tsc
meeting
we
finally
merged
the
TSE
scope
document
have
been
working
on
for
a
while
and
I.
I
So
it's
fairly
limited,
it's
mainly
based
around
node
core
and
supporting
projects
around
that
and
it
states
that
whenever
we
want
to
increase
the
scope
beyond
what
is
listed
there,
so
it
beyond
what
is
obviously
not
core
and
safe.
We
wanted
to
bring
on
a
new
project
that
was
completely
unrelated,
note
core.
Then
we
would
need
to
have
a
discussion
with
the
board,
so
we
would
seek
board
approval
for
that
increase
in
scope.
Where
we
don't
wear
it
doesn't
increase
the
scope.
I
Then
we
just
go
ahead
and
do
it,
and
so
speaking,
of
which
we
have
it
brought
on
a
new
project.
There
is
a
project
called
node
inspect,
that's
not
rica,
fused,
with
note
inspector,
it's
no
dash
inspect,
and
this
is
a
a
replacement
for
the
inbuilt
nodejs
command-line
debugger,
which
is
going
to
be
it's
going
to
not
work
soon
because
of
the
VA.
We
had
basically
dropping
support
for
how
we
do
that
and
it's
it's
not
very
well
supported
code
anyway,
so
somebody
has
written
there
a
player.
I
It's
been
for
that
using
a
very
new
v8
feature
that
we
are
shipping
the
VIP
inspected
protocol.
So
it's
basically
a
feature
for
feature
replacement
of
the
command
line
debugger
and
it's
being
pulled
into
the
node.js
foundation
in
the
github
repo.
It
may
eventually
ship
with
no
recall,
but
even
if
it
doesn't
it's
a
viable
replacement
circular,
my
debugger,
so
that's
something
that
we
have
taken
on
and
lastly,
the
you
may
have
seen
a
email
garand
about
the
the
legal
committee
require.
I
The
tsc
is
requesting
the
legal
committee
look
at
the
ad
to
proposed
pull
request
that
changed
the
copyright
hairs
in
source
files.
So
this
was
a
request
that
came
through
from
the
legal
committee
and
it's
now
going
back
to
the
legal
committee
for
some
questions
and
approval.
So
that's
I
believe
going
through
the
board
to
the
legal
committee
to
get
the
approval
or
comment
and
then
come
back
again.
So
I
think
that's
it
from
the
tsc
william.
Do
you
have
any
anything
else
that
I've
forgotten
there.
I
D
I
A
Idea
was
a
little
bit
garbled.
There
I
think
there's
a
difference
here
between
trying
to
suss
out
everything
that
happened
in
the
tsc
and
actually
having
somebody
represent
the
for
lack
of
better
in
the
opinion
or
the
escalation
of
anything
from
the
TSE
I.
G
I
William
is
not
a
member
of
the
tsc;
he
participates
in
our
meetings
and
you
are
welcome
to
participate
as
well.
William
happens
to
have
a
really
good
memory
for
these
things
better
than
I
do
so
by
pulling
him
in
I'm
simply
requesting
that
he
refresh
my
memory
or
anything
forgotten,
but
your
world
more
than
welcome
to
join
us
on
tsa
meetings.
If
you
would
like
to
participate
in
these
as
well.
A
Ok,
we've
got
a
lot
of
agenda
to
get
through,
I
want
to
knock
through
the
rest
of
these.
So
a
quick
update
from
the
community
committee,
so
Tracy
has
a
draft
charter
that
was
attached
as
exhibit
b.
It
is
it's
still
under
review
on
the
community
side
of
things,
but
for
those
participating
that
review
it's
coming
along
nicely
in
nearing
kind
of
the
final
stages.
A
A
A
E
J
Trigger
the
Charter
is
in
a
good
place
of
being
a
PR
right
now,
we've
gotten
some
really
good
feedback
so
far,
and
some
members
of
the
TSU,
as
well
as
the
community
have
been
have
been
giving
some
really
good
input.
That's
really
grown
up
that
and
it's
on
the
shoulders
of
giants.
So
it's
from
a
lot
of
the
work
that
tsc
had
learned
but
I
think
I
absolutely
expect
it
to
be
in
the
next
meeting
in
February.
J
A
Of
details,
I
think
as
it
is
now
attaches
the
exhibit.
It
is
pretty
much
in
the
state
that
is
probably
better
than
a
lot
of
the
documents
that
already
exist
on
the
technical
side.
It's
now
in
a
process
of
review
where
it's
being
improved
kind
of
beyond
and
with
what
we've
learned
from
some
of
those
documents.
So
yeah
it's
come
along
really
nicely,
but
we'll
definitely
have
that
up.
In
two
weeks
from
today
at
the
in-person
meeting,
yeah.
J
J
And
then
the
next
is
the
our
bi-weekly
updates.
So
we
realized
that
there
was
a
lot
of
there's
been
a
lot
of
places
that
we
can
improve
on
communication
with
even
what
the
node
foundation
team
is
doing
internally,
so
I'm
going
to
start
publishing
a
bi
weekly
update
into
the
community
committee
repo,
so
that
more
folks
can
be
aware
of
that.
It's
I
mean
it's
not
going
to
be
like
a
medium
post.
B
A
B
J
J
D
To
yeah,
no,
it's
really
cool
first
off.
This
is
super
awesome.
Is
there
a
specific
place
inside
that
repo
to
point
people
to,
if
say,
like
I,
wanted
to
draft
up
something
that
we
could
all
share
to
send
out
to
people
that
we
could
do
outreach
for,
like
kind
of
like
a
forum
for
Mishkin
a
letter
to
try
and
get
more
people
involved.
J
J
So
much
yeah,
that's
great
yeah
and
then
finally,
just
inclusivity
strategy
update.
So
the
first
strategy
point
was
the
community
committee
organization
so
we're
getting
that
moving
along
another.
J
Another
point
that
we
have
movement
on,
or
at
least
is
actively
engaged
in
conversation-
is
the
refactor
of
our
online
communication
channel
the
current
a
discussion
around
that
a
slack
versus
IRC.
It
is
a
very
thoughtful
discussion.
That's
happening
right
now
and
that
has
not
been
decided
so
we'll
see
how
that
goes.
J
J
Yeah
I
mean
to
be
perfectly
honest.
The
decision
for
me
was
just
going
to
be
through
an
overwhelming
majority
of
people,
and
I
think
that
that's
a
really
good
question,
because
the
problem
there
is
that
you
can
have
people
really
engaged
in
the
conversation
itself,
but
that's
very
different
than
like
a
majority
of
community
members
who
are
just
trying
to
use
IRC
or
slack
and
and
not
the
one,
send
the
decision
making.
So
I
think.
A
J
B
A
I
think
there's
a
couple
things
that
we
need
to
sort
of
tease
apart.
Here,
though
one
is,
the
board
needs
to
be
involved
in
where
we
allocate
time
and
resources
into
either
creating
a
new
channel
or
helping
support
an
existing
one.
The
second
part
of
this
is
that
there
is
an
existing
community
of
maintained,
errs
and
like
people
that
are
moderating
the
IRC
channel.
That
also
wants
support,
at
least
at
the
level
of
you
know,
moving
the
access
owner
from
being
Isaac
to
the
foundation
for
things
like
that.
So
maybe.
I
A
J
A
Right
so
yeah,
there's
like
I,
think
the
discussion
right
now
isn't
at
the
point
where
you
would
want
to
say
you
know
here
are
the
things
that
we
would
vote
on
or
here's
exactly
where
we
would
spend
our
time.
But
once
we
get
near
a
place,
we're
actually
going
to
need
some
input
from
the
board
on
how
the
resources
to
get
allocated
as
well.
Yeah,
okay,
yeah.
A
I
mean
people
more
than
funds.
I!
Don't
think
that,
even
if
we
wanted
to
pay
for
slack,
we
don't
have
the
money
to
pay
for
a
slack
the
size
of
which
we
expect
that
community
to
grow
because
paid
slack
is
per
user
and
it's
yeah.
If
you
compare
kind
of
our
community
to
any
of
the
other
programming
canoes
that
are
on
there,
you
very
quickly
reach
a
size
and
scope
that
the
weekend.
J
Yeah
we
actually
talked
to
so
I'm
trying.
I
am
in
the
midst
of
planning
a
call
with
another
programming
community
that
does
operate
under
slack
they've
got
about
12,000
members,
so
I'm
interested
to
hear
their
take,
but
we've
also
talked
to
I
think
another
foundation
who
had
attempted
the
paid
slack
and
it
was
extreme
yes
x.
It
was
not
a
fun
thing
to
watch
those
costs
or
so
yeah
we'll
see
but
yeah.
That's
it
on
that.
That's.
A
Okay,
cool
moving
along
we're
getting
into
the
2016
report
now,
so
this
is
something
that
we
compiled.
We've
been
trying
to
get
all
the
stats
together
of
you
know
how
we
did
in
2016
eventually
will
probably
work
this
into
like
a
really
pretty
document
that
we
can
share
out
more
or
publicly,
but
right
now
we
really
just
wanted
to
share
and
get
feedback
on
some
of
the
metrics
that
we
have
just
with
the
board
here.
So
first
in
2016
we
did
a
bunch
of
events.
A
D
D
A
E
A
D
A
D
A
We
have
a
lot
of
other
metrics
that
show
that
a
little
bit
better
though
so,
for
instance,
the
website
has
geographic
distribution.
That's
really
really
accurate
and
can
give
us
a
picture
into
like
areas
that
we
didn't
actually
do
an
event
in
so
yeah
we're
we're
compiling
all
kinds
of
data,
but
yeah
so
interactive.
As
you
can
see,
we
reached
about
726
in
Austin,
which
was
our
highest
event.
Any
other
questions
about
these
before
we
move
along.
F
H
What
are
we
going
to
determine?
What
are
we
gonna
set
the
target
for
how
big
we
want
Vancouver
to
be,
because
you
know
I
would
like
to
see
those
numbers
grow
well
over.
A
thousand
I
know
that
that
that
should
be
easy
if
we
know
so
the
line
things
avoid
conflicts
like
we
had
last
year
and
and
such
yeah.
A
So
so
the
upper
cap
of
what
we
can
do
was
sort
of
set
in
the
exploratory
phase
last
year
when
we
started
looking
at
venues,
because,
obviously
you
know
if
we
said
well
what
about
5,000
people
that
would
be
significantly
more
expensive
in
just
getting
a
venue
and
we
had
to
get
the
venue
last
year.
So
we
have
an
upper
end
of
psy
there,
eleven
or
twelve
hundred
for
dis,
your
venue
in
in
Vancouver,
but
the
real
target.
A
You
know
that
we're
confident
I
actually
think
that
we're
going
to
sell
it
out,
but
we'll
we'll
be
discussing
that
in
a
lot
more
detail
when
we
go
through
the
budget
and
we
go
through
some
of
the
targets
for
both
sponsorship
and
tickets,
which
were
discussing
in
the
private
session.
Just
this
meeting
and
then
we'll
have
some
information
in
the
public
session
actually
buy
in
two
weeks
for
the
februari
one.
A
I
These
are
yep
commits,
really
healthy
up
by
a
significant
amount,
largely
driven
that
this
we've
had
some
major
spikes
here.
That's
hardly
about
the
code
and
learn
events
that
the
Michael
champion
initially
but
were
taken
on
by
some
other
people
at
the
two
node
Interactive's
during
the
year,
particularly
the
one
in
in
Austin.
The
if
you
look
at
commit
grass,
is
just
this
massive
spike
and
that's
because
we're
this
huge
room
of
people
that
were
actually
actively
committing
to
core
and
really
enjoying
it,
and
we
saw
we
had
great
feedback
from
that.
I
The
thing
we
haven't
tracked
here
is
is
last
ability,
so
what
we
want
to
do
as
well
is
track.
Are
these
Wolf's
or
are
these
people
sticking
around
because
that's
that's
a
true
half
metric?
We
can
attract
people
and
show
them
how
easy
and
how
low
friction
it
is
to
get
involved,
and
you
know
it's
not
as
scary
as
as
as
you
might
think,
but
do
they
stick
around
and
keep
on
contributing.
I
I
Okay,
the
when
we
look
at
download
numbers
and
the
slope
of
adoption
curves
for
all
the
different
versions
of
know.
We
can
see
that
people
are
jumping
on
new
versions
of
TS
lines
and
we
do
the
others,
even
though
they
are
looking
up.
The
others
are
slowly
decreasing
a
little
bit
slower
than
the
right
we'd
like
to
see,
but
probably
in
line
with
expectations
of
how
software
gets
faced
out
of
the
time
anyway,
so
really
healthy
on
the
download
numbers,
so
we're
tracking
in
the
right
direction.
There.
I
We
have
closed
Corre
Caminos
now,
so
that's
people
who
have
committed
on
the
core
repo,
not
all
50
60
marks
that
are
active
in
the
last
few
months.
Even
but
a
hundred
people
have
committed,
and
when
you
look
at
the
the
number
of
commits
coming
from
those
contributors,
the
last
line
that
thinks
there's
less
than
half
of
the
core
changes
come
from
the
top
ten
contributors.
I
The
reason
that's
meaningful
is
that
that's
decreased
over
time
and
it
that
when
you
take
the
top
10
in
each
period,
you
would
expect
you
would
hope
that
to
be
decreasing
to
show
a
greater
spread
of
work
across
a
broader
number
of
people
entities
so
that
when
you
take
the
top
ten,
it's
less
than
same
time
last
year
by
quite
away.
So
if
the
loan
is
being
shared
a
lot
more
broadly
across
the
contributor
brace.
So
so
look
pretty
much.
All
of
the
metrics
have
been
out
to
choose.
I
4
2016
have
been
surprisingly
good,
exceeded
my
expectations
and
hopes
and
to
the
point
where
what
we're
interested
in
now
is
digging
deeper,
deeper
into
finding
fearing
out
the
nature
of
the
quality
here.
So,
as
I
said,
with
the
commutes,
are
these
people
sticking
around
so
2017
will
be
about
understanding
better,
whether
these
numbers
we're
seeing
instead
of
just
being
proxies
for
good
measurements,
whether
they
are
actually
good
measurements?
So,
hopefully,
we'll
have
better
details
for
you
later
on
and
it
just
on
top
of
this
as
well.
A
Alright,
so
let's
look
at
adoption,
so
we
doubled
again
Michael.
H
Sorry
I
keep
jumping
ahead,
unmuting
it
like
Ed's
as
you're.
Moving
on
the
next
section,
so
a
question
rod
is
you
know
how
now
that
we've
sort
of
successfully
maintained
gross?
Are
we
beginning
to
have
a
better
sense
of
what
what
the,
what
the
things
that
we're
doing,
that
that
will
help
us
continue
to
achieve
that
growth
are.
I
No
I
think
and
that's
our
challenge,
I
think
that's
the
challenge
for
the
board.
It's
a
challenge
for
the
TFC
and
and
the
various
community
groups,
so
we
I
think
we
said
this
last
year
as
well.
We
we've
succeeded
by
default
because
we
really,
we
simply
reinvigorated
the
health
of
the
project
by
making
excitement
around
contributing,
and
we
made
it
feel
like
more
exciting
project.
It
was
progress.
We
were
dropping
new
features.
We
were
people
who
are
excited
about
staying
up
to
date,
with
es
6
and
7,
etc,
etc.
I
So
notice
it's
healthy
by
default,
not
necessarily
because
of
what
we've
been
doing,
particularly
at
a
foundation
level.
So
the
challenge
now
for
the
board
I
think
this
is
going
to
be
something
they're
going
to
be
have
to
be
a
topic
at
the
the
next
board
meeting
the
in-person
one.
What
are
the
things
that
we
need
to
be
doing
that
maintain
and
potentially
increase
this
adoption
and
the
health?
So
what
do
we
need
to
understand?
We
talk
about
is
light
at
last
meeting.
What
an?
I
A
Also,
I
mean,
I
think,
that
the
data
that
we're
going
to
get
from
code
and
learn
going
forward
is
going
to
give
us
a
lot
of
input
on
whether
or
not
that
particular
thing
works
and
keeps
people
around,
which
is
great,
because
that's
one
of
the
more
proactive
efforts
that
we've
done.
That
is,
that
is
new
from
when
we
started
the
foundation.
A
We
know
that
the
initial
governance
model
that
we
set
up
and
bringing
things
under
a
foundation
led
to
this
large
increase
in
contributors,
but
we
basically
maintained
that
that
rate
of
adding
contributors
since
then
with
maybe
a
slight
uptick
from
100
to
125
percent,
and
maybe
that's
due
to
code
and
learn.
But
we
need
better
data
to
tell
us
exactly
why.
A
I
A
Did
they
call
it
it
basically
just
a
build
/
nodejs
and
they
saw
an
eighty-seven
percent
increase.
The
reason
that
I
think
that
that's
probably
not
a
hundred
percent
is
because
they
did
remove
support
for
0
10,
so
that
probably
led
to
a
slight
drop
off
in
q4
in
how
many
they
were
doing.
But
that
is
also
great
for
us
that
they
deprecated
10
and
that
we're
you
know
forcibly
removing
people
from
0
10.
A
That's
phenomenal,
we're
up
to
about
15
million
cord
downloads
at
months
the
debt,
the
download
rates,
are
growing
faster
than
any
of
our
other
metrics,
and
that's
because
we're
we're
doing
more
releases
consistently,
but
also
just
adoption
of
releases
is
getting
better.
We
can
see
that
in
all
the
data-
and
that's
that's
so
great-
you
know
it
means
that
our
long-term
maintenance
burden
is
going
down.
You
know
it
means
that
we
get
to
dedicate
kind
of
less
resources
over
time
to
you
know
long
maintenance
releases
and
that
kind
of
stuff.
So
that's
all
fantastic.
I
So
people
know
that
that
when
they
hop
onto
a
new
major
release
line
that
it's
going
to
be
stable
for
them
in
production
and
then
particularly
when
were
lit
when
security
releases
come
out,
that
it's
going
to
be
minimal
and
not
risky,
so
we've
we've
really
reduced
the
sense
of
risk
and
increase
the
sense
of
trust
around
core.
So
and
that's
something
that's
ongoing
work,
but
I
think
you
know
you
need
to
congratulate
the
folks
that
have
been
putting
in
the
most
work
there.
So
they
get.
A
Yeah
and
even
beyond
LTS,
like
even
our
new
major
releases
that
are
not
going
into
LTS,
have
seen
increases
in
adoption
each
time
that
we
do
them
not
to
the
level
that
LTS
does
we're
doing
much
better,
even
there
than
even
the
other
one,
but
even
you
know,
are
more
bleeding
edge.
Stuff
is
getting
used
by
more
users,
so
that's
great
to
see
as
well
cool,
okay.
So,
let's
get
into
some
of
the
internal
stuff.
So
social
we've
seen
huge
increases
in
social
we've
added
a
hundred
thousand
followers,
which
is
awesome.
A
We
have
over
400,000
now
we've,
so
our
followers
only
went
up
thirty
four
percent,
but
our
mentions
win
up
two
hundred
fifty
five
percent.
Our
engagement
is
up
three
hundred
percent,
so
not
only
you
know,
are
we
increasing
our
direct
followers,
but
the
way
that
we
use
the
channel
is
getting
a
lot
more
traction
than
ever
before
and
it's
becoming
this
vehicle
for
us
to
really
be
able
to
get
anything
done
better.
If
we
need
attention
on
any
particular
type
of
issue,
if
we
want
to
get
people,
you
know
it
engaged
in
a
new
topic.
A
D
Yes,
so
I
think
one
thing
I
think
I
would
be
genuinely
interested
in
is
figuring
out,
like
those
mentions
how
many
of
them
come
from
people
who
are
like
designated
leaders
in
the
community
like
say
Tracy
or
me.
If
we
could
like
go
through
and
figure
out
how
many
of
those
are
actually
coming
like
from
us
out
versus
how
many
are
actually
coming
in
I.
D
Think
that
would
give
us
a
little
bit
more
of
an
understanding
on
those
numbers
because
I
mean
I,
certainly
know
that
I've
been
like
AB,
mentioning
us
a
lot
on
Twitter
sense
and
so
to
find
out.
If,
if
it's
that,
we're
using
it
more
as
an
organization
or
we're
actually
getting
more
in
found,
metrons,
which
this
number
can't
really
tell
us
at
the
moment,.
K
Hey
Ashley,
Mississippi
I'm
happy
too
soon
analysis
and
try
to
find
that
just
based
on
like
when
I
look
at
the
report,
I
mean
a
ton
of
our
tweets
come
from
the
leaders
on
it,
but
we
also
are
getting
like
tweets
from
people
outside
of
a
leadership
too
so
I
10
in
our
next
reports,
going
forward
just
kind
of
do
a
breakdown
of
what
that
looks
like
how
many
are
coming
from
leadership
versus
just
the
general
community.
Yeah.
D
That's
super
awesome.
I
mean
part
of
the
insight
that
I'd
like
to
see
in.
That
is
that
if
the
leadership
increases
that
the
mentioning
of
node
do,
we
actually
see
that
have
a
positive
influence
on
other
people
like
coming
in
and
also
starting
to
do
that.
If
so,
it's
like
useful
at
all
as
something
as
someone
who
uses
Twitter
to
communicate
a
lot
I'd
be
interested
if
it
actually
has
perfect.
D
I
D
A
Yeah
so
on
hand
also,
like
I,
don't
know
the
spread
between
leadership
and
inbound,
but
I
do
know.
The
inbound
is
way
up
because
it's
becoming
kind
of
a
maintenance
burden
and
we
need
it
ends
at
me-
needs
help
and
we
need
to
figure
out
a
way
to
to
get
the
community
involved
and
creates
an
FAQ
is
for
some
of
the
more
common
questions
that
come
in
bounds.
A
D
A
A
We
had
a
hundred
and
forty-one
thousand
views
and
eighty
one
reads
in
our
Channel:
it's
how
great
that
they
measure
the
difference
between
two
views
and
reads
so
that's
great.
It
means
that
you
know
we're
getting.
You
know
as
much
traction
in
our
own
channel
as
we
could
expect
from.
You
know
a
lot
of
outside
channels
that
we
do.
A
We
also
do
a
lot
of
work
to
try
and
get
access
to,
but
this
is
just
really
really
good
to
see
you
tube
is
also
way
way
of,
mainly
just
because
you
know
we're
getting
more
content
into
it.
We
did
more
events,
so
we
had
more
videos
to
put
in
and
as
well
as
the
fireside
chats
kind
of
keep
a
you
know
rolling,
constant
parade
of
people
coming
in
as
well.
As
you
know,
it's
really
nice
to
have
so
much
transparency
around
how
the
project
works
and
having
all
the
project
videos
go
in
as
well.
D
A
A
Actually,
you
should
already
be
able
to
access
it,
so
I'll
give
it
to
you,
but
I
can
actually
how.
D
Yeah
I
mean
I
just
think
it
would
be
really
interesting.
My
hunch
is
that
the
numbers
regarding
our
meetings
on
transparency
are
significantly
lower
than
the
numbers
on
the
conference
talks
and
like
maybe
trying
to
figure
out
how
we
promote
one
versus
the
other,
and
you
know
the
content
in
each
would
be
useful
action
item
for
making
these
more
accessible
and
honestly
more
interesting
to
the
people
watching
also.
A
It's
worth
noting
that
we
do
know
that
you
know
not.
A
lot
of
people
watch
live
either
this
meeting
or
some
of
the
other
meetings
that
we
do,
but
a
fair
number
of
people
do
go
to
the
meetings
later
and
and
look
at
them.
You
know
after
the
fact,
so
the
fact
that
we
we
have
archiving
and
that
we're
not
only
live
streaming
is
actually
really
important
and
we
give
you
a
lot
more
engagement
that
way.
I.
D
G
Just
say
odd,
maybe
not
oddly,
but
for
the
YouTube
videos,
all
of
the
netflix
videos
are
higher
views
than
pretty
much
everything
else
so,
for
whatever
reason,
maybe
they're
pushing
people
that
way.
So
it
really
wishes
a
lot
of
those
numbers
up
on
just
that
topic
along
that
company
along
or
something.
A
I
think
it
is
actually
also
what
they
talk
about,
so
we
know
from-
and
you
can
see
this
in
the
other
survey
that
we
just
did
and
even
some
of
the
last
year,
but
we
see
a
really
high
demand
for
developer
tools,
monitoring
that
kind
of
content
and
there's
not
a
lot
of
people
actually
doing
talked
about
the
content.
But
netflix
consistently
gives
talks
about
that.
So
that's
probably
one
of
the
reasons
why
they
have
so
much
traction.
A
A
In
total
sales
we
had
about
48
orders
go
through
and
we're
we
may
have
a
a
conference
actually
buy
out
the
rest
of
the
stock,
which
is
probably
good
because
we're
considering
a
different
vendor
for
the
sum
of
the
fulfillment
end
of
things.
We
like
the
store
we
just
were.
We
don't
know
how
we
feel
yet
about
the
the
fulfillment
service.
So
that
may
happen
any.
D
Questions
about
this
are
those
numbers
regarding
the
the
men's
shirts.
D
B
A
B
A
B
A
A
D
I
there
was
not
any
very
specific
questions.
The
discussion
did
definitely
talk
a
bit
about
the
community
committees
proposal
of
a
new
channel,
like
kind
of
I
receiver
to
slack,
and
they
brought
up
get
ur
and
they
were
kind
of
talking
about
moderation,
stuff,
and
so
that
was
very
interesting.
They
had
within
their
own.
They
were
chatting
about
a
couple
of
different
things.
We
got
some
people
listening
from
a
bunch
of
different
countries
to
which
is
neat.
I
do
not
see
other
questions
again.
There's.
D
D
D
A
A
Okay,
so
primarily,
we
rely
on
the
top
level
NPM
number
that
they
have
for
a
30-day
engagement,
but
we
also
track
against
some
other
metrics
that
we
have
on
just
the
growth
of
the
ecosystem.
Generally,
the
growth
of
our
downloads.
We
look
at.
We
look
at
a
bunch
of
different
ones
so
that
if,
if
something
else
was
leveling
off,
an
MPN
still
showed
a
big
increase.
We'd
question
the
number
a
bit
more
yeah.
D
D
A
D
Also,
thomas
is
that
he
uses
the
Travis
owed
attend
every
day,
so
for
what
it's
worth,
that's
probably
a
little
out
of
scope
for
this
meeting,
but
we
should
probably
follow
up
on
it.
I'll.
C
A
Okay,
well,
if
that's
it
motion
to
close
motion.