Community

Open-Source Development:

NONOS is open source, which means all of our code repositories (primarily on GitHub) are open for inspection and contribution. If you’re a developer, you can dive into the code, submit pull requests, fix bugs, or build new features. We follow a transparent development process, our roadmap and design discussions are public. Whether you’re experienced with Rust or just learning, there are issues tagged for beginners and we’re happy to mentor new contributors. Every bit of help counts, from writing documentation to improving user interface elements. By contributing code or documentation, you directly help make NONOS better for everyone.

Forums and Chat:

Join our official community forums and chat channels to connect with other NONOS users. We have an active Telegram group and a presence on Twitter (X) for announcements and discussions. Community members use these channels to ask questions, share tips, and help each other. If you run into a snag using NONOS or have a question about a feature, chances are a friendly community member (or a core team member) will be there to assist. It’s a great way to learn best practices and get the most out of NONOS. Our forums also host longer-form discussions, for example, proposals for new features, security research findings, or user experiences. We encourage a respectful, inclusive atmosphere where everyone’s input is valued.

Feedback and Voting:

As a user, your feedback is incredibly important. We regularly collect input on what features to prioritize next. Through community surveys, forum polls, and the upcoming feature voting platform, you can help shape the future of NONOS. Perhaps you want to see support for a new device or have an idea for a killer feature, let us know! We often run community polls on our development portal to decide on things like default app selections or new UI themes. This project thrives on being by the people, for the people.

Bug Bounty and Security Audit Programs:

Security is our mantra, and the community plays a big role here too. We have a bug bounty program that rewards security researchers (and even keen-eyed users) for responsibly disclosing vulnerabilities they find. If you discover a bug or a security issue in NONOS, report it through our official bug bounty portal, you might earn recognition and a reward depending on severity. By participating, you help ensure NONOS remains robust. We also organize periodic community-driven security audits, where experienced volunteers collectively review parts of the codebase in “audit weeks” and share the results.

Community Economy & Token (Future):

We’re exploring an innovative way to incentivize community contributions. The concept of a native token, SNOX, has been introduced. In the future, active community members might earn SNOX rewards for actions like contributing computing power to the NONOS mesh network, testing new releases, or creating useful capsules (apps). This would align the community with the growth of the platform, as NONOS becomes more widely used, those who helped build it share in the success. While this system is still under development and subject to regulatory considerations, it shows our commitment to a user-owned platform rather than one controlled solely by a company. Keep an eye on our announcements for more on this “earn by contributing” model.

Events and Outreach:

We love engaging with our community through hackathons, webinars, and (when possible) real-world meetups. Look out for our online events, for example, a live-streamed Q&A with the NONOS development team, or a workshop on creating your own capsule app. We also attend cybersecurity conferences and open-source summits; if you’re there, come say hi at our booth or talk. Community members have even started local NONOS user groups in a few cities, check our community page to see if one exists near you or learn how to start one.