Module Maintenance Status

You're really better off trying out the comment_notify module, which is being actively maintained and was based of the code of this module.

Ah! Well...I feel stupid. :) We need the module 'badlands' for this module. :)

1 month ... nor breath nor motion

Yes we are still supporting this module. Sorry about the lapses. We will be working on the issues and post updates asap.

zyxware, you should really consider merging with Comment Notify. There's no need to duplicate modules and I think any features you have that Comment Notify does could easily be added. See http://groups.drupal.org/duplicated-modules-hall-shame for more info.

This module was started as an entirely different concept of subscribing to individual comments as opposed to notifications for all comments like comment_notify was doing originally. We created this module because we needed something like this to do our job and we contributed to it back to the community. Now comment_notify was not being maintained and we went on adding features to comment_subscribe. Yes comment notify was taken up later by greggles and both the modules have similar functionalities currently. I don't quite understand why comment_notify deserved to be taken up by greggles instead of comment_subscribe as comment_subscribe had more features than comment_notify and comment_notify was not being maintained. Yes I accept that there were lapses in the support but we are back on track. We are open to how we can work together with comment_notify especially given the fact that it is going to be in core. But there are lot of users who are using comment_subscribe and they will need support. So how is that going to work out if the projects are going to be merged?

I'm proposing that comment_notify be the module to be merged into for the following reasons:
1. comment_notify was the first project. It started in December 27, 2006 while comment_subscribe started on February 20, 2008.
2. Since your module was created later and started the majority of it's code based on comment_notify, you probably could have easily filed a feature request patch against comment_notify for your different method of subscribing to comments. I did a search through every single comment_notify issue, and unless you used a different Drupal.org username, you did not participate or submit any issues. You just went and created your module anyway, which is not the recommended way to help contribute back if there is a very similar, existing module.
3. If the module was not being properly maintained, you could have applied to take over as a maintainer as per the policies specified in the "Dealing with abandoned modules" handbook page instead of starting a very similar module.
4. Currently, comment_subscribe has 700 6.x and 161 5.x reported users while comment_notify has 964 6.x and 379 5.x reported users. Is it going to be easier to move 861 users or 1,343 users to a different module? All signs would point towards the former. It's fairly easy to move users to a different module. You'd have to work together with the greggles to create one update function inside in comment_notify_install() that would upgrade users/data from comment_subscribe. Then basically turn off all releases on your project page, turn off the issue queues, and make a nice big link on the project page saying the modules have been merged. I had to do this for one of my own modules.

Anyway, that's my arguments for merging back into comment_notify.

It has been decided to merge Comment Subscribe module with the Comment Notify module as both currently have the same set of functionalities. We have stopped our support here and will be providing our support at the Comment Notify issue queue. To help you seamlessly migrate to Comment Notify, we have provided an easy migration pathway using the last update - 6.x-1.4. Migration instructions are provided at the Comment Subscribe project home page . Once again thank you all for your wonderful support and contributions towards this module. See you all at the Comment Notify issue queue :-)