Offering to maintain Media Library Extend

Just moving this up since I have tried to contact the owner several times this year and no word/communication has been recieved.

These offers need to be first posted in the project issue queue as per Offering to become a project owner, maintainer, or co-maintainer → and kept in that queue for at least 14 days.

@apaderno

Ok, thanks!

geoanders, in the past you have offered to maintain a lot of abandoned projects.

Since then, you seem to have lost interest in many of them, and have just gone ahead and removed yourself from the project. This is very disruptive, because that leaves the project with nobody with the permission "admininister maintainers", which means that anyone who want to take over maintenance must go through the site moderators to get there. Just jumping ship is not the right way to do this. Instead, you must set the project's maintenance status to "Unsupported" and post an issue saying you are open to offers to become maintainer.

Unless you take the responsibility for managing a clean succession of maintainership for the projects you have offered to maintain, but since have lost interest in, I would have severe doubts before giving you the permission to administer maintainers (including yourself) of any project hosted on Drupal.org.

Then, in the case of maintainership given because a Project available for adoption → issue, we also need to set the issue back to Active.

Yes, I have offered my time to help keep modules going for the community.

I have not lost interest, but lack of time to dedicate to the modules I currently support. I'm simply trying to focus on the modules that I can commit my time to.

That is my misunderstanding of the process and thought it would automatically end up in the queue for ownership. I can certainly help with transitioning those modules that I currently don't have time for or lack thereof.

I have closed those tickets since I either had those fixes already in the repo or was already addressed. The automatic fixes don't always work out as you might already know.

This is probably not the best of places to have this conversation and should probably be done in a private manner.

apaderno, I agree. This is a big mess.

But I am working on it now. Example: https://www.drupal.org/project/breakpoints_ui/issues/3233657 💬 breakpoints_ui project open to new maintainer applications on 30 Sep, 2021 Active

Hello, sorry for chiming in late to this conversation and not reacting to communication earlier. I've been busy with other things and have moved on from this project.

However, I have some former colleagues whom I trust and who also offered to take on maintainership. I hope it's alright with you if I pass the project on to them, and we will make sure there's a drupal 10 release out soon.

Thanks for understanding, and sorry for the quiet period.

@gisle Without your comment, I would not have noticed what you reported. Since it should be taken in consideration when adding maintainers/co-maintainers, a public comment has been the right action to take.

@geoanders What maintainers should be do when they do not have any more time to maintain a project also applies to your case, especially when you have been appointed maintainer following the Project available for adoption procedure. You got maintainer thanks to a procedure that allowed you not to potentially wait for 14 days or more; people who would like to maintain those same projects should benefit for the same procedure.

@Mirroar They just need to comment on this issue. Site moderators will handle the request.

@Mirroar

Thanks for chiming in and glad to hear that this module will get the attention it deserves. It's a handy module and would hate to see it not maintained. Look forward to seeing a D10 release!

Closing out request as maintainer is bringing on another person to maintain the module.

geoanders, you are not a maintainer of this module. Only a maintainer should move an issue to "Fixed". Nobody should manually set the status "Closed (fixed)". I've set it back to "Active".

You clearly do not understand how to work in the issue queues. Please take some time to read our guidelines on Issue Etiquette → .

Considering I opened the issue, I should have the ability to close it. Specially since if someone else decides obtain maintainership, they will need to open their own issue/ticket. Doesn't make sense to me to keep this open any longer, but do what you will with it.

Either way, this issue can be closed by the powers that be.

@geoanders and everbody else, i will look into this module next week, as i have a very urgent customer project, which costs most of my time right now. Luckily, this module is also part of the project, therefore i have an already ported, and tested local port, so i hope to update the contrib aswell. Also further maintenance etc. i would also address next week, so i think comaintenance would be great, we also rely extremly on this module, and more hands solve more work ;-)

I close this issue as i will maintain this module in partnership with mirroar

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