unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Jakob L. Kreuze" <zerodaysfordays@sdf.org>,
	GNU Guix maintainers <guix-maintainers@gnu.org>,
	Guix Devel <guix-devel@gnu.org>, David Thompson <davet@gnu.org>,
	Magali Lemes <magalilemes00@gmail.com>,
	Tatiana Sholokhova <tanja201396@gmail.com>,
	Pierre Neidhardt <mail@ambrevar.xyz>,
	Mathieu Othacehe <othacehe@gnu.org>,
	Joshua Branson <jbranso@gnucode.me>,
	Pjotr Prins <pjotr2021@thebird.nl>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	Danjela Lura <danielaluraa@gmail.com>
Subject: Re: License of your contributions to the blog at guix.gnu.org
Date: Fri, 11 Feb 2022 09:04:11 -0500	[thread overview]
Message-ID: <87leyhts7z.fsf@dustycloud.org> (raw)
In-Reply-To: <87pmo1ifxj.fsf@gnu.org>

I'm good with it!

Ludovic Courtès <ludo@gnu.org> writes:

> [[PGP Signed Part:Undecided]]
> Hello,
>
> I am emailing you on behalf of the GNU Guix project because you are the
> author or coauthor of one or more articles to the blog at
> <https://guix.gnu.org/en/blog>.
>
> With a few exceptions, these articles do not have a clear license, which
> we would like to fix.  We propose to dual-license all the articles under
> CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant Sections,
> no Front-Cover Texts, and no Back-Cover Texts.
>
> Do you agree with the proposed licensing terms for your contributions to
> the blog?
>
> If you do, please reply to this message to say so, keeping
> guix-devel@gnu.org Cc’d (if you already replied in the previous thread,
> you do not need to reply again).
>
> If you would prefer different licensing terms, or if you have any
> questions, feel free to ask them publicly on guix-devel@gnu.org or
> privately with guix-maintainers@gnu.org.
>
> The clarified license will allow us and others to reuse material in the
> manual, cookbook, and in other free cultural works.  See
> <https://lists.gnu.org/archive/html/guix-devel/2022-01/msg00389.html>
> for the initial discussion.
>
> Thanks in advance!
>
> Ludo’.
>
> [[End of PGP Signed Part]]



  parent reply	other threads:[~2022-02-11 20:50 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
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 [this message]
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=87leyhts7z.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=danielaluraa@gmail.com \
    --cc=davet@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=jbranso@gnucode.me \
    --cc=ludo@gnu.org \
    --cc=magalilemes00@gmail.com \
    --cc=mail@ambrevar.xyz \
    --cc=maxim.cournoyer@gmail.com \
    --cc=othacehe@gnu.org \
    --cc=pjotr2021@thebird.nl \
    --cc=tanja201396@gmail.com \
    --cc=zerodaysfordays@sdf.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).