►
From YouTube: 2021-08-23-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
A
So,
looking
at
the
issues
that
we
have
on
the
agenda,
I
think
we've
covered
these
now
so
yeah,
I'm
just
looking
at
the
first
one
survey
to
get
needs
constituencies
key
technical
areas,
brainstorm
generate
and
next
10
years
for
collaborators.
I
think
that
the
second
two
we
covered
pretty
well
in
the
the
summit
that
we
had.
Let
me
just
pull
up
the
quickly
the.
A
A
A
So
these
were
the
minutes
from
the
last
from
the
summit.
So
in
terms
of
the
technical
priorities,
these
were
the
key
priorities
that
we
came
up
from
the
list.
A
You
know
modern
hp,
suitable
types
for
end
users,
esm
documentation,
webassembly
up
to
date,
is
javascript
supported,
visibility,
permissions
policy,
security
model,
better
multi-thread,
support
single
binary,
and
then
we
had
a
couple
on
the
watch
list
with
quick,
quick
and
serverless,
and
I
think
the
next
steps
on
that
one
were
to
open
a
pr
to
node
core
with
the
technical
priorities.
A
We
had
a
few
volunteers
to
work
on
that,
so
we
haven't
done
that
yet
I've
been
away.
So
I
haven't
done
anything
on
that
front,
but
we
should
kick
that
off
soon.
A
A
And
then
we
had
some
that
were
related
to
the
other
issue
on
the
agenda,
which
was
the
next
10
years
for
collaborators
sort
of
out
of
that
came,
the
the
sort
of
discussions
that
were
trying
to
think
like
one
of
the
major
blockers
was
was
around
build
time.
So
that's
why
we
have
an
issue
there,
as
well
as
a
plan
on
a
deep
dive
for
maintaining
growing
level
of
contribution
in
future
next
10
meetings.
A
So
I
wonder
if,
if,
if
you
think
whether
we
can
close
those
other
issues
out,
you
know
pointing
to
this
and
that
will
open
up
new
issues
that
are
more
specific
to
the
the
next
actions
here.
What's
that,
how
do
people
think
about
that.
B
I
think
it
can
be
close,
but
I
was
thinking
I
was
just
checking
what
we
wrote
on
the
google
doc
last
time.
Could
it
be
also
interesting
to
maybe
at
least
link
on
this
on
the
pier
the
google
doc.
A
B
A
A
A
A
Link
again,
so
people
can
add
themselves
to
the
agenda
or
sorry
to
the
agendas
as
participants.
Maybe
we
could
spend
some
time
planning.
You
know
the
deep
dives
and
and
some
of
the
actions
from
the
the
summit,
which
would
be
a
good
good
thing
to
at
least
get
some
planning
going
forward.
A
So
I've
got
the
actions
here.
Let's
see.
A
So
here
the
I
guess
the
first
question
would
be:
how
do
people
think
it's
best
to
put
that
pr
together
and
work
on
it?
You
know,
I
know
joe
you'd
volunteer
too.
Should
we
should
we
open
a
pr
and
collaborate
in
the
pr
or
do
you
think?
Maybe
we
should
open
a
google
doc
and
put
together
draft
there?
What
do
people
think
will
work
well.
E
B
A
A
A
C
A
B
Yeah
on
the
under
google
doc,
we
had
some,
maybe
not
sub-list
item,
but
at
least
it
was
a
feedback
of
pretty
much
every
people
and
I
remember
the
documentation
we
were
discussing
about
not
available
and
not
really
simple
for
newcomer,
but
also
other
issues.
So
it
can
be
at
least
a
first
part
to
to
help
define
the
bigger
bullet
point.
A
Like
this,
this
pr
shouldn't
be
like
here's,
the
the
five
things
we
need
to
do,
but,
like
a
top-level
description
of
what
we
believe
is
important,
and
you
know
I
guess
we
can
look
at
it
and
say
if
what
we
put
together
isn't
good
enough,
but
otherwise
we're
you
know
to
get
through
the
deep
dives
at
one
or
two
a
week.
We're
talking
a
long
long
time
and
I
think
the
idea
was,
let's
see
what
we
can
put
together
in
parallel
with
that.
A
A
A
A
A
A
Just
looking
to
see,
if
anybody
else
would
volunteered
for
a
particular.
A
A
This
is
more
like
we
said
that
you
know.
Next
steps
would
be
actually
to
be
a
bit
more
of
a
deep
dive
in
each
of
these
to
figure
out.
You
know
what
would
be
important
to
do
for
the
project
at
a
more
detailed
level
than
just
saying
yeah.
This
is
important.
It's
like
okay.
What
should
we
actually
do
and
plan
to
do.
A
D
Like
documentation
seems
pretty
good
the
meaning
of
javascript
support,
that's
not
really
a
technical
problem
for
node,
it's
just
something.
We
need
to
understand
and
define.
D
So
now
there's
wasm
ekma,
402,
ekma,
404
and
ecma
262.
single
binary
I'd
actually
put
up
there
because
it's
a
solved
space.
We
just
never
really
understand
it.
Inside
of
core
itself.
A
Go
from
there
so
we
had
okay
next
steps,
so
I've
got
start
on
that.
One.
A
A
Okay,
so
this
discussion
has
started
there.
I
haven't
had
a
chance
to
read
through,
but
it
looks
like:
we've
got
progress
on
that.
Maybe
I
can.
Can
I
actually
put
this
onto
the
agenda
just
as
a
way
to.
A
Any
more
discussion
on
that
one
do
people
think
we
need
or
just
let
that
go.
Actually.
I
don't
have
it
in
that,
but
like
let
that
go
in
the
discussion
in
the
github
repo
and
talk
about
it
in
one
of
the
future
meetings.
D
So
one
thing,
I'm
concerned
with
with
the
idea
of
a
docker
container,
is
windows
which
is
the
notoriously
hard
to
deal
with
debugging
experience
for
a
lot
of
node
core
contributors.
D
D
D
D
I
I
don't
care
how
it's
solved,
I'm
just
stating
that,
like
we
need
to
be
careful
here,
because
this
solution
went
from
hey,
we
should
provide
pre-built
images
for
people
to.
We
only
need
to
provide
pre-built
images
for
a
subset
of
people
and
not
the
major
subset
of
people
using
node.
A
A
D
D
Yeah
we
can
suggest
it,
I
don't
have
time
to
actually
do
it
so
I'll
I'll
just
talk
to
miles
about
it
and
he
can
go
from
it.
A
Okay,
so
yeah
I
can
see
anyway,
I
haven't
I'm
gonna,
go
back
and
read
through
that.
A
A
A
A
Okay,
so
I'm
thinking
that's
that's
you
know,
probably
what
we
can
cover
in
this
meeting.
It'd
be
good
to
have
a
little
bit
of
time
for
us
to
you,
know
offline
to
work
on
the
prs
and
give
people
heads
up
which
of
the
as
we
have
in
like
what's
up
next
in
terms
of
the
deep
dives.
Is
there
anything
else?
People
would
like
to
cover
discuss
this
this
week.
E
A
If
not,
okay!
Well
then,
let's
close
that
for
this
this
time
and
thanks
for
everybody
who
participated
and
participated
in
the
summit,
then
it's
good
to
see
some.
We
have
some
good
next
steps
to
keep
moving.
This
forward
talk
to
everybody
later
thanks.
Everybody
thanks
thanks,
bye.