[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Clarifying blog post licensing
From: |
Efraim Flashner |
Subject: |
Re: Clarifying blog post licensing |
Date: |
Wed, 26 Jan 2022 11:33:08 +0200 |
On Wed, Jan 26, 2022 at 10:24:11AM +0100, Ludovic Courtès 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?
I agree
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
- 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 <=
- Re: Clarifying blog post licensing, Julien Lepiller, 2022/01/26
- Re: Clarifying blog post licensing, Ricardo Wurmus, 2022/01/26
- 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