►
Description
Details at https://github.com/nodejs/community-committee/issues/27
A
Alright
and
we
are
live
thanks,
everyone
for
joining
in
this
is
the
node.js
foundation
community
committee
meeting
for
April
13
2017.
This
is
our
inaugural
meeting,
which
is
pretty
awesome
yay
in
attendance.
We
have
a
couple
of
people,
we
have
a
William
cap
key,
we
have
Traci
Hines,
we
have
Rachel
whites,
miles,
Boren's
and
JP.
Forgive
me
I,
don't
remember
your
full
name
off
the
top
of
my
head
games.
A
A
A
A
A
A
After
that
we
can't
sometimes
some
groups
who
will
do
sort
of
just
like
a
roundtable
of
where
we
just
give
individual
updates
things
we
have
done
really.
The
some
groups
have
also
stopped
doing
that.
So
this
is
something
we
can
decide.
Is
this
something
that
you
know
we
want
to
do
as
a
group?
We
can
also
skip.
A
We'll
skip
it
for
this
meeting,
but
it's
just
something
keep
them
back
your
head,
so
we
can
figure
out,
that's
something
we
want
to
do,
go
ahead
and
jump
straight
into
the
agenda,
so
we
have
a
fight
up
items
on
the
agenda
which
are
in
the
google
doc
and
also
in
the
meeting
issue.
So
the
first
one.
Let's
take
a
look
at
number
30,
which
is
elect
a
chairperson.
A
E
A
C
E
A
Yeah,
so
the
share
will
be
a
smaller
role,
so
something
I
think
I
would
propose
that
we
do.
Is
you
know,
let's
all
think
about
if
this
is
a
role
that
any
of
us
are
interested
in
and
then
maybe
announce
that
you
know
we're
interested
and
possibly
applying
for
this
role
in
that
issue,
and
then
maybe
in
the
next
meeting,
which
will
be
in
two
weeks,
we
can
kind
of
come
back
around
to
that
and
either
have
a
discussion
around
its
you
sort
of
clarify
things
or
go
ahead
and
hold
a
vote.
C
C
A
E
D
E
So
yeah
the
discussion
that
has
kind
of
in
floating
around
so
far
as
to
what
would
happen
with
these
is
like
those
groups
would
want
to
would
need
to
elect,
to
say:
oh
we're
we're
better
off
over
there,
like
so
I
I
mean
I
I
built
the
list
on
the
I
like
getting
some
ideas
for
what
we
thought
belong
in
a
community
committee
or
under
a
community
committee
and
would
maybe
try
better
there.
Who
knows,
and
then
you
know
if
people
say
yes,
evangelism
sounds
like
it
really
belongs.
C
But
the
one
thing
there
is
I
think
that
those
are
yeah
I
do
I
like
these
and
I
think
this
is
a
task
that
we
should
definitely
ain't
even
forward
on,
but
yeah
ownership
is
definitely
a
thing
that
we
have
to
be
really
it's
more.
It's
definitely
an
outreach
to
people
who
are
working
on
them
just
for
interest
to
gauge
interest,
it's
not
to
say
like
we
want
to
invite
you
to
be
in
this
organization.
It's
hey
like
we're
here,
we're
working
on
this.
C
If
you
think
that
it
would
be
a
good
fit
for
you
guys
like
come
and
attend
the
meetings
and,
let's
think
about
it
code
and
learn,
is
probably
the
only
one
that
I
can
see
that
might
be
I,
don't
think
there'd
be
resistance
to
it
so
much
as
sort
of
like
joining
ownership,
because
it's
a
great
event
and
events
generally
don't
fall
or
haven't
traditionally
fallen
under
toc
domain,
but
because
it
is
until
now
at
least
a
teaching
core.
It's
something
that
I
think
that
is
like
really
really
important
to
people
working
in
those
groups.
C
E
E
I
open
that
and
I
build
my
list,
I
I
kind
of
went
through
and
evaluated.
Is
this
something
where
someone
is
contributing
code?
Or
is
this
a
community-based
thing
and
of
course,
I've
expressed
a
few
times
that
I
don't
have
this
mindset
of
of
an
us
and
them
because,
hopefully,
there's
so
much
overlap
that
everybody's
just
attending
the
same
meeting
just
under
different
names?
E
You
know
a
little
different
topics,
and
so
my
hope
would
be
several
several
of
the
core
people
will
actually,
you
know,
be
within
the
community
committee,
and
you
know
therefore
code
and
learn.
Would
you
know
just
be
the
same
people
because
I
think
if
you,
if
you're
trying
to
draw
those
adjacent
lines,
two
things
I
mean
everything
focuses
around
node.
A
D
C
Go
ahead,
yeah
I
was
gonna,
say
that's
a
good
question
for
context.
Is
that
so,
historically
speaking
and
I
think
Brian
and
William
would
be
able
to
probably
speak
to
this
better.
Is
that
github
things
that
were
in
the
node
organ
github
were
the
tsc
is
just
because,
like
that
was
their
domain
was
sort
of
code
and
github,
but
because,
no
because
we
do
so
much
and
github,
you
know
community
organizing
governance,
it's
it's
grown
to
be
a
lot
more
than
just
like
you
know,
poor
and
working
groups
that
are
only
committing
code.
D
E
E
To
say
we
either
calm
working
groups
or
teams,
but
yes,
and
really
what
this
really
comes
down
to
is
each
one
of
these
would
have
to
decide
like
what
would
this
this
parent
body
like
do
for
me
versus
the
other
one,
and
in
some
of
them
it
might
be
completely
nothing
like.
Maybe
the
help
repo
will
get
nothing
from
the
community
committee.
I,
don't
know,
yeah
well
get.
F
One
thing
that
I
can
throw
out
really
quickly
Rachel
that,
like
maybe
useful,
just
to
think
about
like
how
this
works.
Like
a
great
example
is
we
have
the
LTS
team,
which
isn't
even
a
chartered
working
group
which
technically
like
falls
under
the
purview
of
like
CTC
or
release
or
something,
but
they
get
a
ton
of
work
done
and
then
like
we're
wanting
to
do
more
stuff
related
to
back
ports
right
now.
So
we
kind
of
spun
out
like
an
intro,
an
interest
group
/
team
that
whole
process
took
like
five
minutes.
F
There
was
no
paperwork.
It
was
mostly
just
the
fact
that
there
was
people
that
were
interested
that
wanted
to
do
the
work.
So
I
don't
know
if
that's
helped
for
not
helpful
or
not,
but
just
as
like
a
prior
art,
it's
like
proven,
really
easy
and
for
lack
of
a
better
term
agile
for
collected
groups
of
people
who
have
similar
interests
to
just
start
doing
stuff.
Okay,.
D
E
C
That's
a
good
point,
I
would
say
yeah
and
the
only
the
only
kick
with
that
is
the
we
have
to
find
someone
who,
like
it's
either
like
so
dead
that
everyone,
you
know
anybody
is
just
like
yeah.
I
just
you
know,
have
it
if
you
want
to
revive
it,
but
like
it's
yours
or
otherwise,
it's
sort
of
like
do
we
do
anything
with
it
like
you,
we
do.
We
ask
if
there's
no
one
to
get
permission
from
for
it
to
be
a
part
of
the
community
committee.
Is
there
anybody
to
work
on
it.
C
A
Bye
yeah
I
mean
so
from
a
going
back
to
that
question
from
a
purely
technical
or
well
I,
guess
procedural
standpoint
as
far
as
like
who
has
the
final
say
on
it
or
he
may
who
makes
the
final
decision
in
the
case
of
working
groups.
It
is
that
working
group
that
makes
the
decision
most
likely
they
would
hold
a
vote.
A
They
could
do
a
consensus
driven,
but
it
is
ultimately
the
working
group
that
does
it
because
late
working
groups
are
chartered
is
they
have
autonomy
over
themselves
now,
but
a
team
is
inverse
of
that
and
that
teams
are
not
chartered
and
they
don't
have
autonomy
over
themselves.
So
it's
whoever
they
report
to
which
currently
is
going
to
be
the
I
believe
the
CTC
I,
don't
know
if
it's
in
all
cases,
but
at
least
in
most
and
whichever
ones
are
at
ctc
of
ETS,
see
now,
of
course,
that's
from
a
procedural
sample.
A
Yeah,
that's
like
well
I
think
some
of
the
teams
are
listed
in
the
TSU
charter,
because
the
TSU
Charter
has
a
list
of
like
a
scope
list
or
learning
technically
to
repository
list
and
I.
Don't
know
if
you
could
once
again.
This
is
from
a
purely
procedural.
What
the
bylaws
kind
of
thing
states
I
would
assume
that
teams
and
repose
are
assumed
to
be
the
same
entity
but
I'm
actually
not
sure.
A
E
It's
not
a
one-to-one
mapping
because
you
can
consider
like
evangelism
awesome
has
helped
so
there
it's
a
one-to-many
but
in
for
the
most
part,
yes,
but
everything
onto
the
technical
side
falls
under
the
GSC,
so
some
is
delegated
to
the
CTC
and
then
to
the
team
below
that,
so
I
mean
in
a
generic
sense.
It
all
goes
to
the
tsc.
A
C
My
question
is
like
I'm
trying
to
form
action
items
from
this
and
I
do.
Should
we
I,
haven't
really
I,
don't
think
I've
seen
any
objections
to
what's
been
listed
in
that
issue
for
like
who
would
be
good
to
reach
out
to
so?
Should
we
just
roll
with
who's
listed,
or
should
we
solidify
that
list
first
and
then
do
outreach
I'm
fine
with
like
just
reaching
out
to
everyone
cuz?
I
really
didn't
see
an
objection.
C
A
A
Alright,
so
next
up
going
back
to
going
on
order
on
issues
is
going
to
be
number
28
collaborators
summit
agenda.
So
we
have
the
collaborator
summit
coming
up
in
Berlin
on
May.
Fourth
and
fifth,
I
think
if
I'm
remembering
that
correct
off
the
top
of
my
head,
it's
ripe
for
Jace
come
for
you
in
Berlin,
so
previous
collaborators,
how
much
have
been
really
great
opportunities?
D
A
B
E
C
Think
that
I
think
that
it
would
be
good
for
since
everyone's
gonna
be
in
one
place,
but
the
items
on
our
agenda
especially
focus
on
things
that
are
cross
collaboration,
which
it
I
think,
is
a
lot
of
what
we're
doing
now.
Anyway-
and
maybe
it's
not
agenda
for
the
meeting
but
more
like
a
goal
for
a
while
we're
a
collab
summit
which
is
joe.
I
get
everybody
on
board
with
feeling
like
they
are
a
part
of
community
committee.
Instead
of
a
part
of
like
another
group,.
E
C
I
think
that
that
would
be
especially
good
one
to
have
everyone
in
the
same
room.
Well,
I
am
I
think
that
that's
a
really
good
idea,
because,
like
moderation,
especially,
is
one
of
those
things
where
I
think
we're
like
kind
of
outgrowing
we're
getting
a
little
too
big
for
our
britches
in
terms
of
like
what
moderation
currently
covers,
just
in
terms
of
like
places
like
github,
and
that
we
just
need
to
get
people
like
thinking
about
how
it
had
where
else
it
should
cover
like
how
we
can
all
help.
C
C
C
Of
it'll
it
would
be
more
of
like
a
planning
saying
than
like
a
roadmap
e
thing
and
I've
talked
to
a
few
people
about
it.
But
it's
the
idea
that
I
kind
of
consider-
and
I
keep
making
this
joe
key
phrase.
But
I
kind
of
consider
community
committee,
like
the
Walmart
greeters
of
node,
and
so
as
part
of
that
I
want
to
figure
out
how
we
can
do
sort
of
like
a
meta
collaboration
like
or
like
intro
to
contribution
session
at
the
fall.
Node.
C
So
like
when
you
think
about
something
like
code
and
learn,
it's
very
specific
to
Khor,
which
I
think
you
know
I've
been
talking
to
folks
about
opening
that
up
a
bit.
But
after
in
the
afternoon,
when
we
do
code
and
learn,
you
know
that's
the
beginning
of
collaboration
summit,
but
there's
a
lot
of
people
who,
like
they
can't
just
walk
over
a
table
and
say
hi
they've,
never
participated
and
it's
really
intimidating.
So
what
I
probably
be
really
neat
is
the
idea
of
having
an
intro
session
that
afternoon,
which
is
Oh
like.
C
Are
you
interested
in
working
group?
But
you
don't
know
anybody
and
you
don't
know
how,
like,
let's
walk
through
that
instruction
and
see
how
you
get
started
in
that
and
maybe
like,
let's
walk
through
you're
like
what
they've
been
working
on
and
then
we'll
go,
introduce
you
to
those
group
of
folks
because
it.
A
A
D
C
A
I'm
looking
back
over
right
now,
Jeremiah
filed
it
initially
and
it
so
it's
like
who
has
voting
rights
within
the
Charter.
There
was
a
the
concept
of
two
separate
people.
If
I
remember
this
correctly,
there
was
like
members
of
the
committee
and
then
advisers
on
the
committee
and
those
advisors
come
from
you,
these
external
groups,
and
so
as
a
question
of
like,
is
it
advisors
and
members
or
is
it
just
members
Tracy?
Do
you
have
any
insight
into
that
since
yeah
I
know
you
are.
C
So
I
think
the
discussions
that
I
have
with
people
before
we
lock
that
down
was
one
that
this
could
be
really
complicated
and
it
may
have
needed
like
that,
was
sort
of
like
the
first
workshop
approach.
So
it
could
be
refined
as
well.
But
the
idea
was
that,
like
we
have
a
bunch
of
members
because
we
have
a
ton
of
people
in
like
it.
C
C
I
can't
happen
until
that
occurs,
and
maybe
we
like
change
this
to
say
like
in
66.
You
know
six
months
time.
We
go
back
to
that
method
because
we
don't
actually
have
enough
people
to
really
make
sense
of
that.
Yet.
But
yeah
like
the
issue
with
a
cute
you're
not
going
to
dictate
to
outside
community
groups
how
they're
selecting
representative.
C
Yes,
as
long
as
that's
something
that
we're
able
to
do
like
I,
don't
the
biggest
concern
I
have
is,
if
there
is,
if
like,
what
you
were
saying
is
like
consensus
is
fine
if
we
actually
have
to
come
to
a
vote
and
we
don't
have
a
group
of
people
who
are
allowed
to
vote.
That
would
be
a
problem,
so
I
think
it's
good
to
put
it
on
hold
for
now,
but
we
definitely
I
can
look
into
this
further,
which
is,
and
I'm.
D
D
E
I
mean
for
the
for
the
time
being,
those
members
are
currently
listed
to
have
voting
rights
is
the
short
answer
and
so
I
guess
we
need
to
discuss
like
what
these
external
groups
are
and
how
they
want
to
weigh
in
on
different
things
right,
but
as
far
as
changing
it,
Gina
run
it
through
the
board.
It
is
approved,
oh.
A
C
Yeah,
that's
a
good
point.
I
mean
I
honestly
think
that
I
pre
optimized
I
over
engineered
this
for
something
that
we
you
need
to
happen
because
yeah
I
mean
that's
a
good
point
is:
do
we
really
need
to
have
a
distinction,
or
do
we
even
need
like
one
na
tackling
we
should
we
just
have
members
voting
I.
A
C
C
E
A
Yeah
I
think
there's
probably
two
parts
to
this.
So
let's
say
for
the
sake
of
argument.
We
decide
to
go
with
just
bringing
everyone
on
as
members
for
now.
I
think
the
big
question
around
that
is,
if
we
leave
the
Charter
at
is,
would
we
be
violating
that
charter
in
terms
of
voting?
If
not,
then
I
think
it's
probably
fine
just
to
leave
it
as
is
even
if
we
don't
know
if
we're
not
necessarily
exercising
parts
of
the
Charter,
that's
I
think
that's
fine.
It
might
be
easier
than
actually
making
a
change
right
now.
A
C
E
A
Alright,
so
the
last
issue
on
our
agenda
is
number
11.
This
is
a
central
communication,
medium
for
chatting
in
nodejs
and
I
a
tag
to
the
CC
agenda,
but
there's
a
couple
of
related
ones
that
I
think
also
fit
within
this
discussion.
So
there's
the
question
itself
of
where
should
we
hold
more
real-time,
like
collaboration,
so
the
proposal
is
either
I
or
see
or
slack.
There
been
discussion
of
a
few
others.
A
Webb
says
question:
which
technology
should
we
choose
and
there's
a
lot
that
goes
into
the
decision
from
around,
like
you
know,
ease
of
access,
moderation
and
all
sorts
of
things
like
that
and
there's
also
a
related
question
of
how
do
we
actually
make
the
decision,
like
what's
the
procedure
for
making
that
decision?
How
do
we
vote
on
this.
A
C
We're
totally
stuck
in
the
part
where
we
figure
out
the
logistics
of
the
voting
mechanism,
because
I
mean
this
is
my
personal
fuel,
which
is.
There
are
three
groups
that
need
to
voice
input
on
this
as
distinct
groups,
and
that
is
moderators
from
our
community
at
one
group,
the
tsc
as
another
group
and
then
the
light.
The
last
group
is
community
at
large
and
that's
a
particularly
tough
group
to
get
feedback
from,
because
it
ends
up
being
like
very
much.
C
This
is
like,
ultimately,
the
biggest
challenge
is
that
you
can't
force
anybody
like
if
the
tsc
folks
in
the
tsc
you
who
have
been
working
on
things
for
a
long
time,
don't
want
to
move
over
to
whatever
decisions
been
made.
They
don't
feel
comfortable.
That's
like
a
good
decision.
They
aren't
going
to
do
it
and
that
lack
of
buy-in
is
tough
and
the
same
thing
goes
for
existing
moderators
and
there's
a
lot
of
feelings
on
that.
So
I
do
think
that
that
so.
F
C
F
E
Okay,
so
who
who
are
we
making
this
decision
for,
is
one
of
the
things
I
I'm
wondering
myself,
because
if
we're
making
it
for
the
community,
that's
one
decision
if
we're
making
it
for
the
collaborators
it's
another.
So
what
I've
noticed
is
that
the
collaborators
that
want
to
help
on
IRC
and
answer
things
like
in
the
node.js
channels?
They
do
some
just
sit
in
the
note,
dev
Channel
and
answer
some
things
there
and
that's
fine
and
they
in
general,
a
lot
of
them
communicate
between
each
other
there.
E
But
if
we're
talking
about
more
of
the
seven
million
pie,
7
million
users
of
ours,
that's
kind
of
a
different
story
and
I
think
a
lot
of
this
discussion
has
been
blurred
between
which
target
here
we're
talking
about
and
as
we
can
see
here
in
that
thread,
there's
already
a
slack
community
out
there,
thousands
of
people
on
there
not
sure
if
it's
over
2,000
or
not,
but
a
lot
of
people.
There
are
in
numbers,
probably
and
now
close
to
the
same
as
what's
in
IRC
and
so
I
mean
at
one
level.
E
We
have
IRC
a
moderators
that
say
I
don't
want
IRC,
it's
not
something
I'm
into,
and
they
want
to
be
on
slack
only
you're,
your
ability
to
moderate
care
is
certainly
limited,
but
I
think
that
adds
the
complication
of
this
story
of
who
is
the
person
speaking?
What
is
their
target
of
concern
like
their
target
audience.
C
Yeah,
so
this
is
a
desert,
excellent
point:
William
I
the
the
idea.
This
idea
clearly
came
out
of
the
result
of
my
research
for
the
inclusivity
strategy,
and
so
that
was
supposed
to
be
more
targeted
at
the
community
at
large
and
a
lot
of
people
even
from
our
survey
in
the
winter
said
that,
like
just
the
quality
of
communication,
both
in
IRC
and
slack
are
not
good,
and
so
what
what
I
think
needs
to
happen
and
I?
C
C
E
F
Can
I
throw
something
out
there
feel
free
to,
like
you
know,
shut
this
down?
If
you
think
it's
a
tangent,
but
perhaps
the
whole
slack
versus
IRC
thing
itself,
is
a
red
herring,
I
think
I
can
I
your
seat.
Pardon
I
think
that
actually
I
do
black
and
IRC
are
an
interface
with
the
complaint
that
we
have
is
like.
F
Maybe
there's
a
bit
of
a
complaint
about
onboarding
kind
of,
but
I'm
not
really
seeing
that
as
like
the
major
complaint,
the
major
complaint
is
like
people
want
better
support
and
honestly
I'm,
not
convinced
that
either
slack
or
IRC
are
either.
You
know
like
better
for
support.
We
can
talk
about
like
user
experience
of
slack,
obviously
winning
out
on
IRC
for
the
openness
and
accessibility
of
IRC,
winning
it
over
slack
the
open
source,
nature
of
things
and
slack.
Like
all
these
other
things.
F
None
of
these
actually
have
to
do
with
the
core
issue,
which
is
like
how
are
we
properly
supporting
our
community
and
I?
Think
that
even
the
moderation
thing
that
we're
talking
about
doesn't
really
cover
this
like
as
long
as
we
still
just
have
this
consistent
stream
of
texts.
That
is
the
main
interface
that
people
are
using
to
try
to
get
support.
We're
going
to
run
into
the
same
problems
like
to
me
I'm,
starting
to
think
it's
like.
Do
we
need
a
ticketing
system?
F
Do
we
need,
like
proper
support,
reps,
like
I'm
dream
of
there's
almost
more
like
a
company
right
now,
and
maybe
that's
not
really
feasible
for
us
to
do
as
a
project
but
like
if
the
problem
is
truly
support,
not
a
problem
of
like
do?
We
have
a
community?
Obviously
we
have
a
massive
IRC
community
and
we
have
a
massive
slack
community
and
both
of
them
are
happy
in
their
environments
and
communities
with
the
complaint
and
I
am,
in
my
opinion,
is
inconsistent
support,
but.
C
I
do
think
that
the
support
is
a
part
of
it
that
hasn't
been
discussed,
but
I.
Don't
think
that
that's
exclusively
the
problem.
I
think
it
is
also
community
like
we
have
people
who
are
breaking
off
into
these
smaller
sections,
because
they
don't
feel
like
no
like
either
of
those
are
not
places
that
people
are
hanging
out
like
shooting
the,
and
maybe
that's
okay,
because
it's
too
big,
like
maybe
that's
just
not
something
that
we
can
solve,
but.
F
I
guess
that's
kind
of
what
I'm
getting
and
they
think
you
like
hit
the
nail
on
the
head.
It's
like
the
problem
that
I
think
is
important
for
us
to
solve
is
not
like
telling
people
where
to
build
their
communities.
It's
like
when
people
need
help
from
the
project.
How
do
we
have
a
defined
their
way
for
people
to
get
that
support,
like
maybe
set
up
other
candies
all
the
time?
Well,.
D
E
C
C
C
Also,
do
think
that
github,
it's
not
a
place
for
conversation,
I
know
that
it
has.
A
comment
is
done
but
like
that
is
not
a
real
time
like
that
is
not
a.
It
is
not
necessarily
conducive
to
having
a
conversation
about
something
that
you're
struggling
with,
and
so
I
do.
Think
that,
like
a
chat
mechanism
needs
to
be
in
place
as
part
of
that
I
mean.
E
E
D
E
What
help
does
is
allow
someone
to
formulate
their
problem
and
put
it
out
there,
and
it
also
works
a
little
bit
better
for
our.
You
know
around
the
world
group
of
collaborators
so
that
they
can
get
to
it
when
they
get
to
it,
whereas
these
other
chat
programs,
it
Scrolls
back
in
history
and
then,
if
somebody
wasn't
happen
to
be
paying
attention
at
the
time
it's
just
missed,
is.
C
What
you're
saying,
though,
I
see
what
you're
saying
so
this
is
sort
of
something
that
I
was
having
a
conversation
about
this
week,
so
you
still
have
to
treat
one
as
the
source
of
truth
and
in
this
sense
will.I.am.
Yes,
help
should
be
the
source
of
truth,
but
what
I'm
saying
is
there
should
be
a
hook
into
IRC
or
whatever
chat
mechanism.
We're
doing
so.
C
You
can
have
a
real-time
conversation
if
you
need
to,
but
ultimately
that
needs
to
be
pasted
back
into
the
issues
that
other
people
can
come
back
to
it
and
see
that
and
learn
from
that,
because
it
should
be
like
us
almost
like
stackoverflow
in
the
sense
that,
like
you
can
reference
it
later.
If
the
problem
is
once
you
close
that
stuff,
it's
also
harder
to
service
I.
E
E
There
is
it's
just
lots
of
lines
of
text
going
back
and
forth,
describing
the
problem
trying
different
things
that
gets
lost
in
the
history,
so
I'm
all
I'm,
really
leaning.
It
was
there's
pros
and
cons
of
both,
but
at
the
micro
level,
the
real
time
is
it
certainly,
you
know
far
superior
to
just
send
a
quick
message,
quick
question.
F
F
That
brings
them
into
a
web-based
IRC
chat,
that's
in
a
specific
channel
and
they
just
plug
in
a
username
and
go
whereas
like
if
someone
is
not
in
the
slack
yet,
and
you
want
to
onboard
them
for
a
quick
chat
out
of
help.
You've
got
to
invite
them
and
they've
got
to
sign
up.
Then
they've
got
to
go
through
like
that
tutorial
that
you
always
get
that
you
close
then
put
in
their
name
and
like
it's.
You
know
like
10
steps,
as
opposed
to
a
clip
I'm.
E
With
you
one
hundred
percent
on
that
it
is
a
definitely
a
barrier
to
get
it
in
there
and
that's
why
I
say
like
there
are
people
that
want
both
there's
the
person
that's
like
I
will
continue
to
have
questions
so
I'm
willing
to
do
that
on
boarding
and
there's
the
other
people.
I
want
to
just
jump
in
and
don't
know
if
they'll
ever
come
back
for
question
again.
So,
like
happy,
I
just
see
pros
and
cons
of
both
yeah.
F
But
are
not
moderated
or
properly
maintained
so,
like
maybe
there's
like
a
halfway
point
here,
where
I'm
just
going
to
throw
like
a
make-believe
thing
that
maybe
doesn't
make
sense.
But
if
the
foundation,
for
example,
ran
moderator
training
and
if
you
had
a
space,
that's
a
community
for
nodejs
people.
F
You
could
go
to
the
to
the
foundation
or
to
the
calm,
calm
and
be
essentially
have
your
moderators
trained,
and
it's
essentially
have
a
kind
of
a
stamp
of
approval
that
this
is
like
a
sanctioned
space
for
the
node.js
community,
like
we
can
kind
of
invert
it,
and
rather
than
trying
to
like
control
these
spaces,
we
can
kind
of
let
them
proliferate
as
they
want
and
just
like
kind
of
sign
off,
like
I.
Think
of
like
we
all
jus,
for
example,
as
just
one
is
like
that's
a
very
specific
community.
F
That's
really
wants
things
a
certain
way
and
no
reason
that,
like
we
shouldn't
be
able
to
like
come
to
agreement
now,
they
may
have
no
interest
in
putting
that
stamp
on
their
on
their
slack,
but
they
like
just
from
a
higher
level
I'm
trying
to
think
of
like.
Maybe
the
solution
that
we
need
to
solve
is
just
like
kind
of
like
a
step
higher
than
like
the
granularity
of
telling
people
where
to
go.
F
C
E
E
Right,
we
have
one
minute
remaining
here:
I,
don't
know:
if
we're
going
to
do
public
QA
glancing
in
there
I
see
there
are
a
few
insensitive
comments
perhaps,
and
somebody
asking
if
they
should
learn
nodejs
or
go
of
course
we're
going
to
stay.
You
should
learn
nodejs,
it's
the
appropriate
thing
for
what
you're
doing
yes,
they
are
both
tools
and
they
have
good
reasons
for
each
do
we
want
to
wait
for
any
additional
questions
or
anything
like
that.
We
want
to
continue
on
past
and
I.
Just
have
to
drop
off,
I.
Think.
A
Think
all
of
those
things-
yes,
something
else
I
would
also
add.
Is
it
I
think
it'd
be
a
good
exercise
to
really
go
through
and
document
specifically
what
problems
we
are
trying
to
solve
and
kind
of
what
are
the
various
nuances
to
them?
You
know,
basically,
the
things
we've
been
talking
about
in
this
discussion,
because
I
think
that
will
help
guide
some
of
these
decisions
on
how
we
approach
them.
So
they
talking
about
support
and
like
how
this
is
a
really
key
part
of
our
communication
strategy.
A
But
you
know
there's
other
aspects
feels
like
you
know
what
you
know
creating
safe
spaces
and
you
know
making
sure
that
we
have
moderators
on
hand,
so
that
I,
like
moderator,
training
and
you'll,
just
maybe
like
going
through
like
documenting
these
things
out
we
are
looking
for
and
that
we're
interested
in
I
think
would
be
a
good
step.
Two.
C
D
A
C
A
F
So
Michelle
er
I'm
just
going
to
let
you
know
it's
an
aside
and
it's
kind
of
unrelated,
but
I
will
be
in
London
for
a
week
in
July
cool
feel
free
to
reach
out.
My
contact
information
is
pretty
easy
to
rummage
up,
but
if
you
can't
find
it,
Tracy
knows
how
to
get
a
hold
of
me,
and
maybe
we
think
if
there's
a
talker
or
workshop
or
whatever
I
can
do.
Oh
yeah.