►
From YouTube: Why innersource is a critical component of FOSS sustainability - GitHub Satellite 2020
Description
Presented by Danese Cooper, VP Special Initiatives, NearForm
Innersource is the practice of proprietary companies adopting the modern massive peer-based software development engineering methods proven in thousands of FOSS projects over the past 20 years. Did you know that a booklet about innersource is the single most downloaded non-code asset on public GitHub? Since the rise of GitHub Enterprise, companies are increasingly experimenting with innersource inside their firewalls. Seems like a no-brainer, doesn't it? Most long-established companies need more collaboration and full-stack knowledge (and fewer information silos, resulting resource bottlenecks, "not-invented-here" re-inventions of the wheel, lack of innovation, and all the other un-necessarily wasteful proprietary practices that contribute to poor quality software and low engineering employee morale). Meanwhile, FOSS developers as a rule feel empowered to "scratch their own itches" and therefore suffer from few of these proprietary company woes. But as the FOSS movement has grown, there are cracks in sustainability starting to show in the form of maintainer burnout, lack of sufficient or appropriate corporate support for FOSS, and a real shortage of people willing and able to lead FOSS into the future. So how can innersource help FOSS Sustainability? Learn from someone who is thinking about how to grow the pool of qualified FOSS developers and to improve corporate support for FOSS basically since the term open source was coined. You'll hear about specific actions every developer and every company can take to improve software engineering, whether FOSS or proprietary, and help sustain the precious FOSS ecosystem through the next generation.
GitHub Satellite: A community connected by code
On May 6th, we threw a free virtual event featuring developers working together on the world’s software, announcements from the GitHub team, and inspiring performances by artists who code.
More information: https://githubsatellite.com
Schedule: https://githubsatellite.com/schedule/
A
B
B
Love
to
announce
our
next
speaker,
so
our
next
speaker
was
once
a
privy
Queen
at
Osan
sphere.
And
if
you
don't
know
that
means
she
was
an
outhouse
attendant,
but
then
worked
as
the
CTO
of
Wikipedia,
the
chief
open
source
of
and
her
son,
a
senior
director
of
open
source
strategy
for
Intel
and
another
person.
That
just
means
this
makes
me
feel
like
I
need
to
work
harder
because
of
everything.
A
B
A
C
There,
how
you
doing
my
name
is
Denise
Cooper
and
I.
Am
the
VP
of
special
initiatives
for
near
forum
and
I'm
gonna
talk
to
you
today
about
why
I
believe
that
inner
source
is
going
to
be
very
critical
to
phos
sustainability
in
the
long
term.
So
there's
my
twitter
handle
if
you
are
tweeting
and
let's
get
started
first
of
all
to
level
set.
This
is
tim
o'reilly
and
he
coined
the
term
inner
source
in
2000.
C
You
know,
get
better
outcomes
from
their
engineering
and
they
did
have
some
successes,
but
in
the
long
run
in
2000,
Okin
source
hadn't
been
running
long
enough
for
people
to
believe
that
it
was
a
better
way
to
write
software
and
so
the
company
pivoted
they
still
exist,
but
they
don't
do
a
ton
of
inter
source
anymore.
But
then
we
won
about
five
years
ago.
I
noticed
that
you
know
having
been
in
in
an
open
source
since
the
beginning.
I
noticed
that
people
were
not
fighting
us
anymore.
C
C
C
You
can
get
facility
and
any
part
of
our
code
base,
and
it
seems
like
that
would
be
a
good
thing
inside
of
companies
as
well,
so
I've
sort
of
dedicated
the
last
five
years
and
the
next
five
years
to
getting
inner
source
to
be
a
household
word
and
more
and
more
companies
to
use
it
and
you're
gonna
hear
more
about
that
in
a
minute.
These
are
some
of
the
reasons
why
companies
engage
in
a
nurse
and
I'll
get
to
the
open
source
bit
in
a
second.
C
But
when
you
have
over
specialization
in
a
company,
that's
where
just
a
few
people
know
everything
about
a
key
piece
of
the
code,
but
the
rest
of
the
company
doesn't
really
know
much
about
it
that
creates
silos
and
that
ownership
culture
can
be
a
good
choice
at
some
point
in
a
company's
evolution.
But
if
you
let
it
go
for
too
long,
you
start
seeing
technical
debt
pile
up
and
that's
you
know
denoted
by
the
rust
in
this
picture.
C
It's
not
the
only
structure
that
can
do
this
and
an
engineering
organization,
but
if
your
resources
are
not
being
fully
utilized,
people
are
sitting
around
waiting
for
somebody
else
to
get
something
done,
because
they've
made
a
feature
request
and
nothing's
changed.
Yet,
especially
if
your,
if
your
executives
are
getting
involved
in
escalating
the
priority
of
specific
features
or
specific
requests,
that
you've
got
a
bottleneck
problem.
C
So
this
is
the
number
two
reason
it's
the
number
one
reason
that
PayPal
started
doing
it,
however,
and
there's
a
book
about
that
that
github
has
turned
into
the
most
important
or
popular
non
code
asset
on
github.
It's
called
getting
started
with
inter
source,
and
you
can
go
get
a
copy
of
it.
There
it's
26
pages
and
it's
all
about
a
bottleneck
story.
C
C
They
expect
openness,
they
expect
agency
and
the
way
that
traditional
engineering
is
conducted
is
sort
of
solely
facing
to
them,
which
you
might
think,
isn't
important,
but
if,
if
you've
spent
a
lot
of
money,
selecting
them
and
hiring
them
and
training
them
to
have
them
leave
sooner
than
you
want
them
to
is,
is
not
a
good
thing,
so
there
are
companies
who
are
trying
to
modernize
or
transform
themselves.
Agile
was
the
first
wave
of
this,
but
we've
seen
successive
waves
and
inner
source
is
definitely
one
of
them.
C
Ok,
luckily
there
is
github
and
of
course
this
is
gonna
have
satellite.
So
thanks
for
the
octocat
guys,
but
there
are
other
tools
you
could
use.
Github
is
just
the
one,
that's
most
popular
and
most
associated
with
inner
source
and
they
are
starting
to
write
features
that
are
really
supportive
of
the
inner
source
experience.
Unfortunately,
a
lot
of
companies
go
get
github,
Enterprise
hoping
to
get
inner
source
events
to
happen
inside
the
company,
even
if
they
don't
have
a
name
for
that.
They
want
more
code
reused
or
they
want.
C
You
know
cross
company
understanding
of
the
code
base
or
something,
but
then
when
they
get
it
inside,
they
those
potentials
by
mirroring
whatever
permission
structure
was
in
their
previous
code
management
system,
something
like
well
at
Westar.
Those
people
must
be
excluded
for
a
reason,
so
just
getting
github
enterprise
and
standing
it
up
is
not
enough
to
get
your
culture
to
change
and
that's
why
there's
room
for
people
like
me
to
talk
about
inter
source
to
you?
So
so
this
is
the
inner
source
logo,
as
I
say
in
2015.
C
I
started
talking
about
inner
source,
taking
a
big
career
risk
frankly,
because
open
source
advocates
were
not
into
inner
source
at
that
point
because
they
want
more
open
source
code
and
to
them
it
feels
like
detour,
but
I
realized
in
my
consulting
practice
that
most
of
the
companies
who
were
going
to
come
to
open
source
naturally
had
already
done
so
now.
This
doesn't
count
new
companies
but
I'm
talking
about
the
existing
companies
and
remember
I'm,
worried
about
that
85
percent
that
are
stuck
in
the
salt
mines.
C
So
I
thought
that
if
we
could,
you
know,
use
inner
source
as
a
not
painless,
because
it's
definitely
a
trick
to
get
it
and
implemented
in
your
company
well,
but
to
get
companies
started
on
their
inner
source
journey
inside
the
firewall,
so
they're
not
risking
brand
embarrassment
if
they
get
it
wrong
and
I
posited
that
that
would
lead
to
more,
not
less
open,
source
and
I.
Think
that's
true.
So
now
we're
to
the
question:
is
inner
source
going
to
actually
help
vas
sustainability?
C
Is
it
really
going
to
be
you
know,
hands
across
the
ocean
and
I
think
so.
Here's
some
evidence.
First
of
all,
today,
most
open
source
developers
work
for
a
company
that
pays
them
to
do
open
source
now,
20
years
ago,
open
source
was
mostly
a
hobbyist
thing.
You
did
your
day
job
and
then
you
came
home
at
night.
C
You
worked
your
open
source
project
that
it's
been
a
long
time
since
that
was
true
and
I
personally
think
that
that's
a
really
positive
development
for
open
source,
for
instance,
Linux,
would
not
have
triumphed
over
many
other
unix's.
If
IBM
had
not
said,
look,
here's
our
logo
right
next
to
the
penguin,
we're
making
a
bet
on
this
that
was
incredibly
validating
18
years
ago,
when
they
did
it
well,
maybe
it
was
nineteen
years
ago
when
they
did
it,
and
you
know
it
made
all
the
difference.
So
I
think
it's
a
good
thing.
C
That
corporations
are
paying
people
to
work
on
open-source
as
long
as
they
on
that
at
the
end
of
the
day,
any
reputation
that's
built
around
that
project
belongs
to
the
individual
developer,
not
to
the
company.
It's
a
halo
effect
to
the
company,
because
open-source
is
people
and
it's
individual
people,
because
people
change
jobs
right,
but
I'm
worried
more
about
in
the
sustainability
realm.
First
of
all,
how
can
we
make
sure
that
maintainer
burnout,
which
is
a
really
big
problem,
goes
away?
C
How
can
we
scale
open-source
not
just
more
projects
but
more
people
working
on
the
projects,
so
I
started
thinking
about
the
need
to
train
younger
and
younger
people
to
think
about
software
development
in
an
open-source
way
or
an
inner
source
way
right
now,
inner
source
open
source
are
not
really
taught
in
universities
much.
There
are
a
couple
of
pioneering
teams
that
do
that,
but
mostly
it's
still
the
old
school
way
of
doing
development.
In
fact,
it's
hard
to
learn,
agile
in
an
or
in
a
university.
Now
right.
So
excuse
me.
C
They
have
to
be
interested
in
that
being
taught
so
that
the
employees
that
they
hire
already
know
how
to
do
it
in
our
comfort
with
it
and
that
pushes
that
age
lower
and
lower
that
we
start
teaching
how
to
do
this
stuff-
and
you
know,
really
open
sources
about
all
the
votes
rising
in
collaboration
winning
over
competition.
It's
still
possible
to
compete,
but
why
compete
on
the
horizontal
stuff
compete
on
the
verticals
right?
Alright,
but
also
you
know
we
have
so
many
projects
now
and
so
few
experts
that
can
actually
maintain
them.
C
As
I
keep
saying,
we
have
real
fatigue
going
on
and
I
think
that
dipping
into
the
existing
pool
of
engineers
is
the
fastest
way
to
get
people
who
are
willing
to
work
on
maintaining
projects,
because
you
know
they're
battle
tested,
they've
been
in
companies,
they
know
about
the
long
haul
and
if
you
have
successful
software,
it's
not
all
invent
invent,
invent.
There's
an
awful
lot
of
maintain,
maintain
I
think
that
the
best
place
we
can
go
to
look
for
that
that
skill.
Those
maintainer
is
in
the
existing
pool
of
engineers.
C
C
This
is
a
list
of
companies
that
talk
openly
about
their
inner
source
journey
and
it
represents
a
small
percentage
of
the
total
companies
that
are
involved
in
inner
source
and
I
know
that,
because
I
talked
to
most
of
them,
these
are
there's
people
who
are
willing
to
be
public,
so
we
can
quote
them,
but
I
want
you
to
notice
two
companies
in
particular
on
this
list.
I
mean
there's
a
pretty
broad
group
here,
but
look
up
in
the
corner
there
in
the
left
is
Microsoft
and
then
Comcast
right
sort
of
kitty-corner
to
it.
C
Those
are
surprising
companies,
in
my
opinion,
to
be
on
an
inner
source
journey
for
different
reasons,
but
why
they
did
it
is
sort
of
similar,
so
both
of
those
companies
started
with
a
little
open
source
at
the
edges
of
the
company,
and
this
is
a
really
common
pattern.
People
don't
want
to
go
all
in
on
open
source.
They
start
out
with
just
one
project
at
the
edge
and
those
engineers
have
special
rights.
They're
specially
able
to
go.
Do
this
work
on
this
project
right
well
after
they
get
a
taste
of
that
success.
C
And
then
Microsoft
is
an
even
more
interesting
case,
because
you
know
famously
they
were
the
big
enemy
of
open
source
for
a
long
time,
but
they
have
fixed
that
and
now
they
want
all
the
engineers
of
Microsoft
to
learn
how
to
work
in
this
collaborative
way.
And
that's
a
sea
change.
That's
the
kind
of
thing
that
will
really
build
the
number
of
people
that
are
available
to
maintain
projects.
C
So
the
reason
I
know
those
stories
in
depth
is
because
I
run
a
podcast
through
my
company,
that
is
about
inner
source
and
what
companies
are
doing
with
it
and
I'll
tell
you
a
little
bit
later
how
to
get
to
that
podcast.
This
is
a
graphic
that
Bosch
built
for
itself
that
shows
clot
cross
collaboration
within
their
divisions.
So
each
of
those
little
clusters
is
a
division
of
the
company
and
all
of
the
cross
connects
in
the
center,
our
collaboration
that
are
happening.
C
This
is
inter
source
Commons,
which
is
your
one-stop
shop
if
you're
interested
in
learning
more
about
inter
source,
this
is
a
nonprofit,
or
at
least
it
we
filed
for
a
non-profit
status
that
it's
a
community.
That's
been
together
for
about
five
years
and
like
any
open
source
community
there's
you
know
a
10x
progression
of
people
who
are
looking
to
people
who
are
contributing
to
people
who
are
leading.
So
you
can
meet
the
leaders
of
the
inter
source
movement,
inner
source,
common
story.
C
You
can
find
out
about
events
that
they're
holding
you
can
find
assets
like
like
PDF,
copies
of
all
the
books
that
have
been
written,
including
that
one
I
mentioned
earlier,
and
my
latest
book
and
and
books
that
other
people
have
written
in
an
academic
research
all
aggregated
into
one
place.
You
can
find
it
and
and
then
work
that
the
community
is
doing
to
build
training
assets
that
are
freely
available
and
also
patterns
to
identify
patterns,
and
all
of
this
work
is
done
with
a
lot
of
joy.
C
It's
really
a
great
community
and
you
can
join
it
for
free
by
just
asking
for
a
slack
account
on
this
front.
Page
of
inter
source
of
common
story,
so
I
hope
you
guys
will
go
check
that
out
and
now
we're
coming
to
the
end
of
my
story
about
how
inner
source
is
going
to
help
the
open
source
movement.
That
was
absolutely
my
motivation
for
bringing
it
to
the
fore
again
and
I'm,
seeing
you
know
not
just
those
two
companies
I
mentioned,
but
all
over
town
I'm
seeing
open
source
come
out
of
this.
C
So
let's
join
together
in
the
beautiful
new
future
that
we're
hoping
for-
and
thank
you
very
much.
This
is
the
URL
to
find
those
podcasts,
I,
think
near
form.
Comm
slash,
inner
source
might
work
as
well,
but
that
one
will
definitely
work
my
email
address.
If
you
want
to
get
a
hold
of
me
and
thank
you
so
much
for
this
opportunity
to
talk
about
inner
source
and
class
today,
I
really
enjoy
talking.
C
A
Thank
you.
Sorry
much
that
wonderful
presentation,
taste,
I,
love
all
the
talk
about
open
source,
it's
something
they
talk
about
a
lot
on
the
enterprise
side,
on
the
sales
side
and
I
think
it's
a
really
good
stepping
stone
to
get
into
open
source
as
well
I.
Just
thank
you
so
much
that
presentation
also
for
showing
us,
the
cool
logo
party
and
a
logo
in
a
source.
Alesis
is
really
going
to
tweeted
it
out
yourself.
Yes,
right,
thank.
C
A
B
Do
an
absolute
honestly
I
want
to
thank
you
as
well
Denise.
You
know,
I
I,
don't
have
the
the
career
that
you
have
had
yet,
but
I
do
go
and
talk
with
enterprises
about
inter
sourcing,
and
you
know
the
top
topics.
I
usually
talk
about
are
how
you
know
open
collaboration
encourages
more
contributions.
You
have
developers
that
don't
have
to
start
from
scratch
on
new
projects
and
ultimately
it
strengthens
the
project,
but
I
think
something
I
learned
from
you
is
it's
a
great
recruiting
tool
as
well
and
I?
B
C
Well,
I
think
it
can
be
at
the
very
least,
it's
going
to
clean
up
some
of
the
problems
in
your
engineering
organization,
but
my
experience
is
that
something
like
75%
of
the
companies
that
I
have
worked
with
and
I'm
trying
very
hard
to
touch
most
of
them
find
that
they
are
better
equipped
to
deal
with
open
source
as
a
holistic
thing,
not
just
a
you
know,
weird
boutique
thing,
that's
happening
on
the
edges
of
the
company
and
that's
super
positive
I.
Think.
C
A
C
It's
definitely
cultural
shift
it
that,
if,
if
it
was
easy
for
people
to
figure
out
how
to
do
this,
they
just
do
it.
But
what
we
find
is
each
individual
company
is
not
collaborating
for
a
different
reason.
So
in
some
companies,
they've
concentrated
on
hiring
wizards
or
they've
grown
wizards
and
the
wizards
don't
want
to
share
their
tricks.
That's
really
a
common
problem
right
in
other
companies,
everybody's
matrixed
into
time,
management
and
they're
all
come
there,
basically
competing
against
each
other
inside
the
company
for
resources,
so
their
management
won't.
C
Let
them
share
with
other
groups,
because
that
would
be
you
know,
giving
away
points
in
the
game.
Somehow,
there's
lots
of
different
reasons
why
companies
don't
collaborate
more,
but
they're
usually
reasons
that
also
lead
to
bad
habits
and
endemic
problems
that
are
hurting
the
company,
creating
technical
debt
or
or
giving
them
liability,
because
they
just
don't
have
good
cross
company
knowledge
about
how
things
work
right.
B
A
killer
productivity,
you
know
and
I
think
for
a
couple.
We
have
a
couple
more
questions
coming
in
here
now
and
I
think
with
companies
that
I
stalk
with
a
lot
you
know
say
when
we're
trying
to
promote
inner
source
a
lot
of
what
they
say.
Is
you
know
we?
Don't
we
just
don't
do
that
here
or
we're
scared
of
open
source
and
I'm
sure
you've
heard
that
yeah,
it's
not
a
thing.
C
You
know:
there's
lots
of
different
ways
to
get
open
source
off
the
ground
and
the
last
book
that
I
wrote
a
year
before
last
with
somebody
from
University
of
Limerick
class
young
Stoll
who's,
a
researcher
right,
so
it's
sort
of
academic
but
also
groovy
kind
of
book.
It's
a
case
study
book
and
it
talks
about
different
companies
that
have
gotten
to
inter
source
in
different
ways
and
actually
we're
getting
ready
to
do
another
edition
of
it,
because
we
found
some
more
really
good
patterns
and
stories
about
how
people
get
there.
C
But
there
are
companies
that
get
there
from
a
single
engineer,
literally
a
single
engineer,
saying
wow:
why
aren't
we
using
the
reusing
code
more?
Why
are
we
all
writing
the
same
code
or
solving
the
same
problem
based?
How
is
that
better?
And
you
know
if
it's
the
right
engineer-
they
can
lead
a
revolution
from
where
they're
sitting
now
eventually
they're
gonna
need
the
support
of
senior
management,
but
they
can
get
pretty
far
in
showing
the
value
that
can
be
created
by
just
by
shifting
to
this
other
way
of
working.
C
Just
by
doing
it
themselves,
you
know
solving
their
own
problems
first,
which
open
source
is
basically
enlightened,
self-interest
right.
We
we
wanted
to
be
able
to
make
changes
so
that
we
could
get
our
own
work
done
faster
rather
than
relying
on
other
people
to
have
time
to
do
it.
It's
a
it's
agency,
being
you
know
manifest
and
in
companies.
A
lot
of
culture
has
beaten
that
out
of
the
engineers
and
I
think
that's
unfortunate,
because
there's
so
much
better
if
they
have
a
little
agency,
but
it's
also
possible
that
senior
management
decides.
C
A
B
C
Is
one
of
the
prime
movers
or
inner
source
adoption
right
now,
because
everybody
has
to
do
it
from
scratch?
There
is
no
just
add
water
and
you
have
DevOps
solution.
You
have
to
fit
it
to
your
culture
in
your
organization,
so
you
got
a
choice.
You
can
do
all
of
it
yourself.
Every
single
team
doing
their
own
integration,
their
own
deployment
characteristics
or
you
can
do
it
once
for
the
company
or
you
could
do
just
the
deployment
once
and
then
let
everybody
integrate,
there's
lots
of
different
ways
to
get
there.
C
But
it's
an
opportunity
for
code,
reuse
that
we
don't
see
come
through
very
often
so
yeah
you
for
doing
that
and
I
think
what
you
need
to
do
is
be
able
to
demonstrate
again
the
value
that
you're
creating
for
the
company
by
doing
inter
source
and
come
over
to
the
discussions
group
and
we'll
talk
about
tomorrow.
Hey
Oh.
A
Denise
is
alright.
Thank
you.
So
much
for
presentation,
as
Denise
said,
she's
gonna
be
over
in
the
discussion.
The
next
stop
now
now
before
you
grab
minis
you've
tuned
in
all
the
way
from
island.
I
know
it's
so
late
as
I.
Thank
you
so
so
much
for
staying
up
with
us
and
providing
all
that
amazing
millions
of
you
know
sauce.
Thank
you
very
much.
Thank
you
for
the
opportunity.