public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] maintainer-wanted bugcount
Date: Mon, 26 Nov 2007 12:09:06 +0100	[thread overview]
Message-ID: <474AA952.5050103@gentoo.org> (raw)
In-Reply-To: <20071126100504.GN4368@supernova>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Donnie Berkholz wrote:
> On 10:46 Mon 26 Nov     , Markus Ullmann wrote:
>> when taking a look at the open bug count for bugs assigned to
>> maintainer-wanted (2450 at the time of writing), it seems pretty obvious
>> that we really can't handle all of them, at least not without growing at
>> least two dozen devs to maintain it properly.
>>
>> As I highly doubt this will happen within a week, we have to make a
>> decision how to proceed with this stuff. So what options do we have?
>> These come to mind:
>>
>> a) WONTFIX them within 4 or 8 weeks without picking them up
>> b) reassign them to herds (some herds are on CC) and have them
>>    respond withing 4-8 weeks and give a yey or boo.
>> c) let interested users move it to sunrise (some of them are there)
>>    so that the ebuilds are at least at our QA level we maintain for
>>    gentoo-x86 and are there to be picked up by devs if they're
>>    interested
> 
> What is bad about the current state of leaving maintainer-wanted bugs 
> open? What problem is it causing that you want to fix?

++, we should look at our prerecruitment process. Make it easier for
interested users to come into contact with the right herd/people, so that they
can be given simple tasks and guidance, learn and have fun.

Marijn

- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHSqlSp/VmCx0OL2wRAv2zAJ9hd9MPUfxmYJxEBO9M09LgeAy8oACdGdBb
PomZs9zmN7rEGR/vWrYsoMA=
=ohQI
-----END PGP SIGNATURE-----
-- 
gentoo-project@gentoo.org mailing list



  reply	other threads:[~2007-11-26 10:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26  9:46 [gentoo-project] maintainer-wanted bugcount Markus Ullmann
2007-11-26 10:05 ` [gentoo-project] Re: [gentoo-dev] " Donnie Berkholz
2007-11-26 11:09   ` Marijn Schouten (hkBst) [this message]
2007-11-26 13:12   ` Markus Ullmann
2007-11-26 19:34     ` Steve Long
2007-11-26 20:03     ` [gentoo-project] " Hans de Graaff
2007-11-27 17:44       ` [gentoo-project] " Steve Long
     [not found] ` <20071126110158.GG14557@curie-int.orbis-terrarum.net>
     [not found]   ` <fiel19$567$1@ger.gmane.org>
     [not found]     ` <200711261754.27816.george@gentoo.org>
2007-11-26 18:16       ` Markus Ullmann

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=474AA952.5050103@gentoo.org \
    --to=hkbst@gentoo.org \
    --cc=dberkholz@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox