1 |
I understand that the implication and the time demand of this last |
2 |
point may be a little excessive. If anyone still has the time to fill |
3 |
the skeleton in, they are still welcome to do it. Otherwise with the |
4 |
bug list it will be enough. I would prefer to keep the keyword for |
5 |
Bugday Members to administer. |
6 |
|
7 |
On Mon, Mar 1, 2010 at 11:19 PM, Ben de Groot <yngwin@g.o> wrote: |
8 |
> On 1 March 2010 22:17, Ioannis Aslanidis <aslanidis@×××××.com> wrote: |
9 |
>> [...] |
10 |
> |
11 |
> Great ideas! |
12 |
> |
13 |
>> The teams should send the list of |
14 |
>> bugs, with each bug filling a skeleton similar to the following: |
15 |
>> |
16 |
>> * Ticket number. |
17 |
>> * Title. |
18 |
>> * Clear, easy to understand, short description of what we want to |
19 |
>> delegate to our users. |
20 |
>> * Topic of the task (as in networking, C/C++, python, ebuild, etc.). |
21 |
>> * Difficulty of the task. |
22 |
>> * Detailed step-by-step description of the task. |
23 |
> |
24 |
> This will not work. You need to keep things really simple for our devs. |
25 |
> I don't see anybody but the most dedicated ones, who also happen |
26 |
> to have a lot of time on their hands, fill out such a detailed form. |
27 |
> |
28 |
> I'd say let devs just nominate bugs, either by adding BugDay to |
29 |
> the keywords field or something similar, or by passing the bugday |
30 |
> team a list of bug numbers. Then the bugday team can sort these |
31 |
> and see if any instructions are needed. They could always ask the |
32 |
> involved devs/teams for more info when necessary. |
33 |
> |
34 |
> Cheers, |
35 |
> -- |
36 |
> Ben de Groot |
37 |
> Gentoo Linux developer (qt, media, lxde, desktop-misc) |
38 |
> ______________________________________________________ |
39 |
> |
40 |
> |
41 |
|
42 |
|
43 |
|
44 |
-- |
45 |
Ioannis Aslanidis |
46 |
http://www.deathwing00.org |
47 |
<deathwing00[at]gentoo.org> 0x47F370A0 |