Contributing
August 3, 2026 · View on GitHub
Spread the word
This is the most impactful contribution you can make.
Spread the word. Online on your favorite social media channels. Offline to your friends and family who are looking for a privacy-friendly alternative to big tech.
Engage with the community
Just hang around, enjoy the vibe. The Ente community — the people who are building Ente, and the people who are using Ente — hang out at various places depending on their proclivity:
Just being around might seem a small thing, but it provides us energy. Knowing that there is a community of people who care for what we are building, who want us to do better.
Translate
Visit our Crowdin projects to help with translations:
| Project | |
|---|---|
| Mobile |  |
| Web / Desktop |  |
If your language is not listed for translation, please create a GitHub issue to have it added. It is okay to have partial translations. Once ~90% of the strings in a language get translated, we will start surfacing it in the apps.
Document
The help guides and FAQs for users of Ente products are also open source, and can be edited in a wiki-esque manner by our community members. More than the quantity, we feel this helps improve the quality and approachability of the documentation by bringing in more diverse viewpoints and familiarity levels.
See docs/ for how to edit these documents.
Code contributions
Consider contributing in ways other than code. Our problem is not a lack of code.
If you do contribute code, keep changes small and well-scoped: for example, fixing a specific bug or adding more custom icons to auth.
For anything that changes UX, however small, please talk to us (on GitHub or Discord) before writing code. Whether a change fits the product is not something a diff can show, and we don't want you to spend effort on something we then cannot merge.
Please don't open PRs with big product changes. These will not get merged. If you wish for a new feature or a behaviour change, start a discussion, or add your perspective to the (likely) existing thread about it.
On agents: LLM-generated code is not a problem in itself, but writing code is not the bottleneck; verifying it is. What makes your contribution valuable is the testing and judgement that you add.
Ensure that you test everything that you touch. In your PR, include before / after screenshots, and clearly indicate the tests that you performed.
Leave a review or star
If you haven't already done so, consider starring this repository or leaving a review on PlayStore, AppStore or AlternativeTo.