Open source or proprietary, choose wisely!
If you’re involved in open source work in or around a business, you will inevitably have the discussion, “Is this open source or proprietary?” Do not take this moment lightly. This seemingly easy question is met with strong opinions on both sides. Friendships have been lost. Companies have suffered. It’s as close to religious warfare as we can get in the tech world. It’s time to call a truce. There are plenty of valid arguments on both sides. Patrick McFadin outlines the pros and cons of each. Using example scenarios of projects that must decide whether or not they’ll be open source, Patrick explores objective ways to make a decision without descending into chaos and name calling. Even without a completely objective picture, understanding both sides of the argument can help keep you on track and civil. Patrick has been involved in OSS for more years than he likes to admit and would love for his past mistakes to benefit you. Topics include: - Key questions to ask to help guide your decision - Reasons for choosing OSS - Reasons for staying strictly proprietary - Considerations for mixing OSS and proprietary models - Transitioning from one model to the other
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to Open source or proprietary, choose wisely!
Similar to Open source or proprietary, choose wisely! (20)
More from Patrick McFadin
More from Patrick McFadin (17)
Recently uploaded
Recently uploaded (20)
Open source or proprietary, choose wisely!
- 1. @PatrickMcFadin Patrick McFadin Chief Evangelist for Apache Cassandra, DataStax Open Source or Proprietary: Choose Wisely! 1
- 2. Why? We are an Open Source company We sell an Open Source product Our company has an OSS repository We want to be an Open Source company
- 4. The world has changed
- 5. The world has changed • Open is easy • Worldwide communication is instant
- 6. This is how business works now Source: Black Duck OSS Survey 2016
- 9. Adoption Source: Black Duck OSS Survey 2016
- 10. Adoption
- 11. Too big for one company • Competing POV • Specific interests
- 13. Engineers still need to eat
- 14. Haha! I don’t need money! Haha! Neither do I!
- 15. Why mix types? Don’t hurt the small teams Build things large organizations will pay for Open Closed Finding the fine line
- 16. Transitioning from one to another
- 17. You need a good plan Source: Black Duck OSS Survey 2016
- 18. Restrictive Licenses License Can Can’t Must Special Case GPLv2 • Commercial • Modify • Distribute • Place Warranty •Sublicense •Hold Liable •Include Original •Disclose Source All changes have to stay GPL GPLv3 • Commercial • Modify • Distribute • Place Warranty •Sublicense •Hold Liable •Include Original •Disclose Source •State changes Fixed “Tivo Hole” in GPLv2 AGPL • Commercial • Modify • Distribute • Place Warranty •Sublicense •Hold Liable •Include Original •Disclose Source •State changes •Include Copyright Made clause for “Network Software” Internal Use: Safe, SAAS Application: Warn, Product Distribution: Danger
- 19. Permissive Licenses License Can Can’t Must Special Case Apache •Commercial •Modify •Distribute •Place Warranty •Sublicense •Private use •Use Trademark •Hold Liable • Include Copyright • Include License • State Changes • Include Notice Provide a notice in each file changed. Explicit patent license from contibuter. BSD •Commercial •Modify •Distribute •Place Warranty •Sublicense •Use Trademark •Hold Liable • Include Copyright Do anything you want, just include the BSD copyright MIT •Commercial •Modify •Distribute •Private use •Sublicense •Hold Liable • Include Copyright • Include License Do whatever. Include license and copyright Internal Use: Safe, SAAS Application: Safe, Product Distribution: Safe
- 20. OSS Supreme court • 7 members • Cross section of opinions • Executive branch has veto
- 21. The law • Employee contracts • Most assign rights to employer • We acknowledge that
- 22. Employee rights? Work Off time
- 23. The setup • Employees self-report via a google form
- 24. The process • Form submitted • Docket number created
- 25. Rulings • Summary are ruled on immediately • Full court go to public hearing
- 26. Full hearing • WebEx for entire company • Sides are argued • Questions are asked
- 27. Action • Ruling is posted • If employee project • Repo is moved • or • contract is updated
- 28. Still learning
- 29. Lock it down and make the freeloaders PAAYYYY!!! Give it all away!
- 31. Choose wisely! Follow me on twitter for more fun and excitement @PatrickMcFadin