From: Dmitry Alexandrov <dag@gnui.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org, Zhu Zihao <all_but_last@163.com>
Subject: Re: What's the license of Guix's blog?
Date: Sat, 25 Jul 2020 00:36:47 +0300 [thread overview]
Message-ID: <a6zosihc.dag@gnui.org> (raw)
In-Reply-To: <877dutx75x.fsf@gnu.org> (Amin Bandali's message of "Fri, 24 Jul 2020 11:30:02 -0400")
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Amin Bandali <bandali@gnu.org> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>> I would propose GFDLv1.3+ without invariant sections, since that can then be relicensed to CC-BY-SA should anyone need it.
>
> but reading the text for GFDLv1.3, specifically "11. RELICENSING", it seems to me that the explicit permission to relicense GFDLv1.3-covered work to CC BY-SA 3.0 was only valid until August 1, 2009.
And it had been never valid for any blog, only for a ‘wiki’.
> I would suggest explicitly asking the FSF or seeking legal advice about that, to know whether that section still applies today.
If one finds the licence itself unclear, there is also a FAQ [1].
[1] https://www.gnu.org/licenses/fdl-1.3-faq.html
> Another good candidate is CC BY-SA 4.0, which was declared one-way compatible with GPLv3...
...yet not with FDL (which Guix manual is under).
> I have also seen folks license material on their site under GPLv3+.
And neither licence is mutually exclusive with the other one!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2020-07-24 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:50 What's the license of Guix's blog? Zhu Zihao
2020-06-12 16:20 ` Dmitry Alexandrov
2020-07-24 14:20 ` Ludovic Courtès
2020-07-24 14:44 ` Tobias Geerinckx-Rice
2020-07-24 15:30 ` Amin Bandali
2020-07-24 21:36 ` Dmitry Alexandrov [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6zosihc.dag@gnui.org \
--to=dag@gnui.org \
--cc=all_but_last@163.com \
--cc=help-guix@gnu.org \
--cc=ludo@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).