Committed to Code

Moodle is a learning management system for producing Internet-based course Web sites. It is written in PHP and is easy to install and use on Linux, Windows, Mac OS X, SunOS, BSD, and Netware 6. It has been designed to support modern pedagogies based on social constructionist theory, and includes activity modules such as forums, chats, resources, journals, quizzes, surveys, choices, workshops, glossaries, lessons, and assignments. It has been translated into over 70 languages, with more on the way, and supports the popular SCORM standard for content packaging. Moodle offers a free alternative to commercial software such as WebCT or Blackboard, and is being used by a growing number of universities, schools, and independent teachers for distance education or to supplement face-to-face teachin

Code Analysis


Recent Highlights

Avatar

Large commit — Merge branch 'MDL-29624-master' of git://github...

More than 1000 lines of source code were added or removed in this commit.

In commit e1e3fa21 by aparup (Using name ‘Aparup Banerjee’) on 2012-05-10 (8 days ago)

Anon32

Large commit — Merge branch 'w19_MDL-32843_m23_yui351' of git:...

More than 1000 lines of source code were added or removed in this commit.

In commit 96fdfb44 by Dan Poltawski on 2012-05-09 (9 days ago)

Avatar

Large commit — MDL-32843 import YUI 3.5.1

More than 1000 lines of source code were added or removed in this commit.

In commit 353efa00 by Petr Škoda (skodak) (Using name ‘Petr Skoda’) on 2012-05-08 (10 days ago)

Avatar

Large commit — MDL-32680 import latest TinyMCE 3.5

More than 1000 lines of source code were added or removed in this commit.

In commit 3690955e by Petr Škoda (skodak) (Using name ‘Petr Skoda’) on 2012-05-03 (15 days ago)

Anon32

Large commit — MDL-31270 mod_assign: introducing the assignmen...

More than 1000 lines of source code were added or removed in this commit.

In commit bbd0e548 by Damyon Wiese on 2012-05-03 (15 days ago)

See all highlights…


News

Gavin Henrick: Moodle Research Conference extends submission deadline till 28th May

Earlier today Martin Dougiamas posted on Moodle.org about the upcoming Moodle Research Conference on 14-15 September 2012 in Heraklion, Crete.

“The purpose of the conference is to support networking and sharing among those who are ... [More] researching Moodle and thinking about ways to improve it for different learning scenarios.   It will also directly inform the development of Moodle in the future.”

This is going to be interesting aspect which was not apparent before but makes sense to learn from successful case studies of implementation of Moodle.  Martin went on to explain:

“We’ve had a good number of papers already submitted for the conference, so it’s looking pretty exciting!  Submitted papers range from in-depth case studies of how Moodle can be applied and used in various environments to interface design experiments and the development of whole new modules to introduce new techniques.

(Personally I love detailed and rigorous case studies.  There are so many ways to apply even a stock Moodle but it’s important to understand what patterns best achieve our goals of improving education and why they work)”

They have extended the submission date until the 28th May, so if you have a paper to submit, go ahead! You have two more weeks to do so.

Conference link – > http://research.moodle.net/ [Less]


Moodle Research Conference 2012

by Martin Dougiamas.  Hi all!

You may have seen the news that we are holding our first official Moodle conference dedicated to research on and around the Moodle platform:

    Moodle Research Conference - ... [More] research.moodle.net
    14-15 September 2012    Heraklion, Crete

The purpose of the conference is to support networking and sharing among those who are researching Moodle and thinking about ways to improve it for different learning scenarios.   It will also directly inform the development of Moodle in the future.

We've had a good number of papers already submitted for the conference, so it's looking pretty exciting!  Submitted papers range from in-depth case studies of how Moodle can be applied and used in various environments to interface design experiments and the development of whole new modules to introduce new techniques.

(Personally I love detailed and rigorous case studies.  There are so many ways to apply even a stock Moodle but it's important to understand what patterns best achieve our goals of improving education and why they work)

We've had requests to extend the submission date a little, so we've done that.  You now have until 28th May to submit your papers!

If you had been undecided until now and missed the deadline this week, or have only just heard about it  - send in your paper and come along!   It's going to be two days of fascinating and meaningful discussions and debate!  And it's in a beautiful location too. 

I'd appreciate you spreading this message to any relevant communities of practice that you are part of - thank you!   You can send them to this URL:   http://goo.gl/eWcH2 [Less]


Gavin Henrick: Some criteria to review when considering a plugin

Although for my plugin reviews I do not do a comprehensive analysis, this is something I use in my consulting and training and recommend to people to think about these type of issues when considering implementing a 3rd party plugin.

There ... [More] are many great 3rd-party plugins available for Moodle. However, it is important to assess the suitability and reliability of the plugin before adopting it. The list in the linked document is not exhaustive as there may be more or fewer questions depending on the individual installation and organisation.

Some hosting providers may have already have audited the plugin and publish a list of ones they approve for their hosting platform - Remote-Learner for example. However. as although something may be technically okay, the suitability and cost implications may be something to make you think.
The list is basically something that one could use to assess the risk related to implementing the plugin. Each question could have a few lines to describe what it means, but you should get the overall picture. To give some context I will explain the reasoning behind three of the questions here:

Question: Has it got a Moodle Docs page.

Even though a plugin may have extensive documentation already, if someone is in Moodle and clicks the Moodle Docs link at the bottom of the page in a plugin that’s where they end up. So having a page, or even a stub page which has the links to official documentation is a good thing and helps people getting lost.

Question: Do they (the author)work for an established Moodle development team (Moodle partner, the OU, or HQ for example)?

This is an assessment of business risk. If someone is a freelancer, the ability for them to provide ongoing support for a module is sometimes (not always) less than where it was built-in an established development team where it may be in use by many clients or installations and thus maintained for business reasons. This is not always the case, but it is just one of the many things that one coud consider.

Question: Does it impact performance of Moodle in normal or high traffic usage?

How complex is the solution? Is it using a lot of slow database queries constantly, are they optimised? are the server resources being heavily used by this and reducing the overall performance? Does it encourage more synchronous activity or is it asynchronous? Understanding what the impact of the usage of the plugin, especially if it is heavily adopted by courses is important.

Download Some Criteria for reviewing plugins (pdf) - 409.64 kB
Please feel free to add any questions or sections that you think should be added to the list [Less]


Moodle 2.2.3, 2.1.6, 2.0.9 and 1.9.18 are now available

by Michael de Raadt.  Moodle 2.2.3, Moodle 2.1.6, Moodle 2.0.9 and Moodle 1.9.18 have been released.

In addition to a number of bug fixes and small improvements, security vulnerabilities have been discovered and fixed. As always, we ... [More] recommend that you upgrade your sites to these latest versions as soon as possible. All admins of registered Moodle sites have been notified with security issue details.

Upgrading should be very straightforward. Full details about the releases can be found in the release notes:

Moodle 2.2.3 release notes
Moodle 2.1.6 release notes
Moodle 2.0.9 release notes
Moodle 1.9.18 release notes

The releases themselves are available via the Moodle download page as packages or direct from our CVS and Git repositories.

Please note that Moodle 2.0.9 and Moodle 1.9.18 are no longer fully supported. They are supported for security fixes only. [Less]


Integration, exposed: Integration round 2012-05-11 Summary - hi, stables!

by Eloy Lafuente (stronk7).  

Cold numbers:

71 issues have been successfully integrated with 9 rejected and 1 delayed. That is near 89% success,  one, well done!

Notes:

Because some of the ... [More] features planned for Moodle 2.3 are still being improved and finished, it has been decided to delay the beginning of the QA testing cycle for 2 weeks, so it will be starting on May 21th. Surely that will cause the final release date (originally scheduled for June 4th) to be moved slightly in order to GTD™ properly.

So, no doubt, the next week will be an intense one. It is the last one for anything wanting to debut in Moodle 2.3.

In the stable side, the last produced weeklies are the candidates to become the next minor releases, so expect Moodle 1.9.18, 2.0.9, 2.1.6 and 2.2.3 to be announced and available on Monday, April 14th. We are packaging all that stuff, release notes, security advisories right now. 

Hot topics:

MDL-32843 - YUI updated to 3.5.1
MDL-31147 - In progress, detect and take rid of deprecated stuff.
MDL-32718 - Recent activity fixes under group modes.
MDL-32899 - Fixing the assignment upgrade tool.
MDL-32849 - Better support of URL rewriting by slasharguments and themes.
MDL-32689 - Allow blocks to decide if collapse is allowed.
And a lot more in multiple areas like mod_assign, ajax, enrol, quiz, calendar, forms, administration, scorm, E_STRICT fixes...

Warm thanks:

To Aparup Banerjee, Dan Poltawski and Sam Hemelryk, for their continuous handling @ the iTeam*, always finding, sharing, instructing, proposing and collaborating in a wonderful way. Thanks, I love to work with you!

Ciao all, stronk7 

* iTeam: Integration Team, take that dear Apple, I was first (I hope)!    [Less]


Read all Moodle articles…

Edit RSS feeds.