►
From YouTube: 2022-03-16-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
march
16
2022.
We
will
follow
our
standard
approach
of
going
through
the
agenda
that
was
posted
in
the
repo.
It
was
posted
as
issue
number
122.,
I'm
just
going
to
put
in
no
sorry,
I'm
just
going
to
put
in
the
link
to
the
minutes
if
people
could
add
themselves
in
that
would
be
great,
and
I
add
that
to
the
chat
where's,
the
chat.
A
Okay,
so,
first
of
all,
does
anybody
have
any
announcements
that
they'd
like
to
make.
A
A
A
Okay,
let's
go
and
look
at
the
issues
which
are
tagged
for
the
agenda.
The
first
one
is
identifying
next
mini
summit
topics.
I
think
that
one
I
did
take
a
quick
look
at
and
you
know
we've
discussed
what
they
are
they're
they're
documented.
What
we
need
to
do
is
open
the
issue
and
I
think
we
had
a
volunteer.
So
jean
is
going
to
open
that
issue
and
we'll
work
to
get
that
opened
by
the
end
of
this
week.
So
we
can
start
promoting
and
inviting
people
and
stuff
like
that.
A
Okay,
so
the
next
one
is
the
opengs
summit
world
2022
that
one.
I
know
we
had
a
good
discussion
last
time
as
well.
I
think
we've
got
a
pretty
good
idea
of
some
of
the
things
we'd
submit
joe.
I
know
you've
been
talking
a
little
bit
to
the
organizers,
so
that
seems
to
be
progressing,
but
I'm
not
sure
is
are
is.
Are
we
ready
to
start
submitting
topics
yet
or
is
that
still
a
little
bit
out?
Oh
you're,
on
mute?
A
There
we
go.
So
this
is
we're.
B
Talking
about
the
collab
summit
is
that
right,
that
is
yeah
yeah.
So
I
think
that
it
would
be
great
if
there
was
a
little
bit
more
instruction
on
in
the
issue,
but
I
don't
think
that
should
hold
us
back.
I
think
that
they
are
ready
for
people
to
start.
You
know
suggesting
sessions.
A
Okay,
so
I
guess
then
our
question
is
we
have
in
that
issue
a
number
of
sessions
we
wanted
to.
Let's
see
right,
we've
documented
a
number
of
sessions.
So
it's
really
a
matter
of
like
who,
from
our
team,
is
going
to
go
and
propose
those.
B
So
are
these
ideas
things
that
we
think
like?
I
guess
my
question
is:
do
we
need
to
get
interest
gauged
on
all
of
these
ideas
or
do
we
just
propose
them
and
then
see
what
happens
and
then
you
know
nobody.
A
I
think
they're
yeah,
I
think
we
just
propose
them
like
these-
are
the
ones
this
team,
we
think,
would
be
useful,
like
the
common
session,
like
maybe
I'll,
volunteer,
to
submit
that
one,
and
then
you
know
like
the
the
technical,
deep
dives,
the
assignment
observability,
like
that's
another
session,
which
is
just
like
our
you
know,
would
be
like
our
mini
summit.
Just
we'll
do
it
in
person
right
because
we
thought
those
were.
A
B
A
B
B
A
B
A
B
It's
all
good,
so
yeah
michael,
do
you
want
to
propose
the
to
the
common
and
the
baseline
review
and
and
I'll
just
throw
in
the
deep
dives.
A
A
Okay.
So
that's
good
on
that
one,
creating
the
communication
channels
to
the
periodicals
that
one
I
think,
let's
I
think
we
discussed
a
little
bit
before.
Let's
put
that
to
the
end,
and
we
can
sort
of
look
back
because
we're
going
to
spend
a
bit
of
time.
Brainstorming
there,
the
next
one
was
suitable
types,
mini
summit,
deep
dive.
A
Next
steps
from
what
I
understand
it's
actually
tyranny
is
is
having
a
meeting
with
with
rich
to
talk
about,
like
incremental
changes
to
the
docs,
to
support
the
the
types
changes.
So
I
think
that's
the
next
step
and
I'm
not
sure,
there's
too
much
else
to
talk
about
on
that.
One.
A
A
So
I'll
paste
it
here
in
the
chat
and
I'll
put
it
in
the
minutes,
it's
basically
a
pr
which
tries
to
start
to
document
what
we
discussed
in
terms
of
single
executable
application
support
as
well
as
I
did
some
proof
of
concept
so
like
on
linux.
It
actually
is
a
working
proof
of
concept
of
being
able
to
bundle
in
something
and
have
it
run
in
javascript,
along
the
lines
of
what
we
discussed.
A
So
I
found
it
interesting,
at
least
on
linux.
It
was
possible
to
make
it
work.
There
are
some
good
comments
already
in
the
in
the
pr
there,
so
I'm
going
to
make
a
few
changes
along
with
those
and
there's
some
good
issues
and
stuff.
But
if
you,
you
know
we're
at
the
mini
summit,
it's
worth
taking
a
look
and
commenting
there
and
but
that's
kind
of
some
some
forward.
Some
some
forward
progress
on
that
front.
A
So
then,
I
think
the
last
issue
we
had
on
the
agenda
was
the
communications
channel.
So
I
know
joe
you'd
reached
out
to
I
guess
one
of
the
the
groups
that
regularly
publishes
work
work
like
what
do
you
call
them
newsletters
right
and
they
sounded
interested
in
in
like
the
project
providing
some
topics
of
interest
right.
A
A
So
the
the
question,
then,
is
like
what
is
a
good
way
for
us
to
easily
feed
that
info
to
them.
Like
it.
The
kind
of
things
in
my
mind
that
are
key
is
one
you
know
have
a
place.
We
can
tell
those
groups
to
say
like
here's,
where
we'll
put
info
or
here's
how,
where
we'll
send
info,
if
that
we
think
would
be
good
for
newsletters
and
we
which
we'd
like
to
go
out
newsletters
and
have
them
watching
and
receiving
that,
and
then
the
flip
side
is
like
how
do
we?
B
Yeah,
it's
a
good
question.
We
had
talked
before
we
went
live
about.
You
know
using
maybe
a
repo
which
I
think
would
make
sense
for
us,
as
you
know,
collaborators
and
coders,
but
I
have
a
feeling
on
the
pr
and
marketing
comm
side,
that's
less
a
thing
that
they
have
kind
of
integrated
in
their
daily
routines.
B
I'm
wondering
if
we
can
leverage
the
foundation
in
some
way
and
maybe
it
still
isn't
even
a
repo
like
say
in
the
cross
project
council
or
I
mean
in
the
openjs
foundation
org.
We
have
a
repo
for
like
pr
marketing
and
you
know
alex.
Maybe
even
in
the
read
me
we
have
some
of
the
outlets
that
we
would
want.
To
I
mean
maybe
it
would
be
different
for
different
projects,
but
I'm
even
trying
to
think
about
like
cross
project
pipeline
sort
of
stuff.
B
You
know
if
somebody
if
we
could
rely
on
the
foundation
to
help
us
conduit
these
two
to
right,
publications,
weeklies.
What
have
you
then?
Maybe
that
would
work.
You
know.
B
Yeah,
it's
a
good
question,
I
mean.
Maybe
we
should
just
focus
on
what
we
think
we
need
and
then
you
know
can
see
from
there.
Yeah
expand
it
out
if
it
seems
generic
yeah
yeah.
So
what
do
we?
What
are
we?
What
are
we
thinking
that
we
want
to
get
out
there?
Are
we
talking
about
security
releases,
all
releases,
you
know
any
surveys,
or
you
know
kind
of
all
of
these
things
is
that
what
we're
I
think
it's.
A
Like
right
now,
you
know
if
we
pick
any
one
of
those
newsletters
there'll,
be
some
interesting
topics
and
but
they're
sort
of
picked
up
ad
hoc
and
I
think
bradley
you
were
thinking
like
say
for
the
next
10
it
might
you
know
it
would
be,
it
would
be
a
way
to
say
we
want.
You
know
say
we
had
a
survey
yeah,
we
want
to
say,
like
hey,
there's
a
survey
going
out.
Please
get
your
you
know
it's
it's
awareness
beyond
just
like
twitter
or
something.
C
Yeah,
so
there
are
definitely
different
crowds
that
people
might
not
be
aware
of,
especially
if
they
are
twitter.
Heavy
in
communication,
like
the
youtube
side
of
javascript,
is
an
example
of
a
completely
isolated
crowd
that
is
actually
fairly
heavy.
C
B
What
can
you
because
I
am
familiar?
What
is
what
does
that
look
like,
and
how
do
you
think
that
we
would
get
integrated
like
what
would
be
an
example.
C
C
So
antoine
hamel,
I'm
gonna
butcher
his
name,
sorry,
he
doesn't
have
social
media,
for
example,
which
I
think
would
be
great
if
I
could
move
to
that
kind
of
model
as
well.
C
But
at
least
branching
out
and
stuff
seems
reasonable
for
a
few
of
the
other
ones
like
people
who
are
only
going
through
courses
like
egghead
or
they're,
going
through
more
technical
blogs
and
youtube.
I
don't
think
that's
really
going
to
be
a
target
audience
for
us.
I
don't
know
how
we
could
integrate
with
how
they
do
things
like
you.
Don't
want
people
who
already
have
sponsors
to
have
extra
call
outs
and
things
like
that.
A
B
Yeah,
but
I
mean
we
could
but
but
but
I
I
feel
like
this
is
a
very
this-
this
conversation
could
be
its
own
mini
summit.
Lots
of
things
come
to
mind,
I
mean
I
could
imagine
you
know
we
could
ask
the
foundation
to
like
you
know,
do
a
do.
B
A
weekly
kind
of
you
know
summary
of
any
sort
of
notable
things
for
any
of
the
projects,
and
there
probably
might
only
be
five
minutes,
but
it
would
be
something
that
people
could
glom
on
to
in
in
what
you're
describing
bradley,
but
I'll
also
say
really
quickly.
This
makes
me
wonder
if
we
should
be
doing
more.
B
B
To
some
extent,
yeah
the
the
the
the
news,
the
blog
section
on
the
website
is
primarily
just
you
know,
releases
and
the
occasional
kind
of
thing,
but
it's
something
I've
been
asking
about
for
years,
especially
as
we
were
working
on
the
website
redesign
stuff
and
not
really
using
medium
anymore.
Like
you
know,
I
mean
that
could
just
what
I'm
thinking
is
that
could
be
a
a
pipeline
for
for
people.
It's
just
not.
C
Yeah
we're
just
trying
to
open
up
pipelines
because
in
particular
like
we
release
something
and
then
in
particular,
social
media
gets
a
hold
of
it
or
the
orange
site
gets
a
hold
of
it,
and
it's
just
chaos
having
people
able
to
participate
generally
alleviates
that
somewhat
or
feeling
that
they
know
something
is
coming
in
the
pipeline.
A
Until
it's
already
in
there
right,
like,
I
think
the
newsletters
are
a
very
good
concrete
one.
So,
let's,
if
we
can
figure
that
one
out,
that's,
I
think
a
good
thing
to
like
what
are
we
actually
going
to
do
there,
and
then
we
could
loop
back
to
the
other
ones,
because
I
think,
like
joe
said,
we
could
spend
quite
a
bit
of
time
talking
about
all
of
those
right.
B
Yeah
and
I
think
it
would
be
interesting
to
document
the
problems
that
we're
trying
to
solve
specifically
so
that
we
know
we're
we're,
not
spinning
our
wheels
that
wouldn't
solve
them,
because
I
think
if
I,
if
I
understand
you
correctly
bradley,
I
think
one
of
your
main
concerns
is
changes
in
node.js
that
you
know
the
collaborators
know
the
people
who
are
deep
into
the
project
know,
but
the
wider
you
know
community
isn't
aware.
So
how
do
we
surface
those
potential
changes?
B
Those
conversations
earlier
in
the
process
so
that
people
can
get
engaged
and
not
be
blindsided.
B
B
I
mean
you
know
as
silly
as
it
I
don't
know,
I'm
wondering
if
there
should
be
like
some
sort
of
like
comms,
you
know
github
team
and
when
anyone
thinks
like
oh,
this
conversation
should
be
surfaced.
You
know
tag
tag,
the
coms
team
and
say:
hey.
Can
we
get
this?
You
know
out
there
and
then
that
comms
team
would
know
to
you
know,
get
get
the
foundation
to
help
us
put
together
something
or
just
tweet
about
it
or
or
you
know,
send
it
out
a
week.
Please.
C
We
we
have
some
automation
already
with
the
node
twitter
stuff
and
we
also
have
the
now
available
github
actions
stuff.
Maybe
like
you're
saying
we
don't
need
the
comms
team
to
do
it
exactly.
They
could
just
triage
on
a
weekly
basis
and
just
we
could
tag
stuff
and
yep
a
week
gets
tagged.
It
gets
added
to
somewhere
yeah
yep
and
then
usually
I
would
guess
it
would
just
be
like
a
dump
of.
What's
going
on.
C
C
Yeah
and
be
like
this
pr
is
getting
close
to
landing
or
whatever,
and
just
some
instruction
on
when
you
add
the
tag,
you've
gotta,
do
something.
D
This
sounds
like
a
discussion.
We've
had
quite
a
lot
in
the
release
group
where
things
do
get
tagged,
notable
changes,
but
we
really
need
to
crowdsource
what
people
want
to
write,
because
the
people
who
know
what
to
articulate
about
that
particular
change,
you're,
probably
the
ones
who
wrote
it
or
heavily
reviewed
it.
D
B
Yeah
I
mean
the
slack
integration.
Stuff
is
good
for
the
social
team
for
tierney
and
me
you
know,
and
by
that
I
mean
it's
nice,
that
the
release
team
can
tag
us
and
we
can
just
jump
in
and
retweet
or
what
have
you
so,
whatever
we
think
would
work
would
be
good
to
have.
B
C
I
think
the
big
thing,
the
big
problem,
with
notable
changes
that
was
just
brought
up
is
there
is
a
lack
of
explanation
like
if
marking
something
with
a
label
either
one
of
these
notable
change-
or
I
don't
know-
needs
comms
whatever
the
other
label
is.
If
either
of
them
happen.
C
I
mean
if
you
open
up
an
issue
and
say
it's
gonna
close.
If
you
don't
comment
on
it
at
least
that
makes
people
know
that
hey,
I
tagged
the
issue
I
have
to
comment
on
it
so
say
I
were
to
tag
something
the
bot
sees,
I
added
it
and
they
open
up
an
issue
on
wherever
the
releasers
maybe
have
their
own
little
area
for
it,
and
then
that
just
puts
my
github
username.
It's
like
please
describe
in
a
paragraph
what
you
wanted.
D
Yep,
that's
it
and
yeah.
We've
played
quite
toyed
with
the
idea
before
just
having
a
bot
say
hey,
this
has
been
tagged
with
notable
changes.
Can
anyone
just
post
this
comment
or
edit?
This
comment
with
what
you
want
to
be
reflected
in
a
change
log.
It
might
be
nothing
it
might
or
it
might
be.
Hey.
I'm
gonna
write
a
paragraph,
but
it's
still
a
crowdsourcing
problem.
I
think.
D
B
Yeah-
and
I
can
see
it
being
in
in
the
in
the
pr
issue
itself-
the
tooling
is,
is
there
you
add
the
label?
You
know
whether
an
issue
not
a
comment,
pops
up
with
the
person
who
added
the
labels
tagged
saying
please
describe
you,
know
what
what's
notable
here
and
then
maybe
even
have
some
tooling
within.
B
I
keep
thinking
of
slack
because
I
don't
have
a
good
handle
on
my
github
messages
yet,
but
if
there
was
like
a
tooling
thing
where
a
weekly
digest
comes
in
to,
like
you
know
some
sort
of
comms
channel,
we
could
click
through
to
each
one.
You
know
grab
the
summary
and
and
surface
them.
You
know
into
the
pipeline
whatever
that
means.
C
Yeah,
that
would
be
a
good,
because
that
would
give
newsletters
releases,
whoever
something
they
can
pick
and
choose
what
they
want
to
put
yeah,
because
it
might
be
that
they
want
to
skip
a
week
for
one
issue,
for
whatever
reason
stuff
like
that.
A
C
Well,
it
depends
if
all
the
comments
are
inline
in
a
pr.
It
definitely
doesn't
make
sense
if
it's
like
a
separate
thing
that.
C
B
B
Yeah
yeah,
I
I
feel
like
if
we,
if
we
set
it
up
in
such
a
way,
you
know
whether
it's
tierney
and
me,
although
I
hesitate
to
volunteer
for
too
much
more
stuff
but
or
or
you
know,
someone
at
the
foundation
if
they
could
quickly
scan
a
a
slack
channel
or
know
how
to
pull
up.
B
You
know
an
org
with
all
the
issues
tagged
a
certain
way
and
know
that
the
summary
is
going
to
be
in
there
there
they
might
be
able
to
do
some
of
that
legwork
and
then
throw
out
an
email
or
some
sort
of
push
to
whatever
organizations
like.
I
think,
if
we
minimize
friction
and-
and
you
know
there,
there
will
probably
need
to
be
a
little
bit
of
work.
But
as
long
as
we
minimize
friction
as
much
as
possible
that
it's
doable.
A
A
Then
saying
put
this
tag
on
the
existing
issue
right
and
I'm
just
thinking
that
doesn't
require
any
work
on
the
automation
front,
because
you
could
end
up
with
then
a
repo
that
has
some
small
number
of
like
here's
things.
Here's
news,
which
we
would
be
will
you
know,
would
would
make
sense
to
feed
to
the
the
groups.
B
It
might
be
interesting
to
talk
to
you,
know
robin
and
alex
and
jory
about
this
to
see
because
we're
kind
of
maybe
guessing
as
what
we
think
they
would
find,
help.
D
Yeah
just
fyi
there
was
similar
discussions
yesterday,
they've
started
a,
I
don't
know
if
it's
weekly
or
every
two
weeks,
marketing
public
meeting
for
openjs-
and
I
sat
in
on
my
and
some
of
these
discussions
came
up
around
where
they
should
be
surfacing
updates
for
node
in
particular,
should
they
be
on
the
openjs
website.
So
I
think
there's
all
kind
of
links
together.
C
I
mean,
regardless
of
what
we
do
with
a
bot.
What
was
being
mentioned
about
having
just
the
repo
would
most
likely
be
the
output
of
the
bot
anyway,
so
we
could
just
start
there.
A
A
C
B
A
Yeah,
like
the
readme
for
the
for
their
repo,
would
be
like
hear
the
instructions
of
you
know.
You
have
a
piece
of
news
that
you
want
to
get
out
there
yeah
paste
it
here.
Yep,
you
know,
and
then
what
is
some
explanation
what's
going
to
happen?
Well,
it's
it
could
be
like,
and
we
will
send
a
summary
of
this
to
these
newsletters
on
a
weekly
basis.
We,
the
openjs
staff,
will
review
it
for
publication
on
the
website
on
a
periodic
basis
like
we
could
then
add
a
list
of
things.
A
A
A
B
A
B
A
B
Yeah
yeah
and
I
agree
beth
the
template.
You
know,
links
links
to
the
relevant
issues
and
whatnot
and
a
good
summary
yeah.
I
I
think
the
foundation
would
be
a
minimal
to
to
to
popping
into
a
repo
once
a
week
and
and
just
pulling
out
the
issues
and
then
once
they
do
surface
them,
they
close
the
issue
and
it's
kind
of
easy
to
manage.
A
B
You
know
we
have
the
social
team
repo,
but
this
seems
different
than
that
right.
This
should
just
be
its
own
com
sort
of
report.
D
B
Yeah,
ironically,
there
is
a
tweet
repo.
That's
so
people
go
to
the
social
team.
I
know
this
is
what
happened
to
you
the
other
day,
michael,
but
people
go
to
the
social
team,
repo
and
they're,
like
I
don't
know
what
what?
But
you
go
to
the
tweet
repo
to
get
a
tweet
out
so
yeah
something.
Obviously
we
would
need
to
talk
to
tierney
about
too,
but
I
could
go
either
way
really
on
that
it
could
be
like.
B
B
That's
to
me
in
this
scenario:
we're
describing
that's
a
little
bit
manual
like
alex,
for
example,
would
they
would
register
their
in
interest
with
her
and
she
would
have
a
list
somewhere
on
the
other
side
of
the
fence?
But
I
mean
people
could
watch
the
repo
people.
Could
you
know?
Do
it
self-serve?
I
just
don't
know
if
anybody
who's
doing
that
sort
of
work
is
going
to
be
interested
in
that.
A
B
A
B
C
C
A
Just
like
a
news,
repo,
maybe
is
the
easiest
that
way.
You
know
people
can
actually
register
if
you're
yeah
github,
you
can
just
watch
it
and
get
all
the
things
that
way,
but
then,
as
an
extra
service,
you
know
that
we've
asked
the
foundation
comms
teams
to
look
once
a
month
and
send
a
summary
to
an
email.
If
that's
what
you
want
to
sign
up
for.
A
A
C
A
So
I
guess
we'd
need
to
see
if
the
foundation's
up
for
that-
and
I
guess
you
know-
confirm
that
we
think
that,
like
the
newsletters
would
want
to
register
for
something
like
that.
A
Okay,
well,
I
think
that
that's
that's
pretty
good,
and
you
know
once
we
get
that
confirmation,
I
I
think
it's
basically
a
readme
with
a
repo
with
a
readme
that
has
that
basically
documents
this
and
then
some
some
publicizing
to
the
rest
of
the
collaborators
to
say:
hey
we
put
this
in
place,
yep,
yep
and-
and
I
suspect
the
foundation
may
also
want
you
know
joe.
If
you're
saying
they
were
looking
at
putting
some
stuff
on
the
website
and
stuff
like
that,
would
be
a
feed
for
that
as
well.
B
Yeah
yeah,
considering
right
now
we're
not
using
medium
and
the
blog
on
the
website
is
really
just
about
releases.
You
know,
I
think,
having
other
outlets-
and
I
think
you
know
just
having
the
foundation
help
us
with
that
sort
of
an
outlet
on
their
blogs,
makes
sense
to
me.
A
A
Okay,
anything
else
on
that
one,
we
should
talk
about.
A
I
guess,
then,
that
we
are
at
the
end
of
the
agenda.
Does
anybody
have
anything
else
we
should
talk
about
before
we
close
out.