1790
Comment: add me
|
1828
|
Deletions are marked like this. | Additions are marked like this. |
Line 41: | Line 41: |
1. [:DavidMorenoGarza:David Moreno] |
Rationale
Around 100 RC bugs is 100 RC bugs that should go away NOW.
So the idea is:
100 developers × 5 days = 100 RC bugs fixed
[http://bts.turmzimmer.net/details.php?bydist=both&sortby=packages&ignmerged=on&new=7&refresh=1800 Detailed list of bugs]
Rules
- Write your name in the list before the game start.
When the game starts, you are assigned a RC bug. Assignment is made using a very complicated method used by the Chinese secret services called the [http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Pastiches/Pifom%C3%A8tre pifomètre].
- You have 5 days to close the RC bug. Possible outcomes are:
- You upload a NMU that fixes the bug to unstable.
- You send a patch to the bug and the maintainer does an upload.
- You convince, with a mail that details the rationale, a release manager to tag the bug lenny-ignore.
- You convince, in a similar way, a release manager to remove the package from lenny.
- You downgrade, with appropriate rationale, the bug to a non-RC severity.
- If, during this timeline, you manage to fix a RC bug that is more than 3 months old by providing a patch, you will be called a WINNER.
The 5 first WINNERs will be sent a box of home-made cookies by ?JossMouette. (Other proposals to motivate people to become WINNERs are welcome.)
If you don’t manage to close the RC bug in 5 days, you have to bake cookies and send them to someone who has managed to close one or to a release manager.
Expected timeline
- Game starts: 25 Oct
- Game ends: 30 Oct
Register here
?JossMouette
[:DavidMorenoGarza:David Moreno]