Problem/Motivation

As Drupal 7 is no longer supported we should update the list of maintainers of this module. When this issue is closed all Drupal 7 issues will be triaged and mark moved to the 3.x branch or marked as out-of-date.

Proposed resolution

Thank @mfb, @ergonlogic and @astonvictor for their service and update the list of maintainers. File an issue to change project ownership to @chr.fritsch

Do this on 1st July 2025.

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

Comments

alexpott created an issue. See original summary.

alexpott’s picture

I have reached out to @mfb, @ergonlogic and @astonvictor via their contact forms on Drupal.org and asked them to comment on this issue.

chr.fritsch’s picture

Thank you @mfb, @ergonlogic and @astonvictor for all your work on the Drupal 7 version.

It's time to get rid of all the D7 issues. I am +1 on this.

astonvictor’s picture

Hi there,

I didn't work on 7.x version. I only worked on 3.x version.
Here is the list of tasks I worked on - https://www.drupal.org/u/astonvictor/issue-credits/710994

thanks

alexpott’s picture

@astonvictor thanks for replying on issue. Can I ask how you became a maintainer? I've asked the other 3.x maintainers and no one can remember adding you. The reason I ask is that some of the commits you've made to 3.x were a bit premature and have required some re-working. See #3525533: Use an access check to prevent deleting entities if the user does not have break lock permission as an example.

astonvictor’s picture

I guess it was done by https://www.drupal.org/project/projectownership project.

If you want, you can restrict my permissions e.g., delete permission to create new releases, etc.

ergonlogic’s picture

At the moment, I don't have bandwidth to help maintain this module. So I'm fine with having the ownership changed and removing me from the list of maintainers.

mfb’s picture

I could continue dealing with any security issues on the drupal 7 branch, but that's all I've had time for since taking on co-maintainer role, not other bugs or feature requests, or other branches.

alexpott’s picture

@mfb as Drupal 7 is no longer under security support the only thing that could happen is something through the D7LTS community programme so that's a different thing all together and would not require you to be a maintainer of this module.

avpaderno’s picture

(As a side note, astonvictor has been added in #3424090: Offering to co-maintain Content locking.)

alexpott’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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