From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Guix Devel" <guix-devel@gnu.org>,
"GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: Clarifying blog post licensing
Date: Wed, 26 Jan 2022 11:30:58 +0100 [thread overview]
Message-ID: <0E16B2FF-A485-41BF-9408-5D47BF3616DB@lepiller.eu> (raw)
In-Reply-To: <87bkzykfyc.fsf@inria.fr>
On January 26, 2022 10:24:11 AM GMT+01:00, "Ludovic Courtès" <ludo@gnu.org> wrote:
>Hello Guix!
>
>With a few exceptions, our blog posts do not have a license, which is
>not great as it prevents sharing and reuse, at least by those outside
>Guix circles (we discussed it in the past but never got around to fixing
>it).
>
>I’d like us to clarify that, with a footer on blog posts saying that,
>unless otherwise stated, posts are dual-licensed under CC-BY-SA 4.0 and
>GFDL 1.3+ (the latter so we can reuse material in the cookbook and in
>the manual). Patch below.
>
>What do people think?
>
>If maintainers and everyone agrees, I’d like to publicly email all the
>authors asking them whether they agree with the proposed licensing
>terms, or whether they’d like a different free license. The script
>below enumerates blog post authors (the list needs a bit of cleanup
>still):
>
>--8<---------------cut here---------------start------------->8---
>scheme@(guile-user)> ,pp authors
>$22 = ("A collective of GNU maintainers"
> "Andreas Enge"
> "Chris Marusich"
> "Chris Marusich and Léo Le Bouter"
> "Christopher Baines"
> "Christopher Lemmer Webber"
> "Danjela Lura"
> "Danny Milosavljevic"
> "David Thompson"
> "Efraim Flashner"
> "Florian Pelz"
> "Guix Hackers"
> "Gábor Boskovits"
> "Jakob L. Kreuze"
> "Jan (janneke) Nieuwenhuizen"
> "Jan Nieuwenhuizen"
> "Joshua Branson"
> "Julien Lepiller"
> "Konrad Hinsen"
> "Laura Lazzati"
> "Ludovic (civodul) Courtès"
> "Ludovic Courtès"
> "Ludovic Courtès and Leo Famulari"
> "Magali Lemes"
> "Manolis Ragkousis"
> "Marius (mbakke) Bakke"
> "Marius Bakke"
> "Mathieu Othacehe"
> "Maxim Cournoyer"
> "Pierre Neidhardt"
> "Pjotr Prins"
> "Ricardo (rekado) Wurmus"
> "Ricardo Wurmus"
> "Roel Janssen"
> "Simon Tournier"
> "Tatiana Sholokhova"
> "Tobias Geerinckx-Rice"
> "sirgazil")
>--8<---------------cut here---------------end--------------->8---
>
>How does that sound?
>
>Thanks,
>Ludo’.
>
I agree
next prev parent reply other threads:[~2022-01-26 10:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:24 Clarifying blog post licensing Ludovic Courtès
2022-01-26 9:30 ` Manolis Ragkousis
2022-01-26 9:33 ` Efraim Flashner
2022-01-26 10:30 ` Julien Lepiller [this message]
2022-01-26 11:16 ` Oliver Propst
2022-01-26 12:06 ` Ricardo Wurmus
2022-01-26 14:24 ` Maxim Cournoyer
2022-02-05 11:20 ` Ludovic Courtès
2022-02-06 5:08 ` Maxim Cournoyer
2022-01-26 16:42 ` Tobias Geerinckx-Rice
2022-01-26 17:57 ` Vagrant Cascadian
2022-01-26 18:55 ` Tobias Geerinckx-Rice
2022-02-05 11:22 ` Ludovic Courtès
2022-01-27 5:57 ` Jan Nieuwenhuizen
2022-01-27 16:15 ` pelzflorian (Florian Pelz)
2022-01-28 23:10 ` Gábor Boskovits
2022-01-30 4:21 ` jbranso
2022-02-05 13:47 ` License of your contributions to the blog at guix.gnu.org Ludovic Courtès
2022-02-05 14:04 ` zimoun
2022-02-05 14:07 ` Luis Felipe
2022-02-05 14:10 ` Tatiana Sholokhova
2022-02-05 14:12 ` Mathieu Othacehe
2022-02-05 16:39 ` Pierre Neidhardt
2022-02-05 18:49 ` Leo Famulari
2022-02-05 22:55 ` Magali Lemes
2022-02-06 8:35 ` Efraim Flashner
2022-02-07 18:48 ` Christopher Baines
2022-02-07 22:46 ` Léo Le Bouter
2022-02-07 23:03 ` Marius Bakke
2022-02-08 5:53 ` Konrad Hinsen
2022-02-09 2:47 ` zerodaysfordays
2022-02-10 8:10 ` Chris Marusich
2022-02-11 14:04 ` Christine Lemmer-Webber
2022-02-14 17:36 ` Ludovic Courtès
2022-02-14 19:51 ` Andreas Enge
2022-02-28 20:17 ` Danjela Lura
2022-04-05 16:00 ` Ludovic Courtès
2022-07-04 13:55 ` Please reply: " Ludovic Courtès
2022-07-07 13:54 ` [EXT] " Thompson, David
2022-04-05 18:14 ` Roel Janssen
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=0E16B2FF-A485-41BF-9408-5D47BF3616DB@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).