all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Blackbeard <barbanegra+guix@posteo.mx>
Cc: guix-devel@gnu.org
Subject: Re: [GSOC 2020] Introduction and asking for feedback
Date: Wed, 11 Mar 2020 15:35:21 +0100	[thread overview]
Message-ID: <87zhcngdsm.fsf@gnu.org> (raw)
In-Reply-To: <3eff499a-b60a-6952-9e6f-0e3aa9fd337f@posteo.mx> (Blackbeard's message of "Fri, 6 Mar 2020 00:33:53 -0600")

Hi Alberto,

Blackbeard <barbanegra+guix@posteo.mx> skribis:

> I want to apply to Google Summer of Code. The ideas I am most interested are
> a) for GNU Guix: 'Content-addressed protocol for substitutes' and b) for
> GNU Shepherd:  "Syntax and semantics of systemd units in the Shepherd",
> because I have a feeling any of this two would improve the experience
> of most
> Guix users.
>
> However, I would like to ask for feedback in which might be a better option,
> I would like to chose a project that I can get help and the community is
> interested in.
>
> Any help with the project and proposal would be much appreciated.

I’ll answer because I’m listed as mentor at
<https://libreplanet.org/wiki/Group:Guix/GSoC-2020>, though honestly, I
think this would have to be someone else or you’ll get very frustrated.
:-)

For both projects, I encourage you to follow the links to get a better
understanding of what the project means.  For project (a), please also
familiarize yourself with substitutes, how they work, and perhaps have a
look at the (guix scripts substitute) and (guix scripts publish) modules
(they may be intimidating at first, so don’t expect to grasp every
detail from day 1, that’s fine!).

For project (b), I’d encourage you to take a look at the Shepherd: it’s
a small project and relatively easy to follow, I think.  If you’re not
familiar with systemd units, you can read
<https://www.freedesktop.org/software/systemd/man/systemd.service.html>
and find what mechanisms are missing from the Shepherd’s API at
<https://www.gnu.org/software/shepherd/manual/html_node/Service-De_002d-and-Constructors.html>.
Pick a specific feature (e.g., “socket activation”), and think about
what it would take to implement it in the Shepherd.

From there, you can go ahead and ask specific questions about things you
don’t understand here or on IRC.

Happy hacking!  :-)

Ludo’.

      reply	other threads:[~2020-03-11 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  6:33 [GSOC 2020] Introduction and asking for feedback Blackbeard
2020-03-11 14:35 ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhcngdsm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=barbanegra+guix@posteo.mx \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.