unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Karim Taha <kariem.taha2.7@gmail.com>, guix-devel@gnu.org
Subject: Re: GSoC 2023
Date: Wed, 08 Mar 2023 18:32:51 +0100	[thread overview]
Message-ID: <86mt4nb130.fsf@gmail.com> (raw)
In-Reply-To: <CAHNti2e-0rHnq4_6aZJAaVhpWTNab=ChvkaoafikVhFm8M-d8Q@mail.gmail.com>

Hi,

On Mon, 06 Mar 2023 at 23:44, Karim Taha <kariem.taha2.7@gmail.com> wrote:

> Hello all, I'm Karim Taha, a senior computer engineering student at
> Cairo University. I'm interested in the Guix project list for the 2023 GSoC
> program. I would like to work on ' Robustify long-term support for
> Reproducible Research' project', I can write c/c++, python, haskell, elisp
> and scheme. My main OS is Arch linux. I would like to know if there are any
> required skills. I hope you all have a nice day.

Thanks for your interest.

If you can become familiar with the details, I can co-mentor it—which
means we’d need to find a co-mentor.  :-)

I would suggest “poking around” generally speaking, which means first
installing Guix.  A good first contribution is often a package: one that
you’re missing, that needs an update, etc.

Then I’d encourage you to look more closely at the area you’re interest
in.  Well, from my point of view, a good way for diving into is by
investigating #51726 [1] #48540 [2] and probably more in the bug
tracker. 

1: http://issues.guix.gnu.org/issue/51726
2: http://issues.guix.gnu.org/issue/48540


Feel free to ask questions in guix-devel mailing list or IRC libera.chat
#guix or #guix-hpc.

Cheers,
simon




  reply	other threads:[~2023-03-08 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 21:44 GSoC 2023 Karim Taha
2023-03-08 17:32 ` Simon Tournier [this message]
2023-03-14 10:08   ` Simon Tournier

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=86mt4nb130.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=kariem.taha2.7@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.
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).