[Deploying Sakai] QA testing idea - Adopt-a-Tool ?

Neal Caidin neal.caidin at apereo.org
Mon Oct 21 11:55:47 PDT 2013

[ qa, dev, docs, production, sakai-user, pedagogy]

At our QA team meeting last week, we discussed the challenge of testing the upcoming 2.10 release. One idea we discussed is an Adopt-a-Tool approach. The idea is that certain tools may be more heavily used, or more strategic to your institution's mission than other tools in Sakai and therefore, perhaps you would have more of a vested interest in ensuring the quality of the tool for the Sakai 2.10 (or whatever it will be called) release? 

What do you think? Does this make sense for your institution as a way to commit resources for the upcoming need for QA testing? How should we implement this (such that, for example, we don't have 10 institutions adopting the Lessons tool and no institutions adopting Assignments) ?

Other ideas for getting a great participation in 2.10 testing are much appreciated. Feel free to send brainstorm ideas.


P.S. I'll be sending out more information on 2.10 testing and how you can get involved soon (whether or not you like the Adopt-a-Tool idea).

Neal Caidin
Sakai CLE Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20131021/8ce72903/attachment-0001.html 

More information about the production mailing list