Moodle OPs – 17th April

Actions from last meeting

Joblink – Moodle Developer. I’ve added the latest job description to our Team Wiki, under Team. Please read, deal with typos, spellings etc., and leave comments. I’ll forward this to Julie on Wednesday

Development Plan:  See later

MoodleMoot: Taliesin will feedback to all on his presentation at MoodleMoot at the next e-learning Team meeting


Discussed the idea of SAMIS occurences in the integration script. This was for English Centre. Current thoughts include this being a script that is run once after a period after the course has started. It would enrol students into their groups based on the occurence details.

Action >> Nitin – contact English Centre to say we’ve added it to the list and have some thoughts.

Action >> Nitin add it to trac, and also include on the Software Development Plan. Once agreed then wide the net to include Joe Buchanan in the specification / testing phase.

Discussed the software development plan. The initial idea is to have identified what we will develop for  rest of year and 2009/10.

Acton >> All – think about adding projects

Action >> Lisa & Nitin – when next go through Trac tickets identify any which are this type of work.

The plan is for us all to meet up near the end of May to prioritise the ones we’d like to implement. There will also be a further discussion with the wider e-learning team

Other points

Moodle 2.0 – decided that we’d install Moodle 2.0 with a sync’d update on multimedia. The timeplan for the actual migration will be either Summer 2010 or Summer 2011 – it depends on the software performance, and required support needs. There is not yet a plan for what we are going to look at with Moodle 2. However, some of the enhancements might be in place so this would influence our decissions. We’ll need to workout a more coordinated testing plan for Moodle 2.0.

Work schedules

Need to fit the following into regular work schedules

1. Maintance (patching etc.,) – every fortnight. This needs to be included within the Tech Meetings as a standing item – just yes / no for the next weeks tag and what support will be required.

2. Cron job the user access reports. Originally linked to LDAP, developed by Matt. Get this running on Multimedia and email ping each week to e-learning@ so it can be cut and paste into the table.

3. Re-iterate the current cycle;

Every Monday – Lisa and Nitin meet to MOSCOW the Trac Tickets

Every Tuesday – All meet to discuss trac tickets and identify what next

Tuesday – Thursday >>> primary slot for ticket solutions

Every Friday (lunchtime) – sign off what is going into tag update

The sign off will require people to confirm that it works … testing might include – local machine, multimedia and test (when appropriate)

Every Tuesday – tag goes live

Friday & Monday >> for longer development projects

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s