Merge "Comment automatic title" and "Re: Comment subjects" projects

Hello,
I found your module some weeks ago, but it was not doing what I was needing, so I developped comment_auto_title.
That will be a pleasure to work with you and merge our two modules to make a big one that handles many possibilities for comment titles. :)

I read in the description page of your project that it handles several ways of "cutting off"
is there any other feature(s) it brings?

I recently became co-maintainer of comment_subject and we opened a new branch having token support
I see ahoeben was interested on a possible merge of these two modules

should we include this functionality as a new feature for comment_subject?

@ahoeben (startposter and maintainer of the 'other' module: http://drupal.org/project/comment_subject): Good initiative to propose cooperation!

To promote cooperation, I have submitted following here: http://drupal.org/node/915490

---

This is an example of a request which fits both modules:
http://drupal.org/node/915470
http://drupal.org/node/915486

Maintainers of both modules have done great jobs so far. :-)

Drupal guidelines recommend maintainers to join forces (whenever modules offer similar functionality): http://drupal.org/node/23789

Advantages of joining forces:
1) As development effort is focused on ONE module (a SINGLE codebase), solving issues happen faster and (functionality, security and performance wise) better.
2) No incompatibilities can arise between similar enabled modules.
3) Less effort is needed from the maintainer and the rest of the module community (incl. submitting and processing issues and feature requests).

So, please:
A) At least, reference each other's projects on both your project pages and (online) documentation, if you have not done so already and as some responsible maintainers have done in similar cases: http://drupal.org/node/532278
B) Become co-maintainers of each other 's project.
C) Stop adding new features to the newest module and add those features to the oldest module (if they are not already implemented in the oldest module). In the meanwhile, continue fixing new issues in the newest module, until the oldest module offers all the features of the newest (obsolete) module.

I am curious to witness, which maintainer is really the most cooperative. ;-)

Hi,
I added a link to Re: Comment subjects in my module's description, and I have not been working on this module for a long time, I can assure you I won't add any new feature.
If Re: Comment subjects maintainer is willing to enclose any of my code in his module, go for it ! I prefer one full featured module than two.

I also added a link (from the 'other' side)

comment_subject is not getting any new features either
1.x branches have the same functionalities that its author (ahoeben) left
2.x branches got token support (the only "new" feature, and has been there for a while)

if this merge is gonna happen, it should be for D7 (the earlier the better)

so, how is it going to be? (I mean, which one will get patches from the other one?)