Few notes on filing "papercut" bugs

Mat Tomaszewski mat.tomaszewski at canonical.com
Fri Jun 12 11:07:07 UTC 2009


During the recent UDS we launched a "100 Paper Cuts" project 
(https://edge.launchpad.net/hundredpapercuts), aiming to target and fix 
small but significant design and usability bugs in Ubuntu. We set an 
arbitrary target of 100 to be fixed for Karmic release.

The response so far has been overwhelming and we are already finding it 
difficult to filter out bugs that indeed are "papercuts" from the ones 
that aren't. On that note, I think we need a clearer definition of which 
bugs do qualify as papercuts.

Please do file as papercuts:

- bugs that are system-wide (Nautilus, Gnome panel, etc), rather than 
app-specific (F-Spot, OOo, Terminal, etc.)
- bugs that impact standard workflows (like connecting to the network, 
copying files, browsing folders, etc.), rather than specialised or 
corner case workflows (e.g. dragging an image in evince)
- bugs that are easy to address, rather that ones that require 
significant design or development efforts
- issues with existing features, rather than requests for new features
- bugs that relate to usability and design (like size of the 
notification bubbles), rather than broken software (e.g. notifications 
flickering in fullscreen)

Please pass this message on to anyone who may be interested in making 
Ubuntu better.

Many thanks!


More information about the Ubuntu-devel-discuss mailing list