|
| 1 | +--- |
| 2 | +title: Trademark Policy |
| 3 | +layout: docs |
| 4 | +origfile: Trademark-Policy.md |
| 5 | +origtitle: Trademark-Policy |
| 6 | +permalink: /docs/Trademark-Policy |
| 7 | +redirect_from: |
| 8 | + - /docs/Trademark_Policy/ |
| 9 | + - /wiki/Trademark_Policy/ |
| 10 | +--- |
| 11 | +* TOC |
| 12 | +{:toc} |
| 13 | +== THE RED ECLIPSE MARK POLICY == |
| 14 | + |
| 15 | +== General Guidelines == |
| 16 | + |
| 17 | +The purpose of the Red Eclipse mark policy is to encourage the widespread use of |
| 18 | +Red Eclipse marks by the community while controlling the use of the marks in |
| 19 | +order to avoid confusion on the part of software users and the general public, |
| 20 | +to maintain the value of the image and reputation of the marks and to protect |
| 21 | +them from inappropriate or unauthorized use. |
| 22 | + |
| 23 | +Any use of any Red Eclipse mark must be in accordance with this policy. Any use |
| 24 | +that does not comply with our trademark policy is not authorized. |
| 25 | + |
| 26 | +Marks cover the following items: The name "Red Eclipse", the Red Eclipse emblem |
| 27 | +(without text) and the Red Eclipse logo (with word art text). |
| 28 | + |
| 29 | +Do not assume that this policy will answer every question about the use of Red |
| 30 | +Eclipse marks, if in doubt, contact the Red Eclipse project. |
| 31 | + |
| 32 | + |
| 33 | +== Declaration == |
| 34 | + |
| 35 | +The Red Eclipse project delcares that: |
| 36 | + |
| 37 | +1. For the purposes of tax, trademarks, copyrights, and ownership, Red Eclipse |
| 38 | + is considered to be the property of Mr Quinton Reeves as sole proprietor |
| 39 | + executed from the province of Australia, as is produced as a hobby project |
| 40 | + for no profit. |
| 41 | + |
| 42 | +2. For the purposes of identifying adjoining identifying names for tax, |
| 43 | + trademarks, copyrights, and ownership, the following terms are considered |
| 44 | + synonymous with the sole proprietor of the project, Mr Quinton Reeves: |
| 45 | + - Red Eclipse |
| 46 | + - Red Eclipse Community |
| 47 | + - Red Eclipse Developer(s) |
| 48 | + - Red Eclipse Owner(s) |
| 49 | + - Red Eclipse Project |
| 50 | + - Red Eclipse Team |
| 51 | + |
| 52 | +3. The official contact methods are, but not limited to: |
| 53 | + |
| 54 | + - Discussions: https://redeclipse.net/discuss |
| 55 | + - Bugs and Issues: https://redeclipse.net/issues |
| 56 | + |
| 57 | +4. Personal information and contact details for Mr Quinton Reeves is available |
| 58 | + to eligible organisations on request. Please email: [email protected] |
| 59 | + |
| 60 | + |
| 61 | +== Permitted Use == |
| 62 | + |
| 63 | +You may use the marks without prior written permission (subject to the following |
| 64 | +terms): |
| 65 | + |
| 66 | +1. To refer to the Red Eclipse software in substantially unmodified form. |
| 67 | + |
| 68 | + "Substantially unmodified" for source code means built from the source code |
| 69 | + provided by The Red Eclipse project, possibly with minor modifications |
| 70 | + including but not limited to: the enabling or disabling of certain features by |
| 71 | + default, translations into other languages, changes required for compatibility |
| 72 | + with a particular operating system distribution, the inclusion of bug-fix |
| 73 | + patches, or the bundling of additional extensions. |
| 74 | + |
| 75 | + "Substantially unmodified" for gameplay and art means using the game data |
| 76 | + provided by The Red Eclipse project, possibly with minor modifications, for |
| 77 | + example including additional maps, artwork, and sounds. The gameplay and art |
| 78 | + needs to closely resemble that of Red Eclipse in it's unmodified form, and not |
| 79 | + create an unfair advantage in gameplay. |
| 80 | + |
| 81 | + Example: You may modify Red Eclipse to start in windowed mode by default, but |
| 82 | + if you set the gravity in the game to zero, this counts as a |
| 83 | + substantial modification. |
| 84 | + |
| 85 | + Example: You may modify the laser beams to be green instead of purple, but if |
| 86 | + you change all the weapon models into fresh fruits, this counts as a |
| 87 | + substantial modification. |
| 88 | + |
| 89 | +2. To identify Red Eclipse as a distinct component of a software offering. |
| 90 | + |
| 91 | +3. To factually refer to The Red Eclipse project itself, its products, or its |
| 92 | + protocols. |
| 93 | + |
| 94 | + Example: You may use "Bob's Add-ons for Red Eclipse" or |
| 95 | + "Bob's forum for Red Eclipse" but not "Bob's Red Eclipse". |
| 96 | + |
| 97 | +4. When referring to Red Eclipse that is substantially modified, to say |
| 98 | + that such software is a "derivative of" or "based on" Red Eclipse. You may |
| 99 | + use the marks as part of the name of a product designed to work with Red |
| 100 | + Eclipse, so long as the name as a whole (via its other components) clearly |
| 101 | + and unambiguously distinguishes the product from Red Eclipse, and the |
| 102 | + general presentation of the product does not imply any official association |
| 103 | + or identity with the Red Eclipse project. |
| 104 | + |
| 105 | + |
| 106 | +== Non Permitted Use == |
| 107 | + |
| 108 | +You may not use the marks in the following ways: |
| 109 | + |
| 110 | +1. In any way likely to cause confusion as to the identity of the Red Eclipse |
| 111 | + project, the origin of its software, or the software's license. |
| 112 | + |
| 113 | +2. In any way that indicates a greater degree of association between you and |
| 114 | + Red Eclipse project than actually exists. |
| 115 | + |
| 116 | +3. In any way that implies a designated successor to Red Eclipse |
| 117 | + (e.g., "Red Eclipse++" is not permitted). |
| 118 | + |
| 119 | +4. In any way that indicates that the Red Eclipse project favours one |
| 120 | + distribution, platform, product, etc. over another except where explicitly |
| 121 | + indicated in writing by the Red Eclipse project. |
| 122 | + |
| 123 | +5. In any way that promotes the use of third party services over those provided |
| 124 | + by Red Eclipse. |
| 125 | + |
| 126 | +6. In any way that could be deemed harmful or disruptive to the Red Eclipse |
| 127 | + community and/or project. |
| 128 | + |
| 129 | +Thus uses of the marks in a domain name or company name without explicit written |
| 130 | +permission from the Red Eclipse project are prohibited. |
| 131 | + |
| 132 | + |
| 133 | +== Other Legal Notes == |
| 134 | + |
| 135 | +The Red Eclipse project reserves the sole right to: |
| 136 | + |
| 137 | +1. Determine compliance with this policy. |
| 138 | + |
| 139 | +2. Modify this policy to preserve the rights of Red Eclipse, the public, the |
| 140 | + community, and the users. |
| 141 | + The latest version of the Red Eclipse Mark Policy should be available at |
| 142 | + <https://redeclipse.net/wiki/Trademark_Policy> |
| 143 | + |
| 144 | +3. Grant exceptions to this policy, of any kind and for any reason whatsoever, |
| 145 | + other clauses notwithstanding. |
| 146 | + |
| 147 | +== Other Use == |
| 148 | + |
| 149 | +If you have questions regarding the policy, or if any of the examples are |
| 150 | +unclear, feel free to contact the Red Eclipse project using the details provided |
| 151 | +in the declaration above. |
| 152 | + |
| 153 | +If you would like to use the Red Eclipse marks for any other use, please contact |
| 154 | +us and we'll discuss a way to make that happen. We don't have strong objections |
| 155 | +to people using the name for their websites and businesses, but we do need the |
| 156 | +chance to review such use. |
| 157 | + |
| 158 | +In other words, it's not a big deal, and a short conversation (via the forums |
| 159 | +for example) should clear everything up in short order. |
| 160 | + |
| 161 | +If you currently have a product that is using the Red Eclipse marks in a way |
| 162 | +that don't follow this policy, don't panic. Let us know, and we'll work it out, |
| 163 | +as described above. |
| 164 | + |
| 165 | + |
| 166 | +== Attribution == |
| 167 | + |
| 168 | +This text is Copyright (C) 2011-2019, the Red Eclipse Team |
| 169 | +and is available under a Creative Commons Attribution-ShareAlike 4.0 |
| 170 | +License <http://creativecommons.org/licenses/by-sa/4.0/> |
| 171 | + |
| 172 | +A large portion of the content in this text is based on |
| 173 | +<http://wiki.documentfoundation.org/TradeMark_Policy> |
| 174 | +which is Copyright (C) 2011, The Document Foundation |
| 175 | +and is available under a Creative Commons Attribution-ShareAlike 3.0 Unported |
| 176 | +License <http://creativecommons.org/licenses/by-sa/3.0/> |
| 177 | + |
| 178 | +Additionally, some content is based on |
| 179 | +<http://www.softwarefreedom.org/resources/2008/foss-primer.html#x1-700005.6> |
| 180 | +which is Copyright (C) 2006, 2007, 2008, Software Freedom Law Center, Inc. |
| 181 | +and is available under a Creative Commons Attribution-ShareAlike 3.0 US |
| 182 | +License <http://creativecommons.org/licenses/by-sa/3.0/us/> |
0 commit comments