<html><body bgcolor="#FFFFFF"><div>On 4 Jul 2010, at 00:11, Tim McNamara <<a href="mailto:paperless@timmcnamara.co.nz">paperless@timmcnamara.co.nz</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>Hi devs,<div><br></div><div>500+ unclosed bugs causes problems. I feel intimidated & overwhelmed by this number. I also find it difficult to find material sift through bug reports, to find areas where I can help (although, at the moment, I'm quite content with sugar-love level problems). However, 500+ bugs isn't that accurate. Some have been identified as upstream problems, but their resolution status remains open.</div>
<div><br></div><div>I suggest that we make more use of the "wontfix" resolution status. In 5 minutes, I've found some likely candidates. "wontfix" comes with a high risk of alienating people submitting bugs, but a polite note saying that it's upstream or possibly something like "Unfortunately, we have higher priority areas to work on right now. However we would welcome a patch if you are still wiling to work on this issue. It's great that you've taken the time to submit the bug, and we have looked into resolving things for you."</div>
<div><br></div><div>Some candidates: </div><div><br></div><div>wontfix - upstream</div><div> <a href="http://bugs.sugarlabs.org/ticket/1307"><a href="http://bugs.sugarlabs.org/ticket/1307">http://bugs.sugarlabs.org/ticket/1307</a></a></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
<br></div><div>wontfix - other priorities</div><div> <a href="http://bugs.sugarlabs.org/ticket/288"><a href="http://bugs.sugarlabs.org/ticket/288">http://bugs.sugarlabs.org/ticket/288</a></a> </div><div> <a href="http://bugs.sugarlabs.org/ticket/292"><a href="http://bugs.sugarlabs.org/ticket/292">http://bugs.sugarlabs.org/ticket/292</a></a></div>
<div><br></div><div>duplicates</div><div> <a href="http://bugs.sugarlabs.org/ticket/172"><a href="http://bugs.sugarlabs.org/ticket/172">http://bugs.sugarlabs.org/ticket/172</a></a></div><div> <a href="http://bugs.sugarlabs.org/ticket/394"><a href="http://bugs.sugarlabs.org/ticket/394">http://bugs.sugarlabs.org/ticket/394</a></a> </div>
<meta http-equiv="content-type" content="text/html; charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><div>I think that resolving bugs, even if by using the wontfix tag will make other areas easier.</div>
<div><br></div><div>Also, I don't know if I have the permission to change resolution status when something hasn't been touched for 12+ months. If I were to change status on likely candidates, would this anger the other developers?</div></div></blockquote><div><br></div><div>I know it's sensitive, for us slightly more delicate souls, but if you feel strongly about a bug status... I'd say go for its change of status. It will trigger either action/indifference from genuinely interested parties, possibly patches/discussion, action, and glory ;)</div><div><br></div><div>It seems fair to say there is some level of (completely understandable) analysis paralysis for some level of bugs. Bug triage activity is at a low at the moment. Don't apologise for bringing that task back up in everyones focus/face.</div><div><br></div><div>Regards,</div><div>--Gary </div><br><blockquote type="cite"><div>
<div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Tim</span><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Sugar-devel mailing list</span><br><span><a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a></span><br><span><a href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a></span><br></div></blockquote></body></html>