Why is there no new Release? Nobody pays for basics
summary
ReaR started as a paid consulting project to replace an expensive commercial DR product and now automates bare‑metal restores by integrating with many commercial backup tools; used in many data centres, 193 contributors and seven maintainers support it, Red Hat and SUSE provide commercial support, and there are ~2.5k issue tickets. Releases happen only every few years so a GitHub Actions snapshot pipeline supplies builds, but documentation, cross‑architecture testing and sponsored automated testing remain underfunded and unreliable.
AI-written summary · about
chapters (11)
- 0:00Introduction and speakers
- 1:07About the open source project
- 7:13What is REAR and its purpose
- 10:00History of REAR project
- 13:54REAR's success and growth
- 17:30Challenges in open source maintenance
- 19:38Maintainer engagement and funding issues
- 22:07Current release management struggles
- 22:48Attempts to find solutions
- 23:30Audience discussion and suggestions
- 31:10Closing remarks and Q&A summary
related talks
41mWhy is there no new Release? Nobody pays for the basics 🙁
35mOpen-source releases: Everything we've learnt in 4 years
33mDeveloping RHEL open source way
21mCommunities, Enterprises and All the Rest
20mJuggling the dual life of an enterprise open source project
50mDo our development tools need a refresh?
49mOpen Source is Broken, and it’s Our Fault
35mReleasing Ceph - Deep Dive Into Build Infrastructure