From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: "Mark H Weaver" <mhw@netris.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: GNOME 40 work should be done on Savannah
Date: Wed, 31 Mar 2021 04:08:28 +0200 [thread overview]
Message-ID: <29cc8654696a9e563ea74bdf8bf52f64ae14cd1c.camel@zaclys.net> (raw)
In-Reply-To: <87k0po13z8.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]
On Tue, 2021-03-30 at 21:55 -0400, Mark H Weaver wrote:
> I'm sorry if that happened. It was not my intent. Can you show me
> what
> I wrote that misrepresents your position?
I don't have the energy now I feel already bad enough this discussion
even happened, in a way that even Ludo, the creator of the GNU Guix
project, ended up saying that they think I don't understand the review
process. I think I do understand it and I wonder why anyone made me a
GNU Guix committer if they think any other way.
> I answered essentially the same question in my last message, so I'm
> not
> sure why you're asking again. We've been successfully accepting
> contributions from non-committers for years.
I think one has to realize that being a non-committer is a really
frustrating experience even if your work is of good quality and that
frustrating experience is demotivating and makes people give up. And
having a branch and special relationship with a GNU Guix committer
(like what we're doing with Raghav) is helpful to capture Raghav's
motivation and energy in a way they do not get frustrated and give up.
> Yes, of course. To be clear: you are well within your *rights* to do
> so, regardless of what anyone else thinks.
>
> My main concerns are:
>
> (1) The primary branch for GNOME 40 work should be on Savannah, and
> that's where we should encourage Guix developers to do this work.
> No Guix developer should be asked to work on an external site in
> order to contribute to the GNOME 40 effort.
That's where it felt it was the best place to collaborate for me and
Raghav (non-committer).
>
> (2) Any work that you and Raghav do on an external site should be
> _regularly_ merged into Savannah, in manageable pieces, after
> being
> reviewed of course. If you do this, my concerns over review
> quality
> would be addressed.
We already seek to do this.
>
> (3) If changes are made on the 'wip' branch on Savannah that conflict
> with your preliminary work on an external site, it would be your
> responsibility to rebase your work as needed, just as anyone
> proposing a patch would be expected to do. That should be an
> incentive to submit your work to Savannah early and often.
If changes were to be made in a way that rebasing work and solving
conflicts becomes too much trouble we will probably give up (Raghav
probably) and there wont be any GNOME 40 upgrade.
> Would this be acceptable to you?
I don't even know anymore.
> Regards,
> Mark
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 2:08 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29cc8654696a9e563ea74bdf8bf52f64ae14cd1c.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 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.