A fork load of maintenance - forking a key dependency
summary
The BBC maintains a production fork of dash.js for BBC DVB‑DASH to support broadcaster extensions on web and connected TV, accepting a high maintenance cost: porting V3→V4 takes about one year porting V3→V4 with each upstream major release requiring patching. Mitigations include legal signoff and CLA tracking, a decision record of divergences, active maintainer engagement, modular code and feature flags off by default so useful patches are upstreamed and selectively consumed back into the fork.
AI-written summary · about
chapters (8)
- 0:00Introduction to BBC forks
- 3:04Challenges of maintaining a fork
- 5:54Legal and governance processes
- 8:18Technical and project strategy
- 14:26Execution and upstreaming
- 17:03Outcomes and team collaboration
- 18:31Summary and best practices
- 25:35Q&A session
related talks
43mMedia Source Extensions
43mDASH and Media-over-QUIC Transport Face-Off: Performance Showdown at Low Latency
19mDevOps for Frontend: beyond Desktop Browsers
26mContent Steering with MPEG DASH
58mModern & secure adaptive streaming on the Web
39mMaintainer Q&A
45mModern & secure adaptive streaming on the Web
46mModern & secure adaptive streaming on the Web