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

lhridley created an issue. See original summary.

lisa.rae’s picture

avpaderno’s picture

Title: Request for higher maintainer permissions for @lhridley on Flysystem module » Offering to maintain Flysystem
Issue summary: View changes
Issue tags: -become maintainer
w01f’s picture

+1 for an additional active maintainer if they're offering

avpaderno’s picture

As 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.

avpaderno’s picture

Status: Active » Closed (outdated)

I 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.

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.

lisa.rae’s picture

Status: Closed (outdated) » Active
lisa.rae’s picture

I 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.

lisa.rae’s picture

Version: 2.3.x-dev » 3.0.x-dev
longwave’s picture

Project: Flysystem » Drupal.org project ownership
Version: 3.0.x-dev »
Component: Miscellaneous » Maintaining offer
Category: Support request » Task

The 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

avpaderno’s picture

Of 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.

lisa.rae’s picture

Thank you @avpaderno!!!!! Much appreciated!

avpaderno’s picture

avpaderno’s picture

This is the first message I sent.

Hello Vijay,

I am contacting you because Lisa (https://www.drupal.org/u/lisarae) offered to become maintainer for Flysystem (https://www.drupal.org/project/flysystem), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3498284 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Lisa will be probably made maintainer.

I am contacting all the project maintainers, and the project co-maintainers with the "Administer maintainers" permission, who logged in at least once in the past 12 months.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on the offer issue. We need this to know it was intentional and not a misunderstanding on what the offer required.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Active » Postponed

I 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.

lisa.rae’s picture

Thank you @avpaderno!

jungle’s picture

Status: Postponed » Fixed

As 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.

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.

avpaderno’s picture

@jungle Thank you for taking care of this!

lisa.rae’s picture

@avpaderno, @jungle thank you both!

Status: Fixed » Closed (fixed)

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