uBixSys is built by people who like building tools — small, sharp, standards-committed software they'd actually want to run. If that sounds like you, there's a place to help, whether or not you write code.
Every project under uBixSys is open source and self-hosted on purpose: software you can read, run, and depend on without handing your data to someone else. Keeping tools like that honest — correct, documented, and genuinely dependable — is more than any one maintainer can do alone.
We hold the work to a high bar: strong standards, real tests, and clear documentation. Contributing here means caring about that bar as much as we do — and you don't have to be a developer to make a real difference. Reporting a clear bug, reproducing a failing test, or fixing a stale doc all move the projects forward.
The most useful help, in roughly the order it tends to matter — none of it requires commit access.
Put each RC and release through its paces on your own hardware, OS, and configuration. Real-world coverage catches what CI can't, and a passing run on your setup is a data point that matters.
When a test goes red, help track down why. A clear diagnosis — the conditions, the trigger, the likely cause — is often more than half the fix, and it's some of the highest-leverage help you can give.
Open clear, reproducible bug reports — minimal steps, expected vs. actual, versions and environment — and help work existing ones toward resolution. A good report is a gift to the next person who hits it.
Keep the docs accurate as the tools change, sand down the rough edges that tripped you up, and help make them available in more languages so more people can use these tools.
Anyone hoping to help develop and maintain our applications should be able to meet the bar we hold ourselves to. It's demanding on purpose — it's what keeps the tools dependable.
dev, land through reviewed no-fast-forward merges, and keep commits coherent and self-explanatory.Starting points for getting into the code and the issue trackers.