►
Description
Open source is the foundation of modern software development. It is the stepping stone to find, learn, and master code, and it’s how we build amazing things together. But collaborative and accessible open source projects depend on the efforts of dedicated maintainers and contributors to flourish.
In this panel, four experts will share their experiences growing and maintaining successful open source projects.
Moderated by Brandon Keepers (GitHub, far right), with (from left to right):
* Erika Heidi (DigitalOcean)
* Justin Dorfman (MaxCDN)
* Judy Gichoya (OpenMRS)
* Mike McQuaid (GitHub).
About Satellite:
GitHub Satellite 2016 was a celebration of the latest and greatest in development. Watch the recordings to learn how engineers, founders, activists, and beyond tackle the latest and most difficult challenges in software.
For more, join us in San Francisco on September 13th-15th for GitHub Universe, three days filled with the creativity and curiosity of the largest software community in the world.
For more information, go to githubuniverse.com.
A
Alright
welcome
everybody.
Thank
you
for
coming
today
we're
going
to
talk
about
maintaining
open
source
projects,
so
I
think
a
lot
of
us
have
seen
that
open
source
has
become
the
foundation
of
modern
software
development,
but
all
of
these
amazing
open
source
projects
that
we
use
have
real
people
behind
them.
So
today
we
wanted
to
bring
a
good
sampling
of
people
to
participate
a
lot
and
open
source
and
just
hear
their
stories
here.
What
it's
like
for
them
getting
started
an
open
source.
A
What
it's
like
to
grow
a
successful
open
source
project,
some
of
the
challenges
that
they
face
so
for
the
next
40
minutes.
We're
gonna
be
asking
these.
These
four
amazing
panelists
some
questions
I've
got
a
few
to
start
with,
but
in
about
10
minutes
or
so
I'm
going
to
start
asking.
If
any
of
you
have
questions
so
feel
free
to
start
thinking
about
that,
and
then,
when
we
turn
to
you
just
raise
your
hand
and
katelyn
over
here.
A
We'll
walk
around
with
the
microphone,
so
be
thinking
about
all
of
your
hard
questions
about
open
source
for
the
panel
so
to
introduce
the
panel
first
time.
Brandon
keepers
we're
a
good
hub
on
focusing
on
making
open
source
more
accessible,
making,
yet
the
github
product
better
for
open
source
to
my
right
here
we
have
Mike
McQuaid,
who
I've
had
the
pleasure
working
at
with
at
github
as
well.
A
Mike
works
on
the
homebrew
OSN
package
manager
project
and
he's
one
of
the
people
that
I'm
always
constantly
amazed
that
how
productive
and
effective
he
is
on
maintaining
his
project,
so
I'm
always
picking
his
brain
and
on
how
he
does
it
so
well.
Next,
to
Mike
we
have
judy
judy
katoya
judy
works
on
the
openmrs
project,
which
you
heard
about
in
the
keynote
this
morning.
Openmrs
is
this
fantastic
open
source
project
aiming
to
bring
medical
records
systems,
especially
to
the
developing
world,
but
I
was
talking
to
somebody
this
last
we
were
actually
I.
A
Think
Justin
was
telling
a
story
about
somebody
this
last
week
he
was
gonna,
be
on
a
panel
with
Judy,
and
this
person
was
a
doctor
and
they're
like
I've
heard
of
openmrs.
So
it's
very
well
known
across
the
medical
field.
Judy
is
also
a
doctor,
so
we're
going
to
ask
her
more
about
that.
What's
it
like
to
be
a
doctor
and
a
software
developer
next
to
Judy,
we
have
Justin
Dorfman,
so
Justin
works
he's
very
involved
in
a
lot
of
open
source
projects
like
bootstrap
being
one
of
them.
A
B
A
Here
how
we
can
contribute
to
open
source
in
in
ways
beyond
code
and
then,
finally,
on
the
end
we
have
Heidi
came
across
Heidi
actually
from
hacked
over
fest
the
shirt
that
she's
wearing
better
a
couple
years
ago.
It's
a
hackathon
that
digitalocean
sponsors
and
get
have
participated
in
this
last
year,
but
Heidi
is
participated
in
a
lot
of
open
source
projects.
A
A
C
C
Nobody
knew
how
you
could
actually
earn
money
from
open
source
or
how
could
you
actually
live
from
that
in
any
way?
So
it
was
really
like.
It
was
a
completely
different
reality,
but
eventually
like
in
the
2000s,
and
so
it
started
to
get
bigger
and
then
my
actual
first
contribution
was
really
a
few
years
ago,
because
I
use
it
to
share
code
a
lot,
but
it
never
actually
contributing
to
other
project
because
it's
different
right.
C
D
E
Sing
with
Erica
like
it
started
with
Linux
in
the
late
90s
and
I,
kept
having
this
issue
where
I
couldn't
print
out
my
homework,
because
there
was
no
printer
driver
compatible
with
my
linux
distro.
So
I
kept
going
to
my
teacher
yeah
I
can't
print
out
my
homework.
So
you
know
she
was
sick
of
hearing
that
excuse.
E
I
went
back
to
windows,
I
started
making
really
crappy
band,
or
you
know
punk
rock
band
websites
and
PHP
and
mysql,
and
then
it
was
until
2010,
where
I
wrote
a
blog
post
on
how
to
configure
nagios
an
oven
to
monitor
Cassandra
06,
the
first
version
of
Cassandra,
and
then
people
started
linking
to
the
post
and
writing
about
it.
And
I
was
that's
the
moment
where
I
was
like
oh
wow.
This
is
this
is
powerful,
so
doc
I.
That
was
my
crack
pipe.
B
I
can't
say
that
I
started
out
with
open
source.
I
was
as
medical
in
medical
school
in
Kenya
was
struggling
with
the
HIV
epidemic.
We
needed
a
better
way
to
organize
medical
records
for
the
patients
who
were
seeing
and
I
was
already
tinkering
around
computing,
and
so
you
know
I
went
in
and
was
frustrated
because
sometimes
you
spend
so
much
time
outside.
You
know
like
tracing
results,
things
that,
for
me,
I
felt
like
was
called
walk,
which
were
you
know,
annoying
me
and
I
thought.
B
Well,
maybe
if
I
had
a
system,
this
would
be
easily
money.
So
I
started
doing
meeting
my
needs
and
it's
been
my
focus
building
programs
that
are
used
for
patient
care
and
helping
doctors
before
I
knew
about
open
source,
so
I
started
getting
involved
in
computing
and
building
software
and
having
a
fun
believe
that
it
should
be
free
before
I
started
getting
into
the
box
of
these
free
software.
These
open
source
software-
and
you
know
I,
guess
non
there,
but
I
can't
tell
you
like
really
when
the
transition
here.
That's
awesome.
F
Sir,
oh
I
was
loud,
yeah
I,
think
I
boringly,
like
to
the
other
people
in
the
panel
Linux
was
my
sort
of
gateway.
Drug
I
went
and
studied
computer
science
at
college,
hadn't
really
ever
used
linux
or
whatever
before,
but
it
seemed
like.
If
you
want
it
to
be
one
of
the
cool
kids
or
not
cool
kids,
I.
Guess
it's
computer
science
of
college
right
then
learning
how
the
next
work
would
be.
The
thing
you
would
do
so
I
ended
up
doing
that.
F
Writing
some
really
crappy
bug
reports
than
some
mildly,
better
bug
reports,
then
kind
of
helping
other
people
and
then
I
think
as
I
got
towards
the
end
of
college.
I
started
actually
kind
of
producing
open-source
myself
and
then
kind
of
starting
with
contributions
like
I.
You
know,
work,
there's
a
summer
internship
and
did
some
stuff
at
the
Linux
kernel
and
then
spent
a
few
years
working
on
the
KDE,
desktop
environment
and
then
started
working
on
homebrew
back
in
2009.
I
think
it
was
and
then
that's
my
kind
of
main
thing
nowadays.
C
C
So
I
find
this
is
really
funny
story,
because
when
I
decided
to
do
it
was
not
like
I
decided
kind
of
they
decided
for
me,
I
was
using
a
project
and
I
found
the
little.
It
was
not
a
book.
It
was
some
misleading
messages,
every
message
and
it
seemed
something
like
very
easy
to
fix.
But
I
just
went
to
IRC
and
say:
hey
there's
this
problem
here
and
I
didn't
expect
that
they
said
well.
C
C
Say
that
don't
be
afraid,
because
people
people
who
are
running
open
source
projects,
they
really
need
contributions,
and
they
are
really
helped
happy
to
help.
If
you
just
need
to
ask
so
good
communication
is
very
important,
and
if
you,
if
you
don't
really
know
exactly
how
the
process
of
creating
a
pull
request
or
creating
a
fork
or
a
base,
you
can
ask
and
and
I'm
sure
that
we
will
have
happy
to
help
you
with
that
as
well.
E
There
was
a
just
basically
in
the
beginning:
I
took
everything
personal
so
like
if
I
my
Paul
request
got
like
denied
I
was
like
what's
wrong
with
me.
You
know
and
I
think
that's.
The
major
thing
is,
as
I've
been
doing
this
longer
and
longer,
and
managing
my
or
maintaining
my
own,
sometimes
a
pull
request.
Doesn't
you
know,
match
your
a
line
with
your
vision
and
you're,
just
like
a
like
awesome,
but
thanks
I
can't
do
it.
So
it's
not
a
personal
thing.
It's
just
a
hey,
I,
gotta
I
can't
acquire
technical
debt.
E
Email,
if
you
email
the
maintainer,
if
you're
scared
about
something
and
if
it's
relevant,
they'll
email
you
back
very
quickly
because
they
want
to
grow
their
open
source
projects
and
by
emailing
them
and
then
asking
the
question
that
you're
afraid
to
ask.
It
means
that
you're
not
going
to
not
commit
to
it,
so
they
have
a
sort
of
like
a
one
of
the
word
I'm
looking
for
it's
in
their
best
interest
to
email,
you
back
and
say
hey.
This
is
what
you
need
to
do
so.
E
F
The
best
thing
you
can
do
I
think
is
right,
loads
and
loads
of
docs
and
as
the
user,
the
best
thing
you
can
do
is
try
and
like
read
as
much
as
you
can
and
as
has
already
been
said,
like
don't
worry
about
making
mistakes,
you
know
most
open-source
maintainer
is
get
that,
like
you
know,
keep
loading
you
to
this.
People
haven't
used
this
project
before
they
may
not
have
ever
used
gear
hug
before
this
project
or
whatever.
F
So
don't
worry
about
that
and
then
the
flip
side
of
it
is
you
know
whatever
you
do
do
whenever
you
can
do,
will
be
really
valued
because
most
of
open
source
is
done
by.
You
know
people
in
their
spare
time
and
things
like
that
and
white
little
one-off
contributions
by
the
spare
time
or
some
part
of
their
work
that
they're
not
obligated
to
do
so.
If
you're
able
to
kind
of
take
any
time
to
do
that,
you
will
find
that
most
people
will
be
super.
Grateful
yeah.
A
So
one
of
the
things
one
things
I
love
about
software
development
and
open
source
in
particular-
is
people
from
all
kinds
of
backgrounds
are
using
it
to
solve
different
problems
like
we
all
come
at
it
for
different
reasons.
It
might
be,
for
you
know
linux
or,
for
you
know,
I
had
some
some
side
project
that
I
was
interested
in
I'm,
like
Judy
I'm,
really
curious
to
hear
how
coming
at
it
from
your
perspective,
like
what
was
it
like?
B
I
think
I
think
for
me,
I
was
very
lucky
because,
when
I
started
out
with
medical
school,
that's
when
Kenya
was
really
struggling
with
the
HIV
pandemic
and
I.
Remember
when
we,
when
we
used
to
when
we
started
going
to
the
clinical
words,
would
have
a
split
I
think
we
had
nicknamed
it
Bosnia,
which
is
like
really
bad.
B
B
That's
outside
your
time,
so
you
have
to
out
introduced
myself
and
you
feel
you
know,
try
something
you
know
someone
may
reach
out
to
you
and
you
know
once
if
you
feel
like
this
could
be
a
fee,
then
you
know
you
look
at
their
mantra
and
you
know
figure
out.
Does
that
you
know
rhyme
with
you
as
a
person,
because
that's
how
we
work
on
open
source
they're
very
few
people
walk
on
open
source
as
part
of
their
jobs.
B
A
Other
son,
a
lot
of
actually
really
good
points.
I
want
to
come
back
to
the
the
job
one
in
a
little
bit,
but
before
that
you're
talking
about
you
know
getting
in
to
open
our
mrs
as
a
passion,
I
think
one
of
the
challenges
I
hear
people
talk
about
the
most.
Is
they
don't
know
where
to
get
started
or,
like
you
know
how
to
find
a
project?
He
talked
about
like
what?
What
does
that
process
been
like
for
you
or
what
was
it
like
when
you
first
got
started?
F
Yeah
I
guess
for
me:
it's
always
been
a
project
that
I'm
interested
in
or
ideally
I'm
interested
in
and
amusing,
and
it's
not
perfect.
So
there's
something
around
the
edge
that
I
feel
like
I
can
jump
in
and
help
with
and
I
see
people
kind
of
bouncing
off
open-source,
sometimes
because
they
kind
of
come
in
with
an
attitude
of
okay,
I
want
to
contribute
open
source
and
then
they
try
and
find
a
random
project
and
it
feels
more
like
home
work
for
them
because
they're
not
doing
something
they're
interested
in.
F
So
I
guess
I
would
say
you
know
if
you
work
as
a
software
developer
or
if
you
don't.
If
you're
you
know
someone
who
owns
a
computer,
you
probably
use
some
piece
of
open
source
software
and
there's
probably
something
about
one
of
the
pieces
of
them's
or
software
you
use,
which
is
irritating
so
like
going
and
trying
to
to
fix
those
things.
F
This
is
the
problem
I'm
having,
and
why
can
someone
kind
of
help
me
with
this
I
think
that
kind
of
pathway
and,
from
my
perspective,
it's
the
best
way
to
sort
of
get
in
rather
than
trying
to
feel
like
you
know,
it's
your
moral
duty
to
you
know:
contributor,
open
source
because
I
don't
think
it
I,
don't
think
anyone
is
obligated
to
but
I
think
it's
good
to
do.
If
you
can
find
something,
that's
actually
fun
and
interesting,
and
if
it
stops
being
fun
and
interesting
than
find
something
else
to
work
on.
A
Erica,
you
gave
a
talk
called
the
art
of
programming,
which
is
fantastic,
highly
recommend
checking
it
out,
but
in
there
you
talk
about
the
role
of
was
a
curiosity
and
passion
in
driving
interest
in
programming.
Can
you
talk
like
what
does
that?
Look
like
around
open
source
as
well?
Is
that
same
same
message
apply
yeah.
C
I
really
believe
that,
then
it
has
to
do
with
like
choosing
the
right
projects
for
contributing
to.
If
you
there.
I
think
that
choosing
a
project
has
two
different
approaches.
You
can
choose
a
project
that
you
are
really
interested
to,
or
you
can
try
to
find
a
project
that
is
super
friendly.
Maybe
it
will
make
you
more
comfortable.
It's
a
good
approach
for
a
first
contribution,
but
contributing
to
a
project
that
you
are
really
passionate
about
is
different
because
you,
you
know
what
you
are
dealing
with.
C
You
know
better,
you
know,
so
you
know
things
that
you
can
make
better.
You
can
improve
and
then
curiosity
is
important
for
that,
because
you
are
not
just
a
sitting
and
complaining
about
something
that
you
found
and
then
it's
wrong.
It
seems
wrong
or
you
would
like
that
it
would
be
better.
Some
people
would
just
sit
around
and
complain
on
to
read
it
about
it,
but
you
can.
C
If
it's
an
open
source
project,
you
can
always
go
there
and
make
a
contribution,
and
if
you
are
curious
enough
to
see
what
is
wrong
and
then
you
find
the
problem
and
you
think
about
a
way
to
solve
that
that
with
a
little
bit
of
creativity
and
then
you
will
be
able
to
contribute
and
make
a
difference
for
that
project.
So
it's
beneficial
for
everybody,
for
the
project
and
for
you,
because
you
have
a
better
project.
A
better
library
or
the
application
that
you
will
be
working
on
so
totally
makes
sense
right,
good.
B
B
You
know
even
organizations,
you
don't
have
to
always
steal
time
from
you
know
your
personal
life.
You
know
you
can
also
create
this.
You
know
situations
and
I
hope
that
we'll
see
where
companies
come
up
with
some
butter
cause.
You
know
like
in
academia
where
people
are
free
to
explore
projects
and
figure
out.
You
know
what
they
like,
because
I
think
that's
really
important.
You
know
as
as
life
you
know
just
having
you
know,
this
is
from
being
a
doctor.
B
As
life
comes
on,
and
you
say
you
don't
want
to
wait
for
the
day
that
doctor
says
you
have
cancer
and
you
can
walk.
You
know
you,
as
you
grow,
that
you
start
to
appreciate
like
meaningful
work.
You
know,
and
so
these
opportunities,
where
you
can
also
gain
personal
satisfaction
and
it's
good
for
the
company,
because
you
mourn
get
your
new
buck
at
wow.
That's.
A
Awesome
so
I
want
to
start
with,
like
our
own
experiences,
getting
started,
an
open
source
because
I
think
as
we
as
we
start
to
think
about
maintaining
projects.
Remembering
what
it's
like
to
be
new
is
really
important.
Can
you
talk
a
little
bit
about
how,
in
each
of
your
projects
that
you
worked
on
like?
How
do
you
make
the
project's
welcoming
to
new
people
or
how
do
you?
How
do
you
encourage
contributions.
F
Yes,
sir,
on
homebrew
we're
a
better
sneaky
about
it
and
hopefully,
if
any
of
you
use
or
contribute
to
Humber
and
future,
you
need
to
forget
everything.
I've
told
you
now
because
so
a
little
secret,
so
we
just
generally
try
and
like
upsell
people
every
stage.
So
if
there's
someone
who
complains
about
something
on
Twitter,
we
say
like
hey:
why
don't
you
create
an
issue
and
if
they
create
an
issue,
then
we
try
and
like
get
more
and
more
information
out
them.
F
So
it
turns
from
being
just
an
issue
to
being
a
good
one,
and
then
we
might
say
oh
hey
like.
Could
you
try
and
make
a
pull
request
for
this?
Like
here's,
all
the
kind
of
docs
we've
written
for
doing
this
will
help
you
do
so
and
stuff
like
that,
and
then
we're
try
and
get
them
to
do
that
a
few
times
and
then
after
they've
done
a
few
pull
requests,
then
it's
like
a
do
want
to
be
a
maintainer
and
then
y
que.
F
It's
obviously
like
it's
a
a
funnel
so
like,
for
you
know,
maybe
for
every
ten
or
a
hundred
people
up
one
of
those
layers
you
and
they
get
kind
of
a
couple
who
end
up
going
up
to
the
next
layer,
but
I
think
almost
taking
that
attitude
of
like
every
single
person
that
comes
on
to
your
project
is
a
potential
maintainer
and
future,
because
the
one
in
my
experience,
an
Everett
ability
of
open
source,
is
that
people
will
work
for
a
while.
They
will
get
bored
and
then
they'll
go
away.
F
E
Will
say,
like
we
I
work
on
a
project
called
Schimmel
and
we
submitted
a
ticket
to
get
it
into
row
and
I
was
very
surprised
of
how
quick
and
detailed
your
responses
were,
but
when,
when
it
Nick,
we
got
unit
test
was
breaking
and
it
was
like
it
wasn't
like
figure
it
out.
It
was
just
like
hey.
This
is
what
I
think's
going
on.
So
if
what
should
have
probably
taken
two
weeks
of
us
going
back
and
forth
and
picking
it
out,
you
know
your
team
has
definitely
just
stepped
up
to
the
plate.
A
B
Think
one
thing
for
openmrs:
we
have
talked
openmrs
dog
and
you
go
there
and
the
first
thing
you
should
do
a
big
it's
removed
from
google
groups
to
more
social
media
platform.
Sort
of
you
know
what
you
can
see
proposed
and
you
can
subscribe
to
post
and
the
first
thing
we
want
you
to
do
is
introduce
yourself
and
we
have
lots
of
people
who
introduced
themselves
every
single
day
and
open
a
marathon
has
one
pass
on
a
community
manager.
That's
it.
B
We
don't
hire
anyone
else
and
he's
in
charge
of
infrastructure,
but
occasionally,
like
I,
will
troll
around
who
came
into
the
new
community
and
other
people.
Do
that
and
write
you
a
quick
message
and
say
welcome.
Then
we
divided
our
intro
tickets.
So
we
have
like
really
basic
things
like
maybe
changing
a
message:
door
properties
file.
B
You
know
which
should
be
like
easy
to
do
and
you
know
possible
to
do
and
then
we
also
have
sometimes
you
have
Sprint's
running
and
in
the
past
what
would
have
is
would
have
a
senior
developer
much
to
a
junior
developer
to
help
you
like
do
team
coding
to
get
started
and
I
mean
that's
expensive,
because
you
know
if
you're
just
there
for
a
week,
then
that's
time
we
said
you
know,
but
we
still
sort
of
did
that.
Then
we
had
openmrs
university.
B
So
if
you're
having
trouble
figuring
out,
oh
you
know
a
specific
because
there's
a
lot
of
domain
knowledge.
First
of
all,
if
you're
ranked
you
know
trying
to
contribute
to
a
project,
you
know
you
can
come
in
and
say:
hey
I
would
like
to
hear
about
maybe
form
creation
or
something
else,
and
someone
can
schedule
like
I
university
forum
and
just
talk
about
you
know
you're
doing
some
live
coding
during
that
time.
B
So
so,
if
you
can
introduce
yourself
pick
an
intro
ticket
and
they
will
feel
they
were
labeled
but
and
then,
if
you
need
help
either
watch
previous
recordings
for
the
university
or
ask
for
a
new
topic
for
university.
If
you
find
the
sprint
running,
that's
the
best,
because
we
do
a
morning
scrum
every
day
and
you
can
see
what
your
blocker
is
and
people
sort
of
help
you
out
from
there
I
think
you
you
can
stay
with
openmrs
community
easily.
B
C
That's
the
one
of
the
most
important
things:
if
you
want
to
have
more
contributors
is
have
a
really
good
documentation,
and
some
kinetic
cannot
underestimate
and
something
that
I
found
musical
for
web
projects
is
also
having
like
a
vagrant
set
up.
So
people
can
easily
spin
out
a
victory
machine
because
not
everybody.
C
We
have
vironment
ready
for
running
in
the
project
and
if
you
the
easiest
thing
that
the
easiest
that
you
can
make
for
people
to
to
get
your
project
up
and
running
it's
the
better,
so
they
will
be
more,
it
would
be
quicker
for
them
and
they
don't
have
to
install
a
lot
of
stuff
and
get
machines
and
then
also
like
make
it
clear
that
you
are
welcoming
all
tops
all
types
of
document
contributions
like
documentation
or
a
small
contributions
that
it's.
This
is
also
important.
A
A
So
had
this
little
bit
of
commentary,
I
promised
you
guys:
I
wasn't
going
to
give
commentary,
but
I
I
want
to
point
out.
Openmrs
is
an
example
of
this.
The
first
time
I
came
across
the
project,
I
was
actually
blown
away
with
like
how
polished
and
professional
it
was,
and
I
thought
that
there
was
like
a
company
behind
it
and
I
thought
that
you
know
I
thought
you
got
paid
to
work
on
it.
Are
you
saying
you
don't
the
only
person
employed?
This
is
Michael
tianity
manager.
B
B
We've
been
we've
been
very,
very
lucky,
I
mean
we,
we've
had
a
brand,
that's
spread,
you
know
by
word
of
mouth
and
so
we're
used
in
multiple
countries.
The
countries
that
have
come
up
and
said
we
want
to
use
openmrs
or
national
Liam.
Are
you
know,
places
like
Kenya
Tanzania,
you
know,
then.
We've
had
I
mean
I,
think
anyone
who
SAT
is
for
like
open
source
medical
record
system
sort
of
is
drawn,
draw
community
and
some
go
away
and
some
say,
and
so
we
have
individual
contributors.
B
We
have
companies
like
thought
walks
who
have
come
and
say
as
part
of
our
social
default.
You
know
program
we're
going
to
give
you
40
developers
to
build
openmrs
and
you're
going
to
give
this
back
to
you
for
free
and
anyone
in
the
world
can
use
it,
and
so
that's
a
big
commitment
like
full-time
developers.
B
You
know
who
come
in
and
scram
and
build
this
tool,
and
so
we
have
local
country
initiatives
like
in
Mozambique
because
they
have
to
build
their
stuff
in
Portuguese,
and
you
know
that
still
comes
back
to
the
main
community
for
you.
So
we
had
a
very
sort
of
various
type
of
implementers
and
community
members,
but
one
of
the
things
I
think
in
terms
of
governance.
You
know
we
have
some
like
a
leadership
cancer,
but
the
community
voice.
B
We
may
not
always
listen
to
everyone
just
because
you
know
in
two
conflicting
places,
it's
easier
to
do
one
thing
than
another,
and
so
our
model
what's
what's
helped
us
is
we
build
a
platform
and
other
users
can
come
and
build
in
products
on
top
of
it,
and
so
we
can
have
a
very
diverse
sort
of
community
from
that
yeah.
But
when
using
like
42
countries
now
so
that's
awesome,
yeah
I,
so.
G
D
So
I
have
a
question
about
community.
A
lot
of
open
source
communities
have
got
a
reputation
for
not
being
very
friendly
environments
in
terms
of
two
to
outsiders.
So
what
could
an
open
source
project
due
to
want
to
encourage
people
to
join
them
and
what
kind
of
social
tools
do
you
use?
Is
it
mailing
lists?
Is
it
IRC?
What
are
the
best
ways
to
be
open
and
be
friendly
with
the
communities.
B
So
what
I
call
the
social
media
based
on
discuss,
and
so
you
can
create,
you
know
subtopics,
and
you
can
tag
and
subscribe
to
specific
ones
that
you
like.
We
do
have
an
IRC
channel
and
we
really
discourage
other
forms:
private
forms
of
communication
unless
absolutely
necessary.
You
know
like
if
it's
a
personal
thing,
but
this
we
initially
we
use
google
groups
and
we
just
migrated
from
that
and
we
I
know
we
lost
a
few
number
of
people,
but
it's
worked
out.
Well
other
people
able
to
come
in
and
just
crawl.
B
A
F
In
her
breeze
case,
and
as
you
kind
of
touched
on
safe
spaces,
I
think
like
for
us
it's
kind
of
interesting,
because
we,
because
the
majority
of
our
users
are
developers
as
well.
We
have
more
of
our
discussion.
Probably
the
bulk
of
our
community
is
on
gal
bit
cell
in
issue,
simple
requests
and
the
big
thing
we
had
the
big
things
we
found
have
really
helped.
I
think
one
has
been.
We
have
like
a
code
of
conduct
like
quite
a
long
time
ago.
F
You
know
there's
now
tools,
so
you
can
delete
comments
and
block
users
and
stuff
like
that,
and
that's
not
necessary
very
often,
thankfully,
but
it's
really
good
to
do
that
and
it
does
seem
to
signal
to
people
and
I've
had
a
few
private
emails,
sometimes
where
someone's
been
very
rude
to
them
and
then
one
of
the
maintenance
of
mutually
jumped
in
and
said.
No
actually,
that's,
not.
Okay.
You
need
to
read
our
code
of
conducts.
F
F
Actually,
when
I
got
this
rude
message,
I
was
going
to
not
work
in
this
project
anymore,
but
then,
like
now
that
I
had
no
that
kind
of
much
the
bulk
of
the
project
the
maintainer
has
have
my
back,
like
I,
now
feel
able
to
continue
working
on
this
project.
So
for
me
a
big
part
of
it.
Is
it
being
a
safe
space,
because
if
people
are
doing
this
in
their
free
time
or
you
know
part
of
their
job
or
whatever
you
know,
no
one
wants
people
to
be
rude.
E
It
really
sucks
because
there's
so
many
really
talented
female
developers
that
get
harassed
and
I'm.
Really
it's
unacceptable
and
I
really
do
think.
We
all
need
to
kind
of
watch
out
for
each
other,
because
you
know
if
someone
wants
to
contribute
to
open
source
and
do
amazing
work
and
then
get
death
threats.
Irc
like
I,
know,
there's
nothing
like
you
can
really
intercept
there,
but
it's
just
it.
No
one
wins
and
I
really
do
think.
I
really
do
hope.
E
More
people
hold
those
who
are
a
holes
accountable
because
you
know
if
we
all
just
turn
away,
then
nothing's
ever
going
to
get
done.
So
you
know,
I
was
looking
forward
to
meeting
Jesse
and
she
couldn't
be
here
today
and
you
know
I'm
just
why
you
know,
because
because
we
just
looked
the
other
way,
so
I
really
hope
everyone
with
whether
you're
male
or
female,
someone's
doing
something
that
is
destructive
to
the
community.
This
is
a
great
community
like
call
them
out.
Don't
don't
let
this
happen
anymore,
I'm
sick
of
it.
I.
F
You
probably
know
who
some
of
these
people
are
and
I
think
you
know
it's
are.
Frankly,
everyone
involved
an
open
source,
it's
our
job
to
make
sure
that
we
work
in
a
way
that
is
appropriate
and
work
in
a
way
that
is
like
diplomatic
and
friendly.
And
if
you
cannot
do
that
and
I
cannot
do
that
sometimes
as
well.
F
We
should
feel
able
to
call
anyone
out
on
that
and
say,
like
look,
there's
no
need
to
be
mean,
there's
no
need
to
be
rude
and
I
hope
that
everyone
in
this
room
feels
that
when
they
leave
here
today,
they
feel
able
to
call
other
people
out
such
as
myself,
regardless
of
where
they
are
and
make
this
a
more
welcoming
space
for
people
to
get
involved
with,
because,
ultimately,
that's
the
only
way
open
source
projects
are
going
to
continue
to
grow.
This.
A
Is
such
an
important
topic
that
I
wish
we
could
spend
a
ton
more
time
on
we've
actually
blown
through
our
our
time
so
far.
So
if
you
want
to
talk
to
any
of
these
folks
will
stand
be
standing
right
out
here.
Please
come
up
these.
These
four
have
incredible
experiences
and
I'm
sure
we
would
be
happy
to
answer
any
questions
or
talk
more
about
some
of
these
issues.
So
thank
you
very
much
for
coming.
Thank
you
all
for
participating.