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 e4e075ae09 Update uglifier dependency to version 1.0.0		2011-06-21 08:32:40 -07:00
app	Create reminders in the database	2011-06-13 15:39:39 -07:00
config	Don't preload application	2011-06-20 10:59:51 -07:00
db	Create reminders in the database	2011-06-13 15:39:39 -07:00
doc	first commit	2011-02-14 13:28:51 -05:00
lib/tasks	first commit	2011-02-14 13:28:51 -05:00
log	Upgrade to Rails 3.1.0.beta1	2011-05-05 19:38:25 -07:00
public	Enable asset pipeline	2011-05-31 04:12:38 -07:00
script	first commit	2011-02-14 13:28:51 -05:00
test	Update execjs dependency to version 1.2.0	2011-06-18 13:54:22 -07:00
vendor	Upgrade to Rails 3.1.0.beta1	2011-05-05 19:38:25 -07:00
.gitignore	Update rails dependency to 3.1.0.rc1	2011-05-22 03:42:21 -07:00
.travis.yml	Revert "Use db:schema:load task instead of db:migrate"	2011-06-14 07:45:03 -07:00
Gemfile	Add concurrecy with unicorn	2011-06-20 10:40:34 -07:00
Gemfile.lock	Update uglifier dependency to version 1.0.0	2011-06-21 08:32:40 -07:00
LICENSE.md	Add periods	2011-04-28 07:37:54 -07:00
Procfile	Add concurrecy with unicorn	2011-06-20 10:40:34 -07:00
README.md	Update URL for Cedar stack	2011-06-18 14:57:03 -07:00
Rakefile	Upgrade to Rails 3.1.0.beta1	2011-05-05 19:38:25 -07:00
config.ru	first commit	2011-02-14 13:28:51 -05:00
screenshot.png	Update screenshot	2011-05-09 00:08:37 -07:00

README.md

Adopt a Hydrant

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

Screenshot

Continuous Integration

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

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