Browse files

Replace placeholder README with actual README

  • Loading branch information...
1 parent 0952684 commit 966a2ac9fad1041b34d740f7bd473828a7cc44a4 @sferik sferik committed May 11, 2011
Showing with 61 additions and 19 deletions.
  1. +61 −19
@@ -1,29 +1,71 @@
-# The Code for America RubyGem template
+# Futures Pipeline
-If you want to create a new Code for America gem, you can use this gem as a template.
-It's similar to [suspenders][suspenders], but for RubyGems instead of Rails.
+Ruby wrapper for the Futures, Inc. US Military Pipeline API
+ gem install futures_pipeline
-For more information on RubyGems, you should read the [RubyGems Manuals][manuals].
+Continuous Integration
+[![Build Status](](
-After cloning this gem, you'll want to make the following changes:
+Usage Examples
+ require 'futures_pipeline'
-1. Replace all instances of gem_template and GemTemplate with the snake_case and CamelCase name of your gem, respectively
-2. Add a summary and description to the [gemspec][gemspec] file
+ @client =
+ # Return an array of 50 careers
+ # Return an array of 50 careers
+ # => "Chief Executives"
+ # => "11-1011.00"
+"11-1011.00") # Return detailed information about Chief Executives
+In the spirit of [free software](, **everyone** is encouraged to help improve this project.
-This template includes:
+Here are some ways *you* can contribute:
-* [RSpec][rspec] for isolation testing
-* [SimpleCov][simplecov] for C0 code coverage
-* [ZenTest][zentest] for continuous testing
-* [YARD][yard] for documentation
+* by using alpha, beta, and prerelease versions
+* by reporting bugs
+* by suggesting new features
+* by writing or editing documentation
+* by writing specifications
+* by writing code (**no patch is too small**: fix typos, add comments, clean up inconsistent whitespace)
+* by refactoring code
+* by resolving [issues](
+* by reviewing patches
+* [financially](
+Submitting an Issue
+We use the [GitHub issue tracker](
+to track bugs and features. Before submitting a bug report or feature request,
+check to make sure it hasn't already been submitted. You can indicate support
+for an existing issuse by voting it up. When submitting a bug report, please
+include a [Gist]( that includes a stack trace and any
+details that may be necessary to reproduce the bug, including your gem version,
+Ruby version, and operating system. Ideally, a bug report should include a pull
+request with failing specs.
+Submitting a Pull Request
+1. Fork the project.
+2. Create a topic branch.
+3. Implement your feature or bug fix.
+4. Add documentation for your feature or bug fix.
+5. Run <tt>bundle exec rake doc:yard</tt>. If your changes are not 100% documented, go back to step 4.
+6. Add specs for your feature or bug fix.
+7. Run <tt>bundle exec rake spec</tt>. If your changes are not 100% covered, go back to step 6.
+8. Commit and push your changes.
+9. Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)
+Copyright (c) 2011 Code for America.
+See [LICENSE]( for details.

0 comments on commit 966a2ac

Please sign in to comment.