<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <div class="main">Hello, ubuntu-devel. I just posted a blog entry urging people working on hundredpapercuts to help deal with the deluge of bugs being added to the project, the majority of which are invalid. In "phase 1" of hundredpapercuts, we encouraged people to report trivially fixable usability bugs affecting the default Ubuntu experience, and many such bugs were reported! Along with these reports came many people's pet bugs and rants (e.g. "fix my wifi!") so now we're entering "phase 2" of the project, where in addition to encouraging people to continue reporting potential paper cuts, we will begin encouraging people to triage incoming bugs. At this point, we are only encouraging people to mark bugs invalid in hundredpapercuts if they are very confident the bugs do not qualify. Please have a read, get involved, and by all means make alternate suggestions for how we can direct the course of this project. Thank you, David ####### (From <a class="moz-txt-link-freetext" href="http://blog.davebsd.com/2009/06/15/calling-all-paper-cutters/">http://blog.davebsd.com/2009/06/15/calling-all-paper-cutters/</a>) <a href="https://edge.launchpad.net/hundredpapercuts" onclick="javascript:pageTracker._trackPageview('/outbound/article/edge.launchpad.net');">One Hundred Paper Cuts</a> is off to a great start. After <a href="http://blog.davebsd.com/2009/06/10/one-hundred-paper-cuts/">my last post</a>, many people began adding existing bugs to the project, and filing new bugs as paper cuts. Now we have hundreds of bugs filed, and we will probably have hundreds more by the end of the week, but many of the bugs are not paper cuts. Some people are confused because, although every paper cut is a usability bug, not all usability bugs are paper cuts; also, although we have committed to fixing one hundred paper cuts, when your bug does not qualify as a paper cut, that does not mean we do not think it’s a great bug that should be fixed. As a reminder, a paper cut is: <ul> <li>Very easy to fix.</li> <li>A bug that, if fixed, makes Ubuntu more usable for a significant percentage of users.</li> <li>A bug that affects a default install of Ubuntu 9.10. A good rule of thumb: if the bug affects an application that is not in the applications menu by default, it is probably not a paper cut. We are looking for “ambient paper cuts,” little glitches a user might encounter many times during the day.</li> </ul> A paper cut is not: <ul> <li>A new feature. If it requires writing more than a few lines of code, or adds any new visual elements to an interface, it’s not a paper cut.</li> </ul> Now that everyone is posting their pet usability bugs as paper cuts, we need to start filtering out the noise to find the hundred paper cuts to fix for Karmic. <a href="https://bugs.edge.launchpad.net/hundredpapercuts/+bugs?search=Search&field.status=New" onclick="javascript:pageTracker._trackPageview('/outbound/article/bugs.edge.launchpad.net');">Here are all of the new paper cuts</a>. Please take a moment to go through one or two of them, and mark them invalid if they fail to meet any of the positive criteria above, or if they meet any of the negative criteria listed. <ul> <li>If you find a bug that only affects a small number of specialized users (<a href="https://bugs.edge.launchpad.net/hundredpapercuts/+bug/306630" onclick="javascript:pageTracker._trackPageview('/outbound/article/bugs.edge.launchpad.net');">like this one</a>), mark the bug invalid in hundredpapercuts with the comment “This is not a paper cut because it is not a general usability issue, but rather a bug affecting a relatively small user population.“</li> <li>If you find a bug that is not trivial to fix (<a href="https://bugs.edge.launchpad.net/hundredpapercuts/+bug/306630" onclick="javascript:pageTracker._trackPageview('/outbound/article/bugs.edge.launchpad.net');">like this one</a>), mark the bug invalid in hundredpapercuts with the comment like “this bug is not trivially fixable, so it is not a paper cut.” If you are not sure whether a bug is trivial to fix or not, just leave it alone.</li> <li>If the bug is a vague rant about someone’s problems with Ubuntu (<a href="https://bugs.edge.launchpad.net/hundredpapercuts/+bug/387473" onclick="javascript:pageTracker._trackPageview('/outbound/article/bugs.edge.launchpad.net');">like this one</a>), patiently ask the poster to identify the particular issue they believe to be a paper cut. If they cannot identify one, kindly mark the bug as invalid in hundredpapercuts.</li> <li>Only take any of these recommended actions if you are very confident that your decision to mark the bug invalid is correct. There is absolutely no harm in leaving the bug for someone else to adjudicate; however, there is harm if you mark a good paper cut invalid by mistake.</li> </ul> When reporting a new paper cut, please make an effort to identify the other projects affected by the bug. If you can go so far as to search upstream bug trackers first, and file paper cuts there, that would be incredibly helpful. Many people are reporting new bugs in hundredpapercuts without bothering to report the bug against the software project that is actually affected. If you can identify the actual project affected (for example, gnome-panel or network-manager), please mark the bug as affecting that project. Finally, let me reiterate–when a bug is marked invalid in hundredpapercuts, that doesn’t imply that it’s not a good bug, that it doesn’t affect user experience, or that it won’t be fixed in Karmic. Thanks! </div> </body> </html>