Simon,
"if you can use a mouse and a web browser then you can test a package"
This statement seems to contradict these statements:
"I want people who will sit down with a package, install it.. "
"Each volunteer will need to ..Produce a test plan/checklist. This will be a simple list of test performed, that can be re-used each release."
Volunteers also need to know:
1. where to find available packages
2. how to prepare a package for install (what needs to be decided operationally before reaching this point)
3. documentation on how to install the package --including understanding the jargon and concepts presented in the package documentation
4. other underlying assumptions about how packages fit into the system.
These implicit assumptions may be clear to developers, but without clear documentation, I don't see how "anyone" who can use a mouse and browser can volunteer for testing.
