A web application that allows citizens to "adopt" civic infrastructure, such as fire hydrants that need to be shoveled out after it snows.
Go to file
Erik Michaels-Ober 0d45efac05 Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00
app Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00
config Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00
db Add address fields 2012-01-02 10:46:44 -08:00
doc first commit 2011-02-14 13:28:51 -05:00
lib Reconfigure assets for Rails 3.1.0.rc5 2011-07-30 08:52:38 -07:00
log Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
public Update rails dependency to version 3.2.0.rc2 2012-01-10 14:35:38 -08:00
script first commit 2011-02-14 13:28:51 -05:00
test Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00
vendor Update rails dependency to version 3.2.0.rc2 2012-01-10 14:35:38 -08:00
.gitignore Update rails dependency to version 3.2.0.rc2 2012-01-10 14:35:38 -08:00
.travis.yml Revert "Add back Rubinius support (only in 1.9 mode)" 2012-01-12 15:43:18 -08:00
Gemfile Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00
Gemfile.lock Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00
LICENSE.md Add periods 2011-04-28 07:37:54 -07:00
Procfile Use thin in production 2011-08-27 12:14:10 -07:00
README.md Revert "Add back Rubinius support (only in 1.9 mode)" 2012-01-12 15:43:18 -08:00
Rakefile Finish refactoring out hydrants 2011-09-15 16:58:44 -07:00
config.ru Finish refactoring out hydrants 2011-09-15 16:58:44 -07:00
screenshot.png Refactor in preparation for Bootstrap 2.0 2012-01-16 14:18:08 -08:00

README.md

Adopt-a-Hydrant Build Status Dependency Status

Claim responsibility for shoveling out a fire hydrant after it snows.

Screenshot

Adopt-a-Hydrant

Demo

You can see a running version of the application at http://adopt-a-hydrant.herokuapp.com/.

Installation

git clone git://github.com/codeforamerica/adopt-a-hydrant.git
cd adopt-a-hydrant
bundle install

Usage

rails server

Contributing

In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

  • by using alpha, beta, and prerelease versions
  • by reporting bugs
  • by suggesting new features
  • by translating to a new language
  • 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 closing 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 issue 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 tests for your feature or bug fix.
  5. Run bundle exec rake test. If your changes are not 100% covered, go back to step 4.
  6. Commit and push your changes.
  7. Submit a pull request. Please do not include changes to the gemspec or version file. (If you want to create your own version for some reason, please do so in a separate commit.)

Supported Ruby Versions

This library aims to support and is tested against the following Ruby implementations:

  • Ruby 1.9.2
  • Ruby 1.9.3

If something doesn't work on one of these interpreters, it should be considered a bug.

This library may inadvertently work (or seem to work) on other Ruby implementations, however support will only be provided for the versions listed above.

If you would like this library to support another Ruby version, you may volunteer to be a maintainer. Being a maintainer entails making sure all tests run and pass on that implementation. When something breaks on your implementation, you will be personally responsible for providing patches in a timely fashion. If critical issues for a particular implementation exist at the time of a major release, support for that Ruby version may be dropped.

Copyright

Copyright (c) 2011 Code for America. See LICENSE for details.

Code for America Tracker