Projects for new developers
Getting started
Moodle uses PHP, JavaScript, SQL and a number of other Web languages, so learning those is a good place to start.
When you have some basic PHP programming skills, you may wish to start learning about how the Moodle code is organised. It is recommended that you complete the Introduction to Moodle Programming course on dev.moodle.org. To access this you will need to have an account on moodle.org first.
If you are looking for projects suggested in the tracker, look for issues with the 'addon_candidate' label.
If you are looking to make a quick contribution, look for tracker issues with marked as easy.
Please consider adopting a plugin seeking a new maintainer. See the Plugins adoption programme.
As you become more involved in Moodle development, you might like to learn more about the coding conventions used and how changes to Moodle core code are processed.
Potential projects
This evolving page lists possible Moodle projects for new developers derived from community suggestions.
If you have any ideas for new features in Moodle which might be suitable as projects for new developers, please see New feature ideas.
Allow to crop/resize/rotate images when inserting them
This project is inspired by MDL-32183. There are two options on how to implement this functionality - as a repository plugin or as an atto plugin.
- Skills required: Javascript (YUI), PHP
- Difficulty level: Medium
- Possible mentor:
Improve Behat tests in SCORM plugin
The Moodle SCORM plugin does not contain very many behat tests and most tests are manual. The Claude Ostyn diagnostic SCO should be used to implement a range of new Behat tests to cover the functionality that the SCORM module provides.
Deliverables:
- Behat tests for all existing SCORM QA tests (where possible)
- Behat tests for all SCORM settings (eg standards mode, mastery score settings etc)
- The code should pass 100% of the Moodle codechecking tools to ensure the code meets with Moodle Guidelines.
Extra requirement for prospective students. Moodle requires all GSOC applicants to make an attempt at fixing at least 1 issue in the Moodle tracker before their proposal can be considered - on top of this you must also attempt to convert one existing QA test into a Behat test. This MUST be completed before your application can be considered valid. If you do not have time to do this before the submission deadline your application cannot be considered.
- Skills required: PHP
- Difficulty level: Medium
- Possible mentor: Dan Marsden
See also
- GSOC - describing Moodle's involvement with Google in their Summer of Code program
- Popular new feature and improvement requests in Tracker that can be implemented as plugins
- Archive of outdated and/or inactive calls for projects
- a Wishlist by some Moodle users. Some of the good ideas here may be adopted.
