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 519d79efbe Update sprockets dependency to version 2.2.2		2012-11-27 19:21:34 -08:00
app	Prevent mass assignment with strong_parameters instead of attr_accessible	2012-11-15 09:34:19 -08:00
config	Prevent mass assignment with strong_parameters instead of attr_accessible	2012-11-15 09:34:19 -08:00
db	Remove support for Ruby 1.8	2012-06-18 15:08:19 -04: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	Add new fixtures to tests	2012-11-15 08:56:00 -08:00
vendor	Remove support for Ruby 1.8	2012-06-18 15:08:19 -04:00
.gitignore	Remove .DS_Store from .gitignore	2012-04-16 12:52:11 -07:00
.travis.yml	Remove support for Ruby 1.8	2012-06-18 15:08:19 -04:00
Gemfile	Prevent mass assignment with strong_parameters instead of attr_accessible	2012-11-15 09:34:19 -08:00
Gemfile.lock	Update sprockets dependency to version 2.2.2	2012-11-27 19:21:34 -08: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	Remove support for Ruby 1.8	2012-06-18 15:08:19 -04:00
Rakefile	Remove support for Ruby 1.8	2012-06-18 15:08:19 -04: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. 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 repository.
Create a topic branch.
Add specs for your unimplemented feature or bug fix.
Run bundle exec rake test. If your specs pass, return to step 3.
Implement your feature or bug fix.
Run bundle exec rake test. If your specs fail, return to step 5.
Run open coverage/index.html. If your changes are not completely covered by your tests, return to step 3.
Add, commit, and push your changes.
Submit a pull request.

Supported Ruby Version

This library aims to support and is tested against Ruby version 1.9.3.

If something doesn't work on this version, 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 version 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.