Proposal: Version 2.x of the Module for Drupal 11+

I appreciate that others are interested in improving this module. I actually reached out to the maintainer a while back about co-maintainership so I dig that somebody active is interested in taking it further.

That said, this includes work I performed without attribution in Git. Add onto it that the work I did was performed while working for the US Department of Justice who also paid me to perform much of this work... and you really are going to want to make sure the appropriate folks and organizations are getting credit for work performed.

I'd suggest going through the process of this module being recognize as unmaintained and getting maintainership, then merging in my and any others work with proper attribution, and then you can spin off a 2.x with your work or modifications to work performed by myself and/or others.

Hi @jnicola,

Thanks for your message — and first of all, I want to say I completely understand your concerns.

Let me be clear that I absolutely do not intend to take credit for anyone else’s work, and I agree 100% that all contributors and organizations involved — including yourself and the US Department of Justice — should be properly credited and acknowledged. That’s extremely important to me too.

From my side, I worked on a complete refactor of the code to modernize it and make it more in line with current practices. While doing so, I thought it would be a good opportunity to also address the existing issues — including yours — and make a version that benefits the community more broadly. Since I was already touching a large part of the code, it seemed like the right moment to bundle improvements together. But I understand now that the way I submitted this might not have reflected the proper sequence or attribution and I'm sorry about that.

The process you propose makes perfect sense to me. I’ll switch the MR to draft status while we wait for the maintainer’s input and ensure your work is properly integrated with full attribution before building upon it.

If we don't hear back from the maintainer, I’m also totally open to going through the official process to have the module marked as unmaintained.

I’m not seeking to become the maintainer, especially since you've already initiated that discussion. But if you'd like to collaborate, I’d be more than happy to be co-maintainer with you or others. My goal is simply to help and contribute — not to create tension or step on anyone’s toes.

And of course, if my issue or MR is considered inappropriate or premature, I’m totally okay with closing it for now and seeing how things evolve. I just wanted to share what I had done and hopefully make it useful for others.

Looking forward to hearing from you — and thank you again for your transparency and the work you’ve already contributed.

I'm game to co-maintain. It's not as much work as you think.

Let's kick off the official process and go from there. I'll start that here shortly or tomorrow, as work allows :)

I'm actually in the process of moving a whole bunch of custom code from .module hooks into class hooks. I should have time in the near future to review this work as the other issues that have recently been opened. Thanks for the interest and the assistance!

Okay, well that's cool. Since we've got this many interested folks... maybe we can all collaborate?

At the very least I've got some code in here I'd love merged in :) Should be all mergable PR's!