From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mark H Weaver <mhw@netris.org>,
Christopher Baines <mail@cbaines.net>,
guix-devel@gnu.org
Subject: Re: GNOME 40 work should be done on Savannah
Date: Wed, 31 Mar 2021 02:16:01 +0200 [thread overview]
Message-ID: <d4c214a30b98829f98bf402087ede6763b099890.camel@zaclys.net> (raw)
In-Reply-To: <87wntog7r7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Tue, 2021-03-30 at 14:12 +0200, Ludovic Courtès wrote:
> > I don't feel like people should be barred to contribute to that
> > GNOME
> > 40 upgrade because they arent an approved committer. That doesnt
> > feel
> > inclusive to me.
>
> I respectfully think you misunderstand the review process. Review is
> about sharing responsibilities and reducing the likelihood of
> mistakes.
Additionally, please put that quote into it's surrounding context and
don't assume things I have not said, I was explicitly speaking about
wip branches on Savannah excluding non-committers from collaborating on
them easily.
If I created a wip-gnome-40 branch on Savannah then Raghav cannot push
and we cannot work together easily, that way the GNOME 40 upgrade
probably wont happen because Raghav is already tired I felt in some
way.
I think the way we work here is the best conditions to capture Raghav's
motivation and energy right now and invest it within this GNOME 40
upgrade before they give up and we don't have this GNOME 40 upgrade
worked on. We need git to collaborate on patches together, that's all.
But those patches of course do get through the review process, first
with me reviewing changes as they happen, then as a whole also, because
we wont push anything to core-updates, master or else without review.
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-31 0:17 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 [this message]
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
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=d4c214a30b98829f98bf402087ede6763b099890.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=mhw@netris.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).