From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ROX: maintainer-wanted and apps out of date
Date: Mon, 12 Sep 2005 18:40:35 +0100 [thread overview]
Message-ID: <20050912184035.3129f047@snowdrop.home> (raw)
In-Reply-To: <200509121932.37955.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
On Mon, 12 Sep 2005 19:32:32 +0200 Carsten Lohrke <carlo@gentoo.org>
wrote:
| On Monday 12 September 2005 19:03, Ciaran McCreesh wrote:
| > The easiest way to improve those ebuilds' chances
| > of getting into the tree is by getting them up to a good enough
| > standard that whoever picks them up is very unlikely to have to do
| > major extra work on them.
|
| To have even more unmaintained packages in the tree. The tree it is
| that needs QA. If "maintainer-wanted" bugs stay open forever - who
| cares.
The people who work with maintainer-wanted care.
| > It was discussed on this list.
|
| Thanks for the pointer. :p So from the user point of view it's better
| to file a request without attaching an ebuild, because it wouldn't
| directly resolved WONTFIX?! (Before you answer that: From the user
| point of view, not your's.) I mean I'm often giving a pointer on an
| formal issue or a very wrong attempt, but being that strict is not
| neecessary, discouraging and probably some even take the chance to
| molest about Gentoo, imho.
Not really. It's pretty likely that anyone who looks seriously at
maintainer-wanted will include "and KEYWORDS includes EBUILD" in their
search. They'll probably include "and KEYWORDS includes REVIEWED" too...
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-12 17:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 13:58 [gentoo-dev] ROX: maintainer-wanted and apps out of date Peter Hyman
2005-09-11 15:50 ` Maurice van der Pot
2005-09-11 16:42 ` Peter Hyman
2005-09-11 19:24 ` Maurice van der Pot
2005-09-11 21:02 ` Alin Nastac
2005-09-12 0:10 ` Aron Griffis
2005-09-12 7:04 ` Alin Nastac
2005-09-12 0:14 ` Peter Hyman
2005-09-12 0:25 ` Ciaran McCreesh
2005-09-12 0:38 ` Alec Warner
2005-09-12 11:55 ` Carsten Lohrke
2005-09-12 14:03 ` Chris Gianelloni
2005-09-12 14:26 ` Re[2]: " Jakub Moc
2005-09-12 14:28 ` Maurice van der Pot
2005-09-12 15:41 ` Peter Hyman
2005-09-12 16:12 ` Martin Schlemmer
2005-09-12 17:00 ` Peter Hyman
2005-09-12 17:12 ` Jan Kundrát
2005-09-12 17:25 ` Stephen P. Becker
2005-09-12 17:51 ` Chris Gianelloni
2005-09-12 17:03 ` Ciaran McCreesh
2005-09-12 17:32 ` Carsten Lohrke
2005-09-12 17:40 ` Ciaran McCreesh [this message]
2005-09-12 17:56 ` Re[2]: " Jakub Moc
2005-09-12 18:53 ` Carsten Lohrke
2005-09-12 19:21 ` Ciaran McCreesh
2005-09-13 0:20 ` Nathan L. Adams
2005-09-12 19:26 ` [gentoo-dev] " Dan Meltzer
2005-09-12 0:27 ` [gentoo-dev] " Stephen P. Becker
2005-09-12 0:36 ` Peter Hyman
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=20050912184035.3129f047@snowdrop.home \
--to=ciaranm@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