Marking D7 projects supported again we care about
As @mustanggb said in #14 (closed) drupal.org has hit the kill button for Drupal 7 support on drupal.org.
The good news: Update XML is still here, for example for Views https://updates.drupal.org/release-history/views/7.x
The most important project is Drupal 7 core, where we don't have D7Security members yet that want to step as core maintainers. I don't plan to maintain Drupal 7 core, as I'm relying on the D7 extended support vendors to supply updates to me and leaving the maintenance work to them. However, I'm happy to support community members that want to step up as Drupal 7 core or contrib maintainers in the D7Security group. Please follow https://www.d7security.org/docs/general-information/d7security-members/ if you want to join!
I think it does not make sense to fork hundreds of git repositories when we don't want to make changes for now. We only want to provide updates for those modules when a security fix or compatibility fix needs to be done.
We can set projects to supported again quickly without forking the git repository yet:
- A D7Security member needs to trigger https://gitlab.com/d7security/d7security/-/pipelines/new
- PROJECT_NAME: fill out drupal.org project name, example: rules
- PROJECT_VERSION: leave empty
- Add project to supported projects https://gitlab.com/d7security/d7security/-/blob/main/supported_projects.txt?ref_type=heads with a pull request
- Add responsible maintainer to wiki list at https://gitlab.com/d7security/d7security/-/wikis/Supported-Drupal-7-projects#maintainers-for-projects
The only problem is that it needs to be done for hundreds of modules, so we need lots of volunteers.
It probably also makes sense to start a wiki page who maintains what D7 project, so that it always clear who can help when security issues are found. Did that at https://gitlab.com/d7security/d7security/-/wikis/Supported-Drupal-7-projects#maintainers-for-projects