►
From YouTube: 2022-04-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.js
next
10
meeting
for
april
27
2022..
A
You
know
we
only
have
a
few
people
here
today
in
a
fairly
short
agenda,
but
I
think
it's
worth
running
through
just
for
a
quick
update
and
so
we'll
go
from
there.
Here's
the
link
to
the
minutes.
If
people
want
to
add
themselves
into
the
people
who
are
present,
it
would
be
great
I'm
just
going
to
do
that
for
myself.
While
we
speak.
A
Okay,
so
any
announcements
before
we'd
like
to
before
we
get
started
with
the
agenda.
A
A
That's
where
we
discussed
that
it
would
be
good
to
have
some
some
sessions
during
the
collaborator
summit.
We
did
in
past
meetings,
talk
a
little
bit
about
what
those
might
look
like.
A
I
have
submitted
two
one,
which
was
the
you
know,
our
our
sort
of
mini
summit
set
ones
which
were
like
deep
dives
on
esm
and
observability,
and
then
the
other
one
was
for
the
sort
of
you
know
track
level
just
met
where
I'm
imagining,
like
previous
collaborations,
there's
sort
of
like
a
common
track
where
everybody
you
know
is
there
before
we
do
a
breakout.
A
So
if
there
is
one
of
those
we
submitted
also
submitted
one
to
be
like
hey
a
little
bit
of
an
update
on
the
progress
on
this
effort
and
and
so
forth.
So
those
two
are
number
316
and
number
315.
A
we'd
also
talked
about
maybe
doing
a
follow-up
on
http.
In
terms
of
you
know,
we've
done
a
deep
dive.
I
I
did
mention
that
to
mateo
and
he's
gone
ahead
and
submitted
one
on
on
that.
So
I
think
that's
good
and
I'm
just
looking
to
see
right,
so
I
think
we've
got
our
submissions
in
in
terms
of
you
know.
A
B
Yeah,
because,
basically
I
I
did
it
so
that
mateo
was
submitted
something
about
http,
but
that's
really
great,
because
even
now,
with
the
release
of
node,
18
and
http
and
the
new
fetch
method
and
everything,
I
think
we
will
have
a
lot
to
discuss
about
that
and
at
least
have
some
feedback
from
the
user
base
which
is
great
to
have,
and
because
also
it
was
a
long
request
to
add
future
compliance
fetch
for
the
past
at
least
five
years.
I
think
maybe
more
yeah.
B
It
would
be
great
to
have
time
to
discuss
about
that.
So
that's
pretty
great
and
yeah,
also
on
the
two
other
parts
of
for
for
the
other
part.
I
didn't
add,
I
think,
a
lot
of
topic
we
want
to
to
suggest,
but
maybe
ever
some,
I
think,
driving
point
we
want
to
to
discuss
together.
At
least
we
we
won't
have
to
to
search
and
to
find
something
we
want
to
discuss.
A
A
You
know
putting
together
the
agenda,
the
sort
of
track
level-
one
I
think
we
do
want
to
put
together
agenda.
I
hadn't
done
anything
yet
because
I
was
kind
of
waiting
to
see
that
it
gets
accepted.
A
Oh
there
we
go
so
it
should
be
promoted,
so
I
don't
know
like
did
we
want
to?
We
could
brainstorm
that
a
little
bit
now
or
you
know,
I
don't
know
I
it's
maybe
not
sure
joe
you've
heard
anything
either
but,
like
I
don't
know
what
the
timeline
is
for
like
accepting
the
sessions
and
whether
we
have
time
once
we
hear
that
you
know
there
is
one
or
not
to
plan
out
the
agenda.
C
Yeah,
it's
a
good
question.
I
mean
I
think
they
have
a
lot
set
aside
for
node,
so
you
know,
I
think
we
should
just
try
to
move
forward
and
assume
that
things
will
work
out
but
as
as
things
take
shape,
we
can
talk
to
them
more
directly
about
it.
A
A
And
and
then
the
question
is
like:
is
this
an
opportunity,
so
I
think
the
track
level
session
was
like
okay,
you
know
the
goal,
in
my
mind
at
least
is
like.
Let's
get
some
broader
visibility,
you
know
encourage
people
to
come
and
that
might
be
covered
by
like
hey.
What's
you
know
the
short
intro
to
what
we've
already
done?
Does
the
longer
sessions
plan,
the
other
thing
that
could
be
useful.
There
is
some
broader
input
right.
A
So,
like
maybe
like
it's
the
you
know
technical
priorities,
you
know
from
the
from
the
things
that
we
have
what
would
be
useful
to
have
in
that
section
and
maybe
get
like
do
people
say
these
still
look
like
the
right
technical
priorities
or
are
there
other
ones
that
people
think
would
make
sense.
B
B
The
always
recurring
talk
and
discussion
about
should
we
move
and
and
enforce
esm
or
not
or
what's
a
target
for
that.
I
think
it's
a
quite
important
issue
to
try
to
address,
and
I
think
someone
was
talking
about
that,
and
maybe
james
was
talking
about
that
on
twitter.
The
other
day.
I
saw
some
thread
about
that.
So.
A
A
Track
level
agenda
is
like
maybe
30
minutes
right,
for
everybody
would
be
better
yeah.
So
I'm
just
thinking
on
that.
One,
like
you
know,
part
of
it
is
like
yeah,
it's
a
broader
audience.
Let's
bring
everybody
up
to
date.
I
think
we
can
give
a
sort
of
a
whirlwind
tour.
Tour
of
you
know
how
we
went
through
the
constituencies,
what
they
needed
and
ended
up
with
the
technical
priorities.
B
A
A
A
B
D
A
Yeah,
I
think
I
think
it
would
be
good
like
so
it's
like,
okay,
you
know,
put
slice
slide
up
with
existing
ones
right
and
then
we
can
ask
for
missing
no
longer.
A
Right
and
at
the
end
of
that,
you
know
in
theory,
you
know
me,
you
know
that
might
be
like
15
minutes
or
we
can't.
We
can't
do
a
lot,
but
we
could
at
least
get
some
get
that
conversation
started
right,
yep
and
if,
in
there
you
know
it's,
like
everybody
just
says:
oh
yeah,
those
are
still
the
top
most
priory
important
things.
Maybe
that's
good.
If
it
starts
a
whole
conversation,
then
you
know,
we
know
that
that's
something
to
focus
on
like
a
revalidation,
some
other
time.
B
That
yeah,
I
think
it's
a
good
start
and
we
will
see
if
we
because
I'm
pretty
sure
that
even
if
we
try
to
block
15
minutes,
we
will
have
in
one
case
no
one
will
be
saying
about
anything,
so
it
will
be
done
in
two
minutes
or
we
will
have
a
lot
of
people
trying
to
right.
Yes,
so
yes,
so
I
think
we
will
try
to
to
stay
with
that
plan
and
we'll
see
how
it
went.
B
Yeah
true,
but
it
will
really
depend
on
the
size,
because
when
we
were
in
montreal
I
think
we
had
some
group
with
20
to
30
people
sometimes,
so
it
also
depends
on
what
would
be
the
other
session.
At
the
same
time,.
A
Yeah
this
will,
I
mean
this.
One
in
particular,
was
meant
to
be
like
the
common
track,
so
everybody
you
know
but
we'll
see,
and
it
depends
how
the
track
comes
out,
but
I
think
this
is
a
good
plan
in
terms
of
contents.
Okay,
anything
else.
We
should
talk
about
on
that
agenda
item
before
we
move
forward.
A
B
A
I'm
gonna
stop
sharing,
then.
Okay,
the
next
one
is
create
communications
channel
to
gs,
newsletters
periodicals
joey.
You
want
to
update
on
on
that.
C
One
yeah
sure
I
think
the
status
is
that
we
had
a
pr
opened
up
that
we
merged
yesterday
and
it
outlines
the
process
to
engage
with
the
marketing
team
and
the
coms
team
in
the
open
jazz
foundation.
C
They
basically
have
said
they're
they're
pretty
busy
through
april,
but
I
think
we
have
a
system
in
place.
So
we
can
start
to
you
know.
The
end
of
april
is
pretty
much
here,
so
we
can
start
to
take
advantage
of
that.
I
think
you
know
one
next
step
might
be
to
figure
out
how
to
socialize
that
pathway,
so
that
could
still
be
done,
but
I
think
the
system's
in
place.
A
A
B
Okay,
yeah:
I
was
just
thinking
about
that,
how
it
will
work
who-
which
people
will
will
be
here
to
to
provide-
let's
say,
article
blog,
post
and
stuff
like
that.
A
A
The
expectation
is
that
they'll
help
provide
whatever
information
is
needed,
like
whether
it's
a
paragraph
that
says
like
here's,
the
thing
to
feed
to
the
to
the
periodical
you
know,
whoever,
whoever
is
saying
hey
we
should
do.
This-
has
to
also
put
provide
enough
information
or
answer
questions
to
make
it
happen.
A
A
And
like
if
you
read
through
that
and
there's
any
questions
that
you
have
or
or
like
you
think,
there's
more
clarification,
just
pr
something
in
that
said
that
that's
that
clarification
right
like
okay,
great!
I
will
check
that
because
yeah,
you
know,
I
think
joe
and
I
have
read
through
it
and
we're
like
okay.
This
seems
clear
to
us,
but
you
know,
but
once
you
once
you
write
something,
then
it's
hard
to
see
the
flaws.
So
if
you
do
see
some
some
stuff
just
pr
it
in
and
that's
the
way
yeah.
B
A
Okay
sounds
good,
then.
The
next
issue
is
suitable
types,
mini
summit
dot.
Next
steps
thanks
tierney
for
making
it
I
I
know
it
sounds
like
you
you're
challenged
right
now,
so
it's
great
the
the
the
one
step
that
I
know
this
is
is
sort
of
the
the
next
thing
that
we
were
actively
working
on.
That
was
the
updating
the
docs.
E
I
I
finished
up
reviewing
that
with
trot.
I
I
comment.
I've
commented
kind
of
the
next
steps
in
the
issue.
Specifically,
you
know
the
advice
I
got
from
trot
was
pinging
the
tsc
with
a
specific
proposal.
I've
documented
that
proposal.
I
can
link
it
here.
It's
it's
now
a
little
bit
hidden,
just
because
there's
been
a
few
things
after
it,
but
that
specific
issue
comment
is
the
one
that
should
be
reviewed.
E
I
can
update
the
main
thing
with
it
as
well:
actually,
but
yeah
basically
issue
proposal
or
the
sorry.
The
proposal
is
adopt
the
structure
and
begin
implementing
it
back
by
doc.
E
I
don't
think
wholesale
implementation
is
going
to
be
the
best
approach
forward,
so
just
start
going
through
and
doing
it
doc,
doc
fixing
doc's
parser
if
it's
needed,
where
it
comes
up,
you
know
and
kind
of
doing
that,
slowly
yeah,
the
other
other
thing
there
is
electron,
is
very
open
to
having
that
the
changes
feature
built
in
they're
actually
they've
wanted
the
the
feature
we
have
for
some
time
and
just
haven't
had
time
themselves
to
implement
it.
E
So
that's
a
good
way
for
us
to
kind
of
you
know
there
is
a
path
forward
on
that
too,
whether
that's
helping
them
parse
our
thing
or
which
I
I
don't
think
quite
fits
in
with
the
the
ideology
of
doc
sparser,
but
helping
them
parse
our
thing
or
implementing
a
way
to
parse
it
and
then
doing
a
transform
of
our
thing
to
whatever
that
implementation
is.
E
E
A
A
E
I
don't
know
if
he
said
he
I
he
said
he
was
fine
with
it.
I
can.
I
can
ping
him
to
ask
for
approval
if
that
is
helpful,
but
yeah.
A
It
would
be
like
as
soon
as
there's
two
like,
if,
especially
since
he's
so
active
on
the
docks
I'd,
be
pretty
comfortable
that,
like
once,
he
approves
it.
It's
been
open
a
long
time.
Nobody
else
has
been
saying:
hey,
don't
do
this,
you
know
so
actually
the
the
the
suggestion
in
terms
of
the
ping,
the
tse
approval.
What
I
actually
think
might
make
sense.
There
is
to
open
a
pr
to
make
this
a
strategic
initiative
that
says,
like
here's,
the
approach
of
what
we're
going
to
do
we're
going
to
do
it
doc
by
doc.
A
You
know
what
you
have
in
that
comment
and
that'll
have
it.
You
know
on
the
tse
agenda
as
a
you
know,
as
something
that's
got:
visibility
and,
and
we
can
sort
of
talk
about
progress
or
non-progress,
and
would
that
be
a
strategic
initiative
in
the.
A
E
Cool
perfect,
but
I
will
do
that.
A
Yeah,
so
if
you
want
to
do
that,
I
was
going
to
say:
I'd
volunteer
to
create
one
but
like
and-
and
I
think
what
I
what
I'd
say
is
like
put
yourself
as
the
champion
yep.
I
you
know
typically
they've
been
tc
members,
but
I
really
don't
think
we
wanted
to
limit
to
that.
So
I
think
you
know
that
would
be
a
good
it'd,
be
a
good
way
to
push
the
discussion
that
to
say
like
okay,
you
know:
do
we
need
to
have
a
co-champion
in
the
tse
or
not?
A
A
Champion
and
ideally
there's
like
a
link
to
just
that,
one
paragraph
or
two
that
outlines
the
the
the
proposal.
I
think
that's
a
good
way
to
yeah.
We
get
tse
feedback
because
people
can
say
yeah
that
makes
sense
or
not,
and
then
we
actually
have
it
documented
and
keep
track
of.
What's
going
on
there
cool
sounds
good.
Okay,.
E
E
To
say
I
I
will
probably
get
to
that
in
the
next
couple
weeks.
I
I
don't
know
if
I'll
get
it
get
to
it
in
the
next
couple
days,
so
like
either
next
week
or
the
week
after
probably,
okay.
D
A
Okay,
so
that's
good,
I
not
on
the
agenda,
but
I'm
just
trying
to
think
other
initiatives.
I
don't
think
I
have
any
updates
and
that
does
take
us
to
the
end
of
our
agenda.
A
Okay,
well
thanks
for
everybody's
time
and
we'll
see
you
again
in
a
couple
weeks.
I
guess
the
you
know
I
may
try-
and
I
haven't
had
a
lot
of
time
lately,
unfortunately,
but
we
can't
think
about
like
if
there's
anything
else,
besides
prepping
for
the
openjs
world,
I
think
that
actually,
maybe
is
a
good
thing
to
focus
on
the
next
many
summits
and
stuff.
A
But
if
there
is
anything
you
know
open
an
issue
tag
it
with
the
agenda
and
show
up
for
the
agenda
next
time
sounds
good.
Okay,
thanks
talk
to
everybody
later.