►
Description
A
A
A
A
D
They're
they're
kind
of
that
one
thing
is
that
is
it
a
tsc
working
group,
a
CTC
working
group
or
a
TLP
and
then
there's
also
just
in
general,
like
I,
there
wasn't
a
meeting
this
past
Friday
and
originally
Sam
I'd
be
going
with
every
two
weeks.
I,
don't
know.
If
there's
a
meeting
scheduled
for
next
week,
I
just
was
wondering
what
they
act:
I'd
lat.
What's
the
activity
there?
What's
the
state
to.
A
A
B
A
You
talked
about
the
community
committee
and
probably
around
the
proposal
about
that.
We
talked
about
mbm
and
virgin
management
and
also
no
dash
inspect,
which
the
tsc
approved
to
bring
in,
and
the
CTC
also
approved,
to
bring
in
the
foundation.
So
I
believe
we
have
moved
it
in
and
that
is
we
figured.
It
was
under
the
scope
of
our
existing
responsibility,
since
we
already
ship
sign
almost
identical
to
it,
but
we
will
be
still
delivering
an
update
to
the
board
via
rod
bag
that
we
that
we
brought
in
just
to
be
transparent
about
that.
B
E
The
main
not
the
main
thing
was
that
the
next
step
that
they
were
waiting
on
was
the
actual
data
from
from
Mayo
the
note
security
data
to
actually
start
deciding
what
to
do
and
get
going.
So
I
think,
that's,
what's
holding
things
up
a
little
bit
yeah
what
they
do
that
you
know,
I
think
this
I
think
there
was
like
three
main
things
that
were
pretty
clear:
it's
just
that
they
were
the
main,
the
main
impetus
for
getting
a
stir
in
the
first
place
with
the
data,
and
the
data
is
not
shown
up
yet.
A
B
C
E
A
Doesn't
sound
like
it
so
version
management
and
nvm,
so
the
war
version
management.
Guess
it's
like
an
investigation.
Grouper
I
am
not
sure
what
we
call
it.
It's
an
open
group
for
people
to
join
that
care
about
version
management
that
want
to
discuss
it.
They
came
back
to
us
and
said
that
they
didn't
think
it
was
a
good
idea
to
move
nvm
into
the
foundation,
at
least
at
this
point
in
time.
A
D
D
A
D
B
B
D
A
D
A
But
sorry
not
just
like
the
new
installer
I
mean
from
like
they
say
the
current
OS
X
installer
I'd
still
love
it.
If,
if
there
was
like
at
least
an
option
to
install
a
burden
manager
for
that
I
think
I
would
help
a
lot
of
people.
I
mean
that's
kind
of
like
a
technical
thing,
but
I.
Think
relating
to
this
thing,
I
will
probably
propose
that
separately.
D
Cool
yeah,
one
of
the
I
mean
Jason
intro
from
here.
Microsoft
actually
wrote
up
an
alternate
for
nvm,
and
this
was
part
of
the
discussions.
There
was
a
JavaScript.
It
is
a
JavaScript
Orient
one
but
part
of
like
that's
that's
nice
for
us
cuz.
We
want
to
test
chakra.
Sometimes
it
helps
us
like
swap
out
the
engine.
It's
the
kind
of
thing
that
maybe
in
the
future
could
help
with
swapping
out
nvm
with
something
else.
A
A
A
B
Well,
I
can
speak
about
the
the
date
through.
There
are
two
issues
there,
the
date,
one
really,
if
you
take
it
more
of
a
high
level
than
just
a
day.
It's
it's
kind
of
me
wanting
to
know
if
all
these
projects
that
we're
working
with
and
the
the
license
that
is
they're
written
is,
is
right,
so
it
really
comes
down
to
like
we
don't
get
proactive
feedback
from
the
legal
groups
and,
like
you
guys,
are
doing
good
or
you
guys
are
messing
up.
B
E
E
E
They,
like
you,
know,
run
your
code
through
some
fancy
software
that
magically
figured
that
if
you
have
any
GPL
code
in
it,
that
kind
of
thing
I
I
feel
like
they're,
mostly
a
scam,
but
but
it
it
does
make
people
kind
of
feel
warm
and
fuzzy
about
it.
So
we
can
look
at
you
know
how
much
it
would
cost
and
how
much
we
really
want
and
what
we
want
to
see
from
I
kind
of
audit
yeah.
B
E
B
E
Told
but
that's
the
dental
problem
and
and
it's
a
weird
kind
of
cross,
DCO
issue
or
whatever
so
I
think
once
we
solve
like
our
pending
issues,
we
can
definitely
look
at.
You
know
ways
that
we
can
make
the
code
more
accessible,
legally.
I
think
also
like
the
more
that
you
go
down.
This
rabbit
hole
the
more
that
you're
going
to
get
suggestions
for
things
that
will
improve
the
legal
situation
of
the
code,
but
may
introduce
barriers
to
contribution
and
adoption
right
like
you
can
get
more
legal
protection.
E
A
B
B
E
B
I
mean
really
that
we
have
a
lot
of
other
projects
and
that
I
know
node
core
is
like
the
the
Starchild
here
and
so
a
lot
of
people
focus
on
that
which
obviously
has
a
lot
of
attention
and
probably
a
lot
more
need,
but
you
know
we're
pulling
in
all
of
these
other
projects.
You
know
node,
inspect
and
node
report
is,
you
know
just
the
side,
things
that
are
going
even
even
the
Installer
that
you
started.
A
B
Like
maybe,
you've
missed
that
part
of
the
call,
really
it's
just
it's
kind
of
a
kind
of
like
knowing
that
the
legal
team
is
is
looking
at
what's
happening
here
at
what
us
non.
Lo
hairs
are
doing,
and
in
saying
you
know
now
we're
not
doing
something
horrible,
and
so
the
issue
I
opened
was
about
dates.
Something
I
was
working
on
stumbled
across
it
and
I
wasn't
quite
sure
if
we
should
be
updating
those
dates
or
not,
and
you
know
so,.
C
D
D
E
E
History
of
it
at
this
point
is
that
a
lot
of
people
and
projects
use
it
to
as
an
easy
way
to
know
when
the
last
time
that
the
file
was
updated
or
that
it
went
through
some
kind
of
legal
check.
You
know
a
lot
of
these
policies,
predate,
get
and
predate
good
version
control
tool,
so
yeah,
that's
kind
of
my
take
on
it,
but.
B
A
E
E
One
thing
that
all
note
really
quickly
about
new
projects,
so
the
board
did
the
board
and
legal
committee
did
already
create
a
list
of
legal
requirements
for
bringing
a
new
project,
and
that
is
a
list
of
essentially
acceptable
licenses.
Along
with
some
other
practices
like
adoption
of
the
DCO,
we
should
be
making
sure
that
we
follow
that.
We
should
should
not
fall
out
of
alignment
with
that
for
new
projects
that
we
bring
in,
and
we
may
have
at
some
point,
particularly
I
don't.
E
I
don't
know
offhand
that
every
single
sub-project
has
a
dco
in
it,
but
it
probably
need
it
definitely
needs
it
if
it
doesn't
have
it.
So
we
need
to
go
through
that
and
comply
with
what
they've,
already
kind
of
laid
down
and
that's
kind
of
the
base
level
protection
that
we
should
be
looking
for
beyond
that.
Like
asking,
for
you
know,
additional
legal
review
with
Williams
suggesting
I
think
that
it
is
a
good
idea,
but
we
probably
want
to
take
the
recommendation
that
we
have
four
core
knock
through
them.
E
B
E
That
may
be
true,
but
court
also
is
the
largest
legal
liability.
So
a
lot
of
the
sub-project
have
West
code
that
we're
worried
about
copyright
issues
in
or
at
issues
and
stuff.
Like
that
also,
you
know
some
of
the
sub-project
are
necessarily
used
by
everything
or
could
be
replaced
more
easily
than
the
core
code.
So
I
think
the
way.
E
E
B
I
I
mean
I,
see
your
point.
I
guess
I
would
say
I
would
suspect
someone
like
netflix
would
be
have
a
different
urgency
on
like
they're
postmortem
tools
that
they're
using
and
making
sure
they're
all
covered.
Because
that's
going
to
be
important,
you
know
everyone's
going
to
have
their
own
version
of
important.
So.
E
The
note
ll,
node
and
node
report
are
in
an
easy
stage.
Like
there's
few
contributors,
you
know
they're,
all
collaborators
are
very
friendly,
so
I
think
if
there
was
something
we
wanted
to
change
and
use
them
as
a
template.
It's
not
a
bad
idea
as
a
starting
point.
Like
me,
we're
sighs
we
go
on
a
date,
err
ones
where
we
could
probably
make
that
chain.
E
So
that's
that's
accurate
I
mean
I.
Think
that
again
it's
most
important
that
we
just
make
sure
that
we
comply
with
the
existing
guidance
that
we
have,
which
definitely
says
that
we
should
have
a
dco
on
all
of
these.
If
we
don't
have
a
dco
that
actually
does
open
us
up
a
bit
more,
as
we
add
more
contributors
to
make
things
more
difficult,
so.
E
B
E
E
D
E
E
A
D
Commented
at
the
very
end
last
time
we
basically
said
another
week
and
then
we'll
merge
it
in.
She
wrote
at
the
very
bottom
today
that
she's
not
going
to
make
it.
Let's
see
so
she
wrote
they
haven't,
merges
prei
because
it
kind
of
prefer
fat
es,
never
merged
this
I.
Don't
think
this
is
gorgeous
so
feel
free
to
wait
on
Michaels
response
to
my
last
comment.
A
E
E
A
E
And
also
we
can
wait
until
the
entire.
We
should
also
wait
until
the
entire
travel
thing
is
done
to
update
the
cost,
because
it'll
be
a
combination
of
their
flights.
There,
other
hotel
reimbursement
and
all
those
things
may
come
in
at
different
times.
Right,
like
I
got
I
got
a
bill
for
Anna's
flight
really
early
details.
Actually,
that's
not
sure
I
didn't
give
it
that
early,
because
they
only
simply
LF
one
invoice.
E
E
Allocation
right
now,
the
idea
was
that
this
fund
will
just
get
updated
and
the
tsa
can
go
back
to
the
board
and
say
hey.
We
need
more
money,
here's
what
we
spent
the
money
on
before
on
really
important
stuff
like
sending
our
contributors
dc39
meeting
and
then
the
board
will
very
easily
just
kind
of
update
it,
but
we
we
wanted
to
make
sure
that
that
we
had
that
relationship
ongoing
and
that
we
didn't
just
have
a
giant.
You
know
pocket
of
one
out
of
allocated
money
that
nobody
was
spending
like
we
did
last
year.
B
B
You
know
just
give
tained,
occasionally
saying:
hey
michael,
what's
the
final
price
on
this
and
then
it'll
get
eventually
get
PR,
so
it
might
not
be
fast,
but
it
would
be
a
process.
I
say
that
we
go
ahead
and
merge
this,
and
if
there's
any
other
little
things
we
want
to
adjust,
we
can
do
that
in
a
different
PR.
E
Yeah,
what
one
kind
of
guide
that
you
might
want
to
look
at
is
a
the
Brooklyn
Draya
organization.
They
they
basically
have
a
big
javascript
file
that
has
line
items
with
comments
for
every
expense
and
every
piece
of
money
that
comes
in
and
it
just
always
kind
of
totaled
out
to
whatever
their
their
ongoing
expenses
are,
which
is
really
nice
but
like
we,
we
may
want
to
put
in
that
document.
E
A
Right
so
I
wrote
a
comment
back
on
in
response
from
essentially
from
what
Michael
said
to
Anna
and
then
also
requested
that
the
dark
be
updated
about
just
updating
the
cost
once
the
actual
cost
after
the
travel
is
done.
I
don't
know
if
we
have
enough
people
here
to
approve
to
merge
this
Jay
and
Brian
already
proved
it
Michael
Dawson
approved
in
who
else
do
we
actually
need
to
have
approved
us
I'm.
B
E
It
should
be
unless
there's
objections
right,
it
can
land
and
yes,
there,
a
long
time.
You
know
that
is
that
is
literally
the
process.
Like
I
know,
I
wrote
up
that
process
like
Becker's
about
the
same
process.
We
have
for
code
that
we
have
for
other
procedural
changes.
I
just
think
that
people
are
less
confident
about
the
process
than
they
are
about.
B
E
A
E
A
D
I
really
issue
everyone's
worth
discussing.
It
is
that
the
I
mean
we
don't
usually
get
quorum
anywhere
near
for
most
of
the
people
on
the
list
are
not
really
here
like,
and
we
can't
change
it
till.
We
have
the
processes.
I
think
we've
kind
of
suspended
any
changes
to
membership
for
a
year
almost
because
we
were
waiting
to
clarify
all
those
process
and
so
yeah
like
if
I
want
to
go
through
and
clean
up
some
of
the
old
issues.
I
can't
cuz
I
can't
close
them.
Yeah.
E
So,
okay,
a
couple
things:
the
membership
thing
like
yeah.
We
definitely
need
to
be
more
cautious
about
that
and
I'm
not
entirely
sure
that
there's
consensus
there
now
in
general,
you
only
need
quorum
if
you
don't
have
a
consensus.
So
if
nobody
objects,
you
don't
need
a
quorum
to
contribute
something
or
to
commit
something
or
to
change.
Well,.
E
E
Now,
like
I,
do
think
that
somebody
has
dropped
the
ball
here
in
just
driving
a
consensus
around
getting
those
membership
changes
in
probably
because
the
few
people
that
we
have
in
leadership
here
like
overloaded.
But
this
is
one
of
the
reasons
why
we
wanted
to
split
the
role
in
two
so
that
there
was
somebody
driving
the
tsc
and
somebody
else
on
the
board.
E
A
E
E
D
E
So
my
main
question
is
like:
are
they
actually
interested
in
these
procedural
matters,
like
one
of
the
reasons
why
we
creat?
Why
we
split
the
ctc
and
TSE
was
because
a
lot
of
these
people
like
didn't,
want
to
be
involved
and
wanted
to
be
involved
just
in
the
code
stuff
and
so
far
like
they
might
poke
into
like
one
or
two
issues
a
year.
E
E
In
that
part
of
the
process
like
I,
don't
know
why
you
would
start
altering
the
meeting
times.
It
seems
kind
of
cart
before
the
horse
like
when
this
happened
on
that
on
the
on
the
CPC.
It
was,
you
know,
a
lot
of
people
that
were
engaged
in
github,
constantly
weren't
able
to
attend
the
meetings,
because
the
meeting
for
rotating
times
like
that
was
a
really.
E
D
E
Yes,
and
what
is
that?
That
should
be
a
general
principle
across
the
project
right
like
and
also
I
mean-
and
this
is
happening
in
the
CPC
and
elsewhere,
like
the
main
mode
of
contribution-
needs
to
be
on
github
and
need
to
be
completely.
You
know,
accommodating
of
every
time
zone
and
that
these
these
meetings,
regardless
of
when
you
have
them,
are
hard
to
attend
and
hard
to
contribute
to
and
that
they
should
really
only
be
used
at
tiebreakers
and
to
handle
like
really
contentious
issues
right
like
that
should
be.
E
B
E
Bends
in
europe's
I,
don't
think
they're,
quite
the
opposite,
so
I
think
the
other
issue
also
may
be
the
day,
because
if
I
recall
like
when
we
set
up
this
meeting
time
when
everything
was
combined,
then
wasn't
it
quite
a
bit
and
it
was
chosen
because
it
was
like
late
for
Ben
and
early
for
rod,
so
they
could
get
on.
But.
A
A
B
A
B
A
A
A
So
as
for
the
next
meeting,
the
next
meeting
for
this
group
will
be
on
februari
than
ninth,
probably
the
same
time.
Unless
rotating
meetings
end
up
in
between
that,
but
I
highly
doubt
they
will
and
there's
also
a
google
calendar
for
this,
which
is
linked
in
the
minutes
dark.
But
we
should
probably
put
that
may
be
something
somewhere
like
on
the
actual
TSE
repo
to.