unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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:06:29 +0200	[thread overview]
Message-ID: <daf4ffb72f959cc35ddd53b752a2ddee0fcb2fa5.camel@zaclys.net> (raw)
In-Reply-To: <87wntog7r7.fsf@gnu.org>

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

On Tue, 2021-03-30 at 14:12 +0200, Ludovic Courtès wrote:
> I respectfully think you misunderstand the review process.  Review is
> about sharing responsibilities and reducing the likelihood of
> mistakes.
> 
> It’s crucial from many different perspectives: security-wise,
> socially
> (the process is transparent, everyone gets a chance to chime in or to
> just see what’s cooking), and technically (we all learn and build
> better
> software, and we reduce the risk that users receive broken software
> on
> their next ‘guix pull’).
> 
> The process to get commit access is documented and it revolves around
> two criteria: the person must have experience with the project and
> must
> know the rules.
> 
> That’s not “bureaucracy”: it’s about building a community around
> mutual
> understanding of what each one of us may or may not expect from their
> peers.
> 
> 
> All that said, it’s of course fine to collaborate on external
> repositories, even though I agree with Mark that getting “closer” to
> Guix folks may be profitable to everyone.  In the end, work should be
> submitted for review, and for a patch set like this, it’ll probably
> be a
> ‘wip-’ branch on Savannah.
> 
> Thanks,
> Ludo’.

I think Mark misrepresents my sayings in their messages. 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? Don't we have the right
with Raghav to cooperate together on some patchset however we want? It
never meant that review process had to be skipped in ANY way.

Only Raghav and myself has showed up to cooperate on GNOME 40 upgrade
for now, and that's also why we are doing it this way.

I feel bad now that it seems like everyone assumes we are doing things
we are not.

Léo

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-03-31  0:06 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 [this message]
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
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=daf4ffb72f959cc35ddd53b752a2ddee0fcb2fa5.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).