On Mon, 08 Aug 2005 16:26:24 +0200, Alexander Sack <asac@jwsdot.com> said:
> Manoj Srivastava wrote:
>> My personal choice is to forward the bug reports in the cases it
>> makes sense, after triaging the report (yes, I triage rteports to
>> save my upstreams time); and in cases it makes sense, I ask thre
> But how do you judge that such a request makes sense?
Common sense? Experience? Exercising sound judgement about my
packages is, after all, one of the skills I bring to the table.
> In case of mozilla*s it is important to consider that upstream has a
> *really* restrictive policy of about what feature gets included in
> their "lightweight-apps" (ffox, tbird). So as a general rule of
> thumb it holds true that "feature requests don't make sense" by
> definition.
If those were my packages, I would either not as the user to
send things ahead, or determine if the wish was something I
reasonable even under upstream policy and go bat for the user.
If I felt strongly enough about the request, I might implement
it in Debian's package.
But those are not my packages, and we don't have concrete
wishlists to examine, and I would probably not have time to evaluate
them even if we did.
> So, should we close them all?
Who said anything about closing featrure requests?
> I don't think so, so for me it looks rather sane (in case of
> mozillas) to inform the submitter about those facts and give them
> hints about the procedure that has the highest probabily to succeed
> without wasting upstream resources (e.g. say they should first find
> some backup in the mozilla community in forums and mailing list
> before posting another enhancement bug that is likely not get
> implemented or is simply just ignored).
And, in any case, keep the bug open in Debian's BTS to record
progress, so that other people can either help, or not waste their
time.
manoj
--
When stupidity is a sufficient explanation, there is no need to have
any recourse to any other. -- Michael Uhlmann
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C