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

use explicit sections on the contact page

Browse Source
This commit is contained in:
Daniel Micay 2020-12-02 19:11:26 -05:00
parent 5f98855412
commit c42bde7daa
1 changed files with 74 additions and 69 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

143
static/contact.html
View File

@ -44,93 +44,98 @@
<a href="#contact">Contact</a> <a href="#contact">Contact</a>
</h1> </h1>
<h2 id="contacting-the-project"> <section id="contacting-the-project">
<a href="#contacting-the-project">Contacting the project</a> <h2>
</h2> <a href="#contacting-the-project">Contacting the project</a>
</h2>
<p>Do not contact us with offers to sell us products or services.</p> <p>Do not contact us with offers to sell us products or services.</p>
<p>Please don't contact the GrapheneOS project or developers to request support / <p>Please don't contact the GrapheneOS project or developers to request support /
device support / features or to report bugs. Use the <a href="#community">community device support / features or to report bugs. Use the <a href="#community">community
platforms</a> and <a href="#reporting-issues">issue trackers</a> listed below. The platforms</a> and <a href="#reporting-issues">issue trackers</a> listed below. The
developers are active on the IRC / Matrix channel but the broader community can 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 usually answer most questions, and this allows the developers to focus their time and
energy on the project.</p> energy on the project.</p>
<p>Email is the preferred way to contact the project. Twitter direct messages are <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 good way to contact 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 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 a message to be read, only as a regular notification that is likely to be missed or
forgotten.</p> forgotten.</p>
<p>Please do not send multiple copies / versions of the same email to different <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, 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 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> copies of the same email in their inbox.</p>
<p>You can contact <a href="mailto:contact@grapheneos.org">contact@grapheneos.org</a> <p>You can contact <a href="mailto:contact@grapheneos.org">contact@grapheneos.org</a>
for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to for topics related to GrapheneOS. Please don't send emails unrelated to GrapheneOS to
this address.</p> this address.</p>
<p>The <a href="mailto:security@grapheneos.org">security@grapheneos.org</a> <p>The <a href="mailto:security@grapheneos.org">security@grapheneos.org</a>
address is for reporting high priority security issues related to GrapheneOS. Please 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 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 priority of emails that are not security reports. Your emails will be treated as a
much lower priority if you misuse this address.</p> much lower priority if you misuse this address.</p>
<p>The email address of the lead developer is <p>The email address of the lead developer is
<a href="mailto:daniel.micay@grapheneos.org">daniel.micay@grapheneos.org</a>.</p> <a href="mailto:daniel.micay@grapheneos.org">daniel.micay@grapheneos.org</a>.</p>
<p>The official Twitter account for the project is <a href="https://twitter.com/GrapheneOS">@GrapheneOS</a> <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 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 <a href="https://twitter.com/DanielMicay">@DanielMicay</a> and is primarily focused on
the privacy and security research/engineering work on GrapheneOS.</p> the privacy and security research/engineering work on GrapheneOS.</p>
</section>
<h2 id="community"> <section id="community">
<a href="#community">Community</a> <h2>
</h2> <a href="#community">Community</a>
</h2>
<p>The official chat room used to discuss the project is the IRC channel #grapheneos <p>The official chat room used to discuss the project is the IRC channel #grapheneos
on irc.freenode.net and on irc.freenode.net and
<a href="https://freenode.logbot.info/grapheneos">publicly logged</a>. The channel is <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> 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> <p>The official subreddit is <a href="https://reddit.com/r/GrapheneOS">/r/GrapheneOS</a>.</p>
</section>
<h2 id="reporting-issues"> <section id="reporting-issues">
<a href="#reporting-issues">Reporting issues</a> <h2>
</h2> <a href="#reporting-issues">Reporting issues</a>
</h2>
<p>Most issues should be reported to the global OS issue tracker for GrapheneOS <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 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 source tree (like the websites) has a dedicated issue tracker. The issue trackers are
listed for reference:</p> listed for reference:</p>
<ul> <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/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/hardened_malloc/issues">hardened_malloc issue tracker</a></li> <li><a href="https://github.com/GrapheneOS/hardened_malloc/issues">hardened_malloc issue tracker</a></li>
</ul> </ul>
<p>Standalone app projects:</p> <p>Standalone app projects:</p>
<ul> <ul>
<li><a href="https://github.com/GrapheneOS/Auditor/issues">Auditor issue tracker</a></li> <li><a href="https://github.com/GrapheneOS/Auditor/issues">Auditor issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/PdfViewer/issues">PDF Viewer issue tracker</a></li> <li><a href="https://github.com/GrapheneOS/PdfViewer/issues">PDF Viewer issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/platform_packages_apps_Updater/issues">Update client issue tracker</a></li> <li><a href="https://github.com/GrapheneOS/platform_packages_apps_Updater/issues">Update client issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/Vanadium/issues">Vanadium (Chromium variant) issue tracker</a></li> <li><a href="https://github.com/GrapheneOS/Vanadium/issues">Vanadium (Chromium variant) issue tracker</a></li>
</ul> </ul>
<p>Services:</p> <p>Services:</p>
<ul>
<li><a href="https://github.com/GrapheneOS/AttestationServer/issues">AttestationServer (attestation.app) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/grapheneos.org/issues">grapheneos.org issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/releases.grapheneos.org/issues">Update server (releases.grapheneos.org) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/connectivitycheck.grapheneos.org/issues">Connectivity check server (connectivitycheck.grapheneos.org) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/mail.grapheneos.org/issues">Mail server (mail.grapheneos.org) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/time.grapheneos.org/issues">HTTPS time server (time.grapheneos.org) issue tracker</a></li>
</ul>
<ul>
<li><a href="https://github.com/GrapheneOS/AttestationServer/issues">AttestationServer (attestation.app) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/grapheneos.org/issues">grapheneos.org issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/releases.grapheneos.org/issues">Update server (releases.grapheneos.org) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/connectivitycheck.grapheneos.org/issues">Connectivity check server (connectivitycheck.grapheneos.org) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/mail.grapheneos.org/issues">Mail server (mail.grapheneos.org) issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/time.grapheneos.org/issues">HTTPS time server (time.grapheneos.org) issue tracker</a></li>
</ul>
</section>
</main> </main>
<footer> <footer>
<a href="/"><img src="/logo.png" width="512" height="512" alt=""/>GrapheneOS</a> <a href="/"><img src="/logo.png" width="512" height="512" alt=""/>GrapheneOS</a>