Gauging the risk of 3rd party Moodle Plugins

If you’re like me you have a test site that is solely used for testing modules and addons (lest anything were to go very bad when introducing some new code).  But aside from installing and testing it how do you know it’s safe to use on a production site with students? Aside from the number of downloads and the size of the community that’s talking about it at Moodle.org in the forums, you can also check with many of the Moodle Partners who share basic information about plugins that they’ve code reviewed for inclusion on their hosted systems for clients.

• Moodlerooms lists many modules that they’ve created and many community modules that they support: http://page.moodlerooms.com/l/1662/2011-05-03/KAJGB/1662/111461/ComparisonMatrix_5211.pdf
• Remote-Learner does the same on their site http://remote-learner.net/content/remote-learner-approved-moodle-modules
• Lambda Solutions provides a list of their preferred/recommended community modules: http://www.lambdasolutions.net/files/u92/moodleServices_MODULES.pdf
• Netspot, while not publishing a list does provide some great tips and is open to code review: http://netspot.com.au/pro_plugin.html
• Moodle.org itself publishing some information on how to get your contributed module reviewed via the tracker: http://docs.moodle.org/dev/Guidelines_for_contributed_code

If you’re creating your own module and want it tested or are hesitant to use one of the newest modules published at Moodle.org, consider having the code reviewed through one of the options above.  Please note though that cost and time for a code review will vary by vendor/community resource.