►
B
E
C
A
C
Awesome
so
hello,
everyone
and
thank
you
for
coming
to
today's
community
committee
meeting.
We
have
a
suite
of
new
observers
from
the
working
group
at
node
interactive,
so
we're
gonna
go
down
the
list.
I
guess
my
list,
cuz
I
know
what
changes
for
everyone
as
you're
talking,
so
that
we
we're
using
zoom
this
time
instead
of
hangouts.
So
it
might
change.
But
I'll
go
down
my
list,
so
I'm
CUNY
siren
developer
advocate
at
notes,
source
and
I'm,
a
co-chair
with
Rachael
of
the
Tracy
you're
next
hi.
A
B
C
C
C
H
I'm
Ben
I
am
a
developer
for
a
small
start-up
health
startup
company
right
now.
I
also
did
a
lot
of
music
in
the
web.
Stuff
and
I
lead
a
few
meetups
here
in
town,
specifically
PDX
node.
So
I
did
a
lot
of
sort
of
ground-level
getting
people
into
node
stuff
at
the
moment
and
really
excited
to
be
here.
C
C
J
C
L
C
N
O
Everybody
dance,
Aisha,
no
Jess
at
large
I'm
an
observer
and
been
sort
of
helping
bootstrap
a
couple
things.
User
feedback
is
something
that
I'm
interested
in
helping
out
on
and
I've
been
encouraging.
Folks
from
and
of
the
enterprise
community
that
that
haven't
felt
like
they
had
a
way
to
interact
with
the
the
foundation
leis
to
come
and
collaborate
in
the
kumkum
and.
C
C
B
C
C
G
C
A
So
hi
again
this
is
Tracy.
I'm
gonna,
see,
let's
see
if
the
share
screen
doesn't
get
a
little
wonky
with
this
fun
setup
that
we've
got
going
on.
M
A
So,
first
of
all,
I
want
to
say
hi
to
any
and
all
observers
we
like
to
use
the
observer
status
as
a
way
to
become
a
member
for
the
community
committee,
because
when
it
comes
to
contributions
clearly,
because
our
work
is
mostly
outside
of
code
within
a
project
in
the
community,
we
have
to
have
other
ways
of
being
able
to
allow
you
to
contribute.
So
code
does
not
equal
contributions
when
it
comes
to
community
committee
and
so
welcome.
We're
really
excited
for
anybody
and-
and
you
can
also
observe
meeting.
So
what
will
happen?
A
What
we
often
have
happen
as
well
as
well,
have
visitors
from
other
parts
of
the
project
or
from
the
ecosystem,
who
are
providing
us
guidance
and
they'll
visit
for
a
single
meeting.
But
if
you'd
like
to
keep
returning
being
marked
as
an
observer,
is
a
way
that
you
can
build
up
to
becoming
a
member.
We
actually
have
that
in
our
documentation
for
how
you
end
up
building
up
to
becoming
a
member
of
our
community,
and
so
you
can
actually
see
here
in
the
community
committee.
We
have
our
governance
document.
A
Which
is
probably
just
not
a
good
idea
for
me
to
do
this:
okay,
sorry
and
I.
What
I
would
recommend
is
first,
is
if
you're
interested
in
and
helping
out.
We
don't
have
too
many
documents
right
now,
but
the
governance
doc,
the
contributing
doc
and
the
collaborator
guidelines
are
I
think
not
too
long
and
a
great
way
to
get
to
see
sort
of.
What's
going
on
in
the
path
to
to
a
member,
and
of
course
we
want
to
recognize
that
we
have
a
code
of
conduct.
A
A
For
for
those
who
are
interested
in
becoming
in
participating,
you
can
you
don't
have
to
be
a
member
to
participate
right,
you're
here,
you're
talking
you're
filing
issues,
you're
filing
PRS,
you
don't
have
to
be
a
member
to
do
any
of
that,
and
we
welcome
any
contribution,
especially
when
you've
asked
for
help,
because
we
love
to
be
able
to
provide
context
if
you're
missing
that.
So
a
good
way
to
look
at
things
that
you
might
want
to
hop
into
are
our
issues
section.
A
So
we've
got
Help,
Wanted
and
good
first
issues
as
labels
here
in
our
issues
and
we're
certainly
trying
to
look
and
see
how,
as
we
add,
more
issues
on
a
regular
basis,
it's
good
for
us
to
look
to
see
what
those
good
first
issues
are,
because
that's
a
great
way
for
you
to
help
contribute.
Usually
it
means
that
we've
provided
enough
context
that
you
can
hop
in
and
get
started.
A
But
if
you
have
questions
my
recommendation
is:
is
anyone
who
has
already
participated
in
in
that
issue
in
particular
or
who
has
filed
the
issue
or
pull
request?
It's
a
great
opportunity
for
you
to
ping
them
for
guidance,
and
that
can
be
I
believe
in
our
sorry
I'm
trying
not
to
keep
this
too
long-winded.
Yeah.
C
A
We
have
ways
for
you
to
be
able
to
contact
existing
members.
If
you
have
questions
you
know,
we
have
our
github
identities
as
well
as
email
addresses.
I
am
also
available
on
Twitter
for
dm's.
That
folks
need
me
and
I
think
the
number
of
other
members
are
as
well,
but
obviously
since
we
have
our
emails
listed,
that's
probably
the
first
line
of.
If
you
have
a
question
and
I
think
that's
that.
C
C
C
You,
okay,
awesome
I
will
leave
a
note
on
this
issue
there
for
me
as
well
to
follow
up
with
you
Adam
cool,
so
next
item
on
the
agenda.
This
is
an
item
that
I
think
Michael
Michael
has
given
us
context
on
in
the
past,
but
it's
the
documenting
expectations
on
the
GSA
and
Kham
Kham
members,
so
Michael
I
know
we've
kind
of
heard
from
you
on
the
past
on
this.
Could
you
give
us
kind
of
a
brief
description
and
then
where
it's
at
now
and
what
we
need
to
do
to
move
forward?
Yeah.
G
Absolutely
so,
basically,
you
know
the
the
goal
is
to
formalize
expectations
and
expectations.
We
think
we're
kind
of
already
there,
but
to
make
it
clear
that
you
know
we.
We
have
a
higher
level
of
expectation
on
the
people
who
take
up
the
leadership
positions
across
the
project.
G
So
this
is
a
first
attempt
to
document
what
they
are.
You
know
they're
they're
things
like
being
a
good
example
for
the
you
know
the
rest
of
the
the
community.
G
You
know
I,
don't
think
I
want
to
go
through
exactly
everything,
that's
there,
but
you
know
they're
there
as
a
as
a
first
cut
at
you
know
what
those
expectations
are.
It's
been
out
there
for
actually
quite
a
long
time.
The
next
step
is
for
it
to
land.
There
are
a
number
of
you
know,
six
or
seven
lgt
M's,
no,
currently
outstanding
objections
and
I
think
you
know
for
this
group.
It's
it's
kind
of
the
last
call
to
get
in
there
and
comment.
Otherwise.
You
know
my
plan
is
to
land
it
tomorrow.
C
C
So
with
that
I
know
both
Richard
and
I
need
to
review
it,
and
you
know
anyone
else:
it's
either
participating
as
a
member
or
an
observer.
We
would
like
to
get
your
feedback
on
that
document
specifically,
so
you
don't
need
to
be
shy
about
it.
You're
welcome
to
contribute
and
share
your
thoughts,
we'd
love
to
have
it
and.
G
I
guess
a
lot
as
well.
Like
you
know,
this
is
not
the
final
version
right.
This
is
just
the
initial
version.
You
know
my
preference
is
to
get
something
landed
and
then
you
know
iterate
from
there.
So
you
know
if
you,
if
you
ful,
fully
object
to
what's
there
then
hey,
we
should
do.
We
should
block
and
stop
doing
that.
G
E
G
C
C
O
Something
that
I've
been
very
inspired
from
you
know
interacting
with
the
kubernetes
community,
as
they
defined
some
of
these
and
laid
down
some
of
these
things
they
brought
with
them
this.
You
know
very
healthy
expectation
that
they
were
gonna,
get
things
wrong
and
they
were
going
to
work
to
improve
that
over
time.
O
F
A
G
E
C
B
B
This
sort
of
thing
I've
put
out
calls
on
Twitter
for
more
people
to
see
if
they're
interested
in
it
and
I
think
that
we're
really
at
the
point
where
we
need
to
actually
finally
start
taking
some
action
items
towards
you
know
breaking
those
people
into
working
groups
and
figuring
out
the
best
way
to
tackle
it
and
like
what
are
the
best
ways
to
you
know:
move
forward
with
the
actual
working
groups.
Tracy
and
I
have
briefly
discussed.
B
Looking
at
the
demographics
of
the
active
languages
that
are
used
from
countries
that
are,
you
know
not
not
native
English
speakers
and
I
know
that
we
have
there's
at
least
three
or
four
different
languages
represented
for
people
that
are
volunteering
to
help.
So
I
also
want
to
say
that
I,
ideally
in
the
past,
we
just
discussed
issues
and
said
what
we
need
to
do
with
them.
But
we
haven't
really.
You
know
taken
the
initiative
to
just
cuz
everything's.
It's
been
extremely
busy
4-node
the
past
few
months,
so
what
I
would
like
to
do?
B
Is
I
I've
volunteered
to
help
organize
the
internationalization
working
group.
I,
unfortunately,
can
only
speak
English,
but
if
anyone
else
is
interested
in
helping
me
out
by
the
next
meeting
in
two
weeks,
which
will
be
during
note
convey
you
so
that's
gonna
be
difficult.
I
would
really
like
to
help.
I
would
like
to
have
some
help,
making
a
list
of
all
the
people
that
said
that
they
were
interested
in
working
on
the
internationalization
working
group
figuring
out
what
what
skills
that
they
have
with
previous
internationalization
efforts
and
figuring
out.
B
What
exactly
we
want
to
focus
on
first
like
if
there's
something
that
should
be
translated
before
other
sections,
which
is
just
you
know,
maybe
even
ojs
website,
maybe
the
documentation
may
be
read
meas
for
different
working
groups
under
the
node.js
organization.
I
would
like
to
see
if
anyone
would
like
to
help
do
that.
Is
there
anybody?
That's
interested
in
this
sort
of
thing.
F
F
F
B
L
I
would
also
suggest
dropping
into
the
individual
node
repos
for
each
language.
You
can
look
at
the
graphs
when
you
look
at
the
overall
repos
and
you
can
see
which
ones
have
activity
greet
and
drop
in
there
and
just
leave
a
message
because,
like
Korea,
for
example,
Korean
is
actually
active
and
participate
in
other
parts
of
the
org
yeah.
B
L
C
A
A
F
Because
there's
been
one
touch
base
about
it,
but
at
the
at
node,
interactive
I
mentioned
possibly
reaching
out
the
translation
team
at
LinkedIn
about
donating
translation
services
to
the
node
projects.
In
some
capacity,
I
spoke
with
the
head
of
translations
at
LinkedIn
about
that
it
seemed
very
interested
and
curious
to
explore
it
more.
It
would
require
more
details,
couple
work
and
help
get
that
together
and
see
if
you
can
explore
that
yeah.
B
That
would
be
super
helpful.
Also
I,
don't
know
about
how
linked
and
oh
no
I
lost
my
chat
window.
I,
don't
know
how
LinkedIn
does
it
compared
to
Microsoft,
but
do
you
have
access
to
all
of
the
Microsoft
teams
or
staff,
or
are
you
separate
from
us
I
I.
B
O
There
are
three
events
halves
of
this
jeaious
comp,
asia,
node
fest,
and
it's
the
time
of
the
year
for
play.
Node
though
I
haven't
seen
the
announcement,
yet
it's
Korean
a
node
conference,
so
be
a
great
opportunity.
If
we
can,
you
know
kind
of
see
those
things
up.
We
have
people
I
know.
Myles
is
heading
there
to
dance
comp,
Asia
I
believe
that,
can
you
know
some
carry
the
baton
and
work
with
folks,
locally
yeah.
C
I
know
Myles
is
also
doing
a
values
session
at
Discogs
Columbia,
and
so
that
might
be
another.
We
just
reach
out
to
miles
on
that
cool.
Okay,
let's
see
here,
I'm
making
sure
I
have
okay,
so
done
with
the
mark
on
the
internationalization
and
localization
working
groups.
So
no
Jia's
user
feedback
project
planning
Tracy.
Do
you
want
to
take
this
one?
It's
it's
still
on
the
agenda.
I
know:
we've
talked
about
it
previously.
I
know:
we've
had
interest,
you
know.
A
So
what
I
would
like
to
see
I
think
we've
seen
activity
from
Dan
as
well
as
James
now
I
know
that
Michael
settler
had
been
done.
He'd
also
like
to
help
out
so
I
think
that
we've
already
got
some
stuff
going
on
I.
Think
behind
the
scenes.
That's
gonna
happen.
That's
an
absurd
fishing
in
a
more
formalized
project,
moving
forward,
but
the
user
feedback
initiative.
So
we've
got
that
issue,
but
I
would
love
to
see
you
all
kind
of
take
the
next
steps
with
that.
A
So
we've
got
notes
from
our
initial
meeting,
but
because
all
of
the
energy
I
think
that
is
moving
forward
with
this
is
from
other
folks.
A
next
meeting
might
be
a
good
thing,
because
that's
the
user
feedback
initiative
in
itself
is
such
a
large
project
that
we
were
talking.
A
collab
summit
about
we've
had
a
couple
people
step
forward,
offering
their
project
management
skills.
They
are
professional
project
managers
by
career
experience
and
that's
something
that
we
desperately
need
within
across
the
project,
but
especially
with
things
like
user
feedback
and
initiative.
A
A
Dan
then,
like
that's
great,
then,
because
I
know
that
again
what
we
heard
in
feedback
during
node
interactive
was
that
a
lot
of
the
people
who
want
to
engage
with
parts
of
the
user
feedback
initiative,
don't
really
work
in
github
and
that's
that's
great,
that's
fine,
and
that
means
that
we
can
bring
in
more
people
by
connecting
in
other
ways.
We
just
need
to
have
a
way
to
report
back
in
github,
for
transparency
sake
right.
O
And
my
biggest
asked
there
is,
please
assume
ignorance,
not
malice.
If
you
don't
see
things
coming
in
the
expected
channels,
you
know
I've
been,
you
know,
posting
a
bunch
of
issues
into
the
TSC
and
various
other
areas
and
definitely
noticed
a
lot
of
the
areas
where
folks
would
expect
yeah.
Of
course
you
are
always
in
github
all
day
too,
and
you
know
the
reality
is
no
running
my
mouth
somewhere.
O
Gathering
with
Mike
and
and
William
immediately
after
this
session,
so
if
you're
really
interested-
and
you
want
to
engage
in
kind
of
organizing
the
the
meeting
and
doing
what
Tracy
was
saying-
a
really
kick
starting
that
the
process
again
here
I,
you
know,
raise
your
hand
and,
and
please
join
us,
and
you
know
we'll
try
to
get
the
media
announcements
and
a
regular
meeting
page
and
set
up
and
on
the
the
calendar
and
in
the
the
Comicon
repository
for
everyone
to
join
in
soon.
Is
that
been
Michael
that
you're
talking
to.
G
O
O
Maybe
a
little
strong,
but
you
know
starting
to
talk
about
what
you
know
what
the
needs
are
and
yeah
I
think
we
may
have
a
fairly
daunting
scope
of
work
ahead
of
us
in
that
you
know,
what's
been
laid
out
there
and
you
know
trying
to
map
that
to
available
time
and
effort
and
prioritize
put
some
of
that
project.
Every
stuff
took
to
work
and
see
how
we
can
break
things
down
into
something
that
we
can
make
meaningful
progress
on
right.
G
Figure
that
out
and
get
back
to
us,
the
other
thing
is
like
that.
That
meeting
is
the
focus
of
that
of
figuring
out.
You
know
how
you
guys
are
gonna
push
it
forward,
or
is
it
actually
start
to
talk
about?
You
know
if
somebody's
interested
in
just
participating
but
not
leading
it,
should
they
join
that
meeting?
After
probably
not
know.
A
Also
I
think
to
clarify
too
is
what
I
think
what
Dan
is
talking
about
is
a
facet
of
the
user
feedback
initiative.
It
is
not
the
entire
initiative,
so
you
know,
we've
got
a
take
off
bites
little
bites
at
the
elephant,
because
this
has
been
needing
to
happen
for
years,
so
Dan
is
running
with
one
of
those
facets.
Another
one
that
was
mentioned.
I
think
that
Raphael
is
really
good.
A
C
So
this
is
probably
a
good
way
to
get
started
on
that
survey
stuff.
If
anyone
else
is
interested,
you
know,
I
I,
don't
know
if
we
landed
on
anything
Tracy
for
the
infrastructure
for
this.
But
if
you
know
that's
something
we
can
work
with
if
work
on
with
anyone
who
is
interested
in
helping
out
with
this
yeah.
A
I
think
so
it
was
it
was
that
the
last
meeting
was
you
you,
you
myself
and
Michael
Dawson,
but
we're
happy
I'm
happy
to
help
with
the
survey
stuff.
I
believe
what
we
talked
about
was
just
Google
Forms,
because
anything
else,
you
end
up
having
more
problems
around
permissions
and
account
ownership,
and
there
may
be
benefits
to
that.
But
you
know
something
like
Survey
Monkey,
but
then
there
there's
also
we're
trying
not
to
do
large
enough
surveys
where
Survey
Monkey
would
be
beneficial,
I,
think
and
and
Google
Forms
does
have
basic
analysis
now.
A
A
Like
if
they
want
to
talk
about
the
you
know
the
more
specific
work
I,
don't
it's
hard
to
I
guess
so,
like
for
survey
work.
If
somebody
else
in
even
the
community
committee
notices,
we've
had
some
surveys
requests
filed
like
maybe
they
need
to
ping
myself
or
you
or
whoever
else
is
offered
to
help
with
the
surveys
from
within
the
community
committee
sort
of
like
who's
taking
ownership
of
these
things
when
they
don't
necessarily
have
a
working
group,
gotcha.
C
G
Let
me
just
see
we
should
so
I
think
this
is
like
there's
it's
similar
discussions.
I
think
we're
having
the
tea
see
that
really
like
there'll,
be
initiatives
and
I.
Think,
like
the
surveys
and
the
user
feedback
is
a
set
of
initiatives,
we
should
almost
have
them
on
the
agenda
each
week
to
see
like
it.
The
answer
may
be
nothing
to
say
but
sort
of
every
week.
It
should
almost
be
like
hey.
Is
there
an
update
on
the
survey
stuff?
G
O
J
O
J
J
G
C
Okay,
so
next
agenda
item
I
believe
we've
hit
both
of
the
items.
I
lost
the
issue
both
of
the
items
for
the
user
feedback
initiative.
I
do
want
to
make
sure
we
have
ten
minutes
left,
so
I
got
a
kind
of
push
through
this
a
bit
but
moderation
team.
So
the
one
of
the
issues
filed
in
the
admin
repo
was
goodbye
miles
Boren's,
asking
us
to
kind
of
participate
in
a
discussion
around
and
the
expectation
expectations
for
the
moderation
team.
C
This
is
more
of
a
ask
for
review,
rather
than
you
know.
We
need
to
deep
dive
into
this,
but
the
moderation
team
for
context
for
those
who
are
new,
the
moderation
team
is
a
team
form
relatively
recently.
I
think
we
have
two
members
here
myself
and
Raphael,
who
that
basically
isn't
empowered
to
go
in
and
moderate
quickly,
rather
than
having
kind
of
you
know
an
issue
around
moderation.
Where
can
I
moderate
this?
Is
it
okay
to
moderate
this
so
this?
C
This
is
a
group
of
people
who
have
been
approved
by
both
earth
not
objected
to
by
both
DTSC
and
the
community
committee
that
you
know.
Isn't
it
it's
empowered
to
go
do
this,
so
this
is
effectively
saying
these
are
the
people
we
can.
We
trust
and
we
think
they
can
go
moderate
this
and
so
right
now
the
discussion
is
around
enabling
how
how
should
the
moderation
team?
You
know
what
what
does
the
org
need
to
expect
from
the
moderation
team?
C
What
are
the
deliverables
of
the
moderation
team
and
not
just
this
physical
layer,
tangible
deliverables,
but
like
to
what
extent
is
it
in
or
is
the
team
enabled?
And
so
you
know
this
is
an
issue
that
needs
to
be
reviewed
by
the
compound,
just
like
it
does
by
the
TSE
and
went
through
a
similar
process
that
we
did
to
add
the
members
in
so
this
is
a
description.
I
was
like
kind
of
everyone
here
to
look
at.
C
G
Out
in
yesterday,
in
the
TSE
meeting,
we'd
asked
forced
to
give
an
update
on
the
progress
so
far,
which
he
did.
He
also
scoped
worth
what
they
thought
there.
Their
scope
was,
which
you
know,
is
implementing
process
the
policy
and
process
not
necessarily
defining
it.
They
did
agree.
They
could
make
some
suggestions,
but
you
know
if
you're
interested
you
could
go.
I
posted
the
link
in
the
the
chat
here
as
to
the
the
presentation
deck
that
they
did
it.
If
you
want
to
see
it
live,
you
can
go
back
to
the
recording
and
listen
to.
K
K
P
K
Know
the
government-
and
we
say
the
moderation
team-
is
the
police.
We
don't
want
that
body.
You
know
separation
of
a
separation
of
powers.
We
don't
want
that
body
set
the
rules.
We
want
that
body
to
be
executive
and
the
moderation
team
sort
of
agreed
on
that
that
we
don't
we
want
to
make
suggestions.
We
don't
want
to
be
our
own
advocates.
K
C
C
C
But
I,
you
know
the
point
is
they're.
Creating
the
rules
creates
a
conflict
of
interest
and
it
is
at
that
if
there
is
a
conflict
of
interest-
and
there
is
an
issue
with
an
action
the
moderation
team
takes,
it
becomes
difficult
for
us
to
as
mother
to
the
moderation
team.
It
becomes
difficult
to
say,
you're,
entirely
impartial
and
that
can
create
an
issue
with
the
trust
placed
in
the
team,
broadly
by
the
close.
The
community
committee
and
DTSC
well,
I.
Think.
A
That
the
point,
though,
that,
like
the
reason
why
the
rules
for
moderation
team
were
set,
the
way
they
were
was
that
consensus
building
with
calm,
calm
and
TSC
has
to
occur
so
that
the
moderation
team
is
never
owning
that
exclusively
anyway.
But
the
expertise
of
those
who
were
chosen
for
moderation
and
because
they
are
neck-deep
in
moderating,
provides
them
unique
opportunity
to
offer
that
expertise
to
to
help
define
the
policy.
But
they
alone
aren't
plus
wanting
the
policies
to
be
set.
Yeah.
C
And
that's
exactly
is
the
moderation
team
will
not
like
the
discussion
to
be
kind
of
bland
is
we
will
not
+1
it?
We
will
not
write
it,
but
we
are
happy
to
help
offer
expertise
like
help
offer
this.
This
can
be
helpful.
This
can
be.
This
will
be
an
issue
because
of
how
its
been
implemented,
but
the
the
kind
of
the
way
that
we've
landed
is
that
the
team
should
not
be
creating
policy
period
happy
to
help
creep
on.
You
know
that
consensus
building
of
calm,
calm,
ntsc,
but
not
necessarily
creating
yeah.
O
O
G
I
know
and
I
think
Tracy.
You
know
I.
This
I
had
the
same
initial
reaction
that,
like
hey
I,
thought
we
formed
the
team
to
do
some
of
that.
But
you
know
III
definitely
understand
the
rationale
and
the
approach
and
I
think
it's
a
matter
of
just
making
sure
that
things
don't
fall
through
the
cracks,
because
I.
C
C
G
G
G
A
A
It
was
because
the
the
expertise-
that's
you
know
that
that
can
help
define
that
policy,
but
I
also
made
sure
that
the
TSC
and
Kham
Kham
in
writing
that
that
turf,
that
governance
would
be
responsible
for
approving
it,
because
if
the
leaders
aren't
on
board
with
how
that's
working,
then
the
moderation
team
absolutely
will
get
blamed
for
this
thing
that
they
should
not
get
blamed
for
it
right.
That's
why
they
+1
so.
C
C
Tracy
suggested
we
do
a
online
working
session,
but
basically
what
it
is
is.
As
part
of
the
issue
described,
we
talked
about
earlier
around
the
documenting
expectations
on
Thyssen
community
committee
members,
one
of
the
s,
and
that
is
to
define
values
that
the
community
community
committee
and
TSE
can
be
upheld,
and
so
I
wanted
to
kick
off
this
issue.
To
get
the
ball
rolling
on
that
I
actually
found
a
very
optimal
one.
B
That
the
the
idea
that
we're
going
for
is
at
the
the
nodejs
code
in
Monday,
we
all
broke
up
into
groups
and
wrote
down
words
on
giant
pieces
of
paper
about
like
what
we
felt
was
important
to
the
nodejs
community
and
project
of
the
whole
and
we're
basically
gonna
do
that
on
a
more
focused,
specifically
level
to
values
of
the
that
sentence
made
no
sense,
I'm
specific,
specifically
to
what
is
important
as
the
community
committee.
B
L
Question
on
that,
what
do
we
suspect
the
calm
comes?
Values
would
differ
from
the
community's
values.
C
You
know,
but
much
in
the
same
way
that
community
committee
differs
from
individual
membership.
You
know
we
have
to
have
a
bit
of
a
more
refined
set
of
definitions
for
community
committees
as
a
yes,
just
like
the
or
as
a
committee,
just
like
ETSU
doesn't
necessarily
represent
every
single
developer
that
uses
node.
G
Think
in
the
discussion
it
was
that
they
may
be
more
specific,
so
you
could
kind
of
look
at
as
a
tiered
level
where
you
know
you
have
the
first
level
of
sort
of
higher
level
values
and
then
you
know
we
have
may
have
more
specific
values
which,
like,
for
example,
might
be
bringing
in
and
user
input
right
which
doesn't
apply
to
everybody
but
does
apply
to
the
community
community.
So
it's
sort
of
that
layering,
III,
I,
hope.
In
the
end
we
don't
have
conflicting
values.
It's
more.
C
G
C
J
C
Okay
cool,
so
this
is
a
sorry.
I
was
very
confused
there,
so
this
is
a
PR
in
the
admin
repo
and
I
realize.
We've
talked
about
that
admin
repo
several
times
for
those
of
you
who
don't
have
the
context
on
that.
That
is
a
repo
that
is
collaborative
between
the
TSC
and
the
community
committee.
That
has
some
hosts
some
administrative
kind
of
tasks
like,
for
example.
C
This
issue
is
proposing
moving
the
code
of
conduct
for
the
org
and
the
moderation
guy
as
well
to
into
a
central
place
that
they
can
then
be
referenced
from
individual
repositories,
just
kind
of
to
be
a
neutral
place,
and
so
what
this
PR
is
is
just
moving
that
into
one
place.
In
addition,
I
believe
miles
realize
you
should
have
separated
the
Erb
said
that
he
should
have
separated
the
COC
in
moderation.
C
Discussions
into
two
separate
requests,
but
you
know
just
this-
is
a
review
to
do
review
for
the
community
committee
and
observers
as
well
to
know
see
if
we
have
any
changes
that
need
to
be
done
here
and
he
feels
so
I
think.
Unless
anyone
has
questions
around
that,
you
know
it
would
be
great
to
get.
It
would
be
great
to
get
you
know,
input
on
in
this
issue
and
then
we
can
push
it
through
or
address
that
input
to
make
sure
it
aligns.
Yes.
G
Certainly
I
mean
from
from
their
husband.
There
was
some
pushback
to
moving
them,
but
from
what
you
know,
my
personal
opinion
is:
if
we're,
if
they're
the
same,
they
should
be
in
one
place:
cuz.
Otherwise
you
don't
know
that
they're
the
same
obviously,
and
they
could
easily
drift
unintentionally.
I
think
you
know
comm
come
again.
Tc
could
still
have
different
code
of
conducts.