I know I am a bit blonde so just bear with my stupid question but this is it!

Could you give me more of a rundown on what we are doing?? Are we testing pre exiting modules or new ones that are being placed on the site?? And how is it going to be done are they going to be sent to us to test first before being placed into the module repository??

Just need these clarified a bit more as there is nothing stating how this is exactly going to work that I can see or am I just not reading the forums properly sorry if this sounds like a silly question!

kiwiguy

At this time, we're working on specifying the QA process. I.e., we're not doing testing yet, but rather trying to define the testing and certification process itself.

The QA process will apply to both new and existing modules.

Hopefully, the QA team itself will not need to do all the testing itself. Other parties can help out with that; for example, a module developer will (ideally) write the smoketests for his module and submit his test results, using the guidelines provided by the QA team.

As for whether the modules will be sent to us before being placed in the repository, I don't know. Possibly they'll be placed in the repository with a "U" (uncertified) classification, and the classification will be revised after the module has been reviewed.