Mark Hinkle runs the Citrix Open Source Business Office and has spent 20 years working with open source communities and delivering open source software. Topics covered in this presentation will include the benefit of his mistakes and successes both in evaluating open source ad an end-user and in delivering enterprise solutions based on open source software.

1. Things I Learned about Open
Source...The Hard Way
OS in Big Organizations II: Failures, Success Stories & Best Practices
SAP Developer’s Group

2. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Slides Available on Slideshare:
http://www.slideshare.net/socializedsoftwar
e
Creative Commons Attributions-ShareAlike 4.0 International
Share — copy and redistribute the material in any medium or format
Adapt — remix, transform, and build upon the material
for any purpose, even commercially.
The licensor cannot revoke these freedoms as long as you follow the license terms.
Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made.
You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the
same license as the original.

3. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
• My open source experiences
• The power law of open source
• Open source is about collaboration not free labor
• How open source provides leverage
• Signs of a healthy open source project
• The role foundations can play in open source projects
Agenda

4. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
• Manage Citrix Open Source Business Office
• Apache CloudStack Committer and PMC Member
• Advisory boards Gluster and Xen Project
• Joined Citrix via Cloud.com acquisition July 2011
• Zenoss Core open source project to 100,000 users,
1.5 million downloads
• Former LinuxWorld Magazine Editor-in-Chief
• Open Management Consortium organizer
• Author - “Windows to Linux Business Desktop
Migration” – Thomson
• NetDirector Project - Open Source Configuration
Management
About Me

5. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
The Hard Road to “Enlightenment”
• Non-contributing user
• Open source desktop advocate
• Non-OSI approved license
• Open core
• LinuxWorld Editor-in-Chief aka “brainwashing”
• Open sourcing to an organization
• Open sourcing to another organization
• Still searching for open source nirvana

6. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
The Power Law of
Open Source

7. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
"No matter who you are,
most of the smartest people
work for someone else.”
Joy’s Law (the Open Source Advantage)

8. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
The Power Law of Open Source

9. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
How it Works
• Large user base to move the development needle (only
a small number of users give back)
• Context over Code (user generated improvements are
better informed, use code often worse)
• Collective Intelligence bears more leverage because
coordination isn’t needed as much (Collaborative
Intelligence)

10. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Open source is about
collaboration not just
free (as in beer) labor

11. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Open Source Strategy
Open Source 2005 – Tom Sawyer Open Source 2014 – John Nash

12. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Avoid The Pareto Optimality
Pareto efficiency, or
Pareto optimality, is a
state of allocation of
resources in which it is
impossible to make any
one individual better
off without making at
least one individual
worse off.

13. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
How open source
provides leverage

14. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
How Consumers Gain Leverage
End-User Solution Providers
Lower Cost
Typical lower than proprietary alternative
Quality
Many eyeballs make all bugs shallow
User controlled Consumption
Only buy support when needed
Continuity
No Need for Escrow or Worries about Company
behind code
Faster release cycles
Quick bug response and aggressive release cycles
Recruiting
Often find talent in projects
Agility
Reduce R&D costs
Product Management - Product Development
– Testing – Documentation – Translation
Ops Cost Reduction
Customer Support – Distribution - Capital
Software Costs*
Sales and Marketing
Partner Integration - Brand Awareness - Pre-
Sales

15. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Open Source
“In The Mythical Man-Month, Fred Brooks observed that
programmer time is not fungible; adding developers to a late
software project makes it later. As we've seen previously, he
argued that the complexity and communication costs of a project
rise with the square of the number of developers, while work done
only rises linearly….if Brooks's Law were the whole picture Linux
would be impossible.
Gerald Weinberg's classic The Psychology of Computer
Programming supplied what, in hindsight, we can see as a vital
correction to Brooks. …where developers are not territorial about
their code, and encourage other people to look for bugs and
potential improvements in it, improvement happens dramatically
faster than elsewhere.”
Eric S. Raymond, The Cathedral and the Bazaar

16. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Signs of a Healthy Open
Source Project

17. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
• Code Velocity
• Committers
• Committer Reputation
• User-driven or Vendor-Driven
Innovation
• User Activity
• Corporate Support*
• Reputation of Foundation*
VETTING OPEN SOURCE PROJECTS

18. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
OPEN SOURCE ANALYSIS
http://www.openhub.net http://activity.openstack.org

19. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Github
• Awesome hosting service
• Wild west
• Easy to follow and fork
• Nice social networking
features
• Companies can great
“official” repos e.g. Netflix

20. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Developer Diversity
https://www.openhub.net/p/Hadoop/contributors?sort=latest_commit

21. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
• Flaw fixed in April 7, 2014
• Demonstrates fragility of unmanaged open
source
• Pre-Heartbleed 1 full-time developer, $7k
per year in donations
• Massive failure of risk analysis
• >500,000+ websites affected
• Tens of millions of dollars in lost productivity
and SSL reissues, billions of dollars in
unsecured risk
• Core Infrastructure Initiative funding via
Linux Foundation Collaborative Initiative to
shore up the project employee dedicated
developers and provide oversight backed by
Amazon, Adobe,Bloomberg,Dell,Google,
HP, IBM, Intel, Microsoft, Qualcom,
Rackspace, Salesforce, VMware
Case Study: Fragile Open Source
Heartbleed OpenSSL

22. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Development Velocity
Source: OpenHub.com
Flat Nagios
Growing Hadoop

23. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Google Trends: Technology Buzz
Source Google Trends: http://www.google.com/trends/explore#q=nagios%2C%20Hadoop&cmpt=q

24. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
The role foundations can
play in open source
projects

25. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
How Foundations Can Help OSS
• Vendor neutral
• Enforce a meritocracy
• Provide a shield for developers
• Ensure continuity of project beyond a single company
• Provide vehicle for pooling resources
• Create ecosystems
• Not all are especially well-funded to accomplish this
mission

26. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
The Linux
Foundation
• Founded 2007
• Home of Linux Kernel, Xen Project, Open
Daylight
• Companies and individuals can join
• Governed by voting classes both corporate and
individual
• ~230 corporate members
• $15.6 million in revenue

27. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Apache Software
Foundation
• Founded in 1999
• Home ofApache HTTPD,
ApacheTomcat, Apache
• Only individuals can join
• Sponsors have no say in
project
• Great development
methodology
• Minimal corporate financial
backing
• $1.2 million annual income

28. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Eclipse
• Project started in 2001
• Foundation started in 2004
• Foundation kickstarted
growth
• 204 members companies
• 175 active projects
• $4.1 million a year in income

29. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Vanity Foundations
• Foundations to align and
build brand
• Very focused on a single
technology
• Easier for companies to
direct resources
• Newer model
• May not be non-profit

30. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
Non-Profit Status for Software
Foundations
• Recent Yorba decision by IRS
rejects non-profit status
• OpenStack Foundation not a non-
profit but trying
• New foundations coming online
this year CloudFoundry and .Net
• Less effective use of donations
without tax-exempt status
• May lead to international non-
profit organizations
• International law could cause
upheaval and introduce new
legalities to OSS ecosystem

31. By Mark R. Hinkle
@mrhinkle
mrhinkle@gmail.com
Things I Learned about Open Source…The Hard Way
CONTACT ME
Happy to Chat about Open Source, Cloud or Pittsburgh Sports
Professional: mark.hinkle@citrix.com
Personal: mrhinkle@gmail.com
Phone: 919.228.8049
Professional: http://open.citrix.com
Personal: http://www.socializedsoftware.com
Twitter: @mrhinkle