Monday 18th March, 2013
9:30am to 10:15am
Many higher education organizations are attracted to open source because they can make changes as their needs dictate. This carries risk: over time a local implementation can become burdened by these local customizations, or “hacks”, until it collapses under its own weight. That’s not good. However, a second strong point of open source is the community which supports it: you’re not alone and there is strength in numbers. Working collaboratively can lead to a sustainable model of development which includes core engagement.
In this case study, I will show how a group of relatively small schools can leverage their limited developer resources to get desired changes made in the core product in lieu of local hacks. We’ll cover engagement, best practices, coding standards, version control, and the development process. This talk will use Moodle, a popular open-source learning management system (LMS), as its example, but the principles are broadly applicable to other projects.
Web developer, Amtrak zealot and occasional B-movie reviewer. bio from Twitter
10:30am Designing for the (Multi) Big Picture by Jon Brousseau
Sign in to add slides, notes or videos to this session