►
Description
https://github.com/nodejs/TSC/issues/61
Participants:
* Rod Vagg @rvagg (TSC)
* James Snell @jasnell (TSC)
* Alexis Campailla @orangemocha (TSC)
* Jeremiah Senkpiel @Fishrock123 (TSC)
* Michael Dawson @mhdawson (Observer)
* Bryan Hughes @nebrius (Observer)
A
A
A
A
B
B
We
do
have
an
LPS
team
and
LPS
repo,
and
it
it
works
rather
well
without
actually
having
to
charter
a
working
group
and
that
a
lot
of
these
other
important
groups-
you
know
quite
a
few
of
them-
could
actually
just
be
unchartered
as
working
groups
and
just
establish
this
team
and
that
the
ones
that
we
keep
is
a
working
groups.
Things
like
me
with
the
documentation
website,
build
those
actually
do
make
sense,
moving
up
to
a
higher
level
at
the
TV,
given
their
scope.
B
For
example,
the
documentation
working
group
is
not
just
working
on
a
documentation
in
core
they're,
also
doing
documentation
directly
against
the
website,
I'm
putting
out
the
guides
and
that
kind
of
thing,
and
it
makes
sense
for
a
cooperator
kind
of
a
higher
level
same
thing
with
the
website.
Working
group
bill
is
not
just
doing
stuff.
The
core
was
also
doing
stuff.
The
lid
UV,
the
testing,
no
testing,
that
kind
of
things
that
is
have
a
broader
scope.
B
If
we
recast
this
into
not
saying
all
of
these,
existing
work
groups
are
moving
up,
but
only
a
handful
of
the
working
groups
to
want
to
make
the
most
sense
move
up
to
the
tsc
level
and
the
rest
of
the
work
groups
actually
get
unchartered
and
made
into
just
regular
team
under
core
all
right,
so
that,
from
that
point
on,
a
work
group
is
always
chartered
by
the
by
the
GSC
or
is
under
core.
We
would
just
form
new
teams
that
make
sense
right.
C
Now
the
ones
that
work
groups
like
safe
for
the
LTS
working
group,
it
was
kind
of
delegated
the
authority
to
I,
don't
decide
when
the
LTS
releases
were
going
out.
That
kind
of
stuffs,
as
opposed
to
going
back
to
the
tsc
I.
Don't
know
if
that
affects
that
at
all
that'd
be
the
only
question.
I
have
oh.
B
So
we
can
have
some
authority
and
one
to
actually
cut
those
in
that,
and
the
TC
just
basically
refers
to
that
team
for
managing
that
person
and
said
it
was
rather
well.
Even
though
we
haven't
had
a
chartered
work
group
I,
think
I
think
the
opportunity
here
is
actually
to
eliminate
some
of
that
perceived
bureaucracy
of
having
to
form
a
workgroup
all
right
and
having
to
go
through
this
charter
process.
You.
D
E
B
Fall
under
the
TC
process,
for
whatever
the
GC
decides,
the
full
working
groups
would
have
this
whole.
Now
that
they're
the
tongs
they
could
have
their
own
process
all
right,
but
those
that
have
to
be
chartered
at
atif.
It
is
tsc
level
and
and
reviewed
there.
If
that
work
group
wants
to
take
some
of
the
responsibility
of
the
TC,
it
would
still
have
to
come
to
the
TC
impasse.
It's
actually
what
this
will
end
up
doing
would
be.
The
TC
is
like
a
work
group
for
core
right.
B
F
But
what
suggest
that
you
could
step
back,
because
what
I
find
confusing
about
this
prd
kind
of
bundles
to
big
changes,
and
one
is
the
decision
of
the
mission
of
the
TC
and
focusing
primarily
on
quran
and
and
two
is
the
restructuring
to
make
to
fulfill
that
mission.
I
guess
so,
I
guess,
once
you
let
go
of
their
mouths,
they
should
host
another
project.
That
is
structurally
economic
sense.
F
But
so
far
we've
been
discussing
the
mission
of
the
foundation
and
when
we
show
host
projects,
all
I
think
this
is
almost
should
almost
be
two
separate
PR.
In
a
way
so
I
mean
we
compared
the
idea.
Okay
is
our
mission
now
to
focus
on
core,
because
that's
kind
of
the
main
discussion
that
we've
been
having
right
and
then
once
we
make
that
decision,
that
what
is
the
best
structure
to
fulfill
that
objective,
I.
B
A
That,
if
we,
if
we,
if
we
continue
to
tackle
the,
what
is
the
mission
thing
and
what
is
our
role
here,
then
it
should
become
clear
or
what
what
we
should
do.
Organizationally
I
think
Michaels.
Just
putting
you
know,
geez
just
jumping
forward
to
many
steps
for
us,
so
it's
all
getting
jumbled
up.
So
we
need
to
encourage
him
to
walk
back
of
it.
The
the
mission
thing
I
mean
that
I'm.
A
A
That
is
beyond
call,
then
opens
up
justification
to
start
a
new
TC
underneath
the
board
and
that's
something
I
really
want
to
avoid
I
want
I
want
them
to
be
three
groups
in
the
foundation:
there's
board,
executive
and
and
technical
execution,
which
is
governed
by
the
tsc
and
I,
want
to
try
and
make
sure
that
we
keep
it
that
way.
We
don't
have
multiple
arms
of
technical
execution,
because
it's
just
going
to
make
things
extremely
difficult.
A
C
A
B
D
D
D
D
E
I
think
that
overlap
between
the
CTC
and
T
is
he
has
also
kind
of
helped
drive.
Some
of
the
confusion
about
the
tses
role,
as
some
of
the
concerns
I've
heard
from
others,
is
that
the
tsc
has
like
deep
knowledge
of
neo
node
core,
which
you
know
structurally
is
actually
not
the
case,
but
you
know,
because
an
overlap
is
sort
of
viewed
that
way
and
so
the
relationship
with
other
projects.
D
A
D
A
So
here
yeah
he's
a
board
concern
which
I
was
like,
oh
also
share,
which
is,
when
you
start
adding
members
from
these
disparate
projects.
If
we
were
to
bring
in
more
projects-
and
you
start
adding
them
as
to
the
tsc
it
dilutes,
the
TS&CS
concern
and
attention
away
from
call
more
and
it
makes
it
naturally
makes
the
TSE
and
more
expansionary
body,
because
it's
made
up
of
more
and
more
people
from
the
outside
that
naturally
have
an
outside
perspective
and
I
think
the
board.
A
The
board
concern
here
is
that
it's
changing
the
mission
of
the
foundation
a
bit
too
much
and
and
it
could
lead
to
you-
know
a
patchy
style
situation
where
it's
just
constantly.
I
was
looking
for
new
things
and
I
share
that
as
well,
because
I
still
like
I
like
call
to
be
at
the
core
of
our
vision,
and
so
that's
one
problem.
We
bring
on
additional
members
from
these
other
projects.
C
E
And
I
think
one
thing
that
contributed
this
confusion.
You
know
people
on
the
board
and
elsewhere
was
actually
going
back
to
the
communication
problem.
You
know,
I'm
people
actually
myself
included,
that
Express
was
a
at
it
as
a
top-level
project
and
it
wasn't
till
later
they
learned
that,
oh,
it's
actually
just
in
the
incubator,
so
I
think
it
was
like
that
early
misconception,
which
it
was
just
a
communication
problem
sort
of
led
ealing.
Some
of
these
fears
about
the
TSE
growing
too
quickly.
A
A
According
to
that
mission,
and
at
the
moment
we
don't,
we
just
very
executing
different,
even
though
executive
is
executing
on
its
own
plans
with
regard
to
education
and
and
these
events
and
they're
just
happening,
and
it's
it's
not
easily
justifiable
in
terms
of
a
central
mission,
they're,
just
things
that
you
do
because
you're
doing
them
so
I'd
really
like
us
to
have
that
sense
of
mission.
This
is
what
we're
doing,
which
we
stir.
C
A
A
Okay-
let's-
let's
not
I'm
mike
shanin
this
too
much
because
we
don't
have
actionable
work
here.
As
far
as
I
can
see,
except
discussion
on
the
PR,
I'm
still
going,
I'm
going
to
go
back
and
pull
that
mission
of
their
again.
That
I'm
only
just
now
catching
up
on
my
backlog
of
THC
level
work
and
so
I'll,
try
and
try
and
get
to
that
as
soon
as
I
can
is
there
any
actionable
items
that
you
want
to
do
in
order
to
discuss
about
this
particular
issue.
B
I
think
we
probably
just
need
to
bring
it
back
to
github
distress
it
a
bit
more
there.
The
concern
about
splitting
the
pr,
I
think
is
very
valid.
I
think
we
need
to
get
a
little
more.
Have
this.
This
notion
of
what
will
happen
to
be
working
in
groups
become
a
little
bit
more
crystallized
and
documented
I'ma
forward
a
little
decision,
but
I
think
just
bringing
it
back
to
github,
maybe
take
up
two
more
iterations
and
revisit
next
week,
but.
C
A
I
supposed
to
do
that
last
week
during
the
week,
but
didn't
get
to
it
so
I'll
prioritize
that
and
and
then
try
and
focus
that
down
just
that
question
and
then
I
also.
I
really
need
to
get
the
ball
involved
in
that
discussion,
as
well.
I
told
them
of
the
last
boarding
the
board
meeting.
I
would
but
I
wanted
to
get
a
closer
consensus
here
about
that
before
we
push
the
ball
and
then
explained
that
the
discussion
again
so
I
have
to
move
on
that
next
few
days,
if
weekend
so
I'll
try.
A
A
The
earlier
the
guidance
proposal
section,
this
is
guidance
for
new
projects,
I
I'm,
proposing
here
that
we
defer
this
discussion
because
it
comes
back
to
this
same
area
of
structure
expansion
mission.
Do
we
even
want
to
expand?
Is
it
that
kind
of
stuff?
So
it
just
seems
like
it's
just
a
to
stick
to
too
many
steps
forward,
and
we
need
to
put
a
hold
on
that
and
figure
out.
This
other
stuff
first
said
Sandra.
D
C
C
A
A
D
The
only
thing
is,
it
requires
someone
to
have
like
machine
to
do
this
on.
Currently,
that's
my
secondary
computer,
it's
perhaps
would
be
possible
to
do
it
on
a
main
machine.
Although
then
you
would
have
to
record
the
desktop
audio
and
your
microphone
currently
I.
Have
it
on
a
separate
machine
where
all
the
audio
is
just
coming
from
uber
conference,
where
I'm
not
actually
picking
my
mic
up
on
it,
so
that
everything
is
in
sync
properly.
D
D
Is
it
it's
like
it
I
think
ones
like
configuration
and
stuff
it
OBS
runs
on
like
almost
any
platform,
including
Linux
11.
Big
thing
to
note
is
I
just
use
like
a
nodejs
like
image,
because
there's
I
can't
really
screencap
uber
conference
for
who's
speaking.
That's
because
geolocation
is
shown
if
ended,
and
if
someone
calls
in
with
the
phone
number
the
phone
number
might
be
shown
so
I'm,
not
maybe
there's
like
a
better
eating
tool
like
I.
D
C
D
D
We
went
we
never
went
with
something
like
I
mean
slack
would
have
liked
the
same
problem
with
a
new
audio
calling
like
slack
or
teamspeak,
or
discord,
or
anything
like
that,
and
that's
because
sometimes
people
actually
need
to
call
in
because
they
don't
good
interconnections
and
stuff
like
over
conference
and
gotomeeting.
Actually,
like
has
capabilities
for
that,
where
people
can
call
them
up
real
phones
and
not
just
computers,
so
yeah.
A
D
A
D
So
that's
not
actually
true,
although
it
definitely
does
help
so
about
the
node.js
foundation.
Thing
YouTube
has
this
pretty
great
system
where
you
can
add,
like
admins
two
channels
really
easily,
and
they
don't
actually
need
authentication
to
the
main
part,
although
they
can
do
anything
on
the
channel,
then
so
that's
good,
because
you
can
actually
edit,
like
the
stream
title,
but
to
actually
stream
there's
just
like
this
key
thingamajig
that
you
need,
you
don't
actually
need
a
fennec
ation,
ok,
so
anyone
with
that
key
can
do
you
don't
need
to
do
anything?
Yes,.
A
D
D
A
D
So
there's
one
person
in
the
YouTube
chat
has
been
asking
some
things,
so
one
thing
that
they
said
was
they
were
pretty
lost
about
what
the
thought
flattening
proposal
was
about
until
they
actually
listened
to
a
YouTube
meeting.
So,
oh
well
so
I
one
of
our
two
TSE
meetings
to
get
like
context
about
why
there
were
concerns
and
that
there
even
were
concerns
about
adding
other
groups.
But
they
also
say
that
they
should
be
able
to
post
that
to
the
actual
issue,
and
then
they
have
an.
A
A
We
could
do
better
travels
around
LTS
show
that
we
could
do
better,
but
at
the
tsc
level,
like
the
width,
we've
got
significant
amount
of
churn
and
we
are
even
having
trouble
with
ourselves
keeping
up
with
it
all
and
we're
certainly
not
bringing
on
outsiders
with
it.
So
we
we
need
to
do
better
on
this
area.
I
think
it's
failing,
and
it's
not
a
good
one.
D
A
To
hook
that
out
ourselves,
yeah
I,
initially
the
the
just
behind
splitting
off
was
that
we
had.
We
had
very
deeply
technical
call
concerns,
and
then
we
had
organizational
concerns,
and
so
this
this
body
is
more
about
organizational
concerns
at
the
technical
side
of
the
the
technical
execution
side
of
the
foundation.
D
Dirty
to
the
CTC
as
a
note,
so
the
TFC
is
prob
oublie
somewhat
miss
named
at
this
point,
and
the
reason
for
that
is
that
we
started
with
it
as
the
technical
steering
committee,
and
that
is
what
it
is
in
the
foundation
charter
documents
and
that
is
quite
difficult
to
change.
So
we
haven't
changed
anything
about
that
about
the
name.
A
Yeah
and
to
be
honest,
there's
so
much
flux
of
we
ourselves,
if
not
figure
that
what
we're
doing
we
just
we
just
know
that
we
can't
mix
up
organizational
management
concerns
with
technical
concerns
and
I.
Think
we've
done
a
good
job
at
letting
the
CTC
focus
on
technical
concerns.
I
think
that's
that's
that's!
The
one
wing
we
have
out
of
this
is
that
the
CDC
is
quite
is
a
bit
more
focused.
D
I
might
as
well
just
read
it
off.
Okay
I
think
stalled,
/
sale
info
doesn't
represent
the
know,
Gia's
community.
Well,
there
are
things
there
sitting
for
a
long
time.
Updates
code
in
line
for
example,
code
and
learn,
is
something
that
Michael
tried
out
around
know,
convey
you
and
just
afterwards,
for
helping
people
understand
what
kind
of
went
into
node
core
development,
how
to
maybe
it
started,
but
I
don't
think
that
has
really
gone
anywhere.
D
So
Michael
emphasized
again
on
the
CGC
meeting
yesterday
that
thing's
getting
hard
to
manage
these
proposed
the
new
structure
and
attempt
to
help
I'm
very
much
for
staying
away
from
the
pre
I
OJ's
life,
where
things
move
really
slow,
but
are
some
initiatives
biting
off
too
much
work
right
now
for
the
amount
of
time
the
bone
tears
have
to
offer?
I
say
that
it
was
the
last
question.
A
Yes,
yeah,
we
I
think
we
absolutely
recognize
this
and
and
that
I
think
it's
it's
the
responsibility
of
all
of
us
here
to
push
back
on
the
churn.
The
impacts
ask
particularly
so
codon
loan
is
an
example
churn
that
is
pretty
much
dead.
Now
it
was
an
experiment
that
was
run
by
michael.
I
don't
think
any
of
us
had
anything
to
do
with
that,
and
so
we
need
to
try
and
pull
that
back
another
one.