►
Description
2:02 - Program Start
3:34 - Q&A Intro
3:55 - What is InnerSource and how is it different from Open Source?
8:10 - How do you start practicing InnerSource?
12:49 - Who would be the most important stakeholder in supporting an InnerSource initiative
16:47 - What is an Open Source Programs Office?
20:19 - Do organizations have to fully adopt open source practices to be effective?
25:35 - How can I implement or adopt InnerSource? What are the first steps?
31:55 - How do I measure the success of InnerSource?
43:51 - What tools can help improve the discovery of InnerSource projects within a company?
45:35 - A practical checklist for getting started with InnerSource
50:42 - Further resources
What is #InnerSource? How is it different from Open Source? How does it help organizations? What are practical steps to move InnerSource forward within a company? These and many more questions are answered by Zack Koppert and Prem Ponuthorai, Senior DevOps Engineers.
InnerSource Commons: https://innersourcecommons.org/
InnerSourceFAQ template: https://github.com/demo-days/innersource-faq-template
A
Hello,
hello,
hello,
friends,
nice
to
see
you
all
hello
to
folks
from
iran,
hello
to
folks
from
paris
happy
friday,
happy
saturday
for
some
of
you
good
morning
good
afternoon,
good
evening,
good
night
and
thanks
to
everyone,
especially
for
those
of
you
who
are
joining
us
in
the
wee
hours
of
the
morning.
I
I
hope
there
are
other
ethiopians
in
there,
hello,
everyone.
I
see,
canada.
A
I
see
rio,
belarus,
that's
awesome,
tajikistan,
colombia,
colombia,
shout
out
to
colombia.
I
know
things
are
not
super
easy
over
there.
We're.
Thinking
of
you
also
not
super
easy
for
the
folks
in
india.
We
are
also
thinking
of
you,
but
to
get
right
to
it.
Today
we're
going
to
dig
into
a
new
topic
for
the
next
few
streams
inner
source,
whereas
last
month
we
talked
about
what
is
open
source
software.
A
Why
you'd
want
to
use
or
contribute
to
it,
how
to
do
it
safely
and
what
structures
in
a
company
can
help
with
the
process.
Now
we're
going
to
talk
about
what
we
can
learn
from
how
open
source
works,
not
quite
the
code
itself,
but
the
process
of
open
source
software
development
and
with
that
I'd
like
to
bring
in
zach
back
from
our
last
stream
as
well
as
prem,
both
of
them
are
senior
devops
engineers
welcome,
gentlemen.
B
D
C
D
Before
we
get
in,
I
think
hello
to
everybody,
shout
outs
to
everybody
who
is
making
time
to
to
jump
in
for
this
session.
What
we've
got
lined
up
for
today's
session
is
more
towards
the
q,
a
where
zack
and
myself
are
going
to
be
quizzing,
each
other
understanding
what
is
in
a
source
and
how
our
experience
speaks
to
the
different
stakeholders
that
has
been
involved
in
their
inner
source
journey.
So
without
further
ado,
I
think
zach.
B
Yeah,
that's
a
that's
a
great
question
and
a
perfect
one
to
get
us
started
so
that
folks
can
understand
to
all
be
on
the
same
playing
field
here
when
we're
talking
about
terminology
like
inner
source
and
and
organization
initiatives
and
all
that
kind
of
stuff,
so
to
get
started
with
the
first
part
of
that
question.
You
know,
inner
source
is
essentially,
if
I
boil
it
down
to
one
sentence:
it's
the
application
of
open
source
practices
like
code
reusability
and
building
communities
around
code
from
different
places
and
that's
all
applied
inside
of
an
organization.
B
C
B
Inner
source
like
how
would
that
even
work
inside
a
company
like
companies,
you
know
develop
products,
somebody's
building,
a
website
like
they
wouldn't
intersource
that
to
the
company,
because
that
company
is
inside
that
company
they're
going
to
build
other
websites
that
look
exactly
like
that
one
well,
it
starts
to
actually
work
if
you
break
it
down
into
smaller
modules,
smaller
pieces
right.
So
let's
say
you
know
we're
building
a
two
websites
for
github.
For
example.
B
You
know
one
of
them
is
going
to
be
our
our
github.com
our
main
website
and
then
the
other
one
is
going
to
be
like
our
support
website,
but
maybe
they
both
have
a
chat
feature
or
something
like
that.
Well,
you
don't
have
to
write
that
code
twice
from
two
different
teams:
yeah,
you
know
possibly
even
on
two
different
technologies.
B
You
can
just
write
it
once
and
reuse
it
in
both
places,
but
you
have
to
have
this
mindset
across
your
whole
organization
and
the
visibility
and
transparency
across
your
whole
organization
to
be
able
to
see
those
opportunities
for
consolidating
right,
and
so,
when
I
can
say
consolidate,
I'm
talking
about
you
know
just
reusing
a
single
piece
of
code
instead
of
doing
it.
So
it's
a
lot
of
people
ask
about
like
well
what
what
tool
do
I
need
to
install
for
to
to
use
inner
source?
It's
not
like
that
at
all.
B
It's
it's
more
about
a
community.
It's
a
way
of
working!
It's
a
way
of
developing
your
products
by
looking
at
what
exists
first,
just
like
we
should
be
looking
at
what
open
source
exists.
First,
before
we
try
and
build
stuff,
we
should
also
be
looking
at
what
inner
source
exists
or
can
be
created
before
we
build
stuff.
So
that
makes
sense
answer
your
question.
C
D
B
B
We
don't
want
to
reinvent
the
wheel
right
yeah,
but
then,
when
you
think
about
what
it
feels
like
to
actually
do
inner
source,
it
feels
like
a
community
of
people
from
different
spots
in
your
organization,
not
just
your
team
working
on
a
single
piece
of
code
right
and
it
feels
like
managers
collaborating
together
and
talking
about
how
they
can
get
features
done
versus
assigning
it
to
a
specific
team.
It's
got
to
get
done
by
a
specific
deadline,
and
otherwise
you
know
the
whole
train
kind
of
comes
off
the
tracks
right.
D
B
C
B
B
D
That's
that's
a
that's
a
good
one.
I
think
it's
they
say
the
journey
of
thousand
steps
starts
with
one
the
first
step
and
the
first
steps
always
the
hardest,
and
I
think,
in
my
opinion,
the
first
step
towards
adopting
or
embracing
any
source
is
creating
a
culture
of
sharing
right
and
it's.
I
know
it's
very
broad
in
in
terms
of
like
how
do
you
start
sharing?
How
do
you
create
the
culture,
because
it's
not
something
that
that
is
out
of
a
book
or
something
that
you
can
instruct
people
right?
D
I
think
one
quick
way
on
how
you
can
get
started
with
creating
a
culture
of
sharing
is
creating
communities
of
practice
within
the
organization
and
within
github
itself
within
our
team.
You
know
there
is
a
great
bunch
of
community
of
practice.
Folks,
I
know
like
you
know,
I've
been
I've
been
blessed
to
work
with
these
great
individuals.
D
The
entire
team
who
has
been
spearheading
specific
subject
matters
in
their
community
of
practice
areas.
So
you've
got
people
in
in
let's
say,
administration
practice
that
that's
javier
and
then
yourself,
who
is
in
the
open
source
and
innosource.
We've
got
stefan
who's
into
migrations.
We've
got
also
at
the
other
stephen
to
actions,
and
you
know
I'm
missing
out
a
lot
of
names,
but
the
entire
group
of
team
that
we
have
have
created
a
community
of
practice
verticals
on
different
topics
where
we
share
and
discuss
about.
D
How
can
we
better
improve
the
solutions
that
we
have
right?
Not
only
solution,
but
also
the
tools
and
the
key
criteria
in
collaboration
or
creating
the
culture
of
sharing?
Is
we
created
a
a
place
or
a
voice
where
it's
it's
hurt,
and
this
voice
is
in
terms
of
the
shad
communication
channel
that
we
have
right-
and
this
is
you
know,
slack
workspace.
D
Right
because
you
know
it's
the
same
principle
of
open
source
where,
as
an
example,
if
you
have
an
excellent
community,
but
if
you
have
a
code
base
that
is
not
so
good,
the
community
is
going
to
strive
to
make
it
better
right,
whereas
the
the
reverse
is
also
true
right.
If
you
have
an
excellent
code
base,
but
if
you
don't
have
a
community
that
gives
too
much
attention
to
it,
the
code
base
is
eventually
going
to
die
off
right.
D
B
Cool
yeah,
so
if
I
was
kind
of
summarize
some
of
the
ideas
that
you
talked
about
at
a
high
level,
it
sounds
like
building
communities
around
code
and
having
those
communities
really
tend
to
or
garden
those
code
bases
to
keep
them
sort
of
evergreen
to
keep
them
in
a
good
spot.
And
then,
when
you
talk
about
what
these
communities
are
centered
around,
it's
it's
not
just
code,
but
it
sounds
also
like
we're
talking
about
you
know.
B
D
C
A
D
Us
the
freedom
to
create
the
practice
areas
and
build
a
community
around
it.
So
I
think
it's
a
great
shout
out
to
all
of
those
folks.
There
yeah
yeah,
awesome,
yeah
yeah,
that's
a
shameless
plug,
I
admit,
but
I
think
hey,
I
gotta.
Do
it
so
right.
So
my
next
question
to
you,
since
we
spoke
about
community
right
who
do
you
think,
would
be
the
most
important
stakeholder
as
a
community
to
support
this
innocence
initiative.
B
Despite
any
feelings
so
yeah
in
terms
of
like
most
important,
I
could
give
you
maybe
the
top
two
or
three
but
yeah
so
in
terms
of
stakeholders
in
in
your
organization
that
you're
trying
to
get
intersource
moving
in,
I
would
say
the
the
first
thing
is
really
to
look
at
the
individuals
that
would
make
up
these
communities
right.
So
you
could
convince
leadership.
B
You
could,
you
know,
make
pretty
power
points
that
people
clap
at
the
end,
but
if,
if
you
don't
have
folks
on
the
ground
who
are
actually
dealing
with
these
subjects
that
want
to
engage
in
a
community
of
people
that
deal
with
that
subject,
then
it
won't
work
right,
it'll
fall
apart,
you
don't
have
a
community
without
community
members,
so
there's
that
way
to
look
at
it.
Another
way
to
look
at
it
and
I've
seen
it
go
both
ways
is.
B
Is
that
if
you
don't
have
the
leadership,
support
and
a
specific
real
like
sponsor
somebody
who's
really
behind
this
and
trumpeting
the
benefits
and
things
like
that
at
the
leadership
level,
then
you
know
they
could
find
out
about
this.
Oh
okay,
you
know
several
people
from
different
product
lines
are
meeting
on
this
topic
of
you
know.
B
I
don't
know
how
to
deal
with
databases
on
the
web
and
and
trying
to
optimize
that-
and
you
know,
I
think,
that's
just
a
waste
of
time
as
a
leader,
so
I'm
going
to
ask
them
to
stop
doing
that
because
it's
not
revenue
generating
activity.
You
know
I'd,
rather
them
just
focus
on
their
product
backlogs,
which
are
moving
too
slow,
or
you
know
just
different
things
like
that
and
trying
to
optimize
out.
You
know
this
this
sort
of
sharing,
so
you
don't
want
leadership
to
stamp
it
out.
B
So
you
need
a
leadership
sponsor.
You
want
a
community,
so
you
need
community
members.
The
other
important
stakeholder
is
sometimes
this
isn't
necessarily
like
leadership
or
a
community
member,
but
like
a
facilitator,
think
about
like
a
program
manager.
Somebody
like,
if
you
have
an
open
source
programs
office
like
we
talked
about
last
week
on
friday,
on
on
demo
days.
If
you've
got,
you
know
somebody
managing
how
you
consume
and
produce
open
source.
B
That
leadership
is
maybe
more
willing
to
accept
versus
just
like
these
hodgepodge
tag.
Groups
of
people
that
are
trying
to
network
with
each
other,
but
sort
of
don't
have
the
visibility
into
other
teams
and
I'll
just
say.
I
I'm
saying
all
of
these
things
as
if
your
organization
is
very
large,
you
know
and
that
you
have
multiple
products,
some
organizations
don't
and
that
doesn't
mean
that
inner
source
isn't
important
there.
D
B
Yeah
yeah
yeah
definitely
yeah.
I
like
that
illustration.
That's
a
good
example
nice.
So
I've
got
a
question
for
you.
I
mentioned
I
mentioned
open
source
programs
offices.
I
I
said
you
know
we
talked
about
that
last
week
on
on
demo
days,
so
you
know
kind
of
with
the
pers
perspective
of
inner
source
or
for
people
that
didn't
catch
the
the
last
session.
What
is
in
ospo?
What's
an
open
source
programs
office.
D
A
definition
towards
the
business
goal
of
an
organization
is
really
very
important
because
you
need
a
clear
message.
I'll
give
you
an
example,
let's
say
we're
trying
to
navigate
out
of
a
maze
right,
and
I
use
this
example
all
the
time.
So,
if
I
were
to
instruct
somebody
to
to
safely
get
out
of
a
maze,
I
would
say
face
north
walk
for
about
15
minutes
at
a
six
minute
pace
and
then
face
ease
and
then
walk
another
20
minutes
at
a
seven
kilometers
per
hour
pace.
D
Then
you
should
be
safely
out,
but
my
colleague
would
be
giving
the
same
instruction,
but
my
might
have
just
simplified.
It
will
say
that
face
forward,
walk,
20
steps,
turn
left,
walk
another
15
steps,
and
you
should
be
out
all
right.
So
we're
essentially
saying
the
same
message,
but
we
are
defining
it
a
bit
differently
right.
So
I
think
ospo
provides
the
clarity
in
terms
of
what
definition
for
inner
source
or
open
source
means
to
an
organization
right
and
to
come
up
with
this
clear
definition.
D
D
B
Is
interesting,
and
so
I'm
not
going
to
try
and
summarize
that
since
you
summarized
it
so
nicely,
but
I
do
have
a
follow-up
question,
you
know
I'm
thinking
about
how
open
source
and
inner
source
mirror
each
other
and
how
you
know
open
source
can
be
sort
of
chaotic
there's
people
coming
in
from
everywhere.
You
don't
know
what
group
of
people
is
working
on.
What
and
nobody
can
tell
anybody
what
to
do.
B
You
know
do
organizations
do
they
have
to
like
change
to
that
model,
where
you
can
literally
pick
up
your
desk
and
switch
teams
and
switch
managers,
so
you
know
just
based
on
a
whim
or
or
can
you
still
have
an
organization
that
maintains
structure
and
order
and
planning
and
road
mapping,
but
also
do
inner
source
like
does
that?
Do
those
two
things
even
work
together,
yeah.
D
I
that's
a
really
good
question.
I'm
glad
we're
not
keeping
scores
yeah.
I
think
it
depends
on
the
scale
of
the
organization
and
also
its
journey
in
towards
adopting
open
source
and
in
a
source
right
in
most
organization.
I
believe
ospo
starts
off
like
a
group
of
evangelists,
like
a
virtual
team
where
they
have,
like
you
say
start.
D
You
know
a
time
to
meet
and
discuss
about
initiative
and
promote
all
the
efforts
that
they
are
they're,
doing
around
open
source
and
in
source
for
the
organization
once
it
gets
a
little
bit
more
serious
and-
and
we
see
the
the
return
on
investment
and
recent
investment
is
a
big
word.
You
can't
really
quantify
because
it's
there's
no
one
magic
wand
where
we
can
wave,
and
it
says
that
this
is
how
much
you're
going
to
get.
If
you
invest
this
much
time
in
doing
inner
cells
or
open
source
right.
C
B
That
makes
sense
yeah,
and
I
think
that
that
gives
me
hope
that
if
there's
somebody
managing
sort
of
the
alignment
with
the
company
strategy
and
things
like
that-
that
it's
less
likely
to
sort
of
get
chopped
off
and
seen
as
extracurricular,
so
to
speak,
but
more
something
that's
seen
as
an
accelerant.
That
can
really,
you
know,
achieve
the
company's
main
targets
right.
D
Agreed
and
I
think,
to
give
you
an
example
like
how
important
or
how
an
hospital
could
influence
the
the
business
goal.
Let's
say:
if
the
company's
business
goal
is
to
hire
and
retain
talent,
then
they
could,
you
know,
involve
themselves
in
initiatives
that
that
review
the
toolings
that
they
use,
as
well
as
awareness
and
education,
on
how
you
know
the
cool
technology
or
the
cool
platforms
being
used
to
do
software
development
or
to
roll
out
their
their
businesses
right.
D
So
in
that
sense,
they
could
speak
with
the
hr
team
to
say
that,
okay,
maybe
we
need
to
change
the
job
description
or
maybe
we
need
to
say
that
these
are
the
toolings
that
we're
looking
for.
These
are
the
skills
that
we're
looking
for
so
we're
looking
for
somebody
who
is
involved
in
open
source
or
someone
who
knows
about
inner
source.
We
need
those
champions,
so
we
want
to
do
this,
so
they
can
speak
to
the
hr
folks.
D
They
can
also
speak
with
the
different
engineering
managers
to
say
that
all
right,
okay,
we
want
to
roll
out
this
initiative
and
we
need
the
buy-in
so
that
you
have
cross-department
collaboration
and
what
this
benefits
is.
Everybody
wins
so
that
you
don't
need
to
reinvent
the
wheel
and
recreate
the
same
library
where
one
team
creates
a
library
and
the
other
team
leverages
or
helps
to
reduce
the
backlog
of
a
specific
team
right.
D
So
once
you
have
those
different
individuals
representing
different
stakeholders,
I
think
coming
up
with
initiative,
or
speaking
you
know
even
getting
sponsorship
speaking
to
the
corporate
folks
to
say
that
hey,
we
need
this
budget
for
running
some
in
a
sauce
because
it
gives
us
x
amount
of
you
know,
benefits
they
are
going
to
be
that
voice.
So
having
that
well
thought
all
round
complete
or
sport
team
is
going
to
be
really
really
very
important.
I
would
say.
C
B
We
had
one
person
that
mentioned
the
innersourcecommons.org.
I
think
that
was
vincent
and
so
yeah
vincent
thanks
for
throwing
that
into
the
chat.
So
the
innersourcecommons.org
is
a
place
to
go
to
be
able
to
see
a
community
of
people
that
are
trying
to
implement
inner
source
or
have
successfully
implemented
inner
source
at
their
company
or
previous
company.
So
these
are
the
practitioners
that
are
doing
this.
It's
a
great
resource.
They've
got
all
these
sort
of
like
patterns
and
stuff
like.
B
If
you
see
this
pattern
in
your
organization,
maybe
you
should
try
like
this
solution
to
make
inner
source
work
and
or
to
have
inner
source,
create
a
bigger
impact
so
yeah
that
one.
I
just
wanted
to
call
that
out
and
say
that
that
that's
a
super
good
resource.
So
thanks
for
putting
that
in
there
cool.
D
B
Yeah
so
in
terms
of
like,
if
your
organization
says,
okay,
yeah,
I'm
ready
to
adopt
inner
source,
what
are
what
are
my
first
steps?
You
know,
I,
I
think,
there's
a
couple
of
things
that
you
gotta
sort
of
get
a
handle
on
like.
Why
are
you
doing
inner
source?
Why
is
your
company
think
this
is
going
to
be
a
value?
Is
it
for
engineering
efficiency?
Is
it
for
creating
communities
among
your
developers
to
connect
people
and
create
retention
like
really
outlining
those
goals,
like
you
mentioned
from.
C
B
And
writing
those
down
and
saying
okay.
This
is
why
we're
doing
it
so
that,
if
those
are
your
convictions
about
why
you're
doing
inner
source,
you
can
keep
those
and
maintain
those
throughout
the
the
process
and
sort
of
reflect
and
say.
Okay,
is
this
adding
to
my
goal
versus
you
know?
Inner
source
can
mean
a
lot
of
things
to
a
lot
of
different
people,
just
like
open
source,
and
so
you
don't
want
such
a
nebulous.
B
You
know
general
goal,
so
there's
that
strategy
piece
and
then
another
thing
to
do
in
terms
of
first
steps
is
really
identifying
what
projects
or
opportunities
there
are
to
be
shared
so
like.
If
I
am
at
a
you,
know,
financial
banking
company,
or
something
like
that,
and
I
I
look
around
and
I
go
well
gosh.
You
know
between
the
different
products
that
we
offer.
There's
just
there's,
not
a
lot
of
overlap.
There's
not
a
lot
of
the
same
languages
or
technologies
being
used
like
what.
B
What
am
I
even
gonna
inner
source
like
it's
a
great
idea,
but
I
don't
have
any
projects
that
are
really
good
potential.
You
know,
maybe
you
look
at
something
like
in
infrastructure
like
a
shared
ci
pipeline
right,
so
everybody's
got
to
run
tests
everybody's
got
to
check
their
code
quality,
the
security
and
things
like
that
in
their
pipeline.
So
you
know,
could
you
build
a
ci
pipeline?
That
is
a
base
pipeline
that
you
can
reuse?
You
know
it
doesn't
matter
your
technology,
github
actions,
lincoln's.
B
Whatever
you
know
you
can
you
can
create
that
workflow
share
that
that
workflow
with
the
other
product
members
on
your
on
your
team
on
different
teams,
different
products
and
say
hey,
this
is
what
we
use
and
maybe
they
have
an
improvement.
Maybe
they
say
oh
yeah,
we
do
something
similar
to
that,
but
we
also
you
know
we
have
a
linter
in
ours
and
we
check
for
style
you
know
and
and
so
that
all
of
our
style
is
really
consistent
and
readable
too.
Okay,
yeah.
B
I
think
I
want
to
add
that
back
in
you
know,
that's
the
beginnings
of
an
inner
source
project
with
the
beginnings
of
contribution
across
multiple
teams.
You
see
the
values
starting
to
build
up
here
and
and
the
the
quality
of
the
piece
of
software
that
you're
reusing
also
increases
there.
So
that's
a
good
way,
I
think,
to
see
some
of
the
the
starters
of
of
the
actual
tangible
benefits
and
then,
like
we've,
been
mentioning.
B
We've
been
talking
about
like
inner
source
champions,
folks
that
working
at
ospo
or
leadership
sponsors
for
this
really
identifying
those
books
are
write
that
down.
You
know
when
I
say,
write
this
down.
I
just
start
a
repo
in
your
organization
called
inner
source
and
just
like
start
putting
the
stuff
in
there
and
making
it
visible
to
other
folks.
B
So
you
can
start
to
start
to
build
this
community
of
people
that
care
about
the
goal
that
you're
trying
to
accomplish
here
and
then
I
think,
as
you
start
to
grow
in
maturity
like
new
problems
start
to
arise
like
okay,
so
you
figured
out
your
first
couple
of
projects.
That's
great
once
you've
got
you
know,
maybe
five,
six,
ten,
twenty
projects?
B
Okay!
Well
now!
This
is
not
just
like
a
word
of
mouth
thing.
We
can
tell
everybody
about
that.
One
project
that
everyone's
sharing:
how
do
we
discover
what
all
of
these
projects
are
and-
and
so
new
problems
start
to
arise
that
you
have
to
try
and
figure
out
how
to
do
that,
and
so
there
there
may
be
an
upcoming
session
on
on
talking
about
discoverability
and
finding
inner
source
projects.
So
I
guess
stay
tuned
for
that.
The.
B
Probably
not
supposed
to
leak
this
stuff
out,
but
there
it
is,
and
then
yeah
just
the
other
thing
that
I
would
mention
is
making
sure
that
the
transparency
that
you
were
talking
about
is
compatible
with
your
organization
right.
So
I've
worked
with
some
governments
and
government
agencies
that
want
to
do
intersourcing,
like
they're,
very
locked
down
very
secure
on
things,
and
so,
but
even
in
their
organization
they
can
see
value
in
sharing
with
specific
groups
at
an
appropriate
time.
B
B
Using
the
same
source,
control
tool
or
everybody
has
access
to
log
in
to
see
where
code
is,
but
you
know,
maybe
they
don't
have
permissions
to
see
all
the
code,
but
they
have
permissions
to
see
the
code.
That's
acceptable
for
anyone
to
see
those
types
of
activities
of
just
lowering
that
barrier
to
collaborate
is
going
to
be
really
important.
B
B
Yeah,
I
I
guess
the
other
thing
that
I
didn't
mention
was
the
communications,
so
you
should
probably
be
talking
about
this.
You
know
you
should
probably
be
sharing
the
fact
that
you're
working
on
in
your
source
that
you're
starting
these
shared
projects,
I
think,
if
you
try
to
imagine
a
organization
that
does
intersource
really
well,
but
nobody
talks
about
it.
Nobody
shares
about
inner
source.
B
Then
how
does
anyone
know
about
it
right?
So
it's
just
like
it's
an
incompatible
vision.
So
so
you
have
to
sort
of
put
your
neck
out
there,
a
little
bit
be
a
little
bit
vulnerable
and
say:
hey
we're
doing
this
sharing
thing
we're
trying
to
do
it
in
a
very
secure
and
in
a
in
a
way
that's
going
to
impact
the
business
in
a
positive
way,
not
create.
You
know,
just
massive
amounts
of
risk
with
no
benefit
or
anything
so
yeah.
C
A
B
B
You
know
how:
how
do
I
go
about
an
inner
source
initiative
where
I
can
like
measure
some
success
criteria
like
maybe
my
leadership
sponsor,
wants
to
see
an
excel
spreadsheet
with
you
know
three
to
five
bullets
on
it
that
are
either
red
or
green,
and
you
know
want
to
status
update
every
month
like
what
what's
the
right
things
to
to
to
set
as
our
like
success
criteria.
Or
what
do
we
measure
when
we're
trying
to
set
up
metrics
for
like
inner
source.
D
For
example,
if
you
want
to
measure
developer
efficiency,
or
you
want
to
measure
the
amount
of
reuse
of
projects
that
can
translate
or
compute
back
into
a
feature
velocity
on
how
fast
you
release
features
or
you
release
your
your
new
versions
of
the
product
right.
So
if
you
have
a
greater
goal-
and
you
could
let's
say,
make
it
more
granular-
you
will
be
able
to
come
up
with
a
matrix
that
is
aligned
very
specific
to
why
you
want
to
be
doing
insults
in
the
first
place
right.
So.
C
D
Even
if
you
can
achieve
10
or
less
than
10
percent
of
contribution
for
your
department's
project
from
and
different
department,
that
is
already
a
great
win,
because
every
department
is
going
to
have
their
own
deliverables
and
backlog
to
burn
and
deliver.
But
achieving
that
almost
10
percent
or
or
x
percentage
contribution
from
another
team
is
already
considered
a
win.
D
Time
as
as
the
departments
and
teams
mature
with
the
inner
source,
culture
and
journey,
that
number
will
organically
grow
right
and
that
becomes
the
organization's
culture
and
on
on
how
they
share,
how
they
contribute
and
and
learn
from
each
other's
skill
set
right.
So
I
would
say,
as
a
starter,
a
good
matrix
to
consider
would
be
how
much
of
collaboration
is
happening
between
the
groups
or
the
departments.
D
So
if
we
can
quantify
that
to
say
that
I've
received
x,
number
of
pull
requests
from
team
members
who
are
not
direct
team
teammates,
that's
a
good
number
to
quantify,
keeping
track
of
number
of
features
that
we
are
releasing
because
you
know
if,
if
before
doing
inner
sauce,
we
were
releasing
three
features
in
a
quarter
and
because
we
did
in
a
sauce.
After
that,
we
were
able
to
leverage
or
crowdsource
the
skills
that
required
to
burn
the
backlog.
D
D
So
let's
say
if
you
launch
like
a
listing
or
a
page
where
all
of
the
inner
source
projects
are
listed,
if
the
number
of
the
project
is
also
increasing,
that's
also
a
good
positive
indicator
to
show
that
any
efforts
that
you're
doing
is
headed
in
the
right
direction.
Of
course,
these
are
high
level
groups.
You
can
always,
you
know,
revise
and
see
how
you
are.
You
know
progressing.
D
Maybe
that's
not
a
great
example,
but
at
least
you
have
the
conversion
in
that
sense
right
and
also
like
number
of
features.
We
didn't
reuse
code,
so
we
used
whatever
time
that
developers
had.
Instead
of
reinventing
the
wheel,
we
were
churning
out
more
new
features
at
the
same
amount
of
time.
So
those.
C
D
Good
indicators
of
matrix
that
we
could
use,
of
course,
to
keep
track
of
the
matrix.
You
need
like
a
a
checklist
or
maybe
like
a
starting
checklist
right.
So
I
would
also
share
that
you
know.
Number
of
issues
being
open
in
a
repository
is
also
a
good
thing,
because
it's
all
about
the
data
and
how
you
massage
the
data
and
make
meaningful
decisions
out
of
those
data.
So.
A
D
Example,
let's
say
if
a
department
is
sorry
if
a
team
is
building
a
call
component,
a
call
library
and
a
lot
of
different
teams
are
actually
opening
pull
requires
or
opening
up
an
issue
saying
that
this
particular
feature
is
buggy
all,
although
it
sounds
negative,
but
it
also
sends
a
message
to
say
that
people
are
relying
on
that
system.
People
are
relying
feature
and
there
is
traction
right.
So
it's.
A
B
D
Yes
and
one
more
thing
about
matrix,
I
agree
it's
a
very
dangerous
thing
because
it
also
grows
it's
a
living
thing
with
the
project,
because
a
project
that's
newly
being
started.
You
will
have
a
lot
of
contribution
and
you
will
see
numbers
growing
up
and
and
and
the
volume
is
adding
on,
but
as
the
project
matures
and
and
it's
more
stable
and
it
gets
into
a
maintenance
mode.
D
Those
number
need
to
be
translated
differently
because
you're
not
going
to
get
a
lot
of
contribution
because
it's
already
stable
it's
doing
what
it's
supposed
to
do
in
a
very
stable
way
right.
So
you
need
to
always
revisit
at
specific
milestones
and
define
whether
the
matrix
that
you
have
specified
is
it
still
valid?
Is
it
still
bring
the
right
meaning
to
say
that?
Are
you
doing
any
source
the
right
way
or
not?.
B
Yeah
that
makes
me
think
about
at
a
previous
company
that
I
worked
at,
I
did
starting
off
in
engineering.
I
did
a
lot
of
maintenance
work
on
existing
projects
and
they
always
like
label
each
of
the
projects
and
repositories
and
stuff
like
that
either.
This
is
like
a
green
field
project
like
totally
new
exploration
or
it's
a
brownfield
project
where
it's
like
this
is
very
stable.
This
is,
very,
you,
know,
reliable
and
trusted,
and
so
we
sort
of
made
changes
differently
to
those
different
projects,
as
they
were
labeled.
B
That
way,
I
could
see
how
that
would
benefit
in
an
inner
source
context
as
well,
where
you
sort
of
label
like.
Oh,
this
is
a
new
inner
source
project,
lots
of
contributions,
lots
of
unstructured
activity-
and
you
know
direction-
is
still
being
determined
and
things
like
that
and
things
are
moving
quickly,
whereas
maybe
a
project
that
you
know
may
two
of
your
biggest
products
rely
on
which
is
more
stable
and
trusted
like
you,
don't
want
to
make
big
breaking
changes
there
or
anything
like
that,
or
at
least
be
cautious
when
you
do
over
communicate,
yeah.
D
C
B
B
Yeah
yeah
definitely-
and
I
love
that-
because
documentation
is
good
for
it's
good
for
business
and
it's
good
for
the
developer
right,
if
you
think
about
it
from
the
from
the
business
mindset.
Documentation
is
great
because
you
can
put
a
resource
on
a
project
that
they
haven't
seen
before
and
there's
a
great
path
already
laid
out
for
them
to
be
able
to
get
started.
B
Learn
about
the
project,
learn
how
it
works,
because
you
have
all
that
documentation
there
from
the
developer
perspective,
it's
good
because,
when
you're
thrown
on
a
project,
you
know
which
way
is
up
right
and
if
that
project
is
an
inner
source
project,
you
know
it
also
gives
you
more
options
for
mobility
to
move
around
the
company.
Maybe
you
don't
want
to
work
on
your
team
anymore.
You'd
rather
work
on
this
other
team
and
they
use
that
inner
source
project
that
you
know
as
well.
B
So
you
can
sort
of
advertise
yourself
to
that
team.
It's
like
hey
I'd
like
to
do
an
internal
transfer
here,
and
I
actually
already
know
some
of
the
projects
that
and
if
contributed
to
some
of
the
projects
that
you
use
like
that's,
got
to
be
a
pretty
big
gold
star
in
terms
of
for
that
hiring
manager
to
say:
oh,
okay,
yeah,
that's
a
great
head
start.
D
Yeah-
and
I
think
I
would
I
would
say
in
a
source
or
like
the
contribution-
does
not
necessarily
mean
need
to
be
on
code
documentation,
it
could
be
about
knowledge
sharing,
it
could
be
opening
up.
You
know
your
team
to
to
share
how
your
team
has
a
workflow
or
what
is
the
process
that
that
you
know
what
are
the
projects
that
you've
tried?
What
are
the
learning,
so
that
is
also
considered
as
inner
source,
and
it
doesn't
necessarily
need
to
be
around
code,
a
contribution.
B
D
D
B
C
D
B
D
Project
portal,
yeah
yeah
thanks
so
zach
we've
been
speaking
about
a
lot
of
the
items,
and
I
think
it's
only
fitting
that
we
have
like
a
checklist
to
help
folks
who've
been
following
the
the
friendly
banter
that
we
had
going
back
and
forth.
There's
a
lot
of
info.
So
where
can
we
find
this
checklist
or
do
we
have
something
that
we
could
share
with
the
folks
so
that
they
have
a
takeaway
like
you
know?
If
they
want
to
create
a
faq
about
innocence
within
their
organization?
B
Awesome:
okay:
I
see
that
you
folks
can
see
that.
So
what
we're
looking
at
here
is
the
a
repository
that
we've
put
together
and
this
is
public,
so
you
can
take
a
look
at
it.
It's
just
github.com
demo,
dash
days,
slash
inner
source,
dash,
faq
template,
and
so
here
there's
a
a
lot
of
different
resources,
actually
as
well
as
a
github
page.
So
the
idea
is
is
that
you
could
take
this
fill
out
some
of
the
content,
I'm
just
going
to
put
up
the
github
page
that
this
generates
here.
B
B
D
D
C
D
Yeah,
so
we've
got
the
maturity
assessment
in
terms
of
what
are
your
strategies
that
you
currently
have.
What
are
the
manifesto
components
so
meaning?
What
do
you
want
to
include
as
bullet
points
in
terms
of
what
this
temp,
what
this
vision
or
strategy
of
inner
source
mean
and
trying
to
make
in
our
regional
investment
case
where
like?
If
we
do
inner
source,
we
should
be
able
to
achieve
x,
amount
of
benefits
and
so
on
right
and
then
I've
also
included
a
bit
of
inner
source
workflow.
D
So
this
is
more
like
establishing
workflows
on
how
you
would
open
in
a
source
your
projects.
How
can
you
contribute
to
a
different
pro
department,
a
different
teams
project,
as
well
as,
if
you're
planning
to
launch
an
inner
source
repository
on
source
projects?
What
you
need
to
consider
and
think
of
right
and
then
under
monitoring
the
inner
source
initiative?
D
Again,
there's
some
good
further
reading.
I
did
not
explicitly
put
in
tools
or
matrix,
because
it's
going
to
be
very
specific
to
your
business
goals
and
your
organization
beyond
that.
I
think
I've
also
put
in
like
paying
it
forward
because
it
would
be
really
cool
for
you,
folks
or
your
organization,
your
enterprise,
to
share
your
inner
source
journey,
publish
your
blog
get.
You
know,
speak
with
your
marketing
team,
speak
with
your
branding
team
and
and
and
share
your
journey
share
your
knowledge
because
we're
all
in
this
together
right.
D
B
Cool
awesome:
well
thanks
for
thanks
for
sharing
that
from
I'm
thinking
back
to
the
different
times
that
I've
actually
helped
folks
implement
inner
source
in
their
company,
and
this
template
really
hits
on
a
lot
of
the
points
of
sort
of
like
okay.
Well,
the
business
leadership
came
back
to
us
and
said:
what's
the
roi
on
this
like?
Why
are
we
going
to
invest
time
and
money
into
this
so
yeah?
It
looks
like
we
also
have
another
message
in
the
chat
from
from
daryl
about
this
being
really
timely.
Yeah.
B
Yeah
yeah
defining
strategy
and
building
out
that
inner
source
tooling,
is
really
important
and
again
it's
so
much
easier.
If
we
just
do
that
together,
the
inner
source
details
of
your
projects
can
look
so
different
from
organization
to
organization,
but
how
you
run
inner
source
at
an
organization
can
actually
be
really
similar.
So
those
are
opportunities
for
open
sourcing
things
and,
like
we
had
mentioned,
as
well
as
in
the
chat
as
well
as
in
the
repo
there's
the
innersourcecommons.org
as
well.
B
B
So
we've
got
a
professional
services
organization,
prem
and
I
are
both
a
part
of,
and
so,
if
you'd
like
folks
like
us
to
help
out-
or
you
have
any
questions
for
sales
about
like
github,
maybe
you
guys
are
on
a
different
platform
and
you'd
like
to
like
fork
these
repos
and
use
github
pages
like
we
talked
about
today,
there's
a
qr
code
actually
down
the
at
least
on
my
screen.
It's
the
bottom
left
hand
corner.
B
You
can
open
up
your
camera
app
with
your
phone
and
take
a
picture
that
will
take
you
to
the
website
to
be
able
to
get
in
contact
with
somebody
that
can
do
a
demo
for
you
of
kind
of
what
github
has
to
offer.
If
that's
something
that
you're
interested
in
there's,
obviously
no
no
obligation
or
anything.
We
just
thank
you
guys
for
joining
us
today
for
being
able
to
talk
about
inner
source.
It's
it's
a
topic
that
I'm
really
passionate
about.
B
D
B
Yeah,
so
we've
also
teased
several
times
as
prompted
in
the
chat
about
what's
coming
up.
Next,
so
do
check
out
our
github
linkedin
events
page,
and
you
can
actually
just
go
ahead
and
say
that
you're
going
to
attend
and
it'll
remind
you
about
our
next
session.
I
believe
going
on
next
friday,
also
about
inner
source,
so
yeah.