Tutorial Tuesday: The Moodle Tracker

For today's Tutorial Tuesday, I wanted to take a break from providing a typical "how-to" guide for using features or modules within Moodle. Instead, I wanted to shine a light on Moodle community, and particularly, the opportunity that the Moodle tracker provides users throughout the world to impact Moodle code development.

Basic view of Moodle tracker dashboard

True to all open-source software, one of Moodle's most espoused benefits is that it's source code freely available for anyone to download for their own use (whatever that may be). However, I don't think it's emphasized enough how even new users can use the Moodle tracker to immediately start impacting which features, functionality and issues are prioritized and resolved by Moodle's community of developers, partners, educators and learners. Essentially, the Moodle tracker "democratizes" Moodle code development, and you don't have to be a developer to really make a difference.

Though issue trackers have been used successfully by many other open-source projects, Moodle has done a great job of making it as streamlined and accessible as possible. But just to get you started, here's a couple of links to the quick how-to guides for getting the most out of the tracker:

• Tracker Overview

• How to Submit a new feature idea

• How to submit a bug

• Logging new issues or improvements

• How to see what code was changed
  

Any suggestions to new Moodle users in getting the most out of the Moodle tracker? Feel free to submit them in the comments below.

Thanks for reading