| 1 |
On 1 March 2010 22:17, Ioannis Aslanidis <aslanidis@×××××.com> wrote: |
| 2 |
> [...] |
| 3 |
|
| 4 |
Great ideas! |
| 5 |
|
| 6 |
> The teams should send the list of |
| 7 |
> bugs, with each bug filling a skeleton similar to the following: |
| 8 |
> |
| 9 |
> * Ticket number. |
| 10 |
> * Title. |
| 11 |
> * Clear, easy to understand, short description of what we want to |
| 12 |
> delegate to our users. |
| 13 |
> * Topic of the task (as in networking, C/C++, python, ebuild, etc.). |
| 14 |
> * Difficulty of the task. |
| 15 |
> * Detailed step-by-step description of the task. |
| 16 |
|
| 17 |
This will not work. You need to keep things really simple for our devs. |
| 18 |
I don't see anybody but the most dedicated ones, who also happen |
| 19 |
to have a lot of time on their hands, fill out such a detailed form. |
| 20 |
|
| 21 |
I'd say let devs just nominate bugs, either by adding BugDay to |
| 22 |
the keywords field or something similar, or by passing the bugday |
| 23 |
team a list of bug numbers. Then the bugday team can sort these |
| 24 |
and see if any instructions are needed. They could always ask the |
| 25 |
involved devs/teams for more info when necessary. |
| 26 |
|
| 27 |
Cheers, |
| 28 |
-- |
| 29 |
Ben de Groot |
| 30 |
Gentoo Linux developer (qt, media, lxde, desktop-misc) |
| 31 |
______________________________________________________ |
Archives