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.
112 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 9194f97251 Use version of therubyracer specifically designed to build on Heroku 2011-05-05 19:55:15 -07:00
app Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
config Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
db Update for MySQL compatibility 2011-03-28 19:24:44 -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 Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
script first commit 2011-02-14 13:28:51 -05:00
test Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
vendor Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
.gitignore Upgrade to Rails 3.1.0.beta1 2011-05-05 19:38:25 -07:00
Gemfile Use version of therubyracer specifically designed to build on Heroku 2011-05-05 19:55:15 -07:00
Gemfile.lock Add therubyracer to satisfy production JavaScript runtime dependency 2011-05-05 19:48:00 -07:00
LICENSE.md Add periods 2011-04-28 07:37:54 -07:00
README.md Add periods 2011-04-28 07:37:54 -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 Add README 2011-04-28 07:35:15 -07:00

README.md

Adopt a Hydrant

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

Screenshot

Adopt a Hydrant

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 specs for your feature or bug fix.
  5. Commit and push your changes.
  6. 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.