On 05/13/2013 12:11 PM, Luke Sneeringer wrote:
> On May 13, 2013, at 10:06 AM, AK <[email protected]> wrote:
>
>> WONTFIX does sound rude to me, as well. Perhaps 'onholdindefinite' can
>> be used instead, the effective meaning is the same, just the term itself
>> is more polite. It seems that nobody looking at it would think "I'll
>> just wait for a while and surely it'll get fixed.". Instead, anyone
>> needing it would think "If it is to be fixed, it's clear someone has
>> to make a case for it." -ak
>
> Note: "won't fix" is used on many bug systems, not just Django. So,
in choosing to go for a euphemism, you're also (unintentionally)
obfuscating, because you're subtly communicating that it's somehow
different than the standard "won't fix".
>
> Best Regards,
> Luke Sneeringer
>
I should have mentioned that I know it's used on other bug systems, and
that I agree it's less clear. It's a tradeoff that you often have when
you try to be polite: the alternatives are usually more blunt and clear.
In this particular case, I don't think it's a problem because there are
only two choices here - either someone cares about the ticket being
fixed, or not.
If not, there's no problem. If yes, the main message will not be lost:
"this ticket isn't going to get fixed and you have to convince someone
if you want that to happen."
I agree 'onholdindefinite' is a bit awkward, I think it's a bit better
than wontfix but wontfix isn't terrible either.
-ak
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.