Request to become co-maintainer

Have you contacted the maintainers directly?

Marked #2951419: Please add me to the co-maintainer(s) module. as a duplicate of this issue.

As there's been no response to issues from the maintainers, please follow Dealing with unsupported (abandoned) projects.

See #2032001-41: Content Access Drupal 8 port:

I did not have much time for maintaining the project during the last years and unfortunately id.tarzanych seems inactive as well. Anyone who would like to step up and help maintaining would be welcome! Please contact me via my contact form if you are up for getting involved!

Hi sathish.redcrackle,
and I happy to hear you're interested in joining this important project as a co-maintainer.

I am actively looking for co-maintainers. However, I would like to see some of your code first. If you still are interested, pick any issue in this project that requires code to be written and submit a patch. I promise that I'll review it. If your code is good, I'll sign you up.

Please also state whether you are git vetted (aks. allowed to opt into security coverage). I am not going to reject those that are not vetted, but I'll do a more thorough review. That will benefit us both.

Postponing until there is a patch to review.

What is the plan (date) for creating a new "release" version of those module and not just "dev" builds?

What is the plan (date) for creating a new "release" version of those module and not just "dev" builds?

Currently no plan. This is unpaid work, so it is impossible for me to commit to a schedule. I do it in my spare time.

If somebody is willing to sponsor the renovation of this project, I shall be able to commit to a firm time of delivery.
Cost would be US $1500 (paid in advance via PayPal or bank transfer), and promised time of delivery would be one week after payment is received. The release will be a full release (not just alpha or beta), and it will have security coverage.

Main blocker is security issues in both branches, but the integration with ACL is currently broken and need fixing as well before I can make a release.

Can we add the person offering to co-maintain? Maybe that could help us move forward.

Can we add the person offering to co-maintain? Maybe that could help us move forward.

xeM8VfDh, please see comment #4.

I've already offered to add this person as a co-maintainer. However, he hasn't replied to the offer. Since the offer was posted in 2017, but was not responded to until May 2020 (when I became the project's maintainer) I am not surprised. It is very likely that he has moved on, found other solutions, and simply no longer is interested in this project.

Also note that everybody (including sathish.redcrackle) can help move this forward instantly without being first promoted to co-maintainer. They can do this simply by writing and/or reviewing patches. If you look at the recently fixed issues, you'll see that this happens very quickly with this project, and also that issue credit is always given to those who help.

If a project is actively maintained (and this project now is), my experience is that adding an additional maintainer does not help a project move forward, unless the new maintainer is already engaged with in the project and shows an interest in working in the project's issue queue as a coder and/or reviewer. That is why I don't add co-maintainers if they don't show engagement.

But thank you for reminding me about this. Since more than three months has passed since co-maintainership was offered, it is time to close.

Removed legacy related issue.