►
From YouTube: Node.js Technical Steering Committee meeting
Description
A
A
She's,
not
here
oh
I'll,
read
through
it
says,
there's
three
open
issues
asking
permission
to
move
to
repose
into
the
foundation:
everybody
on
the
TSC
NCC.
Please
do
quick
quotes
on
github.
So
basically
that's
a
reminder
from
Francisca
to
go
check
those
issues
and-
and
you
know,
give
you
a
+1
or
not,
so
we
can
move
them
forward.
Some
of
them
have
been
hanging
out
a
while.
A
So
that's
that's
great
that
she
went
ahead
and
did
that
the
other
announcement
I'll
throw
in
is
that
it's
the
last
week
to
nominate
people
for
the
TSC
chair
and
directors.
So
if
you're
thinking
about
doing
that,
just
make
sure
you
don't
miss
the
cutoff
I
think
it's
around
the
end
of
this
week,
any
other
announcements
that
people
have
yeah.
B
A
B
C
A
A
A
A
A
That's
the
tight
tracking
issue
for
run
time.
Declaration
of
buffer
constructor
I,
don't
know
again.
If
anybody
has
any
specific
issues
to
discuss
this
week
on
that
front,
I
know
I've
seen
some
some
work.
You
know
a
short
blog
post,
but
I
don't
know
anything
other
nut.
Does
anybody
else
have
anything
to
add.
A
A
D
D
A
We
will
just
opening
this
up
quickly
on
the
Nappy
front,
while
I
do
that
we're
still
working
on
the
back
for
port
for
8x
I
believe
last
time,
I
checked
just
needed
a
good
CI
to
get
it
landed,
maybe
a
few
more
reviews,
and
otherwise
you
know
we're
working
on
issues
that
have
been
opened
in
the
the
repo
some
activity.
In
terms
of
you
know
what
potentially
adding
some
new
API
is
and
stuff
like
that,
but
nothing
really
to
call
out
so
going
down
the
list
for
the
people
we
have
so
modules.
D
B
D
In
a
yes
and
mode
right
now,
we're
identifying
all
potential
features
and
the
module
system
may
have
and
then
from
that,
that
list
of
all
features
will
be
airing
it
down
to
the
features
of,
or
at
the
very
least,
the
implementation
that
will
be
made.
A
proposal
viable
model
working
group
module
team
for
what
what
changes
need
to
be
made.
D
Can
I
chime
in
really
quickly,
my
god,
absolutely
on
HD
on
the
HTTP
to
front?
If
there's
anyone
in
this
meeting
who
has
patient
8
point
X
is
about
70
commits
behind
master
and
it's
walking
everything
ending
I
took
a
stab
at
it
that
getting
things
going
and
got
some
one
flicks
resolved,
but
it
seemed
like
there's
some
simple
table
issues
or
there's
some
issues
with,
like
certain
sequence,
features
not
being
available.
I
I
got
to
the
point
where
I
wasn't
really
confident
in
being
able
to
move
it
forward.
D
C
D
A
Okay
on
the
open,
SSL
evolution,
we
don't
have
raw
today,
but
you
know
I
think
they're
on
track,
we're
on
track
before
the
proposal
that
he'd
sent
out
earlier.
In
terms
of
you
know,
we
went
out
with
1.0,
1.1,
0
and
being
on
track
to
being
able
to
upgrade
to
1.1.1
moving
forward
workers.
I,
don't
know
if
there's
anything
new
on
that
front.
A
C
Not
really
it's
not
from
me,
it
might
be
worth
mentioning
that
some
of
the
other
people
who
are
like
generally
invested
in
getting
workers
apartment
note
seem
to
be
working
on
more
of
their
own
stuff,
but
like
we're
still
having
the
same
issue
that
we
had
before
and
again
it's
like
locked
on
me
or
somebody
else,
finding
time
to
debug
it
and
I
mean
thank
you
for
like
trying
to
reach
out
to
people.
I
know
you
did
that
yeah
yeah.
A
Okay,
so
is
but
yeah
so
I
think
that's
that's.
The
thing
to
call
out
is
there
is
a.
There
is
a
PR
which
is
important
to
that
effort
and
it's
it's
blocked
on.
You
know
getting
issues
on
the
windows
resolves,
so
really.
Our
next
step
is
to
try
and
find
somebody
to
help
out
on
that
front.
So
as
you're
walking
on
Windows
trying
to
trying
to
get
people,
it
helped
okay.
So
if
you
know
Windows
and
are
interested
in
moving
the
workers
stuff
forward,
that's
a
good
place
to
jump
in
error
messages.
Joey.
A
B
A
A
A
Okay,
so
it
was
a
question,
says,
sits
from
bench,
mirror,
says:
I'd,
love
clarifications.
What's
the
current
relationship
between
noches
and
standard
bodies,
as
well
as
an
understand,
as
well
as
understanding,
what's
the
correct
way
to
pursue
changes,
we'd
like
in
what
WG
specs
so
I
guess?
What's
our
that
what
WG
policy
I
can.
D
Speak
to
that
man,
the
the
what
Lake
is
an
open
group
middle
meeting
and
everything
as
far
as
I
know,
there
is
nothing
stopping
us
from
participating
aside
from
showing
up
and
participating
any
individual
who
wants
to
participate
in
the
working
trip.
As
far
as
I
know,
we'd
always
be
able
to
show
up
to
their
repos
and
to
participate
in
the
discussion
and
try
to
submit
changes.
It
is
a
bias
towards
serving
browser
vendors
after
what
week,
but
that
is
part
of
their
charter.
D
And
there's
in
I
want
to
just
emphasize
that
if
people
want
to
get
involved,
they
totally
should
shouldn't
feel
blocked
or
needing
to
wait,
no
project
to
do
anything
and
if
you
want
to
go
and
represent
what
you
think,
support
these
cases
or
note
that
totally
makes
sense.
Although
I
think
that
if
you
want
to
be
going
and
explicitly
representing
note
itself,
which
would
probably
be
more
explicit
about
that,
since
we've
also
been
engaging
one
tc39
I
do
think
that
this
actually
makes
sense
for
us.
Have
them
were
listed
initiative
around.
C
A
D
Think
I
think
the
next
action
would
would
be
spitting
up
some
sort
of
initiative
or
at
least
getting
a
pulse
if
people
are
interested
in
getting
together
and
I
can
take
that
anyone
else
interested
in
that
I
know
we
have
James's
shut
up.
James
I'm,
promoting
you
and
James
may
have
some
insight
and
thoughts
into
this
as
well.
Hi
James.