From c42bde7daa9ea0fbc89e17e7cc07647699a0e3a6 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Wed, 2 Dec 2020 19:11:26 -0500 Subject: use explicit sections on the contact page --- static/contact.html | 179 +++++++++++++++++++++++++++------------------------- 1 file changed, 92 insertions(+), 87 deletions(-) (limited to 'static/contact.html') diff --git a/static/contact.html b/static/contact.html index 7fd45dc4..81ba4133 100644 --- a/static/contact.html +++ b/static/contact.html @@ -44,93 +44,98 @@ Contact -

- 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 IRC / Matrix channel 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 contact@grapheneos.org - for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to - this address.

- -

The security@grapheneos.org - 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 - daniel.micay@grapheneos.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.

- -

- Community -

- -

The official chat room used to discuss the project is the IRC channel #grapheneos - on irc.freenode.net and - publicly logged. The channel is - bridged to Matrix and is available at #grapheneos:matrix.org for Matrix users.

- -

The official subreddit is /r/GrapheneOS.

- -

- Reporting issues -

- -

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:

- - - -

Standalone app projects:

- - - -

Services:

- - - +
+

+ 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 IRC / Matrix channel 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 contact@grapheneos.org + for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to + this address.

+ +

The security@grapheneos.org + 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 + daniel.micay@grapheneos.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.

+
+ +
+

+ Community +

+ +

The official chat room used to discuss the project is the IRC channel #grapheneos + on irc.freenode.net and + publicly logged. The channel is + bridged to Matrix and is available at #grapheneos:matrix.org for Matrix users.

+ +

The official subreddit is /r/GrapheneOS.

+
+ +
+

+ Reporting issues +

+ +

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:

+ + + +

Standalone app projects:

+ + + +

Services:

+ + +