Repository navigation
docs: relicense from GPL-3.0 to AGPL-3.0 - #129
Open
singlerider wants to merge 15 commits into
Open
singlerider wants to merge 15 commits into
singlerider wants to merge 15 commits into
Conversation
Fix DOM race condition
…educe permissions
`webcap` is a Black Lantern original, so this is the copyright holder relicensing its own work. The notices carry `either version 3 of the License, or (at your option) any later version`, and GPLv3 section 13 already permits AGPLv3 interoperation, so making the AGPL grant explicit needs no contributor sign-off. The program name and copyright line already filled in on the old appendix are carried over verbatim, so the file is the AGPL-3.0 text with this repository's attribution rather than a byte copy of `bbot`. The manifest moves in the same commit. A tree that ships an AGPL-3.0 file next to a manifest naming something else is self-contradictory at the point a packager reads it: `pyproject.toml`. Refs #151
ubuntu-latest moves on GitHub's schedule (bbot-enterprise#149).
The PR moves from master to dev, the family trunk path. dev has no cla.yml (blacklanternsecurity#132 adds the shared caller), so the master-era cla.yml and its runner pin are dropped here. The diff against dev is now LICENSE and the pyproject license field only.
|
I have read the CLA Document and I hereby sign the CLA 1 out of 3 committers have signed the CLA. |
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
3 participants
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.
What
LICENSEmoves from GPL-3.0 to AGPL-3.0.pyproject.tomlmoves with it, in the same commit.Why
Every Black Lantern original carries AGPL-3.0. This repository is an original,
not a fork, so this is the copyright holder relicensing its own work. The
notices carry
either version 3 of the License, or (at your option) any later version, and GPLv3 section 13 already permits AGPLv3 interoperation, so makingthe AGPL grant explicit needs no contributor sign-off.
Attribution preserved
The old appendix had a real program name and copyright line filled in, not the
upstream placeholder. Both are carried over verbatim into the AGPL-3.0
appendix, so this file is not a byte copy of the one in
bbot. Dropping in thebbotfile wholesale would have deleted the attribution.Manifest
A tree that ships an AGPL-3.0 file next to a manifest naming something else is
self-contradictory at the point a packager reads it, so both edits belong in
one commit rather than a follow-up.
Validation
LICENSEfirst line readsGNU AFFERO GENERAL PUBLIC LICENSEtomllibRefs #151