schubert-minglr 0.1.0.2

data/README.rdoc

@@ -0,0 +1,102 @@
+= minglr
+
+* http://github.com/stephenchu/minglr/tree/master
+
+== DESCRIPTION:
+
+* This gem provides two executable binaries to interact with Mingle (http://mingle.thoughtworks.com/mingle-agile-project-management) through its API. It also has sample interactive Rake task on how to facilitate easy card movements when a card enters/exits the development queue.
+
+* mtx is a binary that facilities transition changes for use on rake tasks
+* minglr is a more interactive tool that provides a quick interface for many common uses
+
+== MINGLR FEATURES:
+* lists cards
+	$ minglr cards
+	266 - Task   - Development Complete  - Investigate new tool
+	265 - Defect - New                   - The background is the wrong color
+
+* list users
+	$ minglr users
+	schubert - Michael Schubert - michael@yourcompany.com
+
+* list all cards with the word "foo"
+	$ minglr cards foo
+
+* list details for card 215
+	$ minglr card 215
+	     Number: 215
+	       Name: Add the frobble to the bobble
+	       Type: Story
+	     Status: In Development
+	Description: Lorem Ipsum
+
+* create new story card
+	$ minglr create -t Story -n "My New Story" -d "Story Description"
+	Created story card 271
+
+* update a card
+	$ minglr update 271 -d "Bettter Description"
+	Card 271 updated
+
+	     Number: 271
+	       Name: Add the frobble to the bobble
+	       Type: Task
+	     Status: Ready for Development
+	Description: Better Description
+
+* move card based on defined transitions
+	$ minglr move 266 -c "All done with development"
+	Moved card from In Development to Dev Complete
+
+== MTX FEATURES:
+
+* Executes a card transition through the Mingle API.
+* Caches user-entered information during Rake task execution.
+* SVN Rake tasks to perform update, remove, add, and conflict check.
+* Sample Rake tasks to illustrate a single Rake command line that will grab latest changes, check for conflicts, run tests, check-in, and finally move card on Mingle.
+
+== SYNOPSIS:
+
+Do you forget to update a story card on Mingle when the card has moved into developers' hands? How about forgetting to update the story card to kick-off its sign off process when story is completed? If we let these sloppiness happen too often, communication flow will be hindered, and the time it takes to provide business value through story completions will be lengthened. Fortunately, Minglr can help.
+
+Minglr allows you to write Rake tasks to execute Mingle card transitions as part of your build process. For example, for a developer to check-in new code, s/he could run the following Rake task:
+
+$ rake check_in
+
+At the end of this Rake task, it can execute a Mingle API call through the help of Minglr to execute the appropriate transition for the card being worked on, be it to move a card into 'In Development', or mark it as 'Story Completed'.
+
+Of course, frequently additional user inputs are required to transition a card. For example, a card number and a comment. Minglr also provides Rake helpers to easily prompt users for inputs as part of their Rake runs, as well as caching them to save future typings.
+
+Minglr can be used regardless your application is a Ruby on Rails web application or a simple Ruby application. In fact, it can even be used as a command line tool to transition cards on Mingle.
+
+== INSTALL:
+
+* sudo gem install stephenchu-minglr
+* Preferably install rb-password (http://www.caliban.org/ruby/ruby-password.shtml), through Macports (sudo port install rb-password)
+* Enable Mingle API basic authentication in auth_config.yml, then restart it.
+* Copy over the "path-to-minglr/tasks/*.sample.rake" files and start customizing for your check-in needs.
+
+== LICENSE:
+
+(The MIT License)
+
+Copyright (c) 2009 Stephen Chu
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/Rakefile

@@ -0,0 +1,29 @@
+%w[rubygems rake rake/clean fileutils newgem rubigen].each { |f| require f }
+require File.dirname(__FILE__) + '/lib/minglr'
+
+# Generate all the Rake tasks
+# Run 'rake -T' to see list of generated tasks (from gem root directory)
+$hoe = Hoe.new('minglr', Minglr::VERSION) do |p|
+  p.developer('Stephen Chu', 'minglr@stephenchu.com')
+  p.changes              = p.paragraphs_of("History.txt", 0..1).join("\n\n")
+  p.post_install_message = 'PostInstall.txt' # TODO remove if post-install message not required
+  p.rubyforge_name       = p.name # TODO this is default value
+  p.extra_deps         = [
+    ['activesupport','>= 2.1.0'],
+    ['activeresource', '>= 2.1.0']
+  ]
+  p.extra_dev_deps = [
+    ['newgem', ">= #{::Newgem::VERSION}"]
+  ]
+  
+  p.clean_globs |= %w[**/.DS_Store tmp *.log]
+  path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}"
+  p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc')
+  p.rsync_args = '-av --delete --ignore-errors'
+end
+
+require 'newgem/tasks' # load /tasks/*.rake
+Dir['tasks/**/*.rake'].each { |t| load t }
+
+# TODO - want other tests/tasks run by default? Add them to the list
+# task :default => [:spec, :features]

data/minglr.gemspec

@@ -0,0 +1,11 @@
+Gem::Specification.new do |s|
+  s.name     = "minglr"
+  s.version  = "0.1.0.2"
+  s.date     = "2009-05-20"
+  s.summary  = "Consists of Rake task helpers and a command line utility to help transitioning story cards on Mingle through the Mingle API. Plugs right into your routine \"test > code > check-in > move card\" build process."
+  s.email    = "github@stephenchu.com"
+  s.homepage = "http://github.com/stephenchu/minglr/tree/master"
+  s.description = "Do you forget to update a story card on Mingle when the card has moved into developers' hands? How about forgetting to update the story card to kick-off its sign off process when story is completed? If we let these sloppiness happen too often, communication flow will be hindered, and the time it takes to provide business value through story completions will be lengthened. Fortunately, Minglr can help."
+  s.authors  = ["Stephen Chu", "Chris O'Meara", "Michael Schubert"]
+  s.files    = Dir["bin/*"] + Dir["*.txt"] + Dir["lib/minglr/*.rb"] + Dir["lib/*.rb"] + ["minglr.gemspec", "Rakefile", "README.rdoc", "minglrconfig.sample"] + Dir["tasks/*"]
+end

data/minglrconfig.sample

@@ -0,0 +1,18 @@
+[global]
+	default = someproject
+	username = yourusername
+	
+[someproject]
+  	url = http://your.mingle.host.com/mingle/projects/someproject
+	username = yourusername
+	password = YOURMINGLEPASSWORD
+	delete_property = cp_story_status
+	delete_state = Deleted
+	status_property = cp_story_status
+	story_state_1 = Ready For Development > Sign Up for Story
+	story_state_2 = Dev In Progress > Dev Complete
+	task_state_1 = New > New to ready for Dev for Task
+	task_state_2 = Ready for Development > Dev in Progress
+	task_state_3 = Dev In Progress > Story from Dev in Progress to Dev Complete
+	story_checkout = story_state_1
+	task_checkout = story_state_2

metadata

@@ -0,0 +1,58 @@
+--- !ruby/object:Gem::Specification 
+name: schubert-minglr
+version: !ruby/object:Gem::Version 
+  version: 0.1.0.2
+platform: ruby
+authors: 
+- Stephen Chu
+- Chris O'Meara
+- Michael Schubert
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2009-05-20 00:00:00 -07:00
+default_executable: 
+dependencies: []
+
+description: Do you forget to update a story card on Mingle when the card has moved into developers' hands? How about forgetting to update the story card to kick-off its sign off process when story is completed? If we let these sloppiness happen too often, communication flow will be hindered, and the time it takes to provide business value through story completions will be lengthened. Fortunately, Minglr can help.
+email: github@stephenchu.com
+executables: []
+
+extensions: []
+
+extra_rdoc_files: []
+
+files: 
+- minglr.gemspec
+- Rakefile
+- README.rdoc
+- minglrconfig.sample
+has_rdoc: false
+homepage: http://github.com/stephenchu/minglr/tree/master
+post_install_message: 
+rdoc_options: []
+
+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: 
+rubygems_version: 1.2.0
+signing_key: 
+specification_version: 2
+summary: Consists of Rake task helpers and a command line utility to help transitioning story cards on Mingle through the Mingle API. Plugs right into your routine "test > code > check-in > move card" build process.
+test_files: []
+