TRADEMARKS.md: the marks already in the tree, and the rule for the ones coming #107
Labels
No labels
accessibility
authentication
breaking change
bug
documentation
enhancement
interface
internationalisation
observability
security
tier
1
tier
2
tier
3
tier/4
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Reference
Postulo/postulo#107
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Observation
#106 decided that a plugin may ship a third party's mark with a notice beside it, unmodified,
outside the AGPL grant, claiming no endorsement — and that this is a rule rather than an
exception for Europass. The rule needs somewhere to live before the first plugin logo lands.
It is not hypothetical: there is already an unmarked trademark in the tree
Added by #79, and it is exactly the thing #106 is about: somebody else's mark, shipped in an
AGPL repository, with nothing beside it saying whose it is. Every fork redistributes it. That
is almost certainly fine — it is an approved banner, used to link to the account it belongs
to, which is what approved banners are for — but the repository does not say so anywhere, and
that is the gap this closes.
Two more sets of third-party artwork are in the tree and are accounted for, differently:
src/postulo/static/icons/@licensecommentsrc/postulo/static/flags/assets/support/The first two are copyright licences and are handled. A mark is not licensed at all, which is
why it needs a different kind of note rather than a third licence file.
And Postulo's own name has never been mentioned
assets/brand/postulo.pngand seven derived files undersrc/postulo/static/brand/. TheREADME says the code is AGPL and says nothing about the name or the logo, so a reader has no
way to know what a fork may call itself.
That matters more here than in most projects, because of what the README promises. Never
paywalled is a commitment about the project, not about the code — the licence cannot
enforce it, and a fork that added a paid tier and kept the name would break the promise for
everybody who had heard it. A trademark note is the only instrument that speaks to that, and
it is worth having for that reason rather than for control.
It is also explicitly permitted by the licence Postulo uses. AGPL-3.0 §7 lists the terms a
work may add, and clause (e) is "Declining to grant rights under trademark law for use of
some trade names, trademarks, or service marks". So this is not a restriction bolted on to a
free licence; it is the licence's own provision.
What the document says
the name, say truthfully that something works with Postulo, name a plugin
postulo-something— which is the ecosystem's own convention and must be explicitlyallowed, since eight repositories already use it.
site.instance_name()exists so an operator can,and nothing in a trademark note should read as discouraging it.
it is a modified version and not endorsed. The Firefox/Iceweasel arrangement, without the
argument.
Scope
TRADEMARKS.mdat the root.a paragraph, and that paragraph is the right size for a licence note and the wrong place
for a marks policy.
assets/support/buy-me-a-coffee.png, the way the flags carry theirs.it cannot quietly fall out of date the next time something is vendored.
Classification
Documentation. Prerequisite for #106's artwork; useful on its own regardless.