From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Kierin Bell <fernseed@fernseed.me>
Cc: "Pjotr Prins" <pjotr.public12@thebird.nl>,
"Gábor Boskovits" <gboskovits@gmail.com>,
"Arun Isaac" <arunisaac@systemreboot.net>,
shahsarthakw@gmail.com, "Guix Devel" <guix-devel@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>
Subject: Re: GNU and GSoC
Date: Fri, 1 Mar 2024 22:43:02 +0100 [thread overview]
Message-ID: <20240301214302.2eupbxtpxur6kotn@mailx.thebird.nl> (raw)
In-Reply-To: <87edd24vs4.fsf@fernseed.me>
Thank you for the project idea. I will add it in.
More older proposals are listed here:
https://libreplanet.org/wiki/Group:Guix/GSoC-2023
any of these we want to submit again? New ideas welcome too!
I'll add the Guix-based build tool again (to replace autoconf and
friends) if nothing better comes along. Any Hurd ideas out there? How
about improved Guix support and test coverage? Or Mes - Ekaitz?
GSoC gives extra helpers.
Pj.
On Fri, Feb 23, 2024 at 06:15:39PM -0500, Kierin Bell wrote:
>
> Hey Guix,
>
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
>
> > The GNU project is a GSoC org again. Last year Sarthak did a great job
> > working on parameterization of Guix. It works, and you can try the
> > code. See
> >
> > => https://guix.gnu.org/blog/2023/parameterized-packages-for-gnu-guix/
> > => https://blog.lispy.tech/
> >
> > For this year GNU can propose projects again. We should suggest Guix,
> > Mes and Hurd projects in the coming two weeks. Ping Gábor, Sarthak,
> > Arun, Efraim or me if you are interested in co-mentoring an effort.
> >
>
> Please forgive my ignorance, but are non-mentors/prospective mentees
> allowed to suggest GSoC project ideas here?
>
> I have been wanting to work on implementing a general purpose
> pretty-printing/formatting module for Guix that services (and Guix
> system, style, Home, etc.) could use to serialize their given
> configuration languages. It would be better than manually formatting
> raw strings as is done now by most services. Ludo' first broached the
> topic in a patch review[1].
>
> The project feels to me like it would be much more attainable with
> advice from a seasoned Schemer/Guixer. So a mentor-mentee program could
> be a good fit.
>
> Again, I'm unsure exactly how this fits into the larger goals of the
> project. I suspect that services-related stuff like this may be lower
> on the hierarchy of priorities.
>
> [ Regardless, even if it turns out not to be a good fit for GSoC, I'd be
> delighted to work on this with a bit of help and advice as time
> allows. ]
>
> Best,
> Kierin
>
> [1] https://issues.guix.gnu.org/64620#15
--
prev parent reply other threads:[~2024-03-01 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 7:38 GNU and GSoC Pjotr Prins
2024-02-23 7:49 ` Ada Stevenson
2024-02-23 23:15 ` Kierin Bell
2024-03-01 21:43 ` Pjotr Prins [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=20240301214302.2eupbxtpxur6kotn@mailx.thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=arunisaac@systemreboot.net \
--cc=efraim@flashner.co.il \
--cc=fernseed@fernseed.me \
--cc=gboskovits@gmail.com \
--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).