1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Ditz</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="main.css" type="text/css" />
</head>
<body>
<h1> Ditz </h1>
<p style="border: solid 1px black; background: #ccc; padding: 0.5em;"> Current project status: see the <a href="ditz/">ditz ditz page</a>.
Current project news: see the <a
href="http://all-thing.net/search/label/ditz">blog</a> and <a
href="http://rubyforge.org/pipermail/ditz-talk/">mailing list archives</a>.</p>
<p> Ditz is a simple, light-weight distributed issue tracker designed to work
with distributed version control systems like <a
href="http://git.or.cz/">git</a>, <a href="http://darcs.net/">darcs</a>, <a
href="http://www.selenic.com/mercurial/">Mercurial</a>, and <a
href="http://bazaar-vcs.org/">Bazaar</a>. It can also be used with
centralized systems like <a href="http://subversion.tigris.org/">SVN</a>.</p>
<p> Ditz features a simple, clean commandline interface, a robust plugin
architecture which allows for adding commands and extending model fields and
ditz output, a human-editable file format, and an active developer community.
</p>
<p> Ditz also provides static HTML generation capabilities for producing
world-readable status pages (for a demo, see the <a href="ditz/">ditz ditz
page</a>). It currently offers no central public method of bug submission.
</p>
<h2> "Screenshots" </h2>
<div class="screencap"><code><pre>
$ ditz status
0.4 0/ 1 bugfix, 3/ 6 features, 1/ 1 task xxxx__>>
unassigned 0/ 1 bugfix, 1/ 6 features, 0/ 0 tasks x______
$ ditz
Version 0.4 (unreleased):
> ditz-5: plugin architecture for tighter SCM integration, etc
> ditz-45: bash shell completion
_ ditz-42: add a --comment option like git commit -m
_ ditz-54: HOME environment variable not available on windows
Unassigned:
_ ditz-1: commands needs full argument parsing
_ ditz-32: extended help for commands
_ ditz-37: created and deleted events not in logs
_ ditz-53: allow commands like 'start', 'stop', 'close', etc to take multiple arguments
_ ditz-55: add 'reconfigure' command
_ ditz-58: log and shortlog should take an optional component name
</pre></code></div>
<div class="screencap"><code><pre>
$ ditz show ditz-45
Issue ditz-45
-------------
Title: bash shell completion
Description: we have zsh (ditz-34). but i use bash!
Type: feature
Status: in progress
Creator: William Morgan (wmorgan-ditz)
Age: three months
Release: 0.4
References:
Identifier: d96a7a95dedc20072df13afa4515ee5d739229ce
Git branch: none
Event log:
- changed status from closed to in_progress (wmorgan-ditz, 70 hours ago)
> re-opening because there's going to be more work thanks to ditz-57.
- closed issue with disposition fixed (wmorgan-ditz, eight days ago)
> contributed by christian garbs
- assigned to release 0.4 from unassigned (wmorgan-ditz, eight days ago)
- created (wmorgan-ditz, three months ago)
</pre></code></div>
<div class="screencap"><code><pre>
$ ditz add
Title: remove "references"
Description (ctrl-d, ., or /stop to stop, /edit to edit, /reset to reset):
> with the advent of decent issue interpolation, this isn't that useful.
> this probably deserves some more thought before becoming reality.
> .
Is this a (b)ugfix, a (f)eature, or a (t)ask? t
Assign to a release now? (y/n): n
Issue creator (enter for "William Morgan (wmorgan-ditz)"):
Comments (ctrl-d, ., or /stop to stop, /edit to edit, /reset to reset):
> .
Added issue ditz-59.
</pre></code></div>
<h2>Documentation</h2>
<p> Ditz maintains an issue database directory on disk, with files written in
a line-based and human-editable format. This directory can be kept under
version control, alongside project code. </p>
<p> There are several different ways to use ditz:
<ol> <li> Treat issue change the same as code change: include it as part of
commits, and merge it with changes from other developers, resolving conflicts
in the usual manner. </li> <li> Keep the issue database in the repository but
in a separate branch. Issue changes can be managed by your VCS, but is not
tied directly to code commits. </li> <li> Keep the issue database separate
and not under VCS at all. </li> </ol> </p>
<p> For more, read the <a href="README.txt">README</a> and the <a href="PLUGINS.txt">plugin documentation</a>.
<h2>Getting it</h2>
<p> You can download ditz releases from the <a
href="http://rubyforge.org/projects/ditz/">ditz RubyForge page</a>.
Or, if you have RubyGems installed, simply command your computer to
"gem install ditz". </p>
<p> <a href="http://www.cgarbs.de/stuff/deb-repository.html#ditz">ditz Debian packages</a> are kindly contributed by Christian Garbs. There's also a <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492805">ditz RFP</a> if you are a Debian maintainer with time on your hands.</a> </p>
<p> For source code access, the <a href="http://gitorious.org/projects/ditz">ditz repository is on Gitorious</a>. You can clone it locally like so:
<code>git clone git://gitorious.org/ditz/mainline.git</code>.
You can also <a href="http://gitorious.org/projects/ditz">browse
the ditz git repository</a>. </p>
<h2>Bug reports</h2>
<p> Feel free to post bug reports, feature requests, and any comments or discussion topics to the <a href="http://rubyforge.org/mailman/listinfo/ditz-talk">ditz-talk mailing list</a> (<a href="http://rubyforge.org/pipermail/ditz-talk/">archives</a>). </p>
<p> Of course, you can also submit a bug report by cloning the git repo,
using "ditz add" to add an issue, and sending a merge request or submitting
the resulting patch. </p>
<h2>Related Work</h2>
<p>There's a <a href="http://github.com/kentaro/emacs-ditz/tree/master">Ditz emacs mode</a> by Kentaro Kuribayashi.</p>
<h2>Credit</h2>
<p> Ditz is brought to you by <a href="http://cs.stanford.edu/~ruby/">William Morgan</a> and by
<ul>
<li> Nicolas Pouillard <nicolas.pouillard at the gmail dot coms> </li>
<li> Ramsey Dow <yesmar at the speakeasy dot nets> </li>
<li> Eric Merritt <cyberlync at the gmail dot coms> </li>
<li> Christian Garbs <mitch at the cgarbs dot des> </li>
<li> oleg dashevskii <be9 at the be9 dot rus> </li>
<li> Jeff Balogh <its.jeff.balogh at the gmail dot coms> </li>
<li> Harold Hausman <hhausman at the gmail dot coms> </li>
</ul>
</body>
</html>
|
