Ideally, a paid position, if nothing else, because of the seriousness of the task - that way things would not get delayed because someone had no time due to job/school/etc, and people stuck in testing would know they have a person to turn to who is supposed to help them (the idea of testing is not to have a hundred people individually go and hunt around about their showstoppers - if we know what the problem is, we should have a fix in place in hours if we can, not weeks !). But, even if there are no funds or possibilities for such an option, we could think about things like rotating QAmastership (say, monthly or biweekly, from the pool of testing admins/moderators) to avoid burning out and making some breathing space for volunteers. Effectively, of course, what I called QAmaster, you could say is a part of testing squad administratorship, my point being that such activity (helping developers through testing) should be considered part of the QA procedure itself (the paid position helping to secure dedicated time for this). Seriously, if one person can just double the throughput of testing by helping the developers not just to identify problems but solve their issues, it would mean a lot more applications in Extras, motivated developers, no 'calculative promotions', summa summarum, an investment IMHO well worth the money.