Copyright notices: name the Postulo contributors as the holder, not one person #346
Labels
No labels
accessibility
authentication
breaking change
bug
documentation
enhancement
interface
internationalisation
observability
performance
security
tier
1
tier
2
tier
3
tier/4
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Postulo/postulo#346
Loading…
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?
Requested by the maintainer on 2026-10-01.
Every copyright notice in the repository names one person, Tiago Agueda. The project takes contributions, and its translation catalogues already say
Last-Translator: Postulo contributors; the notices should say the same thing: Copyright (C) 2026 Postulo contributors.Where the wording is
README.md:243(Licence):Copyright (C) 2026 Tiago Agueda. [AGPL-3.0-or-later](LICENSE).THIRD-PARTY.md:3:Postulo is Copyright (C) 2026 Tiago Agueda and is licensed under ...TRADEMARKS.md:3:Postulo's **code** is Copyright (C) 2026 Tiago Agueda, ...pyproject.toml:8:authors = [{ name = "Tiago Agueda" }], which becomes the package'sAuthorfield.tests/test_trademarks.py:63-66asserts the exact stringCopyright (C) 2026 Tiago AguedainTHIRD-PARTY.md,TRADEMARKS.mdandREADME.md, so the three files and the test change together.Writing-a-plugin.md:1485: the catalogue example carries"maintainer": "Tiago Agueda". That field names who maintains a plugin, not who holds its copyright; decide whether the example should name a person at all, or the project.Not this:
SECURITY.mdandFUNDING.mdname the maintainer as the person to write to and the person a donation goes to. Those are true statements about a person and stay. The third-party notices (basecoat, flag-icons, zxcvbn, Lucide) name their own holders and stay.What to decide while changing it
Copyright (C) 2026 Postulo contributorsis the proposal. Keep the first year; add a range only if the project wants one.CONTRIBUTING.mdsays nothing today about the terms a contribution comes in under. Add the sentence that makes the collective notice accurate: contributions are licensed under AGPL-3.0-or-later, contributors keep their copyright, and the notice names them together. Say where the list of contributors is (the git history, or anAUTHORSfile if one is wanted).TRADEMARKS.mdreserves the name and the logo and does not say whose they are. This issue is about the copyright line only; if the marks should also move from a person to the project, that is its own decision and its own issue.authorsinpyproject.tomlcan bePostulo contributorstoo, withmaintainersnaming who answers for a release if that is wanted.Done when
Copyright (C) 2026 Postulo contributors, andtests/test_trademarks.pyasserts the new wording and refuses the old one.CONTRIBUTING.mdstates the terms of a contribution and who the notice refers to.pyproject.tomland the wiki's catalogue example say what was decided.