Stop by to share your experiences, ask questions and discuss topics with other users and developers in our growing community.
Contribute to Nitrux
Contributions can range from something as simple as testing our ISO’s to the more intensive tasks such as maintaining or producing code for Nitrux.
We divide development into several areas, managing different parts of the project. Find out the various tasks you can help with listed below:
- Development, including programming and packaging
- UI Design for Apps
- Documentation and Translation
- Marketing and Website
- Quality Assurance, including testing and bug triaging
Once you get started contributing, you’ll want to create a GitHub account, allowing you to work on bugs, design blueprints, and much more.
Everyone can participate in the Nitrux community on many levels, from merely 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!.
Alongside the communities at Facebook and MeWe, you can communicate with developers or others in the community by using one of the following websites:
Gitter is an open-source instant messaging and chat room system for developers and users of GitHub and Gitlab repositories. Gitter provides its software as a software-as-a-service, with a free option providing all essential features and paid subscription options for individuals and organizations.
You will find the following Nitrux channels on the Gitter network:
- Nitrux/public – Public channel.
You may wish to have software on your system that is currently not available as an AppImage. While you are more than 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. If you’re interested in learning to package software, feel free to visit the AppImage documentation here.
We’re always looking to improve our systems, mainly when they’re not functioning as expected. By reporting bugs, you improve the system not only for you but for all Nitrux users.
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.
You can also find us on Open Collective if you’d like to contribute to our goals.
Nitrux has the following estimated release cycle:
- We expect one minor release approximately every month.
- We expect One major release after approximately ten months (or every ten minor releases).
The development schedule for Nitrux:
|week 1||Nitrux release day. Build ISOs from their respective branches.|
|week 2||Please 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||Please 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 website and documentation to reflect the new version.
Prepare last-minute fixes, push updates to packages, and rebuild ISO files for stable and development branches.
© 2017-2022 Some Rights Reserved. Made with ♥ by Nitrux Latinoamericana S.C.
Any trademarks or logos used on this site are the property of their respective owners.