Offering to maintain Configuration Split Ignore

The proecedure → for becoming a co-maintainer says you post your offer in the project's issue queue (i.e. do not post in the Drupal.org Project Ownership issue queue). By posting your offer in the project's issue queue, you make sure that the project's current owner and most active users see your offer and can comment on it. For the title, use “Offering to maintain Configuration Split Ignore”.

It also says that when opening an issue, you're supposed to contact the current project owner via the contact tab on their Drupal.org user profile page (and/or other means of contact that exists) to let them know about the issue you posted regarding maintainership. There is no record of this being done. Please complete this step, and add the details (who, means of contact and when) to the issue summary.

Finally, the procedure procedure says:

When the project is covered by Drupal's security advisory policy, you need to have permission to opt into security advisory coverage, or the offer must be approved by the project's owner. The site moderators will not add as owner, maintainer, or co-maintainer a user who cannot opt projects into security coverage. See Apply for permission to opt into security advisory coverage → for details on how to obtain that permission.

For more information, see How site moderators handle requests to be project owner, maintainer, or co-maintainer → .

This project is covered by Drupal's security advisory policy, and you don't have permission to opt into security advisory coverage. This means that you must be added to the team by the project's owner. The site moderators cannot add you as a maintainer.

I am moving this to the Configuration Split Ignore issue queue for processing by maximpodorov.

@daffie
Do you have a patch to make the Drupal 10 release of the module?

Hi @maximpodorov, I very happy to see that you are still interested in maintaining this module! We already have an issue for compatibility for Drupal 10. The issue is 📌 Automated Drupal 10 compatibility fixes Fixed . The issue is RTBC. Ready for you to review and hopefully merge. If you merge the issue can you also do a new release.

Hi @maximpodorov it would be really great to merge the Rector patch → that is in the mentioned issue: 📌 Automated Drupal 10 compatibility fixes Fixed

If you don't have time please make @daffie a co-maintainer, so that we can do our Drupal 10 upgrades without having to use Lenient :D

Also here to be available to help co-maintain this module. It's feature complete, so it's just maintaining at this point.

Moving this over to the ownership queue since it's been three months with no response from the current maintainer.

For your offer to be maintainer, please open a new issue.

Since you cannot opt project into security advisory coverage, what said to daffie holds true for you too.
If maximpodorov wants to add you as maintainer/co-maintainer, he will do that, but moving this issue to another queue will not add you as maintainer.

Drupal 10 compatible release is available now.