Problem/Motivation

This module is outdated (currently on Drupal 9) and I would like to help update it to Drupal 10 and eventually Drupal 11.

Comments

sagesolutions created an issue. See original summary.

avpaderno’s picture

@sagesolutions This offer has been kept in the project queue for more than 14 days; if you are still interested in becoming co-maintainer, you can move this issue in the Drupal.org project ownership queue.

sagesolutions’s picture

Project: User Restrictions » Drupal.org project ownership
Version: 2.0.x-dev »
Component: Code » Maintaining offer
avpaderno’s picture

Component: Maintaining offer » Co-maintaining offer
Category: Support request » Task
Status: Active » Postponed

I am going to contact three maintainers (which means who has the Administer maintainers permissions) who logged it at least once in the past year.

avpaderno’s picture

This is the first message I sent; I am still contacting the other maintainers.

Hello catch,

I am contacting you because sagesolutions (https://www.drupal.org/u/sagesolutions) offered to become co-maintainer for User restrictions (https://www.drupal.org/project/user_restrictions), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3511009 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, sagesolutions 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 is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a 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 all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3511009. We need this to know it was intentional and not a misunderstanding on what the offer required.

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

avpaderno’s picture

The status is Postponed because we are waiting for a reply.

Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.

avpaderno’s picture

Assigned: Unassigned » avpaderno

I have contacted all the maintainers who logged in at least once in the past 365 days.

catch’s picture

Project: Drupal.org project ownership » User Restrictions
Version: » 2.0.x-dev
Component: Co-maintaining offer » Miscellaneous
Status: Postponed » Fixed

I haven't been involved with this module since 2008 (!) - I made it solely to enable the same feature to be removed from Drupal core. It looks like there have been no commits from anyone since 2020 so to me it makes sense to accept the offer from @sagesolutions - I've granted you all permissions except for 'administer maintainers'.

Moving back to the project queue and 'fixed' but if that's the wrong place/status feel free to change.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

avpaderno’s picture

Assigned: avpaderno » Unassigned

Status: Fixed » Closed (fixed)

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