An intro to Open Source Product Management or "A PM’s primer on leftist software development models."
This presentation outlines Product Management in open source and outlines enterprise open source product management techniques, best practices in the space, licensing models and other topics that may be of interest to people working in software.
5. What is an open source software product?
An open source software product is a software product wherein the source
code is publicly available
Open source products contain licenses that dictate:
● Who owns the source code
● How the source code can be used or distributed
We say product but maybe we mean project?
● Why is it important?
● What’s the difference?
6. Are open source products a new thing?
☂ No!
● Unix
● 1980s magazines
● Linux kernel
● RedHat: Fedora
● Pidgin
☂ Yes
● Open Source Software is supporting commercialization
now more than ever.
11. Benevolent Dictator For Life
(Project Owner)
Rule with a loving, iron fist
Maintain control and
vision
As a ___
I want to ___
So I can ___
Credit Nathan Fox
@nathanfoxy
12. Community
Has Time
Customers
Grow their skills
Improve the product experience
Learn new approaches
Inspire and Be Inspired
Have a need
Want to support the product
Want documentation and support
Have varying ways of consuming
Have Money
13. ☂ Grow awareness
☂ Increase resources
☂ Standardize
☂ Increase availability /
“surface area”
As a Corporation, I want to {{want}}
So I can {{motivation}}
● Obtain users
● Ship product faster
● Define emerging trends
● Expand availability
14. ☂ Control the project
☂ Govern
☂ Provide support
☂ Attract other
corporations
As an Organization, I want to {{want}}
So I can {{motivation}}
● Provide objectivity
● Grow with stability
● Attract new members
● Reduce single point of
failure
17. Where do projects reside?
Github
Gitlab
Gomix / Glitch
SourceForge
Bitbucket
LaunchPad
Package Managers:
NPM, PyPi, Maven, Aur, RHEL, LaunchPad,
Gem, Pear & Pecl, etc
Microsoft CodePlex
Google Code
18. How does a Product become
Open Source?
… and once it is how do you keep it from falling over?
19. Before you publish, ask...
Why choose to take commercial software to open
source?
What OSS business model do you use?
How do you address the weight of existing code
and cultural history?
Why type of community do you want to create
What open source license fits?
What governance and development models do you
want to use?
Credit: Cyrus Wadia @ Pivotal
20. Business Models
Pure open source
● “Buy-me-a-beerware” (Ex: Tooling, pet projects)
Community open source
● Foundation (ex: Apache Foundation, Linux Foundation, Mozilla Foundation)
“Pure Play” with a focus on services & support
● Race to the bottom. Danger: Commoditization!
Subscription open source
● Hosted Software as a Service subscriptions (ex: Wordpress, Ghost, Sandstorm)
Multi-license open source
● Open source core, closed source value add
21. Organizational ownership benefits
Objective organization growing the project
Dedicated legal, marketing, business, hand-shaking support
IP assistance and less worries
Dedicated growth support for the ecosystem
Reduces “single vendor” risk
Governance model comes built in
Aligning multiple organizations around a single vision*
* hard
22. Governance
The hierarchy and roles that the project participants assume
The definition of participants’ roles in the project
How communication exists within the project
- Chaos vs Process. Fun times, right?
23. Licensing
Copyleft vs Permissive
Copyleft: Anything that you create or link to becomes open source
Permissive: Anything that you do, you can close source
Restrictions determine if additions or links require openness
Captain Obvious Says…”Corporations are generally not fans of giving their IP
away for free, Jimmy.”
25. Make it easy for others to contribute and consume
● Contributor License Agreements (CLAs)
● Empathy for customers and contributors
● Documentation
● Release milestones
● Roadmap policy
● Contribution policy
● Tests & CI
● Overcommunicate
● Excite your contributors
● Learn and teach, teach and learn.
Okay so success. How?
27. No such thing as an OSS company
☂ Engineering Economics
☂ OSS is a method within the space of “Software
Development”
Credit: Stephen Walli
28. Bubble? Growth? Both?
2016: Linux Foundation
attracted over 20,000
attendees from more than
4,000 organizations across
85 countries.
2015: Linux Foundation
attracted over 15,000
attendees from more than
3,100 organizations across
85 countries.
Source can be read
Licenses
Product or project?
Product:
Business can exist
Exists as a foundation for broader services
Evangelism vs Collaboration
Drucker Vs Friedman
Drucker "the purpose of the company is to create a market" Vs Friedman a company exists to provide a return to shareholders
Talk about Pidgin - 73 million downloads
Right MEOW
We've always shared software. From the 1950s until now.
Sendmail was already a company
Mysql was in 95
Redhad in 93
BSGI AT&T
Benevolent Dictator for Life
Note stallman
If programmers deserve to be rewarded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs.
Shirt: Emacs.
BDFL:Linus Torvalds
Who else participates? Communities
Touch to seed and community
just because you're open source doesn’t mean you sell to open source users
Enterprise will most def be your customers. Enterprise software is horrifying.
Customers also provide feedback that you can learn from and circulate
Freeloaders? You’re doing it right.
Lots of reasons but ultimately this exposes you to a new and different way of creating a product
You’re sharing IP, roadmap and trijectory.
Your product history is on the table.
Benevolent Dictator for Life
Benevolent Dictator for Life
Drucker "the purpose of the company is to create a market" Friedman (a company exists to provide a return to shareholders).
Marketplace on top of OSS
Single Vendor Risk
HOW DO YOU ALIGN MULTIPLE ORGANIZATIONS AROUND A SINGLE VISION?
If you’ve originated the project, you should retain the ability to be the soul supplier to control pricing and marketing.
Every place that copywright is applied is about protecting the distrobution chain, but not the author.
Media does not change. The bible doesnt change. Movies dont change. Music doesn't change.
Software is dynamic. You'realways patching always moving. SOftware is never "Done"
Derivativation is key here. If we have code that is derived from GPL code we enter a world where the GPL can arguably be implemented.
Automation means you can scale your project. Good process means scalability.
Talk about marco’s feedback