►
From YouTube: 2022-03-02-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
march,
2nd
2022.
We
will
follow
the
agenda
that
we
had
in
the
issue
that
was
created
for
the
current
meeting
and
actually,
let
me
just
find
that
and
also
promote
joe.
A
A
B
A
Okay,
so
let's
go
on
to
the
first
issue,
which
is
identifying
next
mini
summit
topics.
A
So
we
opened
an
issue
and
started
to
discuss
that
a
little
bit
last
time,
but
the
goal
is
to
kind
of
come
up
with
okay,
what
topics
and
sort
of
when
the
suggestion
was
that
we
should
think
about
like
the
opengs
world
2022
in
terms
of
topics
as
well
see
if
some
might
be
better
or
one
place
versus
the
other.
A
A
C
I
think
last
meeting
with
we
were
speaking
about
reviewing
the
plan
from
modern
http.
Maybe
this
part
could
be
done
during
the
summit.
A
A
A
C
A
Any
other
thoughts
from
people
of
what's
important
to
we
can
probably
come
up
with
a
longer
list,
because,
if
we're
thinking
about
both
the
next
mini
summit
and
the
the
in-person
one,
we
can,
you
know
come
up
with
our
top
say
four
and
then
figure
out.
Maybe
you
know
when
when
and
where
to
do
those.
A
B
Yeah,
I
wonder
if
esm
and
observability
make
sense
to
talk
about
in
the
same
kind
of
pairing,
because
there's
some
relation
there
and
you
might
capture
the
similar
groups
of
people.
A
B
Like
and
I
kind
of
you
know
if
this
is
a
case
of
looking
for
which
to
make
sense
in
person
like,
if
possible,
in
person
which,
to
make
sense
virtual,
my
gut
would
be
the
wasm
and
security
ones,
because
they're
slightly
more
specific
might
make
sense
to
be
virtual.
I
think,
whereas
esm
and
observability,
I
feel
like
everyone,
you
know
whoever's
in
the
room
would
be
interested
in
that
kind
of
thing.
A
A
Looking
at
the
priors
okay,
so
then
that
would
leave.
We
would
have
covered
document
dimension.
Support
for
features,
okay,
observability
permissions
policy,
security
model
that
would
leave
better
multi-throated
support.
B
The
security
one
is
there
anything
that's
a
very
wide
topic
is
like.
Is
there
anything
specific
you
want
to
list
under
that
just
so,
we
can
make
sure
we
have
the
correct
people
in
the
room.
C
I
think
when
we
discuss
about
it,
it
was
a
lot
linked
to
the
policy
and
the
way
that
they
know.
Okay,
okay,
I
was
thinking
it
was
linked
to
how
or
how
they
know
we're
working
with
security,
to
allow
only
policy
to
some
file
system
or
stuff
like
that.
Okay,
but
I'm
I
was
wrong,
I
think.
Well,
no,
I
think.
A
A
So
I
I
think,
that's
a
great
place
for
us
to
sort
of
start
and
say:
okay,
what
what
is
our
security
module?
How
do
we
document
it
and
then
this
that
that
can
lead
into
like
okay?
This
is
our
security
model,
but
that
doesn't
mean
we
don't
want
to
provide
features
along.
A
The
lines
of
what
you
talked
about
like
dino,
provides
some
of
these
extra
things,
which,
arguably
you
know
you
can't
say
that
they're
actually
going
to
protect
you
in
all
sorts
of
situations,
but
they
still
help
people
manage
risk
and
that's
where
you
know
we
can
get
into
like
okay.
What
is
what
are
these
other
things?
We
think
add
value
right
right,
because
that's
that's
a
very
interesting
we've
had
lots
of
discussions
and
actually
at
some
of
the
collaborator
summits,
we've
even
had
discussions
on
those.
A
Well,
you
should
just
make
sure
that
the
docker
container
protects
you
from
some
of
those
things
so
anyway,
I
I
think,
that's
you
know,
building
from
like
here's
the
model
that
we
want
to
provide.
That
says
like
what
things
do
you
have
to
have,
and
then
we
can
get
into
that
discussion
about
what
other
things
help
you
know,
even
if
they're
not
strictly
within
the
security
model,
will
help
people
or.
A
A
B
B
A
A
A
You
know
to
talk
about
what
is
it
that
we
think
we
would
want
to
to
cover
like
we've
got
two
topics,
so
I
think
it'd
be
good
to
say,
let's
plan
some
time
to
try
and
go
into
those
two
topics
because
we're
there
in
person
we've
already
added
this
review
modern
http
plan
progress
are
there
other
sessions,
I
think
beth.
You
might
have
suggested
that
we
try
and
get
like
a
common
session.
Intro.
B
A
I
think
we
could
cover
it
in
underneath
there
right,
like
did
you
say
feedback
or
is
it
a
were
you
thinking
like
to
to
to
teach
people
or
not
teach
people,
but
like
bring
people
up
to
speed,
or
is
it
more
retrospective
or
what.
C
Sure
about
that
I
did
only
one
collaborator
submit
so
not
really
sure
how
it
went
before
that.
B
B
A
Right,
okay,
so
yeah
I
was
thinking
yeah.
So
it's
a
it's
kind
of
like
review
technical
priorities,
priorities.
A
Baseline
review,
maybe,
and
because
we
had
these,
we
also
have
and
I'm
finding
those
right
now.
D
D
A
Is
that
kind
of
what
you're
thinking
that
we
would
go
over
those?
And
we
could
do
we
could
do
kind
of
the
same
similar
whiteboard
sessions?
To
I
don't
know
whether
we'd
want
those
to
be
like
fine
with
what
we
had
there
or
do
new
ones
or,
but
that
it's
a
good
opportunity
to
to
yeah
with
a
broader
audience.
Hopefully,.
B
Yeah,
I
think
in
terms
of
timing,
it
makes
sense
to
review
them
and
then
open
up
like
a
whiteboard
session.
Saying
hey
are
any
values,
constituencies
or
technical
areas
that
are
not
listed,
that
we
think
should
be
listed.
That's
probably
my
way
of
doing
it.
Rather
than
going
back
and
starting
from
absolute
zero,
again
yeah
and
building
on
it.
A
E
I
think
this
is
a
good
idea.
My
only
concern
is,
as
I
remember,
having
long
conversations
about
some
of
these
things,
and
I
worry
that
we
could
just
get
right
back
into
the
weeds
or
something
just
to
be
mindful.
I
guess.
A
Yeah,
we
can
always,
you
know,
do
a
follow-on,
virtual
or
whatever,
but
I
I
like
the
idea
of
just
the
white
space
brainstorm
to
say
like
what
do
you
think
isn't
relevant?
What
do
you
think
is
missing
because
that
might
catch
some
things
yeah.
You
know
it
as
opposed
to,
like
you
said
like
going
into
the
the
like.
We
don't
want
to
get
back
into
the
bike
shedding
of
things
necessarily
because
that
we
could
do
offline.
It's
more.
The
idea,
generation
side
of
things.
E
Yeah
and
another
thought
I
have
that
is
maybe
slightly
off
topic,
but
I'll
just
throw
out
there
real
quickly
is
how
how
I'm
wondering
how
to
get.
E
How
to
encourage
sessions
at
the
collab
summit
you
know,
is
there
a,
I
mean
I
guess
we
just
need
to
raise
awareness
and
and
and
expect
that
different
groups
and
and
areas
of
focus
will
self-organize
or
do
we
think
that
we
should
help
in
that
effort
in
any
way.
A
I
mean,
I
think
in
the
past,
there's
been
like
an
organizing
committee
right
yeah
and
I
haven't
seen
any
sort
of
call,
or
you
know
that,
hopefully
what
we
see
is
some
people
who
are
interested
in
organizing
it.
And
then
you
know
there
was
a
repo
where
it's
like.
Hey,
submit
your
issues
and
stuff
like
that.
E
Yeah,
I
I
worry
that
we
need
to
be
that
needs
to
be
happening
and
I'm
not
sure
who's
yeah.
A
A
A
You
know
some
details
like
that.
That
says:
hey
you've
got
a
room
for
two
days.
You
know:
do
we
have
any
volunteers
to
organize
start
organizing
would
be
a
great
help,
yeah
yep,
so
I
mean,
if
that's
not
going
to
happen
from
that
sort
of.
You
know
that
suggestion.
Maybe
we
should
just
go,
and
you
know
any
one
of
us
can
go
open.
That
issue.
E
Yeah,
I
almost
wonder
if
you
know,
as
I
think
this
tends
to
happen.
You
know
node
can
kind
of
lead
the
way
we
can
maybe
create
an
issue
and
then
show
it
to
other
folks
can
be
like
oh
yeah,
I'll,
open
one,
just
like
that
elsewhere.
I
think
I'll
just
say.
As
an
aside,
I
think
we're
we're
feeling
the
the
pain
of
not
having
jory
around
she's
great
at
helping
some
of
these
things
on.
I
think
she
comes
back
pretty
soon,
but
yeah.
A
E
I'll
go
ping
the
the
channel
right
now
and
then
maybe
you
and
I
can
just
slack
for
a
few
once
I
get
the
details
to
make
sure
we've
got
enough
to
spur
engagement.
Thanks
sounds
good.
A
Okay,
so
sort
of
back
to
the
next
10
sessions
there
so
a
common
session.
I
think
that's
one
you
know,
hopefully
to
get
people
involved
and
the
plan
and
and
even
just
being
aware
of,
like
the
docs
that
we
have
and
contributing
to
help
keep
those
a
lot
like
not
alive
but
like
up
to
date
and
to
reflecting
what
we
think,
I
think
is
important.
A
Reviewing
modern
http
plan
progress
is
good,
a
baseline
review
and
then
two
technical,
deep
dives
anything
else.
People
think
we
should
try
and
do
there.
C
I
think
it's
already
quite
a
lot
because
yeah
for
each
submit,
I
think
we
we
we
block
four
hours.
I
don't
know
during
and
up
during
this
one,
how
many
times
we
want
to
to
to
block
and
stay
together.
I
think,
if
I
remember
right
last
time,
it
was
two
or
three
hours
for
each
collaborator
submit
yeah.
I
think
we
have
joe
was
it
two
days.
A
C
Sorry
maker
yeah
go
ahead
yeah
because
last
time
when
we
were
in
montreal,
I
think
there
is
also
a
working
group
related
to
observability.
A
A
A
A
A
A
Okay
and
I
guess,
then
the
question
would
be
when
yeah
so
openjs
world
is
june.
B
A
Yeah,
so
what
I
think.
B
A
B
A
A
Okay,
so
then
the
question
would
be:
are
there
people
that
we
can
think
of
that
we
should
be
inviting
maybe,
like
I
don't
know,
if
there's
any
volunteers,
for
opening
the
issue
for
the
next
mini
summit.
E
A
I
think
we
have
a
good
template
in
the
past
ones
and
then
basically,
people
can
think
about,
and
you
know
maybe
mention-
or
we
can
talk
about
in
that
issue
who
we,
who
we
want
to
make
sure.
Is
there
right.
A
A
Good,
okay,
I
think
on
the
next
10,
let's
double
check
the
no
new
panels.
Okay
on
the
next
one,
we've
already
discussed
as
well
like
the
summit
open.js
world
2022.
So
I
think
we
have
a
good
outline
there,
and
so
we've
got
whatever
data
we
need
for
when,
like
you
know,
there's
a
place
to
submit
suggestions
and
stuff
like
that
anything
more
on
that
one
we
should
discuss
before
we
move
on.
A
A
Nope,
okay,
note
weekly.
I
think
we
have
an
opportunity
to
reach
out
to
them
as
well.
E
A
A
A
So
maybe
like
joe,
could
you
and
I
take
an
action
to
maybe
try
and
reach
out
through
that
discussion?
Yeah?
Which
discussion
are
you
referring
to?
I
don't
really
want
to
go
into
the
details
because
I
don't
think
it's
public,
but
it
was
discussed
in
the
cpc,
and
so
I
just
you
might
have
some
knowledge
that
I
don't
have.
But
anyway,
let's
we'll
take
an
action
to.
A
A
Okay,
so
then
the
suitable
types
next
steps,
deep
dar
next
steps.
A
My
understanding
is
that
you
know
we've
got
some
things.
We
want
to
change
in
our
style
guide,
which
will
help
us
then
generate
jason,
structured
documentation
more
effectively.
There's
been
some.
I
know,
tyranny's
done
some
work
on
that
front.
I
did
talk
to
him
about
it
this
week
and
you
know
so.
Hopefully
we're
going
to
be
looking
to
get
some
prs
into
the
to
the
style
guide
to
help
facilitate
that,
but
we're
kind
of
still
working
on
that
in
terms
of
next
steps.
A
A
I
think
some
of
these
other
ones
we
may
need
to
think
about
how
we
have
like
a
follow-on
discussion,
although
I
think
I
think
our
best
bet
is
to
get
that
first
concrete
step
done
in
terms
of
the
style
guide
and
then
maybe
we
can
schedule
some
follow-on
discussions,
because
people
have
other
suggestions
or.
A
Okay,
that
takes
us
to
the
end
of
the
agenda.
Are
there
any
other
things
we
should
talk
about
this
week?.
E
A
Not
thanks
for
everybody's
time,
and
we
will
see
you
next
time
thanks.
Everybody
thanks
thanks,
bye,
bye,
see
everybody
later
bye.
Oh.