Offering to co-maintain Asset Injector

Hi, any maintainer feedback? :)
Would be great!

I wrote @pookmish one week ago without a reply. As we pushed a lot of issues and features forward in the last weeks and also helped to improve the module long-term, I'd like to refresh my offer to become co-maintainer.

Moving this to the Project Ownership issues for that reason. Thank you.

Only pookmish can add/remove co-maintainers. Since he logged in at least once this week, I am going to contact him.

This is the message I used.

Hello Mike,

I am contacting you because Julian ( https://www.drupal.org/u/anybody → ) offered to become co-maintainer for Asset Injector ( https://www.drupal.org/project/asset_injector → ), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3452223 → about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue. In the case you accept the offer, you can also add Julian as co-maintainer, but it is not necessary as project moderators can add co-maintainers/maintainers to any project.
Without a comment posted on that issue in the next 14 days, Julian 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.

A last note: This offer is about being co-maintainer, which for us means somebody who does not have all the drupal.org permissions on the project. Even though that 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.

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

The status has been changed because we are waiting for a reply.

Hi @anybody,

I appreciate the assistance in the queues. I've been keeping an eye on anything that looks urgent. Besides the assets:// wrapper, I haven't seen much that has provoked me to jump in. There are some great discussions and work in those issue queues, but for now, I would prefer to keep a close eye on it and avoid additional maintenance burdens. I have some thoughts about refactoring the module into a bundle entity type and possibly allowing content storage along side config storage.

Please continue to contribute through the issue queues and I'm happy to revisit the request at a later date.

Thanks.

Hi @pookmish of course I'm a bit sad, but thank you for your reply. Happy to eventually become maintainer one day.
What shall we do with this request then?

Thank you!

Yeah, I wasn't sure if this issue should be closed or postponed, or what.