[development] forking issue tracking development
drupal at dwwright.net
Sun Dec 17 18:17:12 UTC 2006
On Dec 17, 2006, at 9:17 AM, Michael Favia wrote:
>> I have been developing this in parallel to casetracker and I
>> haven't put
>> it in /modules because I would like one day to see it included in
>> casetracker. I am not a maintainer of casetracker, so obviously
>> it's not
>> me making the decision, so I'm happy to cruise for a while and
>> developing this in my sandbox really makes sense to me.
> Perhaps there is some value to the argument to clean up the
> sandboxes a
> little because i was busy writing a module that duplicates this
> functionality nearly exactly. This Plus the ability to organize your
> cases into order you plan on working on them. Thank you for pointing
> this out.
so, we've got:
- casetracker.module (official)
- casetracker_work.module (sandbox - sime)
- casetracker_fork_2.module (??? - michael favia)
- CCK-based project/issue tracking (http://groups.drupal.org/node/409)
- helpdesk (pre-alpha, i think)
absolutely *none* of these is actually full-featured and does what we
want. i've been working hard making project_issue.module better, and
morbus has been beating casetracker (official) into submission (IMHO,
a tragic fork of resources right there). yes, choices are good.
yes, 1 giant module that does everything won't make everyone happy.
instead of forking our limited development resources in this crucial
space, can't we collaborate more? all the things you hate about
project_issue (and i'm sure there are many), let's just fix them so
it works how we all need, instead of starting over from scratch for
the (N+1)th time...
pretty, pretty please: join the issue tracking group:
collaborate, don't fork...
More information about the development