> leaving a ticket open is a better signal for inviting discussion and patches.
There's been over 22,000 issues raised in Django's history. It's understandable and desirable that maintainers close off tickets aggressively if they don't think they should be tackled. I wouldn't get too hung up on the process there - a sound argument and a bit of proactive work is all that's needed to convince folks to take the time to reassess something like that issue. Personally I think there's a good case to be made for this one so from my point of view, so I'd say go ahead, make the proposal, or better still a pull request, make the argument and *then* see if it is possible to reach a consensus. There's clearly absolutely no guarantee it'd be accepted (there's two core members in this thread making different judgement calls on it, so it's *far* from cut & dried) but you can be sure that folks are willing to put the time in to listen to anyone willing to put in a bit of legwork. Cheers, Tom :) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/14bdc9b2-3cd5-4ca8-945b-891884da7c5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
