Martin Dougiamas

Moodle HQ has been pouring precious resources into 1.9 for nearly 5 years now (including the development time before it released), and will keep doing so for another 6 months.  As far as I am concerned, that's a lot.

It's there, it's very stable, and you can continue to use it as long as you want.   If you want to have someone supporting it for even longer, though, you'll have to rely on broader community support.

I am totally focussed on making Moodle 2.x better and better, based on feedback.  File handling is one the top priorities for 2.3, for example.

About performance issues, it's really not very clear where the problems are.  Many are not having problems, and some are having problems in areas that suggest poor tuning.  I'm extremely keen to fix performance problems as they are identified.  Petr Skoda is the component lead in the tracker of all performance issues and will deal with them.

Some quick thoughts on the whole thread here:

Transclusion ... no.  We tried it out, and rejected it.  I think this would be a far more unpopular and confusing choice than simple separate wikis per version which is at least something that most people who aren't developers can understand.

What those here might have forgotten was that the old single wiki was a total mess.  Different versions smushed onto one page, inaccurate and misleading info.  It was a nightmare for users to navigate.  And yes, to use performance as an example, there are huge differences between 1.9 and 2.2.

The path I've chosen here (and I had to convince Helen initially too ) of separate wikis is the best scenario of the bunch (I'm not saying it's perfect but it's the best we can support).   The update process is simple, users get to see exactly what they need to, and not what they don't.  The wikis are much smaller now, and the differences are much smaller now.

Not every doc change needs to be ported back to older versions all the time.  Just edit the most recent one (2.2).  I'm not too concerned about users of older versions of Moodle missing out on a few edits here and there.   It's still much more complete now than it ever was, and those users will be on the newer versions soon enough.

What I think we need to do is go forward, not back, and make more changes to improve

• education of users about the different versions
• navigaton between different versions

I just wanted to make sure that people were aware of this very cool tool that Sam whipped up last year:   CSS Theme Tool

If you edit CSS in Moodle Themes: check it out!

Hi Greg,

The way it's designed is this: 

If you change the structure of the rubric (adding/removing cells or criteria) then that is likely to change the way grades are calculated, so Moodle will force you to regrade everyone and check that their grades still make sense in the new rubric.  Grades are hidden from the students until you do this, to avoid confusing them.

If you change the rubric in a minor way (eg changing some text only) then you are warned and asked if you want to keep the current grades or not.

It's possible that there are some changes that would not affect grading but we are forcing you to regrade.  These could be considered areas to improve.

So how exactly did you change the rubric?

There are standard web services in Moodle already for that exact purpose (the official app uses them).  Why not use those (and help us to extend them where necessary)? 

      http://docs.moodle.org/dev/Web_services_Roadmap