From Bug To PR: Turning Customer Pain Points Into Upstream Contributions
summary
NetApp Instaclustr converts customer bug reports into upstream fixes by triaging issues, checking existing GitHub work, forking and coding fixes, deploying via an internal branch deploys to meet urgent SLAs, then opening PRs and coordinating with maintainers. Example: a cross‑cluster replication index‑deletion change is developed, deployed to the customer, and OpenSearch PR merged after 4–5 months; major features typically hit releases in ~6 months, with backports when necessary.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04Customer pain to upstream
- 3:37NetApp Instacluster operation
- 5:21Triage customer requests
- 7:47Internal deployment and backports
- 9:10Benefits of upstream contributions
- 10:56Contribution workflow steps
- 13:01Contributing to OpenSearch
- 15:05Non-dev open source ways
- 16:29Q&A
related talks
32mPull Requests: Not Just For Code Anymore
21mWhat does moving to Pull Requests look like? The nginx story
39mThe Life of a Kernel Bugfix
33mWorking backwards
06mLightning Talk: Prometheus Bug Scrub
31mMaintaining a big open source project: lessons learned
29mBreaking the PR Review Bottleneck
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal