►
Description
A
B
I'm
very
happy
to
to
say
that
we
have
time
we
have
an
agenda
for
the
collaborator
summit,
so
I
published
this
last
Saturday
morning,
European
time,
so
you
might
have
not
seen
the
notification
or
anything
there
is.
The
agenda
is
published,
so
I
want
to
remember
that
the
collaborator
summit
will
be
in
Vancouver
after
they
after
no
js'
interactive,
and
it
will
start
on
October
12th
at
1:00
p.m.
and
we
have
alpha
day
from
1
p.m.
to
5
p.m.
on
12.
And
then
we
update
you,
starting
from
9
a.m.
to
5
p.m.
B
B
B
If
you
need
there
are
still
some
slots
free.
So
if
your
team
working
group
whatever
needs
a
space,
please
post
it
in
the
issue.
First
is
write,
something
in
the
issue
and
maybe
open
up
an
issue
on
your
own
repo,
so
that
I
would
like
to
link
I
will
link
it
from
the
agenda,
the
main
agenda.
So
you
can
have
your
own
agenda
readings
to
join,
remotely
and
stuff
like
yeah.
B
A
A
A
A
Okay,
so
let's
move
on
to
the
next
issues
in
the
agenda
and
the
next
one
is
opt-out
or
opt
in
for
warnings
number
two
to
587
last
week
it
was
on
the
agenda
as
well.
The
request
was
that
we
all
go
out
and
you
know
get
up
to
date
and
comment
in
the
issue
itself.
I
think
rich
had
opened
that
one
so
I
don't
know
rich
if
you're
able
to
talk
and
and
do
that
and
sorry
I
should
have
said
people
before
okay,
so
rich
I
think
is
just
typing
in
the
the
minutes.
A
A
You
know
as
a
coal
as
opposed
to
saying.
Well,
we
always
work
to
do
opt
in
or
opt
out.
He
rich
is
also
saying:
that's
nobody's
disagreed
in
the
issue
that
was
basically
Richie
and
myself
had
both
chimed
in
with
that
opinion,
so
yeah
I
think
I'd
favor,
closing
it
as
well.
Unless
anybody
else
has
other
ideas
or
objections.
A
A
I
guess
I,
don't
hear
any
objections
to
closing
so
I
think
we
can
move
forward
on
that,
as
always,
if
you
disagree
or
want
to
to
have
it
reopened,
just
jump
into
the
issue
itself.
The
next
issue
on
the
agenda
is
how
to
do
feature.
Detection
number
two
to
five.
Eighty
five
and
there's
also
the
related
issue
to
two
to
one.
Eight
last
time,
rich
should
actually
volunteer
to
try
and
round
up
input.
So
rich.
Do
you
have
an
update
on
that
case?.
A
A
C
A
Mean
I
think
in
general
there
doesn't
seem
to
be
consensus
that
either
of
them
should
actually
move
forward
now,
411
or
or
or
it
all
necessarily
so
I
guess
it's
the
can.
One
of
the
concerns
is
since
11
is
coming
up.
If
we
did
want
to
do
something,
we'd
have
to
do
it
quickly.
I!
Don't
see
that
there's
enough
consensus
there,
but
if
you,
if
it's
something
you
want
to
push
forward,
it'd
be
a
time
to
jump
in
and
try
and
move
things
forward.
D
A
B
A
A
A
Okay,
so
yeah
well
cut
that's
a
good
idea,
we'll
go
through
the
Gendo
and
then
we
can
come
back
to
that
at
the
end.
The
next
issue
is
on
the
agenda:
snowed
TSC,
so
there's
a
track.
The
tracking
issue
for
updating,
TC
on
board
meetings
and
I
know
miles
joined
along
the
way
so
miles.
Do
you
have
an
update
for
us
on
that
front?
Yeah.
E
E
E
So
we
we
did
have
some
marketing
updates
and
communication
updates.
I
think
the
the
biggest
stuff
that
we
can
talk
about
was
for
no
jeaious,
interactive
or
registrations
are
currently
as
of
last
week
at
637
people,
which
was
40%
higher
than
this
long
time,
the
previous
year,
with
472
of
them
being
first-time
attendees.
E
We
had
some
statistics
statistics
over
the
registration
types
in
past
years,
as
well
as
like
the
talk
so
there's
55
breakout
sessions,
39%
are
no
js'
was
specific.
30%
JSF,
specific
and
31%
is
general
and
community
topics
and
there's
still
work
ongoing
with
the
come.
Come
it's
a
program,
content
for
a
community
corner
I'm
the
other
thing
that
was
brought
up
was
that
there
is
a
t-shirt
design
contest.
E
I
can
put
the
link
in
the
chat
and
there
was
a
very
scientific
Twitter
poll.
It
appears
that,
to
my
dismay,
the
first
option
was
the
one
to
win
and
there's
a
medium
article
I'm
going
through.
You
know
the
different
t-shirt
options
that
there
were
in
the
designs.
So
that's
just
to
talk
about
from
this
one
I
believe
the
next
board
meeting
is
going
to
be
running
in
conjunction
with
node
plus
chance
Interactive,
so
I'll
have
more
updates
after
the
next
one.
You.
F
A
E
So
the
two
biggest
things
going
on
on
the
modules
front
right
now.
The
first
is
a
developer
survey
that
we're
currently
designing.
We
have
two
different
tracks
for
it:
we're
going
through
and
testing
it
and
have
a
first
pass
at
the
content.
I
think
the
hope
is
to
be
able
to
present
it
at
interactive,
potentially
during
the
collaborator
collaborator
summit
or
during
the
code
and
learn
to
get
a
pretty
as
large
of
a
sample
size
as
possible
of
you
know,
developers
to
care
about
this.
E
We're
gonna
do
some
patching
on
ES
modules
itself
and
try
to
come
up
with
what
we're
defining
right
now
as
a
minimal
kernel,
a
small
subset
of
features
that
do
not
preclude
any
of
the
different
features
that
we're
talking
about
from
that
I
think
we've
actually
identified
some
ploy
requests
that
we
can
send
back
against
court,
but
I'll
have
an
update
soon,
as
we
reach
consensus
on
what
that
looks.
Like.
A
On
the
napi
front,
nothing
to
news
still
focusing
on
the
same
testing
for
no
doubt
on
API
the
the
npm
module
we've
different.
We've
got
a
issue
that
lists
the
gaps,
also
working
on
getting
code
coverage
and
then
we'll
be
working
on
filling
those
out
and
continuing
with
Angela's
ation
and
a
focus
on
async
worker
there's
been
there's.
Some
issues
reported
against
that.
What's
there
already
on
that
front,
so
working
on
that
as
well,
OpenSSL
evolution,
rod.
G
G
You
can
see
that
he's
the
notes,
we're
tracking
this
in
issue
number
one:
eight,
seven,
seven
zero
we're
discussing
what
you
know
what
is
to
be
done,
there's
one
failing
test
that
Chiaki
has
identified
as
possibly
a
problem
with
open
SSL,
there's
a
breaking
change
in
the
way
and
they
do
some
callbacks
and
because
of
the
way
we
use
the
vio
interface.
It's
having
some
problems
with
that,
but
I
would
expect
that
to
be
ironed
out,
pre
sitting
and
I.
Think
shakey
will
push
forward
on
supporting
the
other
platforms
and
hopefully
get
this
landed.
G
There
is
a
catch
with
TLS
1.3
sure
he
thinks
that
it
would
always
read
his
quote
here.
Supporting
TLS
1.3
in
node
is
another
story.
It
needs
much
more
work
and
would
have
breaking
up
plates
because
of
changes
of
info
callbacks
and
its
TLS
state
machine
and
deprecated
slash
new
circle
features
40
less
1.3.
You
know
this
is
a
1
1
1.
So
basically
tell
us
what
1.3
is
significantly
different
enough,
that
it
might
cause
some
pain
for
us.
G
So,
unfortunately,
unless
with
unless
excluding
with
some
creative
solutions,
we
may
be
punting
on
1.3
support
until
node
11,
but
getting
1
1
1
into
no
tennis,
the
critical
bit
to
start
with.
So
we'll
get
updates
on
that
as
this
evolves,
but
yeah
so
issue
number
one
one,
eight
seven,
seven
zero
chickie
has
a
working
branch
that
he's
referenced
in
there.
Anyone
wants
to
try
just
poking
around
with
it.
For
now
and
that's
it.
G
A
E
G
Nope
not
for
me,
look
I
said
miles.
You
weren't
in
the
last
meeting,
but
I
said
that
I
think
I'm
gonna,
remove
myself
from
sharing
governance.
I
think
it
was
possibly
a
mistake
to
expand
my
responsibilities.
I
probably
should
be
shrinking
my
responsibilities
at
this
stage
because
I'm
having
trouble
keeping
up
so
and
I
know
it's.
You
probably
don't
want
this
just
completely
lumped
on
you,
but
I
just
don't
think
I'm
in
the
best
position
for
it
right
now.
B
H
H
G
E
A
A
A
So
we
need
to
ramp
up
a
number
of
people
who
can
help
out
on
that
front.
So
it
sounds
like
you
got
the
next.
The
next
action
in
hand
I
I
mean
having
said
that
Ben's
been
away.
I
did
see
him
comment
on
at
least
one
issue
yesterday,
so
he
may
have
some
time,
but
we'll
I
wouldn't
count
on
it
necessarily
anything
else
on
fiat
currency.
E
A
H
E
A
E
Yes,
so
we've
spun
up
the
repo
a
handful
of
people
have
been
nominated
and
added
to
the
team,
we're
currently
in
the
process
of
having
some
conversations
about
the
particular
standards.
Just
as
aside
Michael
Franzese
has
their
hand
raised
and
the
attendees
so
we're
having
conversations
the
specific
ones
that
are
happening
right
now.
E
F
F
F
F
Yes,
yes,
yes,
it's
open
to
all
collaborators
who
are
doing
I'm
and
then
just
a
reminder
again
that
we
actually
do
have
for
the
code
and
learn.
We
have
we're
capping
in
at
Babu.
We
have
about
300
people
who
are
going
to
be
attending,
so
everybody
who
is
attending
the
conference.
Please
do
remember
to
come
as
a
mentor
on
that
Friday
yeah.
Well,
we're
capping
at
a
300,
so
I
think
it's
at
2,
250
or
somewhere
around
there.
Yes,
it's
a
lot!