unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Etienne B. Roesch" <etienne.roesch@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
	"guix-science@gnu.org" <guix-science@gnu.org>
Subject: Re: Hackatathon: 27th June! Let redo ReScience C.
Date: Wed, 31 May 2023 18:14:04 +0100	[thread overview]
Message-ID: <CAPX-MzAEu1=5TrZPZM668=8zTRy6zg-6JPXAjXKr-2SPUeMbkw@mail.gmail.com> (raw)
In-Reply-To: <86o7m0okoo.fsf@gmail.com>

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

Ludo, Simon,

I'll spare you the details, but I am organising a hackathon with students
from various campuses, in a few weeks, and I have decided to propose as a
project that we review the doc for guix, hoping that managing a (small)
horde of beginners will identify gaps and maybe produce useful
insights/content.
Any comment, recommendations, steer welcome.

Thanks for your talk Ludo this week, very cool!

Etienne (Reading, UK)

On Wed, May 31, 2023 at 11:33 AM Simon Tournier <zimon.toutoune@gmail.com>
wrote:

> Hi Ludo,
>
> On Wed, 24 May 2023 at 15:31, Ludovic Courtès <ludovic.courtes@inria.fr>
> wrote:
>
> > 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.
>
> Are you volunteering? ;-)
>
> It could be nice if we can have a list of papers from ReScience C.
> Then, it could helpful to spot out the tasks and how to start for
> Guixifying the paper.
>
> Well, I am pretty busy until Monday, 19th of June but I can dedicate
> some time for preparing these tasks after this date.
>
> WDYT about first collect some papers from ReScience C?
>
>
> Cheers,
> simon
>

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

  reply	other threads:[~2023-05-31 17:14 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
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 [this message]
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-MzAEu1=5TrZPZM668=8zTRy6zg-6JPXAjXKr-2SPUeMbkw@mail.gmail.com' \
    --to=etienne.roesch@gmail.com \
    --cc=guix-science@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    --cc=zimon.toutoune@gmail.com \
    /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).