Offering to maintain Block Access

I contacted @larowlan because he's the only maintainer who's been active in the past years. I sent him this message:

Hi,

Could you post a comment on my offer to co-maintain Block Access ( https://www.drupal.org/project/block_access/issues/3489002 💬 Offering to maintain Block Access Active )? I would like to become a co-maintainer of the module to help resolve any pending and future
issues.

Thanks in advance,
Dieter Holvoet

Hey, as far as I'm aware this module is redundant, the functionality was added to code in 10.2

I'm happy to make a D11 release if there's a need for it, but I'm not sure why it's still needed

Okay, I didn't know! In that case I don't need to become maintainer. Maybe this should be communicated through the project description and the module should be marked as obsolete?

Good idea, will do next week👍

I'm afraid just marking as obsolete won't be enough to provide a smooth transition to the permissions provided by core. I created a separate issue: 📌 Mark the module as obsolete and provide an upgrade path Active .

@larowlan are you willing to keep maintaining the module? If not, my offer still stands.

Yeah I'm happy to see it off into the sunset.
Feel free to ping me if I'm a blocker

Actually, only fengtan, the project owner, has the Administer maintainers permission. It should be him to be contacted.

I sent the same message to fengtan through their contact tab.

Thanks for offering to maintain this project, @dieterholvoet.

I have just granted @larowlan all permissions on this project. I did not contribute to the 8.x branch, and do not use it myself, so I will defer to @larowlan to determine if they need an extra maintainer.

@larowlan could we move this forward? All important issues are ready for review or reviewed. I'd be happy to become co-maintainer and prepare a new release.

Let me just confirm with @acbramley the other maintainer

No issues on my end, thanks for taking the reins @dieterholvoet

Welcome to the team @dieterholvoet - goes without saying but please use one issue per commit for transparency sake.

Thanks for coming onboard

Thanks! Unrelated question: I noticed the D7 releases have been marked as unsupported. Would it be okay for you if I close any D7 issues as won't fix?

Also, the default branch is outdated and I don't seem to have permission to change it: 📌 Change default branch to 8.x-1.x in Gitlab Active .

Thanks for volunteering and welcome @dieterholvoet!

Thanks! Unrelated question: I noticed the D7 releases have been marked as unsupported. Would it be okay for you if I close any D7 issues as won't fix?

As long as they are not relevant for Drupal 10+ (I am guessing none of them are), sure.

Also, the default branch is outdated and I don't seem to have permission to change it: #3515472: Change default branch to 8.x-1.x in Gitlab.

Alright I have made 8.x-1.x the default branch and closed 📌 Change default branch to 8.x-1.x in Gitlab Active .

Automatically closed - issue fixed for 2 weeks with no activity.