move upstream contributions to a section
This commit is contained in:
parent
a66e475a5a
commit
c8ec09a05a
@ -89,20 +89,6 @@
|
|||||||
peripherals, camera, quick tiles), etc. along with more complex user-facing privacy
|
peripherals, camera, quick tiles), etc. along with more complex user-facing privacy
|
||||||
and security features with their own UX.</p>
|
and security features with their own UX.</p>
|
||||||
|
|
||||||
<p>GrapheneOS has made substantial contributions to the privacy and security of the
|
|
||||||
Android Open Source Project, along with contributions to the Linux kernel, LLVM,
|
|
||||||
OpenBSD and other projects. Much of our past work is no longer part of the downstream
|
|
||||||
GrapheneOS project because we've successfully landed many patches upstream. We've had
|
|
||||||
even more success with making suggestions and participating in design discussions to
|
|
||||||
steer things in the direction we want. Many upstream changes in AOSP such as removing
|
|
||||||
app access to low-level process, network, timing and profiling information originated
|
|
||||||
in the GrapheneOS project. The needs of the upstream projects are often different from
|
|
||||||
ours, so they'll often reimplement the features in a more flexible way. We've almost
|
|
||||||
always been able to move to using the upstream features and even when we still need
|
|
||||||
our own implementation it helps to have the concepts/restrictions considered by the
|
|
||||||
upstream project and apps needing to be compatible with it. Getting features upstream
|
|
||||||
often leads to an improved user experience and app compatibility.</p>
|
|
||||||
|
|
||||||
<p>See the new <a href="/features">features page</a> for more details on GrapheneOS
|
<p>See the new <a href="/features">features page</a> for more details on GrapheneOS
|
||||||
features.</p>
|
features.</p>
|
||||||
|
|
||||||
@ -121,6 +107,24 @@
|
|||||||
href="https://attestation.app/tutorial">tutorial</a>. These also support other
|
href="https://attestation.app/tutorial">tutorial</a>. These also support other
|
||||||
operating systems.</p>
|
operating systems.</p>
|
||||||
|
|
||||||
|
<section id="upstream">
|
||||||
|
<h2><a href="#upstream">Upstream contributions</a></h2>
|
||||||
|
|
||||||
|
<p>GrapheneOS has made substantial contributions to the privacy and security of the
|
||||||
|
Android Open Source Project, along with contributions to the Linux kernel, LLVM,
|
||||||
|
OpenBSD and other projects. Much of our past work is no longer part of the downstream
|
||||||
|
GrapheneOS project because we've successfully landed many patches upstream. We've had
|
||||||
|
even more success with making suggestions and participating in design discussions to
|
||||||
|
steer things in the direction we want. Many upstream changes in AOSP such as removing
|
||||||
|
app access to low-level process, network, timing and profiling information originated
|
||||||
|
in the GrapheneOS project. The needs of the upstream projects are often different from
|
||||||
|
ours, so they'll often reimplement the features in a more flexible way. We've almost
|
||||||
|
always been able to move to using the upstream features and even when we still need
|
||||||
|
our own implementation it helps to have the concepts/restrictions considered by the
|
||||||
|
upstream project and apps needing to be compatible with it. Getting features upstream
|
||||||
|
often leads to an improved user experience and app compatibility.</p>
|
||||||
|
</section>
|
||||||
|
|
||||||
<section id="never-google-services">
|
<section id="never-google-services">
|
||||||
<h2><a href="#never-google-services">No Google apps or services</a></h2>
|
<h2><a href="#never-google-services">No Google apps or services</a></h2>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user