From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: guix-science@gnu.org
Subject: Licensing Guix-HPC blog posts under a free license
Date: Fri, 24 Nov 2023 17:58:43 +0100 [thread overview]
Message-ID: <878r6n5br0.fsf@inria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
Hello!
Perhaps you were assuming it was already the case, but it was not: we’d
not agreed upfront on a license for blog posts, making them de facto
non-free. A terrible mistake.
As a good Friday afternoon activity, I embarked on a process to get
approval from every co-author of a post at <https://hpc.guix.info/blog>
for CC-BY-SA 4.0/GFDL 1.3+ dual licensing (same license as
<https://guix.gnu.org/blog>).
You can see the details and progress in this file:
https://gitlab.inria.fr/guix-hpc/website/-/blob/master/BLOG-LICENSING.org
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
reply other threads:[~2023-11-24 16:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=878r6n5br0.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@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.
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).