From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Nirbheek Chauhan <nirbheek@gentoo.org>,
Jeremy Olexa <darkside@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Sun, 27 Mar 2011 19:17:53 +0000 [thread overview]
Message-ID: <AANLkTimoW4QOtSVNVKZZurp9XaSRaQApD9QEUxafxw=m@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikrbqVO6y-Pym+gEpGbEJYtRZmH8JnbpWcY+k5n@mail.gmail.com>
On Sun, Mar 27, 2011 at 1:43 PM, Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> On Sun, Mar 27, 2011 at 7:00 PM, Jeremy Olexa <darkside@gentoo.org> wrote:
>> On 03/27/2011 02:47 AM, Nirbheek Chauhan wrote:
>>> If you prohibit people from doing that, they'll just commit it
>>> normally, and then remove themselves a week later.
>>
>> Why does anyone need to *add* a package that is maintainer-needed? This is
>> one of the problems of the gentoo-x86 tree - too many maintainer-needed
>> packages.
>
> I'm just pointing out that if you prohibit that by policy, this is
> what people will do. The real problem is that maintainer-needed
> packages are allowed to remain in the tree *indefinitely*.
>
>>> I propose that we should be more aggressive about package.masking (for
>>> removal) all maintainer-needed packages from the tree by doing that
>>> one month after they become maintainer-needed. If someone doesn't
>>> volunteer to take care of it, it probably wasn't important anyway.
>>>
>>
>> That is abit extreme for me (read: I don't have motivation to fight the
>> flames), but I wouldn't complain if someone else did it to be honest.
>>
>
> Just start removing old[1] maintainer-needed packages. If people
> complain, tell them to start maintaining it. If they continue to
> complain, ignore them. As tree-cleaner, you have the power to do this
> and not take bullshit from people about it.
The intent of the TreeCleaner project (years ago) was to essentially
look for packages in bugzilla that had lots of bugs and no maintainer.
For a while beandog essentially maintained a site that tracked this
for us (Gentoo Package that need Lovin' was the awesome title.)
From that list you either fixed the problems and commited them (e.g.
you were a roving package maintainer) or you pmasked it and marked it
for the deadpool.
There is not much policy on treecleaning a package just because no one
has touched it. Time since last touch was just one of a dozen
indicators used to find packages that are broken (because a package
not touched since 2006 is also not likely to compile.)
-A
>
>
> 1. Set old as one month, with a 2 month package.mask duration before
> it's removed.
> --
> ~Nirbheek Chauhan
>
> Gentoo GNOME+Mozilla Team
>
>
next prev parent reply other threads:[~2011-03-27 19:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110326055210.E906D20054@flycatcher.gentoo.org>
2011-03-27 4:45 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml Jeremy Olexa
2011-03-27 7:47 ` Nirbheek Chauhan
2011-03-27 10:29 ` Markos Chandras
2011-03-27 9:39 ` Nirbheek Chauhan
2011-03-27 13:04 ` Treeclean all maintainer-needed packages, was: " Chí-Thanh Christopher Nguyễn
2011-03-27 15:37 ` Ryan Hill
2011-03-27 13:30 ` Jeremy Olexa
2011-03-27 13:43 ` Nirbheek Chauhan
2011-03-27 19:17 ` Alec Warner [this message]
2011-03-27 19:40 ` Nirbheek Chauhan
2011-03-27 20:17 ` Alec Warner
2011-03-27 21:25 ` Nirbheek Chauhan
2011-03-27 23:34 ` Ryan Hill
2011-03-28 1:59 ` Donnie Berkholz
2011-03-27 20:44 ` Rich Freeman
2011-03-27 21:09 ` Nirbheek Chauhan
2011-03-28 1:58 ` Donnie Berkholz
2011-03-27 21:28 ` René 'Necoro' Neumann
2011-04-05 4:26 ` Jeroen Roovers
2011-04-05 10:58 ` Alec Warner
2011-04-05 15:08 ` Jeroen Roovers
2011-04-18 17:56 ` Andreas K. Huettel
2011-03-27 13:44 ` Rich Freeman
2011-03-27 14:54 ` Tomáš Chvátal
2011-03-27 16:18 ` Rich Freeman
2011-03-27 14:08 ` Maintainership offering; was: " René 'Necoro' Neumann
2011-03-27 19:05 ` Jeremy Olexa
2011-03-27 20:20 ` Proxy maintainership of app-misc/pwsafe, was " Christopher Head
2011-03-27 20:47 ` Nirbheek Chauhan
2011-03-27 20:55 ` René 'Necoro' Neumann
2011-03-27 20:55 ` David Abbott
2011-03-27 21:32 ` Nirbheek Chauhan
2011-03-29 17:50 ` Dirkjan Ochtman
2011-03-29 13:33 ` Jeroen Roovers
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='AANLkTimoW4QOtSVNVKZZurp9XaSRaQApD9QEUxafxw=m@mail.gmail.com' \
--to=antarus@gentoo.org \
--cc=darkside@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=nirbheek@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