Hi Luke,

On Mon, 13 May 2013, 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".

I think it *IS* different to the standard "won't fix". The standard one implies "won't fix EVER" to me, whereas I think the way Django uses this status is "won't fix until someone persuades on the mailing list." Which could be expressed better than that, I'm sure. I did suggest a couple of other options: NEEDINFO and DISCUSSION. I could suggest some more: ITSAPONY? JUSTIFY?

I think we're lucky to have a community where it's possible to persuade the BDFLs to change their minds, and unlucky to have an unfriendly-looking bug tracker which dissuades people from trying.

Cheers, Chris.
--
Aptivate | http://www.aptivate.org | Phone: +44 1223 967 838
Future Business, Cam City FC, Milton Rd, Cambridge, CB4 1UY, UK

Aptivate is a not-for-profit company registered in England and Wales
with company number 04980791.

--
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.


Reply via email to