From: Raghav Gururajan <rg@raghavgururajan.name>
To: Guix Devel <guix-devel@gnu.org>
Cc: "Léo Le Bouter" <lle-bout@zaclys.net>,
zimoun <zimon.toutoune@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Mark H Weaver" <mhw@netris.org>, 宋文武 <iyzsong@outlook.com>
Subject: Re: GNOME 40
Date: Wed, 7 Apr 2021 15:10:44 -0400 [thread overview]
Message-ID: <7a76d9e6-1d2c-b456-ce46-767a248323a2@raghavgururajan.name> (raw)
In-Reply-To: <67c5aac2-2669-62dc-a82a-16c2bf9b554a@raghavgururajan.name>
[-- Attachment #1.1: Type: text/plain, Size: 1124 bytes --]
Hello Guix!
Sorry for the delayed response. I also didn't receive emails as I am not
subscribed to the list.
@Mark
Thanks for bringing up your concern, which is very valid. My hyper-focus
on working on GNOME40 slightly made me to overlook certain things like
mail-lists and reviews, even though I deeply value them.
@Chistopher @zimoun @civodul
Thank you all for your thoughts.
@Leo
It is very natural that one might miss certain things while intensively
working on something. Its great we had/have these folks and other
community members to have our backs by keeping us in check. :)
Let us do this,
[1] Create wip-gnome branch on savannah
[2] Create guix-patches thread for wip-gnome.
[3] Leo, me or anyone else can contribute by sending patches to that thread.
[4] Leo and I (hopefully after getting commit access) can review and
push the patches to wip-gnome.
[5] From wip-gnome, any existing committers can double-check and merge
commits to core-updates.
Sounds good for everyone?
Let us all work together and make Guix's GNOME awesome, comrades! :-)
Regards,
RG.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2021-04-07 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 13:19 GNOME 40 Raghav Gururajan
2021-03-28 15:16 ` Léo Le Bouter
2021-03-28 20:48 ` Mark H Weaver
2021-03-29 7:38 ` Christopher Baines
2021-03-29 23:02 ` GNOME 40 work should be done on Savannah (was: Re: GNOME 40) Mark H Weaver
2021-03-29 23:17 ` Léo Le Bouter
2021-03-30 6:41 ` Mark H Weaver
2021-03-30 11:12 ` zimoun
2021-03-30 23:50 ` Léo Le Bouter
2021-03-30 12:12 ` GNOME 40 work should be done on Savannah Ludovic Courtès
2021-03-31 0:06 ` Léo Le Bouter
2021-03-31 1:55 ` Mark H Weaver
2021-03-31 2:08 ` Léo Le Bouter
2021-03-31 0:16 ` Léo Le Bouter
2021-03-30 6:53 ` GNOME 40 work should be done on Savannah (was: Re: GNOME 40) Christopher Baines
2021-03-29 21:33 ` GNOME 40 Léo Le Bouter
2021-03-31 14:05 ` 宋文武
2021-03-29 11:41 ` Raghav Gururajan
[not found] ` <67c5aac2-2669-62dc-a82a-16c2bf9b554a@raghavgururajan.name>
2021-04-07 19:10 ` Raghav Gururajan [this message]
2021-04-10 7:09 ` 宋文武
2021-04-13 20:27 ` Mark H Weaver
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=7a76d9e6-1d2c-b456-ce46-767a248323a2@raghavgururajan.name \
--to=rg@raghavgururajan.name \
--cc=guix-devel@gnu.org \
--cc=iyzsong@outlook.com \
--cc=lle-bout@zaclys.net \
--cc=ludo@gnu.org \
--cc=mhw@netris.org \
--cc=zimon.toutoune@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).