all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adopt a patch!
Date: Thu, 14 Sep 2017 06:52:04 +0530	[thread overview]
Message-ID: <980b12b7.AEQAQDR72NgAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZudnG@mailjet.com> (raw)
In-Reply-To: <877ex5d555.fsf@gnu.org>


Would it help to have teams of maintainers for specific packages or a
specific category of packages? Perhaps something like Debian has? Right
now, anyone can review any package. But, no one is "responsible" for any
package, and this feels a little chaotic.

Also, should we accept any package into Guix (provided it is free
software, of course)? Or, should we pick and choose, packaging only
sufficiently mature software? What about unmaintained packages? Debian's
policy is to remove unmaintained packages. What is ours? Perhaps we need
some kind of package popularity contest like Debian has.

These questions are bothering me, because I feel we don't have
sufficient labour power to handle the enormous number of packages out
there. I've been meaning to raise these questions at some point. Though
these questions are somewhat tangential to this thread, I thought it
might be ok to raise them here.

  reply	other threads:[~2017-09-14  1:22 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 [this message]
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
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=980b12b7.AEQAQDR72NgAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZudnG@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --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 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.