►
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
Everyone
I
am
a
telco
Lina
and
today
I'm
going
to
talk
to
you
about
community
frameworks
because,
yes
in
the
JavaScript
community,
we
really
like
frameworks
and
maybe
a
little
bit
of
my
personal
history,
but
probably
not
you
don't
care,
but
I
think
that
I
can
I
have
a
story
to
tell
anyway,
if
you
have
some
time.
Please
follow
me
on
Twitter
it's.
You
know,
I
tweet,
about
open
source
things
and
JavaScript
so
yeah.
Maybe
you
would
find
it
interesting.
A
So,
let's,
let's
jump
into
it
long
time
ago,
I
was
I,
wanted
to
be
an
open
source
developer
and
you
know
it
was,
and
I
tried
very
hard
and
I
built
things
with
Ruby
with
CoffeeScript
with
nodejs
JavaScript
I.
You
know,
I
was
I
tried
very
much
and
I
tried
very
much
to
become
an
open
source
developer.
I
really
wanted
I
really
really
wanted
to
do
it
and
yeah
I,
don't
know
I,
don't
know,
I
didn't
go,
he
didn't
go
really!
Well,
you
know
it's.
A
One
of
the
key
things
that
I
wanted
to
do
was
to
build
open
source
to
other
developers,
build
build
amazing
things
and
yeah.
This
was
one
of
the
greatest
stuff
that
you
know.
I
wanted
to
I
really
felt
I
wanted
I
wanted
to
do
this
and
I
wanted
12,
publish
other
developers,
building
software
and
probably
don't
feel
as
mihrab
miserable
as
I
felt
when
I
started
and
scrum
I
don't
know
something
like
that.
A
little
bit
of
the
success
came
when
I
Mosca
in
13.
At
that
point,
in
time
I
was
I
was
doing.
A
Essentially,
it's
as
part
of
my
PhD
I
was
researching
things
on
the
Internet
of
Things
and
I
needed
a
very
flexible
and
DT
broker.
Mqtt
is
you
know
fantastic
project?
Checkout
note
read
as
well,
so
hey
we
are
part
of
the
same
kind
of
family
and
when,
when
I
was
developing
this
this
broker,
you
know
I
I
made
few
mistakes.
The
first
one
was.
It
was
a
completely
unmaintainable,
really
maintainable
architecture.
Internally,
I
made
some
mistakes.
I
didn't
know
how
to
structure
a
large
and
successful
nodejs
application
back.
A
Then
it's
also
I
never
spent
enough
time
in
in
automation
and
in
making
sure
CI
was
stable.
This
was
actually
really
problematic,
especially
if
you're
building
a
distributed
system
working
in
distributed
systems-
and
this
is
really
really
critical.
I
didn't
spend
any
effort
in
building
a
community
of
maintainer
I
wanted
to
retain
ownership
of
the
project
and,
however
it
it
really
gotten
some
nice
traction
and
it's
and
with
it
there
was
I,
don't
know.
A
Maybe
I
can
I
thought
well,
you
know,
even
though
I
did
this
as
part
of
my
GED,
maybe
I
can
make
some
money
out
of
it.
You
know
I
can
help
me
it
can
help
me
grow.
My
career,
however,
I
had
no
real
funds.
I
didn't
want
to
raise.
Much
was
not
much
of
venture
capitalists
in
Italy
back
then
not
that
there
is
much
now
what
a
little
bit
things
a
little
bit
better
and
the
project
essentially
failed.
It
was
a
galactic
failure
for
for
a
few
reason.
A
Well,
the
main
reason
was
that
you
know
I
built
a
master,
and
this
monster
was
as
too
many
dependencies
really
too
many.
It
was
doing
too
many
things.
It
was
not
modular.
It
was
night
with
that.
No
community
and
I
thought
it
was.
It
was
a
mirror.
I
was
a
Nero
and
I
could
development
in
the
software
and
make
it
great,
which
turns
out
the
case.
That's
not
our
open
source,
that's
not
our
open
source
work
and
you
know
that's
it.
So
what
can
we
say?
A
We
got
another
color
and
they
packaged
it
up
and
sold
it
to
very,
very
large
company
for
tens
of
millions
and
none
of
the
three
people
that
I
mentioned
actually
made
any
money
about
this
yeah.
These
didn't
really
go
well
for
my
four
mice.
For
for
myself,
really,
in
fact,
whenever
this
niche
was
developing
and
when
it
was
creating
to
develop
some
of
the
some
of
you
know,
the
project
was
growing
a
little
bit
and
it
had
a
community.
He
started
to
have
at
the
beginning
of
a
community.
A
Maybe
people
you
know
started
complaining
and
they
started
saying
well
I'm
going
to
stop
using
this,
your
library,
because
you're
not
fixing
this
bug.
This
was
actually
really
really
bad
and
it
was
like
it
felt
really
bad
I,
don't
know.
I
felt
bad
I
was
like
I
was
completely
and
utterly
destroyed
by
by
that
by
that
sentence,
which
is
very
strange
right.
Why?
Well,
you
know
why
nobody
is
appreciating
what
I'm
doing
why
they're
not
they're,
not
you
know,
I
try
to
help
the
community
I
try
to
help
people.
A
Why
I'm,
not
you
know,
being
successful
at
all?
Well
and
then
I
started
following
in
in
in
a
bed
trap,
which
is
mostly
called
the
impostor
syndrome.
You
know
in
in
many
challenges
we
can
be
personal,
professional
professional.
We
are
l
beg
by
the
cripton
thought
that
people
like
us
could
not
be
successful
and
you
know
it's.
A
I
thought
you
know
other
people
can
do
it
because
they
are
special
or
great
and
essentially
better
than
me
because
of
whatever-
and
you
know
this
kind
of
what
happened
and
in
fact
the
reality
is
that
you
know
any
of
that.
That's
not
there's
not
such
a
thing.
You
can
know
something
you
can
have
something
to
say
in
the
world.
A
Believe
me
yourself
and
in
fact
you
know
the
key
thought
that
resonated
well
with
me
was
and
I
started,
asking
myself
the
question:
if
we
I
was
just
building
software
for
myself-
and
these
was
you
know
who
am
I
doing
this
software
for
well
I'm,
not
you
know
it
is
I
want
to
improve
the
experience
for
other
people.
Others
I
want
others
to
enjoy
my
software.
So
it's
it's
really
really
tricky
and
it
comes
for
love
with
a
large,
a
responsibility.
A
To
be
honest,
because
there's
a
lot
of
other
things
that
you
know
are
required
for
open-source
to
be
successful,
you
need
a
product
strategy.
You
need
documentation.
You
need
to
have
a
developer
experience
on
the
product
before
developers
that
are
contributing
to
the
project
itself.
You
need
to
have
a
delivery
strategy.
You
need
to
have
long-term
support
semantic
versioning,
a
lot
of
things,
people
really
like
one
dot
or
dot.
Oh
by
the
way
and
two
dot
order
you
need
to
have
licensing.
You
need
to
have
reliable,
towing,
tooling,
including
CI.
A
A
Apparently
I
was
a
fool
and
you
know
there
was
zero
chances.
I,
don't
know
what
to
say,
but
that's
there
that's
reality.
So
one
of
the
things
that
that
you
want
to
do
is
you
might
want
to
think
well.
I'm
I,
just
I
can
just
do
a
start-up.
I
want
to
do
a
startup
to
convert
to
to
make
sure
that
the
mic
my
project
is
safe
and
by
creating
an
economical,
a
company
behind
it.
I
can
make
sure
that
it's
safe
and
successful.
Well,
you
know
having
a
successful
stop
is
art.
A
A
Well,
the
question
that
you
want
to
ask
is
that
if
there
is
another
way,
is
there
another
way
where
you
can
target
when
you
can
be
successful
and
create
something?
Well,
you
know
there
is
and
an
open-source
project
is
as
good
as
its
crew
as
it
is
its
community,
which
is
really
really
really
really
critical.
A
So
the
only
thing
you
need
to,
if
you
are,
if
you
care
about
your
open-source
project,
and
if
you
want
to
build
an
open-source
project,
you
only
need
to
care
about
your
community.
Who
is
your
community?
What
are
you
talking
to
that's
what
you
should
care
about
and
where
you
should
talk
so
well,
let's
see,
let's
try
again,
let's
tell
another
story
and
let's
see
what
can
do
we
can
do
differently
now,
okay,
so
back
in
2013.
A
At
this
exact
same
time
when
I
was
developing,
Mosca
I
also
built
another
product,
another
library
called
level
graph.
I,
don't
know
you
probably
don't
remember
this,
you
shouldn't
okay,
the
type
of
research
should
have
been
done
in
for
developing.
This
thing
ended
up
spreaded
all
around
the
world
for
other
interesting
things,
so
I
don't
care,
but
what
happened
is
that
this
is
level
graph.
Was
a
nice
graph
database
built
on
top
of
level
up,
which
is
a
wrapper
for
level
2b
by
the
way
level
up
is
phenomenal.
You
should
check
it
out.
A
A
Wrote
about
open,
open
source
and,
and
he
stated
that
individual
making,
significant
and
valuable
contributions
are
giving
the
committee
access
to
the
projects
to
contribute
as
they
see
fit.
This
is
critical.
This
is
how
you
grow
community.
This
is
how
you
open
it
up
and
you
enable
others
to
join
the
project.
A
A
However,
every
collaborator
can
nominate
somebody
else,
so
a
nominee
and
the
nominees
should
have
significant
and
valuable
contributions
across
the
node.js
organization.
Those
are
two
excerpt
from
the
node
governance.
The
node
governance
is
such
a
big
file,
so
you
should,
you
might
want
to
you,
might
want
to
check
it
out
and
and
read
a
little
bit
more,
but
it's
actually
very
an
interesting
read
and
it's
also
really
really
fascinating.
So,
let's
keep
going
and
see
where
we
are
now.
A
If
I
am
going
to
be
asked
to
receive
this
question
now
after
seeing
all
of
this
and
after
knowing
where
at
what
a
good
community
of
users
is
when
somebody
tells
me
that
they
are
going
to
stop
using
my
library
because
they're
not
I'm,
not
fixing
a
bug.
Well,
there
is
only
one
answer
to
them
and
it's
thanked
here.
A
Please
stop
it's
really
really
better.
If
you
do
something
else,
and
the
reason
is,
is
that
they
don't
you
don't
want
to
be
filled
to
felt
pressures
in
knocking
them
and
they
don't
want
to
be
part
of
a
community.
They
just
want
to
freebie.
This
is
one
freebie
really
and
well.
Everybody
likes
free
beer,
but
there
is
no
such
thing
as
free
beer
to
some
extent
somebody
is
paying
for
it.
So
you
don't
want.
You
really
really
need
to
do
this
and
they're
not
really
useful.
So
by
the
way,
don't
be
that
person?
A
Okay,
really
don't
be
that
person.
Let
me
let
me
let
me
repeat:
this:
don't
be
the
person
that
asked
for
a
fix
on
a
library
without
being
willing
to
contribute
any
time
into
fixing
that
work
yourself.
It
might
be
that
you
need
to
contribute
very
well
rapport
script
to
reproduce
the
problem
or
you
know,
spend
time
to
actually
fix
it
by
yourself,
but
you
need
to
help
okay
be
a
very
good
citizen
of
open
source.
A
So,
let's
keep
going
and-
and
you
know
it
even
though
I
got
involved
in
several
successful
open
source
projects,
it's
still
sticking
to
my
hand
into
my
mind
on
how
can
I
build
a
successful
and
launch
a
successful
of
a
sort
of
open
source
project
myself.
First
of
all,
you
need
I
want
that.
You
need
to
scratch
your
own
inch.
You
need
to
be
able
you
need.
You
know
you
need
to
build
something
that
you
have
I
use
some
unique
perspective,
and
you
want
to
need
to
be
something
to
say
on
that
specific
field.
A
A
It
was
some
Valentine's
Day
I
was
on
a
business
trip.
My
fiance
was
not
really
happy
about
it.
To
be
honest,
but
you
know
it
was.
It
was
a
business
trip
and
I
was
I
had
dinner
with
my
colleagues
and
after
that
we
spent
the
night
coding
our
finger.
Hi
Dave,
hey,
miss
you,
so
in
fact,
and
and
I
found
my
niche,
ok
and
I
call
it
the
adapter
problem.
Now
this
is
a
piece
of
paper
right
and
with
a
piece
of
paper.
A
You
know
you
can
you
know
you
can
only
fold
piece
of
papers
so
many
times,
okay,
I,
don't
know,
I
keep
folding
my
piece
of
paper,
but
you
know
there
is
only
unlimited
tons
of
time
where
I
can
fold
it,
because
after
a
while
I
cannot
fold
it
anymore.
You
see
it's
too
hard
and
the
problem
with
this.
It's
that
you
can
only
have
so
many
abstractions
before
your
code
becomes
extremely
slow
and
I
got
focused.
I
focused
myself
and
I
focused
my
career
on
improving
performance
of
nodejs
and
ojs
applications.
A
So
one
of
the
first
thing
that
I
built
is
Pino,
which
is
a
really
nice
lager
and
Wow.
It's
you
know
it
took
the
I
presented
it
at
a
nice
conference
in
San
Francisco,
then
a
bunch
of
other
events,
somebody
dedicated
a
poem
to
me
and
a
which
is
their
the
author
of
Pinot
Thank,
You
Emily.
It
was
a
greatest
moment
and
of
know
Julia's,
roar
and
in
fact,
in
the
key
moment
where
things
change
was
when
I
started
to
ask
you
know
a
stranger.
Would
you
like
to
help
maintaining
Pino?
A
He
was
able
to
change
jobs,
chain,
job
change
life
he
infinitely
subtly
significantly
so
hey,
but
it
was
kind
of
a
big
surprise
and
I
have
seen
it
firsthand
ow
open.
Acting
people
acting
open
source
and
building
a
community
and
being
part
of
a
community
can
help
somebody
career
and
can
somebody's
life.
So
this
is
one
of
the
greatest
thing
that
I
think
I
am
proud
of.
So
you
know,
Pinot
is,
is
now
very
successful,
is
the
fastest
long
before
not
Jes,
and
it
has
very
minimal
features.
A
So
don't
expect
much,
but
it
has
a
great
community
and
it's
right
now
downloaded
maybe
4
million
times
per
month,
which
is
you
know
pretty
successful
to
some
extent.
From
my
point
of
view,
it
has
four
active
collaborators
and
it
has
now
reached
version,
6,
Hey,
successful
library
and
so
next
I
started
asking
myself
a
nice
question
is
how
can
I
build
a
new
web
framework
for
nauseas?
Well,
why
do
I
want
to
given
web
framework?
Because
I
was
not
really.
A
Happy
about
the
performance
of
of
node.js
applications
and
I
was
doing
some
benchmarking
and
a
lot
of
consulting
and
turns
out
that
there
was
some
lot
of
time
spent
in
no
J
in
inside
the
node.js
framework
and
inside
node
modules
and
inside
libraries.
There
and
I
wanted
to
fix
that,
because
most
of
the
time
the
CPU
time
should
be
spent
in
running
a
business
code
is
run
in
Europe
the
developers
application.
The
framework
should
not
be
in
the
way
to
gather
together
good
performance.
A
So
this
time
I
didn't
want
to
be
a
fool
and
in
fact
I
didn't
want
to
I
knew
I.
Couldn't
do
that
all
alone.
I!
Actually
I've
learned
my
lesson
so
I
started.
I
want
I
really
needed
to
build
a
community,
because
this
was
it's
AG
again
and
work
like
shipping.
A
new
web
framework
is
gargantuan
and
I
really
wanted
to
build
and
I
really
wanted
to
build
a
community.
So.
A
The
first
thing
that
I
started
is
I:
I
didn't
want
to
start
developing
the
framework
up
until
I
could
find
another
human
being
that
have
been
interested
in
the
journey
in
sharing
the
journey
with
me
and
building
with
me
together
now
this
has
been
one
of
the
funding
moment
of
for
me,
because
I
was
saying,
I
basically
said
well:
did
they
open
source
the
code
matters
so
little
in
what
I
wanted
to
build
that
I'm
going
to
focusing
on
convincing
somebody
else
right
about
that
time,
I
ended
up.
I
was
doing
that.
A
A
I'm
working
I
would
like
to
start
working
on
new
on
a
new
web.
Flavourful,
no
joy,
yes
to
solve
all
these
problems,
that
I'm,
seeing
on
the
right
on
the
others,
and
he
said
Oh
interesting
and
then
we
started
working
together
and
we
started
developing
software
together
and
we
were
chatting
every
every
few
days.
We
started
tinkering.
We
spent
long
nights,
maybe
doing
stuff
and
well
or
remotely
by
the
way,
all
on
github
and
pushing
things
whenever
we
could
I
yelped
and
him
find
is
next
to
jobs.
A
So
again,
I'm
feeling
very,
very
proud
and
yeah.
So
it
went.
It
went
really
really
well
so
anyway,
let's
go
and
start
about
the
genesis
of
a
framework,
and
it's
it's
really
that's
what
led
to
fast,
if
I
and
fast,
if
I
is
the
framework
with
myself
and
Thomas
dellavedova
built
together
and
what
we
have
started
first
of
all
is
based
on
governance.
In
fact
it
was
from
the
start.
It
was
never
to
be
my
own
thingy.
Okay,
he's
a
sure
thing:
it's
not
my
project!
A
It's
our
project,
I
I,
probably
had
the
idea
and
some
of
the
founding
moments,
but
it's
not
mine,
I'm,
not
the
first
contributor
of
the
project.
Okay,
to
be
clear.
Thomas's
I
am
NOT
and
it's
community.
First,
we
welcome
first-time
contributors.
In
fact,
we
want
to
grow
our
community
of
collaborators.
So
if
you
want
to
join
and
want
to
contribute
to
a
nice
open-source
project,
please
can
we
have
a
lot
of
things
to
do
really
a
lot
of
open
issues.
A
It's
also
based
on
the
concept
of
shared
ownership.
So
if
we
don't
want
to
be
in
a
position
of
you
asking
us
for
a
fee
for
for
fixing
a
bug,
we
want
you
to
fix
your
own
bugs
okay
and
that's
how
we
grow
our
community
so
that
this
is
everybody's
frameworks,
so
everybody
needs
to
contribute.
It's
also
based
on
some
few
very
important
technical
details.
So,
first
of
all,
we
didn't
want
to
have
much
overhead
in
production.
Now
you
can
have
you
need
to
have
some,
because
it's
clear,
it's
not
rust,
okay!
A
A
In
here
to
have
a
good
security
model
and
I
have
a
good
security
security
reporting
security
reporting
and
by
the
way,
thanks
open,
Ji,
sangs
nodejs
prefer
for
providing
this
it.
It's
based
on
the
concept
of
plugins.
So
if
something
could
be
a
plug-in,
it
likely
should
so.
We
created
an
open
core
system
where
it's
highly
extensible,
even
though
it's
you
know,
cost
free
those
mechanism
are
cost
free
and
it's
highly
extensible.
You
can
plug-in
and
not
things
in
several
places
of
the
framework
and
customize
it.
A
The
way
you
want
so
that
you
can
develop
your
own
plugins
and
tune
it
to
be
the
what
you
need
on
your
project.
It's
also
easily
testable
and
so
code
bitten.
We
pacifies
easily
testable.
It
has
a
nice
dot,
inject
function
which
is
fantastic
and
and
then
it's
we
didn't
want
to
do
any
monkey
patching
of
core
of
node.js
core.
That
is
one
of
both
of
my
main
critics
for
a
lot
of
frameworks.
A
So
no
monkey
patching
sorry,
you
need
support
semantic,
versioning
and
long-term
support
strategy,
and
it
should
you
know:
are
there
two
HTTP
1.1
so
first,
if
I
was
then
born,
and
it's
right
now,
one
of
the
fasted
web
framework
for
nodejs.
It's
it
has
ten
active
contributor
collaborators,
and
it
has
you
know
now:
reach
version
trees.
No,
it's
in
belize,
canada
staged
as
a
time
of
this
talk
and.
A
It
has
now
an
ecosystem
of
140
plugins
and
it's
actually
very
easy
and
fun
to
use.
So
please,
you
know
check
it
out.
I
just
want
to
say
a
few
parting
words,
which
is
people
use
software
I
built
and
there
are
means
some
and
impart
on
some
great
communities
know
JSP,
know
fast
if
I
and
you
know
in
20
20
modules
that
I
maintained
will
be
downloaded
around
five
billion
times,
which
is
a
little
bit
staggering.
To
be
honest,
and
with
this
I
want
to
say.
Thank
you.
A
Thank
you
for
your
time
and
please
check
us
out
near
forum.
Is
a
professional
services
company
based
in
Ireland?
We
do
all
things
JavaScript,
so
if
you
need
any
help
with
node
or
react
or
whatever
just
hook
us
in,
and
we
can
probably
help
you
and
I
just
want
to
say
thank
you
for
coming
to
my
talk
and
I
hope.
The
story
was
nice
and
you
and
you
enjoyed
and
you
enjoyed
it
and
see
you
next
time.
Bye,
bye,.