Dev Log #7: First Community PR — The Bareos Team Joins In
Five weeks into development. The codebase is public, the README is written, the build instructions are tested. And then — the first pull request from outside.
Build Improvements from Bareos
Joerg Steffens from the Bareos project submitted build improvements that make Onesimus easier to compile on various Linux distributions. The changes include:
- Dynamic detection of static vs. shared OpenSSL
- Proper Qt 6.8 minimum requirement enforcement
- Build requirement documentation
It’s a small PR in terms of lines changed. But it’s a massive signal: the Bareos community is paying attention.
Why This Matters
Open source projects live or die by community engagement. The first external PR is a milestone — it means someone outside the core team read the code, understood the build system, and cared enough to improve it.
For Onesimus specifically, having the Bareos team involved means we’re building something that aligns with where Bareos is headed. We’re not building against Bareos — we’re building with it.
A Second PR: Restore Improvements
Shortly after, a second PR arrived — this time touching the restore browser functionality: fixing the BVFS navigation, adding missing WhereAcl support, and setting the default API mode to JSON compact. The kind of improvements that come from someone who actually runs Bareos in production.
How to Contribute
Every contribution matters — not just code. Translations, bug reports, documentation, and even just feedback on the UX all help shape the project. If you manage Bareos and want a better interface, come build it with us.