How New Relic Went Open Source: Code & Culture
summary
New Relic decides to open-source its entire instrumentation layer — roughly one third of its codebase — and converts a three-month sprint into a July 22 launch, removing non‑OSS third‑party libs, unifying on single‑source development, and publishing agents and SDKs under open licenses. Issue and feature workflows move from private Jira to GitHub issues with GitHub Actions CI CD, new security and escalation policies are defined, and early metrics follow GitHub’s guide for discovery usage retention and maintainer activity.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:51The Instrumentation Layer
- 11:22Code Cleanup
- 13:30Melissa Klein
- 13:45Ben Evans
- 14:33Open by Default
- 15:01Go Where the Engineers Are
- 16:27Contributions Are Visible
- 17:34The Open by Default Transformation Guidebook
- 18:31Issue Life Cycle Management
- 21:20Security
- 22:42Customer Escalations
- 23:00Integrate Customer Escalations into an Open Source Process
- 25:47Update Our Hiring Profile
- 26:27Moderation Guidelines
related talks
57mOpen Source at commercial organisations
23mThe Open Source Journey of the Most Unlikely Participant
40mHow to Open Source a Project and Possibly Not Fail While Trying
38mCode, Control, and Community: How Open Source is Reshaping Innova...
15mLessons learned: Guidance on how to make open source development a success
36mIntersource is GitHub culture and open source principles
04mThe role of open source in a company
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration