unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: GNOME 40 work should be done on Savannah
Date: Tue, 30 Mar 2021 14:12:44 +0200	[thread overview]
Message-ID: <87wntog7r7.fsf@gnu.org> (raw)
In-Reply-To: <35efe3776747ef36d6eec350843428fa0abf22fd.camel@zaclys.net> ("Léo Le Bouter"'s message of "Tue, 30 Mar 2021 01:17:59 +0200")

Hi Léo,

Léo Le Bouter <lle-bout@zaclys.net> skribis:

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

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


  parent reply	other threads:[~2021-03-30 12:15 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           ` Ludovic Courtès [this message]
2021-03-31  0:06             ` GNOME 40 work should be done on Savannah 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
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=87wntog7r7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=lle-bout@zaclys.net \
    /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).