Get involved
Orivon is open source and built in public, with its community. You do not need to write code to move it forward, and you do not need anyone's approval to start.
Ways to contribute
Code
Orivon is TypeScript on Electron, with no compiler needed. Fix an issue, improve a feature, or port an app. Start with CONTRIBUTING.md.
Use it and report
Daily use finds what tests miss. Send a report with Report a problem in the browser, or open an issue on GitHub.
Content and growth
Posts, threads, articles, videos and translations that explain what Orivon does. Share them in Discord's content & ideas channel.
Community
Welcome newcomers, answer questions, join events, and help run a regional channel.
Design and writing
Interface design, illustrations, and documentation like this page.
Partnerships
Projects and people in Web3 who want to build with Orivon or bring it to their audience.
Open roles change often, so they live in Discord's roles-openings channel rather than here.
Start in three steps
- Join the Discord and introduce yourself in introductions.
- Read the contributor path in contributor-path: the community roles, and what earns each one.
- Start. Contribute in the way that suits you. To propose something bigger, or to apply for a role, open a ticket in open-ticket and the team will reply there.
The contributor path
| Role | Who it is for |
|---|---|
| Orivon Cadet | New, active supporters: in Discord, on X, sharing ideas and feedback |
| X Publisher | Regular authors of original posts about Orivon, with a private channel to the core team |
| Involved | Trusted contributors who support the project consistently and meaningfully |
| Elite | The core team: trust, responsibility and long-term contribution |
Community roles such as Contributor, Creator, Vanguard and Legend recognise activity, educational content and long-term dedication; roles-details explains each one.
How contributions are recognised
Every contribution is tracked, so none of it depends on someone remembering:
- Code and documentation: your commits and pull requests on GitHub.
- Content: what you share in content & ideas, recorded in content-merits.
- Community growth: recorded in growth-merits.
- Anything else: post a self-report in contrib-reports. A spreadsheet you keep up to date works best; the channel's pinned message has a template and the current priorities. A ✅ from the team means it has been recorded.
Each week the team picks a Contributor Spotlight: the people whose work made the clearest difference, with the reason stated publicly.
Core team and partnerships
The core team is made of contributors who are committed (working actively with the rest of the team), trusted (built over time) and coordinated (a shared way of working and compatible hours). To be considered, fill in the core team and partnership form and open a ticket.
Developers can apply through the developer form.
Partnerships work the same way, for projects, creators and people with reach in Web3. They give direct access to the core team without the core-team criteria above.