2. Channeling resources to fixing those bugs.
3. Measuring and celebrating progress towards fixing those bugs.
4. Tracking impact of the fixes in upstreams over successive versions.
Important! 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
- 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)
If you liked this article, subscribe to the feed by clicking the image below to keep informed about new contents of the blog:
0 comments:
Post a Comment