k1nq/TREK
1
0
Fork 0
mirror of https://github.com/mauriceboe/TREK.git synced 2026-06-19 05:11:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: Add Trademark policy

Browse Source
This commit is contained in:
jubnl
2026-04-26 15:36:34 +02:00
parent 0eca6d54a1
commit 90d86eda61
1 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TRADEMARKS.md
+14 -14
View File
@@ -20,14 +20,14 @@ goodwill, or designs (our "Marks").
Whenever you use our Marks, you must always do so in a way that does not mislead Whenever you use our Marks, you must always do so in a way that does not mislead
anyone about exactly who is the source of the software. For example, you cannot anyone about exactly who is the source of the software. For example, you cannot
say you are distributing the "TREK" software when you're distributing a modified say you are distributing TREK when you're distributing a modified version of it,
version of it, because people would think they would be getting the same because people would think they would be getting the same software that they
software that they can get directly from us when they aren't. You also cannot can get directly from us when they aren't. You also cannot use our Marks on
use our Marks on your website in a way that suggests that your website is an your website in a way that suggests that your website is an official TREK
official TREK website or that we endorse your website. But, if true, you can website or that we endorse your website. But, if true, you can say you like
say you like TREK, that you participate in the TREK community, that you are TREK, that you participate in the TREK community, that you are providing an
providing an unmodified version of TREK, or that you wrote a guide describing unmodified version of TREK, or that you wrote a guide describing how to use
how to use TREK. TREK.
This fundamental requirement, that it is always clear to people what they are This fundamental requirement, that it is always clear to people what they are
getting and from whom, is reflected throughout this policy. It should also getting and from whom, is reflected throughout this policy. It should also
@@ -56,7 +56,7 @@ in any way.
## Distribution of executable code that you have compiled, or modified code ## Distribution of executable code that you have compiled, or modified code
You may use the word Mark "TREK", but not any TREK logos, to truthfully You may use the word mark "TREK", but not any TREK logos, to truthfully
describe the origin of the software that you are providing, that is, that the describe the origin of the software that you are providing, that is, that the
code you are distributing is a modification of TREK. You may say, for example, code you are distributing is a modification of TREK. You may say, for example,
that "this software is derived from the source code for TREK." that "this software is derived from the source code for TREK."
@@ -94,11 +94,11 @@ redistributed:
## Statements about your software's relation to TREK ## Statements about your software's relation to TREK
You may use the word Mark, but not TREK logos, to truthfully describe the You may use the word mark, but not TREK logos, to truthfully describe the
relationship between your software and ours. Our Mark should be used after a relationship between your software and ours. The word mark "TREK" should be
verb or preposition that describes the relationship between your software and used after a verb or preposition that describes the relationship between your
ours. So you may say, for example, "Bob's app for TREK" but may not say "Bob's software and ours. So you may say, for example, "Bob's app for TREK" but may
TREK app." Some other examples that may work for you are: not say "Bob's TREK app." Some other examples that may work for you are:
* [Your software] uses TREK * [Your software] uses TREK
* [Your software] is powered by TREK * [Your software] is powered by TREK