Offering to maintain Required API

Created on 4 December 2024, 23 days ago

Problem/Motivation

I would like to become a co-maintainer of the Required API module to add Drupal 11 compatibility along with any appropriate RTBC issues and create a D11-compatible release.

You can view my profile to see my history of work.

Proposed resolution

Review my profile and, if approved, add me as maintainer with appropriate permissions to merge code, manage issues, and create releases.

Remaining tasks

Add DieterHolvoet as co-maintainer of Required API.

💬 Support request
Status

Active

Version

2.0

Component

Miscellaneous

Created by

🇧🇪Belgium dieterholvoet Brussels

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

Comments & Activities

  • Issue created by @dieterholvoet
  • 🇧🇪Belgium dieterholvoet Brussels

    I sent the following message to @duaelfr, the only maintainer who's been active in the past years:

    Hi,

    Could you post a comment on my offer to co-maintain Required API ( https://www.drupal.org/project/required_api/issues/3491568 💬 Offering to maintain Required API Active )? I would like to become a co-maintainer of the module to add Drupal 11 compatibility along with any appropriate RTBC issues and create a D11-compatible release.

    Thanks in advance,
    Dieter Holvoet

  • 🇫🇷France duaelfr Montpellier, France

    Hi Dieter!
    Thank you for stepping up and offering to maintain this module.
    As a package, would you also want to maintain the Required by role module? ;)

  • 🇧🇪Belgium dieterholvoet Brussels

    Yes, that's alright. That's going to make it easier to keep the two compatible and in sync.

  • 🇫🇷France duaelfr Montpellier, France

    There you go!
    Thank you for your involvement!

  • 🇧🇪Belgium dieterholvoet Brussels

    You're welcome! One question, I won't be maintaining the Drupal 7 version of the module since I have never even touched a Drupal 7 installation in my career as web developer. I noticed the Required by role module has a lot of open D7 issues. Would you be okay with me closing these as won't fix and marking the D7 release as unsupported? Or do we actually have a maintainer who at some point will step up and fix these issues? Most of these haven't been touched in 5+ years.

  • 🇫🇷France duaelfr Montpellier, France

    I don't think anyone is ever going to fix these issues but I'd keep them until D7 official EOL because someone might want to get a patch from them and might not think to search in closed issues. Marking the D7 release as unsupported is totally okay, though.

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

Production build 0.71.5 2024