Get Involved.

Contribute to Nitrux

Contributions can range from something as simple as 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.
  • See our tutorial Making and AppImage in Nitrux.
  • See 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. You improve the system for you and all Nitrux users by reporting bugs.

• Bug Repository for Nitrux

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

Determine if the bug is a bug

You should not file a bug if you are:

1. Requesting new software.
2. When discussing features and existing policies and proposing features or ideas. For such circumstances, please add a feature request.
3. When filing a bug against software not provided by Nitrux.

Submitting a bug report

Before submitting a bug, you should look at the existing bug reports and known issues to verify the bug hasn’t been reported already. You should file a new bug report if the bug has not been reported.

You must specify three things:

1. What do you expect to happen?
2. What happened?
3. If possible, a minimal series of steps is necessary to make it happen, where level 1 is “start the program.”

Additional information about the bug

Some extra options you can use to make your bug report more complete:

1. This bug is a security vulnerability: Please check this only if your bug report describes behavior that a malicious actor could exploit to compromise your security or safety and cause issues such as identity theft or “hi-jacking.”
2. Include an attachment: Add supporting attachments to explain or help others reproduce the bug. An attachment might include a screenshot, a video capture of the problem, or a sample document that triggers the fault.

Feature Requests

Nitrux uses GitHub to keep track of feature requests.

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

Submitting a feature request

Before submitting a feature request, you should look at the existing feature requests and release announcements to verify the feature hasn’t been requested already. You should file a new feature request if the feature has not been requested.

How do I write a reasonable feature request?

1. A feature request should be specific.
2. Include images that would make the request tangible.
3. Reference factual content in support of your request.

What should I not do?

1. Avoid being vague about the benefits (or possible drawbacks).
2. Don’t leave the specifics up to the community. While this is your feature request, it should clearly outline the scope of the request. Unclear requests may be subject to closure as being too broad or unclear.
3. Avoid emotional discussions or motivations.
4. Don’t ask for the moon; be realistic.
5. When filing a feature request against software not provided by Nitrux.

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.

Roadmap

Nitrux has the following estimated release cycle:

• We expect one new release every month.
  

The development schedule for Nitrux:

Week 1	Nitrux release day. Begin work for next release.
Week 2	Review the list of issues labeled as bugs at our GitHub organization. See the list here. Generate new ISO builds to test fixes.
Week 3	Review 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.