unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Léo Le Bouter" <lle-bout@zaclys.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNOME 40 work should be done on Savannah
Date: Tue, 30 Mar 2021 21:55:12 -0400	[thread overview]
Message-ID: <87k0po13z8.fsf@netris.org> (raw)
In-Reply-To: <daf4ffb72f959cc35ddd53b752a2ddee0fcb2fa5.camel@zaclys.net>

Hi Léo,

Léo Le Bouter <lle-bout@zaclys.net> writes:
> I think Mark misrepresents my sayings in their messages.

I'm sorry if that happened.  It was not my intent.  Can you show me what
I wrote that misrepresents your position?

> We are ONLY using git to exchange work and collaborate on the patchset
> with Raghav, how else do you want us to work with Raghav on some git
> branch on Savannah if Raghav doesnt have commit access?

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.

> Don't we have the right with Raghav to cooperate together on some
> patchset however we want?

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.

(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.

(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.

Would this be acceptable to you?

    Regards,
      Mark


  reply	other threads:[~2021-03-31  1:57 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 [this message]
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
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=87k0po13z8.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=lle-bout@zaclys.net \
    --cc=ludo@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).