SunRed/licenses
1
0
Fork 0
Code Issues Pull requests Releases Activity

Update sources, Add SPDX identifier

Browse source
This commit is contained in:
Manuel 2024-07-21 15:43:01 +02:00
parent bc63340f29
commit 57a944df4c
Signed by: Manuel
GPG key ID: 4085037435E1F07A
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -3,10 +3,12 @@
This repository preserves unusual (open source) software license choices and extensions of well known licenses. Use at your own risk.
## [GNU Affero General Public License v3.0 only](agpl-3.0-only)
SPDX identifier: `AGPL-3.0-only`
This license only covers the version 3.0 and therefore does not accidentally grant any unwanted permissions in the future that may come with a new version of this license and therefore puts no trust in the Free Software Foundation.
## [GNU Affero General Public License v3.0 only with linking exception](agpl-3.0-only-linking-exception)
SPDX identifier: `AGPL-3.0-only WITH GPL-3.0-linking-exception`
Same as [AGPL v3.0 only](agpl-3.0-only) but the license extension allows linking against (A)GPL code (e.g. a library) without the need for redistribution and therefore allows inclusion in projects using usually incompatible licenses while still getting changes back made to the code itself. It also keeps the aspect of the AGPL regarding restrictions on network distribution while not allowing decompilation and reverse engineering on the "combined work" (e.g. in the sense of a compiled binary using that library) like it would be the case with the LGPL.
@ -18,7 +20,7 @@ You may combine the license header in `LICENSE.txt` with the copy of the origina
<https://spdx.org/licenses/AGPL-3.0-only.html>
<http://mo.morsi.org/blog/2009/08/13/lesser_affero_gplv3/>
<https://spdx.org/licenses/GPL-3.0-linking-exception.html>
<https://opensource.stackexchange.com/questions/1410/what-is-the-difference-between-gpl-classpath-exception-vs-lgpl>