Closed (fixed)
Project:
Block Access
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Nov 2024 at 16:09 UTC
Updated:
9 Apr 2025 at 13:49 UTC
Jump to comment: Most recent
Comments
Comment #2
dieterholvoet commentedI contacted @larowlan because he's the only maintainer who's been active in the past years. I sent him this message:
Comment #3
larowlanHey, as far as I'm aware this module is redundant, the functionality was added to core 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
Comment #4
dieterholvoet commentedOkay, 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?
Comment #5
larowlanGood idea, will do next week👍
Comment #6
dieterholvoet commentedI'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: #3489678: Provide an upgrade path to the permissions provided by core.
Comment #7
dieterholvoet commented@larowlan are you willing to keep maintaining the module? If not, my offer still stands.
Comment #8
larowlanYeah I'm happy to see it off into the sunset.
Feel free to ping me if I'm a blocker
Comment #9
avpadernoActually, only fengtan, the project owner, has the Administer maintainers permission. It should be him to be contacted.
Comment #10
dieterholvoet commentedI sent the same message to fengtan through their contact tab.
Comment #11
fengtanThanks 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.
Comment #12
dieterholvoet commented@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.
Comment #13
larowlanLet me just confirm with @acbramley the other maintainer
Comment #14
acbramley commentedNo issues on my end, thanks for taking the reins @dieterholvoet
Comment #15
larowlanWelcome to the team @dieterholvoet - goes without saying but please use one issue per commit for transparency sake.
Thanks for coming onboard
Comment #16
dieterholvoet commentedThanks! 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?
Comment #17
dieterholvoet commentedAlso, 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.
Comment #18
fengtanThanks for volunteering and welcome @dieterholvoet!
As long as they are not relevant for Drupal 10+ (I am guessing none of them are), sure.
Alright I have made 8.x-1.x the default branch and closed #3515472: Change default branch to 8.x-1.x in Gitlab.