Please do not add anything else to this whiteboard. This page will be used solely for the Blueprint Information above. The discussion has been moved to the Ubuntu Wiki https://wiki.ubuntu.com/FutureOfThePapercutsProject

* Discuss the main reasons why contributors have lost interest in the project
    - Limited scope of the definition of a paper cut.
      + Many trivial bugs which are in dire need of being fixed don't fall under the definition of a paper cut.
      + Contributions to Ubuntu can come in many forms (https://wiki.ubuntu.com/ContributeToUbuntu), but the paper cuts project only seems to be dealing with bugs in the code. Expanding the definition to any trivial bug in any "core" Ubuntu asset would broaden the scope in such a way as to bring in many community members who lack the skills and knowledge to write code and fix bugs, but do wish to contribute in some way.. -- Chris Wilson (notgary)
    - Lack of visible progress when patches sit for months either on Launchpad or upstream without any action can be disheartening. -- Chris Wilson (notgary)
      + Find ways of speeding up the approval process for patches -- Chris Wilson (notgary)
    - The paper cuts project could use it's own mailing list, rather than piggy-backing on the Ayatana list where paper cuts mail can easily be drowned out by Unity discussions. -- Chris Wilson (notgary)

Natty: 60-69 bugs
Oneiric: 47

* How can we widen the scope?
  - Bitesize: easy to fix bug,
  - Papercut: easy to fix UI bug that is a part of the default Ubuntu/Kubuntu installation and in an application that is used regularly by end-users.

  Wiki page: https://wiki.ubuntu.com/PaperCut
  Confirmed/Triaged bugs: https://bugs.launchpad.net/hundredpapercuts/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED

* Which scope does the project fit well in?
Bilal's proposal: Drop the papercut definition, and rename the project to "Desktop Bitesize" or something to differentiate it from the Unity Bitesize campaign.

Chris Wilson's (notgary) proposal: Bilal's suggestion is in the right direction, but I think going one step further and renaming it "Ubuntu Bitesize" would be a better idea if my proposal for expanding the paper cuts project to an Ubuntu-wide project (see above) were to be considered

Changes this cycle.
1) Regularly ask on IRC for more contributors

2) Scout around for desktop-bugs which fit the Papercuts definition, file them in the Papercuts project.

3) Consider having a target package of a week, highlighting the papercuts in that package.

4) Expand scope of papercuts to commonly-used Open-source apps.

5) No changes in definition.

6) Also, regularly feature bugs and contributors on OMG! Ubuntu!

7) Encourage contributors to *upstream* all patches.
    - Get all contributors to upstream their patch and link the upstream bug before we accept it downstream.
      + And if there's no upstream bug, then the contributor should file one themselves.

8) Bug Weeks, focus on a single package papercut bugs for a week.
    - All three tasks will happen in this week:
      - File, Triage and Fix.

Work Items:
[bilalakhtar] Ask Daniel to mention Papercuts on harvest.ubuntu.com: TODO
[bilalakhtar] Decide on the papercut milestones for the P cycle: DONE
[YokoZar] Talk to Jorge on a possible merger between the two initiatives: TODO
[YokoZar] Talk to MPT about a separate database with alternate SC app descriptions: TODO