►
From YouTube: Node.js Technical Steering Committee meeting
Description
B
A
So,
let's
just
get
started
with
the
issues
from
the
issue
tracker.
The
first
issue
that
we
have
is
issued
to
zero.
Eight
two,
eight
nominating
John
David
JD
Elton
s,
collaborator,
congratulations,
John,
David!
Thanks
for
joining
us,
we
are
hoping
to
see
more
pour
request
from
you
and
then
the
next
issue
is
two
zero.
Three
one.
Six
documentation
update
the
notable
changes
in
ten
dot,
X
Rubin
added
that
to
the
TAC
label.
A
C
So
I
covered
it
in
the
in
the
issue.
Just
basically
I'd
prefer
not
to
be
changing
those
after
the
fact,
unless
they
are
obviously
incorrect,
but
after
talking
about
it
with
Ruben
and
Laura
folks
remember,
but
as
long
as
the
changes
are
also
made
to
the
to
the
release
branch
and
to
the
the
website,
post
blog
posts
and
keeping
those
name
in
sync,
then,
okay,
nine
points.
A
A
E
E
A
E
At
a
previous
meeting,
where
Nikita
wasn't
I
volunteered
to
to
help
push
that
forward,
to
take
what
Nikita
Rowe
work
with
Nikita
or
just
take
the
ball
and
run
whatever
and
just
kind
of
try
to
get
something
together
that
we
can
put
together
and
I
proceeded
to
do
nothing
with
it.
So
this
so
so.
This
is
all
this
is
also
on
me
to
actually
do
something.
Okay,.
A
A
A
A
E
B
E
E
D
E
D
B
A
A
C
E
C
A
Let's
skip
that.
If
miles
is
not
here,
Michael
anything
for
an
API
on
the.
F
F
B
Yeah
this
so
I've
still
got
a
pending
item
to
get
the
docs
done,
but
the
other
thing
is:
if
s
still
one-one-one
been
pushed
out
the
release
date.
I,
don't
know
the
context
there.
I
suspect
it
was
simply
that
all
the
complexity
with
TLS
1.3
needed
more
baking
time,
so
they
haven't.
If
they've
removed,
they
proposed
release
date.
Last
date
they
have
his
19th
of
June
for
b-26,
so
hopefully
June
early
July
we'll
see
how
my
blesses
a
one
on
one
cross
fingers
and
then
we
can
get
this
landed
before
no
ten
LTS.
F
F
C
It's
an
excellent
pour
request.
Definitely
we're
going
to
look,
but
it
does.
We
did
that
one
there's
another
issue
camera
what
it
was.
We
have
a
couple
issues
right
now
that
are
there
that
are
highlighting
the
fact
that
we
need
to
resolve
the
namespace
her
core
modules
issue.
We
don't
need
to
have
that
discussion
right
now.
I
just
want
to
you
know
mention
it
just
shows
on
everybody's
mind,
is.
C
C
What
I've
seen
that's
been
progressing
rather
nicely
I
mean
there's
still,
there's
still
some
to
do
and
some
improvements
to
be
made,
but
no
no
blocker
is
enough,
but
no
also
no
significant
news.
Okay,.
C
Just
letting
the
FS
promises
stuff
continue
to
bake
we're
yeah
there's
been
efforts
to
improve
test
coverage
there,
which
has
been
fantastic
to
see
I'm
holding
off
on
pushing
hard
on
many
of
the
other
core
api's
to
promise
apply
those
until
and
we
are
relatively
certain
that
the
FS
promises
are
going
to
work
as
expected,
and
we're
gonna
see
the
adoption
of
those,
so
that's
kind
of
where
it's
at
right.
Now.
Okay,.
C
G
But
I
can
probably
speak,
there's
no
much
much
improvement
there.
The
only
thing
that's
been
talked
about
recently
has
been
some
discussion
of
the
activity
area
of
I
think
the
support
for
us
Inc
iterators.
So
there
is
a
tracking
issue
somewhere
that
they
can
link
that
Beverly
in
the
last
few
meetings.
So
it
was
actually
kind
of
a
mouthful
but
I
never
reported
this.
So
ok
bye
bad.
So
if
you
are.
G
A
G
I
can
speak
about
that
because
there
was
a
massive
bug
of
facing
cooks.
So
basically
not
the
note,
if
you,
if
you
don't
know
the
know,
Teller
lead
is
a
nutribullet
production
if
you
are
relying
on
any
APM
integration.
So
basically
that's
that's
the
hard
truth.
So
I
did
the
back
part.
So
there
was,
the
bug
was
fixed
in
in
v8
tip
of
tree.
Whatever
it
is,
I
did
the
backdoor
commit
to
six
point
seven
and
it
has
been
landed
on
the
pull
request
that
taargus
has
opened.
G
B
G
I
think
so
Benedict
did
a
fantastic
optimization
of
a
sync
await
and
these
fantastic
optimization
of
a
sink.
Oh
wait,
I
think
optimized,
the
one
of
the
promises
of
a
sink
await
away.
Really,
however,
that
completely
masked
mess
with
us
in
cooks.
So
it
broke
completely
plumbing
jokes,
because
we
didn't
ask
for
a
sink
await.
We
test
only
for
promises
and
for
primarily
there
was
no
problem
whatsoever.
G
B
G
G
A
G
There
was
a
nice
discussion
about
this
somewhere
about
the
fact
that
the
Aston
Kooks
texts
were
written
before
we
had
a
sink
await
in
v8.
So
whenever
we
introduced
a
new
feature,
should
we
add
unit
tests?
This
is
a
question
mark
like.
Should
we
revisit
what
we
have
on
v8
ships?
The
language
is
a
new
feature,
should
we
add
new,
can
add
new
unit
tests
to
pull
the
PI's
to
see
if
they
still
work
with
the
new
concepts.
This
is
a
question
for
the
TSA
that
being
backed
up.
That's
not
the
time
of
the
discussion.
A
A
B
E
You
because
it's
about,
if
we
can
enable
cloaking
basically
in
the
channel
and
I,
think
I
think
having
people
who
are
actively
managing
IRC,
because
very
few
people
in
CC
do
to
answer
that
question
would
probably
be
best.
So
it
would
be
great
if
Jeremiah
were
here,
but
unfortunately
he
can't
make
it
and
we're
great
for
miles
were
here,
but
unfortunately,
and
maybe
before
go
ahead.
James
sorry.
A
The
person
I'm
sorry
I,
can't
I'm
gonna
butcher
your
name,
but
the
YouTube
question
is
also.
Is
that
a
particular
comment
on
an
issue
do?
Do
you
want
those
to
be
answered
by
the
TAC?
It
sounds
like
this
is
really
more
the
calm,
calm
space
I
mean
we
can
look
at
it,
but
I
think
TAC
would
be
much
more
helpful.
There
hi
Jenny.
B
A
Could
talk
to
people
in
the
badges
team
I'm,
not
sure
who
is
in
the
badges
TMO
what
that
is?
Okay,
perfect
yeah,
so
they
will
talk
to
calm,
calm
and
I'm
sure
you
can
resolve
this
thanks
for
listening.
Anybody
else
have
anything
before
we
finish
the
public
part
and
thanks
for
listening
and
the
question
check
out
the
node.js
foundation
calendar
for
upcoming
meetings,
and
we
have
another
TC
meeting
next
week.
Bye,
bye.