►
From YouTube: 2022-07-06-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
A
B
C
And
I
think
we
did
have
two
main
topics,
one
about
our
communication
channel
about
javascript
newsletter
and
pretty
much
everything
and
also
another
one,
which
is
a
feedback
from
the
mini
unit.
We
held
during
the
energies
conferences.
C
Yeah,
I
don't
really
have
something
special
on
the
part,
nothing
really
to
add.
I
will
just
add
myself
on
the
present
people.
A
B
A
So
create
the
communications
channel
this
one,
I
think
we're
just
kind
of
waiting
on
the
on
the
foundation.
Now
I
know
they've
had
some.
You
know
some
people
who
were
coming
or
going
or
let
me
there
was
an
issue
here
where.
A
The
next
one
was
suitable
type,
skinny
summit,
deep
dive
and
next
step.
So
let's
look
at
it.
C
Should
we
try
to
have
something
to
automatize,
to
have
some
automation
when
any
kind
of
let's
say
meeting
here
occurred
to
have
just
to
have
a
tweet
about
it,
because
I
think
a
lot
of
people
are
not
aware
first
of
the
calendar
of
this
kind
of
meeting,
but
also
to
have
an
easy
way,
because
I
know
you
posted
some
time.
I
also
do
post
a
link
sometime
for
the
meeting,
but
it
could
be
great,
maybe
node.js
or
bgs
foundation,
some
some
automatic
stuff
to
to
say.
C
A
A
So
maybe
like
an
issue
here
to
say,
is
this
because
I
think
the
first
conversation
needs
to
be
it's
like.
Is
the
social
team
happy
to
tweet?
Have
the
node.js
account
tweet
all
that
stuff
out
yeah?
I
personally
think
it
would
be
great,
but
you
know
I
think
the
discussion
there.
So
if
you
want
to
open
an
issue
there
to
sort
of
say
hey,
could
we
get
tweets
and
I
think
you're
thinking
like
in
advance
right.
C
Yeah
we
could
have
something
in
advance,
also,
maybe
every
I
don't
know
monday
to
have
a
tweet
which
would
we
recapitulate
recapitulate
every
meeting
we
will
have
for
the
weeks
for
the
current
week,
but
also
maybe
one
hour
before
with
some
information,
because
I
know
that
a
lot
of
people
are
not
aware
of
the
calendar
link,
which
is
right
a
bit
hidden.
When
you
go
at
least
on
the
node.js
website.
C
You
don't
really
have
a
lot
of
information
on
that
part,
so
I
think
you'll
be
better
and
could
be
part
of
this
kind
of
initiative
to
gather
more
people
to
communicate
and
just
discuss
about
node.js
and
the
community
part
which
would
be
a
great
one,
would
actually
be
good.
I
think
for
sure.
Okay,
so.
A
Do
you
want
me
to
open
an
issue
on
social
media?
Okay?
Why
don't
you
open
an
issue
on
the
social
team
and
make
a
suggestion
of
like?
Did
we
get
a
tweet?
You
know
what
do
you
think
of
a
tweet
once
a
week
that
announces
like
all
of
the
the
meetings
I'm
just
thinking
like
that
would
be
easier
to
manage
than
the
one
that's
like
an
hour
before
because,
like
benefit
doesn't
work,
there's
a
problem,
there's
more
so
starting
with
one
which
is
like
hey
here's,
the
upcoming
meetings
for
the
week.
C
Oh
yeah,
it
could
be
great
yeah.
I
would
open
that
I
wasn't
even
aware
of
this
team
social
team,
so
I
I
will
open
an
issue
on
that.
One
yeah.
B
A
Like
the
automation
that
we
have
to,
that
should
be
like
automating
that
shouldn't
be
that
hard,
I
think.
Even
so,
if
we
had
an
agreement
to
do,
it
would
be
yeah.
C
And
I
think
we
can
also
I'm
not
really
sure
about
that.
I
did
not
work
with
the
api,
but
I
think
on
youtube.
You
can
have
some
kind
of
api
notification
which
you
can
link
with.
I
don't
know
how
to
tweet
automatically
when
someone
start
a
stream
and
get
both
the
stream
name,
and
maybe
the
content
or
something
like
that.
If
we
want
to
tweet
about
this
meeting,
is
starting
right
now.
A
Yeah,
because
those
are
two
things
that
could
get
more
general,
you
know
involvement
people
showing
up
that
kind
of
stuff.
Yeah
drive,
awareness,
okay,
okay,
so
anything
else
before
we
move
to
the
next
one.
A
A
Right
so
I
think
these
are
all
these
are
also
useful
things,
but
we
should
probably
have
a
a
more
general
and
did
I
for
some
reason.
I
think
I
started
something.
C
Yeah,
I
think
we
should
open
an
issue
to
track
every
changes.
I'm
not
sure
I
think
we
created
one
or.
D
A
One
yeah
I
started
to
basically
create
this
to
say:
okay,
this
is,
and
maybe
we
can
kind
of
get
into
that
discussions
like
okay,
I
think
you
know
we've
got
a
few
more
deep,
dives
or
ones
that
we
haven't
done
the
deep
dive
before
so
maybe
we
can
do
that,
but
I
think
it
makes
sense,
for
you
know
this
team
now
to
be
like.
A
Okay,
let's
look
at
our
summary
of
the
the
technical
priorities
we've
agreed
where
the
status
is
and
what's
going
on
and
just
sort
of
see
like
you
know,
try
to
see
how
we
can
help
move
the
different
initiatives
forward,
the
questions.
Okay,
so
that's
actually
I
think
it's
worth
looking
at
this
one
and
maybe
working
on
it
a
little
bit
if,
if
that
makes
sense
to
you.
A
So
modern
http,
I
think
we
had
the
deep
dive
we
pr
in
into
the
contributing
sort
of
the
project
agreement
of
notes
landed
in
core.
A
I
think
that
one
in
terms
of
like
forward
progress,
it's
it's
maybe
a
matter
of
like
having
it
stink
sometime
or
something
would
be
a
next
step,
but
you
know
maybe
we
can
yeah
that's
urgent
to
do
now.
Right,
no.
C
C
I
think
we
will
need
to
have
some
kind
of
discussion
link
to
that,
maybe
not
just
for
fetch.
But
what
do
we
want
to
implement
because
on
my
side-
and
I
didn't
really
talk
about
on
the
issue,
but
I
took
it
during
the
summit
or
not.
For
me,
it's
a
bit
strange,
even
if,
let's
say
99
of
the
people
wanted
this
change
to
happen
because
they
had
issue
with
the
header.
A
C
I
think
we
will
also
need
to
have
some
parts
on
the
documentation.
I
didn't
check
the
fetch
documentation
since
it
landed
in
core.
I
don't
think
I
saw
a
lot
of
changes.
Maybe
I'm
wrong.
I
didn't
have
time
to
check
on
that
part,
but
at
least
we
will
need
to
document
that
on
both
the
documentation,
part
and
other
part,
we
we
find
interesting
to
to
have
more
information
about.
A
C
I
think
this
one,
you
can
link
the
merge
request.
You
did
following
the
the
opengs
collaborator
submit,
I
think
yeah.
Let
me
just
get
that
because.
B
C
D
B
A
A
So
support
for
features
from
the
latest
technoscripts
back
that
one
you
know
the
I
I
did
talk
to
michael's
and
I
think
the
I
mean
from
our
perspective
and-
and
I
think
that
his
just
but
I
agree,
I'm
not
sure
that
you
know
what
we
would
discuss
in
the
deep
dives
like
the.
Basically,
we
get
the
features
from
the
latest
atmosphere
from
the
v8
implementation
from
the
v8
and
he
helps
keep
that
fairly
up
to
date.
We
could
probably
do
more
to
help
you
know
try.
A
C
Yeah,
I
don't
remember
when
we
were
talking
about
that
like
one
year
ago.
I
think
we
did
some
kind
of
discussion
about
trying
to
implement
also
spec
which
are
not
yet
igma
compliant,
which
means
a
stage
like
two
or
three
or
something
like
that
right.
I
think
we
talked
a
bit
of
that,
so
I
don't
remember
exactly
what
it
was
about,
but
maybe
this
discussion
will
be
about.
C
Should
we
try
to
implement
work
in
progress,
spec,
which
is
some
kind
of
other
execution
than
implementing
v8
new
stuff,
and
I
know
v8
also
implements
some
stage
two
stage:
three
implementation
from
from
the
xmas
standard
yeah.
So
do
we
want
to
implement
some
other
stuff
on
top
of
that
in,
and
I
think
we
will
have
some
issue
when
both
node.js
core
and
v8
will
implement
the
same
function
differently
before
it
standardized.
C
Yeah
yeah
true
because
most
of
the
time,
let's
say
at
least
in
the
past
two
year,
v8
was
quite
fast
on
implementing
new
stuff,
so
yeah,
and
now
that
we
have
fetching
core,
I
think
we
don't
have
a
lot
of
difference
between
the
pure
v8
browser
compatible
function
and
node.js
core.
I
I
I
don't
think
about
something
which
is
really
used
in
one
environment
and
not
on
the
other
one.
So
I
don't
think
we'll
have
a
lot
of
issue,
but
should
we
have
a
discussion
about
that?
A
C
C
Though,
right
I
don't
remember
or
fetch
is
maybe
not
in
the
ecma
ecma
part,
but
I
think
it's
on
the
w3c.
C
I
don't
remember
exactly
where
the
fetch
spec
is
is
defined,
but
I
think
it's
maybe
more
yeah.
Well.
What
I
was
saying
I
think
fetch
is
more
on
the
w3c
than
on
ikma
park.
Yeah.
A
Right,
so
that's
where,
like
it
doesn't
you
know
that
that
that's
a
that's
the
case
where
yeah
it's
not
going
to
come
in
through
the
implementation,
so
we
do
deal
with
it
think
about
it
separately,
but
the
things
from
v8,
like
our
approach,
has
pretty
much
been.
We
just
wait
for
v8
to
implement
them.
There
are
people
who
are
active
in
the
tc39.
A
A
Although
it
might
still
be
worth
documenting
that
somewhere
yeah,
you
can
think
about
that,
like
so,
it's
sort
of
in
our
collaborator
guide
might
be
worth
having
something
to
document
with
what
we,
what
the
status
quo
is
there
right
so.
C
C
D
C
Yeah,
I
think
you
do
have
a
part
ecmascript
something
on
the
page.
I
don't
remember
yeah
so
here,
okay,
so
basically
under
related.
B
D
A
C
Sure
I
think
that
the
only
topic
we
didn't
really
address
on
the
path
to
submit
yeah.
But
do
we
have
a
lot?
I
don't
remember
what
was
the
input
of
other
people
around
that,
but
the
multi-threaded
support.
C
Okay,
so
it
was
about
the
worker
part
or
was
it
about
how
to
fork
and.
A
C
C
I
don't
know
about
the
node.js,
you
not
gs
european
confluence
in
in
near
dublin.
Do
you
have
more
information
if
we
are
able
to
do
a
summit
there
or
we're?
Certainly.
A
Working
on
it,
so
I
expect
it's
gonna
happen.
The
question
would
be:
do
we
wanna
wait
till
then,
or
do
we
want
to
do
like
a
virtual
one
like
we
did
before.
C
A
C
Yeah
true,
maybe
it
would
be
a
bit
harder
for
people
from
bus
from
america.
Let's
say
to
to
join
us
on
this
meeting,
but
I
think
maybe
not
all,
but
some
people
will
be
there
in
ireland
in
october
yeah.
So
maybe
at
least
we
should
try
to
have
a
good,
let's
say
better
setup
on
online
communication
at
least
yeah
due
to
have
something
a
bit
better
for
that.
But
I
think
it
would
be
better
for
most
of
us
to
be
there
in.
A
C
Because,
most
of
the
time
we
won't
have
a
lot
of
people
in
august
and
in
september,
pretty
much
everyone
who
is
coming
back
to
the
office
had
a
lot
of
different
topic
and
pretty
much
everything
so
october.
It
seems
to
be
a
good
timing
from
that,
and-
and
I
think
we
did
the
last
one
during
the
summit.
So
if
we
had
three
months
it
should
be
mid
september.
We
can
add
two
weeks
on
that
should
be
okay
right.
B
C
But
I
think
I
don't
remember
when
we
did
the
last
survey
should
we
try
to
use
this
time
during
summer
to
send
another
survey,
because
I
think
the
last
one
was
at
least
a
year
ago,
so
to
have
feedback
from
the
community
member
on
how
if
they
do
have
other
topic,
they
want
us
to
address
or
to
work
on
right.
Yeah
I
mean
that's,
that's
maybe
a
separate
issue.
It's
like.
Maybe
it's
yeah
yeah
yeah.
It
should
be
a
separate
tissue,
but
I'm
just
thinking
about
it,
as
you
are,
writing
that
so
yeah.
That
leaves.
C
C
A
A
You
know
so
we
could
create
an
issue
which
is
the
feature
request
and
has
you
know
probably
the
value
could
be
like
creating
that
feature
request
putting
in
the
details
and
contacts
that
would
have
enough
information
for
what
needs
to
happen,
and
then
you
know
some
promotion
about,
like
you
know,
can
we
making
it
like
say
hey?
This
is
one
of
the
things
which
is
important
in
terms
of
you
know,
moving
me
something
forward,
and
maybe
that
helps
get
some.
C
A
True
trying
to
get
standard
is
a
whole
different
type
of
work
than
actually
implementing.
I
think,
like
my
take,
is
like
the
loaders
and
the
diagnostics
channel.
There
are
people
working
on
it
as
active
and
those
things
are
likely
to
you
know
maybe
they're
not
moving
as
forward
as
fast.
So,
if,
like
you
know,
there
was
more
people
who
were
interested
to
help.
That
would
be
great,
but
it's
progressing
and
moving
forward
and
we'll
get
there
at
some
point.
A
So
it's
not
like
it's
not
like
some
places
where
there's
like
a
big
gap,
and
so
I
I
guess
it's
kind
of
like.
I
think
that
the
vm
module
is
the
one
place
that
I
don't
see
anything
going
on.
So
that's,
maybe
our
highest
value
of
doing
something,
to
try
and
see
if
we
guess
we're
going,
the
other
ones
I
think
are
are
progressing
along
and
in
the
end,
is
kind
of,
but.
A
You
know
had
a
particular
interest
in
one
of
those
or
somebody
you
know
listening.
Does
they
obviously
both
were
like
hey?
We
could
use
more
people
helping
out,
but
in
terms
of
like
having
momentum,
I
think
we're
good
there,
so
that
was
the
observability
then.
So,
if
we
look
at
the
next
steps,
there.
B
B
C
C
Yeah
because
yeah,
I
would
agree
because
changing
the
trust,
the
trace
model
with
perfecto
is
not
a
big
requirement,
but,
on
the
other
end
working
and
changing
entry
point
with
esm
and
loader
and
stuff
like
that
would
be
a
key
feature
for
us
to
implement,
because
some
people
are
blocked
of
using
esm
or
moving
from
common
gs
to
esm,
because
they
don't
have
the
features
they
need
on.
The
new
implementation
right
so
could
be
a
way
to
prioritize
some
work
being
done.
A
Yeah
right,
like
a
number
of
these,
like
even
yeah
yeah,
it's
interesting,
because
there
is
some
future
relation
with
the
future
requests.
It's
like
how
do
we
you
know
from
this
perspective,
like
we
can't
you
know
this
team
is
going
to
go
and
implement
all
these
things
like.
We
can
raise
the
profile
of
teachers
that
we
want
that
we
think
are
important
to
success
going
forward.
That's
one
way
to
kind
of
help
or
try
to
help
to
get
work
in
these
key
areas.
B
A
You
know
you
know
yeah,
I
easily
see
you
know
say
modern
http.
Are
we
done
or
is
there
no
work
to
be
done
on
that
front
in
terms
of
the
technical
priority
right
and
like
it
might
be,
like
you
know,
green
has
done,
nothing
to
do,
yellow
might
be
like
well,
we're
not
done,
but
it
looks
like
there's
stuff
going
on
and
then
red
might
be.
C
It
could
be
an
easy
way
for
newcomer
for
people
to
have
a
quick
overview.
I
think
for
more
veteran
people
in
northcore,
it's
with
a
link
to
the
re,
the
player
and
everything
they
will
be
able
to
see
that
quite
easily,
but
I
would
agree,
this
kind
of
flight
system
would
be
great
even
more
if
you
want
to
communicate
about
this
kind
of
initiative
outside
it's
an
easy
way
for
people
which
are
not
really
involved
to
have
a
quick
overview.
Let's
say:
maybe
I'm
just
thinking.
A
For
us,
in
terms
of
like
where
we
would
focus
our
discussion
or
not
right,
oh
yeah
also
also
could
be
yeah.
It
could
be
good,
but
maybe
we
can
think
about
the
next
time.
We
could,
you
know,
decide
whether
we
want
to
attach
this
to
get
this
landed
and
then
figure
out
what
our
sort
of
next
steps
are.
After
that.
C
C
C
D
C
C
Yep
should
be
great.
I
think
I
will
also
create
two
other
issues,
just
because
I'm
thinking
about
that.
So
I'm
between
sorry
for
that
we
did
discuss
at
the
start
of
the
year
about
documentation
and
stuff
like
that,
and
I
will
come
back
and
I
would
would
like
to
open
an
issue
about
two
main
topic
which
I
think
would
be
great
to
try
to
handle
for
at
least
the
lgs
ecosystem.
C
The
first
one
would
be
about
doing
some
translation
work.
I
think
we
are
now
one
of
the
last
main
framework,
slash
technology
just
being
in
english,
for
the
documentation,
which
is,
I
won't
say,
it's
an
issue,
but
I
think
it
can
be
when
you
compare
now
node.js
with
php
java
other
ecosystem.
I
think
we
do
like
this
translation
first.
This
is
on
the
api.
A
C
There's
some
support
for
that.
I
think
I
I'm
still
one
people
doing
having
access
to
what
would
we
use
a
clothing
to
do
some
translation,
but
I
think
right,
no
one
is
updating
or
changing.
Anything
so
would
like
to
try
to
purchase
initiative
again
would
be
great.
A
If
they're
volunteered
like,
I
think
the
problem
with
the
internationalization
stuff,
is
it
kind
of
petered
out
or
the
people
who
were
involved
no
longer
had
time?
So
I
guess
yeah
I
mean.
Maybe
it's
a
good
question
like
do.
We
think
internationalization
or
translation?
The
box
is
good
for
our
success.
If,
yes,
then
you
know,
maybe
it
should
be
on
our
technical
priority
list
and
driven
through
that
yeah.
C
C
I
think
the
main
issue
which
were
hard
for
people
was
how
do
we
want
to
collaborate
and
work
on
that,
but
once
this
kind
of
system
is
in
place
a
lot
of
community
members,
a
lot-
let's
say
at
least
three
to
five
per
language-
are
trying
to
be
active
and
to
push
documentation,
and
I
know
that
we
were
expecting
to
have
just
the
main
language
translated
and
with
the
community
effort.
We,
you
know
on
react
team.
C
I
think
we
did
translate
in
around
30
language,
different
language,
so
which
was
quite
nice
and
working
in
parallel
with
a
lot
of
people.
So
I
think
we
do
have
to
think
about
this
part.
I
will
open
an
issue
and
we
can
discuss
that
further
next
in
two
weeks
next
meeting,
I
think.
A
You
know
having
a
discussion,
there's
kind
of
like
there's,
multiple
different
aspects.
There's
one
like
do.
We
think
it's
important
to
the
future
of
ogs.
If,
yes,
we
should
document
that,
like
if
it's
a,
if
it's
not
just
a
place
to
have,
we
should
document
it.
We're
saying
at
least
that
we
acknowledge
this
is
really
important.
Even
for
not
doing
anything
separately,
then
is
the.
A
Can
we
find
people
to
do
something,
but
I
think,
like
yeah,
the
next
10
minutes
is
meant
to
be
like,
let's
identify,
what's
key
future
success,
not
tied
to
whether
we
can
actually
do
it
or
not.
Even
if
we
say
it
is
important,
but
we're
not
doing
anything,
that's
good
to
at
least
understand
and
that
doesn't
get
underneath.
C
I
I
think
I'd
talk
a
bit
about
it
during
the
deep
dive.
Maybe
not
this
one.
I
just
asked
about
it
and
I
think
we
we
wanted
to
discuss
it
a
bit
further
later
on,
and
we
all
forget
about
that,
because
I
also
talk,
I
think
about
the
example
repository
I
think
it
was
lately
handled
by
the
comcom
and
when
the
comcom
was
dissolved.
This
initiative,
about
example,
was
also
led
to
was
forgotten
by
everyone.
That's
it.
A
Could
be
a
good
discussion
again
as
a
topic
for
the
the
collaborator
summit
right.
C
Yeah
yeah,
I
think
it
would
be
great
to
have
something
about
documentation,
but
maybe
not
directly
document
api
documentation.
But
how
do
we
want
to
discuss
about
that?
I
will
open
two
issues
for
this
topic
for
the
next
next
10,
so
we
will
be
able
to
discuss
it
a
bit
further
with
everyone.
I
will
at
least
thank
tierney,
because
I
know
he
wanted
to
work
on
that,
or
it
was
some
one
of
the
initiative
before
that.
C
Yeah,
maybe
also
some
people
from
the
opengs,
maybe
not
openjs
foundation,
but
I'm
thinking
they
won't
also
try
to
have
a
way
to
reach
for
everyone,
and
I
saw,
I
think,
some
documentation
of
projects
inside
the
opengs
foundation
are
already
translated
in
multiple
language,
so
it
could
be
a
great
to
involve
them
on
how
they
do
that
processes
and
stuff
like
that.
Yeah.
A
A
You
know
thinking
about
what
our
next
kind
of
steps
are,
and
I
think
yeah,
one
of
the
things
we
should
think
about
over
the
next
couple
meetings
is
what
some
good
sections
be
at
the
next
collaborator
summit,
because
that's
probably
your
next
good
opportunity:
okay,
perfect,
okay,
thanks
nice!
Talking
to
you
and
we'll
talk
to
you
later
and
thanks
for
anybody
who's
watching
the
recordings
as
well.