►
From YouTube: Inclusivity WG Meeting - 2016-May-5th 10:00AM PDT
Description
Meeting agenda and further information available at https://github.com/nodejs/inclusivity/issues/134
A
B
C
D
A
Alright
welcome
everyone,
so
the
agenda
is
a
short
one,
but
we
have
a
big
thing
to
talk
about,
so
we
don't
have
any
open,
pull
requests
or
any
other
recent
activities
to
kind
of
go
over
like
we
normally
would
do
so
at
this
point,
let's
go
ahead
and
get
into
our
core
thing.
We
want
to
talk
about
so
with
this
group,
we've
been
doing
a
lot
of
work
recently
and
getting
to
start
like
day-to-day
operations
up
and
running,
and
we've
gotten
a
lot
of
our
policies
and
programs.
A
A
Now,
where
you
know
the
day-to-day
is
down,
we've
got
that
set
and
it's
time
to
basically
get
to
work,
to
kind
of
get
started
on
the
things
that
this
group
is
here
to
work
on,
and
so
I'd
like
to
use
this
meeting
to
basically
set
our
medium-term
magenta,
so
the
kind
of
stuff
that
we
want
to
get
done
in
the
next
like
three
to
six
month
time
frame
and
something
like
that
and
so
I'll
go
and
kick
us
off
a
little
bit.
I
want
this
to
be
collaborative.
You
know
there
is
no
actual
plan.
A
Yet
I'd
like
to
come
up
with
some
ideas
here.
We
don't
necessarily
have
to
have
an
exact
list,
but
at
least
like
to
get
that
conversation
really
going.
So
one
of
the
things
that
I
would
I
think
we
should
work
on
is
an
issue
number
7,
70
90
s
where
this
came
from?
Originally
we
have
a
new
issue
somewhere.
B
A
I
create
exactly
where
those
are
132
I'm.
Sorry.
So
if
we
look
at
issue
1
32,
the
idea
for
this
is
to
create
a
proposal
for
a
project,
wide
moderation
framework,
and
you
know
we
already
have
some
stuff
in
place
for
this.
You
know
we
have
a
ton
of
conduct
and
we
have
the
basic
steps
outlined
for
moderation.
What
I
would
like
to
see
the
students
really
flush
that
out
a
lot
you
know
get
more
into.
A
You
know
how
we
assign
people,
how
we
do
moderation,
yeah,
how
we
assign
moderators
and
just
some
flushing
out
of
that
quite
a
bit,
and
the
reason
I
think
that
this
is
important.
Is
we've
had
a
number
of
dust-ups
recently
in
the
node
community,
yeah
I
think
a
number
of
people
of
seeing
the
promises
thread
that
happened.
There
was
a
lot
of
vitriol
there
and
we've
had
a
couple.
Others
like
that
recently
and
what
my
hope
is
that,
with
once
we
have
this
framework
in
place,
we
can
really
reduce
the
amount
of
vitriol
there.
A
You
know
make
it
a
more
collaborative,
more
pathetic
and
you
don't
get
more
people
involved
as
a
result,
because
there
are
a
lot
of
people
who
left
lowes
conversations
because
they
just
knew
they
didn't
feel
comfortable
participating.
So
this
is
the
one
that
I
you
know
pretty
interested
in
seeing
anyone
else
have
any
thoughts
on.
B
I'm
certainly
interested
in
doing
it
if
I
need
to
provide
I've
seen
how
stressed
people
get
kind
of
and
something
goes
wrong
in
modes.
A
lot
of
people
have
something
to
say
which
is
good
and
but
there's
a
lot
of
vitriol
as
well,
and
you
know
I'd
like
everybody
in
node
to
have
a
slightly
nice
a
day
and
so
yeah.
This
is.
This
is
kind
of
important
to
me
as
well
I'm
interested
in
helping.
E
E
A
A
A
E
Look
with
Brom,
if
it's
all
right
with
with
everyone
else,
I
I,
unless
it's
providing
super
necessary
context,
I
prefer
to
dispense
with
with
past
events,
I
think
we
can
all
agree
that
past
Pat
past
stuff
was
not
handled
as
well
as
perhaps
it
could
have
been.
But
let's,
let's,
let's
focus
on
what
we're
gonna
do
in
the
next.
You
know
in
the
next
several
months,
good.
A
Point
yeah
you're
right,
so
there's
been
some
discussion
around
what
this
could
look
like.
This
isn't
just
something
I
can
with
my
head,
but
it's
still
pretty
fake,
but
the
basic
idea
is
that
there's
going
to
be
three
groups,
sort
of
involved
in
moderation
that
kind
of
handled
different
parts
of
it,
the
ideas
we
want
to
sort
of
distribute
the
workload
a
bit,
and
we
don't
want
this
to
be
any
one
group
in
charge
of
it.
A
So
the
basic
idea
is
that
for
us
in
the
inclusive
you
working
group,
we
would
be
the
ones
to
basically
come
up
with
a
lot
of
the
policies
and
proposals
on
how
this
is
done,
which
then
get
passed
up
to
the
TSE
and
back
and
forth
with
the
tsc
to
you
know
really
kind
of
hammer
that
out
and
then
finally
get
that
actually
landed.
And
then
the
tsc
is
sort
of
responsible
for
overseeing
things
at
a
high
level.
A
They
don't
do
anything
day-to-day,
but
they're
responsible
for
like
forming
this
third
group,
which
would
be
a
moderation
team.
Any
idea
what
this
team
is.
This
is
a
group
of
people
who
volunteer
to
act
as
moderators.
You
know
if
the
need
arises
and
you
know.
Hopefully
we
can
get
like
some
training
around
that
too,
or
at
least
some
guides
things
like
that,
and
then,
whenever
we
get
so
far,
it
looks
like
we
need
moderation
or
liking.
A
Oh
thread
might
get
up
until
it
actually
assigned
someone
to
watch
over
that
it
be
exactly
one
person,
and
so
the
reasons
for
doing
this
are
twofold.
One
is
that
we
can
make
sure
that
there
is
someone
who
is
watching
these
Fresno,
for
this
kind
of
you
know
that
behavior
and
things
like
that,
so
that
we
don't
have
gaps,
but
it's
also
to
make
sure
that
we,
you
know
in
some
cases,
don't
get
multiple
people
kind
of
going
in
trying
to
moderate
you.
A
F
So
I
think
this
is
a
good
idea
to
plan
to
have
four
threads
that
could
that
we
anticipate
having
a
lot
of
you
know,
potentially
bad
discussion
going
on.
We
would
assign
of
someone
to
moderate
that
discussion,
if,
like
at
the
tummy
issues
created
and
then
for
other
issues
where
we
don't
anticipate
it,
but
it
starts
to
happen.
Someone
we
just
got
assigned
one
since
recognized
yeah.
C
A
A
Yeah
yeah
yeah
definitely
and
there's
a
real
positive.
We
already
know
Jas
/
moderation,
you
all
have
access
to
it
now
being
members
in
this
working
group
this.
This
is
what
we
use
today
to
kind
of
monitor.
Some
of
this
I
envision
like
that,
would
probably
just
remain
the
same
I'd
like
the
way
it's
used
the
way
things
that
reported
there.
We
will
just
add
a
little
bit
of
process
around
that
my
stuff
like
something
to
check
out
by
the
way
yeah.
A
E
A
Yeah,
that's
a
good
point.
We
could
maybe
say
it
can
be
more
than
one
person
or
maybe
have
like
rotating
schedules
or
yeah.
That
definitely
sell
me
to
be
flushed
out
that
it
does
very
good
point
I'm.
Something
else.
So
single
ism
would
be
important
to
someone
else.
I
think
brought
this
up
was
that
whoever
does
get
assigned
is
someone
who
should
be
pretty
impartial.
So,
for
example,
let's
say
we
were
going
to
do
something
with
streams
and
that
became
heated
you
ever
gets
assigned
to
moderate.
You
should
be
someone
who's,
not
involved
in
streams.
C
Another
thing
to
keep
in
mind
is
I,
think
we'll
probably
need
so
so
usually
there's
not
more
than
one
of
these
a
time
it's
happened
where
there's
been
like
two
really
heated
discussions
at
a
time,
but
it's
pretty
rare,
usually
there's
like
one
thing
that
everyone
started
dog
paddles
onto
and
that's
it's
also
kind
of
an
issue.
If
you
have
just
one
person
trying
to
look
after
the
sheer
volume
of
stuff
that
goes
on
is
a
lot,
then
it
can
be
a
lot
to
keep
an
eye
on.
A
E
Not
I
don't
know
that
we
need
to
figure
that
out
here
and
now
I
mean
we
can
try.
Maybe
but
I
think.
The
main
thing
we
want
to
make
sure
we
agree
on
is
that
this
is
important
and
something
we
want
to
do,
and
maybe
even
try
to
figure
out
who
among
the
people
here
today
is
particularly
interested
in
has
time
and
who,
among
people
who
are
out
here
today,
and
maybe
even
aren't
in
the
inclusivity
working
group,
might
also
be
people.
We
want
to
involve
in
the
process.
A
B
A
G
C
Alright,
so
again,
so
rust
actually
does
something
similar
I
don't
have
the
links
right
now
they
have
a
separate
moderation
team
for
their
thing
and
they
get
a
huge
amount
of
activity
two.
So
it
seems
pretty
reasonable
to
me
that
our
members
on
the
moderation
team
might
be
a
little
less
active
than
that
I
think
some
of
the
people
on
the
rust
moderation
team
are
actually
from
Mozilla
if
I
remember
correctly,
I
might
be
wrong
about
that,
though.
So.
A
I
know
it's
been
translated
to
certain
other
languages,
and
so
the
idea
behind
this
program
would
be
to
formalize
that
probably
some
of
the
stuff-
that's
already
been
done-
maybe
flush
it
out
a
little
more
and
provide
me
on
like
active
translation
services
for
threads.
There
are
questions
over
scope.
You
know,
do
I,
do
it
for
all
threads,
probably
not,
but
you
know
selecting
certain
threads
where
it
seems
like.
This
is
a
really
important
discussion
and
it's
happening
quickly.
We
want
to
make
sure
that
we
can
include
everyone
in
this.
E
G
G
C
B
D
Don't
know
I
know
that
after
value
DSO
thing
happen,
there
were
like
a
lot
of
group
created
a
created
for
specific
languages
and
part
of
the
previously
known
as
I
odious,
Spanish
and
I
know.
There
are
14
languages
and
there
is
a
lot
of
people
on
those
groups
that
maybe
want
to
be
interested
in
how
to
kiss.
So
is
not
one
person
from
the
anticipated
working
group
doing
the
translation
on
the
communication,
but
they
will
be
able
to
involve
the
group
that
agrees
to
contribute
to
a
specific
language.
A
B
B
Everything
is
important
because
all
discussion
is
important
and
if,
in
an
ideal,
world
I'd
translate
everything
for
everyone
and
that
that
is
simply
not
possible,
and
so,
if
we
can
work
out
in
an
issue
or
something
or
even
as
a
document,
you
know
what
constitutes
a
thread
that
we
could
dedicate
the
resources
to
to
actually
translate
I
think
that'd
be
a
good
first
step.
I
like.
C
I
do
want
to
bring
up
a
little
bit
of
concern,
so
the
concern
I
have
with
this
is
that
I
have
not
really
seen
particularly
positive
feedback
from
people
in
the
language
groups,
and
it's
mostly
been
us
being
concerned
about
them.
I
would
like
to
see
people
from
them
actually
wanting
this
people
from
other
languages,
I'm,
not
sure
if
there
is
a
language
barrier,
that's
causing
nuts.
C
A
Think
it's
a
really
good
point.
Actually
this
I'd
have
to
trace
through
where
this
threat
came
from.
Originally
it
didn't,
originate
and
inclusivity
repo
it's.
It
seems
like
it's
one
of
those
things
that
it
comes
up
every
now
and
then
some
people
do
suggest
it
and
want
it
that
aren't
native
English
speakers,
but
this
does
feel
very
ad
hoc
and
I,
don't
feel
like
I'm.
A
very
good
feel
of
you
know.
This
is
something
that
some
people
will
sometimes
say
like.
A
B
Then
maybe
to
reduce
skeet
scope
even
further
and
we
kind
of
reach
out
to
who
he
can
and
see
if
that
would
actually
be
interesting,
because
there's
no
point
creating
this
awesome
thing.
If
nobody
wants
to
use
it
right,
because
we
can
work
for
six
months
and
give
them
something
shiny
and
then
no
one
actually
wants
anything
translated.
So
I
think
Jeremiah
raises
a
really
good
point
now
and
maybe
we
should
work
on
a
way
to
find
out
if
there's
interest,
and
then
we
can
start
to
think
about
what
kind
of
threads
which
stops
translate.
A
A
A
A
Some
of
these
are
kind
of
a
little
more
administrative,
but
ok,
so
I
can
list
off
the
others.
Three
more.
It
looks
like
sorry,
I'm
reading
and
talking
at
the
same
time
doesn't
always
go
so
well
alright.
So
we
have
number
issue
number
61.
This
is
inclusivity
checklist
guide
for
conference,
organizers
and
the
ideas
we
would
come
up
with.
You
know
a
guide
for
running
conferences
in
inclusive
ways
that
we
would
make
available
through
the
node
foundation
and
also
possibly
working
with
other
groups
just
reading
through
the
issue.
A
This
you
know
we
include
things
like
other
groups
to
reach
out
to
you
can
help
with
this
consider
various
considerations
that
you
know
you
want
to
keep
in
mind
when
you're
learning
a
conference
of
things
like
you
know.
How
do
you
deal
with
food
for
different
types
of
died,
restrictions,
things
like
that,
Family
Care
and
all
like
I
stuff?
You
know:
how
do
you
select
a
code
of
conduct?
How
do
you
enforce
it,
just
all
those
sorts
of
things
so
that
way
we
have
someone
is
starting
up
a
conference.
E
Is
so
I'm
going
to
my
feeling
on
that
is
I,
think
others
are
doing
this
like
making
these
kinds
of
checklists
and
recommendations
and
there's
nothing
node
specific
about
it.
So
what
we
can
do,
though,
is
curate
some
links
to
some
quality
resources
and
put
it
in
a
FAQ
or
something
like
that,
but
I
don't
think
we
need
to
actually
like
assemble
a
committee
to
figure
this
out.
I.
B
Agree
with
that,
there's
an
amazing
amount
of
resources.
If
you
just
look
in
the
right
places,
and
so
we
should
probably
listen
to
the
experts-
don't
say
that
you
know
we
don't
know
what
we're
talking
about,
but
it
has
already
been
done.
Then.
Maybe
we
can
kind
of
reduce
the
size
of
that
project
as
a
truck
say.
Oh.
A
A
E
D
B
And
being
part
of
note
j/s
as
an
inclusive
t,
working
group,
people
were
hopefully
start
looking
towards
us
for
these
kind
of
things,
and
if
we
can
just
be
like
here
is
a
guide,
then
we
can
kind
of
guarantee
that
things
are
going
to
be
a
little
bit
more
inclusive.
A
little
bit
smoother
in
there
running
so
I
think
I
think
it's
definitely
worth
being
at
their
time
in
G,.
A
All
right,
I,
think
that
makes
sense
to
me
to
everyone
agree
with
that
that
we
want
to
kind
of
come
up
with.
You
know,
a
small
guide
that
is
probably
going
to
be
mostly
links
to
other
things.
That
won't
agree
with
that.
Do
that
is
part
of
our
medium-term
plans
or
do
go
to
kind
of
put
that
more
in
the
back
burner.
A
Right,
so
we
will
keep
this
one
em
in
there
moving
on.
We
have
issue
number
62.
This
is
pre-conference
education
event,
so
it's
related
to
the
previous
on
what
is
a
little
different.
The
idea
with
this
one
is
that
this
is.
It
would
be
like
an
in-person
workshop,
essentially
for
conference
organizers
and
people
involved
that
will
kind
of
help
them.
You
know,
learn
y'all.
What
is
your
COC
response?
Look,
like
you
know
things
like
this.
How
do
you
phrase
things
to
be
more
inclusive?
A
A
If
there's
gonna
be
a
conference
that
involves
a
lot
of
node,
then
you
could
there
could
be
like
a
work
one
to
two
day
workshop
before
the
house
beginners
get
up
and
running
with
no
to
sort
of
like
bootstrap,
attendees,
I
love
it
so
that
they're,
you
know
more
prepared
to
take
in
the
talks
and
things
like
that.
I.
B
Feel,
like
Ashley
may
have
already
kind
of
done
that
recently,
with
unknown
with
their
node
together
workshops
and
obviously
they
can't
you
around
before
every
conference.
But
maybe
we
can
kind
of
take
what
Ashley
and
others
have
created
there
and-
and
it
feels
like
it'd,
be
pointless
to
create
something
completely
new
when
we
have
something,
that's
just
been
created
and
seems
quite
awesome,
a.
C
A
Ok,
so
maybe
an
action
item
for
this
is
she's
physically
is
just
said.
Yeah
reach
out
to
Ashley
and
say
you
know,
was
the
status
of
this
right
now,
there's
just
something
much
so
here,
because
a
lot
of
these
issues
are
pretty
old
they're
from
last
year,
so
you
know
I
think
a
lot
of
them,
which
is
a
little
outdated
yeah.
This
is
before
note
together
came
around.
Does
anyone
agree
with
that.
A
Alright
and
the
last
program
we
have
is
number
96-
this
is
getting
started
in
nodejs
program
and
I'm
kind
of
tracing
through
some
of
this,
oh
yeah.
So
this
is
kind
of
an
education,
onboarding
type
thing.
There's
this
perception
that
note
is
hard
to
get
into
this
began
yeah.
If
you're
new,
to
note
you
will
learn
about
node,
you
go
to
know,
Jas,
calm
and
there's
not
like
really
any
getting
started
guides,
or
anything
like
that.
Now
you
can
download
it.
C
Docs
working
group
are
we
sure
this?
Is
this
thing,
so
there's
there's
two
possible
things
that
this
can
be
either
there's
I'm.
So
the
getting
started
thing
that
you
mentioned,
which
is
more
or
less
what
we
currently
point
to
node
school
for
all.
But
we
don't
point
to
it
in
the
clearest
of
ways
right
now
and
there's
also
a
ok,
you
want
to
start
contributing
to
core
and
now
what
sort
of
thing
where
that
gets
even
more
difficult
and
it's
pretty
difficult.
A
B
And
I'm
interested
in
both
when
I
read
this
issue,
the
thing
that
I
always
think
about-
and
I
mentioned
this
in
slack
and
a
couple
of
days
ago,
kind
of
you
know,
as
you
said
in
the
beginning,
like
you
go
to
note,
you
download
nodes,
you
look
at
the
API
Docs
to
me.
That's
not
very
accessible
approach
and
I
know
that
node
school
exists
again
in
slack.
I
was
like
that.
Doesn't
really
work
for
me
because
it
feels
like
a
stutter
journey
rather
than
a
smooth
one.
B
B
You
know
not
a
massive
here's:
how
to
build
a
full
stack,
overly
secure,
app,
but
just
kind
of
his
kind
of
way
to
get
started
and
again
maybe
we
could
even
take
kind
of
the
materials
from
from
Ashley
with
no
together
to
kind
of
start
to
not
not
to
copy
it
necessarily,
but
to
kind
of
find
a
good
starting
point
with
that
and
in
create
guides,
because
I
think
that's
something.
That's
that's
really
missing
from
our
front
page
as
well
as
mentions
two
things
like
node
school.
B
If
you
want
to
learn
anything
further,
so
I'm
interesting
that
part
but
I
am
also
interested
in
getting
started
with
the
internals.
But
it
sounds
like
two
very
separate
issues.
So
I
don't
know
if
we
want
to
create.
You
know
split
this
up
Institute
because
it
feels
like
one
for
the
community.
You
know
who
just
want
to
learn
how
to
get
started
with
node
and
then
14.
Ok,
I
know
node.
Now
how
can
I
improve
it?
So
it
feels
like
two
separate
issues:
yeah.
C
B
C
C
C
E
Is
you
know
I
mean
ashley
is
a
wonderful
exception
to
that
rule
and
there
are
others
as
well,
but
by
and
large
people
what
was
the
word
pedagogy
here,
how
to
teach
how
people
learn
and
so
right
I
lost
my
train
of
thought,
but
that
was
basically
it.
I
think
I
got
my
point
across
and
I
didn't
take
any
notes
on
what
I
just
said.
So
now,
I'm
gonna
type
thanks.
I.
B
Agree
with
everything
you
just
said
I'm.
I
also
think
as
a
secondary,
but
almost
as
important,
and
you
know
kind
of
waiting
for
this
is
that
it
gets.
Other
team
are
working
groups
working
together
because,
as
I
discovered
I
think
this
week
or
the
end
of
last
week
when
I
was
last
answer,
questions
and
slack,
they
don't
really
talk
to
each
other,
and
so,
if
we
can
all
kind
of
collaborate
in
a
way
that
no
one
team
has
to
deal
with
like
this
huge
task,
then
we
can
make
friends
and
have
fun
and
I.
C
A
G
A
And
so
I
feel,
like
the
consensus
and
correct
me
if
I'm
wrong
is
that
this
you
know
in
and
of
itself
is
not
something
that
is
in
this
working
grace
purview,
but
the
value
we
can
add
is
to
kind
of
help
like
corral.
This
and
kind
of
get
the
ball
rolling
on
that,
and
then
that
should
be.
Our
involvement
does.
Does
that
accurately
reflect
what
we're
all
thinking
right
now
I
would.
B
B
A
Alright,
so
that
is
I
think
all
of
the
program
things
so
the
other
ones
that
I
skipped
over
was
there's
one.
That's
document
program
issue
structure-
and
this
is
this-
is
more
of
an
administrative
task,
and
this
is
essentially
documenting
how
we're
going
to
document
programs
is
kind
of
a
meta
issue.
So,
like
we
have
this
concept
of
programs.
B
A
Are
you
know
this
sort
of
like
outreach,
kind
of
thing
that
isn't
necessarily
like
internal
to
only
this
working
group,
it's
kind
of
working
with
others,
but
we've
never
actually
really
defined
this?
This
is
just
kind
of
thing
that
we
know
about,
and
so
this
issue
is
like
actually
going
in
and
defining
what
is
a
program?
What
does
it
mean?
You
know,
how
do
we
get
involved
with
stuff
like
that.
C
About
so
I
do
have
a
note
of
something
that
has
been
on
my
plates
that
I'm
hopefully
and
be
doing
within
the
next
two
weeks.
We've
got
a
little
bit
delayed
because
the
v6
release
and
such
so
we
kind
of
have
a
need
for
an
actual
IRC
moderation
policy,
because
IRC
has
some
technicalities
and
things
around
at
the
don't
quite
fit
into
how
our
github
policies
like.
When
do
you
kick
people
from
channels
and
stuff?
Do
you
need
to
et
cetera?
E
C
B
C
Hardware
I
build
used
to
use
it,
but
now
they
use
ifsc
so
get
ur
has
some
really
bad
problems
with
moderation,
because
you
can't
really
do
it.
Also.
None
of
us
pay
attention
to
the
ghetto
chanters
channels
because,
quite
frankly,
we
already
pay
attention
to
like
two
or
three
channels.
So
it's
just
too
much.
C
E
C
E
I,
just
really
really
quickly
wrap
up
with
git
er.
What
I
was
going
to
say
it's
just
that
I
think
a
decision
needs
to
be
made
at
a
higher
level
as
to
whether
or
not
we
you
know
keep
including
these
links
to
get
or
keep
20
people
there.
If
we're
going
to
point
people
there,
we
need
to
moderate
the
rooms.
If
we're
not
going
to
moderate
the
rooms,
we
need
to
stop
pointing
people
there,
but
we
got
to
make
a
decision.
We
got
to
go
one
or
the
other.
We
can't
keep
doing
this.
C
A
E
So
the
question
is:
do
we
want
to
open
it
the
tsc
repo,
or
does
it
make
more
sense
to
open?
It
include
inclusivity
repo
where
we
can
gather
information
like
where
are
their
getters,
that
exists
right
now
and
who
is
or
isn't
moderating
them
and
how
much
uses
they
get
and
then,
when
we
have
that
all
collected
dump
it
on
the
tsc
or
do
we
want
to
inflict
the
you
know
the
back
and
forth
and
lengthy
conversation
on
the
tsc?
E
B
Like
the
idea
of
having
it
in
the
inclusivity
group,
just
you
know
cuz
your
case
was
kind
of.
We
should
probably
collect
data
before
we
bring
it
to
the
TSE,
because
I
imagine
the
Tennessee
is
quite
busy
and
if
we
can
provide
them
with
as
much
information
as
possible
to
begin
with
and
I
feel
like
our
issues
are
probably
nearly
cell
block,
wicker
I.
B
An
issue
in
the
increase
in
between
working
group
might
be
a
good
place
to
callate,
where
we
manage
and
get
sir
and
then
you
know
each
person
individually.
Could
maybe
you
know
pl1
change.
You
know,
depending
on
where
it
where
they
are
in
the
repos
or
we
can
even
you
know,
get
people
from
outside
the
group
to
kind
of
collaborate
as
their
first
pull
request
or
something
I've
know.
Maybe
I'm
thinking
too
much
about
this,
but
there's
some
scope
to
do
see.
Some
things
sounds.
B
B
D
A
Yeah
I,
I
used
to
use
it
more
than
I
do
now.
It
really
took
off
in
Johnny
5,
so
like
25
uses,
I
main
communication
mechanism
as
well
as
a
lot
of
related
projects.
So
that's
you
know
why
the
hardware
working
group
uses
it,
because
that
you
know
there's
mostly
johnny
five
people,
and
I
should
also
mention
the
hard
working
group
is
more
or
less
defunct.
It
doesn't
actually
do
working
group
things
anymore
for
the
most
part,
ok,.
E
A
B
A
Hey
I'm
gonna
recommend
is
like
final
action
items
just
to
make
sure
we
do
it
because
we've
problem
with
a
lot
of
action
aisles
we
haven't
assigned
any
of
them.
Alright,
then
we
get
a
PRN
for
the
notes
and
then
I'll
take
the
notes
and
create
another
issue
that
basis
as
these
are
the
action
items
and
let's
find
people
to
sort
of
scare
head
them.
B
A
That
I
think
we'll
go
ahead
and
close
it
out
everyone
for
joining
this
yeah.
This
was
really
productive,
I'm
happy
about
it
awesome
Anna
will
try
and
get
another
meeting
schedule.
Probably
two
weeks
from
now.
At
the
same
time,
yep
excuse
me:
I'm
eventually
would
like
to
get
your
wrote
a
meeting
time
zone,
but
for
the
time
being,
we
can
just
kind
of
keep
with
this.