From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: John Cowan <cowan@ccil.org>
Cc: guile-user@gnu.org, Dmitry Alexandrov <dag@gnui.org>
Subject: Re: A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list)
Date: Fri, 17 Jul 2020 08:43:05 +0200 [thread overview]
Message-ID: <875zamvdza.fsf@web.de> (raw)
In-Reply-To: <CAD2gp_QuKn5cnp=xVt1mpJt8gKjxTEtCpP_8UQfTSMvNKELRQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
John Cowan <cowan@ccil.org> writes:
> I don't see any. A list of links is unlikely to be included in the source
> code of a software work.
As soon as you put it into the help section of for example a Guile
Studio, displayed with a help-command and referenced back to some degree
(so that it's not just side-by-side distribution), it is included.
>> But I thought GPL is only meant to be used for software? Think I read
>> that many times in the past, that you should not use GPL for things
>> other than software.
>>
>
> Certainly a GPLed presentation or essay that is unlikely to be printed is
> no problem. Most of my presentation slides are GPLed. But being required
> to distribute the editable source for a specific copy of a printed book
> along with the book (or a written offer to provide it on demand) is a
> nuisance.
The source-code requirement isn‘t that big of a problem; I‘m publishing
roleplaying books under GPL and I just upload the code in version
tracking system. The real annoyance is having to include the GPL license
text. That doesn‘t hurt for Software, but for a printed book that eats
several pages I’d prefer using for something else.
If you want copyleft, easy publishing, and GPL compatibility, then the
only option I know is cc by-sa — which has the additional benefit of
being the license of Wikipedia, so you can use content of articles there
or contribute your text to Wikipedia.
The only downside of cc by-sa is that it is compatible to exactly GPLv3.
Creativecommons is the license steward (so they can declare that CC
by-sa becomes compatible to a GPLv4), so this is less of a problem as if
you'd explicitly choose GPLv3 only, but it's still a downside.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2020-07-17 6:43 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 ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dmitry Alexandrov
2020-07-16 18:56 ` 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 [this message]
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=875zamvdza.fsf@web.de \
--to=arne_bab@web.de \
--cc=cowan@ccil.org \
--cc=dag@gnui.org \
--cc=guile-user@gnu.org \
/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).