unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Cc: guix-maintainers@gnu.org
Subject: Re: Licence of the Guix blog posts
Date: Fri, 02 Dec 2022 17:06:34 +0100	[thread overview]
Message-ID: <87lenprdrp.fsf@gmail.com> (raw)
In-Reply-To: <87pmd79epk.fsf@inria.fr>

Hi Ludo,

Thanks for this clarification.  It reminds me hpc.guix.info posts. :-)

On Mon, 28 Nov 2022 at 18:22, Ludovic Courtès <ludo@gnu.org> wrote:

> Simon, what do you think about emailing the authors of the “10 years of
> stories” post asking if they agree with the licensing?  :-)  No rush,
> though the sooner the more likely we are to get an answer.

I will do my best this week-end.


Cheers,
simon


  parent reply	other threads:[~2022-12-02 16:10 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
2022-12-02 16:06   ` zimoun [this message]
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=87lenprdrp.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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).