From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "Ludovic Courtès" <ludo@gnu.org>, "Zachary Liebl" <guix@zachliebl.com>
Cc: guix-devel@gnu.org
Subject: Re: Google Summer of Code Inquiry
Date: Fri, 29 Mar 2024 12:03:07 +0100 [thread overview]
Message-ID: <c38cecbe-53a8-630e-69a0-1632e8b6c757@elenq.tech> (raw)
In-Reply-To: <87cyrdicvg.fsf@gnu.org>
Hi all,
Yes, I proposed the project because that was something I wanted to do
myself, but I didn't have the time for.
As Ludo suggests, start getting familiar with Guix's codebase and usage.
I can help you with contribution later.
When digging on the code, this talk by Josselin Poiret is very helpful:
https://10years.guix.gnu.org/program/#guixy-guile-the-derivation-factory-a-tour-of-the-guix-source-tree
Feel free to contact us at any time and as questions. I more than open
to answer all I can.
Also, I recommend you take a look to what an AppImage is, if you are not
sure about it and how `guix pack` works, i.e. what contents do the
`pack`s have. Once you get that, it shouldn't be too hard to combine both.
Cheers,
Ekaitz
On 2024-03-29 10:52, Ludovic Courtès wrote:
> 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 11:03 UTC|newest]
Thread overview: 10+ 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
2024-03-29 11:03 ` Ekaitz Zarraga [this message]
-- 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
2024-06-12 6:44 ` Ada Stevenson
2024-06-12 6:51 ` Sebastian Dümcke
2024-06-12 9:24 ` Noé Lopez via Development of GNU Guix and the GNU System distribution.
2024-06-11 14:27 Noé Lopez via Development of GNU Guix and the GNU System distribution.
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=c38cecbe-53a8-630e-69a0-1632e8b6c757@elenq.tech \
--to=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=guix@zachliebl.com \
--cc=ludo@gnu.org \
/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).