From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: "Etienne B. Roesch" <etienne.roesch@gmail.com>
Cc: Simon TOURNIER <simon.tournier@inserm.fr>,
"guix-science@gnu.org" <guix-science@gnu.org>
Subject: Re: Hackatathon: 27th June! Let redo ReScience C.
Date: Wed, 24 May 2023 15:31:57 +0200 [thread overview]
Message-ID: <87o7m9n9de.fsf@gnu.org> (raw)
In-Reply-To: <CAPX-MzAhfvncaMX8HFnQXVNKxuMKvU_5FgDwbYP4JNZ3b6N1jg@mail.gmail.com> (Etienne B. Roesch's message of "Wed, 17 May 2023 18:10:14 +0100")
Hi Etienne,
"Etienne B. Roesch" <etienne.roesch@gmail.com> skribis:
> I am in. I have used both nix and guix, but I do consider myself a
> beginner. I am also a plain old researcher in neuroscience, albeit with
> formal training in software engineering. As such I think I would find it
> more valuable to spend time figuring out the best way to describe "a best
> practice" for people like me, onboarding newcomers, and write
> documentation, rather than figuring out why a Makefile doesn't compile and
> computer says no. I am also happy to join more experienced users, of
> course, and follow the flow.
I guess the goal is to make progress on providing Guix files that would
let us re-run code submitted in ReScience C papers (for instance). In
doing that, old-timers like me can of course provide guidance to onboard
newcomers: this exercise is meaningful if we make it approachable to a
wider scientific audience.
We seasoned users (Simon, Konrad, myself, and anyone who feels
qualified) should prepare upfront to get a more precise idea of the
tasks involved and how we can onboard people.
> I have timeblocked the whole, and I am relatively free of my own movement,
> but I can't promise I wouldn't be dragged into some boring meetings. I live
> in the UK (+1h), and speak English and French. :D
Awesome. :-)
BTW, the event will be in English but we can definitely onboard those
who might prefer to speak French or German.
Ludo’.
next prev parent reply other threads:[~2023-05-24 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:51 Hackatathon: 27th June! Let redo ReScience C Simon TOURNIER
2023-05-12 18:46 ` [Spam:]Hackatathon: " Konrad Hinsen
2023-05-17 17:10 ` Hackatathon: " Etienne B. Roesch
2023-05-24 13:31 ` Ludovic Courtès [this message]
2023-05-25 10:08 ` Etienne B. Roesch
2023-05-25 12:19 ` Konrad Hinsen
2023-05-25 12:31 ` Etienne B. Roesch
2023-05-25 12:40 ` Konrad Hinsen
2023-05-31 10:32 ` Simon Tournier
2023-05-31 17:14 ` Etienne B. Roesch
2023-06-26 16:05 ` Simon TOURNIER
2023-07-17 14:00 ` Hackatathon let redo, experience report Simon TOURNIER
[not found] <mailman.135.1684425636.22153.guix-science@gnu.org>
2023-05-18 17:15 ` Hackatathon: 27th June! Let redo ReScience C Peter Polidoro
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7m9n9de.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=etienne.roesch@gmail.com \
--cc=guix-science@gnu.org \
--cc=simon.tournier@inserm.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.