Martin Dougiamas

Perhaps this?

• Recent Conversations
• Recent Notifications

I would personally prefer to see something like the messaging interface on the iPhone, or Gmail for that matter, so you see a list of "conversations" with people sorted with the most recently updated first, going backwards in time.   Effectively your option 2.

Each item just needs the name+icon of the other person, plus the last thing that was said by either of you ... you then click through to see the full conversation.

Yes, Jabber is one of the messaging output plugins(one-way).  Moodle chat is not integrated with Jabber (that's a difficult thing to do).

And once you upgrade to Moodle 2.0, push it to Mooch!

http://hub.moodle.org

Hi Pierre and others!

Yes, the blame for poor communication rests squarely with me and I apologise.

There's a bit of chicken-and-egg here, as we needed a lot of documentation and support and system configuration and processes to cope with our move from cvs to git, but we also needed people familiar with all this to be able to implement it.   Each needed the other, so it's been a bit iterative development (and continues!).  And all this on top of finishing Moodle 2.0 (phew) and continuing on 2.0.1.

But I could have communicated better, I feel.

Please let me assure you that I have no intention of excluding anyone.   What I mean by the list of official developers is that the admin interface we developed for CVS is now defunct (and sometimes innaccurate), we won't be managing access to the main source code that way any more.   We'll need to find a new way of representing developers on moodle.org by their contributions  - fortunately the git database contains all of this information and we will eventually extract it in a friendly display, perhaps similar to: https://www.ohloh.net/p/moodle/contributors

I'm currently still working on configuring the tracker to improve the workflow there (give me a few weeks!), but even now the way for most people to contribute is to post patches against issues in the tracker.  If you learn to use git then you can just post URLs to your code changes, which is easier for everyone.

If you are a "component lead" (someone who has committed to maintaining a module or plugin) then you will also be able to submit such patches for review (and automatic integration into core Moodle).  Right now you need to file an issue in the PULL project but I see this as temporary - soon all you'll need to do is to press "Request review" in the issue itself.