Re: [gentoo-dev] Marking bugs for bugday?

[George Prowse <george.prowse@gmail.com>]

On 01/03/2010 22:19, Ben de Groot wrote:
> On 1 March 2010 22:17, Ioannis Aslanidis<aslanidis@gmail.com>  wrote:
>> [...]
>
> Great ideas!
>
>> The teams should send the list of
>> bugs, with each bug filling a skeleton similar to the following:
>>
>>   * Ticket number.
>>   * Title.
>>   * Clear, easy to understand, short description of what we want to
>> delegate to our users.
>>   * Topic of the task (as in networking, C/C++, python, ebuild, etc.).
>>   * Difficulty of the task.
>>   * Detailed step-by-step description of the task.
>
> This will not work. You need to keep things really simple for our devs.
> I don't see anybody but the most dedicated ones, who also happen
> to have a lot of time on their hands, fill out such a detailed form.
>
> I'd say let devs just nominate bugs, either by adding BugDay to
> the keywords field or something similar, or by passing the bugday
> team a list of bug numbers. Then the bugday team can sort these
> and see if any instructions are needed. They could always ask the
> involved devs/teams for more info when necessary.
>
> Cheers,

You don't need to make it compulsory to fill out those fields and if 
just 1 out of every 10 or 20 bugs gets that filled then it is still a 
big leap forward.

Or... Ask for a dev whose whole job is to fill out those forms. I'm sure 
there are plenty of non-coders out there who would be willing to do it, 
even a team!