►
From YouTube: 2022-09-07-Next 10 years of Node.js
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
So
welcome
to
the
node.js
next
10
meeting
for
September
7th
2022.
we'll
follow
the
agenda,
as
was
outlined
in
the
issue,
which
was
issue
number
150,
158,
okay,
great
so,
but
before
we
jump
into
that,
does
anybody
have
any
announcements
they'd
like
to
make.
B
Naturally,
maybe
just
that
we
will
be
a
lot
of
people
from
the
node.js
community
being
in
the
not
confused
in
less
than
one
month
and
that
we
also
plan
to
have
a
collaborative
submit
today
prior
to
to
the
conference
yeah.
So
if
some
people
want
to
join,
maybe
we
can
share
the
link
or
something
like
that
for
people
to
register
and
join
us.
A
Yeah
I
definitely
the
there
was
a
tweet
from
the
openjs.
What
was
the
welcome?
Js
collaborator,
no
I'm.
A
No
I
pasted
the
link
to
add
people,
add
yourself
to
the
agenda
but
yeah,
there's
there's
the
link
I,
don't
know
how
we
easily
share
that
here.
Well,
I
could
share
my
screen
for
a
sec.
B
A
B
A
There's
the
there's
the
announcement
I
will
do
exactly
that
and
grab
the
link
for
the
collaborator.
B
A
A
Okay,
so
let's
move
on
to
the
issues
we
have
had
for
the
agenda,
then
the
first
one
I
think
is
the
and
I
think
we
could
go
through
these
and
then
we've
got
some
general
topics.
Just
to
summarize,
you
know
we
should
talk
a
little
bit
about
what
we
should
do
at
the
collaborator
Summit,
and
it's
also,
you
know
good
a
good
time
to
sort
of
think
about.
A
Okay,
you
know
what
are
some
next
steps
that
we
want
to
sort
of
focus
on
on
us
a
group,
but
having
said
that,
we
quickly,
though
so
visualization
of
technical
priorities,
so
I
think
John.
You
mentioned
that
yeah.
B
I
did
it
as
time
to
yeah
I
didn't
have
time
to
compute
everything
inside
that
I
do
have
two,
and
that
was
that
was
something
we
talked
like,
maybe
three
or
four
weeks
ago.
Something
like
that.
Yeah
I
wanted
to
add,
let's
say
some
easy
way
to
visualize
how
which
kind
of
technical
priority
we
worked
on
in
the
last
year
with
an
extent
initiative
with
just
some
color
and
some
visualization
didn't
have
time
to
do
that.
So
I
will
try
to
remember
to
to
to
do
it
for
next
meeting.
A
Yeah
I
think
that
that
would
be
a
great
idea.
I'm
just
pasting
this
in
the
chat
like
we
have
this
doc,
which
kind
of
tries
to
outline
like
you
know,
have
we
done
a
deep
dive?
Have
we
documented
stuff
next
steps
but
I
think
that
sort
of
nice
you
know
red,
yellow,
like
maybe
the
top
of
that
document
would
be
a
great
place
to
just
show.
Have
that
thing
to
say:
oh
yeah,
we
think
we're
doing
okay
on
these,
but
here's
one
that
we
really
could.
B
And
I
will
do
that
for
the
next
I
think
we
do
have
a
meeting
in
two
weeks,
which
will
be
great
because
this
way
we'll
be
able
to
redo
it
and
use
that
to
talk
about
it
during
the
collaboration
two
weeks
later
in
in
Dublin
Dublin.
So
that's
that's
a
perfect
timing.
I
think
yeah.
A
That
sounds
good.
Okay.
The
next
one
is
the
example.
Documentation
initiative,
number
154.,
we'll
bring.
B
B
Yeah,
so
for
this
one
it
was
really
it's
linked
to
this
issue
and
the
issue
one
number
before
so
153
that
we
did
discuss
about
improving
the
documentation
and
we
also
talked
about
it
with
the
type
system
and
how
we
want
to
improve
that.
So
let's
say
it's.
A
two-part
I
also
talked
with
offload
10
days
ago.
Something
like
that.
We
had
a
one
hour
talk
together
about
it,
and
we
do
you
gladly
put
every
note
and
what
we
discussed
about
in
this
issue.
B
I
think
the
main
idea
is
for
this
one
the
example
initiative,
so
153
right,
let's
say
I
will
start,
maybe
154,
because
it
was
a
one.
You
were
talking
first
yeah,
so
yeah,
so
one
main
issue
is
a
hard
documentation
and
how
we
are
handling
pretty
much
everything
around
documentation.
We,
it
was
raised
during
our
previous,
let's
say,
a
discussion
that
the
documentation
is
great.
B
So
it's
a
two-part
in
the
two
issue.
This
one
is
really
linked
to
improve
the
documentation,
with
example,
of
real
real
life
project
or,
let's
say
how
to
build
a
web
server
and
build
a
basic
I,
know:
CLI,
happy
Parts
argument
for
CLI
how
to
use
pretty
much
everything
around
multiple
technology,
multiple
framework,
but
also
cloud
provider
and
solution
and
Docker,
and
how
to
use
it
with
real
life.
B
Let's
say,
example
of
basic
project
how
we
can
do
testing
and
stuff
like
that
to
really
provide,
let's
say
some
template
on
different
use
case
with
for
new
command
for
the
community,
which
I
think
this
initiative
could
be
really
a
bit
lead
by
someone
from
inside
node.js,
but
could
be
really
an
initiative
driven
by
external
people
and
really
the
community,
because
we
don't
really
it
could
be
faster
and
to
improve
to
have
a
broader
feedback
and
stuff
like
that.
B
Your
repository
is
already
existing
for
the
past
two
or
three
years,
at
least
without
too
much
without
a
lot
of
changes.
There
is
a
list
of
some
examples
we
wanted
to
add.
So
I
think
it
could
be
great
to
continue
to
improve
these
parts.
A
A
Think
Tierney
had
a
pretty
strong
view
of
what
fit
or
what
didn't
fit,
and
you
know
it
if
you
try
I
think
if
you
try
and
be
that,
like
it's
got
to
fit
into
this
mold,
then
it's
it.
You
know,
there's
a
few
cases
where,
like
I
know,
people
from
our
team
tried
to
contribute
things,
didn't
wasn't
successful
and
it's
like
okay,
we're
moving
on
right.
So
it's.
A
How
do
you
find
that
balance
between
you
know
the
the
maintenance
that
you
can
do
reasonably
versus,
or
maybe
just
you
know,
providing
a
place
where
you
don't
maintain
them,
but
you
try
and
group
them
together.
Yes,
I
just
bring
it
up
this
thing
that
I
know
there's
been
some
discussion
of
like
well.
Where
should
we
draw
the
line?
Maybe
we
should
just
provide
product
documentation
and
it's
up
to
the
ecosystem
to
fill
in
examples
and
stuff
you're.
B
Right
an
answer
so
you're
right
and
we
also
should
not,
let's
say,
handle
the
part
of
the
example
and
documentation
for
other
framework.
It's
not
our
purpose
as
just
a
node.js
collaborative
and
people.
So,
but
one
of
the
issue
which
was
raised
like
one
year
ago
was
really:
how
do
we?
B
A
Yeah
and
I'll
just
bring
up
to
show
this
other
example
of
node
add-on
examples.
So
this
very
specific
to
add-ons,
but
it's
a
model
that
I've
found
has
been
very
useful,
like
people
are
like
hey,
I
need
to
do
this
specific
thing,
and
you
know
this
has
examples
of
those
things.
They
don't
change
much
over
time,
either
so
they're
kind
of
nice
in
that
sense
of
like
okay,
it's
their
their
basic
examples.
A
B
Yeah
I
think
I
think
we
do
have
some
example
on
using,
let's
say,
a
basic
web
server
with
a
database,
and
it
was
just
a
basic,
crud
or
I.
Think
materials
submitted
an
example
with
fastify
and
a
Docker.
Something
like
that.
I,
don't
remember
the
exact
example,
but
something
really
without
too
much
stuff.
It's
not
a
big
database.
It's
just
how
to
insert
something
how
to
get
a
data,
and
that's
all
and
I
do
think,
because
I
saw
that
yesterday
was
also
something
like
that
foreign.
A
Here's
your
SSL
one,
here's
like
the
basic
things
and
you
know
they
integrate
some
of
the
stuff
we're
working
on
they'll
integrate
like
you
know.
If
we
have
a
client
that
makes
it
easier
in
openshift,
we
include
them
in
but
yeah
that
that
concept
is
something
that
makes
sense
for
us
too
yeah.
Okay,
so
that
so
that's
154
and
I.
Guess
it's
like
how
do
you
scoping
that
yep
and
and
I
guess
also
finding
Like
A
Champion
right,
because
it's
it
comes
down
all
these
things.
It
really
comes
down
to
do.
A
We
have
somebody
who's,
passionate
about
moving
them
forward.
Yeah.
B
On
my
side,
I
would
be
Keen
to
work
on
that,
because
I
do
like
this
documentation,
I,
don't
know
if
I
can
send
them
to
initiative
and
it
could
be
a
lot
of
work.
But
this
one
and
153
are
really
linked,
I
think
so
we
we
can
discuss
about
it
in
two
in
let's
say
one
month
in
in
the
collaborative
Summit
or
something
like
that.
A
Yeah
the
153
I
I,
like
the
to
me
internationalization,
even
just
the
very
existing
documentation,
could
be
strategic
in
terms
of
you
know,
making
it
so
that
people
enough
can
can
access
them
in
other
languages.
B
Yes,
I
did
work
on
the
internationalization
part
for
the
react
in
French
and
also
follow
the
project
in
other
languages.
It's
a
lot
of
work,
but
I
was
quite
surprised
with
how
many
people
from
multiple
countries
were
involved.
They
were
Keen
to
work
on
this
kind
of
initiative.
Let's
say
a
big
part
of
the
work
was
really
to
think
how
we
can,
let's
say,
include
a
build
process
or
how
we
want
people
to
contribute
and
this
stuff,
but
once
it's
done
and
yeah
when
it's
working
every
you
do
have
a
lot.
A
B
Yeah
and
we
talk
because
currently
we
do
have
some
node.js-
we
use
protein
I-
think
there
is
an
excess
accordingly
I,
don't
think
we
use
a
result
or
something
like
that,
and
we
did
discuss
also
with
the
flow
about
integrating
that
with
a
new
website
initiative.
And
now
we
can
do
that.
B
Any
take
a
lot
of
note
and
it's
a
bit
lower
on
the
issue,
which
is
more
Keenan,
which
also
opens
some
other
subjects
like
how
we
want
to
try
to
work
that
which
kind
of
documentation
should
we
split
our
Pure
like
a
celebratory
or
pure
technical
documentation
when
you
are
already
aware
or
on
what
you
are
looking
for
and
how
so,
which
is
one
pattern,
pure
technical,
let's
say:
input
output
of
each
function,
each
module,
but
also
an
easy
way
for
people
to
find
something
that
you
don't
know
how
to
do
it.
Yeah.
A
B
To
the
API
dock
is
a
bit
I
think
what
we
currently
have,
because
we
do
have
the
deprecated
function
and
when
you
go,
let's
say
to
the
net
module.
You
have
every
function
which
are
inside
with
the
basic
stuff.
I
think
it's!
This
one
is
mostly
around
that
and
we
talked
about
the
human
readable
part.
Let's
say
because
if
this
one,
where,
if
you
try
to
find
something
which
is
not
HTTP
or
big
module,
you
will
have
issue
to
find
some
some
stuff.
If
you
don't
know
where
to.
A
B
Yeah
go
yeah!
Oh
yes!
Yes
completely!
We
did
discuss
a
bit
more
on
other
side,
so
it's
not
all
link
on
translation,
but
we
raise
the
issue
because
maybe
this
one,
which
is
a
lot
more
technical,
doesn't
really
need
to
be
at
first
translated
in
the
other
language,
because
it's
a
more
in-depth
documentation.
B
A
I
guess
that
is
the
interesting
part
is
like:
where
does
where
does
it
actually
have
the
biggest
impact
be
translated
or
because,
like
some
of
the
the
documentation
in
the
node
like
the
collaborator
guide
right,
we
could
translate
that,
but
on
the
other
hand,
I
think,
unfortunately,
a
lot
of
the
discussion
in
GitHub
and
all
that
is
in
English
anyway
right?
Yes,
so
it's
it's
figuring
out
where
the
where
it
actually
would
help
the
most
I
guess.
B
Yep
no
I
would
agree
with
you
and,
like
I,
don't
think
it's
pretty
useful
to
translate
every
not
not
meetings
or
stuff
like
that,
because
every
meeting
I
entered
in
English
and
we
all
speak
English
and
stuff
like
that,
I,
don't
think
it's
really
interesting
to
also
translate
issue
or
stuff.
Like
that.
B
To
be
completely
honest
for
me,
it's
really
and
what
we
discuss
I
guess
the
first
step
would
be
to
focus
I,
think
on
how
people
are
coming
in
the
language
in
the
technology,
in
the
solution
to
help
them
to
not
have
both
a
Gateway
about
the
technology
and
also
the
long
way
they
are.
Let's
say
spoken,
language
right.
A
B
Think
we
did
talked
a
bit
about
it,
but
it
was
following
not
the
trailer
but
well.
It
was
not
true
where
people
were
put
in
a
vote.
Some
idea
that
would
which
would
be
what
interesting,
to
continue
and
stuff
like
that.
So
I
think
it's
something
in
the
next
term,
but
I,
don't
know
which
one
to
be
honest,
I
should
try
to
find
it
later.
Yeah.
B
Maybe
I
not
sure,
but
maybe
it
was
just
after
we
we
get
a
result
from
the
survey.
We
did
an
initiative
which
could
be
interesting
for
people
and
stuff
like
that.
I
think
we
did
something
about
it.
A
A
B
I
think
we
can
discuss
about
it.
I
know
of
flow
will
be
indulgent
for
the
collaborative
so
I
plan.
I
just
have
to
talk
about
with
him
about
that.
B
Maybe
we
can
open,
let's
say
a
session,
to
involve
more
people
which
will
be
Keen
to
to
jump
in
also
link
to
documentation,
maybe
from
feedback
from
other
long
way
from
other
form
of
Technology
input
and
also
documentation
from
let's
say
Club
provider
as
well,
which
a
lot
of
them
are
translated
to
help
people
to
use
that
so
which
could
help
us
to
to
have
and
to
be
able
to
judge
about
the
effect
and
how
we
want
to
prioritize
that
a
link
to
yeah.
A
B
B
Yes,
so
mostly,
we
did
talk
about
a
lot
of
topic
like
HTTP
on
the
past
year
in
the
first
survey.
We
did
this
regard
two
main
topic,
quick
and
serverless.
From
the
other
side,
we
do
have
the
link
from
the
easy
retro
and
pretty
much
everything
I
was
able
to
find
a
still
working
for
the
feedbacks.
B
So
one
idea
for
the
survey
is
really
to
maybe
ask
the
same
question
about
what
the
community
think
we
should
try
to
work
on
new
subjects,
because
maybe
it
will
be
new
subject
or
the
same
topic.
We
already
try
to
address
and
we
do
discuss
about
it.
I
think
it
was
with
you
Michael
in
the
past,
maybe
last
month,
during
the
next
10
meeting
on
how
we
wanted
to
try
to
have
something
a
bit
regular
about
this
kind
of
survey,
to
have
a
better
understanding
of
the
communities
and
needed
yeah
yeah.
A
It
almost
like
I
wonder
if,
if
we
should
try
and
plan
at
the
collaborator
Summit
to
have
the
like
a
session
on
you
know,
maybe
we
start
with
white
space
which
is
like
well.
What
is
what
is
you?
What
do
you
think
our
top
priority
should
be,
and
then,
like
you
hear,
if
we
it's
just
I'm
gonna,
take
a
note
so.
B
Maybe
it
is
great
because
it
will
Target
a
small
percentage
of
the
community,
but
which
is
mostly
involved
with
node.js,
so
it
will
provide
us
with
a
feedback
from
collaborator.
Contributor
and
people
are
involved
in
the
project.
But
we
should
not
just
use
that
because
it's
not
the
same
use
case
that
we
have
in
a
daily
basis
with
node.js
with
let's
say
thousands
of
people
on
Twitter
and
all
this
stuff.
So,
but
it
would
be
great
to
have
this
input.
B
A
Collaboration
Set
some
evidence
and
I'm
just
so
what
space.
A
And
then
so,
I
can
kind
of
see
that
this
whole
thing
would
be.
Then
then
survey.
A
B
A
B
A
Okay,
anything
else
we
should
discuss
on
that
I
think
I
think
we
can.
B
A
B
Good
cool,
let
me
see
because
I
think
I
did
up.
I
saw
this
one
I
wasn't
the
one
opening
it,
but
I
do
think.
I
have
something
linked
a
bit
to
that
we
discuss
what
was
it
social
yeah
I
did
have
something
open
on
the
social
team
and
I.
Don't
have
any
feedback
I,
don't
think.
Let
me
see
yeah
to
yeah,
so
I
I
will
talk
about
it
a
bit
later,
because
it's
not
directly
linked
at
least.
B
Yeah,
because
this
one
I
think
is
relating
to
try
to
have
more,
let's
say,
open
communication
using
already
well-known,
let's
say,
Media
or
Twitter
account
to
publish
stuff
yeah.
A
And
then
the
suitable
types
next
steps-
these
are
things
we
have
on
the
list.
I
think
these
are
still
important,
but
I,
don't
think
we're
making
any
progress.
I
still
think
they're
kind
of
one
of
the
more
important
things
we
could
push
forward
so
I'm
suggesting
we
leave
on
the
agenda,
even
though
there
isn't
an
update
on
it.
A
Okay,
so
thinking
maybe
we
could
go
over
to
I
think
it's
open,
Js
foundations
class,
so
I'm
at.
A
B
A
So
I
don't
think
we
have
one
but
I
think
we
can
write
it
up,
see
I'm
going
to
find
the.
B
B
A
B
A
So
should
I
list
the
three
of
us
as
volunteers,
I
think
or
we're
all
going
to
be.
There.
A
Yeah
so
I
don't
know,
I
left
it
there
just
in
case,
but
it
doesn't
hurt
yeah
Roy.
What's
your
GitHub
handle
I'm?
Sorry
really
I,
don't
know
just
like
a
name
all
together,
yeah
and.
B
B
A
A
A
B
A
Ahead,
yeah
I
think
we
can
remove
the
last
the
assignments
there,
like
I,
just
removed
from
my
the
follow-up
and
well
additional
context.
Maybe
if
you
want
to
put
a
link
to
the
things
we've
done
already,
but
I
think
those
we
might
fill
in
afterwards,
yeah
actually
well
yeah
yeah,
but
follow
up
I,
don't
think
there
is
any
follow-up.
Is
it
like?
Is
there
any
other
session
like
related
to
this
one.
B
B
Reviews
taking
care
of
priority,
we
did
the
one
year
ago.
B
I
think
I
I
in
my
in
my
issue,
I
did
linked.
It
I
think.
A
A
Okay,
so
that's
I
think
is
a
good
one
and
I
think
Jean
did
you
want
to
create
one
for
like
the
next
10
and
documentation
yeah.
B
I
will
open
one
later
today,
yeah,
because
I.
A
Think
those
two
sound
like
good
good
topics,
I'm
just
looking
at
we
look
at
our
technical
priorities
and
actually
here
I
want
to
find
the.
A
A
But
so
I
think
I
think
those
two
are
good
good
topics
for
sure,
yep
I
think
at
the
same
time
I
might
actually
go.
A
Group
right
now
and
yeah
I
know
it's
a
tangential
here
Michael,
but
maybe
we
should
look
into
booking
like
a
follow-up
for
for
America
time
zone
like.
B
A
A
It's
okay,
I'm,
just
gonna!
Do
that
before
I
forget,
okay,
so
I
think!
Yes,
if
we
two
sessions
on
next
10
stuff
is
probably
unless
there's
like
you
know,
individual
initiatives
that
are
working
away
and
it
makes
sense
to
have
another
another
Deep
dive,
but
I
think
from
us.
Those
two
on,
like
you,
said
the
the
General
one
is
good
and
then
the
one
on
on
documentation
internationalization
would
be
good.
A
B
Not
sure
about
agenda,
but
we
discussed
and
I
open
an
issue
a
few
weeks
ago
on
the
social
team
and
I
didn't
add
any
feedback
on
that
part
our
regarded
in
how
we
can
try
to
maybe
tweet
about
our
daily
meeting
or
something
like
that.
So.
A
A
I'm
actually
trying
sorry
I'm,
just
gonna
find
maybe
one
of
these
other
meetings
that
people
are
on
there.
B
A
A
A
A
A
If
not
I,
guess
I'd
say
thanks
for
everybody's
time
and
looking
forward
to
some
of
those
sessions
at
the
the
collaborator,
Summit
I
guess
offline,
we
should
discuss
a
little
bit
like
you
know,
maybe
even
in
that
issue
we
can
use
it
to
coordinate,
putting
together
a
plan
for
how
we're
going
to
do
that.
A
Maybe
we
can
think
about
that,
but
we
only
have
six
minutes
now.
So
maybe
that
should
be
a
topic
of
I
will
maybe
I'll
maybe
make
sense.
I
can
create
an
issue
in
this
repos
I
know
JS
next
10.
A
A
Not
the
TSC
next
time
agenda,
so
we
can.
We
can
start
to
collaborate
in
the
issue
itself
and
it'll
show
up
on
the
calendar
on
the
agenda
for
next
week,
so
that
we
can
hopefully
close
on
okay
yeah
we're
ready
to
go.
You
know,
I,
guess
one
of
the
questions
is,
do
what
would
we
use?
We
use
for
an
easy,
easy
retro.
A
B
Yep
great
sounds
great
I.
Just
is
the
next
meeting
next
week
or
in
two
weeks
the.
B
A
B
Okay
yeah,
because
this
one
was,
we
already
scheduled
just
this
one:
okay
yeah,
we
moved
it.