ditz 0.4 → 0.5

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,152 @@
1
+ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2
+
3
+ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4
+
5
+ <head>
6
+ <title>Ditz</title>
7
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
8
+ <link rel="stylesheet" href="main.css" type="text/css" />
9
+ </head>
10
+
11
+ <body>
12
+ <h1> Ditz </h1>
13
+
14
+ <p style="border: solid 1px black; background: #ccc; padding: 0.5em;"> Current project status: see the <a href="ditz/">ditz ditz page</a>.
15
+ Current project news: see the <a
16
+ href="http://all-thing.net/search/label/ditz">blog</a> and <a
17
+ href="http://rubyforge.org/pipermail/ditz-talk/">mailing list archives</a>.</p>
18
+
19
+ <p> Ditz is a simple, light-weight distributed issue tracker designed to work
20
+ with distributed version control systems like <a
21
+ href="http://git.or.cz/">git</a>, <a href="http://darcs.net/">darcs</a>, <a
22
+ href="http://www.selenic.com/mercurial/">Mercurial</a>, and <a
23
+ href="http://bazaar-vcs.org/">Bazaar</a>. It can also be used with
24
+ centralized systems like <a href="http://subversion.tigris.org/">SVN</a>.</p>
25
+
26
+ <p> Ditz features a simple, clean commandline interface, a robust plugin
27
+ architecture which allows for adding commands and extending model fields and
28
+ ditz output, a human-editable file format, and an active developer community.
29
+ </p>
30
+
31
+ <p> Ditz also provides static HTML generation capabilities for producing
32
+ world-readable status pages (for a demo, see the <a href="ditz/">ditz ditz
33
+ page</a>). It currently offers no central public method of bug submission.
34
+ </p>
35
+
36
+ <h2> "Screenshots" </h2>
37
+
38
+ <div class="screencap"><code><pre>
39
+ $ ditz status
40
+ 0.4 0/ 1 bugfix, 3/ 6 features, 1/ 1 task xxxx__>>
41
+ unassigned 0/ 1 bugfix, 1/ 6 features, 0/ 0 tasks x______
42
+
43
+ $ ditz
44
+ Version 0.4 (unreleased):
45
+ > ditz-5: plugin architecture for tighter SCM integration, etc
46
+ > ditz-45: bash shell completion
47
+ _ ditz-42: add a --comment option like git commit -m
48
+ _ ditz-54: HOME environment variable not available on windows
49
+
50
+ Unassigned:
51
+ _ ditz-1: commands needs full argument parsing
52
+ _ ditz-32: extended help for commands
53
+ _ ditz-37: created and deleted events not in logs
54
+ _ ditz-53: allow commands like 'start', 'stop', 'close', etc to take multiple arguments
55
+ _ ditz-55: add 'reconfigure' command
56
+ _ ditz-58: log and shortlog should take an optional component name
57
+ </pre></code></div>
58
+ <div class="screencap"><code><pre>
59
+ $ ditz show ditz-45
60
+ Issue ditz-45
61
+ -------------
62
+ Title: bash shell completion
63
+ Description: we have zsh (ditz-34). but i use bash!
64
+ Type: feature
65
+ Status: in progress
66
+ Creator: William Morgan (wmorgan-ditz)
67
+ Age: three months
68
+ Release: 0.4
69
+ References:
70
+ Identifier: d96a7a95dedc20072df13afa4515ee5d739229ce
71
+ Git branch: none
72
+
73
+ Event log:
74
+ - changed status from closed to in_progress (wmorgan-ditz, 70 hours ago)
75
+ > re-opening because there's going to be more work thanks to ditz-57.
76
+ - closed issue with disposition fixed (wmorgan-ditz, eight days ago)
77
+ > contributed by christian garbs
78
+ - assigned to release 0.4 from unassigned (wmorgan-ditz, eight days ago)
79
+ - created (wmorgan-ditz, three months ago)
80
+ </pre></code></div>
81
+ <div class="screencap"><code><pre>
82
+ $ ditz add
83
+ Title: remove "references"
84
+ Description (ctrl-d, ., or /stop to stop, /edit to edit, /reset to reset):
85
+ > with the advent of decent issue interpolation, this isn't that useful.
86
+ > this probably deserves some more thought before becoming reality.
87
+ > .
88
+ Is this a (b)ugfix, a (f)eature, or a (t)ask? t
89
+ Assign to a release now? (y/n): n
90
+ Issue creator (enter for "William Morgan (wmorgan-ditz)"):
91
+ Comments (ctrl-d, ., or /stop to stop, /edit to edit, /reset to reset):
92
+ > .
93
+ Added issue ditz-59.
94
+ </pre></code></div>
95
+
96
+ <h2>Documentation</h2>
97
+
98
+ <p> Ditz maintains an issue database directory on disk, with files written in
99
+ a line-based and human-editable format. This directory can be kept under
100
+ version control, alongside project code. </p>
101
+
102
+ <p> There are several different ways to use ditz:
103
+
104
+ <ol> <li> Treat issue change the same as code change: include it as part of
105
+ commits, and merge it with changes from other developers, resolving conflicts
106
+ in the usual manner. </li> <li> Keep the issue database in the repository but
107
+ in a separate branch. Issue changes can be managed by your VCS, but is not
108
+ tied directly to code commits. </li> <li> Keep the issue database separate
109
+ and not under VCS at all. </li> </ol> </p>
110
+
111
+ <p> For more, read the <a href="README.txt">README</a> and the <a href="PLUGINS.txt">plugin documentation</a>.
112
+
113
+ <h2>Getting it</h2>
114
+
115
+ <p> You can download ditz releases from the <a
116
+ href="http://rubyforge.org/projects/ditz/">ditz RubyForge page</a>.
117
+ Or, if you have RubyGems installed, simply command your computer to
118
+ "gem install ditz". </p>
119
+
120
+ <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>
121
+
122
+ <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:
123
+ <code>git clone git://gitorious.org/ditz/mainline.git</code>.
124
+ You can also <a href="http://gitorious.org/projects/ditz">browse
125
+ the ditz git repository</a>. </p>
126
+
127
+ <h2>Bug reports</h2>
128
+
129
+ <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>
130
+
131
+ <p> Of course, you can also submit a bug report by cloning the git repo,
132
+ using "ditz add" to add an issue, and sending a merge request or submitting
133
+ the resulting patch. </p>
134
+
135
+ <h2>Related Work</h2>
136
+
137
+ <p>There's a <a href="http://github.com/kentaro/emacs-ditz/tree/master">Ditz emacs mode</a> by Kentaro Kuribayashi.</p>
138
+
139
+ <h2>Credit</h2>
140
+
141
+ <p> Ditz is brought to you by <a href="http://cs.stanford.edu/~ruby/">William Morgan</a> and by
142
+ <ul>
143
+ <li> Nicolas Pouillard &lt;nicolas.pouillard at the gmail dot coms&gt; </li>
144
+ <li> Ramsey Dow &lt;yesmar at the speakeasy dot nets&gt; </li>
145
+ <li> Eric Merritt &lt;cyberlync at the gmail dot coms&gt; </li>
146
+ <li> Christian Garbs &lt;mitch at the cgarbs dot des&gt; </li>
147
+ <li> oleg dashevskii &lt;be9 at the be9 dot rus&gt; </li>
148
+ <li> Jeff Balogh &lt;its.jeff.balogh at the gmail dot coms&gt; </li>
149
+ <li> Harold Hausman &lt;hhausman at the gmail dot coms&gt; </li>
150
+ </ul>
151
+ </body>
152
+ </html>
@@ -0,0 +1,45 @@
1
+ body
2
+ {
3
+ background: white;
4
+ color: #404040;
5
+ margin-bottom: 2em;
6
+ margin-left: auto;
7
+ margin-right: auto;
8
+ width: 90%;
9
+ }
10
+
11
+ a, a:visited
12
+ {
13
+ border-bottom: 1px dotted #03c;
14
+ background: inherit;
15
+ color: #03c;
16
+ text-decoration: none;
17
+ }
18
+
19
+ #screenshots
20
+ {
21
+ margin: 0;
22
+ padding: 0;
23
+ }
24
+ #screenshots li
25
+ {
26
+ display: inline;
27
+ list-style: none;
28
+ }
29
+ #screenshots a
30
+ {
31
+ border-bottom: none;
32
+ }
33
+ #screenshots img
34
+ {
35
+ border: 0;
36
+ }
37
+
38
+ .screencap {
39
+ border: solid 1px red;
40
+ background-color: black;
41
+ padding: 0.5em;
42
+ margin-bottom: 1em;
43
+ color: #aaa;
44
+ width: 45em;
45
+ }
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: ditz
3
3
  version: !ruby/object:Gem::Version
4
- version: "0.4"
4
+ version: "0.5"
5
5
  platform: ruby
6
6
  authors:
7
7
  - William Morgan
@@ -9,7 +9,7 @@ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
11
 
12
- date: 2008-07-27 07:00:00 Z
12
+ date: 2008-08-20 07:00:00 Z
13
13
  default_executable:
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
@@ -20,7 +20,7 @@ dependencies:
20
20
  requirements:
21
21
  - - ">="
22
22
  - !ruby/object:Gem::Version
23
- version: 1.8.2
23
+ version: "1.9"
24
24
  version:
25
25
  - !ruby/object:Gem::Dependency
26
26
  name: hoe
@@ -32,22 +32,34 @@ dependencies:
32
32
  - !ruby/object:Gem::Version
33
33
  version: 1.7.0
34
34
  version:
35
- description: "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. 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. There are different ways to use ditz: 1. 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.) 2. 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 commits. 3. Keep the issue database separate and not under VCS at all. Your particular usage will depend on what you want to get out of ditz. Ditz provides a simple, console-based interface for creating and updating the issue database file, and some rudimentary HTML generation capabilities for producing world-readable status pages. It currently offers no central public method of bug submission. Synopsis: # set up project. creates the bugs.yaml file. 1. ditz init 2. ditz add-release"
35
+ description: "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. 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. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. 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. 2. 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. 3. Keep the issue database separate and not under VCS at all."
36
36
  email: wmorgan-ditz@masanjin.net
37
37
  executables:
38
38
  - ditz
39
39
  extensions: []
40
40
 
41
41
  extra_rdoc_files:
42
+ - Manifest.txt
43
+ - PLUGINS.txt
42
44
  - README.txt
43
45
  files:
44
46
  - Changelog
47
+ - INSTALL
48
+ - LICENSE
49
+ - Manifest.txt
50
+ - PLUGINS.txt
45
51
  - README.txt
46
52
  - Rakefile
47
53
  - ReleaseNotes
48
54
  - bin/ditz
55
+ - contrib/completion/_ditz.zsh
56
+ - contrib/completion/ditz.bash
57
+ - lib/blue-check.png
49
58
  - lib/component.rhtml
50
59
  - lib/ditz.rb
60
+ - lib/file-storage.rb
61
+ - lib/green-bar.png
62
+ - lib/green-check.png
51
63
  - lib/hook.rb
52
64
  - lib/html.rb
53
65
  - lib/index.rhtml
@@ -57,15 +69,22 @@ files:
57
69
  - lib/model-objects.rb
58
70
  - lib/model.rb
59
71
  - lib/operator.rb
72
+ - lib/plugins/git-sync.rb
73
+ - lib/plugins/git.rb
74
+ - lib/plugins/issue-claiming.rb
75
+ - lib/red-check.png
60
76
  - lib/release.rhtml
61
77
  - lib/style.css
78
+ - lib/trollop.rb
62
79
  - lib/unassigned.rhtml
63
80
  - lib/util.rb
64
81
  - lib/view.rb
65
82
  - lib/views.rb
66
- - lib/plugins/git.rb
67
- - contrib/completion/ditz.bash
68
- - contrib/completion/_ditz.zsh
83
+ - lib/yellow-bar.png
84
+ - man/ditz.1
85
+ - setup.rb
86
+ - www/index.html
87
+ - www/main.css
69
88
  has_rdoc: true
70
89
  homepage: http://ditz.rubyforge.org
71
90
  post_install_message: