| 1 |
On 01/03/2010 22:19, Ben de Groot wrote: |
| 2 |
> On 1 March 2010 22:17, Ioannis Aslanidis<aslanidis@×××××.com> wrote: |
| 3 |
>> [...] |
| 4 |
> |
| 5 |
> Great ideas! |
| 6 |
> |
| 7 |
>> The teams should send the list of |
| 8 |
>> bugs, with each bug filling a skeleton similar to the following: |
| 9 |
>> |
| 10 |
>> * Ticket number. |
| 11 |
>> * Title. |
| 12 |
>> * Clear, easy to understand, short description of what we want to |
| 13 |
>> delegate to our users. |
| 14 |
>> * Topic of the task (as in networking, C/C++, python, ebuild, etc.). |
| 15 |
>> * Difficulty of the task. |
| 16 |
>> * Detailed step-by-step description of the task. |
| 17 |
> |
| 18 |
> This will not work. You need to keep things really simple for our devs. |
| 19 |
> I don't see anybody but the most dedicated ones, who also happen |
| 20 |
> to have a lot of time on their hands, fill out such a detailed form. |
| 21 |
> |
| 22 |
> I'd say let devs just nominate bugs, either by adding BugDay to |
| 23 |
> the keywords field or something similar, or by passing the bugday |
| 24 |
> team a list of bug numbers. Then the bugday team can sort these |
| 25 |
> and see if any instructions are needed. They could always ask the |
| 26 |
> involved devs/teams for more info when necessary. |
| 27 |
> |
| 28 |
> Cheers, |
| 29 |
|
| 30 |
You don't need to make it compulsory to fill out those fields and if |
| 31 |
just 1 out of every 10 or 20 bugs gets that filled then it is still a |
| 32 |
big leap forward. |
| 33 |
|
| 34 |
Or... Ask for a dev whose whole job is to fill out those forms. I'm sure |
| 35 |
there are plenty of non-coders out there who would be willing to do it, |
| 36 |
even a team! |
Archives