From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: <guix-science@gnu.org>
Subject: One month to the Workshop on Reproducible Software Environments!
Date: Mon, 09 Oct 2023 12:10:24 +0200 [thread overview]
Message-ID: <87bkd814z3.fsf@inria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Hello!
We’re just one month to the Workshop on Reproducible Software
Environments for Research and High-Performance Computing (HPC), which
will take place in Montpellier, France, November 8–10:
https://hpc.guix.info/events/2023/workshop/
Attendance is free but we kindly invite you to register.
The program features talks by scientists, engineers, and system
administrators from different backgrounds who will share their
experience with GNU Guix, as well as tutorials on GitLab, Guix, and other
tools that support scientific workflows—from bioinfo analyses to HPC and
source code archival:
https://hpc.guix.info/events/2023/workshop/program
We wish to make this workshop a hub for scientists and practitioners,
newcomers and experts.
See you in Montpellier!
Ludovic, on behalf of the program committee.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
reply other threads:[~2023-10-09 10:11 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=87bkd814z3.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).