ohac-ditz 0.5.1

metadata

@@ -0,0 +1,116 @@
+--- !ruby/object:Gem::Specification 
+name: ohac-ditz
+version: !ruby/object:Gem::Version 
+  version: 0.5.1
+platform: ruby
+authors: 
+- William Morgan
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2008-09-05 00:00:00 +09:00
+default_executable: ditz
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: trollop
+  type: :runtime
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "1.9"
+    version: 
+- !ruby/object:Gem::Dependency 
+  name: yaml_waml
+  type: :runtime
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "0.3"
+    version: 
+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."
+email: wmorgan-ditz@masanjin.net
+executables: 
+- ditz
+extensions: []
+
+extra_rdoc_files: 
+- Manifest.txt
+- PLUGINS.txt
+- README.txt
+files: 
+- Changelog
+- INSTALL
+- LICENSE
+- Manifest.txt
+- PLUGINS.txt
+- README.txt
+- Rakefile
+- ReleaseNotes
+- bin/ditz
+- contrib/completion/_ditz.zsh
+- contrib/completion/ditz.bash
+- lib/ditz.rb
+- lib/ditz/file-storage.rb
+- lib/ditz/hook.rb
+- lib/ditz/html.rb
+- lib/ditz/lowline.rb
+- lib/ditz/model-objects.rb
+- lib/ditz/model.rb
+- lib/ditz/operator.rb
+- lib/ditz/plugins/git-sync.rb
+- lib/ditz/plugins/git.rb
+- lib/ditz/plugins/issue-claiming.rb
+- lib/ditz/plugins/issue-labeling.rb
+- lib/ditz/util.rb
+- lib/ditz/view.rb
+- lib/ditz/views.rb
+- share/ditz/index.rhtml
+- share/ditz/issue.rhtml
+- share/ditz/issue_table.rhtml
+- share/ditz/release.rhtml
+- share/ditz/unassigned.rhtml
+- share/ditz/component.rhtml
+- share/ditz/style.css
+- share/ditz/blue-check.png
+- share/ditz/green-bar.png
+- share/ditz/green-check.png
+- share/ditz/red-check.png
+- share/ditz/yellow-bar.png
+- man/man1/ditz.1
+- setup.rb
+has_rdoc: true
+homepage: http://ditz.rubyforge.org
+licenses: []
+
+post_install_message: 
+rdoc_options: 
+- --main
+- README.txt
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+requirements: []
+
+rubyforge_project: ditz
+rubygems_version: 1.3.5
+signing_key: 
+specification_version: 2
+summary: A simple issue tracker designed to integrate well with distributed version control systems like git and darcs. State is saved to a YAML file kept under version control, allowing issues to be closed/added/modified as part of a commit.
+test_files: []
+