One Hundred Papercuts
Differences between revisions 1 and 70 (spanning 69 versions)
|
Size: 3682
Comment:
|
Size: 3269
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Karmic Cycle == | #language en #title The One Hundred Paper Cuts Project |
| Line 3: | Line 4: |
| For Ubuntu 9.10 “Karmic Koala,” the Canonical User Experience and Design team, together with community members participating in the Ayatana project, attempted to identify and fix one hundred “paper cuts.” Briefly put, a paper cut was defined as a trivially fixable usability bug that the average user would encounter on his/her first day of using a default installation of Ubuntu Desktop Edition. | <<Include(OneHundredPaperCuts/Header)>> |
| Line 5: | Line 6: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| | |
| Line 6: | Line 8: |
| The One Hundred Paper Cuts project was announced at UDS Karmic in Barcelona and proceeded in the following five phases: | The One Hundred Paper Cuts project exists to work on the little annoyances in Ubuntu. These bugs are normally considered too low priority for the developers of the apps in question, who already have more than enough to work on, and so the One Hundred Paper Cuts project comes along and picks them up. In each release cycle, the project aims to fix 100 of these little bugs and in doing so, give Ubuntu a layer of polish that is not typically found in other Linux distros. |
| Line 8: | Line 10: |
| = Our mission = | |
| Line 9: | Line 12: |
| 1. The preliminary definition of a paper cut was blogged about and posted on the Ubuntu wiki (http://wiki.ubuntu.com/PaperCut), and the community was invited to report paper cuts and to identify existing bugs as paper cuts in Launchpad. Project details were publicized on Ubuntu members' personal blogs, aggregated on Ubuntu Planet and Planet GNOME, and announced on the Ayatana and Ubuntu-devel mailing lists. 1. Within a few weeks, over 1,600 bugs were added to the “papercuts” project in Launchpad. A new team named “papercutters” was formed to triage incoming bugs and generate a set of confirmed bugs which had been checked against the definition of a paper cut. The papercutters team initially consisted of the Canonical User Experience and Design team, but five members of the community were eventually added to the team after demonstrating a strong understanding of the project through bug triage work. 1. Ten weekly milestones, beginning the final week of June and ending the final week of August, were scheduled, with ten paper cuts allocated to each milestone to establish the preliminary set of one hundred paper cuts to fix in the Ubuntu 9.10 release. This series of milestones was intended as a schedule for the Canonical Design team to observe when collaborating with Ubuntu developers and the community, allowing the Design team to focus on a small set of paper cuts each week; these milestones were never intended to be deadlines for fixing bugs. Celeste Lyn Paul was added to the papercutters team to assist in allocating an additional Kubuntu paper cut to each milestone so that the Kubuntu project could also benefit from the paper cuts effort. 1. Each week, a new milestone and therefore a fresh set of ten paper cuts would become the focus of attention. The Canonical Design team would sometimes provide design direction when it was needed in the form of mockups or simple behavioral specifications as comments on bugs, but most effort was spent finding individuals capable and willing to work on implementing fixes, as paper cuts by definition require very little specialized design work. As closer attention was paid to paper cuts within each successive milestone, often a paper cut would become contentious, or it would become apparent that a paper cut was not easy to fix, so the offending paper cut would be marked Invalid and replaced within its milestones with another unallocated, Confirmed paper cut. At the end of each week, a progress report was published that discussed the paper cuts examined that week and celebrated the progress of any paper cuts that had been fixed. |
= Frequently asked questions = * [[http://askubuntu.com/questions/1006/what-is-papercut | What is a paper cut?]] * [[http://askubuntu.com/questions/231178/how-do-i-report-a-paper-cut | How do I report a paper cut?]] * [[http://askubuntu.com/questions/231230/how-do-i-get-the-design-team-to-approve-a-design-proposal-for-fixing-a-paper-cut/231231#231231 | How do I get design input on a paper cut?]] * [[http://askubuntu.com/questions/83629/where-can-i-find-the-latest-paper-cuts | Where can I find the latest Paper Cuts?]] * [[http://askubuntu.com/questions/234982/what-is-the-policy-on-the-backporting-of-paper-cuts-fixes | What is the policy on backporting paper cut fixes?]]. * [[http://askubuntu.com/questions/231243/what-are-the-different-ways-i-can-contribute-to-the-one-hundred-paper-cuts-proje | How can I contribute to the One Hundred Paper Cuts project?]] |
| Line 14: | Line 20: |
| = Paper Cut Cycles = * [[https://wiki.ubuntu.com/OneHundredPaperCuts/Raring | Raring]] |
|
| Line 15: | Line 23: |
| = Meetings = All the details of our meetings, including the agenda and minutes, can be found [[https://wiki.ubuntu.com/OneHundredPaperCuts/Meetings|here]], though quite why you would ever want to go there boggles the mind mince it's all incredibly boring stuff. |
|
| Line 16: | Line 26: |
| == For Lucid == | = Events = There are many important events in the paper cut calendar, both participation in Ubuntu events and running our own little get-togethers. A full list of paper cut events can be found [[OneHundredPaperCuts/Events | here]]. |
| Line 18: | Line 29: |
| 1. Paper cut gets a patch attached. 2. UX checks off on experience. 3. Subscribe “ubuntu-main-sponsors” and assign to "canonical-desktop-team" 4. Desktop team helps submitter work with upstream and simultaneously apply patch to Ubuntu. |
''When you are an active contributor to papercut triaging, you can be asked or ask to join the '''[[https://launchpad.net/~papercutters|Papercutters]]''''' team. |
| Line 23: | Line 31: |
| ''If you are looking for more information about bug triaging, a good source of information is: [[HelpingWithBugs|Helping with bugs]].'' | |
| Line 24: | Line 33: |
| Psychological effect of marking paper cuts invalid. Paper cut escalation: How we discourage hundreds of comments. Share Paper Cut filter (imapfilter). |
= Contact and help = If you want to ask a question or need help, please feel free to contact us via the following communication channels: * '''IRC''': The [[irc://irc.freenode.net/ubuntu-desktop | #ubuntu-desktop]] channel on Freenode. ([[https://help.ubuntu.com/community/InternetRelayChat|How to connect via IRC]].) * '''Mailing List''': Join the [[https://launchpad.net/~papercuts-ninja|Paper Cuts Ninja]] team and send a message to papercuts-ninja@lists.launchpad.net. You can do this without joining the team, but messages from non members are held for moderation, so it'll be faster for you to join. |
| Line 29: | Line 38: |
| Phase 1: Discovery Phase 2: UX assignment Phase 3: |
= Site map = A complete index of the paper cuts wiki can be found [[https://wiki.ubuntu.com/OneHundredPaperCuts/SiteMap | here]]. |
The One Hundred Paper Cuts project exists to work on the little annoyances in Ubuntu. These bugs are normally considered too low priority for the developers of the apps in question, who already have more than enough to work on, and so the One Hundred Paper Cuts project comes along and picks them up. In each release cycle, the project aims to fix 100 of these little bugs and in doing so, give Ubuntu a layer of polish that is not typically found in other Linux distros.
Our mission
Frequently asked questions
Paper Cut Cycles
Meetings
All the details of our meetings, including the agenda and minutes, can be found here, though quite why you would ever want to go there boggles the mind mince it's all incredibly boring stuff.
Events
There are many important events in the paper cut calendar, both participation in Ubuntu events and running our own little get-togethers. A full list of paper cut events can be found here.
When you are an active contributor to papercut triaging, you can be asked or ask to join the Papercutters team.
If you are looking for more information about bug triaging, a good source of information is: Helping with bugs.
Contact and help
If you want to ask a question or need help, please feel free to contact us via the following communication channels:
IRC: The #ubuntu-desktop channel on Freenode. (How to connect via IRC.)
Mailing List: Join the Paper Cuts Ninja team and send a message to papercuts-ninja@lists.launchpad.net. You can do this without joining the team, but messages from non members are held for moderation, so it'll be faster for you to join.
Site map
A complete index of the paper cuts wiki can be found here.
One Hundred Papercuts (last edited 2017-06-04 03:18:26 by es20490446e)