The Dart project doesn't seem to be very active. You can take it over rather than making a duplicate and appending 2 on the end of the name.
Appending a 2 is very confusing to end users who are evaluating which module to use. If the other is abandoned, take it over (this seems to be the case). If it's still active, you should ask to be co-maintainer or how to collaborate with them rather than creating a duplicate. I don't see a single issue from you in the queue for the doubleclick module, which is a sign you didn't try to collaborate.
Comments
Comment #1
gregglesComment #2
nicksanta commentedHi Greggles,
I'm not totally 100% sure of the situation, but apparently the current "maintainer" of drupal.org/project/doubleclick is a douche and doesn't want any more active development of it, and also refuses to add new maintainers.
This is a direct fork made by the original developers (o-minds) and now I have CVS access to it as I did quite a bit of development earlier this year.
I don't think DART and this code base are compatible in their approaches.
I understand the problems with confusing users with multiple modules claiming to do the same thing, but this (as it states on the project page) is the successor to doubleclick.module, and will probably be the most supported one going forward.
Cheers for taking the time to address this issue,
Nick
Comment #3
gregglesWell, it's been 2 weeks since you filed this which means you can take over the module via the abandoned module process.
The current maintainer has never made a commit, so it should be no problem to get it transferred to ominds/nicksanta/whomever you want.
Comment #4
bleen commentedJust to chime in ... the DART module is very much active and maintained (by me).
When the first doubleclick module was created and I discussed merging with the maintainer then ... the approaches really were quite different and merging wasn't practical.
Comment #5
bleen commented...also, I'm confused as it seems that you (nicksanta) are now the maintainer of the doubleclick module. Will you continue development here or there?
Comment #6
nicksanta commentedVery good point. I will attempt to take ownership of the doubleclick module, and that way the politics between jeeran (current doubleclick "maintainer") and o-minds will not be an issue.
@o-minds and @waleedq, i'll add you guys on as maintainers if that is your wish, but out of interest, do you have any plans to further development of the module?
http://drupal.org/node/924842#comment-3575370
Comment #7
nicksanta commentedComment #8
avpadernoFYI, I made nicksanta maintainer of http://drupal.org/project/doubleclick. jeeran, who has been made maintainer of the project upon request by ominds, doesn't have a CVS account; therefore, I removed him as co-maintainer of the project.
Comment #9
nicksanta commentedThis has been done. Included in the new release are a few bug fixes that were never committed to doubleclick2: http://drupal.org/node/944426
Comment #10
gregglesAwesome - thanks nicksanta and ominds.
Now, how about we delete the doubleclick2 project page (I can do that if you agree).
Comment #11
nicksanta commentedYep, go for it greggles.
Comment #12
Ashraf Amayreh commentedFine by me. Nicksanta, please add ominds and waleedq as co-maintainers. We will help with the port to Drupal 7 (when it is released) and with the issue queue.
There's another user who expressed interest in doing some token integration, I'll let you know what his username is when I contact him.
As for Jeeran, when they fuss about this to me, I'll tell them that nicksanta filed a request to an abandoned module and won it. Greggles, feel free to delete this module.
Comment #13
gregglesAwesome, thanks guys. I'm moving this issue to the doubleclick queue so it doesn't get lost.
Comment #14
nicksanta commented@ominds: You can direct Jeeran to my user page where he can contact me if he has any issues. Me becoming the new project owner of doubleclick was not prompted by you, and thus you shouldn't have to do any explaining to him.