From: "Ludovic Courtès" <ludo@gnu.org>
To: Zachary Liebl <guix@zachliebl.com>
Cc: guix-devel@gnu.org, Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: Re: Google Summer of Code Inquiry
Date: Fri, 29 Mar 2024 10:52:19 +0100 [thread overview]
Message-ID: <87cyrdicvg.fsf@gnu.org> (raw)
In-Reply-To: <171158044005.7.1224328489903688445.295627009@zachliebl.com> (Zachary Liebl's message of "Thu, 28 Mar 2024 00:00:38 +0100 (CET)")
Hi Zachary,
Zachary Liebl <guix@zachliebl.com> skribis:
> I am interested in taking on one of your Google Summer of Code projects. I have been a long time NixOS user, and I need an excuse to finally get involved with Guix, and I think this is it.
>
> I am particularly interested in the project "Add support for AppImage in guix pack." What should my next steps be in my application for your GSoC project?
Thanks for reaching out to us! I’m Cc’ing Ekaitz who’s willing to
mentor this effort according to
<https://libreplanet.org/wiki/Group:Guix/GSoC-2024> (other people
familiar with ‘guix pack’, myself included, can give a hand during the
project).
The first steps for GSoC candidates is usually to get familiar with the
project and its code base. I would first recommend installing Guix and
playing around with it, including with ‘guix pack’. You could try
making a first contribution, for example by adding a package that you
need but is missing. Here’s a good entry point:
https://guix.gnu.org/manual/devel/en/html_node/Contributing.html
These are the first things that come to mind but Ekaitz might have other
ideas!
Cheers,
Ludo’.
next prev parent reply other threads:[~2024-03-29 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 23:00 Google Summer of Code Inquiry Zachary Liebl
2024-03-29 9:52 ` Ludovic Courtès [this message]
2024-03-29 11:03 ` Ekaitz Zarraga
-- strict thread matches above, loose matches on Subject: below --
2024-04-01 15:47 Sebastian Dümcke
2024-04-09 15:25 ` Ludovic Courtès
2024-04-10 6:33 ` Efraim Flashner
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=87cyrdicvg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=guix@zachliebl.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 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.