Best Practice in Delivering Successful Open Source Engagement in Organisations
summary
EPAM describes pragmatic steps: an open source charter of five to six bullets that removes approval friction; an open source contributor index (opensourceindex.io) that links GitHub IDs to HR and shows real‑time push events; a release pipeline that usually takes two weeks to release a repo to GitHub; client examples include a 300‑row approved library wiki and embedding an open‑source module into onboarding; recommend a lean OSRB, legal embedded in global counsel, and turning email threads into public FAQs.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:54This is not consultancy
- 3:52Awareness.
- 8:06Freedom to engage
- 11:21Recognition
- 14:43Releases
- 19:11Community
related talks
40mEngagement of Open Source Communities – A Deep-dive Into EPAM’s OSPO
27mDesign Your Open Source Project
28mThe five stages of corporate open source adoption
01h 39mWorkshop: Building and Managing an Open Source Program Office
15mHow to set up an Open Source Program Office? Get insights and use cases from the OSPO Alliance
43mFostering an Open Source Culture
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
25mHow to be a Corporate Open Source Citizen