From: Jakub Moc <jakub@gentoo.org>
To: Carsten Lohrke <gentoo-dev@lists.gentoo.org>
Subject: Re[2]: [gentoo-dev] ROX: maintainer-wanted and apps out of date
Date: Mon, 12 Sep 2005 19:56:20 +0200 [thread overview]
Message-ID: <1087814765.20050912195620@gentoo.org> (raw)
In-Reply-To: <200509121932.37955.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]
12.9.2005, 19:32:32, Carsten Lohrke wrote:
> 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.
[left for later reference]
> 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 at all. There are *lots* of people that actually fix their ebuilds very
quickly and appreciate the comments. And - as everywhere - there's also a bunch
of people that start bitching instead of taking 5 minutes to fix the thing.
Since you said above, that you really don't care if those user-submitted
ebuilds will ever get into portage or will stay in maintainer-wanted queue
forever and that's the stuff in portage that actually matters QA-wise, I'm
missing why are you worried about people not submitting their ebuilds any more.
At the very least, reviewing user-submitted ebuilds and marking things
WONTFIX/CANTFIX/REVIEWED makes it possible to filter out the outdated and
dead-upstream crap, as well as things about which those people who filed the
bugs don't care any more. And, if someone picks those ebuilds up and decides to
maintain them, he can focus more on testing the actual app then fixing a broken
ebuild (or even committing a broken ebuild into the tree).
--
Best regards,
Jakub Moc
mailto:jakub@gentoo.org
GPG signature: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xCEBA3D9E
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E
... still no signature ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]
next prev parent reply other threads:[~2005-09-12 18:00 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
2005-09-12 17:56 ` Jakub Moc [this message]
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=1087814765.20050912195620@gentoo.org \
--to=jakub@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