madjr
November 21st, 2010, 06:02 PM
So if this situation continues it seems that 11.04 will not be as polished as the whole world is looking forward to and instead feel very unfinished and buggy for everyone.
The cry for help was just made by the papercuts team this week, because of a recent lack of members, contributors and testers for natty.
from the canonical blog:
http://design.canonical.com/2010/11/paper-cuts-need-you/
You won’t be surprised to hear that I am on the Papercutters team and, in that capacity, was on the receiving end of an email from Vish who points out a couple of things:
1) Only a handful of members in the Papercutters team are active on the project.
2) For a project to live we need as many people as possible contributing on a fairly regular basis.
If you are new to the area (well, this corner of cyberspace at least) you may not know about the Paper Cuts project. It is an initiative to identify and fix small bugs that impact on the user experience of Ubuntu and the applications that run on Ubuntu.
The Paper Cuts projects needs active participation from as many people as possible, there are many ways to get involved and there is something for you to do whether it is creating an icon, writing a patch, passing the patch through to an upstream, changing the description of an application for the Software Centre, triaging and identifying the Paper Cut bugs or simply cheering everyone along!
If you used to be active but aren’t any more Vish has some questions for you too:
1) Are you having any difficulties working on the project recently , have there been any changes in the process which have made it harder to contribute?
2) Are you finding any part of the process difficult or are you having trouble getting started or understanding the process?
He also has the following request:
We will be starting the Natty papercut cycle soon, do let me or any of the other active members know about the difficulties and if there are any changes to be made to the project which would make it easier for you to contribute to the project?
As a member of the team do take some time every often or so to take a look at the project and to review atleast one bug or item. Each bug every member handles will reduce the workload for everyone in the team.
This is a community project and if the project is to sustain for a long time we need you to pitch in.
The impact of the Paper Cuts projects has grown with every cycle. To date there have been 295 Paper Cuts fixed (https://bugs.launchpad.net/hundredpapercuts/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status:list=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_bra). From descriptions of apps in the Software Centre to the wrong album art appearing in a Rythmbox notification and eog not asking to save changes there have been lots of small fixes that smooth the way for the users of Ubuntu and a host of applications.
This wiki page tells you what you need to do to get involved.
https://wiki.ubuntu.com/PaperCut
Please get involved, get active and let’s help Vish, Sense and all the Papercutters make this a Paper Cuts cycle to remember!
More.. (http://design.canonical.com/2010/11/paper-cuts-need-you/)
Instructions from:
https://wiki.ubuntu.com/PaperCut
CONTRIBUTING
The One Hundred Paper Cuts Project is a great way to get involved in the Ubuntu community. Several members have found paper cuts a stepping stone to get further involved with the Ubuntu community. There are several ways you can contribute:
If you are a hacker or programmer, have a look at the paper cuts that are assigned to a milestone (https://launchpad.net/hundredpapercuts/+series), or that have the 'Triaged (https://bugs.launchpad.net/hundredpapercuts/+bugs?search=Search&field.status=Triaged)' status;
* Not a hacker? No problem, you can help us still:
-Test your favorite default or featured applications and see if you can find any paper cuts that need fixing. If you find any, report them;
-Test proposed solutions for paper cuts;
-Help triaging the paper cuts.
Fixing a paper cut
You can find paper cuts ready to work on by looking at the milestones (https://launchpad.net/hundredpapercuts/+series), or going through bug reports that have the 'Triaged (https://bugs.launchpad.net/hundredpapercuts/+bugs?search=Search&field.status=Triaged)' status.
* Assign yourself to the bug of the paper cut you selected and set its status to 'In Progress';
* Work on a solution and commit it in a branch to Launchpad, or generate a patch;
* Attach the branch or patch to the bug report;
* You can choose to either make sure your solution gets added to Ubuntu and forwarded upstream yourself, or you can wait for the Papercutters to help you with that. Be prepared to process feedback about your solution.
Members who have helped fix papercuts are listed in thePapercuts Hall Of Fame.
For more information about how to fix bugs, also see: Helping with bug fixing (https://wiki.ubuntu.com/Bugs/HowToFix).
How to report a paper cut
If you found something you believe to be a valid paper cut, how do you report the issue?
* Make sure that the issue you're about to report isn't already reported at Launchpad (https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%2520duplicate);
* Make sure the bug is a valid paper cut;
* If the paper cut was already reported in Ubuntu, but not in the One Hundred Paper Cuts project, press the "Also affects Project" link to add the paper cut to the project;
* If the paper cut was not reported yet:
1. File the bug in the affected package in the Ubuntu project on Launchpad. When reporting the bug, use Apport, either via the application's "Help -> Report a Problem" menu item, or by using the command 'ubuntu-bug' and pass the name of the affected package as an argument.
2. Now add the One Hundred Paper Cuts project to the bug report using the "Also affects Project" link.
More information about reporting bugs in general can be found at ReportingBugs (https://wiki.ubuntu.com/ReportingBugs).
Triaging paper cuts
People who would like to help with managing the flow of incoming paper cuts can contribute by triaging the bug reports on the One Hundred Paper Cuts project (https://launchpad.net/hundredpapercuts) at Launchpad.
* Verify the bug is a valid paper cut;
- If not, then mark the One Hundred Paper Cuts project task as Invalid and leave a message to explain your actions to the reporter;
* Verify the paper cut can be reproduced in the development release of Ubuntu;
- If not, then mark the One Hundred Paper Cuts project task as Invalid and leave a message to explain your actions to the reporter;
*Verify the paper cut report contains all necessary information;
- If not, ask the reporter to provide the information that is lacking;
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 #ayatana channel on Freenode. (How to connect via IRC (https://help.ubuntu.com/community/InternetRelayChat).)
*Mailing List: The Ayatana Mailing list (https://launchpad.net/~ayatana).
The cry for help was just made by the papercuts team this week, because of a recent lack of members, contributors and testers for natty.
from the canonical blog:
http://design.canonical.com/2010/11/paper-cuts-need-you/
You won’t be surprised to hear that I am on the Papercutters team and, in that capacity, was on the receiving end of an email from Vish who points out a couple of things:
1) Only a handful of members in the Papercutters team are active on the project.
2) For a project to live we need as many people as possible contributing on a fairly regular basis.
If you are new to the area (well, this corner of cyberspace at least) you may not know about the Paper Cuts project. It is an initiative to identify and fix small bugs that impact on the user experience of Ubuntu and the applications that run on Ubuntu.
The Paper Cuts projects needs active participation from as many people as possible, there are many ways to get involved and there is something for you to do whether it is creating an icon, writing a patch, passing the patch through to an upstream, changing the description of an application for the Software Centre, triaging and identifying the Paper Cut bugs or simply cheering everyone along!
If you used to be active but aren’t any more Vish has some questions for you too:
1) Are you having any difficulties working on the project recently , have there been any changes in the process which have made it harder to contribute?
2) Are you finding any part of the process difficult or are you having trouble getting started or understanding the process?
He also has the following request:
We will be starting the Natty papercut cycle soon, do let me or any of the other active members know about the difficulties and if there are any changes to be made to the project which would make it easier for you to contribute to the project?
As a member of the team do take some time every often or so to take a look at the project and to review atleast one bug or item. Each bug every member handles will reduce the workload for everyone in the team.
This is a community project and if the project is to sustain for a long time we need you to pitch in.
The impact of the Paper Cuts projects has grown with every cycle. To date there have been 295 Paper Cuts fixed (https://bugs.launchpad.net/hundredpapercuts/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status:list=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_bra). From descriptions of apps in the Software Centre to the wrong album art appearing in a Rythmbox notification and eog not asking to save changes there have been lots of small fixes that smooth the way for the users of Ubuntu and a host of applications.
This wiki page tells you what you need to do to get involved.
https://wiki.ubuntu.com/PaperCut
Please get involved, get active and let’s help Vish, Sense and all the Papercutters make this a Paper Cuts cycle to remember!
More.. (http://design.canonical.com/2010/11/paper-cuts-need-you/)
Instructions from:
https://wiki.ubuntu.com/PaperCut
CONTRIBUTING
The One Hundred Paper Cuts Project is a great way to get involved in the Ubuntu community. Several members have found paper cuts a stepping stone to get further involved with the Ubuntu community. There are several ways you can contribute:
If you are a hacker or programmer, have a look at the paper cuts that are assigned to a milestone (https://launchpad.net/hundredpapercuts/+series), or that have the 'Triaged (https://bugs.launchpad.net/hundredpapercuts/+bugs?search=Search&field.status=Triaged)' status;
* Not a hacker? No problem, you can help us still:
-Test your favorite default or featured applications and see if you can find any paper cuts that need fixing. If you find any, report them;
-Test proposed solutions for paper cuts;
-Help triaging the paper cuts.
Fixing a paper cut
You can find paper cuts ready to work on by looking at the milestones (https://launchpad.net/hundredpapercuts/+series), or going through bug reports that have the 'Triaged (https://bugs.launchpad.net/hundredpapercuts/+bugs?search=Search&field.status=Triaged)' status.
* Assign yourself to the bug of the paper cut you selected and set its status to 'In Progress';
* Work on a solution and commit it in a branch to Launchpad, or generate a patch;
* Attach the branch or patch to the bug report;
* You can choose to either make sure your solution gets added to Ubuntu and forwarded upstream yourself, or you can wait for the Papercutters to help you with that. Be prepared to process feedback about your solution.
Members who have helped fix papercuts are listed in thePapercuts Hall Of Fame.
For more information about how to fix bugs, also see: Helping with bug fixing (https://wiki.ubuntu.com/Bugs/HowToFix).
How to report a paper cut
If you found something you believe to be a valid paper cut, how do you report the issue?
* Make sure that the issue you're about to report isn't already reported at Launchpad (https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%2520duplicate);
* Make sure the bug is a valid paper cut;
* If the paper cut was already reported in Ubuntu, but not in the One Hundred Paper Cuts project, press the "Also affects Project" link to add the paper cut to the project;
* If the paper cut was not reported yet:
1. File the bug in the affected package in the Ubuntu project on Launchpad. When reporting the bug, use Apport, either via the application's "Help -> Report a Problem" menu item, or by using the command 'ubuntu-bug' and pass the name of the affected package as an argument.
2. Now add the One Hundred Paper Cuts project to the bug report using the "Also affects Project" link.
More information about reporting bugs in general can be found at ReportingBugs (https://wiki.ubuntu.com/ReportingBugs).
Triaging paper cuts
People who would like to help with managing the flow of incoming paper cuts can contribute by triaging the bug reports on the One Hundred Paper Cuts project (https://launchpad.net/hundredpapercuts) at Launchpad.
* Verify the bug is a valid paper cut;
- If not, then mark the One Hundred Paper Cuts project task as Invalid and leave a message to explain your actions to the reporter;
* Verify the paper cut can be reproduced in the development release of Ubuntu;
- If not, then mark the One Hundred Paper Cuts project task as Invalid and leave a message to explain your actions to the reporter;
*Verify the paper cut report contains all necessary information;
- If not, ask the reporter to provide the information that is lacking;
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 #ayatana channel on Freenode. (How to connect via IRC (https://help.ubuntu.com/community/InternetRelayChat).)
*Mailing List: The Ayatana Mailing list (https://launchpad.net/~ayatana).