unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: "Sarthak Shah" <shahsarthakw@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Interest in Participating for GSoC '23
Date: Tue, 21 Mar 2023 19:52:31 +0100	[thread overview]
Message-ID: <87wn3aq6mo.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CADBZEVm_va0WdFDJs-hzTVnSpB9NP6F_n0JVTu-40TgtmPxmtw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

Hi Sarthak,

Just chiming in on one of your questions.

Sarthak Shah <shahsarthakw@gmail.com> writes:

> Hi Ludovic,
> Thank you for your suggestions!
> I've decided to focus on parameterized packages for my GSoC Application.
> Owing to mid semester exams, I have not been able to contribute much to
> Guix up until recently, and as such my only contributions are a simple
> patch and two packages. I am currently in the process of working on a
> script similar to NixOS' command-not-found that relies on guix index (which
> is yet to be merged).
> I have four questions with regards to my application and I'd appreciate
> answers from individuals in the mailing list;
> 1. Are there any specific issues I could work on to develop a better
> understanding of package transformations and also prove my skills

I think the issue mentioned in the last message at [1] could be a good
start, though it may require some knowledge of Guix, mostly through its
G-Expressions!  You would have to extend the transformation to consider
the case where the source is not a directory.

> 2. What is expected from a project proposal
> 3. Is there a soft deadline for submitting the draft proposal
> 4. Would anyone here be interested in co-mentoring this project

I unfortunately don't think I can co-mentor the project, but I'll always
be happy to answer questions whenever I'm available :)

[1] https://issues.guix.gnu.org/61684#16

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

      reply	other threads:[~2023-03-21 18:53 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
2023-03-21 11:06   ` Sarthak Shah
2023-03-21 18:52     ` Josselin Poiret [this message]

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=87wn3aq6mo.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).