Problem/Motivation

Looking at issues like

and the many RTBC'd issues, the maintainer seems to be inactive.

Also the Co-maintainer added in #3241508: Offering to co-maintain Auto Purge Users doesn't seem to be set anymore.
So I'd like to offer my and @Grevil's help as maintainers. We're using this module and are thereby interested in keeping it safe.

As written in #3289193: Automated Drupal 10 compatibility fixes I already wrote jim.applebee a PM but got no reply.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

Anybody created an issue. See original summary.

anybody’s picture

@apaderno would you also try to contact the maintainer?

avpaderno’s picture

I will contact the required maintainers, but the issue must first choose between maintainer or co-maintainer.

anybody’s picture

Title: Offering to (Co-)Maintain Auto Purge Users » Offering to Maintain Auto Purge Users

@apaderno let's go with "Maintain", I think it's the safer way for the module's future.

avpaderno’s picture

Title: Offering to Maintain Auto Purge Users » Offering to maintain Auto Purge Users
Category: Task » Support request
Status: Active » Postponed

This is the message I sent to jim.applebee.

Hello Jim,

I am contacting you because Julian (https://www.drupal.org/u/anybody) offered to maintain Auto Purge Users (https://www.drupal.org/project/purge_users), a project you created, for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/purge_users/issues/3358461 about accepting or declining the offer? Without a publicly visible comment posted in that issue in the next 14 days, Julian will be probably made maintainer (user with all the permissions on the project).
None of the current co-maintainers/maintainers will be removed from site moderators, nor will the project owner be changed. A maintainer cannot change the project owner.

I am contacting all people with the explicit permission to administer co-maintainers/maintainers for that project. In this case, that is just you.

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

I am changing status, since we are waiting for a reply.

jim.applebee’s picture

I have added Er.Sajal as a co-maintainer - he will handle the upgrades.

jim.applebee’s picture

Status: Postponed » Closed (won't fix)
anybody’s picture

Hi @jim.applebee thank you for the reply. May I kindly ask, why you decided against accepting my offer to help as (co-)maintainer? Would just be interesting to know. I'm fine with anything, would just be sad to see the module dying ;)

jim.applebee’s picture

ok, I added you as well. Thank you.

anybody’s picture

Status: Closed (won't fix) » Fixed

Thank you @jim.applebee! I'll care for the issues very soon.

anybody’s picture

@jim.applebee sorry one last point: Could you please set 4.x as default branch (has to be done in gitlab > settings now) as I don't have the permissions to do that.

Currently 8.x-2.x is the default, that's quite dangerous. Thanks!
With 4.x based on 8.x-3.x we're switching to semVer for Drupal 10.

avpaderno’s picture

@Anybody You should be able to change the default branch from https://git.drupalcode.org/project/purge_users/-/settings/repository. Click on Expand to the right of Branch defaults.)
I can change the default branch even on projects where I cannot administer co-maintainers/maintainers.

anybody’s picture

@apaderno: Sadly not. I can see that page in other repositories, where I'm Maintainer, but not where I'm Co-Maintainer!
https://git.drupalcode.org/project/purge_users/-/settings/repository returns a 404 for me!

Is this a bug perhaps for Drupal Gitlab? Or should there be a separate maintainer permission for that?

@jim.applebee if possible, could you also add my teammate @Grevil as Co-Maintainer? He'd also like to help with his outstanding Drupal experience.

avpaderno’s picture

Nevermind, I was looking to a project where I am maintainer, not co-maintainer. Where I am co-maintainer, I do not see the Gitlab Settings link for that project. I apologize.

anybody’s picture

@jim.applebee sorry so I have to ping you hopefully for the last time. See #13 Thanks!

(Alternatively try to grant maintainer permissions to me, if you'd prefer that)

anybody’s picture

grevil’s picture

Version: 8.x-3.x-dev » 4.x-dev

@Er.Sajal seems to be inactive (atleast for this module), as he wasn't credited for any issues related to this module. #13 would be quite important, as 4.x introduces important batch deletion fixes!

Status: Fixed » Closed (fixed)

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