►
From YouTube: There and back again: Through the realms of open source software - GitHub Satellite 2019
Description
Presented by Devon Zuegel, Product Manager of the Open Source Economy team
Join Devon in exploring the distant lands of open source. She's brought us back customs from programming communities far and wide, to borrow and remix to solve problems back at home, wherever that may be.
Through hundreds of conversations with open source maintainers, Devon discovered that each niche of the developer ecosystem has come up with ingenious techniques and thoughtful methods of coordinating work, investment, and decision-making.
About GitHub Satellite 2019
A community connected by code
Explore our interconnected community—and how collaboration turns ideas into innovations.
Join us in November at San Francisco's Palace of Fine Arts for GitHub Universe - https://githubuniverse.com/
A
A
A
But
they
haven't
necessarily
talks
to
each
other
very
much.
The
java
programmers
don't
really
talk
to
the
JavaScript
programmers,
the
haskell
programmers
don't
really
talk
too
much
to
the
objective-c
people
and
it's
it's
pretty
interesting
to
see
all
of
the
different
tricks
and
different
different
different
strategies
that
they've
taken
up
and
I
think
that
it's
really
useful
to
be
able
to
share
those.
A
So
in
the
last,
in
the
months
before
we
started
building
github
sponsors,
I
interviewed
hundreds
of
developers
and
was
really
inspired
by
a
lot
of
the
approaches
they
were
taking.
This
is
actually
one
my
favorite
parts
of
the
job,
I
love
talking
to
people
about
things
that
passionate
about
and
really
understanding
what
makes
their
projects,
tick
and
I
get
to
compare
the
the
notes
of
the
challenges
and
techniques
and
different
systems
that
people
have
put
in
place.
A
A
A
I,
guess
that
so
yeah
here.
Here's
an
example
of
adding
the
comments
with
pull
requests
and
here's
the
emoji
key
of
all
of
the
different
things
that
you
can
add.
People
for
and
I
assume
they're
accepting
pull
requests.
If
you
see
anything
missing
on
this
list,
I
seen
this
take
root
the
most
in
NPM
communities
like
node
communities,
specifically
within
the
react
world,
but
I
think
that
this
is
something
that
open-source
projects
of
all
types
can
benefit
from
and
something
I've
heard
repeatedly
from
a
lot
of
maintainer
x'.
A
Is
that
as
a
project
scale
in
particular,
the
work
actually
changes
from
being
something?
That's
about
writing
code
every
day
to
a
lot
of
the
management
and
motivating
people
and
understanding
sort
of
the
long-term
strategy
is
talking
to
corporate
users
talking
to
beginner
developers
who
have
never,
you
know
used
open
source
before
who
don't
really
know
what
forking
is
like.
A
But
not
the
only
thing,
another
place
that
I've
personally
drawn
a
lot
of
inspiration
that
is
influencing
how
we're
thinking
about
github
sponsors
and
the
other
tools
that
we're
building
for
maintainer
x'.
Is
this
open
source
company
called
Raza
they're
they're?
What's
called
open
core,
so
they
have
this,
the
the
core
of
open
source
software-
that
is,
you
can
open
pull
requests
on.
You
can
see
all
the
code
and
then
they
offer
services
on
top
of
that.
A
I
actually
think
some
of
them
might
be
in
the
audience
today,
because
they're
based
in
Berlin
and
I,
invited
them
so
welcome
to
craft
work,
something
that
they've
done.
That
I
think
is
really
really
cool
is
that
they
have
something
called
a
contributor
sheet
and
they
made
a
copy
for
me
with
and
I
filled
it
with
fake
data.
So
don't
go
emailing
any
of
the
people
in
here,
because
they're
not
real,
but
they
have
this
contributor
sheet
for
keeping
track
of
all
the
different
people
who
participate
in
their
open
source
projects.
Again.
A
This
is
sort
of
tied
in
with
the
first
concept
saying
there's
all
of
these
contributions
that
don't
necessarily
get
tracked
directly
and
get
her
now,
and
yet
we
really
want
to
make
sure
that
they're,
respected
and
included
as
part
of
the
project
and
and
thanked
for
their
wonderful
contributions.
So
they
have.
A
This
looks
basically
a
CRM
inside
of
Google
sheets,
where
they
may
keep
track
of
all
of
these
people
and
make
sure
that
you
know
if
they
haven't
been
reached
out
to
for
a
while
or
they
haven't
made
a
contribution
in
a
while
that
they
aren't
stuck
on
something
or
that
if
someone
has
been
really
active,
adding
documentation
that
they
get
recognition
for
that.
I
think
this
as
soon
as
they
showed
this
to
me,
I
got
coffee
with
one
of
the
co-founders
and
he
pulled
it
up
and
I
was
like
wow.
That
is
awesome.
A
Complaining
is
maybe
not
the
right
word
concerned
about
the
the
state
of
certain
projects
that
were
really
crucial,
but
were
maybe
not
so
much
fun
to
maintain
or
just
took
a
lot
of
work
or
the
person
who
had
been
maintaining
it
had
to
take
some
time
off,
and
you
know
at
the
end
of
the
day,
if
you
could
be
making
a
full-time
salary,
doing
something
it's
really
hard
to
justify
cheer
for
your
friends
and
family.
Why
are
just
doing
all
this
on
volunteer
work?
So
what
Daniel
decided
to
do
was
he
said?
A
Okay,
we
all
have
these
shared
means.
We
would
all
benefit
if
we
were
able
to
come
together
and
fund
these
developers
to
work
on
this
this
product,
these
projects
and
but
he
said
also,
you
know,
I
I,
don't
know
everything
I'm,
not
a
missions
when
it
comes
to
the
closure
community.
So
what
he
does
is
each
quarter.
A
I
think
this
is
a
really
cool
model
because
it
brings
the
best
of
the
community
together,
and
it
says
it
takes
this
holistic
view
over
the
entire
set
of
options
that
could
be
funded
and
says
you
know
we're
going
to
decide
on
this
and
and
cooperate
together
and
collaborate
together
on
making
sure
that
our
key
infrastructure
is
funded,
so
I.
Think
closures
together
is
an
awesome
model.
A
There's
there's
also
Ruby
together,
which
I
think
was
part
of
the
inspiration
for
this,
though
they're
slightly
different
models
and
I,
and
there
are
some
other
programming
communities
that
are
starting
to
do
these
things
too.
But
I
think
it
would
be
great
if
every
programming,
community,
large
and
small
had
something
like
closures
together
and
I.
Think
it
doesn't
have
to
be
related
to
the
programming.
Language
is
necessarily,
you
could
say,
all
front-end
frameworks
we
want
to.
We,
we
all
have
similar
goals.
A
We
want
to
build
front-end
software,
how
about
we
all
come
together
and
make
sure
that
we
all
have
the
tools
that
we
need.
Similarly,
maybe
you
want
to
increase
the
diversity
and
open
source
I,
think
you
could
have
groups
of
people
coming
together
and
funding
those
goals
all
together
as
well,
so
I
thought
this
model
was
wonderful
and
I
am
really
excited
to
see
more
people
experimenting
with
things
like
that.
A
And
yet,
if
one
person
gets
a
mean
comment
on
an
issue
that
could
tank
their
motivation
and
cause
them
to
not
want
to
spend
time
on
it
anymore
and
totally
fairly,
these
people
are
many
of
you
in
the
audience
are
donating
their
time,
volunteering,
and
so
it
all
it
takes,
is
just
a
little
negativity
to
potentially
reduce
motivation.
So
a
github.
A
Well,
one
of
the
things
we've
been
thinking
about
is
how
to
make
make
that
motivation
stay
more
positive
and
it's
a
pretty
simple
framework,
there's
sort
of
benefits
and
there's
costs
right
on
the
benefit
side.
You
get
to
build
awesome
software
with
people.
You
respect
solving
problems
that
you
find
interesting.
Some
people
get
paid
to
do
open-source.
A
Some
people
have
a
specific
problem.
They're
trying
to
solve
those
are
the
benefits
on
the
the
cost
side.
There
are
things
like
takes
a
lot
of
time
to
work
on
open
source,
sometimes
you're
stuck
triaging
issues
on
a
Friday
night
again,
I
mentioned
abusive
comments
are
serious
if
you
in
open
source-
and
you
know
on
the
Internet
in
general
and
so
I
github.
A
So,
for
instance,
today
we
announced
that
there's
a
new
permissioning
system
before
there
was
just
the
read/write
and
admin
and
we
added
a
little
bit
more
granularity
there
to
reduce
the
burdens
on
maintainer
x',
because
right
now,
up
till
today,
maintainer
x'
were
sort
of
stuck
saying,
making
the
choice
between
whether
to
trust
someone
a
lot
or
to
completely
exclude
them
from
a
project.
And
those
are
two
extremes.
You
don't
necessarily
want
to
give
someone
full
commit
access.
A
But
you
also
don't
want
to
say
now.
You
can't
contribute
unless
you,
unless
I,
fully
trust
you
there's
there's
now
ability
for
a
middle
ground
for
triage
errs,
who
can
assign
issues
they
can
add,
they
can
add
labels
to
issues
and
take
off
some
of
the
burden
of
the
maintainer
x'
without
having
to
create
more
concerns
with
the
maintainer
x'
because
they
have
such
access.
A
Similarly,
that
the
new
maintain
role
makes
it
possible
for
the
the
admins
of
a
project
to
bring
on
more
people
to
take
on
key
administrative
functions
without
necessarily
like
giving
them
a
full
king
keys
to
the
kingdom.
So
that's
something
I'm
very
excited
about
on
the
the
cost
side
that
we're
gonna
reduce
some
of
the
costs
on
open-source
developers
and
then,
of
course,
there's
good
of
sponsors,
which
is
the
first
step
in
increasing
the
benefits
for
maintainer
x'
as
well.
A
I
think
this
is
something
I'm
personally
clearly
extremely
excited
about,
because
this
is
something
that's
going
to
unlock
the
potential
of
a
lot
more
people
to
contribute,
full-time
or
part-time
or
just
a
little
bit
of
extra
time
to
open
source
right
now.
Open
source
is
mostly
limited
to
people
who
can
do,
spend
a
lot
of
free
time
contributing,
and
that
is
absolutely
wonderful
and
those
people
are
a
core
part
of
the
open
source
community.
But
there
are
a
lot
of
people
who
would
like
to
work
on
open
source
more
who?
A
Who
can't
really
do
that
right
now?
So
I'm
really
excited
to
see
how
people
use
github
sponsors,
as
I
mentioned
in
the
keynote
we're
really
looking
for
feedback
and
a
lot
of
the
research,
including
some
of
the
stuff
I,
should
today,
is
what
we're
taking
into
account
as
we
build
out
the
future
of
the
products
too.
So
if
any
of
that
stuff,
particularly
resonated
with
you,
please
let
me
know,
I
would
love
to
hear
it.
B
I'm
Jenny
sarin
I'm,
a
developer
advocate
I'm,
Microsoft
and
I
came
here
because
there's
a
massive
collection
of
JavaScript
people
coming
in
the
next
few
weeks
to
various
events,
and
this
was
very
timely
to
kind
of
understand,
more
of
what's
shipping
and
the
nice
things
that
are
happening,
github
and
also
kind
of
engaging
with
the
JavaScript
community.
So
one
of
the
things
you
know
in
JavaScript
there
is
a
lot
of
code
right.
A
lot
of
modules,
I
think
we're
about
to
hit
a
million
packages
in
NPM.
B
C
Hi,
my
name
is
Dominic
Terra
I
work
on
a
project
called
Co,
scuttlebutt
and
I
got
invited
to
attend
this
conference
because
of
my
part
in
a
recent
drama,
where
I
gave
away
a
little
module
called
event
stream
that
some
of
you
obviously
remember
anyway.
I
noticed
on
your
first
slide
that
you're
from
the
economy
account
open,
source
economy
and
I.
Just
have
a
question
that
I've
been
wondering
how
many
anthropologists
does
get
github
heifer
on
the
payroll.
That.
A
Is
a
great
question
so
I
think
I
don't
know
if
we
have
anyone
with
the
title
anthropologist,
but
in
school,
I
studied
computer
science
is
my
main
degree,
but
I
also
studied
urban
planning,
anthropology
and
economics
and
I
kind
of
nerd
out
on
that
stuff.
In
my
free
time
and
honestly,
I
think
that
was
sort
of
the
key
framing
that
I
brought
into
my
research.
A
Someone
who
I
think
is
here
today
is
also
Nadia,
eggball
she's,
a
good
friend
of
mine
and
someone
who
was
inspired
me
a
lot
and
she
I've
always
really
appreciated
her
her
perspective
on
these
things.
So
to
answer
your
question
directly,
I,
don't
know
if
there's
any
work
specifically
hired
as
anthropologists
but
I.
A
Think
github
is
a
very
human
human
company
and
really
focused
on
the
people
and
even
increasingly
so
we're
very
much
focused
on
the
social
dynamics
and
making
sure
that
these
communities
are
strong,
as
opposed
to
just
focusing
on
the
code
artifacts,
because
it
really
is
all
about
how
people
relate
to
each
other.
Open
source
is
a
process.
Open
source
is
not
just
the
code.
Yes,.
A
C
A
D
D
Put
it
up,
say:
hey
I
made
these
cool
thing,
regardless,
if
I'm
famous
on
Twitter
or
not
and
like
I,
have
a
lot
of
likes
and
retweets
or
not,
people
will
use
it
because
that's
a
lot,
a
huge
demotivator
when
you
spend
like
weeks
on
something
you
put
it
up,
unless
a
famous
guy
retweets
it
nobody
will
see
it
thanks.
That's.
A
A
One
of
the
things
I'm
really
proud
of
about
github
sponsors
is
it's
integrated,
very
natively
into
the
workflow,
and
so,
as
you
pointed
out
right
now
that
you
weren't
talking
about
the
funding
side
so
much,
but
in
the
context
of
funding
I
think
something
you
see
is
that
there
are
some
people
who
are
very
successful,
receiving
money
and
that's
wonderful
and
they're
extremely
great
developers.
But
some
people
don't
want
to
have
a
really
active
Twitter
account.
Some
people
don't
really
want
to
promote
themselves
at
all.
A
They
just
want
to
write
code
or
they
just
want
to.
You
know,
work
on
their
project
and
not
really
do
any
of
that
stuff.
That's
great
too,
and
some
of
the
best
developers
I
know
are
like
that,
and
so
by
putting
it
inside
of
the
workflow.
My
my
hope
and
expectation
is
that
it'll
it'll
sort
of
bring
those
people
up
like
right
now.
A
It
open-source
looks
like
a
little
bit
of
a
power-law
where
there
are
a
few
people
who
are
just
kicking
butt
and
that's
great,
but
there
are
a
bunch
of
other
people
who
are
making
awesome
contributions
to
who
don't
necessarily
get
the
visibility
that
they
deserve.
I
think
that
with
github
sponsors
being
integrated
and
people's
workflows,
it'll
sort
of
flatten
the
curve
out
a
little
bit.
It'll,
never
be
you
know
perfectly
perfectly,
even
but
I
think
it
will.
It
will
bring
those
people
up
and
surface
those
awesome
developers.
A
E
Markers
here
from
the
Python
PI
data
community,
working
mainly
in
pandas,
my
question
is
regarding
the
how
to
the
users
or
the
users
of
it.
Commentators
in
this
case,
interact
with
it
like
for
pandas,
for
example,
when
our
users
suffer
requires,
have
a
bag
or
something
they
just
feel
like
it.
Capiche,
oh
and
it
copies
making
over
life
very
easy
and
managing
those
interactions.
But
when
we
have
requests
for
github
my
case
I
was
extremely
interested
on
like
assigning
issues
to
to
anyone.
Her
betrayal
contributors,
not
only
maintainer,
that
it's
something
I
doesn't
provide.
E
I
was
trying
to
to
communicate
that
with
it
cup,
I
could
contact
support
and
that
I
saw
some
tickets
in
unrelated
repositories
on
github,
where
people
were
reacting
with
emojis.
Like
hundreds
of
emoji
reactions,
people
were
really
interested
on
on
those
features,
though,
but
I
couldn't
see
like
how
we
can
interact
Annika
in
in
more
like
useful
way
than
just
sending
an
email
to
support.
Yeah.
A
Totally
again,
two
answers
so
number
one
email
me,
my
email
is
Devin
Zhuge,
like
github.com
spelled
very
weirdly.
Well,
oh
man,
I
guess
I
have
to
spell
it
now.
De
vo
n
is
a
UE
GTL.
It
get
them
to
come.
You
can
just
take
my
name,
it's
all
over
the
place,
it's
that
so
we
want
to
hear
from
you.
The
other
piece
is
for
open-source
maintainer
zwi.
A
There's
a
community
called
the
maintainer
z--,
it's
a
an
organization
in
github
where
people
can
open
issues
and
have
conversations,
and
one
purpose
of
it
is
to
give
github
feedback
and
to
tell
us
about
that
stuff,
and
the
other
thing
is
to
bring
the
maintainer
together
to
share
stories
with
one
another
and
tips
and
tricks,
and
things
like
that,
so
you
might
I'm
not
sure
if
you're
in
I
don't
think
you're
in
it.
Yet
I
haven't
seen
you
at
least
in
it,
we'd
love
to
include
you
in
that
and
anyone
else
again.
A
Email
me
for
for
that
I'll
send
more
pointers
and
I've
personally
found
the
group
really
motivating
to
also
to
follow
I,
it's
a
source
of
a
lot
of
inspiration.
Energy.
For
me,
there's
there's
a
few
conversations
in
that
a
week
usually,
and
there
have
been
a
bunch
of
times
where
I
get
kind
of
like
tired.
You
know
at
the
end
of
the
week
and
then
I
open
an
email
that
gives
me
the
notifications,
and
it
gives
me
a
lot
of
inspiration
to
keep
going
so
I
think
you'd
like
it
too,
and
that's
a
good
start.
F
You
mentioned
that
you
saw
these
patterns
and
I
wanted
to
ask
if
you
saw
these
patterns,
what
efforts
are
being
made
to
make
these
bathrooms
more
clear
to
the
people
that
are
involved?
You
mentioned
this
maintainer
community
I
heard
about
it
once
maybe
a
year
ago,
but
you
know
never
again,
and
now
you
mentioned
it
again.
How
do?
How
do
you
mean
tanners
actually
get
together
and
share
their
experiences
and
share
their
patterns
for
dealing
with
this
yeah.
A
A
There's
also
a
number
of
conferences
that
I've
been
to
that
I've
been
really
really
helpful,
I
like
to
be
sort
of
a
fly-on-the-wall
sort
of
more
following
along,
but
there's
there's
sustained
OSs,
which
is
something
that
open
collective
puts
on
that's
a
really
motivating
conference.
For
me,
that's
obviously
more
focused
on
the
funding
side,
but
also
other
things
talking
about
how
to
keep
open
source
sustainable
in
general,
not
just
about
money.
A
There's
also
a
conference
called
the
maintainer
z--
that
is
happening
in
October,
I,
believe
in
Washington
DC,
and
it
actually
brings
maintainer
of
all
sorts,
not
just
open
source
software.
There
were
people
who
maintained
like
sewage
plants
and
and
train
tracks,
and
things
like
that.
People
who
maintain
all
sorts
of
infrastructure,
including
digital
infrastructure
and
I'm,
really
looking
forward
to
that
one
as
I
mentioned,
actually
study
that,
like
anthropology
and
urban
planning
and
things
like
that
in
school.
So
it's
a
really
cool
mix
of
those
two
things
so
I
could
send
you
more.
A
Resources
to
I
could
probably
list
a
bunch
more
places,
but
also
would
love
to
hear
what
you
think,
but
what
you
would
want,
because
github
I
think
is
in
this
unique
position
where
we
serve
all
of
these
different
communities
and
the
we
can
sort
of
create
that
space
for
people
to
come
together
and
then
sort
of
hand
it
off.
So
if,
if
that's
something
you're
interested
in
I'd
love
to
hear
from
you,
thank
you.
Thank
you.
G
A
G
My
question,
which
sort
of
goes
back
to
what
was
mentioned
earlier
about
the
Anthropology
aspect,
is
that
it
seems
to
me
that
when
the
community
grows
most
of
the
issues
that
he
also
surfaced
are
like
around
basically
project
management
and
like
handling
people
and
I
was
wondering
if
it
get
up
you're,
considering
exploring
options
of
having
like
more
advanced
tools
for
like
that
CMS
kind
of
Google
table
like
that
kind
of
elements.
Yeah.
A
So
I
want
to
do
it.
I
can't
tell
you
exactly
that,
like
what
our
plans
are
cuz,
it's
something!
It's
not
just
my
decision
to
make,
but
I
think
it's
it's
a
really
cool
tool
and
we're
exploring
that
one
thing,
sort
of
that's
halfway
between
what
we're
good
have
sponsored
is
now
and
that
that
CRM
is
ability
to
be
able
to
manage
the
sponsors
a
little
bit
better.
So
I
know
that's
not
like
exactly
what
you're
asking
about,
but
making
it
so
that
you
can
stay
in
contact
with
the
community
and
so
on.
A
That's
probably
in
the
shorter
term
as
an
it'll
roll
out
over
the
course
of
this
summer,
but
yeah
I
think
like
github,
is
sort
of
the
watercooler
of
open
source
right.
It's
through
you
come
together
and
I
think
we
can
work
on
that
even
more.
It's!
It's
sort
of
naturally
become
that,
but
now
that
we
realize
that
that's
the
place
where
this
is
happening,
it's
on
us
to
build
the
tools
that
makes
that
actually
possible.
So
I
I'm
now
starting
to
sound
like
a
broken
record.
H
Hello,
I'm
Trustin,
streebek
I'm
from
startup
first,
because
I
was
also
part
of
a
good
of
the
open-source
community.
Thank
you
for
get
up
get
up
sponsors.
Thank
you
for
that.
It's
super
great
idea
because
we're
all
struggling,
sometimes
with
money,
but
also
sometimes
with
services
and
by
this
our
startups
provides
data
code,
analysis
services.
H
H
A
A
Me
an
email
same
email.
Is
everyone
I'll
see
ya?
Ok,
actually
in
more
generally,
if
you
guys
have
I'm
happy
to
respond
to
all
the
emails,
but
an
easier
one
to
remember
than
my
weirdly
spelled
name
is
also
open
source
at
github
com
I,
also
man
that
inbox,
so
that's
effectively.
Emailing
me,
but
emailing
me
personally,
is
probably
even
better,
so
I
think
we're
almost
out
of
time.
But
does
anybody
have
one
last
question
that
they'd
like
to
ask
before
I
run
off
stage
great?
A
Thank
you
guys,
all
for
being
here
really
looking
forward
to
hearing
from
everyone
who
questions
and
also
from
anyone
else
who
has
thoughts
or
comments
or
feedback.
This
again,
getup
sponsors
just
start
of
all
the
stuff,
and
we
want
to
be
building
even
more
tools
for
you.
So
please
let
us
know
what
those
should
be
so
that
we
know
how
to
prioritize
thanks.
So
much.