GrapheneOS has a very active community primarily based around the official chat rooms on Matrix.
The links below will take you to the Element web client, which uses matrix.org as the homeserver by default. However, you can use the client and homeserver of your choice to join our rooms.
|#grapheneos:grapheneos.org||Best place to request support, ask questions or get involved in the project|
|#offtopic:grapheneos.org||Discuss topics not strictly related to GrapheneOS|
|#dev:grapheneos.org||Discuss GrapheneOS app and OS development|
|#testing:grapheneos.org||Provide feedback on Alpha and Beta channel app and OS releases|
|#infra:grapheneos.org||Infrastructure monitoring and discussion|
|#media:grapheneos.org||Discuss GrapheneOS in news articles and other media coverage|
The official GrapheneOS space groups together all of the official rooms along with members of the community who join the space. You can join the space at #community:grapheneos.org
We have an official forum for longer form posts, which will be more publicly accessible and easier to search. We are currently using Flarum for our forum.
We have an official Twitter community for GrapheneOS discussions. You currently need to be logged in to access the new Twitter community feature. Discussions about GrapheneOS and apps/services to use on GrapheneOS are welcome. Once you join the community, you can post a thread in the community as an alternative to posting to your own timeline. It will be shown to other members of the community rather than to your followers outside the community. It's essentially a discussion forum within Twitter.
The official subreddit is /r/GrapheneOS. The subreddit is currently primarily used for announcements and you should use the Matrix rooms to seek support or participate in the community.
Contacting the project
Do not contact us with offers to sell us products or services.
Please don't contact the GrapheneOS project or developers to request support / device support / features or to report bugs. Use the community platforms and issue trackers listed below. The developers are active on the Matrix room but the broader community can usually answer most questions, and this allows the developers to focus their time and energy on the project.
Email is the preferred way to contact the project. Twitter direct messages are checked much less frequently. A public @reply in a tweet is not a good way to contact the project. It is not considered sending a message by Twitter and is not queued up as a message to be read, only as a regular notification that is likely to be missed or forgotten.
Please do not send multiple copies / versions of the same email to different addresses. Either send it to a single address or CC the other addresses. In general, it's the same person handling every email address, and they don't need to see multiple copies of the same email in their inbox.
You can contact firstname.lastname@example.org for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to this address.
The email@example.com address is for reporting high priority security issues related to GrapheneOS. Please don't send other kinds of emails to this address. It is not a way of increasing the priority of emails that are not security reports. Your emails will be treated as a much lower priority if you misuse this address.
The email address of the lead developer is firstname.lastname@example.org.
The official Twitter account for the project is @GrapheneOS which is used for official announcements. The account of the lead developer is @DanielMicay and is primarily focused on the privacy and security research/engineering work on GrapheneOS.
The official Mastodon account for the project is @GrapheneOS@grapheneos.social which is used for official announcements. The account of the lead developer is @DanielMicay@grapheneos.social and is primarily focused on the privacy and security research/engineering work on GrapheneOS.
Most issues should be reported to the global OS issue tracker for GrapheneOS sub-projects. However, standalone projects and anything outside of the GrapheneOS source tree (like the websites) has a dedicated issue tracker. The issue trackers are listed for reference:
- OS issue tracker for all GrapheneOS repositories that are not standalone projects
- hardened_malloc issue tracker
- Update client issue tracker
- Talkback issue tracker
- Server infrastructure issue tracker (for issues applying across services)
- AttestationServer (attestation.app) issue tracker
- GrapheneOS site (grapheneos.org) issue tracker
- Update server (releases.grapheneos.org) issue tracker
- Connectivity check / time server (grapheneos.network) issue tracker
- Mail server (mail.grapheneos.org) issue tracker
- App repository (apps.grapheneos.org) issue tracker
- GrapheneOS Matrix server (matrix.grapheneos.org) issue tracker
- GrapheneOS discussion forum (discuss.grapheneos.org) issue tracker