Skip to content

Commit efb817f

Browse files
committed
merge mostly redundant FAQ section into future devices
1 parent c7cb722 commit efb817f

File tree

2 files changed

+6
-28
lines changed

2 files changed

+6
-28
lines changed

static/faq.html

Lines changed: 5 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,6 @@ <h2><a href="#table-of-contents">Table of contents</a></h2>
5454
<li><a href="#supported-devices">Which devices are supported?</a></li>
5555
<li><a href="#recommended-devices">Which devices are recommended?</a></li>
5656
<li><a href="#future-devices">Which devices will be supported in the future?</a></li>
57-
<li><a href="#when-devices">When will more devices be supported?</a></li>
5857
<li><a href="#legacy-devices">Why are older devices no longer supported?</a></li>
5958
<li><a href="#which-legacy-devices">Which devices did GrapheneOS support in the past?</a></li>
6059
<li><a href="#device-lifetime">How long will GrapheneOS support my device for?</a></li>
@@ -346,34 +345,12 @@ <h3><a href="#future-devices">Which devices will be supported in the future?</a>
346345
and dedicated towards it. Releases for each supported device need to be robust and
347346
stable, with all standard functionality working properly and testing for each of the
348347
releases.</p>
349-
</article>
350348

351-
<article id="when-devices">
352-
<h3><a href="#when-devices">When will more devices be supported?</a></h3>
353-
354-
<p>Broader device support can only happen after the community (companies,
355-
organizations and individuals) steps up to make substantial, ongoing contributions to
356-
making the existing device support sustainable. Once the existing device support is
357-
more sustainable, early research and development work for other devices can begin.
358-
Once a device is deemed to be a worthwhile target, the project needs maintainers to
359-
develop and maintain support for it including addressing device-specific issues that
360-
are uncovered, which will include issues uncovered in the device support code by
361-
GrapheneOS hardening features.</p>
362-
363-
<p>It's not really a matter of time but rather a need for community support for the
364-
project increasing. As an open source project, the way to get something to happen in
365-
GrapheneOS is to contribute to it, and this is particularly true for device support
366-
since it's very self-contained and can be delegated to separate teams for each
367-
device. If you want to see more devices supported sooner, you should get to work on
368-
identifying good devices with full support for alternative operating systems with
369-
verified boot, etc. and then start working on integrating and testing support.</p>
370-
371-
<p>It should also be clear that the expectation is for people to buy a device to run
372-
GrapheneOS, rather than GrapheneOS supporting their existing devices. This will only
373-
become more true if GrapheneOS is successful enough to accomplish the goal of having
374-
devices produced based on an SoC reference design with minor improvements for privacy
375-
and security. Broad device support is the opposite of what the project wants to
376-
achieve in the long term.</p>
349+
<p>The expectation is for people to buy a device to run GrapheneOS, rather than
350+
GrapheneOS supporting their existing devices. In the long term, we plan to
351+
partner with OEMs to have devices produced meeting all our requirements,
352+
providing additional privacy/security features beyond them and ideally shipping
353+
with GrapheneOS.</p>
377354
</article>
378355

379356
<article id="legacy-devices">

static/js/redirect.js

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ const redirects = new Map([
2323
["/usage#google-camera", "/usage#pixel-camera"],
2424

2525
["/faq#dns", "/faq#custom-dns"],
26+
["/faq#when-devices", "/faq#future-devices"],
2627

2728
["/hiring#qualitifations", "/hiring#qualifications"],
2829

0 commit comments

Comments
 (0)