►
Description
B
B
I'm
unsure,
if
we're
gonna,
do
any
more
miners.
It
was
you
know
like
we
ended
up
only
doing
the
assembler
minor
changes
from
an
API,
because
it
dot
X,
isn't
maintenance
right
now.
I
know
that
we
are
still
in
the
process
of
kind
of
reflecting
long-term
support
for
n
API
and
how
we
want
to
move
forward
with
that.
So
if
you
are
listening
and
have
any
opinions
around
LTS
and
stuff
like
that,
please
chime
in
over
at
github
comm,
slash
nodejs,
slash.
A
This
is
really
just
for
awareness
to
make
sure
that
anybody
who,
from
the
the
TSC
who's
interested
in
either
those
positions,
is
aware
that
the
sort
of
nomination
period
is
open.
It's
closing
on
the
22nd,
which
I
think
is
next
Monday.
If
I
remember
correctly,
and
you
know,
basically,
it's
got
a
schedule.
If
you
have
any
comments,
concerns
or
if
you
wish
to
nominate
yourself,
please
chime
in
there
any
questions
before
we
move
on
from
that.
B
Not
a
question,
but
something
that
I
think
is
worth
stating
when
the
CPC
officially
forms
I
will
no
longer
be
the
you
know,
elected
director,
the
director
seat
will
move
to
be
a
CPC
director,
and
then
we
will,
after
the
CPC
forms,
have
to
elect
a
new
director
or
the
technical
steering
committee.
I
believe
that
we,
you
know,
have
it
in
the
bylaws
that
the
first
year
that
will
be
something
from
the
nodejs
project,
just
want
to
make
it
pretty
explicit
that
you
know
I'm
not
going
to
be
looking
to
run
for
that
role
again.
B
A
Basically,
can
reach
up
to
miles
or
more
and
yeah
at
that
point,
once
it's
set
up,
we
will,
you
know,
have
an
issue
that
that
calls
for
nominees
and
so
forth,
but
I
think
in
advance.
If
you
are
interested
in
talking
to
miles
it's
a
great
idea
to
get
a
feeling
for
what
it
would
be
and
in
the
contents,
okay,
so
then,
moving
on
to
the
next
issue,
which
is
the
tracking
issue
for
an
update
on
TC
board
meetings,
I
guess
miles.
That's
over
to
you.
A
B
So
nothing
major
to
report
right
now,
I
mean
the
majority
of
things
that
are
happening.
Right
now
are
happening
in
the
weekly
CPC
meetings.
As
far
as
where
we're
at
there
we've
primarily
identified
you
know
which
projects
are
going
to
be
impact
level
projects
they're
in
the
process
of
identifying
and
electing
their
CPC
representatives,
we're
doing
some
drafting
around
like
bylaws
and
process
for
new
projects
joining
the
foundation
as
well
as
figuring
out
like
what
are
the
expectations
for
new
projects
as
well
as
current
projects.
B
Outside
of
that
the
board.
Has
you
know
the
meetings
that
we've
had
a
primary
dinner
round?
Reviewing
and
approving
you
know
the
budgets
and
the
things
that
are
required
to
legally
move
the
merger
forward.
We
do
have
another
board
meeting
coming
up
next
week,
so
that
will
be
or
know
two
weeks
from
now
I'm
lost
I
thought
it
was
on
my
calendar
and
I'm,
not
seeing
it
they're
good
I
see
it
now
will
be
next
Friday.
The
26th
is
the
next
board
meeting.
B
A
Right
bring
that
down
in
a
minute
you
might
wanna
I.
Think
I
missed
your
first
point,
so
you
might
want
to
add
that
one
as
well
next
bullets
next
thing
on
the
agenda
is
going
through
the
strategic
initiatives.
I
think
I
might
suggest
that
we
just
flipped
the
order
and
look
at
the
other
issue,
which
is
the
no
GS
security
working
group.
Hacker
ones
managed
services.
Anybody
have
any
objections
to
that.
A
Okay,
if
not,
then
you
know
what
I'd
suggest
this.
Let's
look
at
that
one.
This
was
opened
by
vladimir
and
you
know,
basically
it
the
context.
Is
that
we're
using
hacker
1
for
the
initial
triage
of
our
vulnerabilities,
both
for
core
and
for
the
ecosystem
and
the
I
think
factor.
One
has
a
new
program
they're
offering
a
pilot
program
which
in
which
they
actually
do
more.
A
They
help
out
more
in
terms
of
doing
things
like
triage
and
initial
work,
around
sort
of
keeping
you
up
to
date
and
managing
the
the
vulnerabilities
as
they
come
in,
so
that
might
actually
reduce
some
of
the
load
on
on
our
trousers.
There's
some
discussion
going
on
in
the
issue
itself,
and
you
know
it
seems
like
we're
trending
towards
agreeing
to
to
take
advantage
of
that.
But
I
think
this
is
just
on
the
agenda
too,
for
awareness
and
to
see
if
there
was
any
you
know,
additional
support
or
objections
concerns
over
moving
in
that
direction.
C
Just
that
they
weren't
there
weren't
any
objection.
Meteo
is
in
favor
of
it.
Rod
was
in
favor
of
it
does
not.
It's
not
super
clear
from
the
description
exactly
what
services
we're
going
to
get
but
I
think
we're
all.
You
know
we're
all
we're.
Just
we're
gonna
give
a
shot
we'll
see
if
it
works,
it
doesn't
work.
We
can
go
back
to
what
we
were
doing,
but
if
it
makes
things
easier,
that's
good,
okay,
so
somes.
A
B
New
in
that
front
miles,
so
we
recently
landed
upstream
the
new
implementation
very
exciting
stuff.
We
made
a
slight
change
to
one
of
the
flags.
Recently,
the
flag
that
was
entry
type,
is
no
input
type,
it
no
longer
works
on
arbitrary
files
is
now
just
looks
all,
and
you
know
streaming
content
in
or
running
execution,
really
really
subtle
things
about
the
differences
there.
If
you
have
more
questions,
feel
free
to
ping
me
and
ask
exactly
what's
going
on
other
than
that.
B
One
of
the
you
know,
big
things
that
we
still
need
to
get
done
is
related
to
how
we're
going
to
handle
custom
loaders,
there's
a
new
implementation
that
we're
working
on
that
builds
on
the
worker
threads,
but
it
has
a
slow
startup
and
some
memory
leaks.
So
we
still
have
an
upstream
day
other
than
that
I
think
the
general
intention
of
the
group
is
hoping
to
get
the
new
implementation
stabilized
locked
and
have
the
flag
removed
before
12
goes
into
LTS.
B
You
know
what
we'll
still
need
a
bit
of
time
before.
We
know
whether
or
not
that
goal
in
accomplishable
but
I
think
it's
really
important
for
the
ecosystem.
So
we
get
this
going
for
it
as
quickly
as
possible
and
we're
also
examining
and
trying
to
make
sure
that
it's
something
we
can
back
port
to
10.
A
Okay
on
the
napi
front,
looking
through
you
still
focus
on
sort
of
the
evangelization,
so
we've
got
an
effort
to
put
together
a
workshop
that
we're
hoping
to
submit
to
note
cough
you
as
well
as
nope,
it's
just
interactive.
We
definitely
saw
an
uptick
in
usage
following
the
workshop.
We
did
it
no
coffee
last
year
and
we
figured
that
you
know
we're
at
the
point
where
you
know
doing
those
workshops.
A
So
if
people
have
suggestions
on
you
know
conferences
where
we
might
be
able
to
do
a
workshop
like
that
for
a
good
number
of
users
or
module
developers,
that
would
be
good
because
I
think
you
know
identifying
a
few.
Others
would
be
nice.
Otherwise,
we've
been
spending
some
time
in
our
recent
meetings
as
well
on
acing
worker.
A
There
was
an
issue
open
that
raised
a
number
of
issues
and
we're
working
through
those
issues,
and
you
know
coming
up
with
the
candidate
solutions,
making
some
fairly
good
progress
or
not
so
we're
going
to
be
working
through
on
that
and
then
otherwise.
Just
supporting
you
know,
people
who
are
using
it
as
part
of
the
ramp
up
I
think
we're
up
to
something
around
a
hundred
and
sixty
hundred
and
seventy
thousand
downloads
a
week,
which
is,
you
know,
still
quite
a
bit
smaller
than
that.
A
D
A
C
Okay,
I,
don't
know
big
things,
I
mean
basically,
we've
got
open,
SSL
1.1.1
site
on
master
will
be
involved
at
X
and
it's
down
in
11,
not
X
and
should
be
in
the
next
ten
decks
so
that
coming
that
evolution
is
coming
your
pace
till
this
one,
three
I,
don't
think
it's
gotten.
A
lot
of
use.
It'll
show
up,
I,
guess
it'll
be
in
this
latest
eleven
dot
X
so
be
interesting
to
see.
If
there's
any
reports
from
the
field
like
positively
or
negative
layabout,
it's
an
integration.
C
It
needs
to
be
explicitly
enabled
on
11
decks,
though
so
I,
don't.
You
know
how
many
people
will
see
that
but
it'll
be
default
and
12
that
X
within
a
in
a
couple
weeks
and
then
the
so
that's
the
the
first
kind
of
a
two
steps,
like
the
first
two
stepping
up
says:
OpenSSL
evolution
is
getting
to
1.1.1.
Second,
one
was
getting
to
us
one
three
dots
apart
and
then
the
third
step
is
flips
and
flips,
basically
is
gonna,
involve
a
a
big
refactor
of
OpenSSL
they're
they're
working
away
at
it
a
lot.
B
There's
not
a
ton
to
say
right
now:
I
guess,
like
one
thing
I
could
throw
out.
There
would
be.
You
know
once
the
CPC
stopped
forms
we're
gonna
have
to
do
clean,
govern
engine
kind
of
based
on
the
new
relationships
that
we
have.
But
you
know
after
that
happened.
Perhaps
this
is
a
strategic
initiative
that
we
can
spin
down
for
a
bit.
Does
anyone
object
to
that?
I?
Just
don't
know
that
this
is
something
we'll
be
actively
working
on
after
we
kind
of
you
know,
realign
based
on
the
new
foundations,
governance.
Does
that
seem
reasonable?
B
E
B
D
A
E
A
Unfortunately,
this
one's
not
actually
done,
and
so
I
mean
it's
being
a
strategic
initiative-
may
not
have
gotten
it
over
the
the
the
line
or
gotten
or
not
focused,
but
it's
it's
not
one.
That
needs
less
attention
versus
more
attention.
Unless
we
decided,
we
just
don't
need
it
because
it's
still
sort
of
in
the
in-between
state-
oh
that's
their
experimental.
We
know
lots
of
people
depend
on
it,
but
it's
not
done
and
there's
no
clear
path
to
getting
out
of
experimental,
either
fair
enough.
A
Yeah,
yes,
okay,
I
mean
the
other
thing.
I've
thought
a
bit
about
those.
Do
we
need
we,
probably
it's
probably
as
good
to
have
somebody
on
the
TSC
who
sort
of
helps
with
these
things
so
yeah,
okay,
so
yeah
we
can
get
to
if
somebody
else
doesn't
beat
me
to
it
at
some
point,
I'll
look
at
a
PR
to
move
that
to
that
needs.
Volunteers
needs
help
open
web
standards.
B
I
was
at
the
Ekman
executive
committee
meetings
last
week,
which
was
very
interesting
finding
out
more
about
how
ECMO
itself
works
and
tc39
was
I.
Guess
two
weeks
before
that
I
mean
from
my
own
proposals.
Top
level
of
weight
is
moving
forward
and
it
actually
looks
like
it
may
be
in
a
place
to
go
to
stage
a
meeting,
which
means
that
we
may
even
see
implementations
of
a
different
browsers
and
one
and
in
v8
before
the
end
of
the
year.
B
It's
pretty
exciting
to
me
and
may
those
changes
may
come
in
be
non-trivial
in
node,
but
it
is
completely
isolated
to
the
module
goal,
so
we
wouldn't
by
default,
be
supporting
it
in
commonjs.
That's
something
we'd
have
to
kind
of
look
into
and
figure
out
if
we
want
to
support
separately
from
that
another
thing
that
is
getting
movement
and
has
been
moved
to
stage
2
for
the
June
meeting
is
built-ins
in
built-in
libraries.
The
chrome
team
recently
did
an
organ
trial
for
a
built-in
called
key
value
store.
B
The
new
temporal
library,
which
is
the
replacement
for
the
date
object,
is
also
looking
at
using
built-ins.
Those
teams
are
pushing
towards
a
URL
like
scheme,
rather
than
like
an
@
/
scheme,
which
is
the
way
in
which
any
p.m.
currently
does
namespaces
I'll
keep
people
updated.
As
that
kind
of
moves
forward.
B
The
MJS
ITF
is
moving
forward.
It's
a
slow
process,
but
it's
happening.
One
thing
we're
also
looking
into
is
just
in
the
new
foundation.
What
kind
of
partnerships
can
we
have
the
standards
bodies
and
will
we
be
able
to
have
representatives
from
the
open
source
project
attending
meetings
at
like
w3c
or
tc39,
representing
our
projects
and
figuring
out?
B
G
G
A
G
D
We
have
just
landed
the
patch
from
Rafael
to
Co
cash
embedded
caleche
online
threat,
so
we
you
appear
in
veto,
so
the
co
cash
issue
has
now
been
fixed
module
that
we
still
have
neighbor
it
on
course
compiled
builds,
but
we
will
get
it
and
I've
been
working
on
a
prototype
of
snapshot.
Integration
I
will
be
sending
patches
upstream
from
my
fork,
so
it's
in
progress.
A
D
A
A
E
So
nothing
much
to
report
this
week,
I
will
get
together
a
document.
Brief
document
probably
won't
be
more
than
a
few
sentences,
hopefully
describing
the
problem
and
hangout
solutions
have
been
proposed,
thus
far,
I'll
run
it
by
rod.
I'll
probably
run
it
by
you.
Michael
may
be
run
by
the
rest
of
the
build
team
and
then
go
from
there
and
try
to
figure
out
what
we
can
do
to
make
our
make
our
build
infrastructure
and
personnel
more
robust
than
it's
been.
It
sounds.