Martin Dougiamas

Can I just clarify a bit here ... I know Tim pretty well, and when I read this post I read it as being self-deprecating, saying that developers needed a brow-beating sometimes.   Which is true.  We need your feedback, and we need people to fight for things.

Let's get those niggly last areas sorted out in the next few releases.

Love you all!

The trouble with letting anyone file pull requests and assign them at the moment is to avoid having to triage lots of bad pull requests and waste the integration reviewers time (they have to be timely!)

The PULL project in the tracker is a first pass at making something usable to get Moodle HQ going without impacting much on the main tracker.

But I agree with you, it would be good to have the same tools available for component maintainers.  Still working on this.  It may be better to include all this in the main workflow for the original issues - we just need to experiment more with configurations.

Just an update on this.

it's a little later than expected, but we are definitely switching to git this week.

All direct CVS access will be switched off today, and during this week CVS will be converted to a read-only copy of the main repository git://git.moodle.org/moodle.git (which will have write access enabled to it).

If you are a third party and have code that you want to get into Moodle, then make sure there is an issue in the tracker addressing and describing it, and then do one of these:

1. if the component has a maintainer, submit it as a patch or git url to the issue so the component maintainer can deal with it
2. if there is no component maintainer, or you ARE the component maintainer, initiate a pull request to have your code reviewed for inclusion in Moodle.  You do this by creating a new issue here:  http://tracker.moodle.org/browse/PULL

We could just turn the rating off ... it doesn't really serve much useful purpose, I agree.

I'll leave that to the facilitators to decide though.