all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adopt a patch!
Date: Wed, 20 Sep 2017 07:21:55 +0200	[thread overview]
Message-ID: <20170920052155.GA1294@thebird.nl> (raw)
In-Reply-To: <ea515420.AEQAQWrlP5IAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZwSg8@mailjet.com>

On Tue, Sep 19, 2017 at 07:52:32PM +0530, Arun Isaac wrote:
> Just thinking out loud: Maybe, we need more people with commit
> access. Theoretically, anyone can review a patch, but ultimately it is
> people with commit access who will have to finally apply and push the
> patch. As the rate of submission of patches grows, this increases the
> work load on those with commit access.

Yes. We do need to think of scaling up even if it is not perceived a
direct problem now. The faster the turn around, the better it is for
submitters and therefore the project.

I think if we agreed that NO one can push their own commits directly
into master/gnu/packages and expand the number of committers greatly
(anyone who has successfully submitted a non-trivial package without
real comment) we can ask more people to look over the patch list. It
ain't that hard. And if someone misbehaves just revert on commit
access.

Some people may turn out to be very active when they get the chance.

Take a look at C4.1. Another Guix hacker pointed me to it about a year
ago. There are some solid ideas here:

http://hintjens.com/blog:93

I agree with Hintjens (who was btw one of the original FOSDEM
organizers) that the more dynamic a project becomes the more
contributions it will attract.

Keep experimenting - we can always revert on ideas. That is my motto.

Pj.

PS debbugs was a great step forward already.

  reply	other threads:[~2017-09-20  5:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11  8:13 Adopt a patch! Ludovic Courtès
2017-09-14  1:22 ` Arun Isaac
2017-09-14  4:26   ` ng0
     [not found] ` <4fecd5dd.AEQAQDR72NkAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZudnG@mailjet.com>
2017-09-17 20:04   ` Ludovic Courtès
2017-09-18 10:45     ` Ricardo Wurmus
2017-09-19 14:15     ` Maxim Cournoyer
2017-09-19 14:22     ` Arun Isaac
2017-09-20  5:21       ` Pjotr Prins [this message]
2017-09-20  6:11         ` ng0
2017-09-21  9:37         ` Arun Isaac
2017-09-21 11:25           ` Adonay Felipe Nogueira
2017-09-21 16:33             ` ng0
2017-09-20 11:48       ` Hartmut Goebel
2017-09-21 14:08         ` Ricardo Wurmus
2017-09-21 14:39           ` Maxim Cournoyer
2017-09-21 16:16             ` Adonay Felipe Nogueira
2017-09-21 20:31             ` Ricardo Wurmus
2017-09-22  5:02               ` Pjotr Prins
2017-09-22 12:15                 ` Kei Kebreau
2017-09-22 10:42               ` Thomas Danckaert
2017-09-22 14:22                 ` Ludovic Courtès
2017-10-14 21:26                   ` ng0
2017-09-22 19:45                 ` Maxim Cournoyer
2017-09-23 19:51                   ` Thomas Danckaert
2017-09-22  9:10           ` Hartmut Goebel
     [not found]     ` <3db6934a.AEQAQWrlP5MAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZwSg8@mailjet.com>
2017-10-13 13:08       ` Ludovic Courtès

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=20170920052155.GA1294@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=arunisaac@systemreboot.net \
    --cc=guix-devel@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 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.