Offerer to co-maintain Password Separate form

Created on 21 July 2025, about 2 months ago

I am interested in co-maintaining the Password Separate form module.
https://www.drupal.org/project/change_pwd_page โ†’

https://www.drupal.org/u/bluegeek9 โ†’

The module has not had a release in a couple of years and does not support Drupal 11. I am interested in fixing bugs and making a Drupal 11 release.

I have created these issues:
๐Ÿ“Œ gitlab ci pipeline Active

I have reviewed these issues:
๐Ÿ“Œ Update README.md file according to "README.md template" Active
๐Ÿ“Œ Drupal 11 compatibility fixes for Password Separate Form Active
๐Ÿ› When an admin changes another user's password, the status message is incorrect. Active
๐Ÿ› PHP 8.4 Implicitly marking parameter as nullable is deprecated Active

๐Ÿ“Œ Task
Status

Active

Version

2.0

Component

Miscellaneous

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States bluegeek9

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @bluegeek9
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States bluegeek9

    I contact Gaurav Pahuja, asking to be a co-maintainer.

    https://www.drupal.org/u/gauravpahuja โ†’

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States bluegeek9
  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น

    Only one of the people with the Administer maintainers permissions logged in at least once in the past six months. I am going to contact him.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น
  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น

    Hello Pushpinder,

    I am contacting you because Steven ( https://www.drupal.org/u/bluegeek9 โ†’ ) offered to become co-maintainer for Password Separate Form ( https://www.drupal.org/project/change_pwd_page โ†’ ), a project for which you are maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3537250 ๐Ÿ“Œ Offerer to co-maintain Password Separate form Active 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, Steven 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/3537250 ๐Ÿ“Œ Offerer to co-maintain Password Separate form Active . 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

    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.

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada er.pushpinderrana Vancouver

    Hi Alberto,

    Thank you for reaching out. I accept Stevenโ€™s offer to become co-maintainer for the Password Separate Form project and agree to provide the standard co-maintainer permissions (Write to VCS, Edit project, Maintain issues, Administer releases).

    Best,
    Pushpinder

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024