Offering to co-maintain ACL

Created on 6 April 2023, almost 2 years ago
Updated 27 June 2023, over 1 year ago

There are a number of RTBC issues that should be merged and included in a new release to make this module Drupal 10 compliant and address a block in content_access development:

RTBC:
https://www.drupal.org/project/acl/issues/3285916 📌 Automated Drupal 10 compatibility fixes Fixed
https://www.drupal.org/project/acl/issues/3193968 📌 Replace all the occurrence of assertEqual() method, that is deprecated. Fixed (change set included in latest patch on issue above)
https://www.drupal.org/project/acl/issues/3324285 🐛 [PHP 8.1] Deprecated function: mb_strlen(): Passing null to parameter #1 Fixed (blocker for https://www.drupal.org/project/content_access/issues/3258804#comment-148... 🐛 [PHP 8.1] Deprecated function: unserialize(): Passing null to parameter #1 Fixed )

The maintainers of this module have not responded to repeated contact attempts both on drupal.org and externally through their publicly listed email addressed.

I would like to offer to co-maintain the module for the purpose of merging these RTBC issues and publishing a new release that will be Drupal 10 compliant, and which will allow content_access to continue development.

I do not have the bandwidth to be an active maintainer on this project, but do have the time to commit to the task outlines above.

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

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

Comments & Activities

  • Issue created by @xem8vfdh
  • 🇳🇴Norway gisle Norway

    According to maintainers.json , you've been added as a co-maintainer with the following permissions:

    name	"xeM8VfDh"
    permissions {
      update project "1"
      administer maintainers "0"
      write to vcs "0"
      maintain issues "1"
      administer releases "0"
    }
    

    IMHO, without the permissions "write to vcs" and "administer releases", there is unfortunately where little you can do to move the project forwards towards a stable release.

    It looks like @salvis could do with some help. If he doesn't have the capacity himself, he should let co-maintainers have those permissions.

  • I don't entirely disagree.

    I am not sincerely interested in maintaining the project beyond getting an official D10 release out (ideally ASAP), but I could potentially have time to contribute to maintenance/bug fixes only. I think the project is relatively mature and is already in a bug-fix-only mode. @salvis has resurfaced recently and been active in assisting me with resolving and commiting various issues, though he has been silent the past few days. He also suggested here 📌 Automated Drupal 10 compatibility fixes Fixed he won't be around for very long, implying he's he to get the module in order for a new release.

    @salvis, what do you think of all of this? Can we commit to a new D10 release in the near future?

  • 🇨🇭Switzerland salvis

    @salvis, what do you think of all of this? Can we commit to a new D10 release in the near future?

    Yes, we'll get this done. Thank you for all your help in the issues queue, xeM8VfDh!

  • @salvis, sounds good

    If there is anything I can do further to expedite the release of a D10 version, please let me know

  • @salvis, where are we on this?

Production build 0.71.5 2024