►
Description
B
A
C
A
B
A
A
A
The
discussion
has
been
around
adding
changing
the
behavior
that,
when
you,
when
you
basically
I,
think
trying
to
set
the
the
properties
on
process
f2
undefined
or
you
know,
with
the
thought
that
that
was
trying
to
remove
them.
That
would
actually
end
up
removing
them.
As
opposed
to
what
happens
today,
which
is
you.
A
F
F
E
A
E
F
Kind
of
discussion
is
stuck
and
large.
Some
numbers
from
the
TSE
thinks
that
that's
a
good
thing
to
do,
and
so
one
Timothy
doesn't
think
so
that's
my
that's.
The
only
reason
why
I
put
it
on
the
TSC
like
I,
agree
that
this
change
should
land
so
I'm.
Not
it
has
been
stopped
for
it
for
some
days,
so
I
think
it's
we
can
decide.
If
you
want
to
move
it
forward
or
not.
I
guess.
A
If
we
could
gather
more
data
that
like
to
me
that
the
the
reason
not
to
do
it
would
be
as
if
we
do
think
it's
gonna
break
a
bunch
of
people
right
like
if
it
doesn't
break
people.
It
seems
like
the
new
behavior
is
the
right
thing,
but
if
it
was
gonna
break
a
whole
bunch,
then
that
would
be
a
reason
not
to.
C
So
from
from
reading
Timothy's
comment,
I
wonder
if
his
suggestion
isn't
to
because
we
all
I
have
a
an
issue
with
no
on
UTF
environment
variables,
if
some
sort
of,
if
we
don't
need
a
different
API
for
getting
and
variables
all
together
for
the
future
regardless.
And
it
might
be
better
to
do
saying
and
not
in
a
new
API.
F
F
A
A
A
F
A
G
A
G
C
A
F
E
A
F
F
Doesn't
seems
to
me
an
issue
that
we
can
that
you
can
discuss
on
the
side
about
this
cinnamon,
so
it's
very
hard
to
make
an
opinion
about
this
stuff.
So
it's
if
you
follow
the
discussion,
is
it's
very
hard,
so
yeah
I'll
send
him
an
email
and
say:
can
we
do
as
a
separate
meeting
to
make
to
make
this
happen,
and
if
there
is
some
coordination
to
banana
I
work
with
him
and
coordinator
Costa,
okay,.
C
C
A
So,
let's
move
on
to
the
next
one,
which
is
1495,
it
has
to
do
with
change,
basically
title
six
type
of
armed
version.
It
seems
like
in
some
cases
it's
it's
compared
with
an
integer
instead
of
the
string.
Seven
I
think
the
reason
it's
on
the
agenda
is
that
basically
hasn't
been
moving
forward.
Rubin
out
of
it.
A
I
think
you
know,
looking
through
the
history
miles
had
run
such
a
make
against
the
leaves
released
to
get
some
data
based
on
that
to
see
if
it
was
gonna
cause
breakage,
because
there's
kind
of
concern,
so
most
people
are,
you
know.
Who've
commented
in
have
said
they're
kind
of
minus
zero
because
they
haven't
we're
not
sure
about
the
breakage.
H
A
I,
don't
know
if
there's
any
like
I
guess
it's
I,
don't
think
that
it's
were
up
to
a
vote
here.
Necessarily
it's
kind
of
like
you
know,
and
let's
say
unless
people
on
the
call
are
willing
to
say:
hey
yeah,
let's
move
this
forward,
it
may
be
back
with
a
comment
saying
you
know.
We
discussed
this.
A
A
A
I
A
Brought
it
up,
nobody
was
comfortable,
you
know.
Maybe
if
there
was
more
data
gathered,
you
know
miles
finished
the
looking
at
commented
based
on
the
Sydenham
runs
or
rotted
commented
it
might
move
forward.
But
at
this
point
you
know
we
really
need
to
wait
for
one
of
those.
Two
things
is
that
a
reasonable
resolution
for
another.
B
One
other
possibilities:
we
can
just
decide
as
the
TSC
that
you
know
we
give
special
dispensation
to
this.
This
one
doesn't
need
two
approvals
or
something
like
that
which
seems
kind
of
silly.
You
think
one
of
us
would
just
go
in
and
give
it
a
plus-one
if
we're
gonna
go
that
far.
But
if
that's
a
possibility-
and
we
have
enough
people
here
today
to
make
that
decision-
if
we
all
agree
that
that's
okay,
I'm.
F
D
A
A
A
D
D
A
A
A
A
C
So
I
think
just
about
everywhere,
I'm
in
ring
to
this
so
I
think
just
a
bit.
Everyone
agrees
that,
like
it
shouldn't
abort,
but
there's
disagreement
on
exactly
what
it
should
do.
I
believe
the
disagreement
is
if
it
should
handle
this
as
if
the
main
property
of
the
package.json
is
missing
or
if
it
should
handle
it.
A
E
C
Other
than
Bradley
seem
to
agree
with
treating
it
as
not
I
think
that
I
think
this
yeah.
This
treats
it
as
as,
if
the
file
isn't
there
pretty
sure
right
so
there's
I
think
there's
like
some
consistency,
stuff
that
Bradley
is
worried
about
you
know.
It's
been
suggested
that
we
might
be
able
to
make
that
more
consistent
in
a
subsequent
PR.
I
C
C
C
C
C
C
C
C
C
A
G
A
A
C
C
C
C
A
A
A
E
A
A
A
A
C
B
A
B
A
B
A
A
E
A
A
A
Okay,
moving
on
to
the
strategic
initiatives
are
a
regular
review
and
API
I'm
happy
to
report
that
bcrypt
now
has
an
N
API
tag
version
and
in
the
regular
er
you
know
the
the
main
repo,
where
b-cups
being
maintained
and
Nicola
who's
been
working
with
the
as
part
of
the
N
API
team
now
actually
is
using
it
at
his
company
in
production.
So
we
have.
You
know
once
at
least
one
instance
where
an
API
is
being
used
in
a
production
application
which
is
good
because
it
helps
satisfy
the
criteria
for
experimental.
A
You
can
read
more
about
it
in
the
link
that
I,
provided
there
we're
also
making
progress
on
integration
with
pre
build.
We
do
expect
the
pr
to,
and
actually
it
shouldn't
say,
pre
build.
It's
probably
preach
yep,
so
I'll
update
that,
but
basically
we're
expecting
a
PR
to
be
opened
against
that
repo,
with
the
changes
that
were
suggesting
as
well
miles,
couldn't
make
it
on
the
module
front,
but
he
did
provide
an
update.
I
won't
try
and
go
through
that,
but
you
can
read
through
that.
A
B
Good
things,
my
moderation
update
is
in
the
issue
for
this
meeting
and
it's
also
in
the
minutes
up
above
in
the
announcements
but
I
also,
we
also
removed
moderation
team
from
strategic
and
issues.
It's
just
an
ongoing
thing
now
and
it's
not
strategic.
It's
spun
up.
It's
working,
everything's
great,
so
I'll
continue
to
provide
updates
because
that's
in
our
in
our
mandate
or
charter
or
charge
or
whatever
its
called,
but
it
doesn't
have
to
be
part
of
the
strategic
updates,
make.
A
A
G
You
yes,
so
yes,
6.4
landed
on
master
last
week
and
I
opened
yesterday
I
think
the
PR
for
vietze
sees
at
5:00,
which
would
be
stable
on
March,
6
and
I
haven't
found
any
major
issue
just
with
some
Power
PC
platforms,
but
only
on
v8
tests.
I,
don't
think
there
is
an
issue
with
node
itself.
Okay,
well.
A
A
A
A
I
We
were
talking
about
how
it
we've
been
using
hacker
one
for
the
ecosystem,
reporting
triaging.
It
was
going
well.
We
still
kind
of
hadn't
got
a
lot
of
response
from
the
core
team,
the
core
security
team.
You
just
wanted
to
get
it
on
the
TSVs
radar
that
you
know
we're
interested
in
doing
this.
I
think
that
can
largely
be
taken
off
of
the
agenda,
because
vladimir
deter
keen
open,
TSC
issue,
474
requesting
that
he
be
added
to
the
core
triage
team.
That
was
before
last
week's
security
working
group
meeting.
I
A
A
A
Think
yeah,
if
people
trying
to
chime
in
on
the
other
issue
as
well,
which
you
know
in
terms
of
his
request
to
join
it
sounds
like
there's
been
at
least
some
some
positive
response,
which
just
probably
the
best
way
to
try
and
push
this
forward.
So
I'll.
Take
the
issue
off
the
this
issue
off
the
agenda.
A
A
F
There
has
been
a
comment
on
the
ESM
named
expedition
and
just
say
that
the
major
one
of
the
question
asked
to
the
DSC
was
about
out
deprecation
I'm,
going
to
be
handled
with
the
SM,
which
is
a
very
long
question.
So,
and
everybody
I'm
already
discussing
with
my
house
on
how
to
to
get
things
point
cast.
D
A
C
I
C
A
E
A
Napi
team
meeting
at
1:30
Eastern
tomorrow
and
then
next
week
we
have
a
build
work
group
meeting
release
now
build
work
group
meeting
scheduled
for
the
6th
at
Eastern,
the
diagnostic
working
group
at
4:00
Eastern
on
the
7th.
A
C
Hey
JD,
he
asks
also,
if
there's
any
plans
to
use
napi
for
notes.
Esm
implementation
in
particular
can
make
things
not
as
v8,
centric
and
I.
Think
I
can
answer
that
so
I
think
there
was
a
long-term
discussion
of
that,
but
there's
certainly
no
short
or
medium-term
plans
of
switching
node
internals
to
use
something
like
an
API.
At
this
point.