Offer to co-maintain

Created on 13 May 2023, almost 2 years ago

I would like to offer to co-maintain this module as part of the #d10readiness initiative.

My plan would be to:

Check all RTBC issues and merge if appropriate
Work on 📌 Automated Drupal 10 compatibility fixes Needs review with other contributers until it is ready, then merge
Tag a d10-compatible release
Continue doing reviews of RTBC issues and merging/releasing as appropriate.

I am the maintiner of a few other popular projects including token_filter and collapsiblock.

📌 Task
Status

Active

Version

4.0

Component

Miscellaneous

Created by

🇦🇺Australia darvanen Sydney, Australia

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

Comments & Activities

  • Issue created by @darvanen
  • 🇦🇺Australia darvanen Sydney, Australia

    I have just now contacted the original owner of this project, along with all three contributors who have 'maintainer' status in gitlab:

  • 🇦🇺Australia darvanen Sydney, Australia
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇦🇺Australia darvanen Sydney, Australia

    Thanks @apaderno, I admit I forgot to check the instructions for opening these.

  • Status changed to Postponed: needs info almost 2 years ago
  • 🇺🇸United States rocketeerbkw Austin, Tx

    Is it just to commit D10 fixes or long term? We already got a new maintainer → , so I'm just a little hesitant to ignore this issue de-facto approve you.

    I'll be at DrupalCon, I can commit to getting D10 issues resolved in the short term.

  • 🇦🇺Australia darvanen Sydney, Australia

    Hey all good, there just hadn't been much activity for 6 months or so so I put my hand up. VERY happy to step back ;)

    The primary purpose was to make this D10-ready, yes, but I would have given it the same care I give token_filter, which is to triage the issue queue and engage with issues that make it to RTBC or sometimes NR.

  • Status changed to Active 12 months ago
  • 🇦🇺Australia darvanen Sydney, Australia

    Hi @rocketeerbkw,

    Wondering if you've had any more thoughts about this? The offer still stands, especially since the Drupal 8+ version has now disappeared from the module home page.

  • 🇦🇺Australia darvanen Sydney, Australia

    Reviving this as there hasn't been any movement on compatibility in over a year.

    Updating to an offer to maintain rather than co-maintain as I've discovered it can be difficult to do some things as a co-maintainer, like set the default branch for issues, which quickly gets annoying.

    I'll start the process from scratch by contacting @rocketeerbkw via the contact form :)

  • 🇦🇺Australia darvanen Sydney, Australia

    I have had no response from Rocketeer and I would like to bring this module up to speed.

    I am not only offering to commit the Drupal 10/11 compatibility, I can commit to:

    • triaging the issue queue
    • managing issues which reach RTBC status
    • keeping the module compatible with the current versions of Drupal

    for the foreseeable future.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    This is the message I sent to rocketeerbkw.

    Hello Brandon,

    I am contacting you because Max ( https://www.drupal.org/u/darvanen → ) offered to become maintainer for Restrict Login or Role Access by IP Address ( https://www.drupal.org/project/restrict_by_ip → ), a project for which you are project owner and maintainer.

    May you post a comment on https://www.drupal.org/project/projectownership/issues/3360174 💬 Offering to maintain Restrict Login or Role Access by IP Address 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, Max will be probably made maintainer.

    You have already commented on that issue, but that comment was posted a year ago. After that, there have not been further replies.

    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.

    As last note: This offer is about being maintainer, which for us means somebody with all the drupal.org permissions on the project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.

    I am contacting all the people who can administer co-maintainers/maintainers for the project.

    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.

  • Assigned to apaderno
  • Status changed to Postponed 12 days ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    @darvanen Are you still interested in becoming maintainer of this project?

  • 🇦🇺Australia darvanen Sydney, Australia

    @apaderno yes, happy to become caretaker and carry out the tasks I outlined earlier, thanks.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I added darvanen as maintainer.

Production build 0.71.5 2024