Closed (won't fix)
Project:
Drupal.org customizations
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2012 at 01:16 UTC
Updated:
21 Aug 2014 at 21:00 UTC
Jump to comment: Most recent
Looks there are patches waiting for review for more than 1 year. IS this module still maintained?
Or could use a co-maintainer?
Comments
Comment #1
quotesbro commentedI am following the instructions for Dealing with unsupported (abandoned) projects:
http://drupal.org/node/251466
I am requesting the maintainership of the Tracker 2 module:
http://drupal.org/project/tracker2
There are few 'reviewed & tested by the community' patches waiting to be committed for 2 years.
I have already tried to contact the module owners a couple of weeks ago via contact form, but they have not replied. So I am moving this issue to the webmasters queue.
I've also started a sandbox project to get familiar with git:
http://drupal.org/sandbox/dberror/1763680
Comment #2
quotesbro commentedComment #3
dwwI'm not sure what to say. Tracker2 is used by d.o. It was originally written by David Strauss and developed enough to work and deploy. The primary functionality of it was already merged into D7 core's tracker.module. So, it's basically at end-of-life.
I was added as a co-maintainer for a couple of issues we needed for d.o:
#404084: Add support for tracking flagged nodes
#928110: Expose tracker2 tables and columns to views
I don't feel like I "own" tracker2 enough to grant new co-maintainers, but David is historically hard to get in touch with for things like this.
Given that this is deployed on d.o, I think we need a high standard for potential maintainers in terms of performance and security consciousness, etc. No offense intended at all, but your profile page doesn't show much history of other modules you've maintained. Your contributions to the tracker2 issue queue don't include a lot of code, and you've RTBC'ed two issues without a substantive review, so it's hard to know how thorough and careful you're going to be. We definitely don't want #1046406: Unsubscribe deployed on d.o since it would conflict with the flag + tracker2 integration stuff we use for following issues. So, I'm reluctant to grant this request...
Then again, maybe if you just made a new 6.x-2.x branch to do whatever you wanted, and d.o stayed on 6.x-1.x, it wouldn't be a problem. You're offering to help, and I certainly don't want to discourage your desire to contribute.
As I said, I'm not sure what to do with this. ;)
However, I wanted to move it to the infrastructure queue so that the rest of the infra team could weigh in. We're collectively responsible for keeping d.o up and running well, and this module is (at least until the D7 launch) a critical piece of code to keep d.o alive.
Thanks,
-Derek
Comment #4
quotesbro commentedThanks for the detailed response, Derek.
Honestly, I didn't know that Tracker 2 is still being used on drupal.org. In this case, I am definitely not ready to maintain this module.
I've already patched it few times for my own needs, so I personally do not need new releases, but maybe someone else does. Then, maybe you could just commit #693366: Remove tracker data for the user being deleted (if you think that it should be commited).