unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: guix-devel@gnu.org
Subject: Proposal for Outreachy (May-August 2020)
Date: Tue, 07 Jan 2020 11:31:07 +0000	[thread overview]
Message-ID: <229482977533dfdcef5a2d60bbc94aee@disroot.org> (raw)

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

Hello Guix Folks! I would like to contribute to Guix via Outreachy program. Based on domains listed in http://guix.gnu.org/contribute (http://guix.gnu.org/contribute/), I would like to work on "Packages". After brief discussion with Tobias (nckx) on IRC, I came up with following ideas. 1) Improve GNOME Software Stack and GNOME Desktop Environment's user-experience in Guix. (a) Revise Package(s): Add missing packages, remove deprecated packages and fix erroneous packages. (b) Revise Meta-Package(s): Clean-up gnome and create gnome-minimal. (c) Revise Package Module(s): Rebase gnome.scm and gnome-xyz-.scm into gnome-core.scm, gnome-deps.scm, gnome-sdk.scm and gnome-extras.scm. (d) Revise Service(s): Add missing services, remove deprecated services and fix erroneous services. (e) Revise Service Module(s): Rebase gnome-dektop-service-type and %desktop-services into gnome-desktop-service-type and gnome-minimal-desktop-service-type. 2) Improve Xfce Software Stack and Xfce Desktop Environment's user-experience in Guix. (a) Revise Package(s): Add missing packages, remove deprecated packages and fix erroneous packages. (b) Revise Meta-Package(s): Clean-up xfce and create xfce-minimal. (c) Revise Package Module(s): Rebase xfce.scm into xfce-core.scm, xfce-apps.scm, xfce-plugins.scm and xfce-bindings.scm. (d) Revise Service(s): Add missing services, remove deprecated services and fix erroneous services. (e) Revise Service Module(s): Rebase xfce-dektop-service-type and %desktop-services into xfce-desktop-service-type and xfce-minimal-desktop-service-type. We can discuss more in detail on IRC to see the gravity of these ideas and then it can be decided whether to go with (1) or (2) or both. Please let me know about your thoughts on this. Thank you! Regards, Raghav Gururajan.

[-- Attachment #2: Type: text/html, Size: 2087 bytes --]

             reply	other threads:[~2020-01-07 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 11:31 Raghav Gururajan [this message]
2020-01-07 11:32 ` Proposal for Outreachy (May-August 2020) Raghav Gururajan
2020-01-07 18:06   ` Jan
2020-01-08 10:40     ` Efraim Flashner
2020-01-08 15:15       ` Jan
2020-01-08  7:06   ` Raghav Gururajan
2020-01-08 15:05     ` Jan
2020-01-08  7:42   ` Raghav Gururajan
2020-01-08 14:59   ` Jesse Gibbons
2020-01-08 15:02     ` Raghav Gururajan
2020-01-09 19:54 ` Jan
2020-01-11 23:39   ` Ludovic Courtès
2020-01-12  1:15     ` Jan

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=229482977533dfdcef5a2d60bbc94aee@disroot.org \
    --to=raghavgururajan@disroot.org \
    --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 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).