InnerSourcing: Adopting open source engineering practices

A brief walkthru on InnerSource based on surveys done by Open Source Initiative and InnerSource Commons, to convince enterprises to adopt lessons learned from open source engineering practices and apply them to the way enterprise products are being engineered internally.

Transcript

1. @kosalanuwan 5/11/2016 InnerSourcing Why should enterprises adopt open source engineering practices?
2. Climate check on Open Source
3. Reasons to use OSS Top factors
4. Programing languages and frameworks Top factors
5. Concerns in using OSS Top concerns
6. Programming Patterns and Principles Style Guides Open source Contributing Etiquette Workflow Design and Health Style Guides Reviews Pipelines Test Suits Code Coverage and more ...
7. No matter who you are most of the smartest people work for someone else! Joy's Law
8. Knowledge is unevenly distributed. It never exists in a concentrated form! Friedrich Hayek, Economist and Philosopher
9. The enterprises need to find ways to access that knowledge!
10. Climate check on InnerSource
11. Why adopt InnerSource? Talent retention and employee satisfaction aren't the reasons to adopt InnerSource
12. What motivates developers? Fun isn't a motivation factor for devs to adopt InnerSource
13. Improved their job satisfaction Almost everybody "strongly agrees"
14. Active > Grow > Automate Journey
15. Software development methods Top methods and practices
16. Minimal-standard Tools for Managing Information Website Message Forums / Mailing Lists Bug Tracking Version Control Real-time Chat Wiki
17. First task is to bring down the hacktivation energy to a level that encourages people to be involved
18. Getting Start Checklist Features and Requirements List Reality of Development Status Downloads Version Controlling Bug Tracking Communication Channels Developer Guidelines Documentation Demos, Screenshots, Videos, Examples, ...
19. Manager does not mean owning the project!
20. Contributing does not mean coding!
21. Not all maintainers are coders!
22. Managing Participants Responsibility without Monopoly Delegation Codeowners Transition Maintainers and Committers Acknowledgments Hiring Open Source Developers
23. If it's worth doing once it's worth automating!
24. $ whois github.com Jake Feinler's "yellow pages" of the Internet
25. Try not to let humans do what machines could do instead! Pragmatic Project Automation, Mike Clark
26. Software quality practices Top methods and practices
27. Software release strategy Top methods and practices
28. Advocating Automation Test Automation Bots Conventional Commits Semantic Releases Release Pipelines Development Containers
29. If I do my job right you never see it! Radia Perlman