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 d4430ef794 Capitalize radians		2012-03-31 05:47:25 -07:00
app	Capitalize radians	2012-03-31 05:47:25 -07:00
config	Pass JavaScript run through the application controller for localization	2012-01-27 20:07:23 -08: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
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	Explicitly specify language	2012-03-12 12:09:11 -05:00
Gemfile	Replace locale middleware with http_accept_language	2012-01-24 11:26:39 -08:00
Gemfile.lock	Update rails dependency to version 3.2.3	2012-03-31 05:28:06 -07: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	Update schema load line [ci skip]	2012-03-01 13:17:32 -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

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

Screenshot

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. 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

Fork the project.
Create a topic branch.
Implement your feature or bug fix.
Add tests for your feature or bug fix.
Run bundle exec rake test. If your changes are not 100% covered, go back to step 4.
Commit and push your changes.
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.