There are four rules to understand when building products out of open source software. A product team (engineering, product management, marketing) needs to understand these rules to participate best in an open source project community and deliver products and services to their customers at the same time. These four rules are the start of all other discussions about the open source product space. The article is posted here: https://opensource.com/business/15/8/open-source-products-four-rules

1. Open
Source
for
Products
in
Four
Rules
(or
Ten
Slides)
Stephen
R.
Walli
@stephenrwalli
Crea>ve
Commons
ABribu>on-­‐ShareAlike
4.0
Interna>onal
License

2. Rule
#1
You
Always
Get
More
Than
You
Give

3. Let’s
Look
at
#1
and
Openstack

4. Let’s
Look
at
#1
and
the
Linux
Kernel

5. Rule
#2
Don’t
Confuse
Projects
with
Products

6. Rule
#3
Don’t
Confuse
Communi>es
with
Customers
Communi>es
and
Customers
live
in
different
value
spaces
(Customers
have
$$$,
Communi>es
have
>me)
Community
Customers
Published
SoZware
Differen>ated
Product
Tradi>onal
Closed
Company
Confusion
Zone

7. Geng
#3
WRONG
7
Customer
Pipeline
R&D
Product
Marke>ng
Messages
$$$
Code,
etc.
Community
The
community
is
NOT
a
part
of
the
pipeline!

8. A
BeBer
Model
for
#3
Community
&
Pipeline
8
Customer
Pipeline
R&D
Product
Marke>ng
Messages
$$$
Code,
etc.
Community
Conversa>ons
They
are
different
conversa>ons
…

9. A
BeBer
Model
for
#3
Community
&
Pipeline
9
R&D
Product
Marke>ng
Messages
$$$
Code,
etc.
Conversa>ons
Iden>fy
Customer
Awareness
Download
&
Try
Deploy?
Train?
???
Buy
Iden>fy
community
What
Mission?
Plagorm
&
Tools
Arch.
of
Par>cipa>on
Code
of
Conduct
IP
Machine
Governance
Structure
Community
members
build
awareness
and
evangelize,
provide
exper>se
and
trial
support,
are
a
demonstra>on
of
solu>on
viability,
and
provide
great
iner>a
around
your
solu>on
…
with
different
tools,
programs
and
metrics.

10. #4
Open
Source
Community
Prac>ces
Project
Exes
published
Project
Build
Automated
I
Project
Install
Automated
Complete
Src
published
Project
BugTracking
Project
Build
Automated
II
Project
Test
Automated
I
Project
Test
Automated
II
Basic
Arch
Descrip>on
Project
License
Project
License
Mission
Statement
Code
of
Conduct
Forums,
Email
Comms
Plagorm
FAQs,
Howto
Governance
Contributoion
Guidelines
Events
Provenance
Tracking
Repositories
Protected
Dependencies
Documented
Contribu>ons
AudiBed
Provenance
Management
CommiBers
Indemnified
CommiBer
Governance
Trademark
Management
IP
Management
Ac>vi>es
Community
Development
SoZware
Construc>on
Maturity

11. #4
Open
Source
Community
PaBerns
Project
Exes
published
Project
Build
Automated
I
Project
Install
Automated
Complete
Src
published
Project
BugTracking
Project
Build
Automated
II
Project
Test
Automated
I
Project
Test
Automated
II
Basic
Arch
Descrip>on
Project
License
Project
License
Mission
Statement
Code
of
Conduct
Forums,
Email
Comms
Plagorm
FAQs,
Howto
Governance
Contributoion
Guidelines
Events
Provenance
Tracking
Repositories
Protected
Dependencies
Documented
Contribu>ons
AudiBed
Provenance
Management
CommiBers
Indemnified
CommiBer
Governance
Trademark
Management
IP
Management
Ac>vi>es
Community
Development
SoZware
Construc>on
Maturity
Encourage
Users
Encourage
Developers
Encourage
Contribu>ons
Encourage
Corp
Contribu>ons