Ruth, I have been in a number of institutions that like the idea of being able to modify code and update software, but most do not have the skills or history with contributing to an OSS community to do this effectively. While at the Open Polytechnic, we were committed to going Open Source, but we were equally committed to taking advantage of the strengths of a robust community by not forking from the Moodle community. Richard Wyles and his team managed the tensions around working with the Moodle community, influencing the Moodle development roadmap, and setting appropriate internal expectation at the Open Polytechnic regarding the trade offs between “autonomy” and “community”.
Can you share UCLA's position around participating in the Moodle community and meeting institutional requirements?
- 868 reads
