►
Description
B
C
Yeah,
it's
only
bad
yeah,
I'm
I
can
so
one
thing
that
I
did
last
week
was:
I
got
started
on
trying
some
stuff
adding
change
locks
for
individual
items
in
the
documentation,
which
is
something
people
have
been
asking
for
a
couple
of
times
over
the
last
year,
and
I
think
that
would
be
pretty
cool,
so
I'm
working
on
that
I.
Let
me
know
when
something
comes
around
and
yeah
Bradley's
next.
F
B
I'm
so
January
bit
difficult
for
making
some
moving
house
Molly
involved
in
that,
but
I
have
been
spending
quite
a
bit
of
time
on
automating,
my
scripts
for
collecting
Health
metrics
on
the
repo
and
also
with
website
downloads,
and
that
kind
of
thing
so
I'll
have
some
things
to
share
for
that
soon.
Next
is
secretary
sector
Dupree
on.
J
K
B
B
A
B
Cool
request:
101
16,
which
is
adding
codon
warnings
to
do
preconditions
back
on
the
agenda
this
week,
deprecation
policy
as
well.
It's
back
same
with
the
copyright
one.
Two
three
issues
there,
which
will
James,
will
give
us
an
update
on
that
sounds
of
it
growing.
The
group
of
releases,
which
I
think
is
back
on
yeah.
B
It
is
back
on
the
agenda
and
the
ESM
eps
bridling
will
is
joining
us
this
week
again
for
I'm
so
hopping
straight
into
it
proposal
to
move
up
guides
from
no
joy
from
no
jets
node
to
know
DJ
s,
/,
no
jstor
org.
So
there's
a
some
guides
in
the
docs
directory,
mainly
under
there's
a
guides
directory
with
also
topics
directory
evan
is
proposing,
but
apparently
as
an
outcome
of
a
discussion
within
the
docs
working
group
that
these
be
moved
to
the
OGS
org
website.
B
H
A
Still
think
it
would
be
better
to
maintain
from
Corey
if
a
build
pipeline
actually
existed
to
get
them
onto
the
website
properly.
Given
that
doesn't
exist
and
probably
won't
be
built
recently
in
due
time,
then
we
should
probably
just
move
them
most
of
the
many
ways,
I'm
not
really
sure
what
we
want
to
do
with
like.
So
we
ended
up
in
a
situation
not
on
purpose
where
we
actually
have
like
guides
and
topics
that
are
about
stuff.
A
K
That's
that's
in
the
issue.
The
the
docs
team
doesn't
want
that
stuff.
They
do.
They
just
want
the
the
user
facing
stuff,
the
stuff,
the
stuff
like
you're,
describing
about
how
to
write
tests
and
everything
like
that
they
think
should
remain
bundled
with
with
the
repository
so
I
think
everybody's.
On
the
same
page,
there
yeah.
B
B
B
B
G
G
That's
basically
it
what
I
would
ask
is
that
if
anyone
can
look
appears,
there
are
some
editorial
types
of
things
that
could
be
made.
If
anyone
has
any
of
those
comments,
any
suggestions
on
what
that
header
should
be
or
changes,
please
get
those
into
the
PR
be
for
curly
a
few
days
before
that
board
meeting.
So
I
can
make
necessary
changes
before
the
board
reviews.
B
B
B
G
This
is
just
the
way
done
reviews
it
is
a
semper
major,
so
it
does
require
to
ctc
numbers
to
sign
off,
at
least
just
waiting
on
on
getting
that
panel.
So
there's
really
nothing
to
discuss
here.
Unless
anyone
has
any
objections
to
it,
I
think
everything
else
can
be
handled
in
github.
I
just
want
to
would
really
like
to
see
it
settle.
You
know
one
way
or
the
other,
as
it
has
been
up
there
for
a
while.
B
B
B
B
G
It
does
make
a
couple
of
significant
changes,
namely
Ducks.
Only
deprecation
would
be
allowed
as
cember
minors
just
having
a
runtime
impact,
and
you
know-
and
there
are
a
few
other
clarifications
there,
so
we
just
need
to
make
sure
everyone
is
comfortable
with
those
changes
and
if
they
are,
please
weigh
in
I,
don't
want
to
rush.
It
I
want
to
make
sure
that
everyone
is
okay
with
that,
because
it
is
a
policy
change,
but
it
would
be
good
to
get
some
reviews
and
I
guess.
What's
weighing
it
out,
James.
B
B
I
D
Yeah,
basically,
the
concept
of
this
pull
request
is
right.
Now
we
access
the
global
process
and
various
places
inside
of
core,
and
if
somebody
overrides
process
with
no
core
can
crash
in
unexpected
ways,
and
so
this
PR
does
two
things
one
is.
It
makes
it
so,
there's
no
actual
access
to
the
global
process
property.
D
There's
a
fairly
sizable
amount
of
Global's
used
in
core
that
we
aren't
having
the
same
sort
of
robust
feature
of
not
crashing
when
somebody,
for
example,
sets
the
global
air
constructor
to
null
and
so
I'm.
Basically
wanting
to
know
why
just
process
there
are
other
Global's
that
are
in
higher
use
than
process.
D
E
D
E
A
A
D
K
B
B
Okay,
I'll
take
you
back
to
github,
then
okay,
I'll
jot
some
notes
in
here.
The
next
one
was
issue
number
1
90
on
the
tsc
repo,
which
was
a
request
by
the
ocean.
Mortimore
was
a
debugging
working
group.
No
will
have
debugging
classless
Diagnostics
to
bring
node
inspect
no
dash
inspect
in
under
the
foundation.
So
for
clarity
no,
this
is
this
is
not
note
inspector
or
no
inspect,
which
is
a
implementation
of
the
debugger
using
the
v8
inspector
protocol.
B
So
it's
it's
like
reimplemented
notes,
debugger,
but
using
the
new
stuff,
and
so
the
request
here
is
to
bring
the
request
here
simply
to
bring
that
project
in
under
the
nodejs
repo
into
the
foundation
the
what
the
next
steps
are.
I
think
you
know,
that's,
that's
that's
something
to
be
dealt
with
separately,
which
might
which
might
include
bringing
it
into
core,
but
that's
a
separate
discussion.
This
is
simply
to
bring
the
project
in
as
a
alternative
debugger
to
a
debugger.
That's
likely
going
away
soon.
B
B
Let's
do
a
quick
right
here
and
we'll
record
those
votes
on
the
issue,
so
all
those
in
favor
of
adopting
this
project
under
the
vanished
actually
before
we
do.
That
should
note
that
pulling
in
existing
projects
into
the
foundation
is
something
that
the
CSC
has
said
that
we
would
interact
with
the
board
on
if
it
changes
the
scope
of
the
work
that
we
do.
B
We
don't
feel
that
this
project
does
change
the
scope
of
our
work,
since
it
already
fits
under
what
we're
doing
is
basically
a
real
implementation
of
the
existing
debugger
so,
but
we
will
inform
the
board
anyway
if
this
gets
brought
in.
So
all
those
in
favor,
please
say
aye
or
per
dr
plus
1
into
the
chat.
I.
E
B
K
I
believe
that's
still
an
open
question,
whether
you
mean
whether
this
will
ship
alongside
or
whether
it
will
be
more
tightly
integrated,
that
kind
of
thing
yeah,
exactly
or
even
ship,
even
ship
at
all,
it
might
be,
users
might
be
required
to
NPM,
install
it
or
whatever
yeah
I.
Don't
there's
no
resolution
on
that
at
this
time,
I
as
far
as
I
know,
if
anybody
knows
differently,
please
speak
up,
but
there's.
C
K
B
So
it
should
be
noted
that
this
it's
pretty
nice
code.
Somebody
actually
cares
about
the
debugger,
unlike
the
rest
of
us,
which
is
great
I'm.
Somebody
did
mention
that
there's
it's
very
promised
heavy
in
there,
but
you
know
my
view
on
that
is,
if
somebody's
willing
to
to
love
this
thing,
then
they
get
to
decide
that
kind
of
stuff.
So
serious.
B
B
B
D
Mostly
we're
down
to
one
final
question,
which
is:
do
we
want
to
implement
a
sink
loader
async
loader
I
have
some
slides,
but
we
should
probably
schedule
a
separate
meeting
for
that
for
now.
I'm,
just
wanting
to
be
sure
that
we're
still
okay
with
everything
and
the
rewrite
on
pull
request,
number
39,
except
for
the
asynchronous
bit
right
now,
is
that
still
to
be
determined
so.
A
D
A
D
D
Continuing
to
have
matching
the
resolution
algorithm,
except,
I
think
the
rewrite
one
actually
explicitly
states
that
we're
using
urls.
If
not,
I
can
go
and
fix
that
we'll
be
doing
single
default
value
for
common
j/s
snapshot
at
end
of
eval,
and
that's
it
with
a
synchronous
loader.
That
means
a
temporal
dead
zone
with
an
asynchronous
loader
I
mean
not
sure
you
can
ever
actually
get
to
a
dead
zone.
I,
don't
think
you
can,
but
that
has
other
implications.
D
Yet
that's
probably
not
going
to
go
until
beginning
of
march,
I
think
or
april
so
we're
starting
to
see
them
out
in
the
wild
people
are
continuing
to
use
the
dot
dress,
file
extension,
which
may
be
a
little
bit
bumpy
for
us
if
we
do
a
new
file
extension,
but
we
have
on
the
agenda
for
tc39
this
month's
discussing
the
grammar
change,
but
it
looks
doubtful
after
reading
and
talking
to
people
about
the
meeting
in
November
so
which
grammar
change
isn't
making
it.
So
source
text
cannot
parse
in
both
script
and
module
mode
really.
D
One
of
the
complaints
was
kind
of
interesting
in
November,
which
was
what,
if
they
bring
import
two
scripts.
So
a
little
interesting
there's
a
ton
of
notes
on
the
tc39
notes.
We
go
if
you
want
to
see
where
dave
herman
discusses,
proposing
that
tc39
come
to
the
node
group
and
suggest
the
use
module
pragma,
so
that
got
stage
one
and
the
tc39
process
in
November.
D
Is
complicated,
it's
not
our
choice
that
we
can
do
because
you
can
still
get
into
odd
situations
with
it.
For
us,
it
would
be.
Optional
is
the
main
problem.
It
would
just
mark
a
source
Texas
only
being
possible
in
module
mode,
but
it
being
optional
means
basically,
node
would
be
degraded
to
a
second-class
citizen.
D
D
D
B
G
Let
what
I
suspect
I
mean
is
it's
going
to
end
up
being
discussed,
likely
grow
extensively,
a
bit
upcoming,
tc39
meeting,
this
kind
of
where
things
are
at
and
I'm
pure.
A
lot
of
us
will
come
up
and
we
discussed
it's
just
a
lot
of
things.
We
just
kinda
to
figure
out
what
we're,
what
we're
going
to
do,
given
that
current
skater
punks
James.
G
B
A
G
D
Yeah
there
are
just
two
pending
items:
really
a
CGC
choosing
sync
versus
async
loader
and
that's
purely
on
us,
and
then
the
other
is
tc39
going
forward
with
changing
grammar
or
not
going
forward
man
if
they
go
forward
we'll
take
that
route.
If
they
don't
go
forward,
we're
probably
going
to
just
only
have
the
file
extension
unless
we
want
to
try
to
bike
sort
through
the
many
edge
cases
we
saw
in
the
past.
Okay.
B
D
Going
to
figure
that
out
this
meeting,
okay
last
meeting,
we
said
we're
going
to
set
up
a
meeting
purely
for
that
and
it'll
probably
just
be
Mason
and
out
slides
ahead
of
time,
there's
not
too
much
to
actually
read
on
it.
This
feels
like
a
few
edge
cases
and
what
happens
and
then
just
thinking
about
how
that
differs
from
babble
and
things
like
that.
Okay,.
G
G
B
B
So,
let's
move
on
the
last
item
on
our
agenda
is
issued
number
48
in
the
CTC
repo,
which
is
growing.
The
number
of
releases
in
the
people
authorized
release
group.
So
the
note
here
is
that
it's
not
limited
to
ccc
members.
It's
actually
open
to
collaborators.
The
CTC
just
needs
to
authorize
this,
and
currently
there
are
two
to
vote
two
people
up
which
is
Italian,
Custis
and
Gibson.
B
B
B
E
B
B
B
B
F
F
F
B
B
You
can
see
the
you
can
go
to
the
we've
got
a
calendar
for
all
our
meetings.
If
you
look
in
the
minutes
for
this
meeting,
you
can
see
a
link
there.
I
think
the
link
is
scattered
around
or
contact
one
of
us.
If
you
want
the
calendar
link,
what
else
do
we
have
coming
up
in
the
next
week?
We've
got
this
DC
meeting
and
next
week
and
yes
c
meeting
next
week.
Aside
from
that,
I
don't
see
anything
else
in
the
calendar.
Oh.