►
Description
A
A
A
B
A
A
Okay,
so
moving
on
to
the
issues
tagged
with
TSC
agenda
from
across
the
repo,
the
first
ones
are
under
no
GS
/,
node
I
think
the
first
one
was
just
to
mention
so
collaborator
nomination
for
Bethany
Griggs
she's
accepted,
and
it
looks
like
from
the
comments
in
the
issue.
There's
no
objection
so
that
will
likely
go
forward
in
the
next
couple
weeks,
just
as
an
FYI.
A
C
B
B
G
So
yeah
at
this
point,
looking
at
the
kind
of
it
just
looking
at
the
sheer
amount
of
work
just
left
to
do,
we
know
kinda
knew
we
have
to
do
it.
I
prefer
to
not
land
around
on
deprecation
for
1000
and
then
reevaluate
before
10
goes
LTS
and,
in
the
meantime,
see
how
much
work
we
can
put
in
to
actually
get
an
ecosystem
caught
up
he's
just
a
shitload
of
work
that
needs
to
get
done.
B
B
I
A
So
I
think
that
was
why
we
decided
to
that.
We
would
do
it.
I
guess.
I
can
I
can
see
the
argument
that,
if
we're
really
asking
people
to
do
work
immediately
and
we're
only
giving
a
short
runway
that
you
know
it's
even
if
it's
slightly
worse,
it
may
be
better
to
give
people
a
longer
runway
and
and
do
it
in
eleven.
Instead
I.
C
K
K
A
J
Like
I
just
wanted
to
mention
that
there
is
at
least
one
person
who,
on
the
mailing
list,
said
that,
after
enabling
the
pending
applications
like
via
an
environment,
they
were
rebels,
so
that
is
always
on
for
them
by
default.
It's
like
whether
doing
normal
development
work
on
those
programs.
They
change
their
mind.
I,
don't
think
they're
here
to
this
meeting,
but
yeah
it's
like.
If,
if
some
of
you
haven't
done
that
yet
they're,
you
should
do
it
like.
I
G
G
D
It's
for
me,
it's
around
25%
of
my
modules,
which
is
a
lot
of
work,
just
counting
those
modules
and
getting
it
up
to
date
with
the
timeline,
I
would
even
say:
11
is
kind
of
stretching
it,
but
the
point
was
made
just
before
it's
also
very
interesting
to
me
is
like
werster's
Wesley.
What's
the
rush
here,
it's
Sara
filling
sure.
That's
the
DDoS
angle.
I
G
One
thing
I
want
to
make
sure
that
we
we
don't
complete
these
issues
too
much.
What
what
is
obvious
is.
It
was
a
more
general
issue
with
deprecations
runtime
deprecations.
Of
course,
we
need
a
better
way
of
handling
these,
something
that
is
something
that
is
actually
more
effective
and
getting
people
that
actually
change
their
behavior
and
something
that
is
not
as
disruptive
to
ecosystem.
G
It's
going
to
take
us
a
little
while
to
figure
out
what
that
right
solution
is
we
have
a
months
until
the
node
10
release,
so
I
don't
want
to
hold
up
to
the
decision
about
the
buffer
constructor
until
we
have
a
better
solution
for
that
night,
we
need
to
separate
those
discussions
and
I,
don't
know
if
we
can
get
a
better
deprecation
strategy
finish
and
landed
in
core
in
a
month.
So.
J
Yeah,
that's
definitely
high
level
discussion
that
we
should
be
having,
but
I
guess.
You
said
it's
probably
not
the
right
time
to
do
that
and
so
I'm.
Coming
back
to
the
point,
that
chopper
is
something
that
a
lot
of
people
have
been
commenting
about
is
like
possibly
a
deprecating
oracle
that
is
outside
of
node
modules.
It's
like
been
really
good
that
you're
actually
working
on
at
this
point,
at
least.
I
H
J
D
I
can
share
first.
Let
me
just
share
my
main
concern.
My
main
concern
is
that
there's
a
big
bunch
of
modules
out
there
that
will
just
never
get
updated
for
various
reasons
and
a
bunch
of
important
modules.
Don't
get
updated
for
just
my
other,
because
to
maintain
are
off
to
do
something
else
or
it's
gonna
take
them
half
a
year
to
merge
ago,
because
it
happens
all
the
time.
D
I'm
curious,
just
like.
What's
the
what's,
the
T
sees
like
opinion
about
that
is
that
okay,
it's
like
said:
okay,
that
we're
gonna.
Have
this
warning
just
being
there
for
like
a
funny
every
year
or
is
the
like?
Should
we
just
start
using
new
modules,
or
you
know,
what's
what's
that
you
know
feeling
about
that.
D
I
mean
if
there's
but
I'm
sure,
there's
like
it
things
like
grocery
fact
that
has
a
bunch
of
dependencies,
because
it's
affected
with
people
that
not
want
to
take
a
while
to
merge
Paul
Chryst,
because
you
know
it's
been
pretty
stable
for
a
while.
So
that's
like
that's
my
main
concern,
I
mean
I'm.
Sure
most
of
my
stuff
I
would
give
to
get
up
to
date.
Giving
it
long
enough
timeline
and
I
understand
it
problem
much
new
code
being
published
with
the
old
with
their
and
old
constructor.
D
Still,
let
me
see
that
that's
important
and
something
that
you
get
the
rest
and
maybe
that's
a
different
issue,
but
just
really
worried
personally
about
justification,
just
be
stuck
there
forever
or
like
or
just
like
things
like
Paris
or
iodine
capacities,
because
people
will
just
forget
to
do
something
else.
Yeah.
G
I,
so
looking
at
some
cut
earlier
today,
come
understand.
Emphasize
this
point
a
little
bit.
There
is
code
for
browser
fights
day
that
actually
dynamically
generates
the
code
and
those
are
much
harder
to
find
and
identify
on
how
to
make
these
fixes,
because
the
code
is
dynamically
generated.
One
module
in
particular
actually
builds
the
string
where
it's
building
the
buffer
constructor
into
the
stringing
code
that
is
generating
it's
not
clear
how
we
inject
a
new
dependency
into
that
path
for
the
polyfill.
So
it's
non-trivial.
I
I
I
B
Dealing
with
abandoned
modules,
so
there
is
a
path
forward
for
important
modules
that
are
abandoned,
run
maintained,
or
at
least
in
in
in
in
many
cases,
there's
a
path
forward.
It's
not
a
complete
solution.
There's
going
to
be
people
who
you
know
maintain,
you
know
who
yes,
there's
gonna,
be
issues
and
I,
don't
know
what
the
answer
there
is-
and
you
know,
but
Matias
raises
a
point.
H
G
I
Another
branch
is
that
if
someone
does
not
run
the
ball
field,
then
the
change
would
become
a
similar
major
for
them
if
they
still
support,
for
example,
node
0.10,
then
drove
in
support
for
that
is
still
he's
speaking.
A
major
change
and
two
major
changes
propagate
much
solely
through
the
ecosystem,
so
the
best
solution
would
be
to
use
a
power
tool
for
resistant
branches,
and
it
is
a
new
modulation
without
the
polio,
direct
and
support
for
all
the
rations.
H
D
H
H
If
we
do
genuinely
believe
that
we
should
get
rid
of
it,
so
we
so
I
guess
the
question
that
they're
making
questions
we
have
to
answer
us
are
we
are
we
actually
committed
to
getting
rid
of
buffer
constructor
usage
completely?
And
secondly,
how
do
we
decrease
that
you
and
if
it's
not
just
a
hard?
Well
it
a
twill,
not
hard,
but
the
straight
runtime
deprecation.
Then
what
other
strategy
could
we
use
to
do
it?
Because,
because,
as
chakra
said,
the
more
we
delay
the
more
the
usage
grows
not
decreases.
G
G
J
That's
so
like
I
mean
we're
having
like
a
lot
of
things
to
talk
about.
If
we're
having
a
lot
of
high-level
discussions
that
are
read
to
happen,
that
we
should
try
to
continue
having
but
like
it
would
be
nice
to
have
us.
The
outcome
of
this
meeting
like
that
had
path
forward
for
this
particular
deprecation.
G
I'll
just
say
that,
as
the
person
that's
actually
doing,
the
1000
release
I'm
gonna
get
out
of
the
building
everything
else.
I
am
extremely
disinclined
to
actually
land
this
/,
no
I
am
not
feeling
comfortable
at
it.
At
all,
I
have
run
the
1000
test
builds
with
pending
notification
on
I
did
so
this
weekend
quite
extensively,
and
it
is
massively
disruptive
God,
Nikita
I.
I
I
I
He
also
said
the
dibs,
so
in
your
own
code
you
would,
if
you
use
a
buffer
constructor
in
your
own
code,
you
will
see
any
potential
on,
but
if
you
use
it
in
the
depths,
you
won't
see
duplication
model
for
now,
at
least
for
ten
canto,
so
I
won't
ask:
does
anyone
have
arguments
against
a
legend?
A
deputation
has
character,
so
they
learned
in
the
duplication
for
the
buffer
constructor
for
cases
when,
in
its
outside
of
role,
models.
B
A
I
B
Yeah
I
have
traced
in
a
trace
warnings,
thanks
to
like
thanks
at
Argus.
I
trace
warnings
enabled
so
I
can
see
where
the
where
the
CLI
is.
You
know
tripping
up
and
every
CLI
is
tripping
up
on
on
stuff.
That's
inside
node
modules
I
haven't
seen
one
yet
that
was
in
the
actual
CLI
code,
for
what
that's
one.
Okay,.
D
But
maybe
maybe
I'm
misunderstanding
what
Nikita
said.
I
also
suggest
this
just
originally
like.
What's
one
of
the
people
suggesting
this,
they
changed
I
think
I
think
it's
a
pretty
ok
path
forward
to
just
so
I'd
from
one
of
the
reason.
One
of
the
things
that
seems
to
be
something
we
have
to
address
is:
how
do
we
stop
people
from
publishing
code?
Then
you
just
knew
buffer,
which
is
seems
to
be
one
of
the
big
problems
here
that
didn't
stop.
So
if
you
have
a
deprecation
that
only
happens
when
you're
with
the
pub
code.
D
Basically,
if
you
have
code
that
you're
running
with
no
like
your
tests
or
stuff
like
that,
where
the
code
does
David's
I
dunno
modules,
folder
relative
to
your
required
at
main
any
for
the
defecation,
so
then
the
users
developing
new
code
or
immediately
see
that
it's
a
bad
idea,
but
downstream
users
of
modules
won't
get
disrupted.
So
we
ten
we
we
can't
Emily
gives
us
time
to
to
like
fix
the
ecosystem
and
in
a
pace,
that's
comfortable
for
everybody.
Well,
hopefully,
stopping
your
code
being
punished.
I
think
that's
a
pretty
valid
argument.
B
So
real,
quick,
just
a
readout
for
listeners
I
think
it's
Collins
comment
and
then
also
to
answer
it
as
their
plus-one
to
that.
But
what
is
the
long-term
plan
from
it?
Assuming
a
lot
of
the
modules
still
won't
be
updated,
so
removal
of
the
buffer
constructor
will
be
a
possibility.
My
hope
is
that
pending
deprecations
will
still.
B
If
you
use
the
pending
deprecations
flag,
then
it
will
still
surface
those
those
those
and
that
if
we
can
get
like
a
lot
of
the
colonic,
some
odd
collaborators
we
get
collaborators
to
you
know
use
the
pending
deprecation
flag
to
route
these
things
out
and
submit
pull
requests.
Maybe
we
can
make
a
small
dent
in
the
most
important
of
these
modules
may
be.
I
G
J
B
B
J
J
B
No
objections
so
I'm
going
to
update
the
issue,
the
tracking
issue,
with
the
information
that
at
the
meeting
today,
we
decided
its
etc
and
I'll
tag,
no
I'll
tag
TSC.
So
if
anybody
here
or
any
of
the
five
CCC
members
who
are
absent
do
wish
to
object
or
ask
questions,
you
have
concerns,
we
can
do
so
in
github.
A
A
Okay,
I'll
suggest
that
we
do
the
update
on
a
strategic
initiatives
last
and
just
do
the
node
GS
admin
one
first,
so
travel
fund,
that's
on
the
agenda,
just
as
an
FYI
to
people
that
just
to
be
aware,
when
you're
approving
the
travel
fund
request
that
we
actually
have
to
be
careful,
that
we
don't
go
over
our
budget.
So
when
you're
approving
them
to
make
sure
you
take
a
look-
and
you
know
be
comfortable
that
we're
still
within
the
limit
we
have
for
the
year.
A
F
B
B
Okay,
I'll
just
keep
going.
We
do
have
a
send
an
email
to
calm,
calm
and
TSC
about
this,
but
we
do
seem
to
have
some
some
organizational
dysfunctions,
probably
too
strong
a
word,
but
hiccup,
perhaps
that
we
need
to
address,
which
is
that
in
the
past
the
travel
fund
was
the
TSC,
so
the
TSC
would
enough.
People
would
approve
it.
We
and
then
someone
would
land
the
change,
and
that
would
be
that
what
seems
to
be
happening
now
is
since
it's
co-managed
by
TSC
and
calm
calm.
A
The
one
suggestion
I
made
in
the
issue
is
if
we
could
actually
get
the
volunteer,
who
kind
of
managed
the
fund.
You
know
that
would
help
make
sure
we
we
know
where
we
stood
and
could
give
the
final.
You
know
if
there
was
somebody
who's,
gonna
actually
say.
Yes,
it's
now
approved
go
ahead
right
because
I
think
it's
just
you
in
this
particular
case,
the
consensus
is,
is
still
the
way
we're
working,
but
as
the
person
going
at
the
book,
you'd
kind
of
like
somebody
to
have
said,
yeah,
okay,
a
consensus
reached
right.
L
A
C
Just
to
be
very
to
ask
a
very
probably
blunt,
not
even
blunt,
like
dumb
question
here
by
considering
that
anybody
that
is,
a
collaborator,
can
ask
for
those
type
of
funds
and
if
they
make
sense
they
and
they
will
reach,
see
them.
Okay,
can
we
just
ask
somebody
from
the
foundation?
Maybe
it
worked
with
this?
C
G
G
Spending
funds
that
aren't
yet
allocated
that
could
be
a
problem,
so
we
have
to
keep
we
had.
We
just
have
to
keep
a
tally
of
how
much
is
left,
so
we
can
ask
for
another
allocation
now,
they're
they're
really
good
about
you
know.
If
we
say
we
need
the
money,
you
know
to
keep
going,
get
us
through
the
rest
year.
They're
gonna
be
good
about
providing
that
there's
plenty
of
money
available.
B
H
B
A
Sure
well,
III
degree.
The
one
thing
I'll
just
add
is
Mateo.
If
we
can't
find
it
a
volunteer
in
the
comm
come
then
your
suggestion
of
you
may
be
asking
the
foundation
makes
sense.
So
let's
keep
it
on
in
the
issue.
There
is
the
next
step,
if
that
doesn't
pan
out
yeah
okay.
Yes,
we
have
seven
minutes
left,
let's
do
the
the
QA
on
or
the
meeting
times
discussion
before
we
get
to
strategic
initiatives,
and
you
know
if
we
have
time
we'll
look
back
to
them.
If
not,
we
won't
so
Chalker
or
nikita.
I
Some
differences,
but
all
those
have
a
common
time
at
16
and
none
of
those
have
anything
doing
16.
So
my
current
proposal
would
be
to
move
the
next
meeting
10
to
16.
Instead
of
what
should
be
something
like
fortunate
I
think
and
for
everything
else.
I
will
email
the
alternative
variants
to
the
email.
A
A
Okay,
so
I'd
so
I'd
propose
we
move
forward
with
you
know.
Basically,
updating
the
calendar.
216
UTC
send
an
email
to
the
mailing
list,
just
as
an
FYI
and
an
opportunity
for
people
to
say,
hey,
wait,
a
second
that
that
doesn't
work
out,
and
unless
that
happens,
you
know
we
can
move
forward
with
that.
Any
objections.
A
A
B
A
A
Will
so,
if
you
think
about
it,
if
anybody,
if
nobody
on
this
call,
can
can
do
it
all
I'll
see
if
I
can
reach
out
to
say
Francisca
who
I
don't
think
is
on
the
call
today
see
if
she
can
do
it,
otherwise
I'll
try
and
figure
out
what
we
can
do
or
not
the
Q&A
time,
yeah
sure.
Let's
we
got
three
minutes.
So,
let's,
let's
just
skip
the
Q&A,
sounds
good.
A
J
J
Yeah
so
like
I
started
according
the
first,
that's
just
wrong.
I
owe
over
to
note
for
the
they
are
just
concerned
with,
like
cleaning
up
once
note
exits,
because,
like
that's
what
we
want
workers
to
do,
it's
like
when
their
note
instances
they
and
I
have
to
take
care
of
that,
and
it's
causing
trouble
on
Windows
and
like,
if
anybody's,
like
really
interested
in
debugging
for
some
Windows
and
has
knowledge
with
like
the
windows
API
itself.
Or
so
we
did
it.
Yeah.
A
A
A
G
Just
ask
for
some
similar
attention
to
the
hb2.
We
need
to
start
building
the
list
of
exit
criteria
for
bringing
a
net
of
experimental
API
has
been
relatively
stable
for
the
past
few
months.
It's
one
change
possible.
Api
change
for
trailers
I'm,
looking
at
making
here
very
very
soon,
but
everything
else
is
pretty
stable
and
it's
done
a
lot
of
fantastic
work
on
helping
on
the
internals
and
performance
in
the
stream
and
all
this
good
stuff,
so
you're
good
to
get
some.