diff options
| author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2022-04-28 01:42:30 +0200 |
|---|---|---|
| committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2022-04-28 01:43:05 +0200 |
| commit | bea891ee29b3e4c07afd530c3025754fb5247e19 (patch) | |
| tree | a3d6d46dd2a5e4fa04c6b0f78a5278e47552f0fd /COPYRIGHTS | |
| parent | c60704f5a6c7a8c10348607604eebfaf3abe983f (diff) | |
| download | abslibre-bea891ee29b3e4c07afd530c3025754fb5247e19.tar.gz abslibre-bea891ee29b3e4c07afd530c3025754fb5247e19.tar.bz2 abslibre-bea891ee29b3e4c07afd530c3025754fb5247e19.zip | |
COPYRIGHTS: clarify licenses more, and add license for new contributions
- If new contributions are under CC0 we don't need to state that
people also agreed to use CC0 for new contributions.
- Before, I forgot to use git commit -a --amend before pushing, so
PKGBUILDs went in instead of packages. I'm using packages to enable
to add scripts (for instance scripts to check the licenses of the
PKGBUILDs) under other licenses. In addition many packages have more
files (like .install files for instance) than just PKGBUILDs and
patches, and the other packages files are also under the CC0
license.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'COPYRIGHTS')
| -rw-r--r-- | COPYRIGHTS | 18 |
1 files changed, 11 insertions, 7 deletions
diff --git a/COPYRIGHTS b/COPYRIGHTS index 10a4b5270..8a82143ae 100644 --- a/COPYRIGHTS +++ b/COPYRIGHTS @@ -1,4 +1,5 @@ -Many PKGBUILDs and associated files comes from one of these projects: +Many packages (PKGBUILDs and associated files) comes from one of these +projects: - Arch Linux - Arch Linux ARM - Arch Linux 32 @@ -8,22 +9,25 @@ They typically come without a license, so while most of them seem to be uncopyrightable due to their extreme simplicity and standardness, this still creates some legal uncertaincy about their licensing. -Some PKGBUILDs also come from Hyperbola, and here there is also some +Some packages also come from Hyperbola, and here there is also some uncertaincy as the project added a CC0 license in its git repository without adding any clear statement associated with it. We still need -to contact them to get more clarification on their PKGBUILDs licenses +to contact them to get more clarification on their packages licenses for new contributions. -Several PKGBUILDS (and associated files) in this repository were +Several packages (and associated files) in this repository were created from scratch, so they don't depend on other projects licensing decisions. -And several contributors agreed to license their past and future -contributions to PKGBUILDs in this repository under the CC0 license: +And several contributors agreed to license their past contributions to +packages in this repository under the CC0 license: - Andreas Grapentin - bill-auger - Denis 'GNUtoo' Carikli - Freemor As for patches, as they are combined with original project source code -they are usually under the same license.
\ No newline at end of file +they are under the same license than the original project. + +All contributions to packages in this repository must be offered under +the CC0 license. |