|
| 1 | +# CodeFRAME Trademark Policy |
| 2 | + |
| 3 | +> This policy explains how you may and may not use the CodeFRAME name and logo. |
| 4 | +> It is intentionally conservative and is **not legal advice**; it may be revised |
| 5 | +> as the trademark application progresses. |
| 6 | +
|
| 7 | +## Ownership |
| 8 | + |
| 9 | +**CodeFRAME™** and the CodeFRAME logo are trademarks of **Noatak Enterprises, |
| 10 | +LLC, dba Bria Strategy Group** ("the owner"). A U.S. trademark application for |
| 11 | +the CodeFRAME mark is pending. All rights are reserved. |
| 12 | + |
| 13 | +The ™ symbol is used because the mark is not yet federally registered; it will |
| 14 | +be updated to ® if and when registration issues. |
| 15 | + |
| 16 | +## The code license does not grant trademark rights |
| 17 | + |
| 18 | +CodeFRAME's source code is licensed under [AGPL-3.0](LICENSE) (see |
| 19 | +[LICENSING.md](LICENSING.md)). **That license covers copyright in the code only. |
| 20 | +It does not grant any right to use the CodeFRAME name or logo.** This is the |
| 21 | +standard position for open-source licenses, which deliberately exclude |
| 22 | +trademarks. |
| 23 | + |
| 24 | +In other words: you are free to use, modify, and redistribute the *code* under |
| 25 | +the AGPL — but the *name and logo* are not part of that grant. |
| 26 | + |
| 27 | +## What you may do (no permission needed) |
| 28 | + |
| 29 | +- **Refer to CodeFRAME truthfully** ("nominative use") — e.g., "compatible with |
| 30 | + CodeFRAME", "a plugin for CodeFRAME", "built on CodeFRAME" — provided you do |
| 31 | + not imply that the owner endorses, sponsors, or is affiliated with your |
| 32 | + project. |
| 33 | +- **State that your fork is derived from CodeFRAME**, as long as the fork is |
| 34 | + clearly named something else (see below). |
| 35 | +- Use the name in **blog posts, talks, tutorials, and reviews** that discuss the |
| 36 | + software. |
| 37 | + |
| 38 | +## What requires written permission |
| 39 | + |
| 40 | +- Using **"CodeFRAME" (or a confusingly similar name) as the name of your own** |
| 41 | + product, service, company, fork, or distribution. |
| 42 | +- Using the **CodeFRAME logo** other than to refer to the unmodified project. |
| 43 | +- Any use that **suggests affiliation, sponsorship, or endorsement** by the |
| 44 | + owner, or that could confuse users about the source of the software. |
| 45 | +- Use on **merchandise** or in **domain names**, social handles, or app-store |
| 46 | + listings. |
| 47 | + |
| 48 | +If you maintain a fork, please give it a distinct name and may say, for example, |
| 49 | +"based on CodeFRAME" — but do not call the fork itself "CodeFRAME". |
| 50 | + |
| 51 | +## Using the mark correctly |
| 52 | + |
| 53 | +- Write it as **CodeFRAME** and include the ™ symbol on first or most prominent |
| 54 | + use: **CodeFRAME™**. |
| 55 | +- Use it as an adjective modifying a noun ("the CodeFRAME platform"), not as a |
| 56 | + verb or a generic noun. |
| 57 | +- `codeframe-ai` (the PyPI package) and `cf` (the command) are technical |
| 58 | + identifiers, not the brand. |
| 59 | + |
| 60 | +## Requesting permission |
| 61 | + |
| 62 | +For any use that requires permission, or if you are unsure, contact |
| 63 | +**licensing@codeframe.sh** describing the intended use. We are generally happy to |
| 64 | +allow community uses that don't create confusion. |
0 commit comments