TFW when your country is funding Open Source development
summary
Contract work on Docs Italia forks Read The Docs to serve Italian public administrations, attempts to add Elasticsearch 5.6 support fail to merge upstream so a long‑lived fork accumulates hundreds of lines and bespoke CI checks, metadata importers and deployment knobs. Maintenance strategy favors rebase to keep history clean, cherry‑pick when needed, and prefer configuration overrides over changing core code. Lessons: contribute small fixes upstream to reduce downstream drift, accept pragmatic design sacrifices to deliver working automation and imports for institutional users.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:09UPSTREAM CONTRIBUTIONS
- 7:42BUILD TRUST WITH UPSTREAM BE PART OF THE COMMUNITY
- 8:50A FORK IS A LONG LIVED BRANCH FOCUPSTREAMLESS DELTA DOWNSTREAM CONTRIBUTING TO OPEN SOURCE IS PART OF THE JOB
- 11:57SYNC WITH UPSTREAM: REBASE VS MERGE
related talks
34mFOSS like a Boss!
33mImproving a Large FOSS Project Sustainability
40mSustainable open source contributions in your business
45mDocs That Scale: Strategies for Sustainable Documentation in Open Source Projects
42mEat Your Own Dogfood - How Upstream Orientation Changed the Way We Work in Open Source Management
13mOpen Source Collaboration by Public Sector Stakeholders
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs
29mOpen Source Contribution - How does it even work?