security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

add notes on preferred contact method

Browse Source
This commit is contained in:
Daniel Micay 2020-06-05 01:32:01 -04:00
parent 00b19dc34e
commit c1e81c8187
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
static/contact.html
View File

@ -42,32 +42,52 @@
<h1 id="contact">
<a href="#contact">Contact</a>
</h1>
<p>Please don't contact the GrapheneOS project or developers to request support or to
report bugs. Use the community platforms and issue trackers listed below.</p>
<p>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 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.</p>
<p>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.</p>
<p>You can contact <a href="mailto:contact@grapheneos.org">contact@grapheneos.org</a> for topics
related to GrapheneOS. The <a href="mailto:security@grapheneos.org">security@grapheneos.org</a>
address can be used for high priority security issues. The email address of
the lead developer is <a href="mailto:daniel.micay@grapheneos.org">daniel.micay@grapheneos.org</a>
as a fallback option for anything else.</p>
<p>The official Twitter account for the project is <a href="https://twitter.com/GrapheneOS">@GrapheneOS</a>
which is used for official announcements. The account of the lead developer is
<a href="https://twitter.com/DanielMicay">@DanielMicay</a> and is primarily focused on
the privacy and security research/engineering work on GrapheneOS.</p>
<h2 id="community">
<a href="#community">Community</a>
</h2>
<p>The official chat room used to discuss the project is the IRC channel #grapheneos
on irc.freenode.net and
<a href="https://freenode.logbot.info/grapheneos">publicly logged</a>. The channel is
bridged to Matrix and is available at #grapheneos:matrix.org for Matrix users.</p>
<p>The official subreddit is <a href="https://reddit.com/r/GrapheneOS">/r/GrapheneOS</a>.</p>
<h2 id="reporting-issues">
<a href="#reporting-issues">Reporting issues</a>
</h2>
<p>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:</p>
<ul>
<li><a href="https://github.com/GrapheneOS/os_issue_tracker/issues">OS issue tracker</a> for all GrapheneOS repositories that are not standalone projects</li>
<li><a href="https://github.com/GrapheneOS/Vanadium/issues">Vanadium (Chromium variant) issue tracker</a></li>