I am not following this line of reasoning: how can adding guidance /
instructions on how to write a good bug report turn people away?
In a previous life, I have studied the factors that shorten the time
required to fix a big. Bugreports that contain steps to reproduce are a
significant predictor to shorten
the time to fix a bug. You can find the paper here:
http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1507233
A systematic lack of replies is also an issue but this solution was not
aimed at fixing that problem.
On Mon, Feb 14, 2011 at 4:39 AM, Bryan Tong Minh
<bryan.tongminh(a)gmail.com>wrote;wrote:
On Mon, Feb 14, 2011 at 2:46 AM, Diederik van Liere
<dvanliere(a)gmail.com>
wrote:
So maybe we can paste these 5 steps (or something
similar) in the initial
form used to file a bugreport.
This would increase the quality of bugreports and make it easier for bug
triaging.
Increase the quality perhaps, but also increase the the barrier of
reporting bugs, and that is something that is not very good imho.
I don't think we have a systematic problem with bad bug reports. The
systematic problem is the lack of replies from developers.
Bryan
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
<a href="http://about.me/diederik">Check out my about.me
profile!</a>