Get Involved

Estimated reading: 2 minutes 73 views

Contributions can range from reporting bugs to maintaining or producing code. Any contribution, even the smallest, is valued.

Areas of Contribution

Artwork.
Development (programming and packaging).
UI Design for Apps.
Documentation and Translation.
Marketing and Website.
Quality Assurance (testing and bug triaging).

To start contributing, create a GitHub account at Nitrux @ GitHub.

Community

Public Forum → GitHub Discussions

Social Media → X · Bluesky · Facebook · YouTube · Mastodon · Instagram · Threads · MeWe

Instant Chat → Gitter · Telegram

Packaging

To package software as an AppBox, visit the NX AppHub wiki.

Report Bugs

Open an issue in the Nitrux Bug Repository using the bug report template.

Feature Requests

Open an issue in the Nitrux Bug Repository using the feature request template.

Release Schedule

Nitrux follows a fixed-release cycle:

One new release every 60 days.
We support each release for 60 days from the Release Announcement.
After a new release, we only support the previous release for upgrades only (not bug reports) for 60 days.
Releases older than that are unsupported.

Nitrux does not follow major/minor versioning conventions. Releases with suffix x.x.0 are not “major,” and x.x.1 are not “minor”; they are simply releases.

Development Schedule

Week 1 → Release day. Create OTA update archive. Begin work on the next release.
Week 2 → Review bug reports. Generate test builds for fixes.
Week 3 → Review feature requests. Generate test builds for new features.
Week 4 → QA tasks. Update website and documentation. Final fixes and ISO rebuild.

Important Notes

The Nitrux Telegram group uses a captcha bot for Spam protection. Failing to pass the captcha will result in the bot issuing a ban.