Financial Services Open Source Participation
0 likes•38 views
The document outlines the benefits and motivations for enterprises to adopt open source software, including cost reduction, higher quality code, and the attraction of top talent. It provides recipes for successful consumption, contribution, and ownership, emphasizing the importance of legal, social, and technical aspects. Additionally, it highlights various success metrics for assessing participation and effectiveness in open source initiatives.
![Motivation
● 30% want to make it easier for
employees [2014]
● 67% encourage contribution [2016]
● 34% have more than 50% of
employees contributing [2016]
● Facebook asked their employees…
“Were you aware of the open source
software program at Facebook?”](https://image.slidesharecdn.com/opensourcingyourenterprise-180508162944/85/Financial-Services-Open-Source-Participation-10-320.jpg)
Financial Services Open Source Participation
- 1. Open Sourcing Your Enterprise Mohammad Rezaei 2017
- 2. Agenda ● General Introduction ● Motivation and cost/benefit criteria ● Open source recipes ● Measure your success
- 3. Levels of Participation ● Consumption ● Contribution ● Ownership ● Start with consumption and have a plan for contribution and ownership.
- 4. Benefits ● Reduce Costs – Concentrate on your domain – don’t reinvent the wheel. – Implement the features you need. – Interoperability – Lower legal costs – no need to review contracts
- 5. Benefits ● Higher quality code – Able to fix issues – Freedom from vendor lock-in – Many eyes, wide usage improves quality and security
- 6. Benefits ● Attract and retain top development talent ● Empower your developers – Full access to code, ease of deployment ● Influence direction ● Reduce rejection of proprietary code
- 7. Risks ● License incompatibility ● Litigation (patent, illegal code) ● Malicious code contribution ● Security/viability of old libraries ● Security of unpatched libraries.
- 8. Culture Clash ● “Can only use software with a support contract” ● “Open source is lower quality than commercial software” ● “Open source is not certified to work with product XYZ”
- 9. Motivation ● 2015 survey: – 88% want to increase contribution – 53% want to reduce employee barrier to participation ● Companies contributing: – 2014: 50% – 2015: 63% – 2016: 65%
- 10. Motivation ● 30% want to make it easier for employees [2014] ● 67% encourage contribution [2016] ● 34% have more than 50% of employees contributing [2016] ● Facebook asked their employees… “Were you aware of the open source software program at Facebook?”
- 11. Consumption Recipe ● Sell the benefits ● Establish a license policy ● Mirror & filter maven and npm internally ● Create a process for other intake ● For large deployments, consider paid support ● Post-use compliance
- 12. Contribution and Ownership ● Three universal aspects: – Legal – Social – Technical ● Understanding it makes you a better consumer!
- 13. Contribution Recipe ● Sell the benefits ● Establish training for people ● Establish a registry of people/projects ● Create bots for compliance/retention ● Establish project approval process ● Setup IP review for outgoing code ● Support both BYOD and enterprise desktop
- 14. Legal ● Review your employment agreements and copyright law ● Explain the rules to your employees ● Understand contribution rules versus consumption rules ● 4 common legal frameworks: – Copyright assignment – Contribution agreement – In == Out – In == Out with DCO
- 15. Social ● Social pillars of open source: – Collaboration, open exchange – Meritocracy – Transparency – Freedom to tinker – Sharing and empowerment – Good citizenship ● Respect the local rules
- 16. Github Contribution Recipe Github.com origin/master user/master Pull request Fork Github Cloud InternalNetwork Internal app proxy/firewall Internal fork Github reverse proxy push clone fetch Code IP Review push/ fork Blocked by git user agent Blocked by URL
- 17. 3 Steps to Contribute ● Get trained – Social/Legal/Reputational aspects ● Approve project – Legal/Vendor review ● Write code – Get IP review if not using BYOD
- 18. Ownership Recipe ● Sell the benefits ● Establish a project approval process ● Establish a presence outside ● Establish guidelines around responding to issues/bugs ● Adopt a contribution model
- 19. Ownership: checkpoints ● Establish a community standard ● Make sure your work is done in the open ● Adopt a uniform license ● Adopt a contribution model ● Code consistency rules ● Treat the community with respect
- 20. Consumption Success ● How long does it take between deciding to use an open source product and actual use? ● How easy is it to evaluate an open source product for use? ● How easy is it to keep up to date with new versions? ● How many manual approvals?
- 21. Contribution Success ● How long does it take between having a patch and having it accepted? ● How many manual approvals?
- 22. Ownership Success ● Is the ultimate source in the open? ● Are discussion and decisions happening in the open? ● How big is the size and breadth of the community? ● What happens when a committer leaves the company? ● What’s the average response time to issues?