Offering to co-maintain RNG Contact

Created on 15 January 2024, 11 months ago
Updated 18 September 2024, 3 months ago

I'm offering to co-maintain this project as we use it on one of our sites and want to see this project well maintained.

Unless this project is unsupported because it was deprecated for an other module? But I see no such documentation on the project page.

💬 Support request
Status

Active

Version

1.0

Component

Miscellaneous

Created by

🇧🇪Belgium jelle_s Antwerp, Belgium

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

Comments & Activities

  • Issue created by @jelle_s
  • 🇧🇪Belgium Jonasanne

    Just checking in for an update.
    Also, I'm happy to help out with co-maintaining if needed.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • Assigned to apaderno
  • Status changed to Postponed 3 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I apologize for being late in handling this offer. There are two maintainers who logged in at least once in the past seven days. I am going to contact them.

    (To make it clearer: This issue has been moved in this queue the same day josanne created #3458289: Offering to co-maintain rng_contact → , a duplicate of this issue.)

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    This is the message I sent to dpi.

    Hello dpi,

    I am contacting you because Jonas ( https://www.drupal.org/u/jonasanne → ) offered to become co-maintainer for RNG Contact ( https://www.drupal.org/project/rng_contact → ), 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/3414729 → 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 Jonas as co-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, Jonas 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 for us means somebody who does not have all the drupal.org permissions on the 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 Jonas all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3414729 → .

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

    The status has been changed 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.

  • 🇺🇸United States markie Albuquerque, NM

    Please feel free to update the issue that is open or if you have another issue, starting a new one. There's not a lot of movement in the queue and I feel we have enough maintainers.

  • 🇦🇺Australia dpi Perth, Australia

    @freelock and @megachriz, maintainers of the RNG → project, are effectively the stewards of this ecosystem last time I checked.

    I no longer manage these projects at all. I'd suggest forwarding requests to them.

    In fact, if/when maintainership shifts with this issue, I'd prefer to be removed entirely from them.

  • Status changed to Needs work 3 months ago
  • 🇦🇺Australia dpi Perth, Australia
  • Issue was unassigned.
  • Status changed to Active 3 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Neither frelock nor megachriz has the Administer maintainers permission; only people who have that permission will be contacted.

    Anyway, markie, who has that permission, already replied. This is now an issue for the project maintainers.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇺🇸United States markie Albuquerque, NM

    @dpi you can turn off notifications but since you created them, we can't remove you from the modules. I believe you can transfer ownership, but not sure of the process for that.

  • 🇧🇪Belgium jelle_s Antwerp, Belgium

    @markie If this project is still actively maintained, could you mark one of the branches as supported? Our update status marks this module as unsupported right now

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    All the releases are marked unsupported because they require a Drupal version that is no longer supported. To be marked supported, they should require at least Drupal 10.

  • 🇺🇸United States markie Albuquerque, NM

    Just pushed a release for D10 support. Should be built in a few. Closing this issue.

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

Production build 0.71.5 2024