unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Etienne B. Roesch" <etienne.roesch@gmail.com>
To: Simon TOURNIER <simon.tournier@inserm.fr>
Cc: "guix-science@gnu.org" <guix-science@gnu.org>
Subject: Re: Hackatathon: 27th June! Let redo ReScience C.
Date: Wed, 17 May 2023 18:10:14 +0100	[thread overview]
Message-ID: <CAPX-MzAhfvncaMX8HFnQXVNKxuMKvU_5FgDwbYP4JNZ3b6N1jg@mail.gmail.com> (raw)
In-Reply-To: <96e447087983499c890e1fc4db3e7f04@inserm.fr>

[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]

Hi,

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 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

Etienne

On Fri, May 12, 2023 at 2:53 PM Simon TOURNIER <simon.tournier@inserm.fr>
wrote:

> Hi,
>
> It's time to run the second Reproducible Research hackathon!  The first
> one was from... 2020 [1], already!
>
> The date: *Tuesday June, 27th*.  Start: 9h30 (CEST) End: 17h30
>
> The plan is to discuss and pick some topics from 9h30 to 10h using one
> BigBlueButton instance (link provided later).  Then, let work together!
> For the ones who want, they can continue to use BBB for discussing, and
> others can synchronise using IRC (channel provides later).  Around noon,
> before lunch break, we all will report our progress on BBB.  Afternoon,
> repeat.  Last, we end with a discussion summarizing the successes or the
> roadblocks and draw the lines of the experiment report.
>
> Well, anyone could come with their own topic they want to redo.
>
> We suggest to pick articles from the ReScience C journal [2] -- they
> provide a high level of transparency about the materials required for
> redoing, IMHO.
>
> Who’s in?
>
> 1:
> https://hpc.guix.info/blog/2020/07/reproducible-research-hackathon-experience-report/
> 2: http://rescience.github.io
>
> Cheers,
> simon
>
>

[-- Attachment #2: Type: text/html, Size: 2642 bytes --]

  parent reply	other threads:[~2023-05-17 20:21 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 ` Etienne B. Roesch [this message]
2023-05-24 13:31   ` Hackatathon: " Ludovic Courtès
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

  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=CAPX-MzAhfvncaMX8HFnQXVNKxuMKvU_5FgDwbYP4JNZ3b6N1jg@mail.gmail.com \
    --to=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.
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).