After couple of weeks of planning and discussions, last week saw a new position in Moodle HQ team. The new "plugins liaison" role is supposed to link Moodle HQ with the world-wide community of plugins developers. The communication channel the position represents is bi-directional. In one way, the liaison keeps the dev community well supported and informed. In the other way, the liaison gathers feedback from the dev community and acts as an ombudsman advocating for the needs of the plugins developers community within Moodle HQ.
Main responsibilities of this job include:
- Managing the Plugins directory content (categories, configuration, permissions and plugins review and approval).
- Plugins directory maintenance and further development.
- Feeding and moderating a blog like forum at moodle.org with interesting news on new plugins or updates, reviews, things of note, API changes, good development practises etc.
- Gathering and acting on feedback on the overall plugins development procedure and the actual plugins directory UI and features.
I must admit I did not hesitate long and proudly accepted the challenge of holding this new position. Additional plugins are essential part of the whole ecosystem where Moodle as a software itself is (just) a platform - like a mobile OS is a platform for apps. Moodle as a project rely on top-quality, trustworthy and continuously maintained community plugins. And I'm happy to be now part of the plugins facilitators team who do their best to keep this ecosystem live.