►
Description
A
B
If
you're
coming
to
the
no,
not
plus
the
is
interactive
conference
in
Vancouver
Vancouver
in
Montreal,
sorry
Montreal,
be
here,
please
remember
to
also
move
travel
for
the
collaborator
summit,
which
follows,
and
in
the
two
days
after
the
conference
we
are
all
the
projects
from
the
open.
Joyce
foundation
will
be
able
to
collaborate,
and
you
know,
share
sessions
and
be
a
fantastic
moment
for
our
community
to
be
part
of.
C
So
I'm
tracking
it
over
in
the
release,
repo
preparations
have
started.
We've
created
two
13
branches,
so
we're
just
following
the
guide
which
is
in
the
is
merged
into
note
Cornell.
So
as
part
of
the
release,
its
guide
we're
following
the
major
set
by
looks
of
it.
The
semver
major
cut
off
that
we
normally
do
would
be
around
the
22nd
of
September.
So
just
something
to
bear
in
mind
and
I've
started:
kicking
off
a
few
test
builds
etc.
So
that's
the
state
of
note
13
at
the
moment,
Thank.
A
D
I
had
trouble
finding
identification
yeah,
the
just
people
wanted
I.
Think
people
should
be
where
I
just
wanted
to
bring
it
to
people's
awareness.
It's
a
low
priority
issues
affecting
only
windows
got
a
CVO
blow,
fixing
it
as
backwards
in
people.
The
issue,
in
brief,
is
using
local
Ben,
SR
or
user
local
somewhere
in
slash
user.
D
Excuse
me,
somewhere
in
slash
user,
slash
local
is
read
for
configuration
by
open
SSL
by
default,
accepted
on
Windows.
That's
not
a
protected
location.
So
if
somebody
already
has
access
to
the
machine,
then
anybody
on
the
machine
can
put
the
data
there.
Changing
at
a
Nadex
is
obviously
backwards
incompatible.
There
is
a
very,
very
low
chance.
Some
of
you
can
actually
and
in
order
to
attack
you
need
to,
you
know,
have
access
to
the
machine,
so
she
can't
lose
recommendation
to
not
fix
it.
A
D
Yep,
so
just
just
a
reminder,
so
they
I
had
agenda,
so
the
security
releases
were
delayed.
They
didn't
happen
yesterday,
there's
some
sort
of
problems
with
open
SSL,
but
they
happened
early
this
morning,
shigeki
has
already
looked
at
the
at
the
at
the
issues
and
he
says
I:
don't
they
don't
apply,
except
for
one
possibly,
which
is
fourth
connection.
I,
don't
think
for
protection
act
applies
to
us
because
no
definitely
we
never
fork
and
then
continue
to
execute.
We
always
fork
an
exact
to
my
knowledge
of
disagrees.
D
I
should
speak
up,
so
we
think
that
quite
literally,
none
of
the
three
issues
affect
node
at
all.
So
it's
it.
The
open,
SSL
updates
firmly
within
and
non-security.
Just
it's
just
another
update
to
a
new
patch
releases,
openness.
So
and
again,
if
anybody
disagrees
now,
you
can
say
I'm
gonna
speak
up
and
comment
in
the.
D
C
A
B
B
The
reason
here
that
what
the
point
of
the
discussion
is
to
introduce
a
behavior
similar
to
the
one
in
Python,
where
you
eat
clean
and
ctrl
C
on
a
note
program,
it
will
play
the
star
trace
of
what
is
currently
doing,
and
this
is
pon
a
little
bit
of
you
know,
discussion
on,
if
we
want
it
to
be,
octane
opt
out.
If
we
wanted
to
print
it
only
theories
actually
Java
Script
code
running.
B
Worthless
if
there
was
nothing
running
and
if
you
should,
we
should
think
a
message
at
all,
so
I
just
wanted
to
bring
the
attention
to
this
PR
because
it's
going
back
and
forth
the
different
implementation
happening
at
the
same
time.
So
it's
probably
better.
If,
if
we
take
a
look
because
it
will
change
our
behavior
significantly
so,
and
the
user
experience
of
note
significantly
so
is
something
that
we
should
really
make
some
decision
on
ourselves
and
try
it
out
and
see
how
that
look
like.
E
Generally
I'm
in
favor
of
any
additional
options
that
increase
improve
the
leaking
experience,
but,
in
this
case
I'm
not
really
finding
the
point
of
printing
the
stack,
trace
and
control
see
because
at
the
time
when
the
controls
he
is
pressed,
the
program
would
be
at
some
arbitrary
points
and
what
value
it
is.
Providing
I
am
not
really
clear
on
that.
D
D
I
noticed
Ben's
comment
that
Python
developers
are
don't
seem
to
mind
it,
which
is
interesting
when
I
press
control
C,
it's
usually
because
I've
decided
I
just
want.
You
know
to
go
away
and
stop
not
because
I'm
interested
in
a
stack,
trace
or
think
that
it
has
a
bug.
I
mean
if
I
it's
busy,
looping
I
might
yeah
and
it's
a
server
I
might
kill
it
another
console,
but
that
will
send
segments
I,
don't
know
really
strong
feelings,
but
I'm
a
little.
D
G
I
tried
the
the
branch
before
and
he
had
some
issues
that
the
current
condition
has
some
issues.
One
is
that
there
is
some
sort
of
implicit
constraint
in
the
direct
callback
which
makes
executing
JavaScript
in
an
interrupt
a
little
bit
unreliable,
which
is
what
does
Piratas.
G
G
H
H
G
G
H
If
you
make
an
experimental
within
behind
that
with
the
flag
and
then
actually
evolve
it
once
for
sure,
once
we
did
it,
if
it's
not
disruptive
or
clear
able
to
pull
all
these
issues
over
time,
then
we
can.
You
know
we
can
make
a
decision
to
go
ahead
and
flip
it,
so
that
that's
always
on
right
and
then
we
can
flag
it.
Not
that.
A
That
was
in
the
issue
the
last
time.
I
looked.
That
was
one
of
the
suggestions
that
like
I,
died
out
it
in,
like
nobody's
actually
said,
could
we
make
it
you
know
on
by
default,
but
with
a
knocked
out,
the
next
suggestion
was
like.
Well,
maybe
we
should
make
it
opt,
opt
in
and
then
consider
switching
it
at
a
major
to
be
on
by
default,
mm-hmm
and
I
think
that's
that's
sort
of
along
the
lines
of
what
yours
justing
is
like.
Yeah,
let's
make
it
experimental.
You
have
talked
in
once.
A
B
It's
very
broken
down
and
within
different.
Everybody
is
some
different
opinion
in
there.
So
that's
why
I
was
calling
for
TSC
attention,
because
this
is
somehow
like
to
some
extent.
We
we
should
make
a
single
statement
to
the
contributor
essentially
saying
this
is
where
we
want
it
to
go
right.
Maybe
maybe.
A
I
B
You
tagged
it
I'm
good,
either
way.
Okay,
this
is
going
to
land
like
without
us,
making
a
statement
on
it
right:
okay,
let's
just
leave
it
on
then
or,
but
if
you
want
to
remove
it,
remove
it
feel
free.
The
way
the
discussion
is
gone,
it
seems
something
that
we
should
decide
like.
It's
so
relevant,
it's
so
important
for
the
user.
Experience
of
not
the
ass
that
I
think
I
feel
it's
something
that
we
should
be
deciding.
What
is
easy
for
the
different
behavior,
okay.
A
B
F
I
I'm
good
I'm
good
in
landing.
It
is
okay.
If
you
could
make.
Oh
you,
okay,
you
did
make
your
provokes,
plus
it
great,
so
yeah
I
mean
Luigi,
you
know
is,
is
against
it
and
you
know
it
does
seem
again.
It
does
seem,
like
you
know,
a
full
and
complete
discussion
has
been
had
you
know,
but
you
know
the
arguments
for
and
against
have
been
made
and-
and
it
does
seem
like
this
is
blocked
without
a
vote,
so
it's
either
close
it
or
vote
on
it.
B
H
It
is
a
sin
for
maybe
so
it
does
require
yeah.
No,
no,
that's
not
off
yet
I'm
I'm,
looking
at
it
right
now
again
and
I
just
want
this.
The
only
change
here
is
that,
after
the
close
event
is
admitted,
no
other
events
will
be
committed
right.
So
if
error
comes
before
close
after
that,
error
won't
be
even
in
England
yeah
I'm
wondering
if,
if
a
statement
shouldn't
be
added
to
the
documentation
on
that.
H
A
I
B
H
A
A
I
I
think
that
one
we're
asking
for
we
can
check
next
week
if
we've
got
enough.
Psc
members
haven't
responded
to
tails
question
and
if
yes
take
it
off,
if
no,
then
it's
a
reminder
for
us
great
okay.
So
moving
on
to
the
next
one,
which
is
25
1789
ongoing
list
of
actions
for
Python
3
compatibility,
close
I
couldn't
make
it
today,
but
he
did
give
a
fairly
comprehensive
update
there
I.
You
know
he
raised
the
good
news
that
are
the
tree.
A
A
You
know
he's
suggesting
to
2587
should
be
reviewed
and
landed.
So
if
people
have
time
to
take
a
look,
that'd
be
good.
No
Jim
1844
needs
to
be
fixed
to
pass
the
tests
and
then
needs
to
be
reviewed
and
landed,
is
sort
of
the
two
of
the
higher
priority.
Things
and
they're
still
helped
needed
on
29
3
26
and
29
415
as
two
other
higher
party
ones,
he'd
like
to
call
out,
and
we've
got
112
days
to
python,
to
end
of
life.
I
C
I
Saying
it
just
in
case
there's
any
I,
don't
see
any
reason
why
it
shouldn't
land
and
I
just
but
it's
been
open
a
while
and
it
looks
good,
but
just
in
case
somebody
else
has
a
reservation.
I'll
wait
a
few
minutes.
If
anybody
wants
to
look
at
it
and
I'll
post
a
link
in
the
chat,
so
you
don't
have
to
type
it
in
I'm.
Talking
about
this
thing,
I
will
land
it
in
about
five
minutes.
Unless
somebody
text
me
here
and
stops
me
set.
A
A
I
F
H
H
You
know
his
latest
comment
there:
it's
not
even
theoretically
correct
and
I'm
reading
more
towards
that
I'd
have
to
go
back
into
it
in
detail
again.
So
it's
been,
you
know,
I
only
looked
at
it
right
after
it
opened,
but
might
that
was
my
initial
take
on
it
as
well,
that
I
don't
believe
the
change
actually
aside
from
unrelated
changes
and
I
I'm
leaning,
one
I
did
sign
off
on
it,
but
then
I
lose
looking
at
it
again.
J
H
Yeah
I'm
definitely
not
saying
that
a
change
should
not
be
made
here.
I.
Just
don't
think
this
changes
the
one
it's
correct,
so
yeah,
it
looks
like
you
know,
and
it's
always
still
kind
of
working
through
it
with
Robert.
So
I
just
don't
think
if
there's
I
don't
think
it's
anything
weak
right
here.
We
just
should
just
continue
letting
it
work
through
the
process.
A
Not
okay,
let's
move
on
to
the
ones
tagged
under
no
GST
SC.
The
first
one
is
next
week's
meeting
conflicts
with
modules
team
meeting
number
748.
We
had
worked
around
that
by
just
moving
the
you
know,
switching
one
week
time
with
the
other
week,
so
maintaining
the
different
time
slots
that
we
have,
which
is
not
having
them
in
the
same
order.
It
does
sound
from
chakra,
though,
that
the
current
spreadsheet
shows
that
we
should
just
update
it
to
being
an
hour
later.
I
So
the
times
are
gonna
change
according
to
chakra,
the
times
are
gonna
change.
When,
when,
when
you
know
you
know,
we
anticipate
Beth
and
Tobias
being
added
to
the
TSC
before
long
and
when
that
happens,
the
times
are
gonna
change
anyway.
So
I
wonder
if,
like
we
should
just
kick
this
down
the
road
another
week
unless
it,
unless
it's
referring
to
actually
next
week's
meeting,
is
it
actually
next
week's
meeting
or
was
this
sub
meeting
I?
Don't.
A
I
mean
this.
His
last
comment
was:
is
that
even
the
current
spreadsheet
just
says
we
should
just
change
it
to
be
an
hour
later.
That
would
be
a
pretty
change.
Oh
yeah
I'm
on
board.
So
I'm,
like
you
know,
I
can
easily
just
drag
in
an
hour
later.
Unless
there's
any
objections
and
that's
kind
of
what
I
was
gonna
suggest,
we
do
plus
one.
A
Okay,
Mike
I'm,
just
gonna,
say
Michael,
we'll
update
the
calendar
entry
and
then,
if
you
know,
if
we
have
to
change
it
again
as
we
bring
people
on
we'll
do
that,
but
that
seems
like
a
simple,
straightforward
fix:
let's
just
do
it.
Okay,
the
next
two
issues
are
nominating
Tobias
and
Bethany,
as
we
believe
the
you
know
our
standard
practice
of
inviting
them
to
a
number
of
TC
meetings.
You
know
we've
done
that
haven't
heard
any
complaints
or
objectives
objections.
A
We
have,
let's
see
one
two,
three,
four,
five,
six,
seven,
eight
nine.
We
have
nine
people
here.
So
it's
not
quite
enough,
for
you
know
a
vote,
which
is
what
our
Charter
requires.
So
our
our
plan
that
we
discussed
a
little
bit
before
the
meeting
started
was
to
make
sure
we
don't
have
any
objections
for
the
people
who
are
present.
A
If
not,
then
we
will
assume
that
the
the
people
who
are
here
of
a
voted
plus
one
and
then
we'll
go
back
to
you-
know
put
that
into
the
original
issues
that
were
open
with
their
nominations.
We'll
also
make
a
comment
stating
that
you
know
for
people
who
who've
already
plussed
one
in
that
original
issue
will
consider
that
a
plus
one
vote
unless
they
object
by
the
end
of
the
week
and
ask
anybody
who
you
know
isn't
covered
by
those
two
to
comment
to
vote.
A
Okay,
we'll
take
silences
consensus
for
those
who
are
here.
That's
the
way,
we'll
proceed
all
out
in
a
few
notes,
a
few
minutes
and
minutes
and
post
those
comments.
Anisha.
The
next
issue,
then,
to
move
on
to
is
under
no
GS
/
admin.
It's
the
moderation
team,
recertification
number
408.
I
I
I
would
love
to
see
them
self
nominate
and
if
anybody
has
people
that
want
to
nominate,
please
do
I
used
to
be
a
member
of
the
moderation
team
and
when
I
left
it
was,
it
was
to
take
a
hiatus.
So
I
might
self
nominate
to
get
back
on,
but
I
might
want
this
hiatus
to
go
another
year.
I,
don't
know
we'll
see.
So
that's
all
I
got
okay.
A
I
Yeah
I
mean
I,
think
I
actually
started
to
do
it
already
in
a
in
an
issue
but
I'll
I'll
yeah
I'll
find
it
and
I'll
email
people
and
I'll
try
to
get
more
active
in
that
yeah
yeah.
A
If
you
just
say,
like
you
know,
here's
the
people
that
are
active,
you
know
and
here's
people
aren't-
are
active.
Let's
research,
the
active
people
I
think
that
would
be
enough
for
us
to
all
just
say,
plus
one
and
close
that
out
once
you
once
you
get
a
good
handle
on
that,
because
I
understand.
That's
work,
though
any
other
comments,
discussions
on
that
one,
okay,.
B
You
see
CPC
is
progressing
doing
doing
his
job.
It's
I
was
just
about
to
drop
the
cold,
so
I'll
keep
these
embarrassed,
embarrassing
short,
so
see
he
is
doing
his
job,
essentially
going
to
standardize
the
values,
project,
criterias,
protein
champions
and
and
so
on,
and
so
forth
that
are
critical
for
onboarding
new
projects.
There
are
a
few
new
projects
being
being
imported
with
with
Alan's
approach
that
are
applying,
so
those
are
kind
of
big,
problematic,
big
thing
that
needs
to
be
taken
care
of
by
the
CPC
and
in
fairness.
B
A
One
thing
I
might
add
is
that
there
is
work
on
the
proposal
too,
for
the
code
of
conduct
handling
shouldn't
really
be
anything
new
there,
because
the
proposal
already
included
the
sort
of
the
approach,
but
this
is
a
how
we'll
handle
the
reporting
internally.
So,
but
if
you're
interested
in
that
side
of
things,
that's
worth
taking
a
look
at
there's
also
been
just
as
a
reminder.
The
you
know,
the
a
few
of
the
repos
are
moving
up
to
the
open
J's
from
the
node
repo
and
we've
seen
that
happen
for
the
summit.
A
Repo
and
there's
there's
a
discussion
of
doing
this
similar
thing
for
the
the
part
of
the
user
feedback
that
was
supporting
user
surveys.
So
just
again,
if
he's,
if
you
see
that
happening
shouldn't
be
a
surprise,
because
you
know
the
that's
been
raised
and
discussed,
but
it's
actually
taking
place
on
the
board
side.
I,
don't
think,
there's
anything
new,
but
what
I'm
gonna
do
is
just
flip
over
right
to
second
to
see,
if
there's
anything
in
the
admin
which
is
active
or
been
added
recently,
I,
don't
think
there
will
be,
though,.
A
F
H
Yep,
so
just
ongoing
progress
so
just
a
little
bit
because
the
some
of
the
underlying
8,000
ng
TCP,
which
is
still
a
work
in
progress
as
the
API,
has
changed
and
completely
broke
everything
I.
A
lot
of
us
have
either
it's
the
the
fun
of
working
against
the
moving
target,
so
we're
working
on
getting
TLS,
handshake
working
again
and
then
we'll
go
from
there.
I
am
in
progress
of
preparing
a
initial
PR
or
to
move
development
into
the
main
repo.
H
It
puts
quick
behind
a
configure
flag,
so
just
building
by
default
will
not
be
that
been
able
a
flag
to
build
it
and
still
be
very,
very
experimental
still
so
once
I
get
to
the
implementation
working
again
and
clear
out
a
few
other
line
items
then,
and
hopefully
that'll
be
by
the
end
of
September
I'll.
Have
that
PR
open,
ok,.
D
I
I
F
A
I
But
I
mean
by
me
the
whole
the
whole.
The
whole
act
of
asking
is
itself
fraught
with
controversy
like
there,
you
know
there
there
are.
There
are
people
like
like
like
rods,
yeah,
well,
who
you
know
absolutely
see
you
know
it
make
me.
You
know
you
know
very
reasonable
arguments
that
that
that
is,
that
would
be
a
step
backwards
in
a
lot
of
ways
right.
A
A
I
Yeah
I
mean
certainly
and
I
mean
you
know,
I'm,
not
gonna,
do
it
here,
but
we
could.
Even
you
know,
name
names
as
to
like
you
know,
you
know,
I
mean
I
mean
you
know,
they're
they're
certain.
There
are
certainly
companies
that
are
that
are
that
are
putting
a
lot
more
into
built
than
other
companies.
And
that's
that's.
You
know,
and
that's
that's
the
way
it's
going
to
be
no
matter
what,
but
but
yeah
it.
Certainly
some
targeted
help
from
some
specific
companies
would
be
would
be
hugely
useful.
To
note
it's.