Offering to maintain Maintenance 200

Contacted barrett at 16.05.2024

Moved to Drupal.org project ownership issue queue.

The project link is https://www.drupal.org/project/maintenance200 → .

Between the maintainers, only Bennett logged in on drupal.org at least once in the past 12 months. I am going to contact him.

This is the message I used to contact Barrett.

Hello Barrett,

I am contacting you because Yogesh ( https://www.drupal.org/u/yogeshmpawar → ) offered to become maintainer for Maintenance 200 ( https://www.drupal.org/project/maintenance200 → ), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3447522 → about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue. In the case you accept the offer, you can also add Yogesh as maintainer.
Without a comment posted on that issue in the next 14 days, Yogesh will be probably made maintainer.

Neither project moderators nor site moderators will remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

The status has been changed since we are waiting for a reply.

I would like to maintain/support Maintenance 200, especially the Drupal 7 version.

It is my understanding Drupal 7 versions are no longer eligible for support.

Community support for contributed modules and themes will continue as it has to date. However, beginning August 1, 2023, once the Drupal 7 branch of a contributed module or theme is marked unsupported it will not be eligible for new maintainership and will not be marked supported again. This will be true if an existing maintainer marks the module/theme unsupported, or if the security team marks it unsupported for lack of response. If there are Drupal 7 modules or themes that you or your clients rely on, then we strongly encourage you to adopt these projects proactively.

https://www.drupal.org/psa-2023-06-07 →

If the applicant adopts the module they will only be able to publish releases for D8 and above.

Setting to Needs Work as the applicant should confirm that they still want to support the module given the limitation against providing D7 releases..

Happy to transfer ownership of the module, assuming it’s still wanted given the D7 note above.

If ownership is not wanted this module should probably be set to a status of abandoned.

@Barrett Thank you for your quick reply!

Hello all Thank you so much for quick update, as I mentioned earlier I am willing to support D7 version of module given the limitation against providing D7 releases. Thanks.

Hi @apaderno, What will be the expected timeline to get update on the request.

@apaderno, what will the next steps on this issue. Please update.

@yogeshmpawar Once a Drupal 7 branch is marked as no longer supported, no new maintainers will be appointed for that branch. That is what End of life announcement and changes to Drupal 7 support - PSA-2023-06-07 → reports.