Simon Coggins

Hi Eloy,

My unique and genuine interest it to see any fix, improvement landing back into "mother" Moodle. So everybody else benefits of it.

That's a totally reasonable request - to answer your question, yes we upstream all Moodle bugs found during development or reported to us. We have an 'upstream' tag in our bug tracker specifically to identify and track upstream fixes. When we file a new Moodle issue we usually supply a patch and respond to review input until the fix is integrated.

Aside from bug fixes we try to offer upstream anything we think would be useful, from whole features, minor improvements, security improvements, performance improvements, or even the occasional crazy idea . If there's anything else we've done that HQ would like to see in core Moodle, drop me a PM.

Finally can I also just say a huge thank you from the Totara dev team for all the hard work you and the rest of the community does to make Moodle the awesome platform that it is. Totara couldn't exist without it and we do appreciate it!

Simon

Hi Andrei,

I'm afraid it doesn't really make sense to report Totara-specific errors on the moodle forums. For questions like this you would be better off raising a support ticket or posting in the Totara forums.

We'll be in touch directly to help with your query.

Simon

I think you could encourage more peer review by:

1. Making it a bit more obvious that it is something you want developers to do
2. Making it clear how to do it
3. Providing easy access to a list of what needs reviewing.

To be honest it never really occurred to me that I could be peer reviewing things - I guess the phrase comes with a certain weight of responsibility. This is linked to your point 3 but is more "am I qualified to do it" rather than "I'm not expected to do it".

For my point 1 I just did some searching to find out how to peer review and found this:

"The component lead should peer-review the change. If there is no component lead for an affected component, any other recognised developer may complete the peer review."

From http://docs.moodle.org/dev/Process#Peer_review

Which make it seem more like an exceptional event rather than something that is actively encouraged.

For 2, the how to peer review checklist is good.

For 3, I just went looking for tickets that needed peer reviewing. Although I could create my own filter in JIRA for tickets with status of Peer Review I eventually also found the Peer Review Dashboard, which is much more helpful. It was tucked away though (Under Tools > Find Dashboards > Search for "Peer Review"). I think it would be good to make it much more prominent.

Simon

We are planning on implementing this feature in Totara soon and are happy to develop it and contribute it to Moodle if they are willing to accept it.

We have filed a bug in the tracker here with some ideas, please vote for it and comment if you would like to see this feature:

https://tracker.moodle.org/browse/MDL-44275

Simon

Have a look at the tracker issue:

https://tracker.moodle.org/browse/MDL-31830

There's been quite a bit of recent progress, and the current prototype is at the stage where feedback would be most appreciated.

Simon