Closed (fixed)
Project:
Drupal.org site moderators
Component:
User account
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
25 Mar 2023 at 01:02 UTC
Updated:
11 Apr 2023 at 20:24 UTC
Jump to comment: Most recent
If I request co-maintainership of a module, I will be able to commit an RTBC patch to dev. Would I also be able to publish a new release?
Comments
Comment #2
avpadernoComment #3
avpadernoIt depends from the permissions given to the co-maintainer, since a co-maintainer is simply a user who does not have all the permissions on the project, which are: Write to VCS, Edit project, Administer maintainers, Maintain issues, and Administer releases.
Write to VCS is the permission that allows to make commits, create branches, and create tags. Administer releases is the permissions that allows to create releases from tags or branches. (In the latter case, the release is a development snapshot.)
Comment #4
xem8vfdh commentedThanks @apaderno.
Is it possible to become a co-maintainer with Administer releases privileges?
I'm specifically wondering about the acl module. It is not Drupal 10 compliant, but I have verified and cleanup patches provided by another community member to make it so: https://www.drupal.org/project/acl/issues/3285916
I do not have the bandwidth to be an admin/owner of the project, but it would be nice if the Drupal 10 patch could be merged and released, since this is a popular package. The primary owner/maintainer @salvis appears absent. He hasn't had any recent activity, hasn't chimed in on this issue, and hasn't responded to any or my contacts through drupal.org or emails to his company's contact address: https://salvisberg.com/contact
Comment #5
xem8vfdh commentedI am not sure if there are other maintainers with commit/release privileges on the project, as drupal.org doesn't make that information transparent. Maybe you can see on your end? If you see other active committers/releasers, I'm happy to contact them as well, but it looks like none of the maintainers are recently active on the project.
Happy to follow any advice you suggest.
Comment #6
gisleDrupal lets any community member examine the individual permssions held by team members by adding
maintainers.jsonto he project's URL.In the case of ACL, the URL to visit is: https://www.drupal.org/project/acl/maintainers.json
As you can see in, this project, only the project owner (salvis) has the permission "Administer releases".
It is certainly possible to become a co-maintainer with "Administer releases privileges. As already pointed out by Apaderno, it depends on the permissions given to the co-maintainer by whoever add them to the team.
There is a recent post by salvis, explaining his absense, see comment #10 in: #3346751: Offering to maintain RoleAssign.
I've noticed that you've posted #3348765: New co-maintainer (and responded).
To move the project forward, you probably need to be added as a co-maintainer yourself, with the necessary permission. To avoid any misunderstanding, I think you should say up front that you want this permission as co-maintainer in your offer to do so. Also, after posting the offer in the project's issue queue, you should send him a PM about your offer. I doubt he monitors the issue queue frequently.
Comment #7
avpadernoYes, it is. Create an issue in the project issue queue, titled Offering to maintain [module name] (replace [module name] with the effective module name) where you offer to become co-maintainer and where you explicitly say you want the permission to create releases too.
Comment #8
xem8vfdh commentedThanks you very much @gisle for pointing me to @salvis' post. I'm sorry to read that but glad he stepped in to explain. I've commented on the maintainership issue, so we can move the discussion there.
And thank you @apaderno for the further clarification.