Having seen Tim’s post about fixing a bug in Moodle core I thought I should take the opportunity to follow up with the next part of the process – integrating the changes into the Moodle core. Once a developer has produced a fix which is ready for integration and requests a integration review then the bug is ‘handed over’ to the integration team.
The integration team
The integration team is staffed by a group of developers at Moodle HQ. We are a geographically disparate team, spread across the world in order to prevent natural disasters and political unrest from affecting the Moodle weekly release cycle. ((That might not be the reason.. ;–) )) Aparup and I are located in Perth, Australia; Eloy in Lardero, Spain and Sam in Nelson, New Zealand.
When Tim first returned to the UK from his time at Moodle HQ, the first thing he did ((Well, the first thing I knew about, anyway)) was to invite me to come to The Great British Beer Festival with him. Apparently i’d taunted him with reports of Real Ale whilst he was in Perth. Well.. it’s time for Tim to get his own back!
After seven years working at LUNS and nine years living in Lancaster, I’ve decided to have a change of scenery and i’m going to be leaving many great friends and colleagues behind to move to Moodle HQ in Perth, Australia. Needless to say, this was not an easy decision to make. (Although the weather like Lancaster demonstrated today could convince me otherwise!)
My involvement with Moodle started with LUNS and it has been a great journey. We were newcomers to the Moodle community with a small project to move a few keen high-schools onto supported hosting platform in 2005. My first post to moodle.org was asking the theme forums for advice on how to do multiple themes on a single codebase and the first patch I remember getting accepted was to help us solve that problem six months later: MDL-6784. Although the git history suggests my first fix was actually a horrible JS change which surprises me more than anyone!)) Today LUNS is one of the largest non-HQ code contributors to recent Moodle releases and have provided hundreds of thousands of people with access to Moodle through our various clients – primary school students, university lecturers, high school teachers, company employees and charity workers. I’ve thoroughly enjoyed that journey and the great people who have made it what it is.
I’m really looking forward to working for Moodle HQ! Despite being so close to Moodle as a developer, I continue to be amazed and motivated by how many people I can touch by working on Moodle. Friends from my days at school and university use Moodle as part of their job on a daily basis, my youngest sister is currently studying and supported with Moodle (unfortunately only at stage 1 of Martin’s pedagogical stages) and I meet more and more moodlers ever day! I’m hoping that my time working as external developer working on the other side of the world to Perth will be a great new perspective to add to the team.
I’ll be working for LUNS for a while yet, but it feels like a good opporunity to thank everyone i’ve worked with over the years at LUNS, clients and community members who accepted my patches. :) I’m touched by the kind post about my leaving. I expect to continue working with you if more indirectly at Moodle HQ. :)
 Making their initial steps to learning how to use a computer  No comment
Earlier today I came across an interesting project which provides a ‘proxy interface’ to Siri on the iPhone 4S allowing custom plugins to be created to respond to requests from Siri.
Eager to try this I hacked together a Moodle plugin for the siri proxy which would do lookups to the Moodle tracker. So, welcome Siri – the newest aid to the Moodle 2.2 QA testing effort :–)
(The plugin I wrote is available on github. It is my first ruby script and its not particularly elegant as it was just for fun :–) )