Is Casetracker still being maintained?

subscribing...

+1

Subscribing

I recently researched this for association.drupal.org's upgrade, which I might blog about in a few days. I decided to migrate to regular node content with taxonomy, views and comment_alter_taxonomy because our needs are simple. This solution may be interim as our needs change (upcoming elections).

http://drupal.org/project/jobtrack was recommended and is under active development, but I did not choose it because it is still in beta and our needs are simple.

And of course, there's always Project issue tracking. ;) Freshly available for 6.x and fully integrated with views... and, you'll never have to worry about it being abandoned, since it's what d.o itself depends on.

As a one-time maintainer of Case Tracker, I agree with dww: CT should die.

So right that in bold letters on project page and close issue?

Dang, and I just started using it. Are there any scripts to migrate to the other projects?

Boombatower: I have nothing to do with CT anymore; would be improper for me to do so.

jjrosent: did you contact the current maintainer? Do you have a cvs account?

Just and FYI, There is an ongoing discussion about two proposed solutions (with patches) in #223187: Drupal 6 Compatibility.

I've also been trying to contact the casetracker maintainer, to no avail. I'm maintaining a Drupal 6 branch for internal use at my company, I'd much prefer I wasn't doing so privately, so if the project is abandoned would be willing to pick up maintainership.

Well, whoever wants to maintain casetracker should apply for a cvs account and link back to this issue in the application. Then update this issue so the project can be signed over to you.

My cvs account is "jmiccolis". Thanks.

done.

I and my coworker have been fixing bugs for CaseTracker module. We'd like to commit many patches, which have been tested and reviewed in the queue, if no one else is committing them.

I have tried to contact @febbraro via Issue queue http://drupal.org/node/678838#comment-7197126, via Twitter https://twitter.com/skyredwang/status/314239417386680320, via Phase2 Contact form (@febbraro's contact form is not available on d.o, neither he showed up on IRC for the past 6 months.). But, I haven't heard anything back.

Therefore, I am writing this request: either help me get in touch with @febbraro or give me committing access to the CaseTracker Module.

I'll make the same offer again 4+ years later... we're just in the final phase of a complete re-write of Project* for Drupal 7. We need this to upgrade drupal.org to D7. Do you and your co-worker have any interest in helping us make that module serve all your needs so we stop pouring energy into having to support and port both of them?

@dww In general, I agree with you that we only need one good solution for tracking issues. Because Project issue tracking module depends on Project Module, so I am not sure if Project issue tracking module can be useful or extended for general purpose (like task management for office workers).

On the other hand, I just used simplytest.me to try to spin up the latest Project module and Project issue tracking (7.x-2.0-unstable1). Project issue tracking still has installation problem #1951858: Remove the deprecated project issue generator for D7. So, I am wondering if they are still too early to test.

If your answer to my first question is yes, then soon or later I will make the switch to Project/Project issue tracking and depends on the progress of the porting, I will try to find the earliest switching point.

But, if the answer to the first question is No, then that's too bad; I and my co-workers will have to patch up CaseTracker .

project.module doesn't imply everything we have on drupal.org. You don't have to turn on project_release, install any of the version control integration modules, etc. In fact, this issue queue right here (Drupal.org webmasters) is a project that just has issues, and is used a general task tracker for volunteers working on this site. Notice how there's no option for the "version" of the project the issue is against? That's because this project is configured not to have releases. See what I mean? Many sites use project + project_issue without project_release as a general task-tracking system, not just for software development and release management.

Yes, the port still isn't done, but it's a) getting heavy attention again now to try to finish it and b) it's already being used by some sites and it seems to be working well. project_issue_generate is just a devel helper module, not related to the code itself (I'll reply more at the other issue).

Anyway, hope it works out! We'd love to have more people using (and therefore helping/supporting) the Project* modules.

Thanks,
-Derek

I'm not clear on what's going on in this issue. Since it was just re-opened yesterday, I don't think it qualifies for the 2-week wait in the issue queue required by http://drupal.org/node/251466 The purpose of that process is to give the issue visibility to the current maintainer, and re-opening a 4 year old issue doesn't really accomplish that, so I'm asking that you open a new issue for this.

I'm also aware that the project maintainer is unlikely to reply. If you need this completed in less than 2 weeks and would like to circumvent that standard process, you can escalate this to someone more comfortable than me skipping the process.