initial commit to seperate repo
This commit is contained in:
commit
1a020ca68b
1302 changed files with 201261 additions and 0 deletions
23
posts/200703cli-bugissuetask-tracking-system.html
Normal file
23
posts/200703cli-bugissuetask-tracking-system.html
Normal file
|
|
@ -0,0 +1,23 @@
|
|||
<html><body><h1>cli bug/issue/task tracking system?</h1>
|
||||
|
||||
<p>Fresh from freshmeat:</p>
|
||||
|
||||
<p>http://www.ditrack.org/</p>
|
||||
|
||||
<pre><code>What is DITrack?
|
||||
|
||||
DITrack is a free, open source, lightweight, distributed issue (bug,
|
||||
defect, ticket) tracking system using a [Subversion](http://subversion.tigris.org/) repository instead
|
||||
of a backend database. It is written in Python and runs in UNIX
|
||||
environment (*BSD, Linux, MacOS X).
|
||||
|
||||
The project is inspired by the idea of [Subissue](http://subissue.tigris.org/) issue tracking system.
|
||||
|
||||
However, while Subissue aims in merely replacing the traditional
|
||||
database storage with Subversion repository, DITrack is a major
|
||||
rethought of the issue tracking system paradigm. The main difference
|
||||
is that instead of sticking to the centralized model (one database,
|
||||
one web interface, one mail integration machinery), DITrack treats
|
||||
underlying Subversion storage as a versioned distributed file system
|
||||
which enables benefits of truly distributed operation mode.
|
||||
</code></pre></body></html>
|
||||
Loading…
Add table
Add a link
Reference in a new issue