Plugins guardians: Difference between revisions
David Mudrak (talk | contribs) m (→How to join: Add note about providing references to existing moodledev work) |
David Mudrak (talk | contribs) mNo edit summary |
||
Line 15: | Line 15: | ||
These three come in this priority order. So for example, even not-so-well-written plugins can be approved as long as it is believed the community would profit from them and there are signs that maintainers will improve them in the future. | These three come in this priority order. So for example, even not-so-well-written plugins can be approved as long as it is believed the community would profit from them and there are signs that maintainers will improve them in the future. | ||
== How to join == | == How to join == | ||
Moodle developers and experienced users are welcome to sign up for the Plugin guardians programme. Please email David Mudrák <david@moodle.com> for more details. Please attach links to your Moodle development related work such as published plugins, Moodle patches, forum posts in developer forums etc. | Moodle developers and experienced users are welcome to sign up for the Plugin guardians programme. Please email David Mudrák <david@moodle.com> for more details. Please attach links to your Moodle development related work such as published plugins, Moodle patches, forum posts in developer forums etc. |
Revision as of 14:14, 30 January 2019
Plugins guardians are Moodle community members who volunteer to provide peer-reviews on plugins submitted into the Plugins directory. Their peer-review is considerably taken into account when deciding on the plugin approval.
Mission
These are the main principles and goals of the Plugins guardians programme:
- Help to build healthy and sustainable eco-system of Moodle plugins.
- Protect the Moodle sites from dangerous, unreliable and generally badly written plugins.
- Serve the plugin authors by providing them with honest feedback on their work, together with suggestions on how to learn to improve their code.
These three come in this priority order. So for example, even not-so-well-written plugins can be approved as long as it is believed the community would profit from them and there are signs that maintainers will improve them in the future.
How to join
Moodle developers and experienced users are welcome to sign up for the Plugin guardians programme. Please email David Mudrák <david@moodle.com> for more details. Please attach links to your Moodle development related work such as published plugins, Moodle patches, forum posts in developer forums etc.