From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Jeremy Olexa <darkside@gentoo.org>, Mike Frysinger <vapier@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 13:17:46 +0530 [thread overview]
Message-ID: <AANLkTik=cLPnD5Y7akyM0xsPgOC7+cvVOh=bj1Opir_y@mail.gmail.com> (raw)
In-Reply-To: <4D8EC104.4090503@gentoo.org>
On Sun, Mar 27, 2011 at 10:15 AM, Jeremy Olexa <darkside@gentoo.org> wrote:
> On 03/26/2011 12:52 AM, Mike Frysinger (vapier) wrote:
>
>> Index: metadata.xml
>> ===================================================================
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
>> <pkgmetadata>
>> <herd>no-herd</herd>
>> <maintainer>
>> <email>maintainer-needed@gentoo.org</email>
>> </maintainer>
>> </pkgmetadata>
>
> Can this practice of adding m-n packages to gentoo-x86 be stopped? If you
> add it, take responsibility for it, please. If you don't want to take
> responsibility for it, at least find a team that is willing to look after
> it.
>
If you prohibit people from doing that, they'll just commit it
normally, and then remove themselves a week later.
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.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2011-03-27 7:48 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 [this message]
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
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='AANLkTik=cLPnD5Y7akyM0xsPgOC7+cvVOh=bj1Opir_y@mail.gmail.com' \
--to=nirbheek@gentoo.org \
--cc=darkside@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vapier@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