►
From YouTube: CHAOSS.Community.April.21.2020
Description
CHAOSS.Community.April.21.2020
B
D
C
D
I
was
just
I,
think
Matt
I,
think
your
pull
request,
merged
and
then
I
realized
Kevin
had
also
submitted
a
pull
request
with
the
exact
same
change:
oh
so
I'm
trying
to
close
Kevin's
without
merge,
but
that
isn't
working
cuz
of
not
working
I
like
ten
minutes
before
this
meeting
and
I
was
like
I'm
gonna.
Do
the
pull
requests?
No.
B
Cool,
so
here
a
few
of
my
you
can
kind
of
see.
I've
done
a
few
things
on
here
and,
of
course,
as
people
want
to
add
things
or
bring
things
up.
That
is
absolutely
fantastic,
so
I
think
the
first
thing
that
I
want
to
talk
about
or
just
kind
of
keep
people
posted
on
is
we
have
the
cast
community
manager
position
posted
now.
Indeed,
I
didn't
change
the
title
of
the
position
just
a
little
bit
to
include
remote
work
as
we
were.
Getting
that
question
a
fair
amount.
B
We
have
to
advertise
it
just
in
a
single
city
without
pay,
we
have
I,
think
we
just
posted
it
on
Friday
or
Saturday
is
when
it
ended
up
getting
posted
I'd
say
we
have
about
60
applicants
60
whoa.
Now
this
is
not
like.
Not
everybody,
like
is
a
good.
You
know
they
qualify
well
for
the
position,
but
so
if,
if
you
could
all
help,
that
would
be
great
to
continue
to
get
the
word
out.
I'd
love
to
broadcast
as
widely
as
possible
to
get
the
best
possible
candidates
for
the
job.
B
D
Is
fairly
common,
every
time
I've
tried
to
hire
a
community
manager,
the
the
number
of
just
unqualified
candidates,
compared
to
what
we're
looking
for,
especially
for
open
source
community
managers,
because
you
get
all
kinds
of
people
who
know
how
to
tweet
and
do
Facebook
and
who
manage
like
leasing,
communities
of
apartment
buildings.
You
get
all
kinds
of
crazy
applicants
for
community
manager,
positions
that
are
just
not
you.
B
B
B
Didn't
at
the
moment,
I
didn't
have
time
this
morning,
I
just
changed
the
title
to
indicate
that
this
is
remote
work.
So
if
you
want
to
change
that
question
feel
free,
does
anybody
have
any
questions
on
this
still
just
like
I'm
just
super
excited?
This
is
gonna
happen,
as
always
thanks
to
the
Alfred
Sloan
Foundation
for
providing
support
to
actually
allow
this
to
happen.
B
F
B
So
this
was
a
group
of
folks
that
was
king,
who
joins
that
calls
regularly
who's
and
I
think
he's
a
huawei
was
trying
to
think
through
the
issue.
Metrics
I
haven't
looked
in
this
in
the
tool
in
tool
in
in
a
lot
of
detail,
but
he
was
suggesting
that
there
was
just
trying
to
get
their
head
around.
How
issue
metrics
are
understood,
so
I
thought
a
chart
like
this
could
be,
could
be
useful
again.
B
G
I'm
not
gonna,
say
I
fully
comprehend
it
yet,
but
I'll
throw
out
there
that
it
like
visualizing
how
they
relate
to
each
other
and
the
interrelation
of
them
and
also
I
love
that
they're
annotated,
as
you
know,
ratios
versus
media
and
like
this
is
that's.
It
looks
quite
nice
to
me
from
that
angle,
but
yeah
not
a
comprehending
all
of
it
just
yet
like
well,
it
does
this
is
this
is
not
perfect.
You.
C
B
So
these
are
I
think
these
are
metrics
that
they
were
trying
to
work
off
of
on
release
and
I
I'm
with
Matt,
but
being
able
to
visualize
the
relationship
between
different
issue,
metrics
or
being
able
to
visualize
between
different,
say,
pull
request
metrics,
because
they're,
it's
kind
of
in
that
same
category
might
be
a
useful
exercise
to
do.
We
don't
have
to
do
it
now,
but
might
be
a
useful
exercise
to
do
at
some
point
to
try
to
think
about
what
these
metrics
mean
in
relation
to
one
another
I.
C
C
C
C
B
C
The
way
the
easier
way
to
handle
it
the
way
I've
provided
data
for
people
is
okay.
Here
is
your
your
initial
here's
your
your
first
closed
date,
and
here
is
your
last
closed
date
or
here's
the
length
of
time
between
when
I
was
opened
and
first
closed
and
the
length
of
time
between
it
was
I
was
opened
and
last
closed.
C
B
Let
me
commit
I'll
come
with
this
a
different
way.
This
was
put
together
by
a
group
of
folks
who
were
trying
to
use
trying
to
look
at
the
metrics
that
had
been
released.
Okay,
awesome.
This
is
how
they
kind
of
observed
the
relationship
between
the
metrics.
So
this
is
the
message
that
they're
getting
as
a
group,
so
it'd
be
like
I'm.
A
group
of
five
of
us
sat
down,
took
the
release
metrics
and
said
how
do
these
all
fit
together.
B
A
B
E
B
H
B
A
lot
of
time
on
this
I'm,
just
I,
thought
it
was
nice
exercise
by
a
group
of
people
trying
to
get
their
head
around
metrics,
who
aren't
necessarily
involved
in
the
development
of
those
metrics.
So
I
think
this
is
one
of
the
first
visuals
that
I'm
seeing.
That
is
how
people
are
observing
these
metrics
yeah.
J
J
So
let
me
give
a
different
angle,
because
we're
talking
about
community
health
I
happen
to
be
okay,
let's
not
use
the
I
okay,
some
people
happen
to
be
edge
cases
when
it
comes
to
systemic
things,
like
issues
and
take
my
word
for
it.
There
there
are
several
patterns
where
issues
become
nightmare
after
nightmare
after
nightmare.
J
When
we
talk
about
issue
age,
we're
saying
the
typical
issue
that
will
be
open,
resolved
and
closed
or
the
typical
issue
that
will
be
opened,
and
basically
one
of
three
things:
either
it's
a
duplicate
or
it's
out
of
scope,
or
it's
not
an
issue
like
works
as
expected
when
it's
actually
that
I
think.
If
we're
talking
about
looking
at
the
health
of
the
community
issue
wise,
we
should
kind
of
look
into
issues
that
really
kind
of
one.
Far
beyond
the
typical
I
have
a
bunch
of
examples.
Just
look
look
my
username
github
I!
J
Guess
I
was
just
you
know,
creating
sample
data
for
everyone,
but
I
have
issues
that
you
know
go
for
years
and
basically
I
don't
yet
except
a
few
labels
here
and
there
and
the
Bob
that
keeps
telling
me
will
close
it
now
and
I'm
like
no.
You
know
so
so
there
are
patterns
for
issues
that
basically
become
nightmares,
and
those
are
issues
that
get
called
the
duplicate
just
because
they're
not
understood
or
you
know,
closed
and
another
issue
is
opened
by
a
more
preferred
way
to
frame
it
by
the
project.
J
These
are
problems
and
open
source
because
you
lose
the
traceability
or
you.
You
know
you
lose
the
originator
of
the
issue
and
I
think
those
those
all
factored
into
the
age
they
factor
into
what
you
call
a
resolved
issue,
and
hopefully
now
github
is
getting
a
different
name.
For
that,
like
there
are
some
that
that
are
gonna,
be
bugs.
Some
will
be
discussion,
so
yeah,
so
I
think
we
want
to
take
the
angle
of
when
issues
go
right
and
when
issues
go
wrong
and
yeah.
Sorry
about
that,
I.
B
Got
it
I
tried
to
jot
it
down
as
I
thought
that
was
a
nice
right.
This
is
this
is
under
the
assumption
that
there's
a
single
issue
open
a
single
issue
commented
on
and
a
single
issue
closed
and
that
issue
kind
of
lives
in
isolation
and
that
there's
not
a
second
issue
open
along
the
same
lines
right.
C
Of
all
T
yeah
I
mean
that
this,
but
I
think
you
could
ask
those
questions.
I.
Think
the
discreet
metrics
that
we're
building
are
right
now
we're
building
metrics
I.
Think
at
a
level
that
is
very
discreet
and
succinct
and
answering
questions
are
trying
to
identify.
Behavior,
like
you
described,
I,
think
that
couldn't
be
done
using
a
number
of
the
metrics
pulled
together.
Maybe
maybe
what's
missing
is
some
kind
of
similarity
checking
to
see
what
issues
are
actually
similar
to
each
other.
C
I
I
think
different
projects
have
patterns
of
just
quickly
decide
some
things,
not
something
they're
interested
in
including
so,
if
it's
a
feature
request,
they
just
get
rid
of
it
and
close
it,
and
if
somebody
really
wants
that
they
might
reopen
it
I
think
something's
a
bug.
Maybe
they
don't
want
to
publicly
acknowledge
that
bug,
so
they
close
it
I
think
there
are
different
cultures
and
open-source
projects
that
treat
issues
in
different
ways
and.
J
I
think
communication
barrier
sadly
treats
issues
in
a
completely
different
way.
Yeah.
You
know
people
prefer
to
take
issues
that
they,
you
know
feel
they
can
do
something
about
and
I
mean
that's
that's
good,
but
I
mean
it's
kind
of
like
discrimination,
but
it's
not
it's
it's
for
the
right
reason.
People
want
to
stay,
engaged
and
motivated
to
work,
and,
and
so
it's
a
gap
in
issues.
J
D
J
G
B
So
I,
thank
you
I
guess.
Part
of
it
is
something
like
this
useful
I
mean
to
me.
It
is
so
when
I
see
people
trying
to
use
metrics
in
ways
or
get
their
head
around
metrics.
So
is
this
something
we
should
ever
provide
a
community
like
here's
an
example,
visual
of
how
metrics
are
ich
two
metrics
might
be
understood
collectively
we
could
put
it
this
way.
Here's
an
example
of
how
pull
requests
must
shoot.
Metrics
might
be
understood
collectively,
yeah.
E
H
H
K
B
Yeah,
so
I
was
thinking
this
right,
while
this
conversation
was
going
on,
I
think
focused
areas
like
around
issues
or
requests
might
kind
of
lend
themselves
the
thinking
about
how
those
specific
metrics
are
related
directly
or
another
versus
other
focused
group
areas.
I
think
the
collection
of
them,
not
necessarily
the
relationship
between
them
that
helps
define
the
focus
area,
so
I
think
some
focus
areas
might
be
inclined
for
this
type
of
visualization.
Another
focus
areas,
perhaps
a
little
bit
less
so.
F
I
I
Actually,
they
made
some
more
edits
to
that
document
today
and
then
I
have
gone
through
and
I
have
basically
pushed
the
the
release
through
for
the
the
new
common
metric.
So
the
only
thing
that
we
were
waiting
for
to
go
live
on.
The
website
was
the
note
to
get
added
to
the
new
metric
repository
page
so
which
I
think
you
and
I
both
had
a
commit
to
address
that.
I
I
E
I
E
C
Was
there
was
one
where
there
was
a
modification
to
an
existing
metric
and
I?
Think
I
don't
recall
specifically,
but
what
I
think
I
remember
is
that
we
are
not
gonna
release
the
modifications
to
existing
metrics
that
those
would
go
through
a
regular
review
period.
That's
right!
You
know
they
just
wait
until
the
regular
review
period.
F
I
B
E
E
If
the
community
grows
too
much,
you
have
a
limit
of
ten
thousand
messages
that
you
can
see,
and
so
especially
larger
projects
might
not
be
a
problem
for
kids,
but
larger
projects
have
problem
that
you
only
see
in
each
Channel,
the
last
ten
messages
or
so,
and
you
miss
a
lot.
Also
slack
is
not
built
for
communities
it's
built
for
corporations,
so
there
are
no
community
management
features
around
enforcing
code
of
conduct
and
or
just
moderating
what
is
happening.
C
G
G
Yeah
I
guess
there's
kind
of
two
questions
that
I
tend
to
like
to
break
out
it's
like
do.
We
need
a
synchronous
communication
site
for
some
reason
like
or
we
can
real-time
chat
with
each
other
and
then,
if
the
answer
is
yes
to
that,
like
it's
lack
the
right
answer
versus
discord
or
IRC
or
whatever
other
channel
so
I'd
be
curious
like
it
sounds
like
the
answer
has
been
noticed,
a
need
for
synchronous,
communication
and
then
there's
you
know
a
secondary
know
of
slack.
So
maybe
it'd
be
helpful
to
have
those
two
separate
so.
H
Most
discourse
combo,
instead
of
a
slack
necessarily
still
I,
have
noted,
and
my
partner,
Selene
and
I
were
actually
talking
about
this.
Just
recently.
A
synchronous,
communication
and
synchronous
communication
are
kind
of
this
dialectical
tension
that
a
lot
of
people
are
like.
Okay,
if
you
do
one
people
get
tired
and
they
don't
necessarily
want
to
reproduce
that
conversation
in
the
other.
So
if
you
start
adding
asynchronous
communication,
people
stop
coming
to
meetings
what
those
meetings
are
also
kind
of
limiting
the
scope
of
who
Kanak
or
cannot
participate.
H
So
what
a
lot
of
people
have
done
is
they've
created,
meeting
archives
that
are
interactable
via
discourse,
and
then
they
have
a
chat
system
attached
to
that
matter,
most
on
the
bottom
of
the
video
meeting.
So
essentially,
what
that
looks
like
is
we
have
this
meeting?
It's
recorded
goes
onto
YouTube,
you
start
a
new
thread
on
discourse.
Discourse
has
a
conversation
about
it,
and
if
anyone
wants
to
make
that
a
part
of
their
discussion
asynchronously,
they
can
go
into
a
modern
US
channel
to
do
it.
B
E
J
J
We
really
manage
the
front
end,
which
is
github
issues
and
weekly
or
sorry
bi-weekly
meeting
we
talk
around
how
we
want
to
manage
the
project
and
it's
black,
there's
also
integration
that
allows
us
to
zoom
that
allows
us
to
github
so
and
calendar
event.
So
everything
related
to
the
project
comes
into
that
one
dashboard.
J
Just
the
last
bit
is
I
believe
from
my
perspective.
If
people
are
affected
by
friction
in
certain
applications,
I've
tried
them
all
and
for
me
the
least
friction
is
with
slack.
You
know,
I'm
gonna,
be
honest.
I
have
friction
following
the
mailing
list.
Opening
email
even
get
help
notifications
and
basically,
when
I
need
to
like
make
sure
I'm
not
losing
sight
of
what
I
need
to
do
now.
J
F
J
C
Yeah
I'll
just
and
the
question
it
costs.
If
you
have
a
ddu
account,
you
can
get
significantly
discounted
slack
like
so
I'm
paying
like
I,
have
fifty
three
users
in
one
of
my
classes.
Right
now
and
I.
Think
it's
costing
me
like
not
that
much
money,
maybe
sixty
dollars
a
month
or
something
like
that,
and
so
the
cost
hasn't
been
a
big
issue
for
me
slack
and
it
could
be
slack
or
it
could
be
this
matter
most
it's
just
another
tool.
C
But
for
me
my
email
is
overwhelming,
and
so
mailing
lists,
like
I,
put
a
lot
of
rules
in
and
I
try
to
get
to
the
chaos
stuff,
but
it
is
I
get
so
much
email
because
I
teach
large
classes
and
my
my
university
likes
to
send
emails
to
everyone
so,
like
anything,
other
than
email
is
I
vote
in
favor
of
I.
Don't
care
what
what
it
is,
but
something
besides.
Email
is
always
a
better
way
to
find
me
and
always
a
better
way
for
me
to
getting
engaged
there.
It's.
A
G
It
I
definitely
helped
I
mean
the
short
version
for
one
of
the
communities
I
manage.
We
I
migrated
people
off
of
a
semi
active
IRC
that
people
were
getting
frustrated
because
they
were
in
different
time
zones
and
formed
ailing
lists
and
merged
them
into
a
single
discourse,
and
then
you
can
use
different
topics
as
different
mailing
lists
subscriptions.
So
per
topic
is
basically
its
own
mailing
list,
but
whenever
somebody
responds
to
the
mailing
list
it
goes
to
discourse
as
well.
So
you
just
kind
of
like
choose
your
own
interface
to
participate.
It's
wonderful!
G
B
G
It
took
me
like
probably
like
one
week
of
paying
primarily
attention
to
that
to
deactivate
stuff
get
people
migrated
over
get
the
topic
set
up
correctly
and
start
documenting
things
and
then
like
another
week
or
two
of
tidying
that
up
as
we
learned
how
like
what
patterns
we
actually
needed.
So
it's
it
just
takes
a
community
manager
type
of
work
with
some
technology
skills
because
this
course
is
really
powerful
and
what
it
lets
you
configure
and.
D
D
Because
you
know
that
I
would
be
okay
with
that.
We've
had
this
discussion
a
bunch
of
times
in
this.
In
this
call,
and
my
my
concern
has
always
been
that
what
I
don't
want
and
I've
seen
this
happen
in
too
many
communities
where
you've
got
you've
got
people
who
use
some
sort
of
forums.
You've
got
people
who
use
the
mailing
list
and
they
are
rarely
the
same
people.
D
So
you
get
two
completely
separate
discussions
about
the
project
happening
at
different
forums
and
that's
that's
what
I'd
I'd
like
to
avoid
I
mean
and
I
I
sorta
have
a
love-hate
relationship
with
slack,
because
on
the
one
hand,
it's
really
nice
to
be
able
to
ping
people
and
get
an
immediate
sort
of
answer,
but
being
in
a
different
time
zone
from
a
lot
of
the
people
that
I
work
with
I
I.
Just
look
at
slack
in
the
morning
and
I.
D
G
H
So
there
is
some
work,
that's
kind
of
already
been
done
where
you
can
have
a
conversation
in
matter
most
and
then
over
that
conversation,
someone
with
admin,
privileges
or
something
like
that
can
create
a
thread
in
discourse
using
a
specific
set
in
matter
most
in
that
synchronous
conversation
moves
into
a
thread
for
asynchronous
conversation
later
in
this
course,
so
matter.
Mouse
can
integrate
kind
of
with
discourse
to
create
that
thread
and
allow
for
any
synchronous
input,
yeah.
D
But
it's
actually
it's
less
that
it's
more
like
the
the
conversation
reached
a
natural
conclusion.
You
know
what
I
mean
I
just
didn't
happen
to
be
part
of
it.
Cuz
I
wasn't
awake
yeah,
so
like
chiming
and
later
feels
weird,
because
I'm
like
but
they've
they've
already.
You
know
resolved
this
and
now
I'm,
just
like
adding
random
commentary.
D
H
The
cultural
aspects
of
asynchronous
response
to
a
synchronous
conversation
I
mean
there
are
solutions
outside
of
technology
that
might
be
able
to
solve
that
like
implementing
a
culture
of
continued
conversation
where
people
are
like
yeah.
This
seems
important
enough
that
we
should
probably
pop
it
into
a
thread,
and
then
they
just
tagged.
The
community
manager
and
the
community
manager
runs
the
spirit
to
pop
that
conversation
into
discourse.
H
F
D
So
if
had
this
conversation
multiple
times
but
I
think
we
should
I
think
we
should
table
table
it
and
then
not
to
have
it
again
that
have
it
again
once
we
actually
have
a
community
manager
on
board,
because
I
think
it's
important
for
the
community
manager
to
be
an
integral
part
of
this
conversation.
Yeah.
B
Totally
all
right
cool
yeah,
it
had
been
a
while,
since
we
had
the
conversation,
so
I
figured
Mike.
You
know
it's
not
always
a
terrible
thing
to
reflect
on
and
it
does
make
me
wonder.
I
mean
listening
to
everybody
here
on
these
calls
and
our
calls
are
getting.
They
have
more
participants.
If
you
haven't
noticed
and
I'm
wondering.
D
B
B
The
next
thing
that
I
had
was
the
metrics
repository.
So
this
is
a
this
gives
me
a
headache,
so
we
have
in
github.
We
have
a
lot
of
repositories
and
a
number
of
the
repositories
are
dedicated
to
say
software.
The
repositories
are
dedicated
to
the
working
groups
right
so
a
value
and
DNI,
and
common
and
evolution
all
that
kind
stuff,
and
we
have
this
this.
In
governance,
we
have
a
repository
dedicated
for
governance
and
we
have
this
repository
called
metrics
and
it's
a
it's
a
high
profile
repository
because
it's
named
metrics
so
kind.
B
D
B
As
a
way
to
just
kind
of
capture
all
metrics,
before
long
before,
we
were
doing
any
of
the
working
groups
and
all
this
these
focus
areas
and
all
that
kind
of
stuff.
So
it's
it's
old,
it
gets
updated,
probably
about
one.
So
what
is
the
repo
say?
Whatever
the
repo
says
is
how
long
it
gets
updated.
It's
not
often,
and
it's
usually
just
kind
of
like
a
one
giant.
B
We
need
to
update
this
thing.
Let's
update
it
all
right
now
and
then
we'll
touch
it
again
in
six
months.
So
it's
not
exactly
this.
Like
really
graceful
process
by
which
this
repository
is
maintained,
I,
don't
know
quite
what
to
do
with
this
repository.
I
don't
know
if
anybody
else
has
thought
about
this
repository
I
actually.
J
Did
but
not
about
this
particular
one.
So
so,
when
we
did
the
badging
structure,
we
thought
to
ourselves
there's
the
diversity
and
inclusion
events
badge
and
then
there's
the
diversity
and
inclusion
project
badge
badging
right.
So
those
are
two
repos,
but
most
people
want
to
go
to
the
you
know:
badging,
slash
diversity
and
inclusion
and
see
what
badges
are
there.
So
it's
kind
of
like
an
umbrella
repo
that
reflects
updates
that
are
happening
in
other
repos
and
includes
common
resources
for
for
working
in
other
weak
repos.
J
Under
that
role,
you're
going
to
find
links
to
go
to
the
places
of
interest
in
the
organization
that
are
of
the
particular
interests
you
have
for
that
particular
function
or
role
you're
coming
to
the
repo
with
it
could
also
be
a
place
where
you
would
have
issues
to
propose
new
metrics
that
don't
necessarily
fall
under
a
working
group
or
to
ask
a
general
question
about
metrics
in
an
issue.
So
I
think
with
automation.
J
Barely
keep
this
reflective
of
you
know,
updates
to
all
the
metric
repos.
You
know
it's
obviously
not
a
short-term
idea.
It's
like
something
you
could
develop
out
of
this
I
think
it's
important
to
have
kind
of
like
fast
lanes,
for
people
to
come
into
a
project.
You
know
I've
looked
at
many
orgs
where
they
have
so
many
repos
that
you
could
group
together
and
you
just
give
up
looking
at
which
repo
you
want
to
look
into.
First,
if
you
don't
know
any
context,
so
it's
like
the
context.
Energy
for
metrics.
J
B
So
one
of
my
one
of
my
things,
I
get
told
fairly
regularly,
I
mean
I,
don't
know
like
a
couple
times:
I
went
to
the
metrics
repo
and
it
doesn't
make
a
ton
of
sense
right
so
I'm,
looking
at
I'm
looking
at
this
long
list
of
metrics
some
that
have
links
some
of
that
don't
have
links
some
that
have
an
assignment
to
a
working
group.
I'm
like
oh
yeah,
don't
look
at
that!
Go
to
the
webpage
and
look
at
right
away.
Seven
people
now
for
the
kind
of
a
canonical
list
of
metrics.
You.
G
The
core
question
to
me
is
like,
what's
the
front
door
on
github,
because
it's
super
unclear
even
to
a
reasonably
experienced
github
user,
like
what,
where
you
should
start
and
in
the
past,
that
means
like
I've,
made
a
mono
repo
like
there's,
you
know
whatever
org
slash
community
is
kind
of
my
default,
because
it's
community
oriented
but
slash
metrics
like
yeah.
It
either
needs
to
be
the
most
up-to-date
thing
or
the
metrics
have
to
be
deleted
and
explained
what
a
metric
is
and
what
this
organization
does
maybe
reframing
it
that
way.
B
B
Have
a
question:
I
guess
for
a
working
group.
Folks,
often
in
your
working
groups,
do
you
actually
go
to
the
slash
metrics
site
to
look
at
like
documented
metrics
that
might
be
useful
in
in
your
respective
working
groups?
I
mean
that
was
one
of
the
intentions
right
that
we
would
just
capture
everything
there
I
go
to
the
website
and
look
there.
B
E
B
J
I
think
we
just
need
a
like
a
choreography
for
it.
You
know,
like
someone,
would
sit
down
and
say:
okay,
you
know
this
is
the
function
of
this
thing,
and
this
is
the
work
that
we
want
to
maintain.
You
know
the
work
load
versus
box
that
we
could
use,
so
we
don't
have
any
workflow.
We
just
have
like
bucks
to
report
an
issues
to
chase
down
on
it.
So
you
know
I
think
it's
just
finding
a
purpose
for
the
repo.
You
know,
I'm.
C
E
H
E
D
K
E
H
There
is
an
opportunity,
like,
obviously
you
can't
pay
anyone
to
do
anything,
but
as
long
as
the
individual
is
like
a
volunteer
or
a
community
member,
that's
not
actively
engaged
in
like
a
primary
matter
with
the
company.
If
you
encourage
people
to
go
on
to
Wikipedia
and
like
update
other
general
pages,
just
regularly
just
share
their
nothing
from
this
community
and
then
say:
I
got
it
from
here.
Once
enough
of
that
information
has
been
built
onto
Wikipedia,
there
becomes
a
necessity
to
index
where
that
information
is
coming
from,
which
usually
means
the
Wikipedia
page.
H
So
a
lot
of
people
have
been
able
to
organically
build
enough
reputation
on
the
site
for
it
to
necessitate
creating
a
new
page,
and
that's
just
encouraging
the
community
members
to
do
it.
So
what
did
digital
marketer
one
of
the
ways
that
we
conceived
of
doing
it
was
basically
a
share.
Your
knowledge
in
digital
marketer
engage
the
Facebook
group.
We
basically
just
had
these
campaigns
that
encouraged
them
to
go
out
on
to
Wikipedia
pages,
make
changes
and
add
information
based
their
expertise
and,
at
a
certain
point
in
time
that
information
kept
coming
from.
H
J
Brand
company,
so
it's
very
interesting
there's
one
thing
about
Wikipedia:
they
keep
chasing
me
every
year
to
donate
they're,
not
doing
very
well
in
terms
of
like,
like
they
are
getting
a
little
bit
of
a
desperate
vibe,
not
like
asking
me
to
donate
because
they're
in
a
good
shape
and
it's
a
good
effort,
but
rather
like
nobody's
listening.
You
know
any
money
kind
of
thing,
so
at
least
we
could
start
donating
and
then
see.
If
that
message
changes
then
there's
hope.
And
then
everything
with
the
video
I
don't
know
is
a
thing
out.
I.
C
B
A
J
I'm
sharing
my
screen
and
I
was
talking.
I
forgot
to
open
the
mic
before
I
started,
sharing
my
screen:
okay,
yeah
so
yeah,
so
I,
just
accidentally
tripped
on
this
when
I
was
like
looking
at
one
of
the
projects.
So
this
is
a
like
a
like
a
new
thing
we're
on
github.
You
basically
could
start
like
mentioning
people
telling
the
all
contributors
bought.
J
There's
like
a
contributor
here
who
is
like
not
represented
way
on
the
github,
repo
or
Fork,
and
then
they
kind
of
like
have
kind
of
a
well
structured
approach
to
make
sure
every
contributor
is
mentioned
and
I
guess
you
know.
This
is
a
very,
very
brief
introduction,
because
I've
seen
it
in
action,
I
haven't
really
went
through
their
dogs
but
yeah.
So
I
just
wanted
to
bring
this
to
the
attention
of
everyone.
I
think
chaos
good
use
it
I.
B
Yeah,
so
whether
this
is
the
solution
and
or
not
I'd,
at
least
like
to
encourage
people
to
think
about
how
we
can
recognize
all
contributors
in
the
chaos
project.
There
are
a
lot
of
people
doing
a
lot
of
great
work
that
aren't
necessarily
identified
and
I.
Don't
know
how
we
go
about
doing
that,
like
a
page
like
that
would
be
amazing.
Yeah.
H
One
of
the
coolest
ways
that
I
found
a
lot
of
youtubers
and
influencers
are
recognizing
patrons
and
people
who
have
contributed
to
their
channel
is
on
content
and
in
videos.
They're
like
hey,
we're
going
to
add
ten
people.
So
if
you
add
a
widget
on
the
blog
that
just
randomly
pulls
a
person,
it
might
be
a
good
way
to
recognize
them
in
active
content.
Mm-Hmm.
K
F
B
B
If
I
I
appreciate
it
and
then
kind
of
the
last
thing
is
just
an
update
for
a
google
Summer
of
Code
and
how
ricci
we
made
our
outreach
recommendation
again.
Oh
Ritchie
wants
to
announce
that
so
we've
made
a
recommendation
to
the
outreaching
program
and
then
google
Summer
of
Code
we've
also
made
our
recommendation
for
the
number
of
mentee
requests.
So
I
think
we're
good,
but
I
guess
is
the
update.
Everything
seems
to
be
moving
fairly
well
in
that
regard.
Both.