[maemo-community] Community Testing Squad (Sprint task:10.01-02)

[From: Valerio Valerio]

Hi,

along with the improvements in the package interface[1], we'll create a
testing squad, in order kick start the testing process and provide better SW
to the Maemo users.

Here is a initial proposal, suggestions welcome:

* Roles:
 - Tester - Any community member
 - Master/Admin - Selected testing squad members.

There will be some special permissions in the testing interface, these
should be only used in extreme cases after prior note sent to the testing
squad mailing list.

* Master/Admin's special permissions:
 - Can demote packages when there is known blockers. (maintainer obligation)
 - Can promote packages when they are stuck in the testing queue for a while
without any known blocker.

* Testing Squad mailing list:
 - Public mailing list where are discussed any situation/issue/doubts
concerning the applications in the maemo.org repositories.
 - Receives a automatic notification for each packages that enters testing,
is demoted or is promoted.

* Organized testing:
 - In each week one of the testing squad members is responsible for the
elaboration of a small list of apps that should be tested. We'll start with
a 5 a day (or 3 a day) approach in the beginning. Of course the testers are
free to test other apps or do all the testing in just one day. The objective
is have the apps tested by the end of the week.

After gathering some feedback, I'll post instructions how to join the team.

What do you think ?

[1] - [url]
http://wiki.maemo.org/Extras-testing/QA_Checklist/QA_Improvements[/url]

Posted also at TMO: http://talk.maemo.org/showthread.php?p=492276#post492276

Best regards,

-- 
Valério Valério
Maemo Community Council Chair

http://www.valeriovalerio.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.maemo.org/pipermail/maemo-community/attachments/20100124/83350cb8/attachment.htm>