From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: "simon tournier" <simon.tournier@univ-paris-diderot.fr>
Cc: guix-devel@gnu.org, guix-hpc@gnu.org
Subject: New Guix-Science mailing list!
Date: Mon, 13 Jul 2020 16:17:58 +0200 [thread overview]
Message-ID: <87h7ubo5wp.fsf@gnu.org> (raw)
In-Reply-To: <web-238347084@univ-paris7.fr> (simon tournier's message of "Fri, 10 Jul 2020 15:54:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Howdy!
"simon tournier" <simon.tournier@univ-paris-diderot.fr> skribis:
> This new post presents the work we did during the Reproducible Research
> hackathon day, the past week. Thanks to everyone for joining! I hope
> it was an enjoying experience.
>
> https://hpc.guix.info/blog/2020/07/reproducible-research-hackathon-experience-report/
>
> Let replicate soon this experiment. :-)
Yup, it was a pleasant and productive experience!
One of the things we discussed as a followup was the creation of a
proper mailing list (guix-hpc@gnu.org is just an alias, which was fine
when there was just a handful of people but doesn’t scale well…).
So… drum roll… here’s a new Guix-Science mailing list!
https://lists.gnu.org/mailman/listinfo/guix-science
We can use it to discuss use cases for reproducible research, HPC, and
all that. Broader discussions should still go to help-guix and
guix-devel.
As for other project communication channels, guix-science members are
subject to the code of conduct:
https://git.savannah.gnu.org/cgit/guix.git/tree/CODE-OF-CONDUCT
I’ve shared the mailing list admin password with Ricardo and Tobias, but
if someone wants to fill that role, please let us know!
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
parent reply other threads:[~2020-07-13 14:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <web-238347084@univ-paris7.fr>]
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=87h7ubo5wp.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=simon.tournier@univ-paris-diderot.fr \
/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).