Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Fix a Moodle bug

From MoodleDocs
Revision as of 02:16, 21 October 2016 by Marina Glancy (talk | contribs)

We are holding Fix-a-moodle-bug project in November 2016. The goal is to encourage community contribution to Moodle and bring attention to our tracker.

Every developer who sends fixes for two bugs from Moodle backlog following our contribution process during November 2016 will receive a Moodle contributor t-shirt from us. If you fix a bug with five or more votes we will give you a t-shirt just for one bug fix.

List of issues that participate in the project

As you can see only issues affecting 3.1 are included in this list. If you are not a developer and would like to promote an issue from tracker that affects you - please make sure that 3.1 is listed as affected version on it (you can edit issue or comment on it if you see that 3.1 is missing). The more votes your issue has - the closer to the top of the list it will appear. We would like to remind everybody how important it is that you search for existing issues before creating new ones. Number of votes is an important criterion that developers look at when selecting issues to be worked on. If somebody creates a duplicate instead of voting on existing issue - it actually decreases the priority of the issue.

If you are a developer, in order to participate in this project you have to send bug fixes for peer review during November 2016. All reviews may take much longer and we will send your t-shirt in January after peer review and integration is completed. Only issues that are “bugs” participate in this project, we freeze all improvements until mid-December.