►
From YouTube: How Intuit is overhauling legacy practices, at scale, with innersource - GitHub Universe 2020
Description
Presented by:
Aliza Carpio, Principal Tech Evangelist, Intuit
Rocio Montes, Staff Software Engineer, Intuit
For large enterprise companies with thousands of engineers across the globe, shifting to an innersource mindset and culture can be a formidable challenge. Such was the case for Intuit in early 2018 when the company set out on its innersource journey. At the time, its engineering teams were using different structures for their repositories, different best-practices for documentation, and different workflows for code reviews. Today, the company is well on its way to company-wide adoption of innersource, with more than half of its repositories open for contribution, and a goal to open them all. In this talk, Intuit will share a model that enterprise companies can use to teach global engineering teams to work as an innersource community. With easier ways to add features, manage dependancies, and build new skills, you'll come away with the knowledge your team needs to build better software faster.
For more from GitHub Universe 2020, visit https://githubuniverse.com
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
Thanks
rocio,
let's
just
just
jump
right
in
I'm,
not
going
to
say,
let's
jump
into
it,
but
let's
go
ahead
and
jump
right
in
now.
What
if
engineers
worked
as
a
community
as
code
stewards
and
not
code
owners?
Mark
earls
the
author
of
the
book,
titled
heard
cited
a
study
in
new
york
between
two
high
school
students,
two
high
school
schools
that
are
close
in
proximity
to
each
other,
but
also
have
similar
socioeconomic
conditions.
The
thing
that's
different
about
them,
though,
is
that
the
test
scores
between
the
two
schools
were
so
different,
especially
in
math.
A
One
of
the
schools
had
really
high
test
scores,
and
so
they
looked
into
why
and
what
they
found
was
the
school.
With
the
higher
math
test
scores.
They
found
that
the
students
worked
on
homework
together
and
studied
for
their
tests.
Together,
they
created
a
community
where
each
member
was
both
teacher
and
student
and
where
each
felt
supported
and
worked
towards
a
common
goal.
A
But
what
if
we
can
imagine
a
world
where
we
work
as
engineers
in
communities
of
practice,
have
almost
no
meetings
and
are
code
stewards?
We
would
probably
hear
something
like
this.
On
my
first
day,
I
was
up
and
running
and
ready
to
code
before
lunch.
Each
team
really
understands
the
customer
that
they're
solving
for
and
the
problem
our
team
gets
to
own
our
own
mission
make
decisions
and
solve
for
that
customer.
We
get
to
see
the
difference
that
we
make,
and
I
know
I
can
make
that
big
impact,
and
so
that
feels
really
great.
A
A
If
it
is
man,
we'd
love
to
connect
with
you
and
learn
from
you
now,
we
do
want
to
reach
that
nirvana
and
we
are
at
into
it
in
a
journey
to
get
there,
but
today
to
get
there
does
have
some
challenges
at
intuit
we
have
six
big
groups
across
multiple
continents
and
multiple
time
zones,
engineers
and
other
technologists
focus
on
delivering
solutions
declared
as
priorities
by
their
groups.
We
have
aggressive
schedules
to
deliver,
features,
fixes
and
products
to
millions
of
customers
and
speed.
Yes,
it's
a
necessity,
but
man
to
get
there.
A
There
are
some
challenges,
so
I'm
gonna
name,
four
of
them
right
now.
Let
me
just
build
this,
so
the
first
is
in
order
to
for
us
to
enable
work
effectively
right
now
we
are
still
in
this
journey
to
move
from
where
code
is
owned,
by
teams
and
and
individuals
to
to
to
more
and
we'll
talk
more
about
the
solution,
but
today
so
many
of
our.
So
much
of
our
code
is
still
owned
by
india
and
so
there's
a
heavy
reliance
on
these
folks.
A
To
actually
you
know,
do
everything
from
you
know
answer
questions
you
may
have
on
that
repo
to
you
know
allowing
or
to
doing
reviews
on
your
pr
now
the
waiting
that
is
involved
with
that,
especially
when
you
have
you
know
when
you
have
disparate
locations
across
the
globe,
can
get
in
the
way
of
really
being
speedy.
In
terms
of
you
know,
committing
your
code
and
that
actually
sometimes
leads
to
heroics
for
our
engineers.
A
A
B
We
implemented
a
solution
that
included
an
inner
source
model.
Inner
source
takes
the
principles
of
open
source
into
the
enterprise
environment,
inner
source,
it's
a
great
tool
to
help
break
silos,
encourage
internal
collaboration,
accelerate
new
engineering
onboarding
and
identify
opportunities
to
even
contribute
back
to
open
source.
So
let's
talk
about
what
our
inner
source
program
included.
B
When
we
first
started
to
look
at
inner
source,
we
discovered
that
many
business
units
and
team
were
already
practicing
some
form
of
inner
source.
The
logical
first
step,
then,
was
to
declare
a
set
of
unified
guidelines
that
outline
the
one
way
that
intuit
engineers
could
use
to
contribute
to
any
repositories
in
our
intuit
ecosystem.
B
These
unified
guidelines
included
a
document
structure
that
every
repository
should
have
in
order
to
be
inner
source.
Ready.
Github
will
automatically
recognize
these
files
and
enhance
a
collaboration.
Experience
for
engineers
documents
like
code
owners
to
quickly
get
those
prs,
a
line
assigned
to
a
code
reviewer
a
contributing.md
to
detail
the
rules
of
engagement
with
each
repository
and
the
pull
request
template
that
gives
every
contributor
a
checklist
to
complete
before
submitting
a
pr.
This
proven
to
be
really
helpful
in
the
contribution
process.
B
Additionally,
we
required
having
continuous
integration
and
continuous
deployment
automation
on
each
of
the
pr's
completed
with
unit
and
functional
tests
that
it
was
definitely
a
must.
These
pr
automations
gave
contributors
quick
and
useful
feedback
about
the
pr
and
the
code
that
they
are
trying
to
merge
on
the
next
slides,
we're
going
to
show
you
that
technology
changes
were
not
enough.
We
actually
needed
to
set
up
our
teams
for
success
in
this
new
world,
so
we
actually
needed
to
think
that
inner
source
is
more
of
a
mindset
change
rather
than
a
technological
approach.
B
We
needed
our
teams
to
understand
that
internal
engineers
were
now
a
first
customer
and
that
would
practice
trial
and
error.
There
were
going
to
be
that
these
frequent
contributors
that
were
going
to
become
a
trusted
committer,
it's
a
new
role
for
us,
a
role
with
defined
responsibilities,
to
ease
and
optimize
contributions
from
frequent
teens.
A
B
B
Additionally,
we
look
for
services
that
were
the
most
common
and
already
had
a
big
number
of
contributors,
so
we
prioritize
these
repos
and
getting
them
in
your
source
ready.
Of
course,
we
needed
to
establish
a
rewards
and
recognition
program.
We're
going
to
talk
about
more
on
that
later,
but
rewarding
early
adopters
was
really
important.
B
So
have
I
sold
you
on
getting
intersourced
implemented
in
your
company?
This
would
be
the
steps
that
you
need
to
take
in
order
to
do
so,
you
will
for
sure
need
leader
support
in
order
to
provide
you
know,
time
for
training
of
their
engineers,
time
for
their
engineers
to
adopt
engineer
guidelines
and
make
the
technology
changes
and,
like
I
mentioned
before,
you
need
to
create
a
set
of
unified
islands,
also
identified
your
model
teams.
B
These
themes
that
are
going
to
be
like
I
mentioned
foundational
capabilities
in
each
of
the
business
units
that
you
have
conduct
workshops
to
teach
how
to
do
in
your
source.
We
actually
have
workshops
at
each
into
its
site
and
every
chance
we
got
every
conference
every
event
there.
We
were
inner
source,
rah
rah.
So
it's.
B
B
You
need,
of
course,
engineers
and
a
product
manager
make
sure
that
you
have
diversity
under
volunteers
from
staff
level
to
early
career
team
members,
and
you
need
to
make
sure
that
they
actually
can
tell
a
story
and
can
do
it
well.
You
will
need
to
implement
dashboards
and
metrics
in
order
to
share
the
progress
and
track
the
readiness
of
the
repos,
as
well
as
the
ability
to
find
those
most
popular
repos,
and
the
foundational
capabilities,
tooling
and
rewards
proved
to
be
very
useful
in
getting
everyone
excited
about
inner
source.
B
We
recognize
that
all
the
benefits
when
we
talked
about
the
benefits
of
inner
source,
we
were
only
talking
about
the
benefits
to
the
business
right,
prioritization
ease
of
releasing
to
our
customers
more
quickly,
more
features.
But
when
we
wanted
to
focus
on
the
engineer,
the
benefits
were
that
they
were
able
to
collaborate
in
different
teams
and
collaborate
in
different
programming
languages
that
they
usually
do
on
their
teams.
So
the
intuit
first
time
contribution
site
on
the
previous
slide
outlined
projects
that
were
actively
looking
for
contributors.
B
These
projects
signed
up
to
the
site
and
said
here
are
some
of
the
issues
that
we
have
and
they
could
be
on
jira
or
on
github,
and
they
were
good
first
issues
that
anybody
could
jump
on
and
solve
them.
We
also
added
an
inner
source
batch
to
our
intranet
for
those
who
have
onboarded
to
inner
source
and
were
participating
in
the
program.
This
is
kind
of
like
a
bachelor
now
back
to
alisa.
Who
will
talk
about
the
engineering
benefits
that
we
saw
with
the
program.
A
Not
only
was
there
speed
and
delivering
solutions
and
and
products
to
customers,
but
there
was
definitely
higher
engagement
from
our
engineers
or
from
product
development
teams,
and
we
believe
that
that
and
we're
starting
to
see.
You
know
some
data
on
this,
but
we
believe
that
higher
engagement
leads
to
higher
higher
retention
of
top
tech
talent,
and
this
is
our
final
slide.
We
are
we'd
love
to
share
with
you.
A
The
resources
that
you
know
might
also
inspire
you
to
take
on
this
model
or
maybe
enhance
the
model
you
currently
have
on
your
inner
source
model
in
your
company.
The
first
is
the
book
that
I
mentioned
called
heard
by
mark
earls,
and
this
is
all
about.
How
do
you
tap
into
the
social
nature
of
beings,
including
human
beings,
in
order
to
actually
create
a
movement
in
order
to
actually
create
change?
The
second
is
inner
source
commons.
We
took
a
lot
of
inspiration
from
the
learnings
and
best
practices
that
they
shared.
A
We
also
wanted
to
make
sure
I
know
rocio
kind
of
touched
on
it,
but
fun
has
to
be
in
a
lot
of
the
things
that
you
do.
I
mean
rosia
talked
about
how
we
went
to
different
sites
and
did
the
rah-rah,
but
we
have
to
infuse
fun
and
we
loved
how.
When
we
looked
at
made
with
code,
they
had
a
section
under
community
and
we
love
some
of
their
ideas.
There
we've
definitely
adopted
those.
And
finally,
this
is
all
about
change
management.
A
Rocio
mentioned
it
that
yes,
tech
is
there,
but
so
much
of
it
is
mindset,
and
so
much
of
it
is
definitely
about
community,
and
so
we
recommend
this
book
by
the
heath
brothers
called
switch.
How
to
change
things
when
change
is
hard,
and
you
probably
you
know,
based
on
what
you've
heard,
you
probably
probably
heard
the
three
parts
to
that
book,
which
is
the
writer
the
visionary,
the
elephant,
which
is
the
emotional
impact
or
the
emotional
you
know
embodiment
of
what
you're
trying
to
do.