►
From YouTube: Node.js Technical Steering Committee meeting 2019-03-27
Description
A
Yeah,
it
looks
like
we
are
streaming:
welcome
everybody
to
the
node.js
foundation,
technical
steering
committee
meeting
for
March
27th
2019,
as
we
always
do.
We
start
with
announcements
and
there
are
a
bunch
queued
up
that
I'm
just
going
to
read
through
and
then
people
can
add
anything
that
I
missed.
A
So
first
announcement
is
that
no
just
twelve
is
coming
and
people
have
breaking
changes
they
want
to
land,
they
should
get
those
landed
on
master
very
soon.
The
released
working
group
has
determined
that
there
will
be
a
cutoff
for
breaking
changes
into
just
twelve
soon.
I
think
it's
at
the
beginning
of
April
sometime
I
can't
find
the
date.
Oh,
no,
it's
March
23rd
it
already
passed,
nevermind,
so
yeah.
So
any
breaking
changes
that
need
to
land
in
node.js
twelve
will
now
require
TSC
approval.
A
So
there
you
go.
Let's
see
what
and
Noches
twelve
should
be
out
at
the
end
of
April.
Also
there
the
fee,
no
jest
collaborators
or
actually
I.
Guess
it's
the
open,
Jas
now
collaborate
or
summit
I
suppose
I
mean
a
mint.
The
collaborator
summit
is
going
to
be
at
the
end
of
May
in
Berlin
right
before
GS
confi
you,
there
is
a
link
if
you
are
an
OG
s,
foundation
member.
There
is
a
link
in
the
know,
jsr
an
issue
and
an
OG
s
summit
repository
issue,
number
149
check
it
out.
A
Please
come
and
hang
with
us
and
yeah
open,
Jas,
so
I
guess
that's
the
Jazz
foundation
and
the
node.js
foundation
collaborator
summit
Thank
You
Matteo.
Yes,
if
you're
an
open,
Jas
Foundation
member
too,
although
that
gets
a
little
weird
because
I
don't
know
that
all
that's
been
completely
determined
yet,
but
it's
in
progress
and
and
we're
pretty
we're
pretty
we're
pretty
we're
pretty
cool
about
letting
people
attend
so
come
on
down.
Okay,
let's
see
here.
A
Oh
yes,
call
for
sessions.
Thank
you.
Yes,
there
is
a
for
the
for
the
summit.
There
is
a
call
for
sessions,
so
if
there's
something
that
you
think
is
of
interest
to
the
community,
that
is
that
you
would
like
to
lead,
facilitate
conversation
about
please
submit,
and
that's
that's
what
that
issue
number
149
actually
is
that's
not
about
the
summit
in
general.
It's
about
a
call
for
sessions,
Thank
You,
Matteo!
A
A
Yes,
if
somebody
already
added
and
this
yeah,
so
we
already
we,
the
the
first
two
issues
on
the
agenda
are
actually
those
two
issues
that
I
put
in
the
announcements.
Thank
you
to.
Whoever
is
doing
the
notes
right
now.
I
appreciate
it.
I
have
a
really
hard
time.
Talking
and
doing.
The
notes
which
probably
signed
I
should
talk
less.
A
A
I
would
like
to
come
back
to
that
at
the
end,
unless
there
are
objections
and
move
on
to
the
the
checklist
to
address
changes
to
move
to
the
open
jazz
foundation,
which
is
admin
repo
issue
number
three
one,
one
Michael
Dawson
who's,
not
here
I,
indicated
that
he
at
least
wanted
there
to
be
discussion,
TSC
discussion
and
consensus
around
how
we
are
how
how
the
the
top-level
committees,
the
TSC
and
con-com,
should
pick
the
two
representatives
voting
representatives,
I
guess
on
the
on
the
CPP.
Is
that
CPC?
A
Whatever
is
the
cross
project
Council,
that
seems
to
be
going
that
conversation
is
happening.
There
seems
to
be
a
lot
of
support
for
doing
what
we
currently
do
for
for
board
directors,
which
is
one
election
for
each
committee
to
pick
one
member
gireesh
had
an
alternative
proposal,
which
I
think
is
reasonable,
that
the
committee's
vote
you
each
vote
on
vote
as
a
collective
body
rather
than
as
separate
entities.
A
I
did
leave
a
comment
like
in
the
last
half-hour
that
that
does
introduce
certain
complexities
and
decisions
that
need
to
be
made,
and
that's
where
the
conversation
is
at
this
point,
I
kind
of
feel.
If
conversation
is
happening
in
the
issue
tracker,
we
should
keep
it
in
the
issue
tracker,
because
if
we
have
it
here,
then
anybody
who's
not
here,
misses
out
on
context.
A
B
B
That's
fine,
too,
two
main
issues
which
I
see
is
that
that
approach
makes
the
two
themes
that
is
TSC
and
the
kong-kong
looks
too
completely
isolated
teams,
with
probably
it's
disjoint
priorities,
number
one
number
two
when
that
is
implemented,
I
kind
of
get
into
an
awkward
situation
where
you
know
I
am
represented
by
somebody
whose
selection
process
I
was
not
part
of,
or
at
least
I
didn't
have
a
say
on.
These
are
the
two
issues
which
I
can
think
about.
B
A
A
A
Okay,
this
is
gonna,
be
a
quick
meeting
so
before
we
go
back
to
Street
initiatives,
anyone
look
quickly.
The
issue
I
think
some
people
added
a
couple
things
to
the
agenda
in
the
comments
kind
of
last
minute
e,
which
is
fine
to
hear
actually,
they
weren't
last-minute
they're,
just
they're
loud.
They
seem.
A
All
right
so
rod
who's,
not
here,
wanted
us
to
just
wanted
there
to
be
attention
about
two
core
repo
issue:
two
six,
seven
one
four,
which
is
updating
the
supported
platforms
for
node
twelve
says
it's
not
ready
for
merging,
but
its
nearing
it
and
he
wants
there
to
be
awareness
on
the
TSC
about
it.
The
baby,
the
bullet
points
he
left
and
there
were
that
we're
they're
settling
on
GCC
six
there's
been
almost
no
feedback
on
Mac
OS
defaults.
A
You
know
rod
feels
like
we're
going
to
have
to
recommend
having
both
you
know,
supporting
both
out
of
the
gate,
but
with
the
Python
2
end
of
life
coming
this
year.
You
know
we
don't
he
doesn't
want
us
to
lock
ourselves
into
supporting
Python
to
for
another.
You
know
18
months
after
that
or
whatever
so
there
you
go.
That's
that
for
awareness,
unless
somebody
has
comments
that
they
want
to
work
Corrections
or
anything
on
that
topic,.
A
A
Okay,
if
anybody
was
talking,
they
were
on
mute
move
along
here,
let's
see
here
and
alright
so
related
to
to
the
December
major
cutoff
for
no
twelve
we
have
well
had.
Let
me
see
if
we
still
have.
We
have
32,
oh
we're
down
to
30.
We
have
30
open,
pull
requests
that
are
labeled
some
ver
major.
A
It
would
probably
be
a
good
idea
for
TSE
folks
to
get
into
that
list
a
little
bit
and
try
to
close
some
of
those
out
or
land
them
close
things
that
are
never
gonna
land
and
land
things
that
are
landable.
That's
an
awfully
large
number
of
breaking
changes
is
kind
of
looming
out
there.
My
personal
opinion
only
and
let's
see
here
and
last
but
not
least,
miles
wanted
to
add
poor
issue
to
six
I'm.
Sorry,
pull
request
to
674
five,
which
is
it
says,
just
for
a
heads
up
or
heads
up.
A
At
the
very
least:
it's
it's
a
new
es
module
implementation.
So
that's
kind
of
a
big
deal
so
go
take
a
look
at
that.
There's
been
a
ton
of
comments
on
it.
It
looks
like
179
comments
and
the
list
and
19
participants.
So
it's
been
very
active,
that's
great,
but
if
it's
been
off
your
radar
and
that's
something
you
care
about
now,
you
know
about
it.
Please
get
in
there
with
that.
Unless
anybody
has
something
else,
they
want
to
talk
about
or
anything
that
I've
babbled
about
that.
A
A
All
right,
then
sounds
like
it's
time
to
get
into
strategic
initiatives.
Modules
miles
is
not
here
and
API.
Michael
Dawson's,
not
here,
OpenSSL
rods,
not
here,
workers
Anna's,
not
here
errors.
Joey
is
not
here.
Core
promise.
Api's
James
is
the
champion
of
he's
not
on
to
guess
he
right
now.
So
we
might
want
to
do
something
about
that
governance
miles
is
not
here.
Oh
good,.
A
Can't
hear
you
Matteo,
oh
okay,
Mateo
wants
to
take
the
prop
missus
API
cool.
Is
there
anything
to
report
today,
Mateo
yeah?
No,
today
I
was
on
a
train,
but
he's
typing
in
the
chat.
So
hunk
I
will
read
anything.
He
types,
okay,
nothing
to
report,
but
we
should
probably
update
the
strategic
initiatives
document
Jeremiah
anything
to
report
on.
C
D
Basically,
thread-safe
function
has
now
landed
in
version
8
as
well.
So
as
soon
as
six
drops
off
the
radar,
we
can
confidently
say
that
an
API
version,
4
is
now
in
all
supported.
Lts
versions
of
node
is
a
and
it's
not
likely
to
make
it
back
to
6
I
mean
not
not
only
because
it's
ember
minor,
but
also
because
it's
it's
lacking
some
major
infrastructure
for
that.
So
so
it's
gonna
be
like
I
said
this.
D
A
A
E
A
A
All
right
thanks,
everybody
see
you
next
time.