Offering to maintain GNU Terry Pratchett Headers

Email sent to Adam through d.o contact form

Likewise, I am happy to support, as well.

Thanks for the support @AndyD328 I've made you a maintainer

Many thanks Adam. I've got a new tag sitting there with the updates from Gareth in it but I don't have permissions to create new releases. Can you add the 'Administer Releases' permission for me or add the 9.1.0 release to the module?

Many thanks!

And thanks to Gareth for making & testing the patch, it went in & worked without any issues.

I added that permission to you yesterday - could you try again please?

I think I need the Edit permission too as that's where the Releases tab lives. I tried going direct to https://www.drupal.org/node/2454419/edit/releases → and I get a 403.

Reviving this issue as there will likely be more work involved to release a D11 version.

Happy to be added to the maintainers list.

Moving to the Drupal.org project ownership to request taking over the gnu_terry_pratchett module:
https://www.drupal.org/project/gnu_terry_pratchett → .

There are now 2 users willing to keep the module active, but the current maintainer is no longer responding to requests.

There was some movement not long ago, but the correct permissions were not granted to create and edit new releases.

Please could you add the correct permissions to both the_g_bomb and andyd328

Many thanks

Gareth

This is the offer made from AndyD328, which is already handled by adammalone.

Other offers need to be created as new issues, following what reported in Offering to become a project owner, maintainer, or co-maintainer → .

I am moving this issue back to the project queue.

@AndyD328 is correct: Without the permission to edit the project page, it is not possible to access https://www.drupal.org/node/2454419/edit/releases → . That is not the page to create new releases, though. New releases are created on https://www.drupal.org/node/add/project-release/2454419 → , which is a link given in the project page.

In the screenshot, it is the underlined link.

On https://www.drupal.org/node/2454419/edit/releases → , it is possible to select which releases are supported and which are suggested.

Since AndyD328 can administer releases, he could also need to mark a release as supported, or a different one as unsupported. (I guess that it would make sense for him to mark the 9.0.* serie as supported.

Thanks for those pointers Alberto, I've never needed to access the releases/versions that way before.

I've moved this back to the ownership queue as, while I can manage releases, we are not in a position to edit the module page or add other maintainers as and when needed.
As Gareth has said, we'd like to keep this module alive and we really need full ownership to be able to do that over time. Is there a reason we/I shouldn't have ownership at this point?

Since the offer to be maintainer has not been full-filled in six months, I will contact adammalone.

Maintainers have all the permissions on the project; co-maintainers do not have all the permissions on the project. That is the difference we made between maintainers and co-maintainers.
In the case the offer to be maintainer is not accepted, we expect to see a comment explaining why.

This is the message I sent.

Hello Adam,

I am contacting you because Andy offered to become maintainer for GNU Terry Pratchett Headers ( https://www.drupal.org/project/gnu_terry_pratchett → ), 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/3422245 → 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 Andy as 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, Andy will be probably made 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.

As last note: This offer is about being maintainer, which for us means somebody with all the drupal.org permissions on the 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.
Andy has been made co-maintainer, but the offer is to be maintainer, which is not an offer to be project owner. If there is any reason not give Andy all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3422245 → .

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

hey i've just given full permissions to andy - if that doesn't work please do what needs to be done to allow him access. thanks all!

Many thanks Adam!

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