Offering to co-maintain Limited Widgets For Unlimited Fields

Current maintainer does not have a contact tab so could not reach out.

I contacted the project owner (and sole maintainer). This is the message I sent.

Hello Oleksandr,

I am contacting you because Stephen ( https://www.drupal.org/u/smustgrave → ) offered to become co-maintainer for Limited Widgets For Unlimited Fields ( https://www.drupal.org/project/limited_field_widgets → ), a project you created for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/limited_field_widgets/issues/3468707 💬 Offering to co-maintain Limited Widgets For Unlimited Fields Postponed 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 Stephen as co-maintainer, but this 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, Stephen 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 for us means somebody who does not have all the drupal.org permissions on the 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 Stephen all those permissions, please explain that on https://www.drupal.org/project/limited_field_widgets/issues/3468707 💬 Offering to co-maintain Limited Widgets For Unlimited Fields Postponed .

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

I am changing status, since we are waiting for a reply.
Please post a comment, after 14 days, if stomusic has not commented here to decline the offer.

The issue has been left in the project issue queue for more than 14 days. I am moving it to the Drupal.org project ownership queue. stomusic received a link to this issue, so he can find it even if I move it in another queue.

Hi guys, I'm really sorry that I've missed this issue notification and you need wait for my answer so long. I've updated maintainers list, check please

No worries at all!

smustgrave does not have the Edit project permission, which is one of the permissions I listed in the message I sent. That is fine, but we need a confirmation it was done on purpose, and not a forgetfulness.

Just to make it clearer: The Edit project permission is necessary not only to edit the project page, but also to access https://www.drupal.org/node/2987154/edit/releases → , which is the page that allows to set a new release as supported or suggested.
Being able to create a new release is useless, without the possibility to set the new release as supported.

Never mind: People with the permission to administer releases see an Administer releases link on the project page. It is not necessary to have the permission to edit the project page.
I apologize: I forgot that detail. (I see the Administer releases link for every project, but I wrongly remembered it took to a different page.)

Since smustgrave can fully administer releases, I am closing this issue as fixed.

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