►
From YouTube: 2022-09-21-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
next
10
meeting
for
September
21st
2022
we'll
follow
the
agenda
in
the
issue
that
was
created
in
the
repo
which
was
issue
number
162.
A
A
B
A
A
What
I
was
just
doing
awesome
perfect
email's
still
not
verified
what.
B
B
B
B
C
A
C
We
were
really
into
trying
to
figure
out
every
technology,
key
area
that
were
needed,
for,
let's
say
the
user
to
be
able
to
develop
and
in
which
kind
of
environment
and
how
we
can
improve
that,
and
it
was
really
focused
on
how
we
can
ensure,
let's
say
the
success
of
a
project
driven
by
the
community
in
terms
of
not
really
I,
don't
think
we
do
have
a
lot
of
Technology
inside
but
more
on
how
we
can
continue
to
work
with
and
involve
more
people
and
bring
right
yeah,
because
I
don't
think
we
do
have
a
lot
of
yeah
on
the
contributing
impact
it's
really
about.
C
B
B
B
B
B
B
A
B
C
For
for
the
easy
retro,
you
gave
the
link
for
the
new
one.
Maybe
just
have
a
link
to
the
one
from
last
year,
so
maybe
people
will
be
able
to
see
how
to
put
again
something
that
I
did
last
year.
Okay,.
A
Do
you
have
the
so
yeah
you
pasted
the
links
and
I.
C
B
C
A
D
D
Generic
conversation
I
think
we
had
in
the
past,
but
I
think
it's
always
a
relevant
one
is
trying
to
just
basically
plan
how
to
actually
get
all
these
ideas
and
plans
in
action
right
like
how
to
translate
these
to
the
rest
of
the
collaborators
and
yeah
I.
A
C
I
I
think
it
was
one
of
the
topic
which
was
raised
on
the
second
on
the
community
brainstorm
last
year
around
that,
if
I
check
it
quickly,
it's
it
was
one
of
the
issue
about
yeah.
We
did
one
part
about
attracting
new
collaborator
and
I
think
we
were
quite
successful
this
year,
but
one
key
topic
was
also
to
engage
and
help
people
wanting
to
collaborate
to
help
and
to
find
how
they
can
help
so
I
think
it's
something
which
is
a
bit
linked
to
what
you
said.
Your
story.
A
Yeah
I
just
added
the
second
one,
because
I
think
it's
kind
of
like
it's
good.
If
they
know
about
it,
but
it
they
got
to
make
sure
we
got
to
make
sure
that
they
feel
like
they
could
pick
it
up.
I'm
pretty
happy
actually
with
like
you
know,
for
example
the
sca
stuff.
You
know
the
whole
new
team
is
formed.
A
There's
lots
of
discussion
and
conversation
going
on
so
the
more
we
can
sort
of
replicate
that
where
we
had
some
good
discussions
on
a
particular
topic
and
then
some
people
who
may
have
had
a
long-standing
interest
in
it,
but
maybe
didn't
you
know,
know
how
to
get
the
project
engaged.
You
know
much
more
active
in
in
a
project
within
you
know,
a
repo
that
we
have
and
lots.
B
Of
I
mean
I
also
think
that
one's
partially,
like
there's
a
company
who
wants
this
for
their
product
in
their
investing
time,
energy
and
money
into
it,
and
so
that
is
you're
talking
about
the
single
node,
executable,
yep
yeah,
the
ends,
I
think
that's
also
a
big
factor
there
that
we
isn't
necessarily
like.
We
did
good
in
open
source
it.
Just
there
was
people
who
who
could
invest
that.
A
I
I,
obviously
I
have
a
different
opinion.
I
think,
like
those
people
always
had
an
interest
and
I
think
the
discussions
helped
to
bring
them
together
and
actually
start
like.
D
B
A
So
it's
yeah
anything
like
anything
else
that
we
should
add.
C
D
D
D
A
A
C
A
Okay,
so
if
you
wanted
to
propose
something,
I
I
will
write
that
yeah
I
mean
this
one.
The
I
was
kind
of
like
trying
to
organize
here,
like
I.
Think
if
we
organize
the
agenda
and
the
things
where
we
think
it's
most
important
to
get
a
broader
collaborator
input,
so
the
why,
like
the
train,
I
think
we
should
definitely
do
the
brainstorms
right
up
front
right
and
then
we
can
talk
about
like
what
would
be
our
next
most
useful
thing
after
those
two
in
terms
of
discussion
with
the
larger
group.
C
A
C
C
B
B
B
A
Think,
like
the
review
of
the
technical
priorities
that
we
could
do
afterwards
right,
we
have
the
brainstorm.
If
we,
if
we
have
time,
we
can
start
to
take
a
look
at
and
see
how
that
thinks,
but
otherwise
we
could
do
that
as
follow
on
the
constituencies.
Changed
I
think
is
kind
of
makes
sense
like
if
we
have
time
kind
of
thing.
D
And
I
think
I
heard
someone
saying
I,
don't
know
if
it
was
the
last
collaborator
Summit,
but
talking
about
how
it's
much
better
to
actually
do.
Brainstorming
like
that,
like
that,
let
people
come
with
the
ideas
beforehand
because
they
might
be
just
steered
and
influenced
like
when
you're
trying
to
have
ideas
on
the
spot,
like
everybody
will
kind
of
try
to
convert
into
the
same
ideas
like
they
try
to
yeah,
there's
like
a
group
effect
of,
like
you
start
to
just
like,
maybe
not
proposing
some
idea,
because
you're
you're
down
the
spot.
D
A
This
one
right
here
to
sorry
to
the
actual
board
itself.
Let
me
put
it
into
the
chat.
A
C
B
A
C
Yeah,
it
can
be
especially
issue
with
action
asking
for
feedback,
something
like
that.
You
just
put
the
link
and
you
tag
everyone
in
node.js.
A
B
B
If,
if
you
tag
members
and
every
team
in
node
is
a
sub
group
of
members,
so
that
will
tag
every
single
person
in
the
org
or
it
should,
if
it
doesn't
something's
broken.
A
B
Yes,
but
I
would
I
would
oh
hold
on.
Can
you
scroll
up
or
is
there
what's
the
what's
the
request
there,
I
I
would
have
a
specific
request
and
I
would
also
change
it
from
collaborators
to
members
so
like
for
the
specific
request
like
that,
yes
I,
believe
that's
the
team,
let
me
double
check,
but
for
the
specific
request
part
like
what
do
we
want
these
people
to
do
with
this?
Do
we
want
do
we
want
them
to
add
stuff?
Do
we
want
them
to
delete
stuff?
B
Do
we
want
them
to
upvote
stuff,
just
make
sure
we
have
like
a
specific
question
or
request
from
from
that?
Let
me
put
Js,
let
me
make
sure
I
get
you
the
team
name
correctly.
B
If
you're
a
member
of
us,
so
it
has
zero
members,
but
oh
no,
no,
never
mind
the
members
of
transitive,
okay
yeah!
That
should
work.
B
You
can
drag
down
under
the
scroll
bar
if
that
helps
the
scroll
bar
on
the
right
there's
a
little
like
handle.
A
Question
is
like
before
we
actually
organized
a
bunch
of
them
like
similar
ones
together,
but
we
couldn't
do
that
if
we're
going
to
reveal
all
the
votes
in
advance,
but
that
it
still.
C
A
C
Yeah
we
can
keep
it
Eden
for
the
first
I,
don't
know:
15
20
minutes
if
needed,.
A
Yeah,
that
makes
sense
well.
Why
don't
we
then
just
say
well
we'll
be
song
like:
please
fill
them
out
and
then
in
this
session,
we'll
probably
reveal
you
know,
reveal
them,
give
people
some
time
to
add
ad
because
I,
you
know
I
suspect
there'll,
be
people
who
come,
but
I
haven't
necessarily
thought
about
it
before.
So
we
can
get
make
sure
we
can
get
their
input
and
then
we'll
reveal
them
and
and
can
go
through
voting
with
the
act
of
people
and
go
from
there.
A
B
B
B
A
Okay,
any
other
say
anything
else.
We
should
talk
about
in
terms
of
the
summit
or.
A
B
C
B
C
We
want
to
have
yeah
on
so
yeah
on
this
one
I,
namely
the
community
service,
so
for
people
outside
which
we
had
something
like
2
000
people
responding
last
year,
and
we
all
only
add
the
fourth
first
question
last
year,
yep
I
think
it
can
be
really
interesting
to
keep
them
as
it
helped
us
maybe
discover
some
new
new
constituency
or
new
feedback,
but
also
to
add
a
lot,
maybe
not
a
lot
more
question
and
we
need
to
focus
some
part
where
mostly
people
are
coming
from
and
also
on
what
kind
of
projects
they
are
working
with.
A
A
C
A
C
I
want
yep
and
I
wanted
to
add.
Also
a
direct
question
for
the
user.
About
recurrence
issue
is
node.js
for
us
a
key
indicator
on
what
would
be
some
of
the
big
pain
pointer
communities
facing.
C
Yeah,
if
you
had
some
more
question,
we
could
be
interesting.
You
can
propose
at
them
also.
C
Yeah
and
the
last,
but
I
will
maybe
delete
it
because
we
just
did
that
with
a
zero
to
five
minutes
ago.
So
I
will
delete
that
right.
So
we
might.
C
I'm
not
sure
but
I
think
last
year
it
was.
We
were
able
to
block
everyone
from
adding
new
new
cards
and
just
allow
them
to
to
vote
to
about
some
of
them
right.
A
A
A
Okay,
so
in
terms
of
next
steps,
I
guess
we
we
put
the
survey
out
after
the
collaborator
Summit
and
maybe
the
ask
is
for
people
to
comment
and
discuss
in
the
issue
between
now
and
then.
B
C
The
issue
it
could
be
easier
if
I
draft
a
peer
or
PR
with
every
question,
so
everyone
would
be
able
to
just
update
or
do
something
directly,
I.
A
A
Yeah,
did
we
have
surveys
right?
Okay,
so
we
could
add
a
new
survey.
C
Is
that
what
just
a
result
from
last
year
yeah?
So
it
was
a
question,
but
we
have
also
also
response
from
people
yeah.
A
So
yeah
I
think
I
think
like
PR
pring
into
here,
like
it
could
be
like
a
new
directory
and
like
a
markdown
version
of
the
questions.
That
would
actually
be
pretty
good
and
easy.
C
I
think
on
this
one
I
add
some
feedback
after
your
email
to
Robin
and
other
people
yeah.
But
that's
all
on
my
part
at
least.