View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#63
A bit late to the party but... we're rehashing ideas now, we should get to an action phase. I have myself suggested over a month ago a similar idea (just called it QAmaster instead of Gatekeeper), and even started knocking on some doors with the idea, to a mixed response. Here's a snipped of a further letter of mine on the topic:

The bottom line is that testing is IMO not working out, de facto becoming a bottleneck - and not only in terms of QA, but procedural difficulties. We have well over 100 packages in testing and there is no tendency of testing getting a better throughput, and there is almost no real solution for libraries. I would wish some council support on it (I would hate people see this as another community member self-initiatedly bossing them around). Of course I don't think *I* have to be that guy (Valerio headed some excellent QA oriented efforts), we might even have a team of QA 'moderators'.
In the end, it's important to have a solid support on this from the powers that be - qamastering (or gatekeeping, doesn't matter how you call it) is not a trivial task, and, as essentially a position of power, has the potential to rub some people the wrong way. If we (as in community) can reach a conclusion to accept such member position(s), the exact workflow, number of people, etc, can be worked out on sprints. If there is no support for a position of such role and authority, all the workflow discussions are not worth much.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 6 Users Say Thank You to attila77 For This Useful Post: