unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Amin Bandali <bandali@gnu.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: Fri, 24 Jul 2020 11:30:02 -0400	[thread overview]
Message-ID: <877dutx75x.fsf@gnu.org> (raw)
In-Reply-To: <87zh7p6ll9.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

Hi Ludo’, all,

Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
[...]
> I would propose GFDLv1.3+ without invariant sections, since that can
> then be relicensed to CC-BY-SA should anyone need it.
>
> Thoughts?
>
> Ludo’.

I'm not a lawyer and this is not legal advice, but reading the text for
GFDLv1.3 <https://www.gnu.org/licenses/fdl-1.3.html>, 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.  Thus, I would suggest explicitly asking the FSF or
seeking legal advice about that, to know whether that section still
applies today.

Another good candidate is CC BY-SA 4.0, which was declared one-way
compatible with GPLv3
<https://www.fsf.org/blogs/licensing/creative-commons-by-sa-4-0-declared-one-way-compatible-with-gnu-gpl-version-3>;
but it does have its own gotchas
<https://wiki.creativecommons.org/wiki/ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions>.
I have also seen folks license material on their site under GPLv3+.
I currently do that for the material on my personal site.

That's my 2¢; hope it helps.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

  parent reply	other threads:[~2020-07-24 15:30 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 [this message]
2020-07-24 21:36     ` Dmitry Alexandrov

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=877dutx75x.fsf@gnu.org \
    --to=bandali@gnu.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).