Closed (fixed)
Project:
Drupal.org project ownership
Component:
Maintaining offer
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
8 Jan 2025 at 19:39 UTC
Updated:
2 Aug 2026 at 15:05 UTC
Jump to comment: Most recent
Please provide me higher maintainer permissions, so I can:
* Add maintainers to the project
* Change default branches in Gitlab
There are ongoing initiatives to get this project cleaned up and to add additional maintainers, as a number of the maintainers on this project are no longer actively involved.
Please assist or advise.
Comments
Comment #2
lisa.rae commentedComment #3
avpadernoComment #4
w01f commented+1 for an additional active maintainer if they're offering
Comment #5
avpadernoAs a reminder: These offers can be moved in the Drupal.org project ownership queue, after they have been kept in the project queue for at least 14 days, and none of the maintainers commented to decline the offer, if the person who made the offer is still interested.
Comment #6
avpaderno(For project moderators who can access the following pages: https://www.drupal.org/admin/people/advanced?name_op=%3D&name=twistor&ma..., https://www.drupal.org/admin/people/advanced?name_op=%3D&name=jungle&mai..., https://www.drupal.org/admin/people/advanced?name_op=%3D&name=mglaman&ma..., https://www.drupal.org/admin/people/advanced?name_op=%3D&name=vijaycs85&....)
Comment #7
avpadernoI am closing this issue because there has not been any follow-up action as described in How to become project owner, maintainer, or co-maintainer from the person who opened this offer.
Comment #9
lisa.rae commentedComment #10
lisa.rae commentedI have been on a hiatus since February 2025, but recently plugged back in, so I’m reopening this issue.
I have finally wrapped up the refactor for version 3.0, which was a complete rewrite, have released it as a pre-stable release, and will be releasing it as stable in the next few weeks after the open issues that are blocking a stable release are resolved.
I’ve also worked some bugs in the issue queue for versions 2.2 and 2.3, and cut bugfix releases for those versions.
There is an open issue that cannot be resolved at this time because I don’t manage the state of the code repository, and can’t set the recommended version of the module. I believe only the module maintainer can do that. Right now the repository is showing the default branch as the 2.0 branch which has been deprecated for quite some time.
Without the ability to properly set the version, it leaves the update manager in a disconnected state.
Comment #11
lisa.rae commentedComment #12
longwaveThe next step is to move this to the Project Ownership queue where a site moderator will try to contact the owner, which I am doing as part of this comment. If they agree, or there is no reply within 14 days, you should be able to claim ownership.
For site moderators: the project link is https://www.drupal.org/project/flysystem
Comment #13
avpadernoOf those people with the Administer maintainers, only the project owner has not logged in in more than a year. The other maintainers logged in at least once in the past six months.
I should be able to handle this request tomorrow.
Comment #14
lisa.rae commentedThank you @avpaderno!!!!! Much appreciated!
Comment #15
avpadernoThe project link is https://www.drupal.org/project/flysystem.
Comment #16
avpadernoThis is the first message I sent.
Comment #17
avpadernoI contacted all the maintainers who logged in at least once in the past 12 months.
The status is Postponed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder that a project moderator's action is required.
Comment #18
lisa.rae commentedThank you @avpaderno!
Comment #19
jungleAs one of the maintainers, I support @lisa.rae becoming a full maintainer of the project. Her work on the 2.x releases and the 3.0 rewrite demonstrates active stewardship of the module.
I have just granted @lisa.rae full maintainer permissions. Thanks @avpaderno for reaching out.
Comment #21
avpaderno@jungle Thank you for taking care of this!
Comment #22
lisa.rae commented@avpaderno, @jungle thank you both!