Comments on: Calling All Paper Cutters http://davidsiegel.org/calling-all-paper-cutters/ David Siegel Thu, 04 Mar 2010 01:16:34 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Ubuntu’s 100 Paper Cuts | DivineOmega http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1361 Ubuntu’s 100 Paper Cuts | DivineOmega Sun, 05 Jul 2009 14:01:24 +0000 http://blog.davebsd.com/?p=333#comment-1361 [...] is plenty more information regarding 100 Paper Cuts, its initial progress and integration/planning for Kubuntu. Please comment and tell me, what do you think of the [...] [...] is plenty more information regarding 100 Paper Cuts, its initial progress and integration/planning for Kubuntu. Please comment and tell me, what do you think of the [...]

]]> By: Scaine http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1363 Scaine Fri, 26 Jun 2009 16:13:11 +0000 http://blog.davebsd.com/?p=333#comment-1363 I still think we're a little wooly on what makes a papercut a papercut, and I'm still bitter that the old copy/paste issue didn't make it into the hundred :-), but I'm pretty excited about this project. If even half of these issues are resolved, it's going to be not just a better Ubuntu, but a better Gnome, since so many of these issues are upstream. Nautilus features very heavily, but even metacity bugs are making the grade. Great stuff. I still think we’re a little wooly on what makes a papercut a papercut, and I’m still bitter that the old copy/paste issue didn’t make it into the hundred Smile, but I’m pretty excited about this project. If even half of these issues are resolved, it’s going to be not just a better Ubuntu, but a better Gnome, since so many of these issues are upstream. Nautilus features very heavily, but even metacity bugs are making the grade. Great stuff.

]]> By: obso1337.org » 100 papercuts and Kubuntu http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1360 obso1337.org » 100 papercuts and Kubuntu Sat, 20 Jun 2009 03:05:53 +0000 http://blog.davebsd.com/?p=333#comment-1360 [...] of you may have heard about Canonical’s new 100 papercuts project (more info). The goal is to fix 100 minor usability bugs for the Karmic release. Although the primary focus is [...] [...] of you may have heard about Canonical’s new 100 papercuts project (more info). The goal is to fix 100 minor usability bugs for the Karmic release. Although the primary focus is [...]

]]> By: Zip, archive, package or compress? Help! http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1359 Zip, archive, package or compress? Help! Thu, 18 Jun 2009 21:53:14 +0000 http://blog.davebsd.com/?p=333#comment-1359 [...] As part of the 100 paper cuts project that we are running for the next Ubuntu release we are focussing on small usability problems that, if fixed, will make the Ubuntu desktop experience feel smoother, safer, better. [...] [...] As part of the 100 paper cuts project that we are running for the next Ubuntu release we are focussing on small usability problems that, if fixed, will make the Ubuntu desktop experience feel smoother, safer, better. [...]

]]> By: David http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1353 David Wed, 17 Jun 2009 03:25:35 +0000 http://blog.davebsd.com/?p=333#comment-1353 Celeste, I am not suggesting that users would know whether a fix involves writing 1 or 1,000 lines of code. In fact, I believe most users won't even know a paper cut is there when they experience one. What I meant to say, is that if someone participating in this project is able to determine with a good deal of certainty that a fix would require writing new code, then they should mark the bug as not being a paper cut. I did not say that users would know this, I even express doubt that project participants would be able to make this determination: "if you are not sure whether a bug is trivial to fix or not, just leave it alone." I also realize that the addition of "minor UI element" could improve usability greatly, but that is not the kind of usability improvement we are calling a "paper cut." It has been really tempting for people to report any and all usability bugs, but our goal is to solve 100 extremely subtle, "ambient" usability issues. The more subtle the bug, the better -- the perfect paper cut is something users never notice, but if fixed would improve usability in an ineffable manner. The addition of even a minor UI element is not a paper cut in this sense. I hope that made sense... I am exhausted from sifting through bugs all day :) Celeste,

I am not suggesting that users would know whether a fix involves writing 1 or 1,000 lines of code. In fact, I believe most users won’t even know a paper cut is there when they experience one. What I meant to say, is that if someone participating in this project is able to determine with a good deal of certainty that a fix would require writing new code, then they should mark the bug as not being a paper cut. I did not say that users would know this, I even express doubt that project participants would be able to make this determination: “if you are not sure whether a bug is trivial to fix or not, just leave it alone.”

I also realize that the addition of “minor UI element” could improve usability greatly, but that is not the kind of usability improvement we are calling a “paper cut.” It has been really tempting for people to report any and all usability bugs, but our goal is to solve 100 extremely subtle, “ambient” usability issues. The more subtle the bug, the better — the perfect paper cut is something users never notice, but if fixed would improve usability in an ineffable manner. The addition of even a minor UI element is not a paper cut in this sense.

I hope that made sense… I am exhausted from sifting through bugs all day Smile

]]> By: Celeste Lyn Paul http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1358 Celeste Lyn Paul Wed, 17 Jun 2009 00:26:34 +0000 http://blog.davebsd.com/?p=333#comment-1358 "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 probably not a paper cut." How are users supposed to know if a minor fix will take more than a few lines of code? And often the addition of a minor UI element might only be a few lines of code and provide a huge improvement (such as a button, icon, or UI effect). Can you clarify this a little more? Or will you just make exceptions for the ones you can discern as easy to fix? “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 probably not a paper cut.”

How are users supposed to know if a minor fix will take more than a few lines of code? And often the addition of a minor UI element might only be a few lines of code and provide a huge improvement (such as a button, icon, or UI effect).

Can you clarify this a little more? Or will you just make exceptions for the ones you can discern as easy to fix?

]]> By: Burbank LUG » Ouch! – Ubuntu gave me a papercut? http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1357 Burbank LUG » Ouch! – Ubuntu gave me a papercut? Tue, 16 Jun 2009 17:37:18 +0000 http://blog.davebsd.com/?p=333#comment-1357 [...] Further reading: Jorge’s Stompbox: Papercut Time Launchpad: One Hundred Paper Cuts project page David Siegle: One Hundred Paper Cuts David Siegle: Calling All Paper Cutters [...] [...] Further reading: Jorge’s Stompbox: Papercut Time Launchpad: One Hundred Paper Cuts project page David Siegle: One Hundred Paper Cuts David Siegle: Calling All Paper Cutters [...]

]]> By: Dave http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1355 Dave Tue, 16 Jun 2009 15:17:11 +0000 http://blog.davebsd.com/?p=333#comment-1355 Mike, I've addressed your comment at the bottom of the post -- thanks! Mike, I’ve addressed your comment at the bottom of the post — thanks!

]]> By: Mike Rooney http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1356 Mike Rooney Tue, 16 Jun 2009 01:35:45 +0000 http://blog.davebsd.com/?p=333#comment-1356 Good summary! For people helping out with triaging, do you want us to do anything with bugs that we can confirm ARE paper cuts, and if so should those be set as Confirmed or Triaged? Perhaps Triaged could be more useful as that means it wasn't set by a random person. Good summary! For people helping out with triaging, do you want us to do anything with bugs that we can confirm ARE paper cuts, and if so should those be set as Confirmed or Triaged? Perhaps Triaged could be more useful as that means it wasn’t set by a random person.

]]> By: Matt http://davidsiegel.org/calling-all-paper-cutters/comment-page-1/#comment-1354 Matt Tue, 16 Jun 2009 01:20:31 +0000 http://blog.davebsd.com/?p=333#comment-1354 This is why I love open source: the community working together. Thanks to you and everyone for this awesome work. This is why I love open source: the community working together. Thanks to you and everyone for this awesome work.

]]>