►
Description
A
B
A
Ok,
so
if
not,
let's
move
on
to
the
issues
tagged
in
the
agenda,
so
the
first
one
is
requests
to
elevate
for
elevated
permissions.
13
1,
337
I
took
a
quick
look
at
that
earlier
and
from
the
latest
comments.
I
think
the
agreement
is
that
you
know
we
can
take
it
off
the
TSC
agenda
for
now.
So
that's
what
I
propose
we
do
unless
anybody
else
has
different
thoughts.
A
D
D
E
E
That
closed
event
in
HTTP
response
is
actually
was
actually
not
behaving
like
the
other
closed
events
in
core,
meaning
that
it
was
only
fired
when
a
request
response
was
closed
abruptly
in
it
was
an
error
like
event
makes
no
real
me
to
me
to
me.
Look
like
a
bug,
but
it's
basically
a
legacy
band.
It
was
basically
a
legacy,
but
anyway
the
reason
for
changing.
This
seems
very
clear
to
me.
However,
that
was
assembler
major
change
that
slipped
in
without
anomalies.
A
A
E
F
E
A
E
E
A
G
A
A
A
E
B
E
E
E
So
those
are
the
questions,
so
those
are
very
like.
Thank
you.
If
you
look
at
the
this
text,
I'm
just
passing
it
here.
You
have
a
child
if
this
taxi
Nate-
and
this
is
the
text
in
you-
intend-
and
you
can
see
that
in
aid,
it
says
indicate
that
the
underlining
connection
was
terminated
before
response
and
was
called
or
able
to
flush.
E
A
E
E
A
A
G
G
G
B
G
G
Think
that
there
is
also
a
way
to
fix
desk
EGP
right
now
without
outer
edge
originated,
but
this
would
go
making
that
function
to
meet
with
echo
morphic
yeah,
that's
not
on
the
organ
theft.
Assault
is
a
parameter,
but
that
also
changed
the
digital
format,
because
they
returned
for
much
have
to
include
this
out.
In
that
case,
if
this
also
has
specified
the
user
to
specify
the
salt
is
ability,
in
fact
that
is
one
of
the
food
carts
of
the
second
one
is
that
there.
B
G
G
A
G
A
H
A
No
I
was
reading
my
hand
just
so
I
could
get
promoted
in
all
right,
so
so
chakra
I
guess
did
it's
like.
Do
you
have
any
recommendations
on
our
on
our
next
step?
Is
it
that
they're?
You
know
we
wait
to
see
what
the
security
working
group
discussion
where
that
ends
or
do
we?
Do
you
think
that
we
need
to
take
some
action
now.
G
One
of
the
purple
section
catch
people
work
specially
was
that
he
should
be
it
removed,
ready
named,
and
this
would
be
a
semi
major
change
because
something
it
was
already
released
by
its
unless
it's
a
lightly.
That
function
is
Houston
ecosystem.
By
now
they
package
I
need
to
take
all
cadet,
Lodge
I'm,
not
sure
if
it
is
possible
to
a
device
attached
pretty
so
much
yeah.
F
I'm
not
sure
it's
possible
to
vary
that
we
should
probably
go
look
if
there's
usage
there,
someone
in
the
chat
was
saying
they've
been
searching
to
I,
get
up,
for
instance,
for
usage
of
it
and
haven't
seen
anything
so
and
I.
Imagine
if
it
is
quite
complex,
it
will
take
a
while
for
anyone
to
actually
like
adopt
it.
You
know
so.
G
In
image
to
something
else,
and
because
if
it
skipped
function
and
have
the
old
one,
okay,
so
one
of
the
possible
solutions
to
introduce
a
safer
escape
function
using
the
AP
that
was
proposed
by
some
of
the
security,
diligent
people
and
renamed
the
old
one
like
to
something
in
a
script
or
whatever.
Let's
keep
something
like
that
and
locate
the
old
usage
of
a
script,
but.
F
I
think
there'd
be
another
possible
option
for
how
to
approach
this.
Although
I
think
it
is
maybe
a
little
bit
unfavorable,
because
it's
II,
it
would
take
a
little
bit
longer
time,
but
we
could
do
something
like
essentially
deprecated
the
current
API
or
issue
warnings
for
it
and
then
change
it
in
December.
Major
version
now
I
know
there's
people
that
actually
want
to
use
this.
So
that
might
not
be
that
effective.
F
G
A
So
why
don't
we
continue
discussion
in
the
github
issue
that
the
sort
of
associate
the
associate
thing
we
might
want
to
talk
about
is
like?
Should
we
be
changing
something
in
our
process
to
avoid
this
kind
of
thing
in
the
future,
like
one
thought
that
pops
into
my
head
is?
Is
it
that
like
editions
of
api's
for
crypto
should
have
some
additional
review
requirements,
or
something
like
that.
A
A
A
Okay,
so
then,
moving
on
to
the
next
issue,
which
is
doc,
remove
two
unused
air
coats
from
Ayres
MD.
That
is
issue
number
two
one,
four,
nine
one
I
think
last
time
as
I
remember,
we
were
basically
just
waiting
for
Joey
to
be
able
to
comment
on
the
meeting
in
the
meeting,
so
I
think
we
need
to
wait.
We'll
wait
another
for
another
meeting,
as
we
still
I
think
want
her
input
on
that.
Yes,.
A
A
The
next
one
would
be
proposal
add
new
core
modules
under
a
scope
that
is
number
three.
Eighty
nine
I
don't
think,
there's
necessarily
anything
for
us
to
discuss
this
week,
except
that
I
believe
there
already
is
like
it
was
suggested.
Maybe
when
implementation
would
help
answer
some
of
the
specific
questions
that
PR
is
open,
I,
don't
know
Matteo
if
you've
had
a
chance
to
look
at
that,
I.
E
A
A
E
A
E
A
I
wasn't
I
wasn't
like
its,
it
was
more
like.
Can
we
come
up
with
a
PR
which
would
clarify
and
make
those
kinds
of
things
obvious,
and
is
it
worth
doing
that
versus
whether
you
can
actually
do
it
or
not?
Right
like
is
either
way.
We
got
all
the
information
we
need,
let's
vote,
or
no
it's
useful
to
try
and
get
the
PR
which
will
clarify
some
of
those
things
and
that's,
let's
just
try.
E
A
H
E
A
A
G
C
A
A
A
D
A
A
D
D
D
A
Thought
I
commented
so
I
guess
maybe
I
forgot
to
comment
in
there
I've.
Basically
in
the
discussion,
there's
also
an
issue
in
the
release:
repo,
that's
I
created
that
was
asking
you
know.
Should
we
have
two
different
distributions,
one
which
is
basically
like
you
know,
it's
got
everything.
It's
got
your
development
tools
and
then
one
which
is
a
stripped-down
version
which
is
just
for
deployment.
A
You
know
some
other
languages
have
something
similar.
Java
has
like
an
SDK
and
a
JDK
I
think
somebody
mentioned
that
you
know
a
couple
of
others
have
something
similar
as
well,
and
it
sounds
like
the
the
docker
team
is
actually
going
through
the
process
of
creating
an
image
where
they're
gonna
strip
out
things
from
our
our
regular
builds
and
the
question
of
from
tyranny.
Who
added
this
was
like
you
know,
should
we
be
thinking
about
doing
something
you
know
releases
as
opposed
to
forcing
other
teams
to?
Actually
you
know,
strip
stuff
out
so
depends.
A
The
the
the
final
suggestion,
like
some
of
the
previous
discussion
after
I,
made
my
suggestion
and
and
what
they're
looking
at
doing
I
think
in
the
darker
one
is
actually
only
provide
the
binary.
So
it's
basically-
and
we
already
do
that
for
Windows-
you
can
get
just
the
binary
with
nothing
else,
and
so,
if
you
just
want
to
run
to
run
it
you've
got
the
binary.
You
can
do
that.
Nothing
else
comes
with
it.
E
A
D
A
A
E
But
it's
so
the
the
amount
of
like
doing
it
with
doctor,
so
the
things
that
they're
going
to
remove.
So
that
is,
after
the
you
remove
NPM
and
the
docs
and
some
stuff
you
just
ship
the
binary.
There
is
not
there's
nothing
else
anymore
to
remove
and
if
we
had
anything
to
note
it
will
be
in
the
binary
right.
A
I
I
meant
more
like.
If
you
want
to
add,
say
you
want
to
add
in
something
that
takes
additional
footprint
so
say
somebody
said:
hey
I
want
to
have
yarn
and
NPM
install
okay,
you
know,
one
of
the
concerns
is,
is
well
wait,
a
sec
you're,
making
the
the
download
size
and
the
footprint
size
bigger,
but
if
we
actually
have
two
different
ones,
maybe
that's
okay,
because
if
you
want
the
small
footprint
you
take
the
small
footprint
one
for
the
other
cases,
it
doesn't
matter
so
much
and
that's
really.
E
A
Yeah
no
right
so
so
the
you
know
the
the
the
thing
would
be.
If
we
actually,
you
know,
I
think
what
I
could
see
us
happen
see
happening.
Is
we
have
two
releases
for
each
platform:
1,
which
is
the
binary
only
and
then
one
which
is
the
like:
the
development
kit
that
has
NPM
and
whatever
other
tools
we
think
makes
sense,
and
so,
if
you
want
something
small
small,
you
take
the
binary.
Only
if
you
want
something
that
includes
the
other
tools,
you
can
get
the
bigger
one
and
I'm
just
curious.
A
B
F
A
Already
one
of
the
one
of
the
images
does
I
think
the
stripped-down
one
won't
have
either,
but,
but
you
are
right,
the
darker
one.
There
is
one
that
I
forget,
which
one
already
includes
yarn,
but
that
that's
sort
of
a
separate.
Maybe
that's
a
is
the
wrong
example.
But,
like
you
know,
say
we
we
had
something
else.
We
decided
we
wanted
to
add
in
you
know,
for
example,
you
know
we
want
I.
Think
one
at
one
example
is
full
I
see
you
if
we
want
to
actually
bundle
in
the
full
ICU
data
there.
A
A
B
A
Okay,
so
yeah
I
think
that's
a
good
point.
So
anyway,
I
guess
it's
like.
If
you
have
any
concerns
or
if
you
are
supportive
of
you
know,
I
guess
it's
like
do.
Do
people
think
we
should
actually
consider
having
two
different
things,
and
you
know
this
is
an
example
where
you
know
we're
by
not
having
that
we're
forcing
the
the
doctor
team
to
do
some
extra
work.
I
would
basically
say
you
know,
jump
into
that
issue
or
the
other
issue
that
I'm
gonna
open
up
paste
it
into
the
into
the
chat
right
now.
A
Yeah
I
think
I
like
basically
it's
like,
let's
computer,
that's
the
fundamental
thing
is
like
is:
is
the
trouble
worth
the
reward
if
docker
was
the
only
place,
but
I
definitely
know
that
other
people
have
complained
about
our
size
of
our
binaries.
Like
you
know,
there's
been
people
saying
it's
been
creeping
up.
What
I
don't
a
hundred
percent
no
weather
is
that
the
people
who
have
been
complaining
about
that
are
also
people
using
docker
or
whether
that
that's
a
you
know
a
bigger
set.