Offering to co-maintain File Browser

+1 from me.

In the mean time, the final point of issue queue triage can already start. It would help give this offering more credibility.

The maintainer for this module has been unresponsive for some time and the module is currently in limbo. I would like to be considered as a maintainer so I can ensure this module stays up to date and has a regular release schedule! Thank you for your consideration.

The project link is https://www.drupal.org/project/file_browser → .

samuel.mortenson logged in at least once in the past six months. I will contact him later.

This is the message I sent.

Hello Samuel,

I am contacting you because Darren ( https://www.drupal.org/u/dfisher → ) offered to become co-maintainer for File Entity Browser ( https://www.drupal.org/project/file_browser → ), a project you created for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3535186 📌 Offering to co-maintain File Browser Active 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, Darren will be probably made co-maintainer.

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.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3535186 📌 Offering to co-maintain File Browser Active . 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

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 an action is required for this offer.

+1 on this, we are past the 14 day mark

awaiting this issue to move forward on https://www.drupal.org/project/file_browser/issues/3451080 📌 Automated Drupal 11 compatibility fixes for file_browser Active

+1... project is ready to be handed over to Darren. Appreciate his work on this.

d.fisher needs to post a comment here, saying he is still interested in being co-maintainer of the File Entity Browser module.

Hi. Sorry. I'm away this week but yes very much interested in still becoming a co maintainer on this project! Thank you.

I added d.fisher as co-maintainer.

Thank you!

Hi sorry to come back on this issue. I've been added to the project as a developer (on gitlab) meaning I can't set a 2.x branch as the default and tag a new major release. Due to the changes to make the module Drupal 11 ready we've had to remove support for Drupal 10.2 and below.

Do I need to go through this process again following these instructions:
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... →

Or am I able to get the maintainer status in gitlab via this issue as there is only a single maintainer and he is uncontactable?

Being co-maintainer on the drupal.org side means being developer on the git.drupalcode.org side. That is described in every page listing the permissions given in a project to each co-maintainer/maintainer.

“Write to VCS” grants the GitLab project developer role. Having both “Administer maintainers” and “Write to VCS” grants the GitLab project maintainer role.

Since in this case there is only a single maintainer, who is also project owner and who did not reply back when I contacted him for this issue, I made you maintainer.

Thank you. I understand and will make sure to apply for maintainership if this arises in the future.

Good news everyone. I've been given full maintainer status so we can get this released. Given that the test is so flaky we are considering removing it before doing a full release. I don't like the idea of removing a test but the functionality works and the test is failing due to a known issue with selenium. I'm going to give it today and the weekend to try and get this resolved and if we're still no further progressed on Monday I will go ahead and tag a 2.0 release. Thank you all for your patience!!