Hi folks. I’ve been the maintainer of cookiecutter-tutor-plugin, a template repository for Tutor plugins. The repo’s goals are:
- provide plugin developers with the bare-bones scaffolding they need in order to make a plugin that can be installed and enabled (without having any affect);
- provide helpful comments and commented-out sections which guide them towards adding common functionality to their plugin; and
- serve as a supplement to the official plugin docs.
As of late, I haven’t had much time to focus on the repository. I can continue nominally maintaining it if I need to, but if there is someone with more time and interest and moving it forward, then I’m happy to pass hand of the reigns!
The reponsibilities, which I’ve ballparked at ~60hrs/year, are:
- Triage and review PRs and issues (~2hrs/month).
- Keep an eye on Tutor’s Changelog. If hooks are added or removed which would affect a “basic” Tutor plugin, then consider making updates to the cookiecutter. (~1hr/month).
- At least once every named Open edX release, between the branch cut and the
- use the cookiecutter to create a plugin. Ensure that the plugin can be installed and enabled in Tutor and that it works as expected. If it doesn’t work, fix it. If there are are deprecation warnings, resolve them. (~4hrs every 6 months)
- run the cookiecutter’s
make testscript, and fix it if it fails (there is no CI currently).
- Consider occasional improvements to the cookiecutter’s structure or docs. Currently there’s one open suggestion. (~4hrs/yr).
You can read more about the rights and responsibilities of Tutor maintainers here.