►
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
C
D
I
posted
in
the
thread,
I
think
there's
some
way
to
like
live
broadcast
to
youtube
without
like
using
hangouts,
but
I'm
not
sure.
If
that's
like
available
to
everyone
or
anything
full
conference,
I
know
for
hangouts
and
then,
if
someone's
in
the
call
they
don't
need
to
be
in
a
call
for
hangouts
okay,
so
you
can
call
them
there's
something
in
a
min
live
broadcast.
It.
B
D
B
C
D
Sorts
yeah,
I
have
I've,
not
updated
my
stuff,
as
I
really
have
an
ID
timer
energy
to
do
that.
I
still
thinking
about
I,
still
think
thinking
about
how
projects
that
might
be
applying
sort
of
fit
into
the
story
of
where
node
is
today
is
probably
like
a
good
good
basis
and
also
like
where
it
might
be
in
the
future.
Yeah
I.
E
D
D
B
B
Why
do
we,
as
the
TSA
think
the
Foundation
exists,
what
what
it
means
to
assist
node
and
help
not
grow?
If
that's,
you
know,
that's
why
it
exists.
What
that
means,
and
then
from
there,
how
do?
How
do
we
judge
projects
to
bring
in
to
align
with
that
mission?
So
I
think
we
can
all
take
it
from
different
ways,
but
Jeremiah
I'm
bunking
to
help
you
and
your
attempt
to
do
my
stories
based
approach.
E
I'm
not
good
against
the
story
based
approach,
but
I.
Don't
think
that
we,
we
cannot
have
some
sort
of
guidelines,
I
mean
maybe
they're
not
hard
guidelines.
So
it's
not
like
a
piece
of
code
that
says
this
project
gets
in
this
project
doesn't
but
try
to
write
down
somewhere.
What
are
some
indicators?
I,
for
example,
Libby
was
a
uncontroversial
because
we
have
a
dependency
on
so
whether
we
have
a
dependency
on
a
project
is
one
of
the
criteria
that
could
be
included
in
the
guideline.
D
C
So
yeah
throw
a
few
extra
little
things
in
here,
so
I
mean
like
the
node
foundations
mission
is
already.
You
know,
support
the
health
and
stability
of
that
said
like.
If
we
were
to
take
on
every
project,
we
would
probably
destabilize
the
toe
ecosystem
right,
there's
something
to
be
said
about
being
like
focused
on
things
that
are
somewhat
restructure,
all
like
to
the
rest
of
the
ecosystem.
What
will
the
interesting
things
that
I've
noticed
through
the
Express
process
as
the
change
pretty
dramatically,
especially
after
Doug
Wilson,
put
all
of
his
projects?
C
It
is
that
we
didn't
just
take
on
like
Express
as
a
project
that
people
directly
been
done
or
use
Express.
It's
actually
also
the
infrastructure
for
remote
of
web
frameworks
in
general,
and
so,
if
you
look
at
the
the
overall
impact
and
importance
of
it,
it's
beyond
as
people
that
npm
install
express
it's
like
all
of
these
other
projects
and
depend
on
it
and
as
as
that
project
is
in
the
foundation,
grows.
If
something
related
to
that
word
of
coming
to
the
foundation,
it
wouldn't
come
in
at
the
state
level.
C
F
I
think
I'm
like
I
agreed
with
rod
and
that
we
really
like
this
philosophical
discussion
about
like
ride
as
a
foundation.
Yes,
but
I
think
if
I
frame
it
for
myself
there's
a
much
more
practical
issue,
which
is
more
projects
like
mean
more
responsibility
to
me
and
that'd
be
fine
if
I,
if
I
gave
a
really,
you
know,
I
care
deeply
about
no
tonight
I'm,
very
convinced
that
Express
is
very,
very
important
for
node
and
get
me
V.
F
Obviously,
but
I
don't
really
care
about
akhiyan,
so
it
probably
probably
be
better
if
it
didn't
end
up
on
my
plate,
so
I
think
for
the
foundation
it
like
the
question
becomes,
you
know:
do
you
want
to
be
a
group
of
people
that
care
about
a
particular
thing,
or
do
you
want
to
be?
You
know
a
shelter
for
open
source
projects
in
general?
You
know
much
like
a
fat
chief,
for
example.
C
People
are
pretty
freaked
out
about
the
Apache
eclipse
thing
like
us
becoming
that
large
in
scope
and
like
even
if
we
said
you
know,
we
only
take
projects
there
in
node.
That,
eventually,
is
basically
everything
like
our
growth
is
way
too
ridiculous.
To
likely
have
that
be
the
criteria
hey
like
it
would
just
end
up
being
as
big
as
a
catcher,
and
so
there's
this
real
question
of
like
how
do
we
court,
like
I,
get
what
you're
saying
about
like
this
matter,
but
I
do
think
the
meaning
to
be
a
little
more
broad
than
like.
C
F
So
I
mean
I
don't
I
don't
agree
with
you
or
parallel
like
I,
in
a
way
care
about
serial
port
to,
but
that's
mostly
because
I,
you
know
I
feel
responsible
for
a
load,
no
delivery.
Dozen
and
robots
are
like
big
users
of
hours
and
I
want
them
to
be
successful,
but
I'd
like
with
a
peon
that
distinction
is
much.
You
know
that's
much
further
away
from.
You
know
what
I
feel
to
be
responsible
for
I'm,
not
saying
that
this.
F
You
know
what
bird
things
or
what
Britt
cares
about
should
be
the
norm
for
what
the
foundation,
except
don't
get
me
wrong,
but
like.
If
can
you
make
sure
that
the
right
people
end
up
having
the
right
amount
of
control
over
the
project?
I
think
that
would
be
much
more.
It's
a
much
more
practical
question
to
answer
and
I
think
if
you
get
that
right,
there's
no
real
objection
from
my
site
anyway.
Well.
C
What
what
I'm
trying
to
figure
out
right
is
like
if
we
so
we're,
basically
asking
ourselves
these
questions
right
now,
which
is
like,
can
we
admit
a
p.m.?
Can
we
admit,
node
calm
and
we
need
to
answer
those
in
a
way
that
is
not
like.
Burt
doesn't
care
about
this,
but
it
and
like
you
know,
we
try
to
quantify
the
impact
that
something
has
in
this
in
this
way.
G
I
guess
it's
I'm
thinking
it
comes
down
to
if
whatever
the
project
is
didn't
exist,
would
it
hurt
no
yeah
good
one?
Actually,
you
know
like
a
serial
port
didn't
exist,
the
answer
you
know
what
we
probably
yes,
because
you
couldn't
do
a
bunch
of
things
and
Express
I
think
the
answer
is
yes
as
well.
A
PM
I,
don't
know
well
enough.
I
did
this.
If
it's
the
one
that
everybody
used
to
test
all
of
their
node
apps
and
without
it
you
know,
test
would
fall
apart.
E
As
far
as
I
understand,
opium
is
the
farthest
removed
from
being
aligned
with
with
a
successful
ojs
itself,
in
that
it's
intended
users
to
test
mobile
apps.
So
they
also,
you
will
testing
up
your
more
apps
weakening
objective-c
and
then
it's
he's
got
a
survey
nodejs
somewhere,
but
it's
not
really
used
by
nodejs
developers,
necessarily
yeah.
F
My
feeling
I
mean
I
can
practice
a
bit
by
any
numbers
with
its
early,
not
the
predominant
test
framework
in
ojs
or
even
a
contender
to
that.
So,
if
it
didn't
exist,
what
would
the
impact
vid
was
well
c
sharp
G
sharp
developers
would
have
a
like
a
harder
time
or
objective
c
developers
would
have
a
harder
time
testing
your
mobile
apps.
B
Will
even
closer,
we
could
ask
the
same
questions
about
grunt
and
gulp
that
they
they
are
essentially
supporting
front
end
and
for
the
most
part
that
people
do
use
it
on
back
in,
but
that
that's
where
they're
most
popular
and
that's
where
they
had
most
value,
but
it
does
actually.
That
is
a
primary
use
case
of
node
tooling,
it's
a
primary
use
case.
B
C
Lines
like
that,
I
totally
agree,
but,
like
those
are
questions
that
we
sort
of
ask
ourselves
when
we're
evaluating
it.
What
I'm,
mostly
looking
for,
is
like
questions
that
we
can
ask
a
project
when
they're
being
admitted
that
are
not
this
objectives
that
are
like
questions
that
would
get
at
the
heart
of
like
how
relied
upon.
C
Is
this
technology
right,
like
like,
like
difference
between
grunting
gulp
and
like
express,
is
that
Express
starting
to
break
into
a
lot
of
components,
and
it
started
to
become
this
infrastructure
for
every
other
new
curve
of
adoption
in
web
frameworks
right,
whereas
grunting
dope
has
their
own
individual
curves
of
adoption,
but
there's
always
a
new
thing
and
that
new
thing
isn't
building
on
any
of
the
shared
infrastructure
between
grunt
and
gulp,
necessarily
but
like?
How
do
we
call?
How
do
we?
C
C
Well-
and
it
may
be
that,
like
you
know,
the
constraints
that
we
operate
under
under
the
tsc
are
a
little
bit
too
specific
to
like
IP
policy
and
code
that
we
can
admit
something
like
that,
and
we
just
need
to
answer
that
question
like
India.
If
the
answer
is
the
tsc
can't
take
that
in,
but
the
foundation
should
do
something,
then
we
can
try
to
find
an
alternative
way
for
the
foundation
to
take
that
end,
not
under
the
tsc
and
that's
okay.
G
Now,
a
bunch
of
the
question
we
could
ask
would
be
lost.
I
was
just
going
to
say
a
bunch
of
the
questions
it
rotted
had
praised,
apply
equally
to
something
like
the
conference's
as
they
do
to
the
specific
technology
you
know.
Does
it
help
grow?
You
know?
No
does
it
does
it
depended
on
her
information
that
kind
of
stuff?
So
it's
interesting
that
you
know
that
one
in
particular
does
fit
into
those
some
of
those
questions.
B
We
could
ask
open-ended
questions
of
projects
when
they're
coming
in
and
let
them
responding
proposal
with
numbers
of
who
they
choose
to
respond.
But
things
like
how
does
your
being
in
the
node
foundation
support
the
note.
The
existing
node
ecosystem?
How
does
your
being
in
the
node
foundation
grow
the
grown
node
adoption
so
ask
those
questions.
Let
them
respond
because,
because,
like
with
a
p.m.
the
fact
is
I
think
important.
Happy
m
is
out
there
and
perhaps
is
actually
really
vital,
and
we
just
don't
see
that.
B
So
if
we
give
them
the
opportunity
to
make
that
case
and
then
it
gives
us
insight
into
another
eat,
we
don't
necessarily
have
really
enjoyed
it
too,
because
and
I
think
that's
something
the
Michael's
been
struggling
with
as
well,
which
is
that
we're
all
extremely
focused
on
core
and
we
have
a
huge
down
in
core
and
when
not
actually
that
bullet
between
across
the
VA
system
and
understanding
the
things
that
are
becoming
important
to
you
and
that's.
That
is
an
important
point
that
we
need
to
be
at
YouTube,
and
we
can.
B
D
It's
like
framework
like
and
has
nothing
to
do,
really
wouldn't
know
it,
except
maybe
we
serve
ap
ice
to
it
or
something
like
I'm,
not
I,
don't
think
that
would
really
fit
cuz.
That's
not
really.
The
focus
like
I've
us,
like
there'd,
be
something
like
the
jQuery
foundation
that
or
something
like
that.
It's
like
a
more
front-end
focus
thing
that
would
be
that
I
think
something
like
that
would
be
better
suited
in
so
yeah.
I.
C
B
C
These
questions
are
like
what
is
the
value
of
the
incubator,
the
whole
process
of
bringing
projects
on
the
foundation,
and
what
are
we
not?
What
are
we
trying
to
accomplish
there
that
week,
can't
just
accomplished
by
like
publishing
these
new
contribution
policies
that
were
a
dreadful
or
you
know,
even
paying
people
to
speak
about
those
and
trying
to
like
proliferate.
A
lot
of
these
ideas
outside
of
hosting
the
projects
sara
lee.
B
Okay-
maybe
we've
exhausted
this
for
now,
and
we
need
to
each
carve
out
some
time
during
our
week
to
think
at
this
level,
because
I
know
most
of
us
a
heads
down
in
a
core
which
is
becoming
increasingly
busy,
as
actually
I've
been
showing
this
with
both
Michael
and
James,
that
our
numbers
for
contributions
are
going
through
the
roof
and
consistently
like
the
last
two
months.
We've
broke
records
on
the
number
of
unique
program
contributors
per
month.
Our
number
of
commits
per
month
is
steadily
rising.
B
All
of
the
metrics
are
basically
just
just
going
up
and
showing
know
what
I
mean
and
I
think
that
means
that
we're
all
those
of
us
sort
of
head
down
heads
down
in
core
are
just
completely
absorbed
with
everything
that's
going
on,
and
we
need
to
try
and
find
time
during
our
week
to
set
aside
to
thinking
about
things
at
this
level
so
that
we
can,
you
know,
cause
going
pretty
well.
So
how
about
we
think
more
about
how
to
make
node
itself
go
even
better.
So
note
is
a
ecosystem
in
the
community.
B
F
But
that
sounds
good
next
week.
I
won't
be
here,
go
yes,
sir.
This
is
mainly
a
question
for
Michael.
Is
there
like
the
deadline
or
a
perk
like
target
date,
for
when
we
have
to
make
a
decision
about
a
peon
or
you
have
the
feeling
there
get
like
impatient
and
never
in
say
nevermind?
What
do
you
think.
C
H
C
But
also
there
are
other
projects
that
are
signing
up
now,
so
sorry,
but
getting
a
lot
of
emails
in
the
background
about
projects
that
want
to
come
on
board
and
to
be
proven,
they
honest
a
lot
of
them.
We
probably
don't
want
to
take
on
this
syrup,
so
I
think
that
would
have
been
telling
them
right
now.
Is
that
we're
not
taking
anything
for
at
least
a
month
until
we
figure
xpress
out
and
at
that
point
we'll
have
much
better
documentation.
F
G
B
C
Okay
and
will
suffer
for
the
questions
and
stuff
like
we
need
to,
like
all
once
we
start
to
figure
this
out,
I'll
sit
down
and
write
them
up,
but
we
should
really
update
the
documentation
for
applying
and
update
the
list
of
things
that
we're
asking
them
there.
So
we'll
have
like
better
documentation
and
more
quantifiable
documentation
and
I.
Think
a
slight
reorganization
that
the
tsc
repo
is
probably
I'm
going
to
need
a
pin
as
well.
G
C
C
Once
we
have
that,
that's
essentially
a
guideline
for
what
the
shape
that
we
want
to
try
to
get
the
IP
into
before
we
graduate
anything
out
of
the
incubator
and
I'm
gonna.
Try
to
write
a
lot
of
automated
tooling
to
figure
that
out
because
across,
like
you,
know,
100
repos,
on
on
three
orbs
for
express,
like
it's
just
not
going
to
work.
To
try
to
manually.
Do
any
of
this.
So
there's
we're
going
to
learn
a
lot
through
that
process
as
well.
C
D
Really
do
it
at
the
start,
so
yeah,
so
we're
trying
to
organize
a
meeting
right
now,
although
it's
a
little
bit
hard
with
everyone's
times
and
I,
don't
think
Doug
can
work
can
do
the
meeting
during
work
hours,
so
that
makes
it
a
little
bit
more
complicated
to
have
a
part
of
your
different
time.
Zones
involved.
Yeah.