Martin Dougiamas

Yes, I would love to see this too now we're starting to get enough people.

This could be allocated on a module by module basis, as a "Maintainer" role. We have a lot of orphan modules.

Even if Maintainers aren't able to do much development it would be great to have people taking care of bugs, closing obvious non-bugs, assigning priorities and so on. Performing QA by testing bug fixes would fit in here as well.

That's something we can do for our own bugs using the bulk-change interface.

The new tracker has CVS integration, which means it will search CVS for check-in messages that reference bug numbers such as MDL-1234, and then automatically attach that information to the bug.

eg http://tracker.moodle.org/browse/MDL-3717?page=vcs

(Note: there may be a delay of an hour or so before it shows up on the tracker because of the way this system works)

So please make sure you reference the bug numbers in your check-ins. Thanks!

Upload them into your Site Files area (and not inside a course).

Thanks for finding that, sorry about the hassle.

The thing has been that none of us use Postgres, so switching was an added learning curve that would slow us down.

Vy is going to work on Postgres now, so hopefully that helps.