►
From YouTube: Morning Keynote- The Road Forward - Tracy Hinds
Description
Morning Keynote- The Road Forward - Tracy Hinds
"In OSS and the Node.js project, we ask of total strangers to collaborate on a project that we all benefit from. In order for them to feel welcomed and stick around, they should feel like they belong.
To create that sense of welcome, barriers to access and biases must be surfaced. People must feel safe enough to contribute. An inclusive, open-source community will result in better code from a more diverse range of developers. We are making up for a lot of lost time due to systemic failures and biases. In order to actualize this change, it should be reflected in representation at every level of leadership in Node.js. We lead by example. This means finding champions within the Board, within leadership of the working groups, and with role model developers in the community. We'd like to talk about how every person in the community can contribute to this, feel a sense of ownership in the community, and see a road forward."
A
A
I
love
hearing
all
of
the
different
perspectives
that
we
get
to
hear
from
different
parts
of
the
community,
so
you've
heard
bits
and
pieces
of
my
talk
in
the
earlier
talks,
so
I'll
try
and
move
along.
If
I
end
up
covering
things
that
other
people
have
already
covered,
you
know
I
think
ashley
did
a
really
incredible
job
of
sort
of
touching
and
introducing
what
what
we
need
to
do
to
to
start
addressing.
What
I'm
going
to
be
talking
about
as
well
and
know
together
is
a
really
awesome
approach
to
that.
A
So
that
was
a
really
I'm
really
lucky
to
be
part
of
that
lineup.
So
yeah
we're
here
today
to
share
some
stories
and
also
some
meaningful
thought
on
the
story
of
community
that
drives
node,
where
we
are
where
we've
been
and
where
we're
really
excited
to
go,
but
to
get
there.
It
takes
a
lot
more
awesome
people
and
that's
not
only
coming
to
the
project
but
staying
in
the
node
project
in
open
source.
A
To
create
that
sense
of
welcome
barriers
to
access
and
biases
need
to
be
surfaced.
People
must
feel
safe
enough
to
contribute.
An
inclusive,
open
source
community
will
result
in
better
code
from
a
more
diverse
range
of
developers,
we're
making
up
for
a
lot
of
lost
time.
Due
to
these
systemic
failures
and
biases
that
have
happened
for
generations.
A
A
A
So
I'm
going
to
ask
you
to
embrace
that
a
little
more
here
today
and
and
more
so
moving
forward.
So
let's
take
a
deep
breath
and
be
kind
receptive
to
maybe
to
this
talk
and
also
what
we've
heard
today,
because
I
really
want
your
insight.
Other
people
in
the
project
want
your
insight,
if
you're
not
already
contributing
and
that's
a
really
difficult
thing
to
present
here
on
stage.
So
thanks
to
everyone-
that's
done
that
so
far
and
who
will
be
doing
it.
A
A
I
know
some
people
this
might
be
preaching
to
the
choir,
but
I
like
to
make
sure
that
people
know
this,
because
I
don't
like
to
assume
that
anybody
does
so
inclusivity,
as
ashley
had
also
covered
means
feeling
supported,
heard,
wanted
and
needed
in
that.
In
our
context,
it's
also
the
intention
and
policy
policy,
so
official
representation
saying
that
people
should
be
included
who
are
otherwise
could
be
excluded
or
marginalized,
to
create
a
productive
work,
climate
of
trust
and
respect
so
we're
working
together
towards
the
common
goal,
which
is
node
diversity,
means
background.
A
A
It's
about
creating
opportunities
for
everyone,
diversity.
Inclusion
brings
us
all
opportunities
to
learn
and
grow
from
one
another.
So
it's
not
just
the
people
we
want
to
include
so
that
they
can
learn
it's
it's
self-serving.
You
will
also
learn.
We
will
all
learn.
We
all
become
better
with
more
diverse
views
when
we
are
able
to
listen
and
learn.
A
A
Diversity
of
thought,
improves,
project
outcomes,
that's
in
companies,
that's
in
products,
that's
in
open
source
projects
and
we'll
get
left
behind,
there's
plenty
of
organizations
that
are
doing
a
good
job
that
are
actively
being
present
and
deliberate
in
the
work
that
they're
doing
and
we
shouldn't
lose
contributors
to
our
project
because
they
don't
feel
welcome.
That's
silly.
A
So
next
I'm
going
to
talk
about
where
we've
been
so
node
and
I'm
sure
this
has
been
covered,
but
just
to
remind
you,
node
is
seven
years
old
now.
So
yesterday
was
the
anniversary
of
the
release
of
node
version
400,
which
combined
both
the
node
project
and
the
io
project
into
a
single
code
base
under
the
direction
of
the
node
foundation.
A
So
it
turned
into
this.
You
know
this
small
group
of
folks
who
are
really
nerding
out
on
a
really
neat
project
and
it
started
turning
into
a
bigger
global
group
of
folks,
the
first
node
conf
community
conference
happened
filled
with
a
lot
of
new
discoveries
and
smaller
burgeoning
communities
coming
together
and
really
getting
us.
You
know
to
discover
different
ways
that
we
could
use
this
new
thing.
You
know
how
many
people
have
been
able
to
make
lights
blank
thanks
to
nodebots.
A
Eventually,
giant
ended
up
stepping
up
as
the
corporate
steward
of
node.
We
ended
up
seeing
larger
traction
communities
such
as
node
school,
which
started
in
2013.
again:
nodebots
helped
grow,
we've
seen
node
together.
You
know
pulling
in
these
really
awesome
communities
that
you
may
not
even
experience
on
a
regular
basis,
but
they're
there
and
they're
doing
really
awesome
positive
work.
A
So
in
most
of
these
moments
in
our
history
so
far,
and
when
I
say
history,
it's
community
because
we're
you
know,
we've
got
some
really
awesome
experts
here
who
can
speak
more
to
the
code
side
of
things
and
there
were.
There
were
a
lot
of
small
groups
in
this
history.
So
far
you
know
the
contributors.
It
was
pretty
small,
especially
when
you're
talking
about
core
the
steward
and
bdfl's,
which
is
benevolent
dictators
for
life
which
don't
end
up
being
for
life.
A
So
the
tyranny
of
structurelessness
is
a
really
interesting,
six-page
essay.
That
was
a
fairly
strong
reaction
to
the
idea
of
the
rigidity
of
structure.
So
that
is
generally
the
idea
that
groups
are
working
on
something
and
they're
working
on
something
like
they
really
want
things
to
get
done.
It
can
be
in
communities
such
as
like
political
communities.
A
It
can
be
in
your
neighborhood,
it
can
be
a
tech
community,
but
every
this
this
group
has
a
common
goal
and
a
lack
of
heavy
organization
and
process
early
on
was
pretty
integral
to
to
node
code
and
community
events
happening.
The
downside
to
that,
though,
is
that
as
the
as
the
platform
matures
again,
that
lack
of
structure
can
end
up
slowing
things
down
or
discouraging
people
who
are
really
excited
to
help,
but
do
need
resources,
so
I
highly
recommend
checking
out
the
tyranny
of
structurelessness
yeah.
A
I
do
want
to
say
that
when
you
see
these
screens,
I
do
want
you
to
pay
attention
to
the
disclaimer
on
the
bottom
right
corner.
We
have
some
really
awesome
historians
in
our
community.
I
am
probably
not
one
of
them
and
I'm
looking
forward
to
input
on
these
afterwards.
So
thank
you
just
make
sure
that
it
is
kind,
and
so
it
worked
like
early
on
this
lack
of
process.
A
This
lack
of
structure
worked,
but
by
allowing
ourselves
to
deny
official
leaders
really
in
in
any
capacity
you
end
up
getting
de
facto
leaders
who
end
up
driving
every
portion
of
your
community
and
that
can
include
whether
you're
paying
attention
to
retention,
which
is
a
very
official
word,
but
it's
like
whether
people
want
to
stay
or
go
or
go.
Try
another
language.
A
A
They
are
absolutely
judging
the
experience
of
the
community
based
on
those
things
so,
and
those
are
people
who
have
potentially
never
contributed
or
they've
contributed
in
the
past
and
they
didn't
feel
really
welcome
or
they
are
currently
contributing
and
they're
on
edge.
So
collaboration
is
a
skill,
so
is
dealing
with
people
that
doesn't
mean
you.
A
You
can't
learn
to
get
better
at
it
and
I
highly
recommend
it
because
it's
good
for
your
career
as
well
as
your
spirit,
and
I
like
to
say
it's
also
it's
it's
good
for
getting
along
with
your
coworkers.
Most
of
us
need
jobs,
and
it
turns
out
that
anybody
who's
working
with
someone
else
in
open
source
that
is
working
even
if
it's
something
that
you
enjoy
doing
in
your
spare
time.
You
are
collaborating
so
maybe
consider
that
the
people
that
you're
communicating
with
you
should
communicate
to
them,
like
you
would
a
co-worker
like.
A
Would
you
get
fired
for
something
that
you
just
said
to
them
on
github?
Would
you
be
pulled
into
an
office
because
your
co-worker
is
really
tired
of
being
treated
like
that
on
a
daily
basis
that
sort
of
thing
so
oh
yeah?
I
should
also
I
should
explain
this
a
little
bit.
So
these
are
really
goofy
illustrations
and
I
had
some
fun
with
rod,
trying
to
talk
about
like
how
you
how
you
explain
these,
because
they
just
get
you'll,
see
the
how
complicated
they
get
really
quickly.
A
A
A
Joint
was
very
invested
right
and
these
are
a
lot
of
the
smaller
companies,
so
I
should
have
had
lots
of
dots
on
the
outside
too,
because
there's
tons
of
people
not
using
node,
it's
fine
so
and
here
what
we've
got,
which
again
probably
inaccurate,
you've
got
no
during
the
fork
and
so
we've
got.
You
know:
we've
got
node
with
joint
over
here
companies
just
doing
their
thing.
A
They
just
want
to
write
node
they
don't
they
don't
really
want
to
know
anything
about
our
community
conflicts
and
then
we've
got
I
o
over
here,
which
is
like
you've
got.
You
know
a
lot
of
activities
starting
to
happen
over
here,
so
you've
got
people
who
were
contributing
to
core
who
are
helping
build
iojs.
A
You
end
up
getting
these
cool
things
that
are
happening
with
working
groups.
So
now
more
people
really
all
of
a
sudden
you're,
seeing
a
lot
more
people
feeling
agency
to
get
to
contribute
and
that's
really
exciting,
but
so
much
of
where
our
negative
experiences
that
have
occurred
have
been
communicating,
or
you
know,
communication
problems
in
general.
A
We
can't
underestimate
how
vital
other
humans
are
and
the
need
for
them
to
know
what's
going
on,
if
we
don't
give
folks
time
to
process
preparation
via
communication
at
any
means,
when
someone
finally
does
discover
the
information,
they
are
getting
surprised,
lots
of
people,
don't
like
surprises,
they
don't
they,
don't
they
don't
absorb
them?
Well,
so
we
had
the
fork.
A
The
fork
didn't
happen
because
people
didn't
get
along.
There
were
people
who
were
contributing
again
to
both.
So
there
were
a
lot
of
processes
that
we
had
set
up
and
I'm
using
the
royal
we
here
so
bear
with
me
to
try
and
help
ensure
a
high
quality
code
base.
It
turns
out
that
we're
always
learning
and
processes
can
get
in
the
way.
A
So
they
can
also
be
changed
by
folks
proving
to
test
out
the
new
processes
which
you
know
was
sort
of
the
mo
of
I
o,
which
was
you
know,
pretty
cool.
So
that's
where
we
were
now.
I
want
to
talk
about
where
we
are
so
we
have
the
cara
meter
and
the
cure
meter
to
me
is
sort
of
a
reflection
of
community
capacity.
A
A
We
have
to
be
able
to
promote
or
sustain
the
well-being
of
the
community
and
its
components,
and
that
includes
individuals
that
includes
informal
groups,
organizations
as
a
whole
social
interactions,
the
physical
environment.
All
of
these
things
are
really
important
to
someone
being
able
to
feel
like
they
are
able
to
contribute,
have
ways
that
they
can
see
that
they
can
contribute
and
then
have
the
time
to
do
it
so
that
ends
up
you
know
being
sort
of
like
in
a
way.
A
What
well-functioning
communities
are
it's
their
ability
to
have
that
capacity,
so
capacity
development
is
a
process
of
change
and
hence
is
also
about
managing
transformations
which
we're
really
trying
to
do
here.
So
people's
capacities
and
institutional
capacity
and
society's
capacity
capacity
change
over
time
and
a
focus
on
what
development
policies
and
investments
work
best
to
strengthen
the
abilities
network,
skills
and
knowledge
base
cannot
be
a
one-off
intervention.
A
So
what
is
our
community
capacity?
This
is
something
that
I've
spent
a
lot
of
my
recent
time,
considering
because
when
you
think
about
what
the
community
capacity
is
or
isn't,
then
you
have
to
figure
out.
The
next
step
is:
how
do
we
fix
that?
Because
I
don't
want
to
find
out
our
community
capacity
isn't
great
and
then
just
sit
on
it.
So
there
you
go.
The
cure
meter
is
in
a
very
interesting
place
right
now,
so
we
keep
seeing
ourselves
hit
walls
in
node,
and
I
mean
that
in
the
community
sense.
A
A
A
So
sort
of
talking
about
where
we
are
now,
it's
very
complicated
right.
So
this
is
also
super
inaccurate
and
this
was
the
fun
the
one
that
rod
and
I
were
laughing
about
a
lot.
So
I
like
to
show
this
just
to
show
how
complicated
it
is.
So
this
is
not
the
I'd
love
input
afterwards,
so
that
we
can
have
a
form-
that's
publishable,
so
yeah.
A
So
we
have
all
of
these
groups
that
are
working
together
and
I
don't
really
like
the
ends
of
these
circles
existing
just
because
it's
not
really.
It's
there's
a
lot
of
blurry
lines
here
of
people
who
you
know
don't
even
want
to
say
necessarily
they're
they're
not
like
identifying
with
the
node
community
but
they're,
absolutely
a
part
of
it.
So
you
have
you
know
all
the
working
groups
with
the
court.
A
You
know
ctc
and
tsc
over
helping
oversee
the
project,
and
you
know
we've
got
the
the
board
of
the
node
foundation
and
the
linux
foundation.
Helping
us
out
and
you've
got
the
execs,
which
should
really
be
much
tinier,
because
just
me
and
michael
and
and
so
this
is
really
just
like
looking
at
this-
I'm
showing
you
all
of
this
lead
up
is
to
talk
about
how
complicated
it
is
for
a
project
to
exist,
but
that
also
as
part
of
all
of
this
process.
This
is
how
complicated
it
had
to
get.
A
A
This
is
a
lot
of
people,
but
it's
also,
you
know
small
groups
of
people,
and
what
are
we
all
trying
to
do
so
now
is
the
time
to
recognize
the
awesome
and
and
make
them
feel
that
sense
of
agency,
but
we
also
have
to
start
giving
a
lot
of
thanks
to
people
and
and
make
sure
to
do
something
like
setting
up
a
system
to
give
thanks
publicly
and
watch
a
new
phase
of
growth
take
place.
But
all
of
that
cannot
happen
without
fixing
inclusivity
and
diversity
in
the
programming
language
community.
A
So
yeah,
what
are
we
trying
to
do
in
order
to
improve?
We
have
to
admit
faults,
not
just
the
faults
of
what
we
have
taken
responsibility
for
in
the
past,
but
also
for
the
larger
world
around
us,
which
you
know
we
want
to
make
better.
So,
as
as
ashley
said,
the
tech
community
has
a
major
diversity,
an
inclusivity
problem.
Those
are
two
different
things,
but
have
to
go
hand
in
hand
and
node
especially
does
right.
A
A
So
the
idea
here
is
that
you
know
it's
sort
of
the
classic
like
project
manager,
thing
where
like
how,
when
we
look
towards
the
future-
and
I
want
to
say
like
whether
I
failed
at
something
or
not-
I
got
to
lay
the
lines
first,
so
we
got
to
know
like
how
many
people
are
in
the
node
community.
Overall,
that's
a
hard
thing
to
say
we're
a
really
awesome
global
group
of
people
and
it's
hard
to
to
even
connect
to
everyone.
A
So
that
was
something
you
know
with
the
node
live
events
that
we've
discovered
traveling
the
world.
We
we
have
not
been
as
connected
as
we
need
to
be,
and,
and
that's
awesome
that
we've
been
able
to
have
that
opportunity.
We
need
to
go
further
with
it.
So
we'll
have
to
look
to
that
moving
forwards
of
having
these
measurable
goals
having
ways
to
say
like
okay,
great,
we
have,
you
know
five
percent
of
all
node,
you
know
community
people,
not
just
core
contributors
are,
you
know,
are
from
underrepresented
groups.
A
I
don't
know
that
number.
We
don't
have
that
number,
but
what
I'm
saying
is
like
we
know
it's
going
to
be
a
low
number
and
I
want
to
see
it
grow.
I
also
want
to
see
it
grow
over
time,
so
a
community
thrives
on
the
diversity
of
its
population.
It's
clear
from
scientific
research
that
diverse
groups
of
people
outperform
homogeneous
teams.
A
As
I
said
before,
project
outcomes
are
improved
when
differences
in
communication
styles
are
properly
managed.
Common
challenges
unite
us,
but
without
access
to
the
ideas
and
experiences
of
a
wide
range
of
people,
the
promise
of
communal
solutions
will
continue
to
elude
us,
so
now's
the
time
it
was
a
luxury
for
us
to
be
able
to
not
address
the
problems
that
other
communities
and
companies
in
tech
had
been
facing.
People
wanted
the
platform
and
could
turn
the
other
way
early
on
because
they
wanted
the
project
to
happen.
A
Establishing
the
platform
is
where
the
energy
was
being
funneled,
but
so
how
do
we
even
measure
that
we
have
a
place
to
start
to
know
where
we're
going
publishing?
You
know
something
like
you've
seen
all
these
companies
do
these
like
diversity,
you
know
projects
and,
unfortunately,
they're.
I
would
say,
unfortunately,
it's
unfortunate
for
them
because
they
get
reamed
for
it
the
next
year,
but
they
release
their
reports
and
it's
the
numbers
still
don't
look
great.
It's
like
it's
really
hard
to
hire.
A
So
it
also
takes
way
more
community
members
feeling
a
sense
of
agency.
Remember
the
idea
of
community
capacity.
So
how
do
we
encourage,
educate
and
be
diplomats
of
the
community
working
together
in
these
places?
So
what
we've
done
is
sort
of
looking
at
the
long-term
outlook
with
short-term
goals.
We
need
to
establish
that
so
the
tsc
individuals
in
the
community,
the
board
and
the
executives
are
all
looking
at
moving
responsibilities
of
the
inclusivity
working
group
which
we
had
heard
about
earlier.
A
So
what
does
that
mean
figuring
out
the
conflict
of
interest
issues
figuring
out?
Why
the
model
that
was
applied
to
the
inclusivity
working
group?
Didn't
work
moving
it
out
of
that
model
so
that
we
can
address
the
changes
quicker.
That's
the
things
that
we're
looking
to
do
so
again.
Sometimes
we
have
to
look
through
the
processes
we
created
in
the
past
to
make
sure
that
they're
still
helping
us
move
forward.
A
In
this
case,
I
think
a
lot
of
us
agree
that
it's
time
for
change,
so
can
we
recruit
folks
within
the
community
groups,
to
help
us
make
this
positive
change?
How
do
we
help
these
communities
feel
a
sense
of
responsibility
for
the
larger
system
because
it
has
to
come
from
the
community
members
themselves?
A
You
can't
just
have
someone
from
on
high
coming
and
saying,
like
that's,
not
cool,
because
if
the
rest
of
the
community
thinks
that
it's
cool
turns
out
the
individuals
who
are
upset
about
it
like
they're,
going
to
feel
other,
that's
a
problem,
so
you
know
what
can
we?
What
groups
can
we
be
looking
at
to
sort
of
like
address
these
issues?
So
we've
got
the
tsc,
the
ctc.
A
You
know
the
working
groups
online
communities,
things
like
irc
github,
so
you
know
you're
talking
about
things
like
moderation,
which
in
itself
is
a
working
group.
You
know,
irc,
surprisingly,
you
know
the
node
channel
in
irc.
The
has
been
you
know,
code
of
contact
and
moderating.
It
has
been
worked
on
for
a
really
long
time
and
I
it's
it
surprises
me.
How
behaved
people
are
in
that?
It's
it's
actually
a
place
that
people
can
go
to
get
questions
answered,
albeit
there's
everyone
asking
lots
of
questions
in
there.
A
So
it's
it's
nice
to
see
that
that
can
happen.
But
then
why
isn't
that
happening
on
somewhere
like
github
and
like
we?
Don't?
You
know
we're
not
really
having
a
central
presence
on
slack.
So
you
know
we
can
look
at
the
node
foundation,
individual
members,
the
corporate
members,
to
look
and
see
how
they
would
also
like
to
you
know:
do
this
really
looking
at
examples
of
communities,
things
like
node
live
and
node
school
and
nodebots
and
node
together
and
node
girls?
A
You
know
we
want
to
raise
up
people
that
are
doing
really
awesome
things
and
you
know
reflect
on
the
contributions.
They've
had
to
the
community,
we
can
do
things
like
you
know,
suggested
ideas
or
things
like
you
know,
coaching
for
people
who
are
trying
to
run
community
events
such
as
like
maybe
make
sure
that
the
panel
that
you're
gonna
see
has
you
know
a
diversity
of
thought,
maybe
not
all
the
same
company,
maybe
not
from
all
the
same
background.
A
That
would
be
really
nice
and
not
only
nice,
but
maybe
it
should
be
a
requirement
helping
to
encourage
new
events
for
to
happen,
especially
around
things
like
workshops
to
teach
or
help
improve
programming
skills,
making
sure
that
those
spaces
are
safe
spaces
that
encourage
confidence
and
integration
into
the
larger
community,
and
that
also
teach
folks.
You
know
things
like
how
to
be
an
ally.
You
know
there
are
group,
the
linux
foundation.
Does
this
for
other
projects.
A
A
A
We
have
to
be
better
about
communicating
to
the
ecosystem
as
well
as
educate,
so
that
they
expect
and
understand
the
values
that
we
have
as
a
community.
You
know
enlist
community
volunteers
to
attend
and
validate
provide
feedback
related
to
community
efforts
and
projects.
We
want
to
provide
opportunities
for
community
members
to
learn
about
moderation,
to
give
perspective
and
to
share
feedback.
A
You
know
they
aren't
happy
with
the
current
state
of
things
and
give
them
the
opportunity
to
give
you
feedback
and
if
they
don't,
you
know,
if
they
don't
have
a
solution.
That's
okay,
too!
Sometimes
people
just
need
to
vent,
and
you
know
other
things
like
the
weekly
newsletter,
which
will
be.
You
know
a
really
exciting
opportunity
that
we've
seen
you
know
prior
in
our
community
and
that
lets
people
know
what's
going
on
in
parts
of
the
ecosystem
as
well.
As
you
know,
taking
ownership
for
some
of
the
tough
stuff
that's
going
on.
A
You
know
this
is
the
node
community
sort
of
people
stepping
into
it,
seeing
like
what
the
heck
you
know
are
we
like,
because
people
will
read
things
in
the
news
and
that's
not
necessarily
like
a
great
way
to
communicate
what
our
values
are.
So
you
know
this
is
what
we
believe
is
how
people
interact
in
the
community
are
expectations,
so
we
can
also
bring
in
experts.
So
we
aren't
experts
in
a
lot
of
things,
though
we
like
to
think
so.
A
I
have
training
in
conflict
resolution
and
mediation,
but
that
doesn't
mean
that
I'm
an
expert
in
it,
so
I
would
say
you
know,
help
bring
in
people
that
do
know
what
they're
doing
to
let
us
know
what
we're
doing
is
useful
or
not
and
find
out
the
blind
spots
so
that
we
can
provide
things
like
training
and
education
so
that
the
leaders
of
the
community
can
help
disseminate
and
share
this
awesome.
You
know
work
that
we
need
to
do.
A
And
lastly,
you
know
things
like
moderating
the
moderators.
How
do
we,
you
know,
give
the
community
a
sense
of
urgency
and
responsibility
for
this?
Let
them
own
it.
You
know
things
like
communal
wow,
community
selected
enforcing
this
is
an
idea.
This
is
not
happening,
so
I
would
love
to
hear
feedback
on
this.
It's
not
happening
yet.
The
idea
of
increasing
trust
and
holding
community
members
accountable
is
something
that
we
have
admitted.
We
have
floundered
in
so
an
example
of
ways
that
communities
have
tried
to
solve.
This
is
a
community
police
enforcement
board.
A
So
when
reports
are
found
to
have
conflicts
of
interest
they're
sent
to
the
civilian
community,
which
would
be
this
board
for
decisions
regarding
misconduct,
anything
regarding
moderation
would
like
need
to
be
a
separate
proposal.
Because
moderation
is,
you
know,
a
separate
working
group,
but
this
is
sort
of
the
idea,
so
it
turns
out
most
people
don't
feel
comfortable
and
supported
if
they
don't
know
who
they
are
reporting
problems
to
part
of
the
problem
with
moderation
and
node.