I understand that the implication and the time demand of this last point may be a little excessive. If anyone still has the time to fill the skeleton in, they are still welcome to do it. Otherwise with the bug list it will be enough. I would prefer to keep the keyword for Bugday Members to administer.
On Mon, Mar 1, 2010 at 11:19 PM, Ben de Groot <[email protected]> wrote: > On 1 March 2010 22:17, Ioannis Aslanidis <[email protected]> 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) > ______________________________________________________ > > -- Ioannis Aslanidis http://www.deathwing00.org <deathwing00[at]gentoo.org> 0x47F370A0
