first experiences with DITrack

A.T.Hofkamp a.t.hofkamp at tue.nl
Tue Jul 10 08:21:29 PDT 2007


Hello,

I was looking for a small issue tracker for some personal projects, and found 
DITrack. It seems to match nicely with my use of SVN (and not so nicely with 
my use of Combinator, but more about that later).

Below are my first experiences.



- I really liked to be able to specify a default set of columns for 'ls'. I am 
  missing the Categories, and have little use for submitter/owner (it is 
always me).



- You seem to use versions a lot, both as where the bug is found and when the 
issue is fixed. I have a lot less need for them (especially the latter), 
wouldn't it be possible to leave the fields open?



- Why do you ask me which version when only one option exists?



- with 'act', the 'edit comment' entry is confusing to me. 'Edit' to me means 
'load file, change a bit, and save it again'. You edit concept is more 'add 
comment'. If you are fighting which letter to use, maybe use of T as in 'add 
text' would be a solution?



- Webpage document format of files is not correct w.r.t. reality. The examples 
don't work. Maybe you could add a unit test with the web-page values, with a 
note that when changing the tests, the page should also be changed?



- Not use DITRACK_ROOT?

I use Combinator (http://divmod.org/trac/wiki/DivmodCombinator) for my 
projects (part of UQDS 
(http://divmod.org/trac/wiki/UltimateQualityDevelopmentSystem)).

The structure of this is

~/projects/Proj1/trunk/.....
~/projects/Proj1/branch/branch1/.....
~/projects/Proj1/branch/branch2/.....

A common ~/projects directory, then for each project Proj1, Proj2, etc a 
directory trunk (the trunk WC), and zero or more branch WCs in 
branches/branchX/...
The logical place for DITrack data is at ~/projects/Proj1/issues, 
~/projects/Proj2/issues, etc.
With that setup, I now have to change the value of the environment variable 
each time instead of just changing directory.





Last but not least:


Although it is not optimal yet, I like the idea and functionality.

I read that you need documentation. What kind of documentation are you 
thinking about?


Sincerely,
Albert





More information about the Dev mailing list