►
From YouTube: 2022-04-06-de.js Technical Steering Committee meeting
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
In
the
issue
that
was
in
issue
number
1203
before
we
get
started,
does
anybody
have
any
announcements
that
they'd
like
to
share
planning.
B
Is
good,
I
we've
released
node.js
12
2212
yesterday,
and
that
is
the
last.
The
release
group
is
not
planning
anymore
any
further
node.js
12
releases,
so
node.js
12
will
go
end
of
life
at
the
end
of
this
month,
end
of
april
2022,
after
which
it
will
receive
no
further
updates.
B
So
the
only
scenario
we
envisage
where
there
will
be
a
further
node.js
12
releases
if
there
were
any
sort
of
security
vulnerabilities
between
now
and
the
end
of
april
that
we
deem
we
would
want
to
put
a
release
out
for,
but
otherwise
that's
it.
No
12vs
no
12
could
be
considered
sort
of
almost
done.
You
know
pending
spending
the
end
of
the
month,
assuming
nothing
else
comes
up.
So
if
you
are
still
running
applications
on
node,
12
and
you're
watching
the
stream,
we
can
only
register
it
again.
B
C
Yeah
so
waleed
ashraf
asked
us
to
announce
that
planning
for
the
open
gs,
world
collaboration
summit
in
june
is
happening.
I
believe
it
is
to
be
a
hybrid
event
where
some
people
will
be
on
site
in
austin,
texas
and
other
people
will
be
other
people,
probably
most
people,
I'm
guessing,
but
I
don't
know
we'll
be
attending
remotely
and
we
need
to
sort
of
get
the
word
out
to
all
team.
C
All
those
sort
of
note
teams
and
working
groups
and
everything
else
and
people
basically
submit
their
session
proposals
and
we
need
to
create
an
agenda
for
the
sessions
and
while
he
has
asked,
if
you
know,
basically
wants
to
tag
at
node.js
members-
and
I
put
a
comment
in
the
tsc
issue-
that
I
think
he
should
do
that,
and
so,
if
anybody
has
concerns,
because
you
know
sometimes
people
don't
like
when
you
tag
a
team
that
has
600
members.
C
But
in
this
particular
case
I
think
it's
appropriate
and
and
any
other
comments
or
things
you
want
to
follow
along
in
its
tsc
repo
issue.
1204.
A
Thanks
and
yeah-
and
we
hope
we
have
as
many
people
attending
the
collaborator
summit,
and
I
think
that
we
submitted
issues
through
the
same
way
in
in
in
the
the
summit
repo
in
the
past
and
work
quite
well.
So
yeah,
please,
everybody
submit
your
start
submitting
your
sessions,
any
other
announcements
before
we
move
on
to
the
issues
tagged
for
the
agenda.
A
If
not
cpc
updates
rich,
do
you
have
any
cpc
updates.
C
No,
there
was
a
this
was
a
working
session
week
and
the
working
session
was
canceled.
A
Okay,
let's
move
on
then
to
the
issues
tagged
for
the
agenda.
The
first
one
is
nominate,
rafael,
silva,
four,
two
five,
seven,
I
think
that's
part
of
our
standard
procedure.
I
don't
know.
A
It
says
number
42462
just
opening
that
if
whoever
added
it
is
here
feel
free
to
jump
in,
but
I
think
this
one
was
added
by
james
and
I
think
yeah.
D
C
The
next
one
is
collins:
the
node
module
node
prefix
for.
A
E
Pick
that
one
up
yeah,
so
we
we
talked
about
this
one
last
week.
My
action
item
from
last
week
was
to
send
a
summary
email
to
the
tsc.
I
did
that
there
hasn't
been
a
lot
of
activity
on
the
email
we
kind
of
proposed
coming
up
with
a
a
resolution
in
a
week.
So
here
we
are
so
yeah.
I
don't
really
have
anything
else
to
add,
except
people
need
to
weigh
in
on
it.
C
C
C
Okay
and
colin
in
your
email,
I
think
that
you
pretty
much
laid
out
what
the
what
the,
what
the
broad
options
are
right.
There
were
like
three
of
them.
I
think.
E
So
I
mean
there's
like
the
extreme
case
we
could
revert
and
then
there's
you
know
various
different
ways.
We
could
go
as
far
as
like
not
supporting
just
the
scope
and
and
basically
supporting
it.
So
yeah
there's,
you
know
basically
two
or
three
high
level
options.
Do
we
want.
A
C
A
E
C
A
E
So
there's
you
know,
there's
a
pull
request,
that's
open
as
well
as
a
branch
to
handle
one
of
the
other
cases.
So
as
long
as
we
don't
introduce
a
bunch
of
different
cases
with
the
vote,
then
I
mean
it'll
be
tight
because
we
need
the
reviews
and
ci
and
stuff,
but
it
could
be
doable
so
beth.
C
Just
put
in
the
chat
that
code
freeze
is
planned
for
the
12th
of
april,
which
would
be
a
week
from
yesterday
well
depending
on
what
time
zone
you're
in
but
approximately
a
week
from
yesterday
and
so
yeah.
So
we
probably
want
to
get
moving
on
this
real,
quick.
A
C
A
C
Day
vote
yeah:
let's,
let's
plan
on
ending
about
no
no
no
later
than
monday,
and
then
you
know
we
can
rush
something
in
after,
but
I
mean
it
is
an
experimental
api.
So
you
know,
hopefully
you
know
if
we,
if
you
know
we
can,
we
can
make
changes.
D
A
A
G
So
that
means
two
versions
more
recent
than
the
stable
v8
and
this
version
will
not
be
stable
by
the
time
we
release
v18.
G
So
I
I
guess
the
first
question
I'd
like
to
ask
here
is:
are
we
okay
with
releasing
node
18
with
a
v8
version?
That's
not
considered
stable.
C
G
I
am
asking
that
because
to
me
the
the
only
the
only
two
other
alternatives.
One
of
them
is
stop
supporting
windows,
32-bit
windows
versions,
because
I
have
no
idea
how
to
fix
that.
I
I
have
I
don't
or-
or
someone
finds
the
time
to
to
find
which
commit
in
v8
fixed
it.
I
don't
know
if,
if
they
fixed
it
by
a
chance
or
if
they
knew
it
was
broken
and
there's
a
commit
that
clearly
fixes
it.
G
I
don't
know
so
that
would
be
an
option
to
yeah
to
stop
supporting,
maybe
temporarily,
we
could
do
that.
Maybe
not
build
32-bit
versions
of
off
node
until
it's
fixed.
G
G
No
sorry,
I
yeah,
I
think
it
only
affects
32-bit,
there's
a
there's
a.
We
are
not
even
sure
if
it's,
if
it's
a
problem
in
v8
or
in
or
in
visual
studio,
it's
just
that
it
crashes
while
building
it.
G
A
A
I
don't
know,
I
think
the
you
know
the
suggestion
that
we
don't
ship
it
initially
but
plan
to
add
it
back
is,
is
a
reasonable
option
in
terms
of
like
it,
doesn't
we
don't
have
to
ship
a
version
which
is
no?
You
know
if
people
are
using
current
we're,
not
shipping,
something
that
isn't
even
beta
yet
and
it's
a
short-term
impact
to
32-bit
users,
and
you
know
well,
I
don't
see
that
as
being
it
seems,
it
seems
like
risk
management
wise
for
us.
That
seems
like
a
good
choice.
A
D
F
I'm
using
it
when
I'm
developing
and
never
see
it's
a
neat
crash,
but.
A
I
guess
the
two,
the
the
the
risk
of
of
dropping
dropping
it
temporarily,
is
that
when
you
bring
it
back,
maybe
there
were
issues
you
know,
there'll
be
problems
added
that
weren't
caught
by
the
ci
in
the
meantime.
A
So
that's
the
sort
of
negative
I
think
beyond
just
not
being
available
and
then
on
the
other
side,
it's
the
using
something
that
hasn't
been
if
it's
alpha
or
whatever
in
our
current.
B
Well,
we
could,
we
could
always
have
the
beta
alpha
on
on
main
the
question's
more
about
going
out
and
releases,
I'm
not
totally
opposed
to
having
you
know
something
on
on
on
on
the
main
branch
of
node,
that's
potentially
unstable.
I
prefer
it
to
be
stable,
but
you
know
if
that
gives
us
the
the
build
coverage.
B
If
that's
the
only
way
we
can
build
in
32
windows,
then
you
know
the
option
is
there
to
have
to
have
what's
coming
in
the
pr
on
master,
but
I,
unless,
unless
comfortable
with
shipping,
that
in
in
the
actual
node
18
release.
A
G
Yeah,
when
are
we
going
to
release
node
18.
G
B
A
So
I
think
the
current
proposal
we're
discussing
is
like
okay,
we'll
go
out
in
node
18
with
10.1,
without
32-bit
support,
we'll
pull
in
the
current
one,
that's
on
canary
into
maine,
and
so
that
we
still
get
the
testing
coverage.
G
I
don't
know,
but
I
will
try
to
make
forward
compatibility
patches
if,
if
it's
possible.
J
G
The
problem:
well,
I
cannot
do
that
right
now,
because
the
10.2
is
not.
The
branch
is
not
cut
yet
it
will
be
cut
right
in
in
a
few
weeks
like
you
know,
you
know
in
one
week
so
yeah
I
will
have
to
wait
for
that.
G
A
Okay,
any
other
discussion
we
should
have
on
that
before
we
move
on.
A
If
not,
okay,
I
will
move
on.
We
only
have
six
minutes
so,
but
I,
I
think,
actually
we'll
be
able
to
get
through
the
rest
of
them,
depending
on
how
long
some
of
them
are
so
the
next
one
is
four
one:
two
six
three
refactor
headers
timeout
and
request
timeout
logic,
four,
one,
two,
six
three,
I'm
not
sure
who
added
that
to
the
agenda.
C
J
C
A
C
The
new
meeting
times,
I
think,
there's
some
offenses
for
the
three
meeting
rotation
and
we
should
go
ahead
and
implement
it.
Okay,.
A
Have
james
on
the
next
10
mini
summit,
it's
tomorrow,
so
just
hoping
everybody.
We
have
a
good
representation
there.
C
I
probably
can't
make
it,
but
can
you
or
someone
else
make
sure
to
you
know,
get
word
out
to
people
about
the
the
openjs
world
summit
collaborative
summit.
A
Let
people
know
so
yeah.
Definitely
we're
planning
another
deep
dive
there.
So
we'll
definitely
mention
that.
A
Okay-
and
that
takes
us
to
the
left
of
things
that
we're
tagged
for
the
agenda.
So
at
this
point
I
think
we
can
drop
close
out
the
public
session
unless
there's
anything
else
that
people
want
us
or
want
to
put
on
the
agenda
first
to
discuss
before
we
do
that.
C
We
usually
do
these
strategic
initiatives,
but
I
think
I
think
we
can
skip
that
this
week,
yeah
exactly
that's
something
from
their
strategic
initiative
that
they
want
people
to
know
about
now.
Now's
the
time.