Since the demo site looks pretty much like a tracker, I will answer here (and should be provided in a README.txt as well) the questions like:

  • have you contacted XYZ module maintainer before developing yours?
  • is this module using the same approach of module XYZ?

Comments

arhak’s picture

comment_driven is not a tracker suite, rather the missing piece for site builders to make their own tracker tailored to their likings (probably relying on CCK and Views as well)

The two modules known to have similarities are comment_cck & comment_alter_taxonomy
each of them has an opened issue requesting a merge with the other and both were contacted on those issues:

I'm not totally aware of the approach followed by other modules, but haven't found yet nothing the like the approach taken (detailed bellow).
I'm aware of following tracker suite solutions (forgive me if I'm missing any, these are the ones who comes to my mind right now):

a comparison of Project Management / Ticket Tracking Systems

The approach taken is to build a node_form and pass it through its normal flow without taking care of what is doing each module
Leaving the node_form follow its natural course aims to maximize compatibility with other contributed modules leaving them the chance to trigger their respective hooks (insert/update/form_alter/etc) and do their own tweaks the way they like without having to treat them on per case basis.
Nevertheless, the whole ground conquered in that matter represents a drawback in another related front.
until now this module requires to decide whether a change was actually made by comparing a posted node_form (which might come from any module) with its $form_state['values']
For some cases this comparison needs discrimination, luckily not based on how they tweak the form, but how they represent their data, which usually is more stable in time and many modules don't need discrimination because they use default data formats

arhak’s picture

Status: Active » Closed (fixed)

I'm closing FAQ issues, since they are old enough, I need to cleanup the issue queue
and they are supposed to be addressed by #771590: preparing a frist draft for README.txt