public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: maintainer-wanted bugcount
Date: Mon, 26 Nov 2007 17:54:27 +0100	[thread overview]
Message-ID: <200711261754.27816.george@gentoo.org> (raw)
In-Reply-To: <fiel19$567$1@ger.gmane.org>

Monday, 26. November 2007, Markus Ullmann Ви написали:
> Robin H. Johnson schrieb:
> > On Mon, Nov 26, 2007 at 10:46:12AM +0100, Markus Ullmann wrote:
> > d) In addition to c), keep them open, flagged with sunrise in the status
> >    board, so that when a developer does want some package not in the
> >    tree, they can search first.
>
> That's done already
So what's the problem? 

The only onse where there is a valid issue, I think, are the ones where 
upstream has gone missing or no longer supports the package. (Even "better 
alternatives" thing is questionable IMHO. There are always people who have a 
different idea of better :)). These can be dealt with by having a dedicated 
force, perhaps comprised of people most annoyed by these bugs ;), who would 
simply scan the bugzilla for maintainer-wanted bugs, check the upstream and, 
if it is dead, close the bug with INVALID and a note of a dead upstream..

>
> > e) Encourage existing developers to review and commit this stuff more
> >    often.
>
> That would be the best option
Except the issue with all these packages is not committing but maintaining 
them. Sure, we could go on a committing spree and never touch any of these 
packages again. We even had such a situation at one point (rather long time 
ago) and it is specifically discouraged now.
The "really best" option would be recruiting new devs so that we have enogh 
people to maintain everything and add more, as was already suggested. This in 
fact does happen, it is just that the rate of new joins cannot be infinite 
plus we seem to experience our growing pains periodically..

George
--
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-11-26 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26  9:46 [gentoo-dev] maintainer-wanted bugcount Markus Ullmann
2007-11-26 10:29 ` Andrey Falko
2007-11-26 11:01 ` Robin H. Johnson
2007-11-26 13:26   ` [gentoo-dev] " Ryan Hill
2007-11-26 14:25   ` Markus Ullmann
2007-11-26 16:54     ` George Shapovalov [this message]
2007-11-26 18:16       ` Markus Ullmann
2007-11-27 17:04         ` Daniel Drake

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=200711261754.27816.george@gentoo.org \
    --to=george@gentoo.org \
    --cc=gentoo-dev@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