diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2021-03-04 18:07:52 -0500 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2021-03-04 18:07:52 -0500 |
| commit | b4f5326c8b29f16d44262dff54b36dca8e6814af (patch) | |
| tree | 9b6d9f31a44263742eb31ac33ce16718c8be9dcd /static/faq.html | |
| parent | 0956dba241fbe6daafd0c049f60f1485b79e237e (diff) | |
move upstream contributions section to FAQ
Diffstat (limited to 'static/faq.html')
| -rw-r--r-- | static/faq.html | 22 |
1 files changed, 21 insertions, 1 deletions
diff --git a/static/faq.html b/static/faq.html index 4460d064..4b0fcaa6 100644 --- a/static/faq.html +++ b/static/faq.html @@ -26,7 +26,7 @@ <link rel="stylesheet" href="/grapheneos.css?29"/> <link rel="manifest" href="/manifest.webmanifest"/> <link rel="license" href="/LICENSE.txt"/> - <script type="module" src="/js/redirect.js?9"></script> + <script type="module" src="/js/redirect.js?10"></script> </head> <body> <header> @@ -117,6 +117,7 @@ <li><a href="#install">How do I install GrapheneOS?</a></li> <li><a href="#build">How do I build GrapheneOS?</a></li> <li><a href="#donate">How can I donate to GrapheneOS?</a></li> + <li><a href="#upstream">Does GrapheneOS make upstream contributions?</a></li> <li><a href="#company">Will GrapheneOS create a company?</a></li> <li><a href="#copyright-and-licensing">Who owns the GrapheneOS code and how is it licensed?</a></li> <li><a href="#trademark">What about the GrapheneOS name and logo?</a></li> @@ -1135,6 +1136,25 @@ support the GrapheneOS project. GrapheneOS is entirely funded by donations.</p> </article> + <article id="upstream"> + <h2><a href="#upstream">Does GrapheneOS make 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> + </article> + <article id="company"> <h2><a href="#company">Will GrapheneOS create a company?</a></h2> |