Open Source in the Enterprise
0 likes43 views
The document discusses the benefits and processes of open source contributions within enterprises, highlighting a case study on the automounter project. It emphasizes the importance of community collaboration, legal compliance, and effective management of software contributions to mitigate risks. The conclusion stresses that while open source requires effort, it offers significant advantages over private forks and potential software obsolescence.
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 2
Background:Morgan Stanley](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-2-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 3
Case Study in Contribution:TheAutomounter
• Integrating new versions took considerable time.
• More than 10 versions of the automounter released in the last 15 years, still going
strong.
• By contributing our patches and working with the community, we have:
– Saved effort on integrating new versions.
– More rapidly adopted new versions.
– Able to adopt new distributions with minimal risk.
– Collaborated over problems with the community.](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-3-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 4
Benefits of Contribution
• Open source allows you to avoid private forks that cause a non-competitive
maintenance burden.
• Contributing demonstrates that your enterprise is an active participant in the
community.
• Open source mitigates risk from:
– Software obsolescence.
– Vulnerabilities or bugs through insufficient review.](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-4-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 5
Contribution Process
Contrib
utor
Manage
ment
Legal
and
Compli
ance](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-5-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 6
Contributor:Managing the Distribution
Software Contributions
• Data leakage protection:
– Code review.
– DLP tools.
• How do you get the software to the manager of the
software? Email, GIT pull request, etc?
• Need to bring in next version containing
contribution and validate successful integration.
Managed Projects
• Data leakage protection:
– Code review.
– DLP tools.
• How do you push software to the external
repository?
• How do you manage pull requests/patch
submissions?
• How do you manage bug reports?](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-6-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 7
Legal & Compliance:Managing the Distribution
Software Contributions
• Reviewing target contribution agreement (if one
exists).
• Reviewing:
– Code review.
– DLP tools.
• How do you get the software to the manager of the
software? Email, GIT pull request, etc?
• Need to bring in next version containing
contribution and validate successful integration.
Managed Projects
• Data leakage protection:
– Code review.
– DLP tools.
• How do you push software to the external
repository?
• How do you manage pull requests/patch
submissions?
• How do you manage bug reports?](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-7-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 8
Legal & Compliance:Questions for the Contributor
• What license do you want to use?
• Who wrote the code? Under what contracts?
• What artefacts with their own licenses are distributed with this software?
• What forums will the team use for discussion of this open source?
• How to manage a contribution agreement?](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-8-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 9
Building a Community](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-9-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 10
Community Challenges
Forums
• Who can communicate? Approvals? Review?
Documentation
• What is it?
• In open source, customers are disconnected from
providers. Documentation is all that they get…
• “Hello World” – show something fast!
• Documentation aimed at the audience.
• Label experimental code.
• Documentation is the priority.
Activity
• Where is the canonical source?](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-10-320.jpg)
![[OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 11
Conclusions
• Open Source is never free
• Open Source is worth the effort](https://image.slidesharecdn.com/opensourceandenterprise2017-nickwilliams-180508163201/85/Open-Source-in-the-Enterprise-11-320.jpg)
Open Source in the Enterprise
- 1. Open Source in the Enterprise Nick Williams
- 2. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 2 Background:Morgan Stanley
- 3. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 3 Case Study in Contribution:TheAutomounter • Integrating new versions took considerable time. • More than 10 versions of the automounter released in the last 15 years, still going strong. • By contributing our patches and working with the community, we have: – Saved effort on integrating new versions. – More rapidly adopted new versions. – Able to adopt new distributions with minimal risk. – Collaborated over problems with the community.
- 4. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 4 Benefits of Contribution • Open source allows you to avoid private forks that cause a non-competitive maintenance burden. • Contributing demonstrates that your enterprise is an active participant in the community. • Open source mitigates risk from: – Software obsolescence. – Vulnerabilities or bugs through insufficient review.
- 5. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 5 Contribution Process Contrib utor Manage ment Legal and Compli ance
- 6. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 6 Contributor:Managing the Distribution Software Contributions • Data leakage protection: – Code review. – DLP tools. • How do you get the software to the manager of the software? Email, GIT pull request, etc? • Need to bring in next version containing contribution and validate successful integration. Managed Projects • Data leakage protection: – Code review. – DLP tools. • How do you push software to the external repository? • How do you manage pull requests/patch submissions? • How do you manage bug reports?
- 7. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 7 Legal & Compliance:Managing the Distribution Software Contributions • Reviewing target contribution agreement (if one exists). • Reviewing: – Code review. – DLP tools. • How do you get the software to the manager of the software? Email, GIT pull request, etc? • Need to bring in next version containing contribution and validate successful integration. Managed Projects • Data leakage protection: – Code review. – DLP tools. • How do you push software to the external repository? • How do you manage pull requests/patch submissions? • How do you manage bug reports?
- 8. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 8 Legal & Compliance:Questions for the Contributor • What license do you want to use? • Who wrote the code? Under what contracts? • What artefacts with their own licenses are distributed with this software? • What forums will the team use for discussion of this open source? • How to manage a contribution agreement?
- 9. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 9 Building a Community
- 10. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 10 Community Challenges Forums • Who can communicate? Approvals? Review? Documentation • What is it? • In open source, customers are disconnected from providers. Documentation is all that they get… • “Hello World” – show something fast! • Documentation aimed at the audience. • Label experimental code. • Documentation is the priority. Activity • Where is the canonical source?
- 11. [OPTIONAL DESCRIPTOR] [PRESENTATION NAME AND | OR DATE] 11 Conclusions • Open Source is never free • Open Source is worth the effort