Edit: Actually, it's not the kind of support you can expect from a commercial vendor - try that with Blackboard or WebCT!Sorry, I just couldn't resist telling you all how happy I am that I am using one of those unreliable systems created by a smattering of teenagers too young to work at Redmond, hackers, virus creators, and a menagerie of others, a platform which cannot possibly offer the same level of support as the professionally built product which sports excellent "project planning, quality control, coding standards, accountability, version control, and support".
I did use WebCT for a few years and never had my bugs fixed so fast. And as far as the feature requests are concerned, my feeling was that they were all automatically deleted on the server before anyone even read them. Now, compare it to this community!However, I think there are a few things that we can learn from the WebCT guys. One such thing might be issuing hot-fixes. In the example of the bug I filed it was fixed in CVS (Moodle 1.2 dev) in a few hours, but I had to fix it myself in my 1.1.1 installation. It was not difficult (just replacing one file), took me just a few minutes, but I guess there are a lot of Moodle 1.1.0-1 users who will continue running their moodles with the faulty assignment until they also run into this bug and then they will have to search the forums or the bug tracker to solve again the problem which has long been solved.
I'd like to suggest an additional resource with such hot-fixes. Whenever a bug is fixed which does not only relate to the new features in the dev version, but also exists in the stable version of moodle, a hotfix could be published. It doesn't have to be a whole new installation package (e.g. 1.1.1, 1.1.2, etc), but just the one file or a few files that need to be replaced.
What do you guys think about it?
Cheers,
Przemek