- 🇳🇿New Zealand quietone
This is now handled by the Project Update Working Group → whose mission is to help "maintainers prepare contributed projects for the next major release of Drupal core".
There are Drupal modules that need Drupal 8 ports finished and better issue queue support. Many of these modules are owned by past contributors who no longer have enough time to contribute or folks who have moved on to other things. Taking over a contributed module is a big commitment for an individual and the process to get added to maintain a module is difficult.
This isn't quite a core idea, but this still seems like the best place to post this discussion.
I'd like to start a community maintenance team for contributed modules. This will largely be a self-organized team which will likely be a Slack channel, a landing page, and a couple of sign up forms. Folks could volunteer their time, and module maintainers could request support from the team for their project.
To start with, we would look at projects that the initial volunteers are most interested in and for projects that have easy wins in terms of completed work waiting.
What do you think of the idea? Do you have suggestions or concerns? If you maintain a module now, what kinds of things would you need to see from the group to be comfortable adding us to maintain your module? If you're interested in volunteering to help out such a group, what kinds of things would you want from the group in terms of support?
If you'd like to discuss this topic on Slack, feel free to join us in #maintainers on Drupal Slack: https://www.drupal.org/slack → .
Closed: outdated
Idea
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is now handled by the Project Update Working Group → whose mission is to help "maintainers prepare contributed projects for the next major release of Drupal core".