►
From YouTube: 2022-03-30-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
team
meeting
for
march
30th
2022
we'll
follow
the
agenda,
which
was
tagged
in
the
issue,
which
was
in
issue
number
125..
Before
we
get
started.
Does
anybody
have
any
announcements
that
they'd
like
to
share.
A
A
Hey
the
next
summit
openjs
world,
2020
2022
that
one
I
think
we've
discussed
and
we
have
a
topic.
I
think,
if
I
remember
actually
you
and
I
joe,
I
think
volunteered-
to
submit
some
submit
these-
do
the
submissions.
A
A
Okay,
so
I'll
try
and
do
that
before
the
next
meeting,
the
I
can
go
back
to
the
minutes
and
look
at
the
ones
joe
and
I
each
volunteered
to
do
a
couple
so
we'll
get
those
submitted.
I
think
joe
at
this
point,
the
the
summit.
Repo
is
ready
for
for
submissions
right.
B
It
is
yeah,
I
I
I
still
feel
like.
There
could
be
a
little
bit
more
there
to
help
folks,
but
I
think
it's
good
enough
and
we
should
just
start
reaching
out
to
people
yeah
and
promoting
and
stuff.
A
B
Yeah
so
I
talked
to
robin
about
this
because
you
know
you
and
I
talked
to
michael
and
you
know,
robin's
very
open
robin
the
executive
director
of
the
open
jazz
foundation
is
very
open
to
figuring
out.
You
know
what
works
well,
she
seemed
even
open
to
you
know.
B
I
think
when
we
were
talking
about
it,
we
were
trying
to
find
some
sort
of
middle
ground
between
you
know
collaborators
who
are
in
github
and
that's
you
know
primary
action
versus
you
know
perhaps
like
marketing
folks,
who
are
you
know
not
as
well-versed,
but
she
seemed
open
to
even
like
just
having
people
tag
her,
which
I
think
you
know
is
maybe
not
the
best
approach,
but
maybe
having
either
a
team
that
she
could
be
on
or
she
and
alex
or
any
other
folks
or
you
know
any
any
any
of
the
thoughts
that
we
had
had
michael
like
around
separate
repo,
and
you
know,
whatever
I
think,
was
easiest
for
the
collaborators
she
would
kind
of
meet
us
there
right.
B
Yeah,
but
I
do
wonder
michael
how
much
this
conversation
overlaps
with
what
we're
talking
about
in
another
conversation,
which
I
think
is,
is
public
right.
There's
an
issue
in
the
tsc
about
noteworthy
stuff.
A
B
A
I
think
I
think
it
was.
This
was
more
external.
Looking
versus
like
that
discussion
is
the
internal
looking
like
even
for
collaborators
who
watch
the
repo
they're,
not
necessarily
you
know
they
they
they
that
other
discussions
like
it
would
still
be
good
to
help
surface
important
things
for
them
to
be
aware
of,
but
I
think
even
like
this.
This
is
more
the
greater
community
of
like
there's
some
great
thing.
You
know
great
publications
like
node,
weekly
and
some
others,
and
we
can
get
a.
We
can
get
interesting
things
out
to
that
larger
group.
A
You
know,
for
example,
hey
there's
a
mini
summit
on
something
if
we
think
that
that
many
that
larger
group
would
be
interested
and
how
do
we
sort
of
feed
stuff
versus
it
just
being
ad
hoc?
What
gets
picked
up-
and
I
think,
in
this
case
it
kind
of
requires
somebody
to
be
volunteering
to
help
craft.
The
message
right:
yeah,
yep,
yeah,
an
issue.
A
Ton
of
comments
on
it
on
it
isn't
going
to
be
that
that
sort
of
here's,
the
paragraph
that
makes
sense.
So
that's
why
I
think
like
in
this
case
it's
somebody
saying
we
want
to
go
to
the
larger,
the
bigger
community
and
I'm
volunteering
to
to
sort
of
help
craft
the
message:
here's
the
message
I
want
to
send
out
right
and
have
sent
out
and
probably
answer
questions
or
whatever.
If
those
groups
have
any
questions.
B
Yeah
yeah
internal
versus
external
makes
sense
yeah,
I'm
maybe
just
confusing
the
two.
A
B
Yeah
yeah
and
I'm
thinking
about
it
further
there's
definitely
overlap
because,
like
for
example,
you
know
there
are
a
couple
of
people
that
that
were
surprised
by
the
test-
runner
work
that
are
not
collaborators
so
there
there
is
definitely
some
overlap.
A
Right
like
if
there
was
like,
if
you
wanted
to
get
broader
input,
you
could
have
been
like
hey
heads
up.
There's
work
going
on
within
the
within
the
node
community
to
look
at
a
a
built-in
test.
Runner.
You
know
if
you
have
thoughts
or
whatever
yeah
be
aware
or
whatever
yep
yep.
A
So
I
mean
it
seems
pretty
low
overhead,
although
since
it's
since
we
were
talking
about
it
being
in
the
social
team
good
to
have
your
cut
your
feelings
on
that
from
being
in
the
social
team,
the
you
know
a
repo
where
you
can
open
an
issue
saying
here's
the
message
we
want
to
get
out
to
those.
You
know
those
periodical
publicate,
publications
whatever
and
then
are
like
hey.
A
B
Yep
yeah,
that
sounds
good.
That
sounds
good.
I
think
the
question
becomes,
you
know
where.
Where
do
we
do
this?
If
we
want
to
do
it
in
a
repo,
do
we
want
to
do
it
in
a
node.js
repo
or
or
do
we
want
to
do
it
like
in
the
open,
js
repo,
so
that
other
projects
could
potentially
take
advantage
of
this
approach
as
well?
You
know
the
question
would
be.
A
Oh,
so
you
mean
like
subscribers
yeah
subscribers,
like
from
the
creators.
I
don't
think
it
make.
You
know.
If
we're
just
going
to
have
repo
you
create
an
issue,
I
don't
think
it
matters
to,
you
know,
say
the
node
project,
whether
it's
in
node
or
it's
in
the
openjs
foundation.
The
only
effect
is
on
the
subscribers.
A
And
I
I
I
can
see
my
gut
feel:
is
it's
not
going
to
be
such
high
traffic,
that
it's
a
detriment
and
it
may
be
a
positive
to
have
it
at
the
open
gs
level,
because
hey
as
depending
on
my
periodical
or
newsletter
or
whatever
it
is,
I
may
be
covering
javascript.
So
I
may
want
news
from
more
places.
B
A
B
A
Adjust
it,
but
you
know,
and
it
gives
one
it
gives
potentially
more
value
and
like
an
offering,
I
think,
that's
actually
nice
for
the
foundation
to
say,
like
here's,
one
of
the
services
that
we
give
you,
we
we
actually
help
bridge
the
the
the
gap
here,
yep
yep
between
coders
and
marketing
folk.
A
That
make
sense
to
you,
yeah,
okay,
so
I'll,
take
the
to
open
I'll,
take
the
action
to
open
the
pr
for
that,
and
then
we
can
just
you
know,
sort
of
close
in
in
the
open
just
repo,
and
we
can
then
hopefully
you
know
just
create
the.
A
Yeah-
and
you
know,
I
think
if
we
open
that
pr,
we
can
point
them
to
it
to
say
hey.
Does
this
look
like
what
you
think
you
agreed
to
thought
was?
Was
reasonable?
Yeah
sounds
good
as
well
as
the
confirm
with
the
cpc
and
everything
that
they
agree.
It
can
be,
it
makes
sense
at
the
open
gs
level
and
if
not,
we
can
always
fall
back
to
the
node
recall.
A
Okay,
that
sounds
good.
The
next
thing
is
on
the
agenda.
Suitable
types
mini
summit,
deep
dive
that
one,
I
don't
think,
there's
anything
report
this
week.
A
A
So
I
think
we've
got
some
good
action
going
on
on
that
front
and
on
the
types
front,
I
think
that
the
next
step
is
is
refining
the
the
dock
guidance
a
little
bit
and
I
believe
tierney
met
with
rich
and
there's
a
there's,
a
path
forward
on
that.
So
that
takes
us
to
what
was
on
the
agenda.
I
think
the
thing
we
should
now
just
double
check
is
the
summit
itself
and
make
sure
that
we're
all
aligned
and
think
that
we're
ready
for
that.
So
I'm
going
to
open
that
issue.
A
So
for
anybody,
if
you
want
here
just
pasting
that
in
the
chat,
so
we
have
it
scheduled
it's
the
seventh
ten
to
two
thanks
joe
for
adding
it
to
the
the
calendar.
A
I
added
it
to
my
calendar,
but
I
forgot
to
move
it
to
the
right
one.
So,
but
thanks
thanks
for
adding
it.
So
it's
in
the
public
calendar
and
we've
got
two
topics:
wasm
and
security
model
policies.
A
I
pinged
a
few
people
on
the
wasm
side
and
it
looks
like
you
know:
we'll
actually
have
some
people,
like
lynn,
clark
from
the
and
and
possibly
luke
wagner
from
the
wasm
side,
to
help
us
in
that
discussion,
which
is
good
and
colin
recommend
a
number
of
people
who
hopefully
are
now
aware
and
may
show
up
the
security
model
of
side
of
things
actually
just
before
we
switch
to
the
security
model.
I
see
jean
you
mentioned
the
of
interest
to
the
napi
working
group
right
yep
right.
A
A
A
Okay,
so
that's
sense,
that's
a
good
point
and
I
guess
then
the
other
side
is
like
who
might
me
who
might
we
want
to
reach
out
to
in
terms
of
the
security
model.
B
Yeah
aristotle,
liran
yep,
I
should
maybe
reach
out
to
marcin.
I
don't
know
if
he's
aware.
B
I
would
think
he
would
be
through
the
note
channels,
but
I'm
not
sure
actually
yeah
do
you
know
his.
A
I
also
wonder
if
there's
anybody.
A
I'm
also
wondering
about
we
had
some
resources
from
trail
of
bits,
helping
at
one
point
I
may
I'm
going
to
reach
out
to
robin
just
to
see.
A
Okay,
I've
just
sent
mashup
message
to
robin
and
we'll
see.
If
maybe
we
can
get
somebody
there
interested.
A
A
Okay,
just
thinking
any
other
thoughts
of
who.
A
And
I
guess,
if
that's,
I
think
that
was
the
only
other
thing
I
thought
was
useful
to
do
so.
We
have
that
scheduled
for
next
week.
Anything
else
we
should
talk
about
before
closing
out
for
this
week.