Get Involved.

Contribute to Nitrux

Contributions can range from testing our ISO to more intensive tasks such as maintaining or producing code for Nitrux. Everyone can participate in the Nitrux community on many levels, from advising fellow Nitrux users to becoming a maintainer. Any contribution, even the smallest, is valued. We welcome everybody to improve Nitrux and spread Free Software!

We divide development into several areas, managing different parts of the project. Find out the various tasks you can help with listed below:

• Artwork
• Development, including programming and packaging
• UI Design for Apps
• Documentation and Translation
• Marketing and Website
• Quality Assurance, including testing and bug triaging

Once you start contributing, you’ll want to create a GitHub account, allowing you to work on bugs, design blueprints, and more.

• Nitrux@GitHub.

Public Forum

Users can find the public forum at our GitHub organization under the Discussions section.

• Please open a new discussion at our GitHub organization.

Social Media

You can communicate with developers and other users in the community by using one of the following social media sites:

• Twitter
• Facebook
• YouTube
• Mastodon
• Instagram
• Threads
• MeWe

Instant Chat

You will find the following Nitrux channels on Gitter.

• Nitrux/public – Public channel.

You can find Nitrux on Telegram.

• Nitrux @ Telegram – Group for English-speaking users.

Packaging

You may wish to have software on your system currently unavailable as an AppImage. While you are welcome to submit a bug and wait for someone else to package the software you want, you can also improve and contribute to the community by packaging software.

• To learn to package software as an AppImage, visit the AppImage documentation here.
• Users can also create their AppImages; to do that, see the following tutorials.
  • More information is in our tutorial: Making and AppImage in Nitrux.
  • More information is in our tutorial: Making a web application AppImage in Nitrux.

Report Bugs

We’re always looking to improve our systems, mainly when they’re not functioning as expected. By reporting bugs, you improve the system for you and all Nitrux users.

• Please open an issue at the Bug Repository for Nitrux and use the template to create a bug report.

Nitrux uses GitHub to keep track of bugs and their fixes.

Feature Requests

Nitrux uses GitHub to keep track of feature requests.

• Please open an issue at the Nitrux Bug Repository, but instead of creating a bug report, use the template for feature requests.

Sponsor Nitrux

Your support can fund various needs of the project. Everyone can contribute to Nitrux, whether you are a coder or a community builder. But if you would instead contribute by directly donating money, we are happy to accept that.

You can also check our current bounties at Bountysource if you’d like to contribute either code or financial support.

• Nitrux@Bountysource.

You can also find us on Open Collective if you’d like to contribute to our goals.

• Nitrux@Open Collective.

You can also find us on Ko-fi if you’d like to contribute to our goals.

• Nitrux@Ko-fi.

Release Schedule

Nitrux has the following monthly estimated fixed-release cycle:

• We expect one new release every 30-31 days, with every new release (Nitrux+0) being supported for the next 30-31 days starting from the day we publish the Release Announcement.
  • 🔰 Information: As the table below notes, there’s no intermediary release, i.e., no “development” release of Nitrux available to the public due to our fast release cycle. All testing is done internally.
  • 🔰 Information: It’s also worth mentioning that Nitrux does not follow the convention of major and minor releases; there are simply releases. New versions with a suffix x.x.1 are not maintenance or minor releases, just like releases with the suffix x.x.0 are not major releases.
• After the 30-31 days period concludes and a new release is available, the previous release (now Nitrux-1) is only supported for upgrades (not for reporting issues or bugs) for the next 30-31 days.
• Once a new release is available, the previous release (now Nitrux-2) is no longer supported as it had passed 60-62 days after it was released. Additionally, as explained in our tutorial, Filesystem, Security, Privacy, and Anonymization Features in Nitrux, user passwords are valid for 90 days, which means that on the 91st day, the Live user credentials won’t work. Thus, that release wouldn’t be installable.

TL;DR

• Nitrux+0: This is the current release, which is actively supported.
• Nitrux-1: This would be the previous release to the current. We still support this release for upgrades (not reporting issues or bugs) after the release of Nitrux+0.
• Nitrux-2: This would be the release before the previous one, which becomes unsupported after approximately 60-62 days from its release and becomes non-installable on the 91st day due to password expiration.

The development schedule for Nitrux is the following:

Week 1	Nitrux release day. Create an OTA update archive to upgrade the previous release to the latest. Begin work for the next release.
Week 2	A review of the list of issues labeled as bugs at our GitHub organization. See the list here. Generate new ISO builds to test fixes.
Week 3	A review of the list of issues labeled as feature requests at our GitHub organization. See the list here. Generate new ISO builds to test new features.
Week 4	Perform QA tasks; prepare for release day. Update the website and documentation. Prepare last-minute fixes, push package updates, and rebuild ISO files.