►
From YouTube: Consumers To Contributors: Open Source As a Competitive Advantage - Brendan O'Leary, GitLab
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Consumers To Contributors: Open Source As a Competitive Advantage - Brendan O'Leary, GitLab
Speakers: Brendan O'Leary
As open source software has eaten the software world, it can be your biggest asset or cause your biggest problems. Most of the time, we consume open source without really considering the long-term impact on our business. So why would a business, enterprise, or organization decide to become a Contributor instead of just a Consumer? In this talk, we'll look at some of the biggest success stories in enterprise open source software partnerships and some of the cautionary tales. The more an organization is involved in co-creating the open source packages they use, the more both the organization and the open source project benefit. This session is for everyone: open source maintainers, OSPO leaders, or open source advocates in large enterprises. At the end of our session, you'll be able to articulate the tangible and emergent benefits organizations and enterprises gain when they stop just consuming open source software and instead embrace "Everyone can contribute."
A
Yet
that's
not
often
how
humans
relationship
with
the
natural
world
works
right
frequently,
it's
all
taken
not
a
whole
lot
of
giving
we're
slowly
learning
as
a
species
how
to
be
better
at
that?
How
to
be
better
custodians
of
this.
You
know
one
planet
we
have
together,
but
even
in
relatively
long-lived
human
practices,
we
can
see
this
somewhat
one-sided
relationship
right
does.
A
If
you
look
at
the
domestication
of
animals
or
plants
for
food
or
companionship,
those
are
often
pretty
one-sided,
if
not
entirely
one-sided,
but
what
if
I
told
you
didn't,
have
to
be
that
way.
There
are
actual
examples
of
mutualism,
which
is
symbiosis,
where
both
humans
and
wild
animals
benefit
from
one
another.
We
all
remember
the
word
symbiosis
from
biology.
Yes,
there's
three
types
of
symbiosis,
parasitic
kamalism
and
mutualism,
and
let's
talk
about
those
so
parasitic
we're
familiar
with
right.
This
is
where
one
species
actively
harms
another
to
gain,
something
for
them.
A
The
parasites
benefiting
while
the
host
is
being
harmed
and
actually
almost
40
percent
of
animal
species
are
parasites.
It's
a
very
effective
way
to
run
a
species
if
you're
looking
to
start
a
new
one
and
the
average
mammal
species
like
us
is
host
to
dozens
of
parasites
at
any
given
time,
but
you
can
also
have
relationships
where
one
organism
benefits
and
the
other
is
not
really
significantly
harmed
or
helped.
A
This
often
involves
an
organism
using
another
one
for
transportation
or
for
housing
right,
like
think
about
hermit
crabs
using
the
shells
from
another
animal
that
they've
discarded
to
protect
their
own
bodies.
This
is
a
long
relationship
between,
but
the
third
type
is
a
long-term
relationship
between
two
individuals
of
different
species
were
both
benefit
and
that's
called
mutualism,
and
the
classic
example
here
is
a
clownfish
right.
The
clownfish
lived
inside
the
tentacles
of
an
enemy
I
have
four
small
children,
so
I'm
very
familiar
with
clownfish
from
Nemo.
A
The
anatomy
protects
the
fish
with
its
stinging
tentacles
that
the
fish
is
immune
to.
It
has
a
special
coating
for
that
and
the
clownfish
actually
protects
the
anemone
from
many
predators
that
would
otherwise
try
to
eat
it
and
I
think
if
you're
sitting
here,
it's
probably
hard
for
you
to
think
of
a
pure
Mutual
relationship
between
our
own
species
and
a
wild
animal.
But
there
are
document
documented
cases
of
this
and
they
go
back
a
really
long
time.
A
It's
now
called
appropriately
the
honey
guide
and
the
Honey
Hunters
have
a
special
call
that
they
make
I'm
not
going
to
attempt
it
and
I
couldn't
find
audio
to
play
for
y'all,
but
there's
a
call
that
the
birds
recognize
and
the
birds
then
will
guide
Hunters
to
beehives
right
and
the
humans
can
then
use
smoke
and
tools
to
subdue
the
bees,
get
the
honey
out
and
the
and
the
Honey
guides,
love
to
then
eat
the
wax.
That's
inside
the
hive
and
without
the
human
helpers.
The
honey
guides
would
be
attacked
by
the
bees.
A
If
they
tried
to
do
this
right
and
without
the
honey
guide
guides,
the
human
Hunters
actually
have
a
harder
time
finding
Venus
when
they
work
with
a
honey
guide,
their
odds
of
finding
a
BNS
are
increased
by
60
percent
and
in
fact,
in
this
area
that
was
studied
by
Dr
spots,
good
as
she's
credited
down
here,
I
actually
have
to
email
her
to
ask
to
use
this
picture.
She's
an
Australian
zoologist
in
in
this
area
was
in
the
Nissan
National
Reserve
in
Mozambique.
A
So
what
does
that
mean
for
us
today
well
to
understand
that
I
think
we
have
to
understand
where
we
are
at
with
the
common
good
that
we
all
use
today
in
our
day-to-day
jobs
and
that's
open
source
software?
We've
heard
often
that
software
is
eating
the
world,
but
that's
actually
a
decade
plus
old.
At
this
point
and
I
think
it's
now
clear
that
open
source
software
is
eating.
The
world
studies
vary
on
this
point,
but
somewhere
between
30
to
50
percent
of
the
total
software.
A
That's
shipped
in
proprietary
software
is
actually
open
source
code,
and
so,
when
Mark
Andreessen
made
this
famous
Proclamation
about
software
eating
the
world,
he
was
trying
to
wake
businesses
up
to
the
imperative.
That
was
in
front
of
them.
The
reality
that
digital
transformation
was
coming
to
every
industry
that
every
company
was
going
to
have
to
become
a
software
company.
A
And
all
of
those
of
us
who
are
here
who
may
not
be
you,
know
CTO
or
CIO
of
their
organization,
but
understand
the
growth
of
Open
Source
have
to
act
like
canaries
in
our
company's
coal
mines
right.
Another
bird
analogy,
educating
and
alerting
our
leadership
of
both
the
opportunity
and
the
risks
involved
that
with
open
source
eating
the
world,
and
so
that's
what
we're
going
to
talk
about
today,
not
just
Birds
I
promise
and
we're
going
to
ask
I'm
going
to
want
to
find
out
how
we
can
be
stewards
of
this
new
era.
A
How
can
we
enable
our
companies
to
move
from
being
mere
consumers
of
Open
Source
to
being
contributors
to
open
source
and
the
community
is
around
it
and
not
just
because
it's
the
right
thing
to
do
or
to
check
some
corporate
stewardship
box,
but
because
it
actually
makes
business
sense
and
I
probably
hear
a
lot
of
you
asking
why
now
Brendan
open
source
has
been
around
a
long
time,
but
I
think
right
now
represents
a
clear
inflection
point
towards
open
source
eating
the
world
right.
We've
seen
Industries
get
massively
disrupted
by
software.
A
First,
companies
I
think
we're
going
to
see
a
second
or
massive
round
of
distribute
of
disruption
from
open
source
first
companies,
and
why
do
I
think
that
let's
look
at
some
data
so
in
a
2022
state
of
Open
Source
survey,
respondents
overwhelmingly
noted
that
they
were
increasing
the
use
of
Open
Source
software
at
their
organizations.
But
if
you
look
deeper
into
the
house
and
whys
in
that
survey,
some
interesting
patterns
emerged.
For
example,
when
we
they
asked
organizations
the
reasons
for
choosing
open
source.
A
We
might
expect
right
number
one
reason:
cost
savings
right,
nope
number
one
reason
was
actually
access
to
innovation,
as
every
company
has
become
a
software
company.
This
becomes
the
place
where
businesses
and
Enterprises
compete.
Thus,
whoever
can
innovate
faster,
more
securely,
provide
more
value
to
their
customers
through
the
software
can
succeed
and
win,
and
where
does
much?
If
not
the
majority
of
that
Innovation
happen
today
what
happens
in
open
source?
And
so
it's
critical
businesses
have
find
a
way
to
be
able
to
access
these
Innovations.
A
But
it's
not
always
easy
right.
There's
many
barriers
to
Enterprises,
large
and
small
when
it
comes
to
utilizing
and
contributing
to
open
source
software
and
one
of
the
main
ones
we
might
think
of
off
the
top
of
our
head
is
well
there's
some
restrictive
licenses,
maybe
attached
to
certain
open
source
right.
You
know
copy
left
license
an
Enterprise
can
be
wary
of
there's.
A
You
know
anti-competitive
Clauses
in
many
open
source
licenses
and
some
licenses
that
are
open
source
adjacent
right
and
that's
going
to
scare
off
risk-averse
for
firms,
but
that
was
not
listed
as
the
number
one
barrier
to
adopting
open
source
software
and
and
its
usage.
It
was
a
lack
of
internal
skills
to
test
build,
integrate,
maintain
and
support
the
open
source
libraries
that
they
want
to
use.
That
was
identified
as
the
most
significant
barrier
to
open
source
adoption,
and
you
know,
we've
seen
that
they
desperately
do
want
to
that
access
to
open
source.
A
A
This
has
been
a
traditional
model
of
monetizing
Open
Source,
but
not
all
open
source
projects
have
this
model
or
even
have
a
company
behind
them
or
don't
have
a
company
behind
them
yet,
and
businesses
might
have
like
to
have
Enterprise
support,
but
that
was
not
the
biggest
challenge
to
surprising
to
supporting
their
open
source
programs
that
they
listed.
Instead
again,
they
identified
an
internal
skills
Gap,
a
lack
of
personal
experience
and
proficiency
with
the
open
source
tools.
A
They're
utilizing
has
the
most
major
challenge
when
it
comes
to
supporting
these
open
source
initiatives,
and
so
what
does
that
data?
Tell
us
I
think
it
tells
us
it's
clear:
it's
not
just
a
software
problem.
It's
not
a
problem
for
a
company
to
throw
a
few
charity
dollars
at
I.
Think
that
even
a
well-placed,
well-funded,
well-regarded,
ospo
or
open
source
program
office
probably
isn't
enough
to
overcome
the
challenges
that
these
organizations
face.
A
The
only
way
to
address
these
challenges
is
head
on
and
decide
that
we're
going
to
take
a
step
back,
we're
going
to
take
a
more
comprehensive
look
at
the
problem
and
declare
that
we
need
a
business
case
for
contributing
to
open
source,
so
contributing
to
open
source
is
directly
one
of
the
best
ways
that
we
can
overcome.
These
big
number
one
challenges
that
we
just
looked
at
it
needs.
You
know
we
want
to
make
sure
that
our
organization
has
access
to
the
latest
Innovations.
A
We
want
to
build
internal
skills
to
integrate
open
source
into
our
business,
and
we
want
to
attract
and
retain
talent
that
have
personal
experience
and
Proficiency
in
emerging
in
a
central,
open
source,
Technologies,
and
so
when
I
was
thinking
about
that
for
more
of
a
business
perspective.
It
got
me
thinking
about
my
degree
a
long
long
time
ago
way
back
thankfully
well
before
social
media
was
quite
as
prevalent
as
it
was
today.
A
I
attended
the
University
of
Maryland
and
there's
a
fabulous
computer
science
program
there,
but
I
regret
to
inform
you
that
I
do
not
in
fact
have
a
computer
science
degree.
I
have
and
I'm
glad
you're
all
sitting
down,
because
this
may
come
to
a
shock
to
the
engineers
in
the
room.
I
have
a
business
degree.
I
know
it's
okay,
we
can
still
be
friends
and
one
of
the
classic
tools
you
talk
about
in
business
school
is
something
called
a
SWOT
analysis
right,
so
s-w-o-t
and
that
stands
for
strengths,
weaknesses,
opportunities
and
threats.
A
And
so,
if
we
think
about
the
problem
at
hand,
I
kind
of
put
together
this
SWOT
analysis
and
and
what
can
we
say,
maybe
about
the
average
business
that
we
all
work
for
in
in
the
room?
Well,
I
think
it's
clear
that
we
all
work
for
companies
with
software
organizations
right
we're
all
in
software
together
and
these
organizations
definitely
see
the
need
for
open
source
adoption.
Heck
I
mean
they
probably
sent
you
here,
because
they
understand
that
right.
But
where
are
we
weak
again?
A
A
A
lot
we've
talked
about
a
lot
this
week.
The
lack
of
understanding
and
proficiency
with
this
is
a
critical
risk
for
the
security
of
and
knowledge
of
your
supply
chain
right.
No
one
here
in
Detroit
that
manufactures
cars
would
tell
you
that
a
supply
chain
doesn't
matter,
and
you
don't
have
to
really
think
about
it
right.
They
understand
how
critical
supply
chain
is
to
the
product
that
you
actually
produce.
A
Well,
what's
the
software
supply
chain,
it's
open
source
software,
and
so,
if
we
think
about
that
chart,
I
think
we
can
come
to
an
even
higher
understanding
of
The
Balancing
Act.
Here,
that's
really
critical
for
businesses
cap,
you
know
what
does
a
business
think
about
every
day,
capture
value
and
reduce
risk
right
and
there's
values
not
only
in
the
software
we're
making,
but
for
the
company
in
the
organization
itself
right.
A
But
next
I
want
to
talk
about
practically
how
we
can
think
about
taking
our
organizations
from
where
we
are
today
using
open
source
and
unsure
of
the
next
step
to
where
we
want
to
be.
This
sculpture
is
actually
the
Spirit
of
Detroit
and
the
artist
has
a
family
there
on
the
right
to
symbolize
human
relationships
with
one
another.
So
how
can
we
unlock
this
Spirit
of
cooperation
in
our
own
organizations?
A
I?
Think.
The
only
answer
is
to
move
from
consumers
of
Open
Source
all
the
way
to
contributors,
and
that
seems
like
a
simple
thing
to
say,
but
I
think
it's
a
rather
long
road,
especially
for
Enterprises.
You
know
many
organizations
today
are
either
implicitly
or
explicitly,
okay
with
being
only
consumers
of
Open
Source,
that's
open
source.
Well,
that's
something!
A
That's
made
by
them
right,
but
at
the
very
core
of
Open
Source
is
the
idea
that
anyone
can
contribute
right,
and
this
is
the
opposite
Viewpoint
of
the
world
of
US
versus
them
and
so
to
get
there
as
organizations.
We
need
to
take
steps,
some
small
and
some
large
to
make
a
conscious
choice
to
change
that
viewpoint,
and
the
first
step
is
to
move
from
a
simple
consumer
of
Open
Source
to
be
customers
of
Open
Source.
A
A
It
would
be
best
if
you
looked
at
you
know
putting
code
and
time
and
money
into
those
projects
in
the
form
of
contributions
and
paid
staff
on
your
team,
whose
primary
focus
is
understanding
the
needs
of
the
business
and
how
they
relate
to
these
critical
path.
Projects
and
financial
support
for
infrastructure
and
other
needs
is
also
a
way
to
align
yourself
as
more
than
just
a
consumer
but
more
of
a
customer,
but
once
we've
become
customers,
the
natural
question
becomes
at
least
from
a
business
perspective.
A
How
do
we
ensure
low
lower
total
cost
of
ownership
for
this?
And
how
do
we
extend
the
competitive
advantage?
That's
open
source
has
allowed
us
to
build,
that
is
by
taking
the
next
leap
and
to
move
from
a
customer
of
the
technology
to
a
contributor.
This
means
finding
ways
to
incentivize
and
reward
open
source
contributions
and
hiring
even
more
folks
to
focus
on
maintaining
or
contributing
to
open
source,
but
just,
as
importantly,
I
think,
it
involves
building
relationships
with
the
open
source
projects
and
communities
that
you're
engaged
in
this
allows
a
connection
to
move
Beyond.
A
This
transactional
customer
transaction-
and
you
know
Financial
relationship
to
one
of
mutual
respect
that
then,
would
help
align
the
community
and
the
company's
goals
together
and
then
providing
space
for
roles
outside
of
just
straight
Finance
or
software.
Engineering
right
is
going
to
help
projects.
Projects
all
have
needs
around
ux
and
documentation
and
design
and
security
other
devops
tasks
that
will
help
build
sustainability
into
these
projects,
and
so
each
of
these
steps
build
on
one
another
move
from
consumer
to
go
from
sorry
consumer
to
customer.
We've
got
to
understand
the
supply
chain.
A
We've
got
to
understand
what
tools
we're
using
our
vendors
are
using,
and
then
we
have
to
put
our
money
where
our
mouth
is
and
contribute
financially
to
those
projects
either
directly
and
indirectly,
but
I
don't
think
you
can
stop
there.
You
have
to
move
from
Cut
consumers
all
the
way
to
contributors
that
involves
building
relationships.
Those
relationships
are
one
of
the
most
critical
parts
of
our
entire
open
source
ecosystem.
Right.
A
And
so
this
is
something
that's
critical
to
the
longevity
of
those
projects.
But
if
we're
building
products
on
top
of
them,
it's
also
essential
and
critical
to
the
longevity
of
our
own
products
and
what
we're
providing
to
our
customer
and
okay.
A
lot
of
this
maybe
have
up
until
now
been
a
little
bit
of
preaching
to
the
choir
right.
A
And
so
let's
talk
about
that.
I
think
individual
contributors
have
a
much
more
ability
to
influence
policy
on
open
source
than
you
think
at
first.
You
know.
On
the
one
hand,
they
may
be
closer
to
the
reality
of
an
organization's
use
of
Open
Source
dependencies
than
anyone
else
in
the
organization
right
they
understand,
you
know
what
we're
using
and
simply
enumerating
those
dependencies
is
a
significant
First,
Step
you'll
likely
need
to
raise
awareness
throughout
your
organization
about
just
how
much
your
team
relies
on
these
tools.
A
Once
that's
complete
understanding,
the
risk
is
often
a
fundamental
way
to
get
the
attention
of
folks
that
you
needed
throughout
the
business.
What
would
have
be
the
business
impact
to
your
organization
if
a
given
Library
just
goes
away
tomorrow?
If
the
answer
is
well,
we
wouldn't
be
able
to
ship
software
until
it
was
fixed
or
well.
Some
are
some
of
our
software
would
just
stop
working,
that's
very
substantial
in
terms
of
impact
and
a
huge
risk
your
business
must
address.
A
You
can
also
encourage
and
support
the
open
source
values
that
we
all
know
and
discuss,
especially
results,
oriented
thinking
and
transparency.
Modeling.
These
behaviors
can
show
others
how
valuable
they
are
and
values
like
those
seem
like
a
simple
thing,
but
I
think
they're
really
essential
and
can
have
an
everlasting
impact
on
your
organization.
A
A
Their
collaboration
results,
efficiency,
diversity,
inclusion
and
belonging
iteration
and
transparency
having
those
values
at
the
core
of
what
we
do
has
not
only
been
a
benefit
to
git
lab
the
open
source
project,
but
to
gitlab
the
company
as
well
and
so
I.
Think,
though,
I
would
attribute
our
success
both
on
the
project
side
and
on
the
company's
side
to
those
values,
and
so
what?
If
you
are
a
business
or
technology
leader,
because
there
might
be
a
few
in
the
in
the
room
right?
A
Well,
firstly,
I
think
you
have
to
buy
into
what
I've
been
saying
so
far.
You
have
to
see
open
source
as
an
investment,
just
like
any
other
other
investment
along
your
value
chain
as
a
well
as
a
place
that
you
must
and
can
achieve
risk
mitigation.
None
of
us
want
to
receive.
You
know
a
call
from
our
CIO
or
our
CEO
in
the
morning
and
they're
saying:
hey
I
was
just
watching
CNN
and
I
heard
about
this
thing.
A
Called
Apache
struts
like
what's
a
struts
and
and
do
we
have
it
are
we
vulnerable,
but
just
as
importantly,
you
have
to
quantify
the
relationship.
This
is
really
important
to
the
organization's
goals
right
down
to
revenue.
If
you
aren't
careful
at
the
beginning
to
make
this
connection,
showing
that
there's
value
of
to
this
work
is
always
going
to
be
an
uphill
battle.
A
You
have
to
stop
and
ask
yourself:
why
would
you
not
want
the
maintainer
for
a
significant
open
source
project
that
you
use
working
for
you?
Why
would
you
not
want
that
kind
of
that
kind
of
town
is
very
hard
to
come
by
and
even
harder
to
retain.
If
your
job
is
to
ensure
that
you
have
the
best
team,
then
you
have
to
open
understand
how
open
source
contribution
relates
to
your
team
members
and,
lastly,
because
I'm
sure
there's
also
a
number
of
ospo
leaders.
A
Here
we
have
to
get
it
into
our
heads
and
the
heads
of
those
we
work
for
that.
Ospos
are
not
just
an
exercise
and
compliance.
A
real
open
source
office
can
Leverage
The
tremendous
power
of
Open
Source
to
add
massive
value
to
the
organization,
and
you've
got
to
be
able
to
articulate
that
vision
and
that
mission
and
all
the
things
we've
discussed
so
far,
so
suppose
you're
able
to
put
in
an
effort
against
these
large
but
attainable
goals.
You
know
how
does
that?
What
does
that?
A
Look
like
I
think
it's
a
matter
of
itemizing
all
the
OS
open
source
that
you
use
in
your
organization
today
be
a
part,
be
it
you
know
a
part
of
your
core
product
or
a
behind
the
scenes.
You
know
part
of
your
devops
processes,
then
identify
which
of
those
ways,
your
business,
you
can
align
your
businesses
goals
with
the
concept
of
being
a
customer
or
a
contributor
to
those
projects.
How
can
you
support
the
sustainability
of
those
projects
and
de-risk
your
own,
your
own
business
and
products
and
I?
A
Unless
you
understand
as
best
as
you
can,
how
open
source
plays
into
and
ties
in
with
things
that
the
business
cares
about
once
you
do,
that,
incentives
will
be
much
easier.
But
unless
you
do
you're
going
to
have
a
really
hard
time
with
incentives-
and
you
know
being
open,
source
contributors
enables
teams
to
be
do
their
best
work
together
to
collaborate
without
boundaries
to
aim
for
and
Achieve
results
together
to
work
efficiently
without
wasted
time
to
bring
together
together,
diverse
skill
sets
and
include
everyone
in
the
process
to
Foster
the
sense
of
belonging.
A
It
reminds
me
of
a
scene
in
the
first
episode
of
Halt
and
Catch
Fire,
which
is
a
drama
about
building
a
company,
a
computer
company
in
the
late
70s
and
early
80s,
there's
a
Visionary,
idealistic
product
manager,
Joe
and
he's
trying
to
convince
this
hardened
engineer
Gordon
to
sign
up
for
what
they're
going
to
build
together.
You
know,
I'm
sure
this
is
not
related
to
any
company
that
actually
existed
if
you
asked
AMC,
but
you
know
either
way
either
way.
A
The
closing
argument
for
this
project
sums
up
nicely
how
I
like
to
think
about
software.
Joe
says:
computers.
Aren't
the
thing
they're
the
thing
that
gets
you
to
the
thing
and
then
later
in
closing
the
series,
another
character
Donna
calls
back
to
that
line
and
adds
the
project
gets
you
to
the
people
and
I
think
that
summarizes
fairly
nicely.
What
makes
open
source
so
special.
A
It
draws
people
in
from
all
over
the
world
to
collaborate
on
the
same
tools
that
we're
then
using
to
build
something
bigger
and
in
this
way,
open
source
allows
us
to
work
together,
not
siled
in
our
own
companies
making
our
own
little
products.
Out
of
you
know,
bubble
gum
and
Bash
scripts
like
so
much
so
many
batch
scripts
right.
It
enables
us
to
bring
to
bear
on
the
problem.
Instead,
all
of
our
collective
experience
and
expertise,
the
project
gets
us
to
the
people,
it's
a
story
of
relationships.
A
Thank
you.
So
much
for
your
time
today,
I'm,
not
the
only
one.
That's
been
talking
about
the
business
case
for
open
source
contributions,
I've
been
compiling
some
resources
at
brendan.fyi,
open
and
I'd
love
for
you
to
check
it
out
and,
more
importantly,
add
things
that
I'm
missing
from
there.
You
can
leave
a
comment
on
it.
You
can
send
me
a
DM
on
Twitter
or
just
tweet
me
at
O'leary
crew,
or
even
it's
on
my
website,
which
is
open
source.
You
can
add
a
merger
Quest
directly
against
the
website.
I'm.
A
They
may
be
linked
there,
if
not
I'll,
add
them
and,
and
so
I
think,
that's
a
great
place
to
start,
because
it's
that's
a
group
where
there's
a
lot
of
Enterprises
that
are
on
that
same
kind
of
Journey
of
like
hey.
We
want
to
do
more
open
source
contributions
and
we
have
things
we
want
to
make
open
source.
How
do
we
get
there.
B
Hey
so
we're
a
service
organization
and
I
can
tell
you
our
c-suite
thinks
of
us
as
a
service
organization,
not
as
a
software
company
right.
So
software
is
a
huge
part
of
what
we
do
and,
as
as
a
in
the
tech
leadership
group
I
feel
like
it
needs
to
be
much
much
bigger
of
an
emphasis
and
like
what
you
what
you're
talking
about
here
seems
like
really
important
to
what
we
need
to
be
striving
towards.
B
A
A
great
question:
I,
don't
have
like
an
example
off
the
top
of
my
head,
but
I'm
I'm
sure
I
could
find
one
and
will,
if
you
want
to
follow
up
with
me
on
Twitter,
but
I
do
think
that
the
line
between
a
services
company
and
a
software
company
is
a
tough
one.
I've
lived
out
myself.
Actually,
my
first
role
at
git
lab
was
building
a
Professional
Services
organization
inside
of
a
software
company,
which
is
like
the
opposite
problem
right,
but
I
do
think
that
you
know
this
competitive
advantage
of
the
expertise
right.
A
Why
do
people
come
to
the
service
service
company
they're,
looking
for
experts
and
so
I
think
that
if
nothing
else,
you
know
building
that
brand
around
being
experts
in
these
tools
that
your
customer
is
going
to
want
necessarily
you
to
bring
in
and
use
and
utilize
and
help
them
figure
out
like
it's
almost
like.
That
would
be
the
number
one
competitive
Advantage
I
would
think
for
a
service
organization
today,
but
I'm
not
in
that
business,
so
maybe
I'm
wrong
and
then
secondly,
I
think
you
know
it's
tough,
because
billable
hours
are
so
nice
right.
A
But
you
know,
efficiency
is
critical
too
and
so
I
think
there's
a
lot
of
efficiencies
to
be
gained
to
say:
hey
we're
gonna.
You
know
Upstream
a
lot
of
this
so
that
we're
not
maintaining
things
internally,
that
aren't
billable
hours
right
and
then
that
will
be
able
to
spend
that
time
instead
on
billable
hours.
Maybe
that
is
a
method.
I
don't
know,
but
I'd
love
to
talk
to
you
about
it.
C
Hey
Brendan,
thanks
for
the
talk
very
helpful,
I'm
curious
to
get
your
thoughts
on
topic
we
get
asked
often,
which
is.
We
have
a
lot
of
large
Enterprise
customers
who
want
to
move
away
from
vendor
login,
which
is
why
they
want
to
get
into
Open,
Standards
or
open
source.
But
do
you
feel
like
open
source
becomes
a
lock-in
in
itself
because
you
can't
get
out
from
there
to
others
and
just
to
follow
up
on
that
is?
Is
it
better
to
talk
about
as
Open
Standards
or
open
source
yeah.
A
Well,
yeah,
so
that
that's
two
different
worlds:
right,
Open,
Standards
and
open
source
I
think
we've
seen
this
move
towards
Open
Standards
in
the
last
few
years.
That
has
been
amazing
and
I'm
really
excited
to
see
that,
because
I
do
think,
that
is
one
way
we
can
de-risk
lock-in
now.
Having
said
that,
you
know
standards
have
come
and
gone
before
that
haven't
solved
that
problem,
so
I,
don't
think
we
can
think
of
that
as
the
only
solution.
I
think
you
also
have
to
have
this.
A
You
know
Innovation
mindset
that
things
are
going
to
change
necessarily
in
the
technology
space.
That's
like
the
Gibbon,
and
so
if
again,
you
have
a
team
who's
familiar
with
that
who's
on
the
front
lines
of
open
sources
on
the
front
lines
of
that
Innovation,
it's
going
to
be
a
lot
smoother
transition,
rather
than
oh
you
wake
up
in
three
years
and
realize
your
whole
stack
is
undo
and
now
you've
got
to
go
hire
our
friend
over
here
to
come
in,
for
you
know,
seven
million
dollars
and
fix
it
all
right.
A
So
yeah
I
think
I
think
that
that
the
talent
and
having
this
kind
of
mindset,
this
Innovation
mindset,
sets
you
up
for
Success
today,
but
also
sets
you
up
for
being
more
agile
and
being
able
to
transform
easier
in
the
future.
I
wish
Open
Standards
would
solve
everything
and
I'm
a
huge
proponent
of
Australian
standards.
Gitlab
is
involved
in
a
lot
of
the
Open
Standards
initiatives.
A
huge
supporter
of
that
I
just
am
a
little
bit
too,
not
quite
optimistic
enough
to
say
that
fixes
every
problem.
D
D
A
Seeing
these
massive
supply
chain
issues
existing
and
as
much
as
I
as
a
software
vendor
would
love
to
sell
you
a
tool
that
fixes
that
problem
I,
don't
again
think
that
there's
one
tool
that
just
solves
that
it's
not
a
problem
that
you
can
only
throw
money
at.
You
also
have
to
be
thinking
differently.
You
have
to
think
about
your
supply
chain
right.
A
D
A
You
know
great
supply
chain
and
just
is
able
to
take
over
the
world
with
it.
I
think
that
that
risk
exists
in
our
businesses
today
and
we're
not
talking
about
it
enough,
because
we
think
of
Open
Source
as
this
free
thing
I'll
give
an
example:
I
was
before
gitlab
I
was
brought
to
a
company
that
was
a
government
contractor.
I
live
in
Maryland,
so
everyone's
a
government
contractor,
and
they
didn't
have
anybody
looking
over
devops
and
that's
what
they
kind
of
brought
me
in
to
do.
A
There's
only
you
know
a
couple
hundred
people
and
I
inherited
like
a
Jenkins
server
right
because
it
was
free
and
they
were
using
it
and
a
whole
bunch
of
other
stuff,
but
specifically
Jenkins
and
early
in
my
tenure,
I
unders
I
came
to
understand
and
then
I
said
in
a
meeting
with
all
the
senior
Executives,
the
CEO
I
said
the
most
expensive
piece
of
software.
We
own
is
called
Jenkins
and
they're
like
what
we
don't
pay
for
Jenkins.
It's
free
right.
We
pay
for
Microsoft
and
we
pay
for
jira
and
we
pay.
A
E
I
just
wanted
to
follow
on
to
that
question.
Specifically
Kristen.
The
CTO
of
the
cncf
has
a
good
blog
post
ways.
Your
company
can
support
and
sustain
open
source,
and
he
quotes
a
Harvard
study
in
that
one.
That
shows
that
businesses
that
actually
contribute
back
to
open
source
can
gain
up
to
a
hundred
percent,
more
productive
value
from
it,
and
so
I
think
that
study
is
linked
on
this
blog
posts.
Yeah,
it's
Frank.