From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Cc: guix-maintainers@gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: Re: Licence of the Guix blog posts
Date: Fri, 02 Dec 2022 16:30:40 +0100 [thread overview]
Message-ID: <878rjpstzz.fsf@gnu.org> (raw)
In-Reply-To: <87pmd79epk.fsf@inria.fr> ("Ludovic Courtès"'s message of "Mon, 28 Nov 2022 18:22:15 +0100")
Hi!
Ludovic Courtès <ludo@gnu.org> skribis:
> Therefore, I propose to apply the following patch, which leaves out a
> couple of posts as “unlicensed”. From there on, we’ll have consistent
> free licensing by default.
Thanks to everyone who provided feedback. I pushed the patch.
Let’s see if we can eventually address the remaining unlicensed posts,
in particular the 10 years one.
Ludo’.
next prev parent reply other threads:[~2022-12-02 15:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <861qmw5uib.fsf@gmail.com>
2022-11-28 17:22 ` Licence of the Guix blog posts Ludovic Courtès
2022-11-28 18:19 ` Ekaitz Zarraga
2022-11-28 19:44 ` Maxim Cournoyer
2022-11-28 19:48 ` Andreas Enge
2022-11-28 20:29 ` Vagrant Cascadian
2022-11-28 20:36 ` pelzflorian (Florian Pelz)
2022-12-02 15:30 ` Ludovic Courtès [this message]
2022-12-02 16:06 ` zimoun
2023-02-11 11:26 ` Simon Tournier
2022-12-03 15:15 ` Thiago Jung Bauermann
2022-12-04 20:36 ` John Kehayias
2022-12-06 9:40 ` Guillaume Le Vaillant
2023-02-11 11:56 ` Csepp
2023-02-12 17:35 ` Csepp
2023-02-11 12:05 ` Lars-Dominik Braun
2023-02-11 13:14 ` Luis Felipe
2023-02-11 13:33 ` Björn Höfling
2023-02-11 15:24 ` License of “10 years of stories behind Guix” Konrad Hinsen
2023-02-11 15:54 ` Hartmut Goebel
2023-02-12 10:05 ` Licence of the Guix blog posts Janneke Nieuwenhuizen
2023-02-15 0:06 ` Arun Isaac
2023-02-15 10:41 ` Alice BRENON
2023-02-15 14:58 ` Eric Bavier
2023-02-13 16:56 Cyril Roelandt
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=878rjpstzz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).