►
From YouTube: Node.js Technical Steering Committee meeting 2019-02-20
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).
B
Thanks,
okay,
so
we're
following
the
standard
agenda
as
in
the
issue
that
was
open
for
the
meeting.
The
first
thing
is
announcements.
I'll
start
off
by
mentioning
that
Jewish
pruna
cell
has
been
mint,
has
been
nominated
as
TSC
member.
So
following
our
process
he's
going
to
attend
a
few
of
the
meetings
so
welcome
to
reach
to
your
first
meeting.
D
D
135
on
the
nodejs
summit,
repo
and
it
will
be
on
the
30th
and
31st
of
May,
and
it
is
issue
so
book.
Your
travel,
that's
an
announcement.
Okay!
Is
it
whereabouts?
Is
it?
Is
it
close
to
the
Jay
scarf
you
venue
or
you
are
asking
a
question
I
catch?
If
you
didn't
check
distance?
Okay,
we
are
still
in
the
process
of
trying
to
see.
If
there
is,
we
can
provide
some
discounts
for
hotel,
okay,.
B
D
B
D
A
D
A
A
A
Is
it
time
for
another
announcement?
I
would
say
yes,
I
would
like
to
make
an
announcement
we
recently
and
recently
being
yesterday
launched
nodejs
death.
That
was
a
six
week
sprint
to
get
it
up
the
door.
It
was
based
on
the
content
from
the
no
GS
website
redesign
group,
the
content
they
had
been
working
on
for
kind
of
like
new,
getting
started
and
learning
content,
but
that
content
was
unfortunately
not
really
out
for
the
world
to
enjoy,
because
you
know
there
was
a
lot
of
other
things
that
the
website
needs
to
do.
A
Jf
scott
dev
and
nodejs
dev
will
take
you
to
that
site
and
we
also
have
github.com
slash
nodejs,
slash,
nodejs
dot
death,
and
that
is
the
repo
it's
a
Gatsby
application,
we're
deploying
it
auto
like
pushes
to
master-
and
you
know,
there's
all
sorts
of
different
ways
that
people
could
come
in
and
get
started
and
help
I
think
that
there's
already
11
or
12
different
people
who
had
committed
just
since
we
kicked
the
project
off
so
you
know,
come
help.
Try
it
out
test
it
out.
Let
us
know
we
can
improve.
B
A
So
we
have
been
working
actively
since
we
announced
the
intent
to
merge
in
October
on
putting
together.
You
know
with
what
the
structure
and
governance
of
a
new
foundation
could
look
like.
A
number
of
people
from
the
project
have
been
actively
involved
in
in
this
process,
I'd
like
to
give
specific
shoutouts
to
Matteo
Kalina
and
Michael
Dawson,
who
have
been
actively
involved
in
the
meetings
and
have
helped
with
a
lot
of
stuff,
as
well
as
Tracy,
Hines
and
Rory
person.
You
know,
there's
been
a
lot
of
drafting
and
a
lot
of
back-and-forth
we're
at
right.
A
Now
we
just
did
in
a
town
hall
yesterday
that
we
opened
to
the
public
record
and
available
on
YouTube.
We
were
planning
another
Kevin
hall
for
about
two
weeks
from
now,
I
hope
we
have
a
board
meeting
on
Friday
and
I'm
hoping
to
get
an
explicit
date
when
I
have
everyone
in
a
room
where
I
can
get
their
schedules
and
we
can
reach
agreement
and
we'll
let
that
date
out
a
little
bit
sooner.
A
A
really
high-level
overview
of
how
this
looks
is
we've
got
a
we've,
got
a
cross
project
council
that
cross
project
Council
is
chartered
by
the
board
to
oversee
and
run.
You
know
they
need
a
technical
and
governance
of
the
foundation
itself.
The
CPC
in
turn
will
then
charter
the
individual
projects.
Individual
projects
will
have
their
own
governance,
that
governance
will
not
be
overseen
maintained,
controlled
or
dictated
by
either
the
CPC
or
the
board.
A
Although
there
will
be
some
foundation
wide
expectations
and,
depending
on
the
level
of
the
project,
as
we're
going
to
have
a
project
progression,
the
level
of
the
project
may
have
certain
constraints
as
well.
There
is
nothing
in
the
constraints
that
we're
looking
at.
That
would
have
the
nodejs
project
not
be
what
we
are
now
calling
impact
level
projects.
Every
impact
level
project
will
be
able
to
vote
to
members
as
voting
members,
the
cross
project
Council
and
the
clock
project.
Council
will
be
the
final
say
on
matters
such
as
budget
in
join
the
foundation.
A
There's
a
lot
more
I
think
that
you
know
just
saying
words
will
not
really
do
this
justice
there's
a
slide
debt.
There's
there's
diagrams
I
can
do
a
performance
dance
about
it,
but
you
know
the
next
town
hall
in
two
weeks
will
be
a
great
time
to
try
to
find
out
more
about
that,
and
you
know,
as
always,
I'm
available
ping
me
on
Twitter
by
email
or
you
know,
I'll
be
there
in
the
pigeon
or
whatever
works
for
you.
Yeah.
B
I
think
it's
just
good
to
shout
out
now
that
it's
getting
to
the
point
where
you
know
we
think
we
have
a
good
set.
So
if
you
look
at
them
and
say
you
have
concerns
or
additional
input
or
whatever
else,
it's
it's
now
the
time
to
kind
of,
say:
hey,
wait,
a
second
or
here's,
some
other
kind
of
things
to
think
about
or
whatever,
because
other
than
that
people
think
it's
in
a
reasonably
good
shape.
Yeah.
A
There
are
no
outstanding
objections
on
any
of
them,
so
if
you
have
them,
it's
a
time
to
speak
up
and
we're
also
moving
on
a
timeline
where
we're
hoping
March
11th
is
the
open
source
Leadership
Summit,
which
is
the
Linux
Foundation's
annual
event,
where
they
bring
together
boards
and
sponsors
from
a
number
of
different
projects
and
different
foundations,
and
both
the
Jas
Foundation
and
the
NED
Foundation
will
be
there
physically.
So
we're
gonna
have
a
large
number
of
both
of
the
boards.
A
They're
imperfect
so
I
would
really
really
love
if
people
to
speak
up,
because
we
are
on
a
timeline
right
now
of
this
merger
becoming
official
as
soon
as
March
11th.
And
so
it's
really
important
that
people
who
have
objections
have
concerns
are
involved
because
we
still
have
times
to
change
things
and
as
a
caveat
as
we've
seen
with
our
own
projects
and
our
own
things
bylaws
charters,
all
these
things
can
be
changed
through
standard
motions
and
in
fact,
one
of
the
things
that
will
be
really
interesting.
A
Rich
I
think
you'll
like
this,
in
particular
I,
believe
and
in
practice,
we'll
see
how
this
works
and
the
new
structure
projects
are
chartered
by
the
CPC,
not
by
the
board.
So
changes
to
the
nodejs
Charter
would
no
longer
require
board
rupal.
They
would
just
require
CPC
approval,
which
should
make
it
way
easier
for
us
to
manage
things,
because
the
CPC
will
be
chartered
by
the
board
to
manage
charters.
B
E
B
F
D
I
bought
that
it's
not
really
it's
not
really
dissolved
in
the
sense
that
it
was
not
a
disk,
an
open
discussion.
It
was
I
thought
I
put
it
on
the
agenda,
mainly
for
for
a
cup
of
notes.
One
is
for
visibility
and
the
other
one
to
gather
feedback
from
you.
Folks,
mainly
I'd,
been
listening
with
James
and
a
lot
of
other
people
on
how
to
put
to
make
our
event
meter
more
promise
friendly,
especially
when
working
with
testing
frame
testing
a
synchronous,
Tinka
wait
code.
D
If
you
need
to
interact
with
some
events,
it's
really
complicated
to
get
to
write
things
up
in
a
way
that
is,
that
looks
coherent
with
the
sinka
white
pad
pattern.
It
feels
it
feels
natural,
okay
and
I.
Add
like
I
put
together
that
that
we
are
based
on
some
code
that
we
got
clean
during
for
a
year
and
something
on
on
several
open
source
projects,
so
open
source
and
private
project.
D
So
I
just
wanted
to
track
what
you
think
folks
and
please
review,
and
if
you
haven't,
if
you
have
concerned,
I'm
planning
to
get
that
landed
as
soon
as
possible.
But
I
just
wanted
to
reiterate,
have
your
feedback
and
ask
your
opinion,
because
you
know
this
is
a
new
API
and
they're
doing
some
little,
not
strong
objection,
not
enough
to
block
it,
but
to
these
does
not
belong
in
core,
while
I
think
it
fits
in
our
promise
based
improve
support
for
promises
education.
So
that's
it.
G
F
F
D
Yes,
it's
more
to
gain
visibility.
If
you
think
this
is
a
good
pattern
or
not,
if
you
want
to
reiterate
before
adding
it
to
the
to
the
runtime,
it
hasn't
necessarily
approval
to
run
to
land
I
am
more
concerned
of.
Is
this
the
right
call
and
it's
more
about
API
design
really,
rather
than
you
know,
other
things
so
I
think
it
could
be
useful
for
simplifying
some
tasks
that
are
dealing
with
sink,
await
and
stuff
like
that.
So.
F
D
D
B
B
D
F
Was
the
one
I
had
added
the
TSC
agenda
label
like
two
and
a
half
weeks
ago?
I
think
and
it
just
never
got
removed.
It
seems
like
where
that's
at
right
now
is
I'm.
A
totally
had
an
objection,
matéo
I
believe
post
a
solution
and
totally
agrees
that
that
solutions
adopted.
Then
it's
probably
fine
and
we're
at
that
point
right
now
that
about
it.
As
far
as
everybody
knows,
particularly
on
the
told
E
and
Matteo
I'm.
F
Cool
so
I
removed
the
TSC
agenda
label,
but
it's
basically
blocked
until
Brian
M
SC
DX
either
makes
those
changes
or
comments
that
he
doesn't.
Why
didn't
mean?
Why
might
not
want
to
make
those
changes,
I
suppose
if
it
really
gets
stalled
and
if
it's
something
we
really
want,
someone
can
just
go
ahead
and
okay.
E
B
A
Meeting
on
Friday,
when
you
just
quickly
pop
something
up
here
and
take
a
peek,
so
we
have,
as
you
know,
the
project
board
that
I
do
that
I
used
to
keep
track
of
all
the
things
that
are
important
to
build.
Oh
I,
just
sent
it
to
someone
privately
I
didn't
mean
to
boom.
There's
the
link.
You
can
see
the
link
in
there.
A
You
can
see
that
we're
working
with
the
legal
Subcommittee
on
how
we
should
address
licenses
for
non
code
initiatives,
I
believe
that
we're
gonna
have
an
answer
for
you
very
soon.
You
know
in
the
order
of
like
one
to
two
weeks.
We
also
have
something
on
here
about
the
travel
fund
for
the
collaborator
summit.
B
A
A
So
modules
we
had
a
meeting
just
before
this
one
you're
kind
of
opening
to
reach
consensus
on
a
few
things,
but
it
turns
out
it's
contentious
and
hard,
so
we
are
right
now
trying
to
meet
a
deadline
of
getting
our
new
implementation
up
streamed
before
nodejs
12.
There
are
two
major
points
of
contention
that
we
need
to
determine
before
we
can.
You
know
like
actually
have
something
that
we
could
present
to
the
project
because
I
mean
first
off.
A
If
this
is
a
group,
that's
looking
to
be
charter,
but
so
we're
trying
to
the
two
big
contentious
bits
are
still
transparent,
Interop
and
file.
Extension
resolution
I
think
there's
a
bit
of
a
debate
between
what
we
should
be
doing
by
default,
and
you
know
like
what
of
how
permissive
to
be
with
behavior,
as
well
as
how
we're
able
to
how
we're
able
to
handle
god,
my
brains,
done
from
all
the
meetings
today.
B
Okay,
next
one
is
any
PI,
so
I
think
you
know,
there's
continued
work
to
help
on
the
adoption
front,
their
husband,
son
Brooke,
good
progress
on
the
modules
that
were
called
out
in
one
of
the
node
core
issues
as
being
problems
for
12.
Before
some
of
the
authors
have
made
an
API
versions,
we've
helped
contribute
some
an
API
versions
of
those.
Otherwise
you
know
there's
a
continued
focus
on.
You
know,
handling
the
issues
that
are
opened
and
dealing
with
the
PRS
that
are
landing
I,
don't
think
gabriel.
F
G
There
is
a
this
is
not
directly
on
the
topic,
but
it's
related
there's
a
security
release
coming
out
next
week,
but
I
think
mrs.
L.
It's
it's
not
for
one
one
zero,
but
it's
for
1
0,
2,
&,
1,
1
1.
So
it's
only
gonna
impact
notes:
6
&
8,
the
security,
the
security
fixes
included,
might
moderate
and
which
is
higher
than
some
we've
done
in
the
past
for
releases,
so
I
would
say
we
need
to
prep
for
security
releases
next
week.
I
haven't
brunei
issue
up,
you
don't
get
hurt,
but
I'll
do
that
today.
G
G
B
Think
you
know,
as
far
as
I
know,
he's
making
good
progress
on
getting
TLS
1,
3,
working
and
I
think
he's
fairly
optimistic
that
we
can
get
like
TLS,
1
3
on
by
default
412
and
back
ported
to
10,
but
not
necessarily
enabled
like
enabled
under
a
flag,
because
there
are
some
things
that
that
change.
When
you
turn
that
on.
H
F
D
A
I'd,
be
okay
with
that
at
this
point
seems
like
something
that
we've
moved
past
and
list
I
guess,
like
the
only
thing
that
I
that
I
would
then
we
think
is
going
to
be
worth
leaving.
That,
therefore,
is
that,
once
the
merge
officially
happens,
there's
likely
changes
we'll
have
to
make.
There
are
definitely
changes
that
we
need
to
make
to
our
Charter
and
possibly
to
like
some
of
the
internal
things
in
the
way
that
we
work
with
stuff.
So.
A
You
know
to
consider
it
all.
This
is
like,
as
it
is
right
now.
Nodejs
has
that
board
seat
in
the
new
structure,
the
CPC
has
a
board
seat
and
then
there's
a
floating
board
seat
that
can
be,
you
know,
assigned
on
an
annual
basis
by
the
CPC
as
it
sees
fit,
which
the
intention
right
now
is
that
that
would
go
to
the
node.js
project
in
the
first
year.
B
C
G
B
A
A
So
this
is,
you
know,
a
major
change
to
our
ecosystem,
where
we'll
be
possible
in
theory
to
NPM,
install
modules
and
then
import
them
in
the
browser
without
requiring
a
build
step,
it
will
just
require
metadata
that
could
be
generated
by
the
package
manager,
some
other
open
standards,
we'll
look
at
the
WIC
G.
Also
that's
a
w3c
working
group
also
has
some
work
going
on
around
a
new
file
system.
Api,
it's
capabilities-based.
It
might
be
something
that's
worth
us
taking
a
look
at
and
potentially
participating
in
they're.
A
Looking
at
spinning
up
a
group
around
quick
as
well
I
know
that
we
have
some
people
beginning
to
implement
quick,
so
that
would
be
probably
a
good
idea
to
get
involved
in
that
process.
Early
on
tc39
happened,
you
know
about
you
know
like
25
days
ago.
I
was
there,
as
was
a
couple
other
people
from
the
foundation,
what
we
tried
to
bring
dynamic
modules,
change
for
the
module
group
that
was
not
successful.
A
A
bunch
of
us
are
still
doing
work
on
the
top
level
of
wait
proposal,
which
is
actually
getting
some
traction
right
now
and
is
looking
like
it
might
be
in
the
timeline
of
something
that
could
happen
this
year,
other
than
that
there
aren't
major
major
proposals
that
would
affect
us
too
much
aside
from
perhaps
decorators,
which
is
fairly
contentious.
So
that's
something
that
you
know
people
may
want
to
look
into
outside
of
that.
F
B
Cothran,
okay
I
know:
there's
lots
of
activity
on
that
front,
though
so
that's
good.
Okay.
So
that's
the
are
updates
on
their
strategic
initiatives
at
this
point.
Unless
there's
any
other
issues
that
people
want
to
raise
or
discuss,
we
should
move
on
to
the
Q&A
from
YouTube
and
if
there
are
any
questions.