choteaumt
/
adopt-a-hydrant
mirror of https://github.com/choteaumt/adopt-a-hydrant.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
A web application that allows citizens to "adopt" civic infrastructure, such as fire hydrants that need to be shoveled out after it snows.
210 Commits 2 Branches 0 Tags 6.1 MiB
Ruby 92.8%
Haml 3.6%
JavaScript 2.6%
HTML 0.5%
CSS 0.5%
Go to file
Erik Michaels-Ober ed6e965b51 Update execjs dependency to version 1.1.3 2011-06-13 23:45:55 -07:00
app Create reminders in the database 2011-06-13 15:39:39 -07:00
config Create reminders in the database 2011-06-13 15:39:39 -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 Enable asset pipeline 2011-05-31 04:12:38 -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 Test against Rubinius 2.0 2011-06-08 12:22:49 -04:00
Gemfile Update rails dependency to version 3.1.0.rc4 2011-06-09 16:54:03 -07:00
Gemfile.lock Update execjs dependency to version 1.1.3 2011-06-13 23:45:55 -07:00
LICENSE.md Add periods 2011-04-28 07:37:54 -07:00
README.md Edited README.md via GitHub 2011-05-27 15:13:30 -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

Adopt a Hydrant

Continuous Integration

Build Status

Demo

You can see a running version of the application at http://adopt-a-hydrant.heroku.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

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

Copyright

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

Code for America Tracker