On 1 March 2010 22:17, Ioannis Aslanidis <aslani...@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, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) ______________________________________________________
