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

add trademark information

Browse Source
This commit is contained in:
Daniel Micay 2020-12-30 23:52:39 -05:00
parent 5b985a2fe1
commit c77f20e27f
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/faq.html
View File

@ -114,6 +114,7 @@
<li><a href="#anti-theft">Does GrapheneOS provide Factory Reset Protection?</a></li> <li><a href="#anti-theft">Does GrapheneOS provide Factory Reset Protection?</a></li>
<li><a href="#bundled-apps">Why aren't my favorite apps bundled with GrapheneOS?</a></li> <li><a href="#bundled-apps">Why aren't my favorite apps bundled with GrapheneOS?</a></li>
<li><a href="#copyright-and-licensing">Who owns the GrapheneOS code and how is it licensed?</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>
<li><a href="#roadmap">What is the roadmap for GrapheneOS?</a></li> <li><a href="#roadmap">What is the roadmap for GrapheneOS?</a></li>
<li><a href="#company">Will GrapheneOS create a company?</a></li> <li><a href="#company">Will GrapheneOS create a company?</a></li>
<li><a href="#install">How do I install GrapheneOS?</a></li> <li><a href="#install">How do I install GrapheneOS?</a></li>
@ -1066,6 +1067,25 @@
owned by Daniel Micay, which was the case for nearly everything in the project.</p> owned by Daniel Micay, which was the case for nearly everything in the project.</p>
</article> </article>
<article id="trademark">
<h2><a href="#trademark">What about the GrapheneOS name and logo?</a></h2>
<p>The GrapheneOS name and logo are trademarks of the GrapheneOS project. These
marks are the process of being formally registered in Canada and the US. In the
meantime, they're protected as unregistered trademarks.</p>
<p>Derivatives of GrapheneOS that are being published/redistributed should replace
the GrapheneOS branding with their own. It needs to be clear to users that it's a
distinct OS based on GrapheneOS. Forks of GrapheneOS are not GrapheneOS itself and
should not be presented that way.</p>
<p>Only unofficial builds of the official GrapheneOS sources should be referred to
as unofficial builds. An unofficial build is a build of the official GrapheneOS
sources with the update server URL changed to another server. A project making
modifications beyond that isn't simply an unofficial build and should be presented
as a distinct OS based on GrapheneOS.</p>
</article>
<article id="roadmap"> <article id="roadmap">
<h2><a href="#roadmap">What is the roadmap for GrapheneOS?</a></h2> <h2><a href="#roadmap">What is the roadmap for GrapheneOS?</a></h2>