From: "Ludovic Courtès" <ludo@gnu.org>
To: Sarthak Shah <shahsarthakw@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Interest in Participating for GSoC '23
Date: Mon, 06 Mar 2023 21:46:43 +0100 [thread overview]
Message-ID: <87jzzt6218.fsf@gnu.org> (raw)
In-Reply-To: <CADBZEVnhWAzt9eo32ZEhB5gvuhP4W0KY53RbdCAXtFTd7GiRVA@mail.gmail.com> (Sarthak Shah's message of "Wed, 1 Mar 2023 06:08:49 +0530")
Hi Sarthak,
Sarthak Shah <shahsarthakw@gmail.com> skribis:
> Hello! I'm interested in contributing to the GNU Guix project through the
> Google Summer of Code program.
> My programming expertise mainly lies with Scheme, Common Lisp, Clojure and
> C/C++, but I can also write code in other languages when needed.
> Additionally, I have some experience as a system administrator of my
> university's HPC system.
> I am also the president of my college's equivalent of a GNU/Linux advocacy
> group, through which I have organized and facilitated GNU/Linux
> installation workshops to introduce my classmates and juniors to free
> software.
Nice, welcome!
> - Continued Rewrite of the Build Daemon in Guile
> <https://libreplanet.org/wiki/Group:Guix/GSoC-2018#Continue_rewrite_build_daemon_in_Guile_Scheme>
> (Mentors
> mentioned: Ludovic (+ David, +...?))
> (If I understand correctly, this will be a continuation of reepca's work
> in 2017
> <https://lists.gnu.org/archive/html/guix-devel/2017-08/msg00267.html>)
I didn’t copy this project over to the GSoC-2023 page because at this
stage I’m no longer sure whether GSoC is the right way for the project
to make further progress on this. I think developers in the community
already experienced with Guix internals and with Fibers will have to
dive in.
[...]
> Apart from the listed projects, I'm also interested in having parameterized
> packages
> <https://lists.gnu.org/archive/html/guix-devel/2020-11/msg00312.html> in
> Guix.
That’s a good idea. If you can become familiar with the details, I can
co-mentor it—which means we’d need to find a co-mentor. :-)
> It's tradition for potential GSoC participants to help resolve issues
> before applying in preparation for the actual task, so I would appreciate
> suggestions on problems I could help with.
I would suggest “poking around” generally speaking, which means first
installing it. 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, for instance package transformations: there are a couple of open
issues at <https://issues.guix.gnu.org> that you might want to read, or
perhaps you’ll have ideas of new transformations to add?
Thanks for reaching out!
Ludo’.
next prev parent reply other threads:[~2023-03-06 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 0:38 Interest in Participating for GSoC '23 Sarthak Shah
2023-03-06 20:46 ` Ludovic Courtès [this message]
2023-03-21 11:06 ` Sarthak Shah
2023-03-21 18:52 ` Josselin Poiret
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=87jzzt6218.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=shahsarthakw@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).