From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: Feedback from JRES in Dijon
Date: Thu, 05 Dec 2019 15:39:43 +0100 [thread overview]
Message-ID: <105BA2D7-8B46-409F-9188-4DA5EC41DC3C@lepiller.eu> (raw)
In-Reply-To: <8D474474-AF4C-4B03-9D38-3BB089BEE4EB@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
I forgot to give you a link to the presentation. It's in French: https://replay.jres.org/videos/watch/c77b3a44-b75f-4c10-9f39-8fb55ae096d7
Also, Marc talked about jdev, another French conference where we could present Guix too: http://devlog.cnrs.fr/jdev2020
Le 5 décembre 2019 15:16:23 GMT+01:00, Julien Lepiller <julien@lepiller.eu> a écrit :
>Hi Guix!
>
>I presented the project at JRES yesterday and had lots of questions and
>reactions.
>
>One person was wondering whether Guix would be a good idea for there
>cluster. I said yes then I redirected them to guix hpc.
>
>Another wanted to have some kind of doi for guix describe + manifest (a
>better UI and easier thing to cite in a paper I suppose).
>
>Another was asking about the possibility ofusing Guix to have multiple
>kernels and boot a debian with guix's kernel (so as to choose a
>compatible kernel at boot iiuc).
>
>The person I talked to at lunch was a bit skeptical about Guix. They
>have it and Nix, with module on their cluster. They told me they were
>more concerned about replicability than reproducibility. Also, their
>users are lost between the options, they have trouble getting help on
>guix from their admins and they end up using conda, yet another tool
>^^".
>
>That's only a few conversations that really marked me, but I had more,
>and I'll hopefully have more this afternoon and tomorrow.
>
>Marc, who organised the guile and guix days in Strasbourg last summer
>is here too and said he will write a tutorial on using vin to program
>in scheme. I'm lookinq forward to reading it!
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
[-- Attachment #2: Type: text/html, Size: 2041 bytes --]
next prev parent reply other threads:[~2019-12-05 14:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:16 Feedback from JRES in Dijon Julien Lepiller
2019-12-05 14:34 ` Pierre Neidhardt
2019-12-05 14:42 ` Julien Lepiller
2019-12-05 15:44 ` Konrad Hinsen
2019-12-05 15:52 ` zimoun
2019-12-06 7:07 ` Bengt Richter
2019-12-06 12:24 ` Konrad Hinsen
2019-12-07 16:35 ` Timothy Sample
2019-12-08 2:48 ` Bengt Richter
2019-12-08 4:11 ` Timothy Sample
2019-12-08 23:09 ` Bengt Richter
2019-12-09 5:23 ` Konrad Hinsen
2019-12-06 12:57 ` Konrad Hinsen
2019-12-10 16:57 ` Ludovic Courtès
2019-12-11 20:48 ` Konrad Hinsen
2020-01-07 16:05 ` Proposal for a blog contribution on reproducible computations Konrad Hinsen
2020-01-09 20:40 ` zimoun
2020-01-10 16:59 ` Ludovic Courtès
2020-01-10 17:19 ` zimoun
2020-01-10 18:53 ` Giovanni Biscuolo
2020-01-11 9:31 ` Konrad Hinsen
2020-01-11 14:05 ` Giovanni Biscuolo
2020-01-13 8:37 ` Ludovic Courtès
2020-01-14 9:06 ` Konrad Hinsen
2020-01-14 15:38 ` Ludovic Courtès
2020-01-14 16:18 ` Konrad Hinsen
2020-01-14 16:40 ` Ludovic Courtès
2020-01-10 17:03 ` Ludovic Courtès
2020-01-11 9:39 ` Konrad Hinsen
2020-01-15 22:20 ` Ludovic Courtès
2019-12-05 15:47 ` Feedback from JRES in Dijon zimoun
2019-12-05 14:39 ` Julien Lepiller [this message]
2019-12-05 15:42 ` zimoun
2019-12-10 17:06 ` Ludovic Courtès
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=105BA2D7-8B46-409F-9188-4DA5EC41DC3C@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@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).