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 414fd9256d Update haml dependency to version 3.2.0.alpha.14 2012-06-15 00:37:08 -04:00
app Always use === 2012-04-16 12:52:26 -07:00
config Initialize on precompile 2012-05-22 10:47:34 -10:00
db Update devise dependency to version 2.0.0 2012-01-27 13:11:29 -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
.gitignore Remove .DS_Store from .gitignore 2012-04-16 12:52:11 -07:00
.travis.yml Install pre-release bundler for Ruby version support in Gemfile 2012-06-12 21:08:00 -04:00
Gemfile Specify Ruby version via Gemfile 2012-06-10 10:02:30 -04:00
Gemfile.lock Update haml dependency to version 3.2.0.alpha.14 2012-06-15 00:37:08 -04:00
LICENSE.md Add periods 2011-04-28 07:37:54 -07:00
Procfile Replace thin with puma 2012-04-22 16:28:56 -07:00
README.md Add links to Pull Request steps 2012-05-28 09:30:05 -10:00
Rakefile Remove executable attributes and shebang line 2012-05-07 13:46:59 -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

This application requires Postgres to be installed

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

bundle exec rake db:create
bundle exec rake db:schema:load

Usage

rails server

Seed Data

bundle exec rake db:seed

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. 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 repository.
  2. Create a topic branch.
  3. Add specs for your unimplemented feature or bug fix.
  4. Run bundle exec rake test. If your specs pass, return to step 3.
  5. Implement your feature or bug fix.
  6. Run bundle exec rake test. If your specs fail, return to step 5.
  7. Run open coverage/index.html. If your changes are not completely covered by your tests, return to step 3.
  8. Add, commit, and push your changes.
  9. Submit a pull request.

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 (c) 2012 Code for America. See LICENSE for details.

Code for America Tracker