bootstrap_mint project open to new maintainer applications on 30 Sep, 2021

I would like to request maintainership for this project. We actively use it at my supporting organization, and need to have this regularly updated at this time.

I am attempting to obtain maintainer of this as it has been up for grabs since 2021 and the organization I am with needs this to be regularly maintained, therefore, I will take that on.

Moving to the correct issue queue.

Quoting from the issue summary:

If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.

This project is opted in to security coverage, and mighty_webber does not have security coverage opt-in permission. The site moderators will not as maintainer someone without this permission to a project opted in to security coverage.

Moving it back to the Bootstrap Mint issue queue.

Do you mind providing guidance on that rather than just blowing past this and continuing to let this module be unsupported? This module needs to be maintained. It hasn't been touched in 5 years.

I'm seeing in the docs from https://www.drupal.org/node/1011698: →

You can only use a project for which you committed most of the code in a branch for that project.
This means that, for example, if you are co-maintainer of that project and you want to become maintainer (user with all the permissions on that project), or the new project owner, then you can use that project for the application, as long as there is a branch in that project with code committed mostly by you.

I have a PR for this that has been open for over a year now that hasn't been touched. I don't know if this counts.

https://git.drupalcode.org/project/bootstrap_mint/-/merge_requests/1.

If that's not the case, then I'll just have to snag the code and bring it into our custom repositories maintained in house and completely abandon this project entirely.

The important part is here: https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

Given the maintainer hasn't been active in four years I suspect they've left the community.

Another option would be to switch to a different Bootstrap theme, like Bootstrap Barrio, which is actively supported.

Do you mind providing guidance on that rather than just blowing past this and continuing to let this module be unsupported?

I have already provided this guidance. Here it is again:

If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.

You are unable to confirm that you have previously received security coverage opt-in permission, because you have not previously received security coverage opt-in permission.

I have a PR for this that has been open for over a year now that hasn't been touched. I don't know if this counts.

I doubt it, since a single PR/MR isn hardly "a branch in that project with code committed mostly by you", as stated on: Apply for permission to opt into security advisory coverage → (you tried to link to the page, but your link is broken).

Anyway, the site moderators don't review requests to opt in to security coverage. That's a separate process. You can try do apply, and if your PR passes peer review, please come back and offer to maintain again. Then, I would be much happy to add you to the team.

If that's not the case, then I'll just have to snag the code and bring it into our custom repositories maintained in house and completely abandon this project entirely.

I understand that this is frustrating. Please understand that there are rules that regulate what the site moderators are allowed to do, including rules imposed by the Drupal security team. I am not at liberty to disregard those rules, even if it means that some abandoned project stay abanoned, and as a result are forked or maintained in-house by those that want to keep on maintaining tyem.