From: Vladimir Zhbanov <vzhbanov@gmail.com>
To: guile-user@gnu.org
Subject: Re: A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list)
Date: Fri, 17 Jul 2020 01:55:18 +0300 [thread overview]
Message-ID: <20200716225518.GA29869@newvzh.lokolhoz> (raw)
In-Reply-To: <97aedc27-985c-ec7a-9dfa-a26efd162a4a@posteo.de>
On Thu, Jul 16, 2020 at 10:47:21PM +0200, Zelphir Kaltstahl wrote:
> Hi Dmitry!
>
> On 16.07.20 11:18, Dmitry Alexandrov wrote:
> > 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...
It is, if you explicitly prohibit invariant section, as in *Guile
Reference Manual*:
<quote>
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; *with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts*. A
copy of the license is included in the section entitled “GNU Free
Documentation License.”
</quote>
So, if you ensure this "no Invariant Sections" stanza is in place,
anything is free and OK for Debian.
...
> What is the impact or are the consequences of incompatibility with GPL,
> with regard to the list of links?
...
> I guess what I would like most would be CC0 with copyleft or GFDL
> without any problems from invariant sections or problems stemming from
> incompatibility with GNU GPL.
>
> On the same page it also says:
>
> /"For this reason, we encourage documentation authors to license their
> works (or dual-license, together with the GFDL) under the same terms as
> the software they refer to, or any of the traditional free software
> licenses like the GPL or the BSD license."/
>
> 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.
>
> Or is it simply GPL that fit the bill of what I am looking for?
I suspect it is all about including chunks of your GPL'd code as
examples into your other licenced docs. And vice versa, e.g. if
you generate some parts of your docs from code comments. If the
licence of the docs is GPL-compatible, then no issues at all.
--
Vladimir
(λ)επτόν EDA — https://github.com/lepton-eda
next prev parent reply other threads:[~2020-07-16 22:55 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 [this message]
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=20200716225518.GA29869@newvzh.lokolhoz \
--to=vzhbanov@gmail.com \
--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).