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:03:25 +0100 [thread overview]
Message-ID: <20050912180325.3d9bdb08@snowdrop.home> (raw)
In-Reply-To: <200509121356.02558.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
On Mon, 12 Sep 2005 13:55:55 +0200 Carsten Lohrke <carlo@gentoo.org>
wrote:
| On Monday 12 September 2005 02:25, Ciaran McCreesh wrote:
| > If you're not up for having your code reviewed, don't contribute to
| > an open source project. No-one expects you to produce perfect code
| > straight off (at least, we don't until we give you commit access).
| > We *do* expect you to be prepared to respond to constructive
| > criticism and improve your code.
|
| Personally I think you're just going a bit wild by closing the bug
| reports as wont fix and expecting users to fix them. That's part of
| developers job, if someone takes into account adding an ebuild to the
| official tree, isn't it?!
Stuff assigned to maintainer-wanted has no developer. From what we've
seen in the past, most of those ebuilds are pretty unlikely to ever get
a developer either. 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.
| While I can understand your motivation, I'd
| like to know if your doing is backed up by at least an informal
| decision (didn't follow the threads which resulted in the maintainer*
| aliases, etc.), because we have enough whining guys, who don't
| understand that our ressources are limited. Caring for the quality of
| stuff, that is not part of the official tree is only bad PR, but not
| a win for us, imho.
It was discussed on this list.
--
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:07 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 [this message]
2005-09-12 17:32 ` Carsten Lohrke
2005-09-12 17:40 ` Ciaran McCreesh
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=20050912180325.3d9bdb08@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