chore: license under AGPL-3.0-or-later - #23
Merged
Merged
Conversation
Add the canonical AGPL-3.0 text as `LICENSE` (fetched verbatim from gnu.org/licenses/agpl-3.0.txt) and surface the choice everywhere a consumer would look: - Root `pyproject.toml` and the two workspace member packages (`opf-api`, `opf-eval`) declare `license = "AGPL-3.0-or-later"` (PEP 639 SPDX expression) and point at the repo-root `LICENSE` via `license-files`. - FastAPI `info.license` restored on the app metadata, so Scalar/Swagger/ ReDoc render the license badge. - README gains a `License` section that calls out the §13 network clause explicitly — anyone running a modified version of this code as a network service must make the modified source available to its users. - `info.version` 0.6.0 -> 0.6.1 (additive, non-breaking). The upstream OPF model in `privacy-filter/` is cloned separately and licensed by its author; this repo's AGPL choice does not relicense it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add an AGPL-3.0-or-later license to the repo.
LICENSE(root) carries the canonical GNU text, fetched verbatim from gnu.org.pyproject.tomlfiles declarelicense = \"AGPL-3.0-or-later\"(PEP 639 SPDX expression) and point at the repo-rootLICENSEvialicense-files.info.licenserestored, so the badge renders in Scalar/Swagger/ReDoc.Licensesection that calls out the §13 network clause: anyone running a modified version as a network service must publish the modified source. Worth surfacing because that's the deliberate distinction between AGPL and plain GPL/MIT here.info.version0.6.0 → 0.6.1 (additive metadata, non-breaking).The upstream OPF model in
privacy-filter/is cloned separately and licensed by its author. This repo's AGPL choice doesn't relicense it.Test plan
uv syncresolves with the new metadata.pytest api/tests/test_routes.py— 22/22.info.license: AGPL-3.0-or-later.🤖 Generated with Claude Code