►
Description
C
B
C
B
I,
don't
think
so.
I
think
they're
waiting
for
us
to
finalize
the
Charter.
There's
still
a
few
outstanding
comments
on
the
PR.
Nobody,
I
might
sell
dancer.
Jeremiah's
question,
I
understand,
is
the
point
where
it
went
from
investigate,
investigate
or
eat
when
we
were
doing
this
was
aboard
me
like,
I
want
to
say
two
or
three
board
meetings
ago,
but
it
was
at
a
board
meeting
where
I
think
they
decided
to
do
that
at.
E
C
F
Not
really
me,
but
no
report
200
was
released
a
couple
days
ago.
So
there's
something
put
in
your
your
weekly
weekly
report:
Jeremiah
dip
it
in
the
nodes
over.
C
Cool
alright,
so.
A
Oh
yeah,
so
that
reminds
me
the
NPM
ID
for
no
Jess
or
note
I
think
it's
no
jess
is
I.
Think
crist's
reserved
that
Chris
Dickinson,
so
I
could
try
to
talk
them
again
about
transferring
on.
Okay
is
yeah,
I
mean
I
want
to
be
like
sure,
want
that
let's
decide
I.
G
A
There's
like
a
difference
between
mpm
orgs
and
users,
I.
Think,
though,
if
it's
under
the
order,
I
think
it's
always
namespace.
I
don't
remember
the
details
exactly
because
that
wouldn't
be
what
we
want.
We
want
it
as
a
top-level
namespace,
probably
on
NPM.
Yes,
then
we
want
have
like
a
node
jess
user
of
some
sort.
Essentially,
I
think
you.
G
C
A
G
H
C
C
Talk
about
a
couple
other
issues,
the
general
day
to
the
member
trouble
fund
meeting
times
in
the
community
committee.
So
quite
a
few
things.
What
I
think
there's
still
some
of
these
are
still
on
the
agenda
for
today.
So,
okay,
so
first
item
on
our
agenda
is
PSC
issue:
205
nominating
joshed
through
the
TSE
josh
itself
nominees,
which.
F
Had
any
objections
it
doesn't
do
cracy,
so
I
pictures
I
better.
Take
the
initiative
that.
C
H
C
C
C
E
But
since
we
have
a
TS
see
that
is
much
larger
than
the
attendees
here,
it's
not
just
going
to
be
objections.
In
this
meeting.
We
have
to
make
sure
that
we
call
a
vote
on
github
and
get
input.
Those
people,
one
of
the
hang-ups,
has
been
we've,
been
waiting
to
sort
out
their
membership
rules
so
that
we
can
ask
people
to
leave
and
then
a
dozen
people
on
so
I
think
what
we
should
probably
do
is
just
call
it
a
boat
on
github
and
then
get
yeah.
That's
it
soul.
E
C
E
C
H
C
Hey
so
so
we
are
actually
revising
the
Charter
here,
the
CSU
charter.
Can
we
remove
the
two
thirds
thing
and
in
particular
well,
while
we're
in
there
I
realized
today,
if
sends
us
about
membership
changes
in
general,
which
would
include
removing
people
even
if
they
self
nominate
to
remove
themselves.
C
C
See
voluntary
resignation
is
already
covered,
yeah,
okay,.
C
I,
think
if
I
can
go
back
and
address
to
the
membership
rules,
thing
where
we
can
take
off
the
two-thirds
requirements
for
adding
somebody
and
just
make
it
a
simple
majority
of
participating
it
as
long
as
there's
no
objections,
I
think
removing
somebody
should
still
be
a
two-thirds
vote,
because
that
needs
to
be
a
pretty
high
bar
for
having
the
TSU
remove.
Somebody.
B
Yeah
agree
with
that
as
well.
Let
me,
especially
since
you
know
the
way
that
the
new
removal
rules
work,
we're
usually
asking
them
to
resign.
So
if
it
gets
to
the
point
that
we're
going
to
remove
someone-
and
they
didn't
resign
on
their
own-
that
that
sort
of
implies
that
there's
a
conflict
and
some
contention
there
and
I
think
having
a
high
bars
really
important.
In
that
case,.
C
D
B
E
C
F
A
No,
like
I'm,
not
sure
if
we
have
talked
about
Josh
and
the
tsc
at
some
point
in
the
past
and
email
but
I
think
generally,
we
should
try
to
at
least
make
the
boots
public
in
some
way.
D
B
Maybe
we
can
do
it
after
your
time
or
something
it
might
be
concerned
with
is
voting
for
membership
specifically,
is
that
we
are
kind
of
like
voting
on
a
person
and
on
an
individual
on
it
really
want
to
create
like
personally,
that
is
here,
but
there's
a
way.
We
could
do
it
also
with
transparency,
so
maybe
after
a
period
of
time
or
something
I,
don't
know.
C
D
E
C
Process
can
be
reaching
the
rotating
okay,
so
issue
number
195
copy
date.
C
This
goes
into
whether
we
can
update
the
copyright
date
in
our
statement.
I
do
we
actually
have
a
date
in
our
copyright
in
our
license?
It's.
C
C
H
H
C
C
Start
this
actually
raises
the
larger
concern.
We
should
not
actually
be
allowing
the
individual
projects
to
set
their
own
copyright
headers.
That
should
actually
be
something
that
has
approved
to
the
board
since
they're
the
ones
actually
just
wanting
to
find
what
that
copyright
is
now
with
regards
to
this
updated
copyright
issues
that
will
be
talking
about
soon,
but
there
is
a
versus
copyright,
node
dais
contributors
on
all
rights
reserved,
there's
no
date
in
that,
and
that's
touring
and
I'm,
but
I
would
propose.
Is
it
all
of
all
projects
use
that
same
header?
In
that
same?
D
B
H
H
B
H
C
H
C
C
E
D
C
C
F
G
C
C
D
C
F
F
C
C
Okay,
yeah,
let
me
figure
out
what's
going
on
there,
then
that's
strange!
Okay!
We
need
to
keep
this
on
the
GSU
addenda
until
we
have
a
natural
charter.
C
C
Updating
the
copyright
issue
174
so
I
gave
an
update
yesterday
on
the
I'm,
a
CTC
call.
There
was
a
meeting
the
legal
committee
meeting
last
week
and
participated
in
a
conversation,
basically
where
we're
at
right
now
is
that
once
the
board
looks
at
it
next
week
should
go
to
be
on
the
agenda
will
get.
C
The
first
key
are
landed
that
restores
the
original
copyright
editor
that
was
removed
back
and
I
Oh
Jess
and
just
the
files
are
still
remaining
from
that
original
changes,
something
like
nine
hundred
or
so
files
that
would
land
and
then
the
second
PR
that
proposes
the
updated
puppy
right.
Hitter
needs
to
go
for
review
by
the
board
and
various
copyright
holders
for
approval.
We
have.
We
cannot
land
it
until
we
get
that
approval.
C
C
I
also
added
at
the
committee's
request,
some
documentation
in
the
collaborator
guide,
saying
that
those
headers
need
to
be
there
and
that
if
they,
if
copper,
a
header
already
exists
that
it
cannot
be
touched
without
board
approval
and
I
got
the
PR
ready
to
go.
It's
just
pretty
much
waiting
on
the
on
the
board
actually
say
when
we
can
move
forward
beyond
that,
there's
really
not
much
else.
We
can
do.
C
D
C
To
be
at
least
assembly
in
the
hands
of
the
legal
committee,
so
in
normally
I
would
say
that
you
probably
do
need
to
get
all
of
the
contributors
but
beast,
but
because-
and
this
is
very
weird-
but
because
joint
you
said
that
CLA,
because
this
was
removed
like
a
lot
of
people.
They
can't
we
do
these
files,
that
is
when
it
was
removed
after
I,
think
removed
it.
C
C
C
C
Need
to
just
make
sure
that
they're,
okay
with
it
and
that
that
you
know
that
they're
not
going
to
objective
it,
just
follows
into
it
the
same
thing
that
yeah
we
want
to
make
this
change.
Does
anyone
object
if
no
one
speaks
up
10
and
we
should
be
good
to
go,
but
we
still
can't
move
until
the
legal
committee
am
innocent
and
the
foundation's
board
right.
C
C
C
Okay,
yeah
yeah
I,
just
I
just
don't
mean
to
myself
because
I
needed
to
make
a
comment.
That's
why
I
was
unneeded.
So
that's
been
so
my
expectation
with
the
next
board
meeting.
Is
this
they'll
approve
the
first
one,
because
it's
fairly
uncontroversial
though
we
just
need
to
get
this
back
in
and
that
we
did
the
wrong
thing
at
one
point,
the
second
one.
C
They
will
probably
look
at
it
and
say:
yes,
that's
the
block
that
we
want,
like
that,
looks
really
good,
but
defer
some
some
work
for
somebody
to
do
to
go
and
look
up
and
answer
any
questions
about
people
that
may
have
contributed
it
during
that
time
and
had
conversations
to
join
I'll
a
kind
of
stuff.
So
I
doubt
that
we'll
have
a
revolution
on
the
second
one.
But
I
expect
a
revolution
on
the
first
one
for
sure.
H
H
C
D
C
C
D
C
Now,
in
the
revised
version
they
what
the
updated
header
that
is
reverted.
So
we
pull
all
of
those
headers
back
out
of
all
those
files,
because
it
touches
test
file
that
such
as
benchmarks,
it
is
it's
throughout.
The
updated
version
would
just
have
the
lesser
copyright,
NS
pdx
identifier,
only
in
the
JS
files
in
live
and
the
C
D
and
H
headers
in
source.
C
C
D
B
C
C
F
G
A
I
think
get
up
might
have
messed
up
on
this
because
I
removed
the
label,
but
it
says
I
also
added
and
removed
it
on
December
15,
yeah
I.
Don't.
C
Alright,
so
this
one's
called
out
for
a
boat.
It
is
a
charter
change,
so
we
have
to
have
two
thirds
of
the
titty
members
weigh
in
on
this,
and
so
I
asked
you
if
you
haven't
done
so
already,
please
go
to
the
github
hood
and
take
a
look
just
to
summarize
this.
Basically,
what
this
does
is
it
puts
an
attendance
rule
on
the
tsc
that,
if
I
don't
want
to
misquote
it
so
ago,
if
someone
does
not
attend
twenty
five
percent
of
the
Verger
scheduled
meetings
within
a
six-month
period.
Basically,
we
we
asked
them
to.
C
And
that
twenty-five
percent
ends
up
being
at
least
one
meeting
every
three
months
and
which
is
pretty
generous
in
here.
You
know
it's
just
you
know.
The
whole
purpose
of
this
is
to
keep
it.
You
know
we've
added
very
difficult.
I'm
steven
corum
falls.
There
are
a
lot
of
people
on
the
on
that
list.
Just
have
not
participated,
and
we
need
to
make
sure
that
we
are
encouraging
that
participation
in
two
people
that
we
do
have
on
the
list
as
being
voting
members
are
actually
engaged.
C
C
C
C
C
Someone
we
need
one
miracle:
gonna
need
the
room,
so
just
just
some
context
here.
My
main
problem
was
a
two-thirds
rule
in
general.
Is
it
it
creates
a
bigger
barrier
to
change
then
of
voting
against
change
red
so
like
the
incentives
around
wanting
to
improve
something,
it
makes
it
harder
for
people
to
want
to
improve
it
than
it
does
for
people
that
just
want
to
keep
things
the
same
loads
about
independence
in
general?
That's
my
issue,
so
whatever
believe
it
hi
I
have
no
I
would
have
no
problem,
reducing
the
role
or
things
like
that.
C
Also
remember
that
I
mean
so
there's
I
think
there
has
to
be
a
distinction
here
between
charter
changes
and
governance
changes,
so
we
own
the
governor's
document
and
it's
in
there
for
that.
It's
also
there
for
the
Charter,
but
the
trevor
also
have
to
get
improved
by
the
board.
So
I
don't
know
why
we
have
like
a
bunch
of
additional
checks
on
something
that
still
has
to
go
from
board
approval.
I'm.
C
B
B
The
only
thing
we
have
left
that
requires
two
thirds
is
removing
someone
and
I
think
that
makes
sense
to
me,
but
yeah
I,
like
they
did
removing
charge
changes
as
well,
just
kind
of
as
we've
seen
here,
and
it's
almost
like
Neil
sometimes,
and
we
can
look
at
changing
governor's
documents,
but
on
occasion
we
might
get
hung
up
on
like
maybe
just
like
a
sentence
or
two
in
the
Charter.
That
would
prevent
us
from
making
a
governance
change
as
well
and
so
yeah
I.
Think
being
able
to
do
those
easily
as
well
is
useful.
C
D
C
C
C
C
F
D
D
C
C
F
C
A
C
C
F
D
C
That's
for
wanted
yeah,
so
let
me
talk
about
this
little
bit,
so
we
we
have
a
code
and
learn
happening
right
and
rich
and
n
are
driving
that
we're
working
on
a
budget
right
now
the
board
will
end
up
passing
a
budget
and
we'll
pay
for
some
stuff
that
needs
to
happen
out
there.
If
we
want
to
do
a
collaboration
summit,
we
just
need
people
to
drive
it
and
to
follow
up
as
well.
The
money
is
not
the
barrier
here.
It's
really
getting
people
to
take
this
on
and
own
it.
C
D
A
A
C
I
think
it's
just
a
matter
of
just
putting
together
the
details,
so
I
think
has
already
been
some
conversation
happening
on
the
github
around
that.
So
I
think
we
just
continue
there
unless
there's
something
specifically
need
to
take
to
the
board
in
terms
of
funding
or
we
use
our
TFC
discretionary
funds.