From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
"Konrad Hinsen" <konrad.hinsen@cnrs.fr>
Cc: guix-devel <guix-devel@gnu.org>, guix-hpc@gnu.org
Subject: Re: “Reproducible research articles, from source code to PDF”
Date: Thu, 18 Jun 2020 14:56:26 +0200 [thread overview]
Message-ID: <86lfkkwn0l.fsf@gmail.com> (raw)
In-Reply-To: <87r1ucmwh5.fsf@inria.fr>
On Thu, 18 Jun 2020 at 13:42, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
>> I'd start somewhat differently: generate diverse use case examples. The
>> contributions to the ReScience reproducibility challenge could be a nice
>> starting point: go through them, one by one, and try to re-implement the
>> authors' various approaches with Guix. Then, in a second step, try to
>> identify additional tooling support in Guix that would make the recipes
>> simpler to implement. That might well lead to the development of ready
>> to use templates, but I prefer starting from a use case analysis to see
>> what is needed in real life.
>
> Yes, sounds like a good plan!
Maybe we could organize a Virtual Hackathon? Over 1 day? Or 2 days?
The power of collective motivation. :-)
next prev parent reply other threads:[~2020-06-18 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 12:25 “Reproducible research articles, from source code to PDF” Ludovic Courtès
2020-06-17 7:06 ` zimoun
2020-06-18 7:31 ` Ludovic Courtès
2020-06-18 9:37 ` Konrad Hinsen
2020-06-18 11:42 ` Ludovic Courtès
2020-06-18 12:56 ` zimoun [this message]
2020-06-18 13:05 ` Ludovic Courtès
2020-06-18 16:28 ` Konrad Hinsen
2020-06-19 12:04 ` Ludovic Courtès
2020-06-19 12:14 ` zimoun
2020-06-19 13:21 ` Ludovic Courtès
2020-06-21 14:50 ` Konrad Hinsen
2020-06-22 7:38 ` Ludovic Courtès
2020-06-18 16:39 ` Pjotr Prins
2020-06-18 2:33 ` Maxim Cournoyer
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=86lfkkwn0l.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=konrad.hinsen@cnrs.fr \
--cc=ludovic.courtes@inria.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).