| 1 |
Alec Joseph Warner wrote: |
| 2 |
> So all 3 of the people subscribed to this list have probably heard this |
| 3 |
> already, but I re-iterate here for those who don't spend their lives |
| 4 |
> staring at IRC backlogs. |
| 5 |
> |
| 6 |
> The current QA team is definately short on overall goals. We have a lot |
| 7 |
> of people that are passionate about QA, and they all do their own thing |
| 8 |
> to contribute. However I think we can do better. |
| 9 |
|
| 10 |
All the points you raise are valid, and have all been discussed before. |
| 11 |
I can remember most of these issues going back to '01/'02. The reason |
| 12 |
they aren't solved yet isn't because it's mentally difficult, or because |
| 13 |
the ideas are stupid. It's because (1) it's a lot of work to put |
| 14 |
everything together, (2) focus has been spent on dictating policies and |
| 15 |
arguing on the lists instead of producing code, (3) nobody has cared |
| 16 |
enough about the problem to actually write tools that developers can accept. |
| 17 |
|
| 18 |
Don't let my comment be a discouragement. It is not. I'm just saying |
| 19 |
that the best way out of this predicament is to just write the tools. |
| 20 |
Writing policies is useful for documentation, but useless for checking. |
| 21 |
Whoever picks up this project should carefully stay of of the limelight |
| 22 |
to avoid the usual flamefests. Historically, that's how the QA people |
| 23 |
got burnt out before, trying to force through policies, and never got |
| 24 |
around to the kick-ass tools we wanted. |
| 25 |
|
| 26 |
|
| 27 |
Cheers, |
| 28 |
|
| 29 |
-- Karl T |
| 30 |
-- |
| 31 |
gentoo-qa@g.o mailing list |
Archives