This talk was geared towards a non-technical audience interested in the magic and wonder of open source. Danny Rosen went over what open source is, why it's important, what it means to have an open source product and why it's important to customers. He also discussed what it's like to be involved in the open source community from the perspective of a user, a product manager and a developer, and the challenges and opportunities related to community management and community involvement.

1. Why Open Source Products Are Important
by a Google Tech Manager
www.productschool.com

2. FREE INVITE
Join 16,000+ Product Managers on
productschool.com/slack-community

3. Product
Management
2-month part-time
Courses

4. Coding
for Managers
2-month part-time
Courses

5. Data Analytics
for Managers
2-month part-time
Courses

6. San Francisco
Silicon Valley
New York
Santa Monica
Los Angeles
Orange County
4,000+
14
Campuses
Alumni
Austin
Seattle
Toronto
London
Boston
Chicago
Denver

7. Include @productschool and #prodmgmt at the
end of your tweet
Tweet to get a free ticket
for our next Event!

8. Danny Rosen
Tonight’s Speaker

9. Product Management and
Open Source
Or… A PM’s primer on leftist software development
models

10. 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?

11. Are open source products a new thing?
● No!
● 1980s magazines
● Linux
● Chrome
● Android
● Pidgin
● Sort of…?
● Open Source Software is supporting
commercialization now more than
ever.

12. Who Uses Open Source?

13. YOU. RIGHT NOW.

14. YOU. TOMORROW.

15. Who Participates?

16. Community
Has Time
Customers
Grow their skills
Improve the product experience
Learn new approaches
Network
Inspire and Be Inspired
Have “a need”
Have varying ways of consuming
Want to support the product
Want documentation and support
Have Money

17. Benevolent Dictator For
Life
Rule with a loving, iron fist
Maintain control and vision
As a ___
I want to ___
So I can ___
Credit Nathan Fox
@nathanfoxy

18. ● Grow awareness
● Increase resources
● Standardize
● Increase availability /
“surface area”
As a Corporation, I want to {{want}}
So I can {{motivation}}
● Obtain dev community
● Ship product faster
● Define emerging trends
● Expand product offering
{{want}
}
{{motivation}}

19. ● Control the project
● Govern
● Provide support
● Attract other
corporations
As an organization, I want to {{want}}
So I can {{motivation}}
● Facilitate vision process
● Grow with stability
● Attract new members
● Reduce single point of
failure
{{want}
}
{{motivation}}

20. 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

21. How does a Product become Open
Source?
… and once it is how do you keep it from falling over?

22. 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

23. 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

24. Organizational ownership benefits
● Objective organization growing the project
● Dedicated legal, marketing, business, hand-shaking support
● IP assistance
● Dedicated growth support for the ecosystem
● Reduces “single vendor” risk
● Governance model comes built in
● Aligning multiple organizations around a single vision*
* hard

25. 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?

26. 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.”

27. ● 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?

28. Thanks!
Me:
Danny Rosen
github/twitter: @dannyzen
linkedin.com/in/dannyrosen
danny.rosen@gmail.com
Sarah Novotny - Kubernetes
David Aronchick - Kubernetes
John Mark Walker @ ARM
Cyrus Wadia @ Pivotal
Marco Nicosio @ Pivotal
Mike Dalessio @ Pivotal
Bridget Kromhout @ Microsoft
Stephen Walli @ Microsoft
Credit
Nathan Fox
@nathanfoxy

29. Part-time Product Management Courses in
San Francisco, Silicon Valley, Los Angeles
and New York
www.productschool.com