What does moving to Pull Requests look like? The nginx story
summary
nginx moves Sept 2024 move to GitHub, shuts its old forums and bug tracker by end of December, giving about five months of data. code churn is low: 50–60 changes/month for nginx versus ~1–1.5 for Postgres; repository size is ~1/10 of Postgres. contributions increase mainly as drive-by doc and message-string fixes, plus two deep protocol fixes; most new contributors are occasional multi-project committers. GitHub workflow forces squash/force-push, creates noisy intermediate diffs, and usually deletes merged branches. evidence supports using PRs as an addition to mailing lists, not a replacement.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 3:05What is EngineX?
- 5:11Codebase comparison with PostgreSQL
- 6:58New contributions after moving to PRs
- 9:04How tools shaped the process
- 11:11Lessons and open questions
- 14:23Q&A and community concerns
- 20:44Summary and closing
related talks
32mPull Requests: Not Just For Code Anymore
20mThe life of an Angular pull request
32mLove and Hate for Pull Requests
16mBeyond Pull Requests: How Non-Code Contributions Scale Open Source Projects
43mMy First Year of Pull Requests
28mPull Requests: Merging good practices into your project
22mFrom Bug To PR: Turning Customer Pain Points Into Upstream Contributions
23mThe Art of the Pull Request