►
From YouTube: 2021-02-04-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.
It
is
february
4th
2021
we'll
follow
the
agenda
that
was
in
issue
number
45
in
the
repo,
and
so
I
guess
the
first
thing
is
I'll
paste
the
link
here.
If
people
can
add
themselves
into
the
attendees,
that
would
be
good
and
then
before
we
get
started,
does
anybody
have
any
announcements
that
they'd
like
to
share.
B
I'll
just
remind
folks
that
the
survey
is
open,
you
know
if
you
haven't
taken
it,
take
it.
If
you
have
promote
it
all
that
stuff.
The
link
is
on
the
home
page
of
the
the
website.
A
A
So
I
think
we
we
basically
put
that
together
and
maybe
that
issue
we
should
close
out
and
open
a
new
issue,
because
I
think
you
know
we've
landed
it
and
the
current
work
is
to
validate
sort
of
get
broader
input
and
validate
that.
What
we
have
there
is
is
good
and
we're
talking
with
the
foundation
about
doing
a
survey,
and
we
put
that
we,
I
wonder
where
we
put
those
questions
together
in
some
I'm
just
looking.
A
Maybe
there's
another
issue
here:
that's
not
on
the
agenda
that
does
cover
that,
because
we,
we
definitely
did
some
work
in
terms
of
putting
together
the
questions
and
we
sent
them
off
and
looking
like
the
survey,
you
know
we
might
target
something
like
the
end
of
this
month.
Just
so,
it
doesn't
overlap
with
the
the
current
one,
but
I
am
trying
to
find
where
that
went
where
that
issue
went.
C
D
Should
be
this
one,
this
document,
I
think
it
was
the
last
one.
D
A
A
I
think
we're
going
to
end
up
writing
a
a
blog
post
to
just
provide
some
context
kind
of
like
what
we
did
for
the
the
promises.
Unhandled,
sorry
unhandled
rejections
survey
that
was
done
earlier,
so
if
anybody
wants
to
help
with
that
or
get
involved
in
that,
let
me
know
and
I'll
pull
you
into
that
work
as
well.
A
Okay,
so
then
there's
mary,
let's
promote
her,
so
the
other
things
we
had
on
the
agenda
were
the
key
technical
areas:
brainstorming,
the
that
list,
which
we
started
last
time.
We
also
had
the
next
10
years
for
collaborators
and
revisiting
the
time
slots.
A
Now,
maybe
once
we
get
mary
promoted,
we
can
talk
about
the
last
two
because
I
think
we've
deferred
them
for
a
couple
times,
and
I
I
know
she
was
you
know
helping
to
push
those.
So
I
think
it
would
be
good
to
see
if
we
can
talk
about
those
first.
D
A
A
I
just
sent
her
that
info
through
twitter
that
you
in
the
end,
use
the
the
browser
instead
because
it
kind
of
looks
similar
in
that
I
see
the
the.
D
A
A
E
E
A
A
So
we
were
just
just
before
you
joined.
We
were
just
looking
at
the
issues
that
were
on
the
agenda
and
two
of
them,
the
sort
of
next
10
years
for
collaborators
and
their
visit
time.
Slots
we'd
skip
the
last
few
times
because
we
were
waiting
for
you
to
be
here
to
to
push
help
push
those
forward.
So
I
thought
we'd.
Maybe
you
know
start
off
by
talking
about
those
and
next
steps
that
make
sense.
Mary.
F
Yeah
so
I
started
a
doodle
a
while
back.
I
haven't
looked
to
the
results
in
a
while.
I'm
not
sure
if
the
doodle
is
still
up.
A
F
So
maybe
we
need
another
method
to
determine
a
time
for
the
meeting
sure
I
think
the
dudu
might
not
be
the
the
best.
A
A
F
A
I
guess
people
are
like
some
people
are
in
europe
as
well
right.
D
C
A
D
A
A
A
B
Tierney-
and
I
were
talking
about
doing
the
social
team
meeting
on
the
off
weeks
at
the
same
time,
okay,
but
you
know
we
haven't
booked
that
yet
so,
first
hey,
we.
B
Them
to
book
it,
but
but.
F
Yeah,
I
think
that
time
we
can
at
least
try
the
time
and
try
it
for
a
few
weeks
and
see
how
how
it
tends
to
go.
A
A
B
B
D
Yeah,
but
I
think
it's
pretty
empty
right
now
I
wasn't
able
to
attend
to
it
a
bit
earlier.
I
don't
know
if
someone
was
inside.
F
But
I
don't
think
it
would.
I
can
check
with
him
if
that
works.
A
B
Yeah
yeah,
so,
okay,
okay,
maybe
just
do
it
next
week,
since
we
already,
you
know,
spent
half
the
meeting
this
week,
yep
yeah,
let's
or
I.
A
Could
yeah,
okay,
so
you're
saying
we
could
reschedule
for
it's
true.
We
could
do
that,
okay,
so
why
don't?
I
change
that,
instead
of
three
weeks
to
be
next
week,
that's
the
11th
right
yep
and
then
repeats
every
two
weeks.
Every
wednesday,
okay,
there
it's
in
the
calendar
I'll
go
back
and
delete
the
other
ones
afterwards.
A
Okay,
so
we
were
adjusted,
adjusted
to
thurs
12
eastern
we'll
try
that
out
for
a
while-
and
maybe
we
can
just
close
out
this
issue
and
we'll
reopen
if
we
need
to
adjust
again.
Does
that
make
sense.
A
A
Okay,
so
that's
good,
that's
the
first
one,
the
other
one
was
the
next
10
years
for
collaborators.
So
we've
got
two
sort
of
two
things:
we
we
we
could
dive
into
the
key
technical
areas,
the
brainstorm
or
talk
start
to
talk
about
the
next
10
years
for
collaborators
and
since
you're.
Here
mary.
Maybe
maybe
we
want
to
spend
some
time
and
at
least
talk
about
the
next
10
years
for
collaborators
and
what
next
steps
might
be
and
what
we
should
at
least
get
us
thinking
about
it.
Does
that
make
sense.
A
A
F
I
don't
have
anything
in
mind
right
now.
If
you
can
start,
I
might
have
some
ideas
later.
B
I
I
can
just
read
a
little
bit
from
your
original
comment:
mary.
You
said
our
discussing
and
reevaluating
our
current
contribution,
workflow
consensus,
seeking
model
leadership,
model,
etc.
B
We
might
come
up
with
ideas
for
improvements,
important
topic
to
discuss.
There
are
some,
you
know,
ideas.
I
guess.
A
C
F
The
like
a
lot
of
this
is
just
the
barrier
to
start
contributing
to
node.js.
Today
is
really
high.
F
F
And,
besides
that,
the
consensus
sticky
model
that
we
use
today,
which
is
lazy
consensus,
it's
been
brought
up
a
few
times
that.
F
Privileging
folks
that
are
very
active
and
very
prone
to
blocking
stuff
versus
folks
that
are
more
reserved
or
have
less
time.
F
F
So
yeah
everything
connects
like
together,
but
the
general
idea
is
making
it
easier
for
newcomers
to
contribute
to
the
project
and
make
it
more
bearable
for
existing
contributors
to
contribute
to
the
project
without
cutting
people
burning
out
so
frequently
because
of
the
process
which
I've
seen
happen.
A
few
times
already.
A
Because
that
might
give
us
some,
you
know
you,
you
mentioned
a
few
like
the
the
consensus
model
like
is
this
the
one
we
need
for
the
next
10
years
or
not
the
you
know,
onboarding
new
collaborators,
you
know
making
that
easy,
but
there's
probably
a
there's,
probably
other
things
in
there,
so
get
actually
having
the
list
and
capturing.
It
would
probably
be
a
good
starting
point.
A
A
What
do
we
think
the
the
good
things
are
and-
and
you
know
in
terms
of
the
collaboration
cycle.
E
A
Grouping
yeah,
there's
sort
of
because
there's
kind
of
like
obstacles
what's
what's
working,
what's
not
working
and
then
there's
like
the
core
like
the
different
concerns
like
the
consensus
model,
like
the
the
you
know,
collaborator
like
they
know
how
long
builds
take
or
those
those
I'm
not
sure
always
will
come
out
an
obstacle.
So
I
don't
know
if
that's
like
another
useful
column
for
like
key
key
areas.
A
E
Yeah
so
the
the
last
link
I
shared
for
the
last
board,
I've
I've
updated.
So
it
has
the
key
focus,
areas,
obstacles,
barriers
and
then
an
area
for
working
well
is
that
right.
F
B
This
is
in
issue
45
the
meeting
issue
or
you
want
to.
Oh
sorry,
you
want
it
in
the
actual
issue.
A
A
E
E
E
G
F
C
H
A
A
A
E
A
E
A
G
A
B
A
E
B
B
C
A
Is
that
about
talking
about
like
the
initiatives
that
that
are
undergoing,
like
the
large
changes,
that
kind
of
stuff,
or
something
different.
E
F
But
I
think
both
both
these
are
direct
negatives.
We
have
on
utsc
and
then
some
working
groups,
and
as
well
as
communicating
in
progress
work
via
social
media
accounts.
B
F
C
I
F
Oops,
I
think
that's
different,
there's
a
difference
between
a
pr
not
getting
revealed
and
it's
getting
actively
blocked
by
someone.
F
F
A
F
I
Yeah,
I
added
that
one
I
think
it
I
agree
kind
of
does
fit
with
consensus
that
that's
something
that
kind
of
comes
up.
Sometimes
that
will
block
a
pr
and
like
sort
of
lead
to
that
lack
of
consensus
like
why.
Why
is
this
being
added
to
core.
E
I
A
Yeah,
just
looking
at
the
other
one,
I
think
the
working
groups
seem
to
be
working
well,
release
cadence
and
the
code.
E
E
A
E
A
A
I
I
A
How
many
votes
do
we
get
10,
10,
okay,
so.
E
And
I
think
it's
at
the
individual
level,
like
on
each
person's
own
screen,
that
you
can
actually
sort
change
the
sort
yep.
A
A
A
So
I
guess
at
this
point:
maybe
we
don't
really
have
time
to
dive
into
these,
but
we
can
capture
it
and
come
get.
You
know
start
with
this
next
time.
I
guess
next
time
we
should
probably
take
a
quick
look
at
and
discuss
the
next
steps
on
the
technology
brainstorm.
We
were
doing
actually
the
there
see
that
that
one
you
put
in
you,
you
created
another
fun,
retro
right.
E
Yeah
I
linked
to
other
boards
that
we've
gone
through
before
and
chat
which
I
can
also
link
in
the
issue.
If
you
want
me
to
share
them
there
as
well
again.
A
I
think
it
was
just
like
I
was
thinking
on
the
technical
brainstorm.
We
thought
it
would
be
good
to.
You
know,
get
something
where
other
people
could
participate,
and
I
wonder
if
between.
If
we,
you
know,
it
would
make
sense
to
just
to
create
a
new
board
just
like
the
one
that
we
did
the
brainstorm,
but
actually
posted
in
an
issue
in
the
node.js
repo
discussion,
like
as
a
discussion.
A
Yeah,
basically
clone
it
and
then
open
a
discussion
that
says
hey
in
the
next
10.
We
were,
you
know,
trying
to
brainstorm
the
the
technical
directions
and
trends
that
are
important,
hey
collaborator,
I
think
like
just
doing
it
with
the
in
a
collaborator
discussion,
would
be
a
great
way
to
see
what
kind
of
on
a
slightly
wider
circle
we
we
hopefully
will
end
up
seeing.
E
I
can
I
can
look
at
doing
that
here
and
right
after
the
call.
A
Perfect
thanks
and
then
I
think
otherwise
we're
out
of
time.
So
when
we
come
back
next
time,
we
can
sort
of
see
what
we've
got
from
that
and
look
at
the
priorities.
We
have
there
and
figure
out
what
the
next
steps
might
be.