►
Description
A
B
Think
it
is
worth
announcing
that
the
call
for
papers
for
node,
plus
Jas,
interactive,
2019
and
sunny
Montreal
is
open
and
awaiting
your
papers,
submit
them
on
the
website.
I
don't
have
the
link
right
now,
but
it's
on
my
Twitter
somewhere,
probably
buried
between
like
110
the
last
day
because
I've
been
busy.
C
A
No
okay:
let's
move
on
to
the
things
tagged
agenda,
so
the
first
one,
twenty
seventy
two,
four
six.
It
actually
was
on
the
agenda
to
make
sure
we've
got
enough
TCO
approvals.
It
does
in
fact
have
two
TSE
approvals,
so
unless
anybody
has
something
that
they'd
like
to
talk
about
I
think
we
can
move
on
to
the
next
one.
A
Nope,
okay,
so
then,
let's
move
on
to
the
next
one
that
is
26
for
one
eight.
This
is
refactor
the
buffer
benchmarks.
It's
a
PR
related
to
removing
a
number
of
benchmarks
to
try
and
shorten
the
run
time.
It
does
look
like
there
was
a
call
for
a
vote
in
the
issue
and
that
was
seconded
I
guess.
The
assessment
was
that
we
we
weren't
going
to
reach
consensus
and
that
everything
we
needed
to
do
to
try
and
reach
consensus
had
been
exhausted.
So
it's
I,
guess
rich.
C
A
A
Okay,
so
moving
on
then
to
the
next
issue,
which
is
doc
update
to
the
TSN
charter.
So
this
is
issue
number
698
I
just
put
this
on
the
agenda
because
it
does
affect
our
governance
and
thought
that
make
sure
everybody
is
aware.
So
please
take
a
look
if
you
have
any
objections.
Otherwise
you
know
I'm
asking
that
Myles
add
that
to
his
list
of
things
that
he
brings
to
the
board,
because
I
I
guess
I'm
a
little
uncertain,
but
probably
this
charter
change
needs
to
be
made
by
the
board.
A
B
Had
a
meeting
next
Friday
yeah
I
guess
this
is
exactly
related
to
just
the
board
meetings,
but
I'll
take
this
moment.
I
guess
we'd
get
this
in
the
open
governance,
but
the
CPC
is
now
officially
formed.
So
one
thing
that
we
will
want
to
look
into
now
and
I
guess
another
thing
to
add.
This
is
an
interesting
a
bit
from
the
board
perspective.
B
Certain
representatives,
as
left,
Google
and
I,
will
be
taking
on
Google's
corporate
seat.
Is
the
plan
right
now
and
so
we're
in
the
midst
of
transitioning
that
and
figuring
out
exactly
how
that
works
and-
and
you
know
doing
that
in
the
meantime,
by
the
current
governance
was
to
complete
the
node.js
project
is
still
eligible
for
a
board
member
as
a
community
representative
that
has
one
for
the
entire
project.
So
it's
not
one
tsc1
Kham
Kham,
which
we've
had
in
the
past,
so
it
likely
would
be
one
representative
from
both
top
level
committees.
B
The
CPC
has
not
kicked
off
any
of
that
election
stuff
yet,
but
I
would
like
to
encourage
us
in
like
maybe
we
could
start
an
issue
in
the
enrico
is
never
too
early
to
start.
Having
these
discussions
and
like
now
that
the
CPC
is
bootstrapped
and
as
far
as
I'm
concerned
chartered
by
the
board
they're
in
a
position
to
approve
of
whoever
that
new
board
member
is
so
I
think
it
is
a
good
time
for
us
to
kick
that
off
as
far
as
I'm
concerned
and
Michael,
you
can
chime
in
if
I'm
off.
B
A
B
A
Agree,
I
was
just
waiting
until
the
CPC
got
to
the
point
where
it
could
sort
of
approve
I.
Think
it's
kind
of
like
the
CPC
might
have
a
final.
You
know
they
might
have
the
ability
now
to
say.
Okay,
let's
confirm
our
governance
or
not
as
long
as
nothing
changes
there.
Then
you
know
exactly
what
you
said
is
the
case
that
for
the
first
year
we
have
a
board
representative,
so
I
agree.
We
should
open
an
issue.
Do
you
want
to
do
that
or
do
you
want
me
to
go
ahead
and
do
that.
B
A
B
I'm
on
it
all
right,
yeah
one
thing:
one
thing
that
would
really
help
me
for
everyone:
when
we
take
things
like
a
charter
change
to
the
board,
it's
important
that
we
have
consensus
on
it
before
the
board,
even
reviews
it
whose
legal
needs
to
review
as
well.
So,
if
folks
could
take
climb
week
to
review
it,
put
in
comments
sign
off
on
it,
we
should
have
all
the
playoffs
on
these
charter
changes
by
the
end
of
the
week.
B
We
likely
want
to
ping
that
to
the
CPC
as
well
as
a
heads
up
about
what
we're
doing,
and
then
we
get
it
on
the
agenda
for
the
board
that
needs
to
get
reviewed.
We
go
so
what
I
think
makes
the
most
sense
for,
as
many
told
us
as
we
can
this
week,
I'll
kick
off
the
process
of
getting
it
put
on
the
board,
humble
and
then
in
next.
When
did
one
big
meeting
and
I
guess
we
have
nine
people
or
do
we
have
how
many
members
are
on
the
TSC
know,
I'd.
A
B
But
it's
more
I
have
seen
in
the
past
that
if
there
isn't
clear
consensus
that
it
will
get
sent
back
from
the
board
sure
how
so
for
me,
when
I
bring
it
to
the
board
I,
just
very
much
like
it
being
in
a
position
where
we
have
lots
of
clear
sign
off
and
that
we've
had
a
meeting
with
quorum
where
we've
agreed
to
it.
Yeah.
D
B
A
A
B
Move
in
create
require
I
think
we
mentioned
this
in
the
last
meeting
landed
in
12.2.
That
was
a
big
movement
there's.
A
couple
of
like
many
of
your
contentious
issues
are
the
big
ones
working
right
now
one
is
file
extension
resolution
and
whether
or
not
the
node
resolution
algorithm
should
be
on
by
default.
The
other
is
whether
or
not
we
should
allow
for
dual
mode
modules
with
a
single
specifier.
So
should
you
be
able
to
like
import
low
and
require
low
and
have
it
work
but
resolve
to
different
files?
B
B
This
is
one
of
the
things
I'm
more
excited
about,
so
it's
the
idea
of
creating
a
new
field
in
the
package.json
called
exports,
which
would
allow
you
to
explicitly
state
all
of
like
the
deep
modules
that
exists
and
he
actually
locked
down
the
module.
So
you
couldn't
just
go
in
and
grab
arbitrary
files.
B
This
is
controversial,
to
say
the
least,
but
those
are
kind
of
the
major
topics
that
we're
debating
right
now,
other
than
that
something
that's
not
so
controversial,
but
just
requires
engineering
effort
is
like
the
new
version
of
the
custom
loader
API.
The
current
version
has
some
like
we
don't
like
the
API
design
of
the
current
version.
There
is
a
new
version
that's
being
made,
but
it
has
memory
leaks
and
it's
kind
of
slow.
C
C
A
B
Tc39
meeting
is
coming
up
just
after
blends,
like
in
Berlin
talk
to
you.
If
there
are
folks
who
are
interested
in
attending,
you
know
it
is
possible
to
come
as
an
invited
expert,
although
you
know
in
general,
because
of
the
proximity
and
how
many
people
may
be
coming
if
you're
interested
in
coming
as
an
invited,
expert
I
would
like
to
work
with
that
individual
to
make
sure
that
a
there
isn't
a
conflict
due
to
the
organization
that
they
represent
and
be.
You
know
that
they
have
some
sort
of
reason
for
being
there.
B
Aside
from
like
it's
just
cool
to
be
in
the
room,
I'm
happy
to
work
with
people
and
help
them
figure
out
how
to
get
there
if
it's
something
that
they
want
to
be
doing,
I'm
excited
exist
in
it.
Top-Level
await
is
coming
along
and
there's
a
potential
that
we
might
be
trying
to
go
for
stage.
That's
really
cool
other
than
that.
B
Daniel
Ehrenburg
little
Dan
on
github
and
I
have
been
talking
quite
a
bit
about
how
to
how
to
best
engage
with
our
community
and
so
like
help.
People
be
successful
and
get
their
feedback
heard.
But,
like
you
know,
setting
people
up
for
success
in
setting
good
expectations,
it's
definitely
something
we
want
to
ramp
up.
But
now
that
we're
a
broader
foundation,
we
have
more
stakeholders
so
like
in
general.
You
know
if
people
are
interested
in
working
on
more
thing
in
the
standards
world,
I'd
love
to
hear
what
you
want
to
work
on.
A
D
D
It's
eventually
going
to
be,
you
know,
evolve
into
HP
3
as
well,
but
the
idea
is
to
implement
the
basic
quick
protocol.
+
HP,
3,
coming
along
nicely
should
have
I
should
have
a
nonstick
faulty
version
within
next
week
or
two
and
I
plan
on
showing
it
at
the
collaborator
7
4.
Who
wants
to
see
it,
and
just
so
folks
know
you
know,
for
full
disclosure,
both
near
formant,
with
the
lab
sponsoring
my
time
to
work
on
it.
D
C
A
Ok
and
napi
work
continues
on
some
of
the
key
issues,
so
around
async
worker
we
have
worked
through
some
of
the
issues
just
need
to
start
implementing
the
ideas
we've
come
up
with
to
address
them,
as
well
as
some
evangelists
they'll
work
on
Evangelos
Evangelos
and
putting
together
workshops
and
so
ok.
So
that
is
our
strategic
initiatives
with
you
so
back
to
the
agenda
that
takes
us
to
the
end
of
the
agenda
there,
any
other
things
people
want
to
talk
about
before
we
close
the
public
session.