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.
347 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
Ryan Resella 0b71636e7e Fixed Travis CI status link in README [ci skip] 2011-09-07 20:31:24 -07:00
app Embed minified Google Analytics code in header 2011-09-03 13:58:18 -07:00
config Change production settings 2011-09-03 13:27:23 -07:00
db Fix version number 2011-08-11 17:12:18 -07: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 Revert "Revert to old skool asset management" 2011-06-23 20:17:01 -07:00
script first commit 2011-02-14 13:28:51 -05:00
test Re-run rails generator for 3.1.0 final 2011-09-03 13:09:58 -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 Use mustang for testing, therubyracer in production 2011-08-11 17:14:58 -07:00
Gemfile Changes for Heroku 2011-09-03 12:33:28 -07:00
Gemfile.lock Update rails_admin dependency 2011-09-05 14:05:17 -04: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 Fixed Travis CI status link in README [ci skip] 2011-09-07 20:31:24 -07:00
Rakefile Make Rakefile executable 2011-08-27 10:56:05 -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.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

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

Supported Rubies

This library aims to support and is tested against the following Ruby implementations:

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.

Copyright

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

Code for America Tracker