DITrack development

[Stefan Reichör]

Vlad Skvortsov <vss at 73rus.com> writes:

> Stefan Reichör wrote:
>> Hi!
>>
>> I discovered ditrack a few days ago and I would like to contribute to this project.
>>   
>
> That's great! :-)
>> I am very much interested in revision control system. I have written
>> the svn interface for emacs (psvn.el). And I am also the main author
>> of DVC.el (an tla, hg, bzr, git interface for emacs)
>>
>> My main interest would be to integrate ditrack in my familiar emacs
>> environment.
>>   
>
> All right, is there anything that needs to be changed on the DITrack
> side for this?

DITrack sometimes asks some interactive questions. It would be
probably a bit easier, if all needed parameters can be passed to one
command. I will post again, as soon I have some progress here.

>> Additionally I would like to allow to use a different backend for the
>> ditrack issues. I'd like to use mercurial or bzr.
>>   
>
> We've been recently discussed this possibility, see
>
> http://lists.ditrack.org/pipermail/dev/2007-May/000258.html
>
> There will be no movement in that direction until 0.7 though.

Is there a roadmap or a release date for 0.7? ;-)

I looked a bit at the DITrack source code.
One thing that needs to be enhanced is the dt-createdb script.
At the moment the support for svn is hardcoded. Additionally it will
always checkout from a svn repository.

What about the following changes/enhancements to allow the creation of
an initial DITrack database for different backends:

* Add a dt create-db command and drop the dt-createdb script
* This would mean that the dt-createdb would be re-implemented in python
* Don't require to run svn co
* Just create the issue-dir
* Optionally add the issue-dir to a given revision control system

I think this would be a first step for me to contribute to DITrack.

>> My question is now, how I can contribute to this project?
>>   
>
> If you need some changes on the DITrack side, post the description
> here and we'll discuss it.
>
> If you'd like to have your code distributed with DITrack, send the
> patches and we'll see what we can do about that.

The most recent version of DITrack I have is 0.5
Should I base my patches on that version? Or is there a way to access
the development branch?


Stefan.