►
From YouTube: Community Committee 09-14-2017
A
Okay,
so
hi
everyone
we
are
on
the
community
committee
meeting
for
September
14th
2017.
We
are
going
to
run
through
the
list
of
people
that
we've
got
attending.
Today's
call
so
I
think
the
best
way
to
do
that
is
looking
at
our
invite
invited
list
for
the
meeting.
If
you're
present
I
would
say,
go
first
and
I
think
that
that
is
Jen.
D
E
A
A
H
So
sorry,
falcomon
I'm
Cora,
could
you
collaborator
for
note
located
in
Cambridge
Massachusetts
awesome.
A
Okay,
so
I'm
here
we're
gonna
hop
into
the
agenda
items
from
there.
So
the
first
up
is
our
discussion
around
electing
a
new
chairperson.
Nominations
have
closed
for
that,
so
the
the
two
folks
we
have
running
our
tyranny
and
Rachel,
and
our
next
step
is
to
host
the
election.
After
discussion
online
there
we
were
trying
to
figure
out
what
was
the
best
means
and
method
to
have
this
election
there's
some
precedence
in
other
parts
of
the
project
on
how
they
vote.
A
A
Does
anybody
have
any
thoughts
around
that?
There
is
there's
a
couple
projects
that
we
can
use
for
this
and
I
would
prefer
for
it.
If
you
know
had
talked
about
I
think
the
compromise
was
instead
of
showing
how
everyone
has
voted
for
the
candidates,
we
would
just
have
the
result
be
public.
Does
anybody
have
objections
to
that.
A
Okay
feel
free
to
raise
your
hand
or
poke
me
if
you
would
like
to
voice
that
outside
of
the
Hangout,
and
so
then
that
would
mean
that
we
are
going
to
move
forward
with
the
secret
ballot
and
as
part
of
that,
we
have
some
options
for
us
and
I'm.
Happy
I'm,
happy
with
I
think
actually
apologist
I
should
have
actually
shared
this
link
ahead
of
time.
There's
a
couple
different
methods
that
can
you
can
use
the
LF
overall
actually
uses
a
system
called
C
IBS,
which
is
the
Condorcet
method.
A
A
The
amount
of
time
that
we
want
to
have
this
open.
So
just
from
a
PR
standpoint,
when
we
talk
about
decision
making
and
honoring
different
time
zones,
the
minimum
is
generally
48
hours.
So
I
would
say
that
if
we
don't
have
everyone
vote,
you
know
if
everyone
votes.
If
we
know
that
the
count
is
has
been
completed
and
all
members
have
voted,
then
we
can
close
the
election
earlier,
but
otherwise
I
would
say
we
need
to
set
a
minimum
window
of
time
for
people
to
be
able
to
vote.
A
D
E
A
E
A
Our
governance,
the
observers-
are
not
voting
members,
unfortunately
yeah
okay,
but
thank
you
for
asking
that
to
clarify
and
as
part
of
that
as
part
of
the
distribution
tyranny
of
the
votes,
I
believe
that
I
have
to
manually
enter
the
emails
for
everyone
who
gets
an
access
key
to
vote.
So
I
don't
actually
like
yeah
it's.
They
obscure
it
through
a
weird
way,
so
that
also
I
like
I
can.
I
know
whoever
has
their
access
keys,
but
I
don't
get
to
see
you
know
if
the
access
keys
aren't
even
necessarily
applied
in
that
same
way.
E
A
G
A
G
I'm
not
sure
which
one
it
was
I,
don't
know
if
rod-like
it's
something
that
Michael
Rogers
had
actually
used
in
the
past
and
I.
Think
James
just
asked
him
and
used
the
same
thing.
But
if
you
have
something
like
if
the
one
that
you
were
referring
to
actually
means
that
even
the
organizer
can't
see
the
results,
I
think
that's
even
better
yeah.
A
I
agree
and
there's
there's
options
for
even
that,
but
I
do
think
like
it's.
Certainly
we're,
certainly
not
using
the
existing
voting
system
that
node
uses
for
the
annual
individual
elections,
because
we're
migrating
away
from
that
system,
but
even
that
doesn't
well
I
guess
it
does
yeah.
It
shows
that
people
voted,
it
does
not
show
who
they
selected.
A
G
A
A
G
A
A
G
A
A
Okay,
so
the
next
agenda
item
I,
initially
have
two
items
sort
of
connected
together
and
one
was
a
PR
and
one
was
an
issue
because
I
think
that
they're
sort
of
intertwined,
so
William
was
kind
enough
to
file
a
PR
sharing
the
conducts
commitment
that
he
had
drafted
and
I
think
that
this.
This
is
a
potential
solution
being
offered
towards
the
issue
that
I
have
identified
all
so
linked,
which
is
to
document
the
guidelines
for
accountability,
expectations
for
all
members
of
the
TSC
CT,
seeing
calm
calm.
So
that's
a
very
I'm
very
wordy
with
titles.
A
So
the
reason
that
these
are
important
to
consider
together,
I
believe,
is
that
that's
what
the
aim
is
right.
The
aim
of
these
and
the
reason
that
those
groups
are
named
is
because
they
are
leadership
groups
and
it
is
not
within
our
scope
to
be
able
to
write
guidelines
for
the
board
as
an
example,
but
we
can,
as
groups
work
together
on
these
guidelines
and
I.
A
Think
that
that's
why
that
issue
is
important
to
look
at
alongside
what
William
was
offering
so
I
think
there
were
some
disagreements
on
the
commitment
statement
and
sort
of
that
as
the
method
for
us
to
communicate
leadership.
Guideline
values
so
I'd
be
interested
to
hear
if
folks
think
my
suggestion
is
taking
what
William
has
written
as
a
PR
and
also
the
really
good
feedback
that
we've
gotten
in
that
issue
regarding
guidelines
for
accountability
and
sort
of
combining
those
into
a
leadership
document,
a
leadership
guideline
PR.
A
A
The
moderation
guidelines
are
for
everyone
who
is
participating
in
node
and
what
this
is
it
and
I
think
what
William
and
William
I
would
love
your
feedback
on
this.
The
point
of
that
statement
is
to
say
that
these
committee
members
need
to
be
held
to
a
higher
standard,
because
our
actions,
don't
necessarily
single
actions
for
good
or
for
worse,
don't
necessarily
violate
code
of
conduct,
but
can
add
up
to
a
pattern
of
driving
folks
away
from
the
project
and
as
leaders
we
have
to
build
a
pattern
of
being
welcoming
and
supportive
of
the
project.
A
That
does
not
mean
that
you
can't
object
to
things
happening
in
the
project
or
be
a
dissident,
but
it
means
that
overall,
you
are
being
supportive
and
trying
to
be
helpful,
and
that's
something
that
we've
seen
over
the
past
couple
of
years
has
we've
struggled
as
a
community
to
voice
is
that
our
leaders
across
the
board
are
being
held
to
this
regardless,
so
they
are
being
held
to
this.
I
will
say
this,
so
this
is
codifying
guidelines
of
expectations
that
have
been
communicated
from
from
many
different
types
of
people
in
different
parts
of
the
community.
A
From
the
board
to
ecosystem
to
other
people
that
are
collaborators
and
saying
like
yes,
we
agree
we
should
be
held
to
this,
and
when
we
are
stepping
outside
of
this
these
boundaries,
when
we
mess
up,
people
should
be
able
to
talk
to
us
and
say
like
yeah.
You
know
these
are
things
that
are
expected
of
us.
I.
D
Am
I
have
a
huge
problem
with
that
personally
I'm,
not
saying
that
like
I,
don't
know
how
to
control
myself.
Obviously,
I
do
but
I
think
that
it
just
leaves
people
up
for
more
scrutiny
like
it's
the
changes
that
are
being
made
for
the
code
of
conduct
which
applies
to
everybody.
You
know
that's
fine.
Those
are
you
know,
guidelines
that
people
know
to
follow,
but
this
just
seems
like
anybody
that
is
putting
themselves
out
there
to
try
and
make
things
better
are
going
to
be
opened
up
to
a
whole
nother
level
of
like
I.
D
Let's
do
so
like
I
mean
I,
don't
want
to
feel
like
I'm
gonna
have
to
go
check
every
single
online
user
profile
I've
ever
made
for
the
past
ten
years
and
see
like
if
people
disagree
with
a
moderation
decision
or
a
community
committee
decision
that
I've
made
that
people
are
going
to
be
coming
after
me.
So.
A
I
I
would
say
first
with
that
is
that
so
as
part
of
TSC
and
as
part
of
community
committee,
people
do
have
to
recognize
that
we
are
being
held
to
a
higher
level
it
level
of
scrutiny,
because
we
are
making
decisions
for
the
entire
project.
We
are
making
decisions
that
affect
8
million
users,
I.
A
E
G
B
E
Think
it
is
fundamentally
different
than
some
of
the
previous
things
that
our
thing
kind
of
submitted
and
I
do
think
you
know
it
does
one
of
those
things
that
I
was
worried
about
as
well.
Is
you
know
having
to
go
scrub
every
single
thing
you
anyone
in
the
project
has
ever
done.
That's
a
member
of
the
TSE
or
calm
calm.
That's
not
something
we
should
ever
have
to
do
as
part
of
this.
E
No
and
it's
explicit
in
kind
of
stating
that
and
not
even
made
a
comment
on
part
of
that
to
try
to
kind
of
get
clarified,
clarification-
and
you
know
it's
very
collaborative
right
now
and
I
definitely
suggest
going
through
and
reading
that
and
then
commenting
on
anything.
If
there's
any
specific
issues
with
it,
it's
a
pretty
well
written
doc.
So
far
and
I
definitely
think
everyone
here
should
probably
try
to
take
some
time
to
go,
just
review
it
and
either
give
a
plus
one
or
minus
one
or
give
feedback
on
it
and.
G
We
should
we
should
apps,
you
know.
Well
absolutely,
you
know
if
we
get
consensus
on
selling
lists,
it's
absolutely
a
we've
documented.
This
is
the
expectation
going
forward
right.
It's
not
a
if
anybody
comes
back
and
says
well
in
the
past
people
we
don't
care
right,
like
we
didn't,
set
these
expectations,
so
they
don't
apply
to
any
pasts
anything
in
the
past.
It's
like
going
forward.
This
is
what
we're
gonna,
try
and
hold
ourselves
right.
F
It
might
be
a
bit
much
to
say
we
don't
care,
but
it
is
like,
in
my
PR
I
specifically
said
it's
during
my
tenure
and
that
are
very
important.
Whether
people
like
it
or
not,
the
the
greater
public
is
going
to
judge
this
committee
in
all
of
the
committees
on
who
they
surround
themselves
with
on
that
committee
who
they
allow
to
be
on
the
committee
and
when
things
don't
go
well,
we
have
lots
of
proof
out
there
that
someone's
going
to
start
digging
through
past
and
and
throwing
it
like.
F
Here's,
a
person
that
says
this
and
they're
on
this
committee,
and
they
feel
this
way
and
we
need
to
have
some
guidelines
in
place
where
we
can
say
well.
That
is
something
that
they
had
in
their
past
and
during
their
tenure
on
the
committee.
They
didn't
reflect
those
values
and
those
views
and
that
you
know
the
individual
can
say
something
if
they
want
about
their
past.
But
as
far
as
the
committee
is
concerned,
we
have
a
guideline
yeah.
A
Yeah,
that's
like
to
a
certain
extent.
We've
definitely
heard
that
you
know
folks
across
you
know
the
community.
As
of
late
saying,
like
you
know,
it's
really
hard
to
hold
people
to
two
rules
that
have
been
put
in
place
on
action
that
were
long
before
the
rules
were
in
place
and
that's
that
gets
ya.
That's
a
tough
argument
and.
E
I
do
think
that
this
is
this
specific
document.
The
Michael
submitted
is
a
PR
is
definitely
a
good
step
to
being
able
to
be
accountable
in
the
future.
For
things
like
what's
happened
recently
with
the
two
instances,
you
know
that'll
kind
of
allow
us
to
have
a
framework
to
go
to
when
it
happens
again.
If
it
does
happen
again,.
H
So
I'm
active
observer
of
the
things
that
are
going
on
I
think
there
were
more
than
two
instances
of
reports
coming
in
from
the
community
about
a
personal
statements
made
by
let's
call
them
leisure
leadership
figures
and
the
fact
of
what
we
did
was
or
what
the
resolution
was
was
something
similar
to
what
William
was
referring
to
saying
this
came
in
the
past.
These
are
not
representative
of
the
values
the
person
has
shown
in
the
project
and
please
refrain
from
personal
attacks.
F
A
Yeah
I
think
that's
that's
something
that
that's
been
communicated
a
number
of
times
is
that
it's
very
difficult
to
hold
people
to
expectations
that
you
didn't
have
explicitly
communicated.
So
you
know,
and
then
there
of
course
right
is
the
problem
that
we
see
is
codifying.
Those
explicit
expectations
can
be
very
challenging
because
people
know
that
once
we
have
them
codified,
you're
being
held
to
them
so
yeah
I'm.
D
A
G
A
You
know
people
to
lead
on
these
messages
as
well.
So
it's
nice
to
see
this
coming
from
the
project
side
to
be
able
to
say
like
this.
Is
you
know
this
is
a
good
step
forward
for
everyone.
So
please,
please,
please
give
input
to
that
folks,
so,
okay,
so
any
other
questions
on
that
I,
just
I'm,
glad
that
folks
are
reading
that
now,
especially.
E
B
F
Yeah,
it's
a
PR
you've
read
he's
free
to
reject
it.
Personally.
I
thought
that
it
would
just
it
would
just
get
accepted
and
sit
in
the
repo
and
nobody
would
ever
notice
it.
Unfortunately,
it
went
more
of
an
escalated
route
and
people
felt
they
needed
to
participate
in
it,
which
was
not
my
expectation
but
yeah.
E
G
A
F
A
Okay,
so
on
to
the
next
agenda
item.
So
the
item
is
issue.
125
email,
Ilyas
is
not
up
to
date
with
a
membership
list.
I
will
share
that
the
only
people
who
ended
up
on
the
email,
alias
were
folks
who
had
explicitly
expressed
that
they
were
okay
with
their
emails
being
on
there,
because
it
is
public.
It
is
published
to
the
repo
yeah.
H
A
F
G
G
A
It's
now,
okay,
so
I
think
the
action
item
from
there
then,
is
just
to
ping.
Everyone
who
is
missing
from
put
a
diff
on
the
email
list
versus
the
active
members
and
reach
out
to
them
to
PR
themselves
on
to
the
email
list
yeah,
because
otherwise,
what
ends
up
happening
is
they
aren't
getting
communications
that
are
private
to
the
calm,
calm
and
not
being
posted
in
public.
So
just
like
their
participation,
okay
and
then
I
think.
A
The
last
item
that
I
had
documented
was
issue
96,
and
so
this
was
just
reporting
back
from
our
user
feedback
initiative
meeting
yesterday,
which
I
think
was
really
productive
and
it's.
This
is
a
really
important
initiative.
So
what
this
essentially
is
in
the
short
is
that
it
is
us
project
managing
and
implementing
more
ways
to
get
clear
feedback
from
the
wider
ecosystem
and
members,
and
that
is
vital
because
we
should
be
making
our
decisions
about
how
we
are
moving
forward
in
the
project
based
off
of
evidence.
A
So
that
is
helpful
and
one
of
the
things
that
we
realized
and
when
we
were
discussing
this
yesterday,
was
that
we
have
a
lot
of
work
in
the
community
committee
in
the
TSC
in
various
parts
of
the
project
and
it's
really
tough
to
get
people
to
do
right.
So
we've
got
people
who
want
to
help
out
in
various
parts
of
the
project.
They
don't
know
how
to
get
started,
and
when
we
come
up
with
things
like
the
user
feedback
initiative,
we
know
it's
going
to
be
really
valuable,
but
we
need
people.
A
So
what
tyranny
and
Michael
and
I
came
up
with
was
that
it
would
be
really
awesome
if
we
did
a
weekly
share
out
by
tweet
or
whatever
social
media.
You
are
using
and
saying
we
need
help
with
X
this
week
right.
So
we
need
help
in
general
with
community
committee
and
the
project,
but
it's
really
nice
to
have
like
an
issue
that
we
can
point
out
and
say
like
we
need
help
with
this.
We
would
love
to
have
someone
to
come
help
us
on
this
particular
thing
right.
A
So
I
could
tweet
and
say
we're
starting
the
user
feedback
initiative.
We're
going
to
be.
You
know,
building
out
surveys
and
a
plan
for
that.
If
you're
interested,
please
let
us
know-
and
that's
just
a
nice
way
to
continue
to
encourage
people
and
also
let
them
know
specifically
what
they
can
help
on.
H
This
whole
thing
is
a
problem
with
selection
bias,
but
Twitter
narrows
our
audience
very
much.
It's
oh
yeah!
It
is
predominantly
in
the
States
and
most
of
my
acquaintances
that
are
not
American
are
not
avid
Twitter
fans,
so
I'm
taking
I'm,
taking
a
lot
of
the
tweets
to
places
like
Facebook
or
different
social
media
channels
right.
A
Yeah,
so
that's
what
I
was
gonna
say
was
that
I
use
Twitter
as
the
example,
but
we
also
like
whatever
social
media
platform
is
useful
to
you
and
your
network
and
helps
connect.
Us
is
what
you
should
be
using
for
this,
so
some
people
will
use
Twitter
because
that's
where
they
live,
some
people
will
use
IRC
chat
right.
A
A
All
right,
well,
okay,
so
is
the
best
way
to
do
that,
like
emailing,
the
community
committee
like
WA
jall,
if
we
do
that
once
a
week,
is
that
reasonable
is
that
obnoxious
is
email.
The
best
way
to
do
that,
I.
E
Don't
mind
you
know
that
that
works
for
me,
but
I
don't
want
to
speak
for
anyone
else.
It's.
C
G
We
even
want
to
think
we
talked
about
Stephen
leicht
tyranny
had
mentioned
he'd
cents.
You
know
periodically
sends
out
just
the
general,
so
you
know
the
general
ones
saying
hey.
We
just
need
help
in
general
yep
and
maybe
rotating
that
across
you
know
it
seems
funny
if
one
person
does
it
every
week,
but
if
we
sort
of
rotate
it
across
the
committee
members
where
each
week
we
sent
one
of
those
out
and
then
kind
of
promoted
it.
That
might
also
be
something
to
to
do.
Yeah.
E
Let
me
give
others
in
the
meeting
a
little
bit
context.
So,
a
while
ago,
I
sent
out
just
the
ask
saying
if
you
want
to
start
contributing
to
note,
please
just
reach
out
to
me
and
I've
had
a
bunch
of
people
reach
out
from
varying
backgrounds,
skill
levels.
You
know
everything
from
you
know
an
entirely
new
beginner
to
people
that
are
experienced
that
are
working
in
large
organizations.
E
E
You
know
I'm
around
the
project,
a
lot
and
so
I
generally
know
those
things
we're
also
working
on
the
getting
started,
repo,
that's
kind
of
trying
to
collect
some
of
that
information
of
where
you
can
get
started,
and
each
kind
of
section
of
the
org
and
so
just
being
able
to
share
that
and
say:
hey
here's.
If
you're
interested
in
doing
Doc's,
you
can
go
to
the
getting
started
or
the
main
repo,
okay,
good
first
contribution,
that's
also
tagged
Docs
or
labeled
Docs.
E
It's
an
easy
way
to
help
someone
get
started
and
like
a
few
of
them
have
already
landed,
commits
and
they're.
You
know
it
was
an
awesome
thing
for
them
to
be
able
to
go.
Do
they
were
excited,
so
it's
a
simple
thing
to
kind
of
low
effort
on
our
end
really
still
was
low
effort.
On
my
end,
it's
an
assumption,
but
it's
not
super
difficult
and
I'm
happy
to
help.
If
anyone
wants
to
kind
of
have
guidance
around
that,
but
it's
a
useful
thing
to
kind
of
get
more
contributions
going
there.
E
H
I
just
want
to
comment
from
the
from
the
core
collaborators
side
that
I
think
we
have
roughly.
Let's
say
one
person
week
was
coming
for
a
second
round
of
tutoring
/
mentoring.
After
doing
their
first
commit,
they
want
to
step
it
up
and
and
that
I
think
that
that
segment
is
a
little
bit
lacking
like
okay.
So
we
have
good
first
contribution.
What's
a
good
second
contribution,
yeah.
H
No
personally,
no
but
I
have
some
PRS
on
the
encore
about
thoughts
and
insights
that
I've
collected
yeah.
A
So
that's
a
follow
up
code
and
learn.
You
know
that
the
original
aim,
of
course,
was
getting
those
good
first
contributions.
It
doesn't
mean
that
it
shouldn't
expand
outside
of
that,
but
and
I
think
there
has
been
discussion
around
like
sort
of
whether
that's
the
appropriate
place
to
continue
that
focus,
but
the
getting
started
doesn't
getting
started
as
a
very
wide
swath,
so
getting
started
can
mean
getting
started
in
node
from
like
not
being
a
programmer
or
being
a
programmer
coming
from
another
language,
it
could
be
getting
started
in
contributing
I
could
be.
A
You
know,
trying
to
move
beyond
that.
First,
getting
started
beyond
that.
First
contribution.
So
if
you
have
ideas
for
that,
that
would
be
awesome
to
document,
because
that's
getting
started
is
more
of
the
place
of
that,
like
those
ideas
and
those
resources
and
then
code
and
learn
right
is
the
implementation
of
that
as
an
event
order
for
contributions,
at
least.
H
E
A
G
A
G
A
Generally,
you
can
DM
the
node
account.
It
is
up
to
the
the
managers
of
the
account
as
to
whether
they
will
retweet
I
will
say
that
so
it's
we
do
have
to
make.
We
try
to
be
careful
just
from
a
strategy
standpoint
with
the
node
account,
because
we
don't
want
to
flood
it
with
so
many
messages
in
a
day
that
so
sometimes
they'll
actually
like.
Sometimes
it
get
spaced
out
a
little
bit
right,
I
just.
A
Yeah
but
yeah
otherwise
yeah
it's
being
paid
attention
to,
and
they'll
try
and
just
retweet
it
anyway.
But
if
you
have
a
specific
ask,
it's
always
good
to
ZM
if
you're
talking
about
Twitter
specifically,
otherwise
we
would
want
to
see
our
well
yeah.
Email,
I
believe
would
be
zippy
and
I
I.