Offering to co-maintain Support Ticketing System

Have you tried to contact the project owner?

This shows the steps you need to take to get co-maintainership. It would be great to get this project up-to-date!

I do apologize for my lack of commits of late. I appreciate your interest, however; the support module is quite core to our consulting business and billing cycles, and as such I've not currently looking for another maintainer for the code.

FWIW: I'm trying to schedule time this fall (DrupalCon Prague and beyond) to resume development work on this and my other projects.

I think it would be very helpful to have another maintainer to help move this project forward.

Definitely interested in seeing movement.

Any update on either continuing development or bringing on co-maintainers? If the project isn't available to be co-maintained it might need some changes. It likely shouldn't have a stable release for D7 there are quite a few outstanding issues such as https://drupal.org/node/1379178 that break core functionality.

Hello,
I'm really interested!
I'm not a programmer, just a simple webmaster, but if you take the module and try to fix some issues it is really great.
a great thank you from now!
ù

Also very interested in moving forward with this project.

We've made internal changes out of necessity. To the point now where integration with any upcoming module update would be almost as much work as a forked project.

Very interesting in what you see as a roadmap. Further integrating existing outside modules and changes in core (views, notifications, cck, and entities are some specific examples) are very important in order to take this project to the next level.

I'll contact you so we can discuss, as I am very interested in collaboration.

Thank you!

Wouldn't it be better to combine efforts into a single module?

I appreciate your interest, however; the support module is quite core to our consulting business and billing cycles, and as such I've not currently looking for another maintainer for the code.

This is bad for a module with (a lot of issue and) no-update (still in RC) for the last 17+ months...
Up for the Fork.

I Would also like to have something to work with. Sounds like current maintainer should give the support project to the community instead of keeping it hijacked.

Alternatively, I will support a fork if needed so that this project can move forward.

DruSu is a fork of this module (as stated in the main page of the module).

If Jeremy won't accept comaintainers, forking would be the best way to do it. There are patches several years old, lying around in these issues. :( And the project is actually marked "Seeking Co-Maintainers"...?

It looks like there is already a fork initiated at drusu. I am looking forward to seeing how that goes.

I am closing this issue, as there haven't been follow-up actions as per Taking over unsupported (abandoned) projects (which isn't just about unsupported or abandoned projects).