[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Clarifying blog post licensing
From: |
Ricardo Wurmus |
Subject: |
Re: Clarifying blog post licensing |
Date: |
Wed, 26 Jan 2022 13:06:15 +0100 |
User-agent: |
mu4e 1.6.10; emacs 27.2 |
Ludovic Courtès <ludo@gnu.org> writes:
> 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?
Sounds good.
> 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):
>
> scheme@(guile-user)> ,pp authors
> $22 = ("A collective of GNU maintainers"
[…]
> "Ricardo (rekado) Wurmus"
> "Ricardo Wurmus"
I agree.
--
Ricardo
- Clarifying blog post licensing, Ludovic Courtès, 2022/01/26
- Re: Clarifying blog post licensing, Manolis Ragkousis, 2022/01/26
- Re: Clarifying blog post licensing, Efraim Flashner, 2022/01/26
- Re: Clarifying blog post licensing, Julien Lepiller, 2022/01/26
- Re: Clarifying blog post licensing,
Ricardo Wurmus <=
- Re: Clarifying blog post licensing, Maxim Cournoyer, 2022/01/26
- Re: Clarifying blog post licensing, Tobias Geerinckx-Rice, 2022/01/26
- Re: Clarifying blog post licensing, Vagrant Cascadian, 2022/01/26
- Re: Clarifying blog post licensing, Jan Nieuwenhuizen, 2022/01/27
- Re: Clarifying blog post licensing, pelzflorian (Florian Pelz), 2022/01/27
- Re: Clarifying blog post licensing, jbranso, 2022/01/29