Three points that promoted InnerSource activities
summary
Nifty reports concrete results from three tactics: team-based platform repos and small shared tools drive cross-team PRs (example: a permission-definition file lets users request access via pull request, reducing maintainer work), workflows use GitHub web UI so non‑engineers edit email templates in‑browser, and internal workshops lower the first‑contribution barrier. Metrics: over 1,000 repositories under one org and roughly 50% of engineers contributing; contribution practice is a 60‑minute session with hands‑on steps and >10 attendees.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 2:17What is Nifty Corporation
- 4:03Discoveries and efforts for InnerSource
- 8:00Three points that accelerated InnerSource
- 8:43Interests align for InnerSource
- 11:16Incorporate InnerSource in workflow
- 12:47Create path to contributors
- 14:11Adapting InnerSource to company
- 15:59Future plans and efforts
- 18:18Summary and closing
related talks
30mInnersource: open source collaboration patterns beyond public FOSS projects
28mA Frictionless Inner Source Journey
25mDriving the InnerSource Program at SAP
18m(Y)Our Journey to Inner Source
14mAdopting InnerSource to maximize Developer Experience
17mEnhancing Developer Experience through InnerSource and Platform Engineering
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
28mA Journey to Inner Source