►
Description
A
A
B
It
was
fixed
in
Russia
for
of
not
version
four
point,
something
like
only
the
branch
that
is
cutting
Spoony
to
Russia,
but
it
wasn't
fixed
that
no
Jeep
used
so
wasn't
fixed
in
motor
vehicle
branch
and
Jenna
bit
from
version
two
to
worship
or
was
a
severe
measure
for
Najib.
So
to
get
the
date
that
no
target
does
not
have
that
the
duty
one
has
to
install
a
similar
measure
of
the
age
of
non
ship
right
now.
B
B
If
someone
wants
Najib,
they
need
to
get
an
update
to
get
a
fix.
It
will
have
to
happen
on
note
outside
so
no
target.
Santosh
get
police
that
thing
special
value
chain
and
no
dark
sucks
said
that
he's
open
to
accepting
such
requests
for
notre
bateau.
So
if
anyone
is
willing
to
take
a
look
which
notoriously
I
can
in
Kanishka
for
give
me
a
second.
B
B
B
A
Added
to
the
TSE
agenda
was
concern
over
lack
of
progress,
so
I
wonder
if
that's
something
we
should
talk
about
it
all
like.
Is
there
a
concern
that
you
know
we
need
more,
but
I,
don't
know
what
actually
to
you
know
specifically
to
do
about
that,
but
is
it?
Is
it
something
that
we
need
to
put
some
focus
on
in
terms
of
getting
more
people
involved
in
no
Jim,
or
are
we
comfortable
that
you
know
it
only
very
rarely
gonna
need
an
update
and
rods
got
a
handle
on
that
at.
B
A
So
I
think
that
that
makes
sense
it
was
like
it
was
tagged,
the
TSE
agenda,
because
we'd
waited
for
a
long.
You
know
an
update
on
no
chip
itself
for
a
long
time,
for
this
issue,
everything's
dealt
with
question
is
like.
Is
there
anything
else
the
TSE
should
be
thinking
about
in
terms
of
the
other
issue
of
well,
this
is
no
chip
is
a
key
component.
Do
we
have
enough
people
involved
enough
attention
on
it
that
kind
of
stuff
I
don't
know
if
anybody.
E
Think
I
think
rod
addressed
this
in
one
of
the
comments.
I'm
guy
could
take
it
out,
so
I
can
post
anything
sue
is
maintained.
It's
just
it's
very
delicate
to
publish
it.
If
anything
goes
wrong,
it
can
break
a
huge
swath
of
the
ecosystem,
yeah
touchy
with
it
I'm
trying
to
see
how
long
it
took
for
the
issue
to
be
closed.
It
seemed
like
it
was
under
a
couple
which
is
not
unreasonable,
particularly
given
that
this
experience
she
didn't
found.
I
could
actually
yeah
if
it's
only
a
few
weeks,
I.
C
A
B
A
D
Get
dog
water,
okay
go
ahead,
so
basically,
this
was
a
problem
with
the
piping
one.
I
wants
its
sphere
problem
type,
a
PI
B
where
a
and
B
are
child
process
of
parent
node
and
his
output
was
split
between
the
parent,
node
and
B.
That's
what
was
fixed
by
one
eight
zero
one
six,
but
then
it
introduced
in
a
class
of
issue
of
type,
a
plus
B
pipe
in
Lucy
I
wasn't
able
to
get
out
of
that.
D
I
was
not
able
to
find
a
way
out
which
will
fix
both
the
issues
and
the
Opie
was
pressing
forward
because
technically
it's
a
regression,
I
wasn't
convinced
and
because
not
one
was
looming.
That's
when
I
added
there
T
is
he
agenda,
but
Anna
has
come
up
with
a
comprehensive
fixed
which
will
address
both
the
body
class
of
problems
so
actually
remove
the
TSE,
as
in
at
the
moment.
So
it's
more
a
concern.
I
know
you
want
to
add
anything.
On
top
of
that.
G
C
I
mean
to
be
clear:
I
think
that
the
use
case
is
it's
not
technical
level
by
our
streams,
work
slightly
broken
like
I
guess
in
theory,
a
like
a
Mateo
has
one
of
these
things
where
you
can
like
split.
A
stream
kind
of
wood
is
kind
of
like
more
technically
correct,
but
I
don't
know
that
we
should
follow
or
not
specific,
especially
when
we
haven't
been
for
so
long
there's
so
much
code
around
and
since
we
can
fix
it
with
that
date.
Now.
A
A
F
Thank
you
thanks
for
having
me
on
today,
I've
been
working
on
the
night
before,
since
it
actually
came
into
the
Linux
Foundation.
So
we're
making
a
couple
of
changes
this
year
to
Mississippi
review
process,
though
that
we
wanted
to.
G
F
And
try
to
get
more
community
coming
around
one
thing.
We
did
have
a
CFP
review
committee
last
year,
we're
hoping
to
make
it
even
bigger
this
year
and
obviously
we're
broadening
it
to
include
the
JSF
projects
that
are
now
part
of
the
open
Jas
foundation.
But
I
wanted
to
make
sure
that
the
TSC
members
and
the
technical
community
on
knows
that.
F
So
that's
definitely
one
sort
of
opportunity
for
people
to
get
involved
and
there's
I.
Also
in
that
issue
have
posted
sort
of
a
summary
of
the
CFP
review
process
with
with
a
couple
of
the
key
date
so
that
you
have
a
sense
for
when
you
know
the
time
commitment
would
sort
of
peak
and
when
you
would
need
to
be
engaged
in
terms
of
reviewing
and
providing
feedback.
F
Those
two
co-chairs
is,
you
know,
talking
to
several
people
within
the
foundation
as
well
as
within
the
community
and
just
trying
to
get
sort
of
a
two
people
that
we
thought
would
provide
balance
and
reflect
node,
as
well
as
some
of
the
other
projects
and
sort
of
be
up
for
that
role
and
all
that
it
might
entail.
And
so
Tracy
Hines
has
agreed
to
serve
as
one
of
the
co-chairs
and
then
the
other
co-chair,
definitely
with
recommendations
from
a
lot
of
the
jsf
community.
People
as
well
as
Jory
is
Kristian
bromine.
F
Those
two
people
have
volunteered
to
serve
as
the
co-chairs
this
year,
but
again
there's
heavy
input
and
from
the
actual
review
committee.
So
we're
really
hoping
that
it
has
sort
of
community
sort
of
endorsement
and
reflects
community's
interests
along
all
along
the
way.
But
I
don't
know
if
anyone
has
questions
or
suggestions
or
ideas
that
they'd
like
to
share.
A
You
want
to
if
you
want
to
participate.
It's
just
add
your
comment
in
1/48
and
if
you
have
any
questions,
I
guess
you
can
also
post
them.
That
issue
in
terms
of
I
mean
it
sounds
like
you
experienced
last
year.
It
was
you
know.
Basically
there's
a
you
know:
coffee
papers
went
out,
there
was
a
I
think
sirs
already
shared
the
the
text
for
what's
gonna
go
out.
F
A
F
Some
of
the
members
here
might
also
be
on
the
compound
or
involved
at
the
board
level
insert
in
various
positions,
but
there's
been
discussion
to
potentially
change
the
name
of
the
conference
so
once
that
is
determined
once
you
publish
the
actual
CFP
and
then
we're
gonna
put
a
blog
post
together
as
well
that
it's
going
to
talk
about
the
larger
CFP
review
process
and
announcer
of
two
co-chairs
and
sort
of
talk
about.
What's
been
changed
what's
changing
this
year
and
if
people
are
curious
about
the
name
change
discussion.
F
Great
I
think
there
was
some
confusion
that
it
was
a
or
there
was
some
concern
that
it
was
a
her
name,
long
name,
I,
think
not
for
various
reasons.
I
guess
there
had
been
inputted
and
people
did
not
like
the
node
plus.
You
know,
J
s,
interactive
name
that
we
can
see
last
year.
So
there's
been
two
suggestions
that
were
sort
of
crowd
sourced
from
the
calm,
calm
and
the
I
guess
some
of
the
foundation
staff,
as
well
as
the
some
of
the
board
members
and
the
two
options
that
the
board
is
going
to
discuss.
F
The
actual
obedient
board
is
gonna
discuss,
are
this
comp
and
then
also
to
become-
and
these
were
names
that
sort
of
bubbled
to
the
top,
when
the
compound
of
through
put
these
names
out
there
along
with
another,
maybe
three
or
four
other
suggestions
that
were
in
the
mix.
But
those
are
the
two
that
rose
to
the
top
and
when
we
and
when
we
said
new
comp
I
think
it
would
be
new,
confident
each
year
would
be
like
new
comp,
2019
or
new
comp,
2020
etcetera.
C
Yeah
I
mean
I,
guess
the
reason
that
we
pushed
to
still
have
it
I
mean
I,
don't
recall
exactly
how
the
discussions
for
name
on
went
last
year,
but
there
wasn't
really
been
like
I
mean
noted,
proactive
was
kind
of
like
the
the
North
American
conference
for
like
large-scale
node
and
like
the
node
collaboration,
what
was
always
attached
to
it
and
it
already
kind
of
like
lost
that
I
didn't
any
largely
last
year.
Even
if
the
name
changed
back,
a
lot
of
the
talks
were
well.
C
F
H
Ike,
if
I
can
add
to
that
a
little
bit,
I
think
that
Jeremiah
is
on
to
something.
Although
to
be
honest
here,
am
I
I'm,
not
a
hundred
percent
on
board
with
the
Reed
I
think
that
it's
important
that
the
name
reflect
the
content
that
we're
having
to
some
extent
whether
or
not
that's
just
node
centric,
but
as
someone
who
you
know
has
helped
drive
the
sponsorship
over
at
Google
and
getting
a
lot
of
people
on
board,
we
want
to
have
a
lot
of
people
come
to
this
conference.
H
While
something
like
this
comp
is
a
fun
name.
I,
don't
know
how
I
convinced
my
management
to
give
us
$50,000
to
sponsor
this
cough
if
it
was
the
open,
J's
foundation,
this
comp,
like
so
like
I,
think
a
good
comparison
would
be
like
Google
has
a
big
event
called
next
and
Microsoft
has
a
big
event.
I
forget
the
name
of
the
Microsoft.
One
has
like
think
like
there's
a
bunch
of
these
like
one
named
ones
that,
like
without
the
name
of
the
organization,
is
attached
to
it.
H
D
H
I
think
is
much
stronger
and
could
be.
Maybe
it
should
be
global
this,
but
that's
a
whole,
but
I
think
it
would
be
important
and
I
think
that's.
Maybe
the
colonel
Jeremiah
was
getting
at
is
you
need
to
mean
maintain,
in
my
personal
opinion,
some
sort
of?
What
is
what
is
this
all
about
in
there,
because
if
all
that
I
have
when
I'm,
when
I'm
selling
this
to
engineers
and
to
upper
management,
is
the
name
that's
the
first
thing.
They're
gonna
see
that
name
needs
to
say
everything.
Yeah.
A
At
the
very
least,
it
should
say
Jas
at
some
point
into
the
name
right
mm-hm,
you,
the
other
question
I
throw
out
here,
is:
do
we
the
other
people
in
the
call?
Have
you
seen
the
discussion
about
the
name?
Has
it
been
visible
enough
or
is
it
that
we
need
an
issue
somewhere
where
there
can
be
more
discussion,
sounds.
F
Yeah
there
has
been
some
discussion
at
the
comic-con
level
and
then
there's
been.
There
was
actually
board
level
discussion
around
a
possible
name
change
several
months
ago
and
miles
I.
Don't
know
if
you
were
involved
in
that
some
of
those
discussions
I
wasn't
involved
in
all
of
those,
so
I
think
people
have
questioned
if
this
node
plus
G
is
interactive,
should
stick
if
it
worked,
you
know,
but
you.
H
Only
I
have
not
heard
anything
directly
from
the
board,
except
for
a
reaction
to
this
request.
I
believe,
but
I
could
be
mistaken,
that
the
only
place
where
I've
heard
this
coming
from
is
from
the
community
committee.
With
this
request.
At
the
moment
it
doesn't
mean
it's
not
worth
digging
into
and
exploring
all
I
can
dig
into
some
of
the
other
merits
there
separately,
but
I
had
not
heard
this
from
other
groups.
Personally,
okay,.
F
A
Like
if
it
was
discussed
in
the
comic-con
meeting
that
doesn't
necessarily
give
any
visibility
to
the
broader
project
or
the
TSC,
so
I
think
you
know.
Judging
for
my
some
of
the
reactions,
that
would
be
good
to
get
an
actual
issue
open.
That
people
can
comment
in
and
yeah
have
a
more
open
discussion
or
or
maybe
you
know,
I
guess
it's
either
that
where
it's
it's
fully
public
or
or
maybe
an
email
chain
that
includes
both
groups
just
to
make.
F
A
F
F
When
we
can
decide
you
know,
should
this
be
more
open
discussion
and
on
the
mailing
lists
or
in
a
public
issue
and
in
what
level
and
I
know
that
there
is
sort
of
the
the
timeline
factor
and
that
we
are
trying
to
get
the
CFP
published,
and
you
know
somewhat
soon,
not
given
the
events
in
December.
But
these
things
start
early
as
we
know.
H
That
one
thing
that's
worth
throwing
out
there:
we
have
a
board
meeting
coming
up
either
this
week
or
next
week.
That's
an
uncertainty
on
the
exact
date,
but
I
think
that
unless
we
have
like
really
clear
support
about
like
a
what's
the
new
name
and
that'd
be
we
have
like
really
clear
consensus.
It's
already
April
and
we
want
to
do
this
event
and
think
a
couple
months.
H
F
H
D
H
A
H
F
A
A
I
A
A
A
The
nominations
closed
on
the
22nd,
based
on
the
schedule
that
we
had
an
issue
and
agreed
to.
There
were
only
two
people
who
raised
them
raised
their
hand
for
the
positions
myself
and
Matteo,
and
given
that
there's
two
positions
and
two
people
I,
suggested
that
we
simply
move
forward
with
myself
as
chair
and
Matteo
is
the
CPC
representative
and
there
seems
to
be
a
reasonable
amount
of
support.
A
A
A
H
We
have
a
board
meeting
scheduled
for
Friday
on
the
agenda.
Right
now
from
us
is
not
too
much
there's
some
stuff
for
the
CPC,
Charter
and
related
stuff,
but
as
far
as
I
know,
there
is
nothing
explicit
from
the
TSC.
Let
me
just
double
check
our
tracking
board
and
make
sure
that
I'm
not
forgetting
anything
right
now
we
have
nothing
anywhere
on
there
like
I
guess,
one
of
the
only
things
that
needs
to
be
done
is
the
google
Summer
of
the
Google
season
of
Docs
application,
but
that's
more
kind
of
like
general.
H
That's
not
really
a
board
matter,
that's
more
just
like
getting
the
foundation
to
get
stuff
done.
If
anyone
has
anything
specific,
they
think
should
be
raised
to
the
board.
Please
let
me
know
I
guess
one
thing
that
I
could
throw
out
there
right
now
would
be.
You
know,
I
do
plan
to
object
to
delaying
the
the
announcement
of
the
zoo
that
my
brain
stopped
working.
The
announcement
of
the
name
and
this
stuff
around
our
event
is
interactive.
Unless
we
have
a
really
really
clear,
you
know
path
to
launching
something
that
doesn't
require
delaying
it.
H
So
I
don't
know
if
anyone
has
any
concerns
with
that.
Please
let
me
know
if
you
have
concerns
with
that
approach
other
than
that
I
can't
think
of
anything
right
now.
Please
bring
me
if
you
questions
if
the
meeting
gets
delayed,
we'll
be
rescheduled
to
some
point
next
week,
all
so
I
guess
it's
worth
letting
people
know
in
case
you
didn't
see
it.
We
do
have
an
open
call
for
the
executive
director
position.
We
have
a
recruiting
firm
that
we're
working
with
and
we
have
an
open
job
posting
on
the
open,
JSO
org
website.
H
We
I'm
doing
a
follow
up
to
figure
out
how
many
candidates
we
have
right
now
and
I'll,
hopefully
have
more
explicit
like
what
information
I
can
share
with
us
about
how
that
search
is
going
for
the
sake
of
candidates.
Probably
a
lot
of
it
needs
to
remain
fairly
confidential,
but
hopefully
I'll
have
some
meaningful
statistics.
To
give
you
an
example
of
you
know
the
scale
of
applicants,
how
long
we're
expecting
it
to
take
and
stuff
like
that?
Okay,.
A
H
The
high-level
bits
that
we
kind
of
need
to
reach
consensus
on
to
move
this
forward
is,
you
know,
is
our
recommendation
that
upgrading
a
module
from
common
jst,
sms,
Enver
major
or
not
that's
kind
of
a
pretty
major
one?
Do
we
want
to
support
dual
entry?
So
do
we
want
to
make
it
possible
to
both
import
and
require
a
module
and
have
that
potentially
resolve
to
a
different
singleton?
Do
we
want
to
try
to
support
requiring
ESM?
H
This
is
something
that
we
believed
was
not
possible
up
until
now,
due
to
specific
hazards,
but
there
are
some
members
who
think
that
it
might
be
possible
and
whether
or
not
we
want
to
keep
the
extension
resolution,
and
so
for
those
of
you
who
are
not
familiar,
we
dropped
the
default
support
for
the
node.js
file.
Extension
resolution
algorithm
in
our
newest
implementation
right
now
making
it
necessary
to
give
full
file
paths
when
you're
importing
modules.
H
That
is
not
the
case
when
you're
importing
Guerre
specifiers
for
modules
that
you've
installed
by
NPM,
and
we
also
have
some
proposals
that
we're
working
on
to
make
it
possible
to
do
like
specific
exports
from
a
package.
But
there
are
still
questions
about
whether
or
not
we
want
that
to
be.
You
know
what
we
do
moving
forward,
so
you
know
I'll,
keep
you
all
updated
as
things
move
forward.
If
you
have
any
explicit
opinions
about
any
of
the
things
that
I've
just
said
would
be
very
happy
to
hear
from
you.
A
Ok,
so
next
is
an
API
on
that
front.
Still,
you
know
focuses
on
supporting
adoption
and
working
through
some
of
the
issues.
We've
spent
the
last
couple
meetings,
looking
at
some
of
the
issues
that
were
reported
with
a
sink
worker
and
we're
putting
together
a
workshop
that
we
hope
to
get
accepted
it.
You
know
the
the
main
node
conferences.
We
saw
a
pretty
good
bump
from
node
conf
you
last
year,
I
think
those
are
the
main
things
Gabriel.
You
have
anything
else
to
add.
Oh
that.
A
A
A
A
C
A
H
Nothing
much
more
than
what
we've
talked
about
so
far.
I
think
that
there
is
definitely
some
work
that
we
need
to
do
as
a
foundation
as
a
whole,
not
just
as
note
figuring
out
like
what
is
our
relationship
with
ECMO
and
what
is
our
relationship
with
w3c,
the
the
that's
kind
of
blocked
right
now
on
the
forming
of
the
CPC,
but
as
things
kind
of
evolve
there
I'll
keep
people
updated.
Okay,.
H
To
just
chime
in
something
really
quickly,
though
I
don't
know
if
people
saw
that
was,
it
was
I
believe
it
was
posted
on
the
dock.
For
for
this
issue,
maybe
not
it
was
posted
somewhere,
but
because
python
2
is
getting
end-of-life
all
over
the
place,
like
there's
actual
problems
right
now
with
just
even
installing
node
via
homebrew,
because
of
our
lack
of
support
of
python
3.
I
think
that
this
is
something
that
we
need
to
escalate.
A
I
guess
what
I
was
gonna
suggest
is
you
know
there
might
be
some
some
of
the
information
you
just
asked
for
him
there.
If
not
I
would
talk
to
sokrati
pre
an
as
well
as
clogs
he's
been
helping
to
push
that
as
well
and
I
know.
There's
various
issues,
I,
don't
know
them
off
the
top
of
my
head,
though.
The.