Hi Django devs,

I would like to raise a little concern I ran into lately. When going over some 
Oracle-related tickets, I came across ticket #20201[0] . The ticket 
description was missing important details, so I commented about them. A few 
days later, Aymeric came around, and closed the ticket as "needsinfo", 
referencing my comment. To me, this raised a couple of conflicting thoughts:

On one hand -- should I have closed it myself, and saved a core-dev the 
trouble? The triaging guide[1] seems very inconclusive about this, advising on 
other reasons to close tickets but not on needsinfo (except "tickets which are 
really feature requests").

On the other hand -- especially, in the wake of the "Perception of attitude in 
tickets" brouhaha -- should we really be closing tickets on needsinfo? In 
other communities, I have usually seen "needsinfo" as a ticket state, rather 
than a reason for closing; such tickets are then closed later, if enough time 
has passed and no further info is received. I realise that, when the person 
closing the ticket specifically says "when you have more info, please re-open" 
(as Aymeric did in this case), then the process is essentially the same, only 
a little more efficient; but I worry that this efficiency may carry a price in, 
as 
Simon put it, "perception of attitude in tickets". 

For what it's worth, I, personally, would feel much more at ease setting 
tickets as "needsinfo" without closing them -- and if it's a ticket state, 
there should be no problem taking such tickets out of the reports developers 
use, so they're almost as far out of the way as closed tickets.

Thanks for your consideration,

        Shai.

[0] https://code.djangoproject.com/ticket/20201
[1] https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/

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