Should consider to breakdown QA processes into phases...

01= kick start phase: module smoketest
02= invite module(s) to have smoketest, let them join & improve the smoketest
03= review and refinement
04= guidelines & documentations setup:
--- QA scope and standards
--- various template/samples; intallation/readme/user manual/test plan/report form, etc...
--- testing process
--- report and feedback process (ie. communicate before certify it)
--- certification process
05= real certification process start with some well known good quality modules
06= review and refinement
07= advise devloper for self-smoketest on their own module during development
08= certification process go ahead for all other modules
09= kick start for theme
10= kick start for Xoops2.1-2.2, smarty, php5
11= continueous review and refinement

Now, all your turns to add/update/delete above and fillup the ideas/details of each QA phase......

PS: smoketest kick start should be a simple assessment, not too complicate at the beginning