From: Martin Schlemmer <azarah@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:12:31 +0200 [thread overview]
Message-ID: <1126541552.14207.61.camel@lycan.lan> (raw)
In-Reply-To: <1126539707.10549.19.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
On Mon, 2005-09-12 at 11:41 -0400, Peter Hyman wrote:
> On Mon, 2005-09-12 at 16:28 +0200, Maurice van der Pot wrote:
> > On Mon, Sep 12, 2005 at 10:03:17AM -0400, Chris Gianelloni wrote:
> > > Many users seem to think
> > > that a WONTFIX is non-negotiable. I tend to agree with them, for the
> > > most part. Rather than WONTFIX them, simply tell them that they won't
> > > be included as-is. WONTFIX gives the user the impression that we are
> > > not interested in their work or the package, when this is not the case.
> >
> > But if a developer tells them what is wrong and to reopen the bug when
> > they've fixed it, it shouldn't be a problem. And that's what I've seen
> > in this case.
> >
>
> I think you all misunderstand MY position on this. I provided ebuilds in
> the hope it would save the maintainers time and effort. If the work I
> did is 90% to spec, then there really is no reason for the maintainer
> NOT to take it, tweak it, and maybe send a note or add a comment to the
> bug as to what was fixed. It would ensure two things: 1) that the user
> will (hopefully) not make the same mistake again, and 2) get the ebuild
> upstream quicker.
>
> Sending it back to the contributor only will waste more time.
>
You will get exactly the same effect if you were to send a patch to LKML
to fix or improve some or other part of the kernel, and either the
coding style, or the way it is fixed is not to Linus or the specific
subsystem maintainer's liking.
The general idea is that if somebody want to get involved, they should
be prepared to to take the time to learn how to do fairly decent
patches/whatever. This makes review easier, and also minimises the
workload on whatever maintainer.
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-12 16:14 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 [this message]
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 ` 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=1126541552.14207.61.camel@lycan.lan \
--to=azarah@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