From: Dmitry Alexandrov <dag@gnui.org>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list)
Date: Thu, 16 Jul 2020 12:18:23 +0300 [thread overview]
Message-ID: <5zanq0m8.dag@gnui.org> (raw)
In-Reply-To: <c3cb1b89-0491-dc95-d2e7-d5d9ae590e8c@posteo.de> (Zelphir Kaltstahl's message of "Wed, 15 Jul 2020 23:14:52 +0200")
[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> On 15.07.20 08:36, Dr. Arne Babenhauserheide wrote:
>> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>>>> First at foremost, the list _itself_ has to be licensed as a free documentation. FWIW, most of ‘awesome lists’ are under CC0.
>>> While the list is not CC0, I meant to put it under "GNU Free Documentation License v1.3", which I think should be appropriate (Is it not?) and free as in freedom. Good that you hint at the license, because I thought it had a license already.
>> GFDL isn’t considered as free by the debian standards, because it can have invariant sections. CC by-sa might be a good fit, since it is compatible with GPLv3 and wikipedia at the same time.
>
> I just read multiple articles about GFDL and CC0 and still don't know what the better choice is for the list.
Sometimes itʼs better to read a text itself than multiple texts about text. ;-) As least FSF have always tried to keep their licences in English, not legalese.
Doing it, you would find out right away, than GNU FDL is a licence for “manuals, textbooks, or other functional and useful documents”; and most of it is about things like ‘Front Cover’, ‘Back Cover’, ‘Title Page’, ‘Dedications’, ‘Endorsements’, etc, and what one have to do when printing 101+ copies.
What is not written in it, though, is the fact itʼs _not_ compatible with any version of GNU GPL.
> In particular I do not find information about whether CC0 is copyleft or not (1)
Quoth <https://www.gnu.org/licenses/license-list.html#CC0> (emphasis mine):
| A work released under CC0 is dedicated to the public domain to the fullest extent permitted by law. If that is not possible for any reason, CC0 also provides a *lax, permissive* license as a fallback. Both public domain works and the lax license provided by CC0 are compatible with the GNU GPL.
|
| If you want to release your non-software work to the public domain, we recommend you use CC0.
Besides being GPL-compatible, itʼs FDL-compatible as well, while CC BY-SA is not.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-07-16 9:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 21:19 Starting a GNU Guile awesome list Zelphir Kaltstahl
2020-07-13 21:56 ` Jack Hill
2020-07-13 22:56 ` Aleix Conchillo Flaqué
2020-07-14 23:26 ` Zelphir Kaltstahl
2020-07-14 9:00 ` Dmitry Alexandrov
2020-07-14 21:23 ` Zelphir Kaltstahl
2020-07-15 6:32 ` Dr. Arne Babenhauserheide
2020-07-16 8:47 ` Dmitry Alexandrov
2020-07-16 19:01 ` Dr. Arne Babenhauserheide
2020-10-10 12:31 ` Zelphir Kaltstahl
2020-10-10 13:14 ` Matt Wette
2020-10-11 0:57 ` Zelphir Kaltstahl
2020-10-11 19:51 ` Ricardo Wurmus
2020-10-11 23:39 ` Zelphir Kaltstahl
2020-10-12 10:33 ` Ricardo Wurmus
2020-11-08 17:09 ` Zelphir Kaltstahl
2020-11-08 18:55 ` Paul Smith
2020-12-05 18:15 ` Zelphir Kaltstahl
2020-07-15 6:36 ` Dr. Arne Babenhauserheide
2020-07-15 21:14 ` Zelphir Kaltstahl
2020-07-15 22:40 ` Dr. Arne Babenhauserheide
2020-07-16 9:18 ` Dmitry Alexandrov [this message]
2020-07-16 18:56 ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dr. Arne Babenhauserheide
2020-07-16 18:58 ` Dr. Arne Babenhauserheide
2020-07-16 20:47 ` Zelphir Kaltstahl
2020-07-16 22:55 ` Vladimir Zhbanov
2020-07-16 23:05 ` Vladimir Zhbanov
2020-07-17 0:20 ` John Cowan
2020-07-17 6:43 ` Dr. Arne Babenhauserheide
2020-07-14 14:14 ` Starting a GNU Guile awesome list Dr. Arne Babenhauserheide
2020-07-15 21:24 ` Zelphir Kaltstahl
2020-07-15 22:29 ` Dr. Arne Babenhauserheide
2020-07-14 16:37 ` Taylan Kammer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5zanq0m8.dag@gnui.org \
--to=dag@gnui.org \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).