►
Description
B
D
D
A
I
saw
also
related
to
the
rate
at
least
nine
point:
X
release
the
release
working
groups
gonna
be
discussing
creating
a
more
more
scheduled
release,
Lang
for
for
the
current
release
line,
okay.
B
Okay,
if
not
we'll
move
on
to
the
agenda
based
on
the
items
extracted
from
the
repos,
the
first
one
on
that
list
is
the
membership
initiative
is
ramping
up.
I
added
that
to
the
agenda,
and
you
know
mostly
I-
want
to
make
sure
that
everybody
was
aware,
because
this
is
being
pursued
under
the
community
committee
team.
But
you
know,
is
basically
intended
to
apply
to
mentorship
across
the
organization.
So
they'll
be
looking
for
people
to
be
involved
from
the
different,
the
different
groups
to
help
mentor
in
different
ways.
B
D
D
This
is
not
a
working
group
under
this
under
the
TFC
is
something
happening
in
the
community
me
Jesse
just
largely
needs
to
be
aware
of
it
as
one
of
these
one
of
the
goals
of
this
advisory
group
is
to
look
at
things
that
are
happening
in
core
provide
feedback,
and
you
know
whatever
form
necessary.
You
know
that
TS
he
can
go
to
this
group
and
say
hey,
you
know
what
do
you
think
of
this
sort
of
the
TS?
Or
this
group
and
saying
you
know
hey?
D
I
mean
that
the
whole
point
of
the
group
is
to
bring
together
representatives
from
companies
that
have
adopted
notes,
but
are
not
currently
active
contributors
to
know.
So
you
know,
Netflix
is
one
of
the
participants,
for
instance,
where
they
have
made
significant
investments
in
using
node,
but
don't
actively
go
out
and
contribute.
D
Whether
or
not
the
feedback
detected
on
is
a
CSC,
the
the
the
idea
is
for
TSE
members
to
participate
as
observers,
basically
literally,
and
it
you
know
in
Britain
to
bring
that
that
feedback
back
to
the
GSM,
so
I'm
going
to
be
participating
as
an
observer.
Only
you
know
in
any
of
your
welcome
welcome
workers
with
just
paste
that
way
as
well.
So
it's
a
very
least
has
this
as
a
feedback
is
being
generated
by
this
group.
I
will
be
bringing
that
back
to
this
group.
F
Okay,
I
I
looked
at
the
notes
and
I'm
wondering
if
we
should
make
it
any
more
clear
that
there
isn't
that
at
least
at
this
point
is
basically
no
commitment
from
the
TSE
site,
because
I
saw
a
bunch
of
responsibilities
for
the
members
and
if
I
were
a
member
and
have
responsibilities,
I'd
kind
of
expect
that
the
other
side
has
responsibilities
too.
But
I
didn't
see
those
in
the
notes
or
a
charter.
We.
D
Could
make
it
clearer
there
in
the
trigger
and
I
know
that,
as
we
have
been
dropping
this
group,
we
have
made
that
clear
a
number
of
times
and
at
the
various
participants
of
this
group
know
that
that
this
is
a
feedback
channel.
It's
not
in
you
know,
hey,
that's
you
see,
must
do
this.
The
funding
oversight,
group
and
that's
that's-
that
is
well
understood
by
the
folks
that
are
participating
at
this
one.
I.
C
Have
concerns
that
this
ends
there's
a
real
focus
on
feedback
to
the
TSC
and
I
think
that,
on
multiple
levels,
the
way
this
whole
thing
is
unfolded
has
sent
a
lot
of
wrong
signals
about
the
way
the
the
project
is
governed
on
the
technical
side
and
about
project
stewardship.
The
TSE
doesn't
make
most
of
the
decisions,
and
things
like
that
and
and
I
think
also
a
lot
of
people
on
the
TSC
were
kind
of
surprised.
C
A
I
think
the
TLD
others
just
like
not
like
some
of
the
members
that
are
there
already
might
understand
these
things,
but
if
anyone
else
wants
that
comes
to
it,
I
just
think
you
know:
I
haven't
double-checked.
If
it
is
this,
is
this
clear
or
not?
But
you
know,
maybe
it
is
already,
but
it
should
just
probably
be
made
extra
clear
that
you
know
we
can.
We
can
take
feedback,
but
you
know
it's
hard
to
act
on
feedback
alone,
because
we're
we're
all
very
busy,
and
so
it's
hard
to
commit
to
anything.
Yeah
yeah.
D
It's
rigorous
today,
you
know
it's
a.
It
is
purely
a
channel
for
these
enterprises
to
be
able
to
say
hey.
These
are
the
things
that
were
our
priories
for
us
with
regards
to
succour,
so
an
example
would
be
you
know,
hey.
We
just
should
not
be
a
surprise
to
anyone
else.
All
right.
It's
something
to
commend
people
been
saying
for
a
long
time.
That's
one
of
the
things
that
they
say
hey.
You
know
we
really
want
you
to
focus
on
better
diagnostic
stuff
right
and
it
gives
us
a
channel
to
say
okay.
D
D
Yeah,
you
know
it's,
you
know.
Obviously
there
is
no
obligation
for
any
of
us.
Did
you
have
any
other
stuff?
But
you
know
listening
to.
Users
is
a
good
time.
A
D
G
D
H
D
Calm,
you
know
what
the
format
would
do.
That
would
all
to
be.
It's
still.
Something
would
need
to
be
worked
out.
So
what
is
the
best
way
for
them
to
actually
go
about?
Collecting
feedback
is
something
with
these
and
this
initiative
in
a
spirit
we
need
to
work
out
for
themselves
right
and
if
we
have
ideas
like
hey,
what
would
be
most
valuable
to
us,
we
can
provide
that
input.
D
A
D
B
The
discussion
I
had
with
then
because
I
asked
that
specific
question
so
that
we
could,
you
know,
try
and
position
things
to
avoid
confusion
was
that
you
know
the
enterprise
advisory
group
would
be
a
group
of
companies
who
have
large
installations
of
nodejs
and
are
there
and
willing
to
you
know,
use
those
installations
to
help
us
validate
or
test
out
things
like
you
know.
If,
if
we're
concerned
about,
you
know,
break
potentially
breaking
changes
that
are
being
being
made
in
a
release,
they
can
use
their
large
installations
to
help.
B
You
know
validate
that
it's
not
gonna
break
things,
give
us
feedback
from
the
perspective
of
people
running
those
large
installations,
and
let
that
group
you
know
the
membership
as
I
understood
it
would
be
sort
of
restricted
to
people
who
have
enough
of
a
implement
eight
of
an
installation
and
sort
of
production,
node
system
that
they
can
provide
that
level
of
feedback,
because
they
have
you
know,
and
only
they
can
do
that
because
they
have.
That
actual.
B
So
it's
it's.
If
I
can
draw
one
distinction
it
between
those
two
in
terms
of
the
kind
of
feedback
that
we
would
look
to
get
it
may
overlap.
It
also
sounds
like
you
know:
the
enterprise
one
was
set
up
a
bit
more,
so
that
those
companies
would
be
self-organizing
running.
You
know
the
the
goals
that
they'll
sort
of
run
it
on
their
own.
The
end
user
feedback
group
is
something
where
you
know.
B
We're
being
you
know
us
in
the
user
and
use
your
feedback
group
are
being
a
bit
more
proactive
in
terms
of
like
reaching
out
to
find
people
will
be
scheduling
a
meeting
to
get
people
together.
Thinking
about
the
kinds
of
questions
that
we
should
be
asking
them
and
those
kinds
of
things
that
helps
to
make
the
you
know,
at
least
in
my
mind
what
the
difference
can
be
and
explain
going
forward.
B
F
F
D
Yeah
we
can
and
evolve
the
wording
so
that
there's
less
of
an
emphasis
there,
but
part
of
the
whole
point
is
for
this
trip
to
be
able
to
say
you
know
these
are
our
priorities
and
things
that
we
think
that
the
technical
project
should
be
paying
attention
to,
or
these
are
the
you
know.
These
are
our
thoughts.
What
that
technical
project
is
doing
CSC
is
integral
leadership
for
the
project.
F
D
Assuming
it's
because
the
visibility
into
how
the
technical
bunch
of
destruction
these
are
contributors,
they
don't
necessarily
know
we're
the
right
places.
That
is
so
they
might
say,
hey.
We
need
better
diagnostic
school
TAC
can
come
back
and
say:
hey
diagnostic
groups,
you
know,
are
you?
We
have
a
large
group
of
users
that
are
saying
that
this
is
important
to
us,
but.
G
B
D
B
I
guess
I
take
a
poll
of
you
know.
Maybe
you
know
who'd
be
interested
if
we
did
set
up
a
meeting.
You
know
where
people
you
know.
Is
there
enough
people
who
think
that's
useful
versus
non
useful
and
happy
to
set
one
up?
If
that's
people
think
it's
interesting,
but
I
don't
want
to
if
people
want
to
just
handle
it
through
github.
D
D
B
You,
if
not
okay,
let's
move
on
the
next
one,
is
4:23.
It's
a
tracking
issue
for
the
strategic
initiatives,
and
so
just
the
idea
is
to
get
an
update
on
each
of
those
in
terms
of
any
PI.
We
did
have
a
good
discussion
last
week
and
we
want
to
make
sure
everybody's
aware
that
we're
making
good
progress,
we
believe
on
satisfying
the
criteria
to
exit
experimental
status.
B
One
of
the
the
members
you
know
was
reaching
out
to
the
maintainer
made
some
suggestions,
the
maintainers.
You
know
suggested
some
other
things
and
we're
kind
of
working
through
those,
so
I
think
you
know
we're
hopeful
that
we're
within
you
know
maybe
I'll
take
a
guess
at
like
a
month
of
having
satisfied
the
criterion
being
able
to
exit
experimental.
D
B
So
I
mean
that's
the
timeframe
we'd
like
to
exit
I'd
like
to
I,
think
we'd
like
to
see.
If
we
could
then
bat,
you
know
at
least
have
it
go
back
to
eight,
if
not
six
in
terms
of
back
boards,
but
I
think
you
know
we
want
to
exit
and
then
start
that
discussion.
D
B
D
Okay,
yeah,
just
if
you
would
just
keep
you
in
the
loop
just
on
what
your
expected
timing.
So
as
we
go
through
the
message
in
percent
I'm
planning
on
that.
H
B
H
One
note
Michael
I
would
you
should
also
check
these
other
module
called
pre-built
pre-built,
which
is
as
some
interesting
download
numbers
as
well
for
doing
the
edits?
What
level
down
uses
for
doing
the
previous
stuff?
It's
I
prefer
personally,
prefer
it
to
note
Prickett,
so
it
should
be
soup
that
should
support
the
that
stuff
as
well.
Yeah.
B
I
think
you
know
a
lot
of
that
to
the
list.
We're
figuring
out
the
story
for
no
pre
trip
and
no
pre
build
I
I
think
we're
hoping
that
that
doesn't
have
to
be
a
blocker
for
experimental
in
terms
of
having
it
completely
worked
out
or
implemented.
But
you
know
we
won't
understand.
Node
pre
chip
to
understand,
make
sure
it
makes
sense
like
there's
nothing
that
doesn't
make
sense,
because
we
don't
think
that
that
part
is
gonna
affect
the
API
is
necessarily
right.
H
H
E
C
G
C
C
To
find
out
what
I
missed
and
I'm
being
messaged
right
now,
actually
somebody
save
this
is
important.
Oh
yeah,
we
did
hear
back
and
it
was
also
blank.
So
we've
gotten
I'm,
just
gonna
change
that
to
say:
we've
been
getting
some
blank
email
messages,
but
not
worried
about
it,
and
that's
it
thanks.
Okay,.
B
Okay,
that's
the
ones
that
were
they
know.
People
have
put
some
updates
in.
Does
anybody
have
anything?
They
want
to
say
anything
new
on,
like
HTTP
James,
to
be
too
high.
H
D
Going
to
say,
the
hb2
is,
there's
been
some
significant
updates
here
recently,
just
kind
of
hardening
the
implementation
and
working
towards
getting
it
right
to
come
out
of
experimental.
My
goal
is
to
have
it
out
of
experimental
by
tenth
and
one
of
the
key
things
that
we
need.
There
is
for
people
to
you,
know
people
you
know
kicking
the
tires
on
it
and
and
testing
it
out.
So
if
you
have
any
any
projects
that
you
can
kind
of
surly
hb2
implementation
net
and
see
what
works
any
feedback
that
would
gobble.
D
H
Was
dreams
so
I
I,
blended,
Myra,
factoring
of
the
of
the
breathable
module
fixing
an
issue
in
the
3000
mark,
long-standing
issue
about
old
streams?
If
we
call
it
all
streams,
note
streams,
whatever
you
want
to
call
them,
which
was
pretty
significant
because
it
was
calling
what
data
creating
an
endless
loop
situation.
If
you
called
push
in
a
synchronous
fashion,
multiple
push
in
a
synchronous
fashion
and
they
simplified
some
user
to
encode
in
doing
so
so
I
I
did
that
and
that's
landed.
You
can,
if
you
can.
H
G
A
2-1
at
the
moment
on
modules,
one
of
the
things
that's
being
looked
into
right
now
is
like
the
module
specifier
and
how
the
resolution
and
the
module
specifier
is
happening.
I'm
doing
some
research
around
that
we
had
dynamic
import
land
onto
a
master
and
so
with
six
point
five
with
six
point:
four:
we
get
access
to
that.
There's
pull
request
open
to
back
port
that
to
nine,
but
we
need
to
do
a
little
bit
of
work
to
make
sure
that
it
is
a
bi
compatible.
G
I'll
likely
have
a
more
in-depth
update
next
week,
also
on
the
TSC
governance,
been
still
thinking
a
bit
about
this
over
the
break
and
hoping
now
that
we're
kind
of
like
back
and
rejuvenated
to
kick.
This
back
off
specifically
focused
around
improving
ways
for
individual
contributors
to
have
growth
within
the
project.
B
I'm,
just
looking
through
the
list
use
each
modules
and
API
OpenSSL
evolution.
Rod
mentioned
that
he
could
make
the
meeting,
but
he
is
planning
to
to
make
a
push
on
that
possibly
schedule
some
meetings
to
discuss
the
OpenSSL
situation.
I
believe
he
did
reach
out
to
the
OpenSSL
team
as
there
was
a
comment
I
believe
from
one
of
them,
but
it
didn't
really
provide
100%
clarity,
so
we're
still
gonna
have
to
dig
in
dot
into
that
to
figure
out
what
our
passport
is.
H
I
Yeah
right
now,
there's
nothing
happening
there
when
I'm
done
with
the
stuff
that
I'm
currently
doing
for
the
C++
screams.
I
might
just
like
try
to
open
my
APR
against
node
with
that
Timothy
Google,
also
like
expressed
in
christen.
That's
like
it's
not
gonna
happen
within
the
next
few
weeks.
Probably.
E
Okay,
I
didn't.
B
D
It's
still
progressing.
We've
made
more
progress
on
converting
more
of
the
error
messages,
I
believe
almost
all,
if
not
all,
of
the
ones
and
JavaScript
land
or
taken
care
of
it's
just
a
matter
of
getting
through
all
of
the
ones
that
are
in
C++
now
and
there's
quite
a
few.
Just
a
crypto
module
node
crypto
alone
has
several
hundred
that
need
to
be
converted.
B
D
D
The
yeah
we
have
a
calm
in
the
way
that
I've
been
approaching.
It
is,
you
know,
taking
the
valid
the
input,
validation,
errors
first
and
we
limit
up
the
JavaScript.
So
anything
that
is
basically
a
type
error
on
an
invalid
Auto
type,
moving
those
checks
out
to
to
JavaScript,
so
we
at
least
reduce
the
number
of
errors
that
were
throwing
from
Masika
filter
and
then
handling
there
is
you
know
in
any
any
areas
that
are
thrown
as
operational
errors
as
part
of
the
processing
to
you
know
and
doing
them
separately.
D
B
D
D
These
error
changes
the
needle
and
I
made
some
changes
before
the
Christmas
break.
There
is
another,
so
middle
PR
that
she'd
be
landing
like
any
any
any
time.
Now
that
does
some
of
the
input
validation
moves
from
some
utility
functions.
I
wanted
to
reduce
the
churn
in
the
PR,
so
I
decided
to
wait
until
those
things
weigh
in
and
then
I'm
going
to
be
iterating
again
on
the
on
the
SS
premises,
young,
with
the
intent
of
taking
and
taking
the
in
progress
label
off
with
MINIX
week.
Okay,.
D
After
that,
I
know
that
Matteo
has
been
working
on
the
eating
a
some
Gators
for
streams
that
PR
should
be
landing
soon,
hopefully,
and
then
there's
some
additional
work.
When
you
would,
we
just
need
to
do
in
terms
of
this
kind
of
making
async
iterators
more
efficient
and
figuring
out
how
we're
gonna
work.
The
other
modules,
if
and
if
we're
gonna
get
a
model,
see
spreads.
B
B
B
I
B
I
I
that
one
I
actually
have
a
branch.
My
only
reason
I
haven't
opened.
The
PR
is
that
one
of
the
tests
is
failing,
so
I
I
basically
used
the
pattern
that
for
the
tests
that
were
in
the
non
and
API
like
the
core
callback
scope,
I,
have
it
all
everything
working,
but
one
test.
It's
not
reporting
the
right,
async,
IDs
and
I
haven't
had
a
chance
to
get
back
to
figure
that
one
out
you.
B
I
B
And-
and
so
I
was
just
mentioning
on
the
demand
front-
that
there's
I
think
we
need
to
do
some
similar
work
there,
but
the
difficulty
is
finding
somebody
who
has
time
or
inclination
to
do
that.
So
that
is
something
that
I
would
call
it
to
the
TSC.
If,
if
you
have
time
or
know
somebody
who
might
that
would
be
one
way
that
we
could
help
one
on
that
front,
I
think.
E
B
B
G
Yeah,
so
we
have
this
sorry,
one
second
I'm
getting
a
cough.
This
issue
that
we
open
talked
about.
Overall,
like
expectations
and
accountability.
We
got
somewhere
with
what
we
added
to
the
Manrique.
Oh
there's,
a
great
document
in
there
around
accountability
for
leadership,
I
think
that
was
a
really
great
start,
a
few
of
the
things
that
we
still
need
to
get
going
on.
This,
though,
are.
G
G
Important
to
start
putting
together
some
thoughts
of
around
the
process
for
that,
and
maybe
we
should
be
spinning
up
that-
can
maybe
be
part
of
the
governance
group
work
that
I
was
talking
about
earlier.
So
part
of
this
is
on
that
side
regarding
they,
like
moderation,
accountability.
The
other
side
of
it
is
the
values
Docs.
So
we've
now
run
a
handful
of
value
sessions.
There
were
definitely
some
things
that
came
up
as
like
consistent
between
them.
G
I
think
that
we
need
to
make
it
a
session,
a
decision
if
we're
going
to
continue
moving
forward
the
work
on
that,
if
we're
ready
to
start
drafting
some
stuff
and
if
we
are
going
to
start
drafting
some
stuff,
what
the
expectations
are
from
the
group
on
it,
so
I
guess
I
can
just
leave
it
to
the
floor.
Based
on
that,
but
I
think
at
a
high
level.
The
governance
meeting
that
I
was
talking
about
spinning
up
would
likely
cover
that
and
the
things
that
we're
talking
about
here.
G
But
if
anyone
you
know
either
a
feels
like
I've
missed
anything
that
we
definitely
need
to
be
thinking
about.
It
really
like
to
hear,
or
on
the
flip
side,
people
are
feeling
content
about
where
we're
at
I
think
that
you
know
we
don't
need
to
do
much
more
work,
I'm
interested
in
hearing
that
as
well.
B
You
I
think
in
my
mind,
like
you
know,
we've
talked
about
setting
up
the
governments
meeting
in
it
and
sounds
like
you're
saying
that's
a
good
place
to
cover
these
issues.
I,
certainly
echo
that
and
I'm
wondering
if,
like
you
know,
we
should
take
the
TSC
agenda
off
this
issue
and
wait
until
that
meetings
held
and
there's
any
more
specific
feedback
or
questions
to
the
TSC.
G
Okay,
well,
it
seems
like
a
good
start,
I'll
make
sure
to
add
the
whole
committee,
but
I'll
take
something
off
this.
We
can
get
the
other
doodle,
and
so
we
can
pick
a
time.
One
thing
I
would
like
to
say
that
everyone
is
like
I
would
like
to
spin
this
off,
as
maybe
a
recurring
bi-weekly
meeting
when
we
start
just
so,
we
can
pick
a
time
that
everyone
can
commit
to.
G
So
I'll
follow
up
on
that
later
this
week,.
B
B
H
C
Added
that
change
so
so
so
current
practice
now
is
TSE
members
are
or
gona's
and
nobody
else's.
You
added
a
change
to
the
pull
request.
You
know
you
with
with
my
blessing
to
to
add
in
the
calm,
calm
chair
or
you
know,
in
the
current
state
of
affairs,
where
there's
two
chairs.
Obviously
we
would
be
both
chairs.
I
think
it's
fair
to
say
that
if
anybody
actually
objects
to
that,
they
should
make
it
known
in
the
pull
request.
C
B
G
D
B
Okay,
does
anybody
else
who's
who's
on
the
call
I?
Guess
it's
it's
the
because
that
is
a
blocker
and
fairly
important
for
the
moderation
team.
So
I
think
that
would
be
sort
of
the
next
step.
Is
that
likely
the
doc
would
be
updated
to
say
that
in
addition
to
you
know
the
TSC
members
and
the
kumkum
chair,
the
moderation
team
would
also
be
Oregon
nurse,
and
so,
if,
if
you
do
have
opposition
or
concerns
with
that,
I
think
it'd
be
good
to
start
chiming
in
on.
In
that
issue,
number
33
what.
C
E
B
I
think
that's
an
important
discussion
that
we
need
to
actually
move
forward
it
at
a
you
know
at
a
reasonable
pace,
because
it's
you
know
the
moderation
team
has
has
raised
the
point
that
it's
it's
it.
It
affects
their
day-to-day
ability
to
do
their
job,
and
you
know
my
I
think.
The
thing
we've
done
well
in
the
past
is
making
sure
that
people
who
have
access
people
get
the
access
they
need
to
do
their
job,
and
this
is
a
case
where
we're
clearly
not
meeting
that.
So
you
know
dive
into
the
discussion
there.
B
C
And
I
think
the
likely
end
result
of
this
is
going
to
be
moderation.
Team
gets
ownership
privileges,
but
there's
you
know
documented
that
the
TSC
and
you
know,
or
whatever
is
the
actual
you
know
authority
over.
You
know
how
you
know
has
actual
final
authority
over
decisions
or
something
along.
Those
lines
is
probably
how
this
is
going
to
shake
out,
but
we'll
see,
I
think.
C
In
the
long
term
they
don't
you
know,
I
mean
I,
can't
speak
for
the
entire
moderation
team,
but
ultimately,
in
the
long
term,
I
would
love
to
see
the
moderation
folks
not
need
ownership
privileges,
but
have
another
mechanism
you
will
bought
or
something
that
allows
them
to
do
everything
they
need
to
do.
But
that's
not
anything,
that's
going
to
happen
imminently,
so
we
need
to
do
something
else.
I
mean.
G
G
B
I
think
that's
you
know,
making
the
you
know
initiative
or
whatever.
There
is
a
good
idea,
but
I
I
I,
don't
believe
we
should
block
like
we
shouldn't.
We
shouldn't
factor
that
into
whether
we
agree
to
give
them
access
or
not
right
like
today.
They
can't
do
their
job
and
it
effectively
and
and
I,
don't
think
we
can
count
on
getting
the
automation
in
place
fast
enough
to
say
well,
we'll
just
wait
for
that.
B
B
C
That
was
me,
so
we're
so
we're
moving
this
removing
this
node
mentorship
repository
into
the
foundation,
the
current
owner,
so
there
there
there
are
three
ways
to
do
it.
You
can
see
Jordan
wrote
them
up.
Actually
you
know
what
I
want
to
take
this
to
the
private
segment.
Actually,
now
that
I'm
thinking
about
it,
I
have
two
things
for
the
private
segment,
and
this
should
actually
go
there,
but
let's
leave
it
on
the
agenda.
Just
to
know
that
the
you
know,
the
the
TSC
is
gonna
figure
out
how
to
make
this.
B
B
A
There
was
a
bunch
of
comments,
the
den
posted
about
the
feedback
group,
which
I
think
I
brought
some
array
up
and
there's
sort
of
a
little
bit
of
discussion
between
women
Tierney.
There
Leo
G
of
n-
and
he
says,
thanks
for
the
amazing
work,
you
guys
folks,
do
keep
up
the
good
work.
A
A
C
C
B
Okay,
so
that's
it
for
today
and
we'll
close
the
stream
and
go
back
to
the
private
session.