On Thu, 02 Apr 2009 22:51:39 +0200, Henne Vogelsang wrote:
If a developer does that to me i ask why in the bug. I don't reopen it and try to explain why this specific bug is so important or anything i simply ask why he closed it in this fashion. Most times you will get an honest answer.
From a time perspective, if users are going to ask "why did you close
See, though, you're a geek like I am (and like the developer probably is) - you have an inverted "tact" filter. :-) Think of a tact filter as being like a firewall. Geeks filter inbound. Normal people filter outbound (they say "gee, should I say that or not" to themselves before they say something - in normal circumstances). The problem is often that Normals (and Geeks in some cases) assume everyone filters the same way they themselves do. It's generally human nature to assume (not consciously) that the reason others do things a certain way is because it's the way they would. Everyone only has their own experience as a frame of reference unless they consciously make an effort to put themselves in the other's shoes. What we're looking at here, I think, is (in some cases) those who filter inbound and those who filter outbound. this", it's less efficient to close without comment because then the developer has to close the bug again and explain why they closed it after being asked. It is more efficient to put the onus on the person who filed the bug to provide more information or to answer and close at the same time if that's the right thing to do.
From a community and overall project perspective, it would also seem to me to be more efficient to comment+close or ask for more information because that encourages the behaviour of users reporting bugs so the distro can be improved.
Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org