From: "Ludovic Courtès" <ludo@gnu.org>
To: "Sebastian Dümcke" <code@sam-d.com>
Cc: guix@zachliebl.com, guix-devel@gnu.org
Subject: Re: Google Summer of Code Inquiry
Date: Tue, 09 Apr 2024 17:25:35 +0200 [thread overview]
Message-ID: <87v84qmuc0.fsf@gnu.org> (raw)
In-Reply-To: <da0d84b3-eb8e-7f3b-6179-bd0b7ff40b42@sam-d.com> ("Sebastian Dümcke"'s message of "Mon, 1 Apr 2024 17:47:34 +0200")
Hi Sebastian,
Sebastian Dümcke <code@sam-d.com> skribis:
> just wanted to chime in. Since last week I have some working code to
> generate AppImages with guix pack. I was planning on tidying this up
> for submission over the next weeks.
> There is still work to do regarding documentation, adding options
> specific to the AppImage format, building the AppImageKit runtime from
> source and a lot of testing.
This is great news! Looking forward to incorporating those changes.
> However, I believe that the remaining effort is around 8-10 hours. I
> am happy to hand the code over to you to finish up and co-mentor
> (though this patch would be my first contribution to guix) if you
> think this is appropriate.
It does sound like it jeopardizes this specific project. In a way,
that’s a good problem to have as a project, but it does mean that
Zachary would need to look for another project (which could still be
related to ‘guix pack’).
Thoughts?
> PS: this is also my first message sent to a mailing list, hope it
> makes it through ok. Please point out any errors or breackes in
> netiquette
It’s perfect!
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-04-09 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 15:47 Google Summer of Code Inquiry Sebastian Dümcke
2024-04-09 15:25 ` Ludovic Courtès [this message]
2024-04-10 6:33 ` Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2024-03-27 23:00 Zachary Liebl
2024-03-29 9:52 ` Ludovic Courtès
2024-03-29 11:03 ` Ekaitz Zarraga
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=87v84qmuc0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=code@sam-d.com \
--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 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).