acb project open to new maintainer applications on 5 Oct, 2021

Hi, i'd like to help out and become the new maintainer/owner. I work for a Drupal based internet bureau called https://cipix.nl.

We use this module in one of our websites and I'd like to see it stable, covered by the security release team and finish the Drupal 8/9 variant.

An example of another module we created can be viewer here: https://www.drupal.org/project/event_log.

Furthermore we write and test patches where we can to help the community.

Cheers,
Tarik

tarik.cipix,
thank you for offering to maintain this.

You write: "I'd like to see it […] covered by the security release team"

It is already covered.

To be added as maintainer, you need to follow the instructions in the issue summary that appear under the heading "Next steps".

One of these say:

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

Such a confirmation is missing from your offer, and I find no record of you having this permission. Please clarify.

You may want to read: Apply for permission to opt into security advisory coverage.

Can tarik.cipix please be given access ?

I'm not sure I am qualified to take ownership, but without a D9 release, I'll have to jump through some hoops to get at this module.

Regarding gisle's comment, "It is already covered", I'm not sure this is the case. D8 is dead and there is no D9 release. We have a patch sitting there, someone with access just needs to pull this in. Ideally, the current maintainer would step up and do a solid on this.

(I'm planning to fork into a private repository to get past this for the short term.)

Thanks, all.

sgroundwater,
yes, access to tarik.cipix can be given by the project's owner (i.e. svendecabooter).

But access cannot be given by me.

When I said in comment #3: "It is already covered" - I was referring to this paragraph on the Access Control Bridge project page:

Stable releases for this project are covered by the security advisory policy.

As for the the process for giving someone access to a project, please see procedures for Taking over unsupported (abandoned) projects. The most relevant bit is this:

When the project is covered by Drupal's security advisory policy, you need to have the permission to opt into security advisory coverage, or the change must be done/approved by the project's owner.

As for you (sgroundwater) to be added as maintainer, I believe you're in the same situation as tarik.cipix. I.e. you do not have permission to opt into security coverage and can only be added by the owner. Please correct me if I am wrong about this.

Hi,

I had completely lost track of this module, and the fact that I am maintainer for it.
I have now added a 2.0.0 release, that adds the D9 support.
Further cleanup / maintenance would have to be done by someone else. I am Ok with it if tarik.cipix want to take on that task.

Hope this helps.

@tarik.cipix I have added you as maintainer to the project.

I think this now can be closed as "Fixed", but I leave that to svendecabooter.

Svendecabooter - The D9 release looks to do just what I needed. I really appreciate the version bump/release. Thanks so much for the help.