mirror of
https://github.com/Psychotoxical/psysonic.git
synced 2026-07-21 23:05:46 +00:00
Frank Stellmacher
7f03a9536a
* docs: add NOTICE and TRADEMARK files Adds a NOTICE.md with the GPLv3 §7(b) attribution-preservation terms that derivative works must carry forward, and a TRADEMARK.md that covers the Psysonic name, logo, brand identity, and the names of original Psysonic features (in particular Orbit) — none of which are licensed under the GPLv3. Forks remain free under GPLv3 to reuse the code, but must rename Psysonic-branded assets and feature names, and must preserve the attribution that original Psysonic features were designed and implemented in this project. * docs(readme): add Forks and Attribution section Points readers at the GPLv3 freedoms while clarifying the expectations for forks: keep the project name and feature names as documented in TRADEMARK.md, preserve attribution as required by NOTICE.md, and do not present original Psysonic work (such as Orbit) as independent creations of a fork.
67 lines
2.7 KiB
Markdown
67 lines
2.7 KiB
Markdown
# Trademark Notice
|
|
|
|
The Psysonic source code is licensed under the GNU GPLv3.
|
|
The **Psysonic name, logo, wordmark, visual brand identity, and the
|
|
names of original Psysonic features are not** — they are excluded
|
|
from the GPLv3 grant and remain the property of the Psysonic project
|
|
maintainers.
|
|
|
|
## Covered Marks
|
|
|
|
- The name **"Psysonic"** (in any capitalization or stylization)
|
|
- The Psysonic logo and icon (`public/psysonic-inapp-logo.svg`,
|
|
app icons, tray icons, installer artwork)
|
|
- The Psysonic wordmark and any derivative branding
|
|
- The names of original Psysonic features that function as feature
|
|
identity, in particular **"Orbit"**
|
|
|
|
## What You May Do
|
|
|
|
- Use the Psysonic name to factually refer to the upstream project
|
|
(e.g. *"based on Psysonic"*, *"a fork of Psysonic"*, *"compatible
|
|
with Psysonic"*).
|
|
- Redistribute unmodified Psysonic builds under the Psysonic name,
|
|
in accordance with the GPLv3.
|
|
- Link to the official Psysonic repository, website, and community
|
|
channels.
|
|
|
|
## What You May Not Do
|
|
|
|
- Use the Psysonic name, logo, or branding for a **modified or
|
|
rebranded fork**, distribution, or derivative product.
|
|
- Name a fork in a way that suggests it *is* Psysonic, an official
|
|
release of Psysonic, or endorsed by the Psysonic project (e.g.
|
|
"Psysonic Pro", "Psysonic Plus", "Psysonic Next", "MyPsysonic").
|
|
- Reuse the Psysonic logo, icon set, or installer artwork in a fork
|
|
or derivative product, even with modifications.
|
|
- Continue to use the feature name **"Orbit"** in a fork or
|
|
derivative. If your fork ships the Orbit feature (or code derived
|
|
from it), you must rename the user-facing feature.
|
|
- Present original Psysonic features (such as Orbit) as independent
|
|
creations of a fork. See `NOTICE.md` for the attribution
|
|
requirements that apply to derivative works under GPLv3 §7(b).
|
|
- Imply sponsorship, endorsement, or affiliation with the Psysonic
|
|
project where none exists.
|
|
|
|
## Forking Done Right
|
|
|
|
You are warmly invited to fork the code under the GPLv3.
|
|
If you publish a fork or derivative, please:
|
|
|
|
1. Choose your own distinct project name and branding.
|
|
2. Keep the GPLv3 license, copyright notices, and the `NOTICE.md`
|
|
file intact (this is required, not optional — see `NOTICE.md`).
|
|
3. State clearly that your project is *based on Psysonic* and link
|
|
back to the upstream repository.
|
|
4. Replace Psysonic-branded assets (logos, icons, installer art,
|
|
wordmarks) with your own.
|
|
5. If you ship features that originated in Psysonic (such as Orbit),
|
|
rename the user-facing feature and credit Psysonic as the
|
|
original designer and implementer.
|
|
|
|
## Questions
|
|
|
|
If you are unsure whether a planned use of the Psysonic name or
|
|
branding is acceptable, please open an issue or contact the
|
|
maintainers before publishing.
|