No description
Find a file
2011-08-19 14:21:48 -07:00
lib Bump version to 0.1.5 2011-05-06 13:19:11 -07:00
test Use SSL-enabled build status image to avoid proxy caching 2011-07-27 00:21:31 -07:00
.gemtest Opt-in for testing with rubygems-test 2011-02-03 13:04:23 -05:00
.gitignore Replace rdoc with yard 2011-05-06 12:13:03 -07:00
.travis.yml Revert "Remove JRuby support" 2011-08-08 13:54:48 -07:00
.yardopts Replace rdoc with yard 2011-05-06 12:13:03 -07:00
Gemfile Add jruby-openssl dependency 2011-05-06 13:13:55 -07:00
init.rb Populate the init.rb file for use as a Rails plugin. 2010-10-11 13:50:58 -04:00
LICENSE.md Add self as co-author 2011-05-06 12:22:32 -07:00
Rakefile Replace rdoc with yard 2011-05-06 12:13:03 -07:00
README.md Switch up Markdown syntax for headers [ci skip] 2011-08-19 14:21:48 -07:00
simple_oauth.gemspec Update gemspec [ci skip] 2011-08-14 23:51:04 -07:00

simple_oauth

Simply builds and verifies OAuth headers

Continuous Integration

Build Status

Submitting a Pull Request

  1. Fork the project.
  2. Create a topic branch.
  3. Implement your feature or bug fix.
  4. Add documentation for your feature or bug fix.
  5. Run bundle exec rake doc:yard. If your changes are not 100% documented, go back to step 4.
  6. Add tests for your feature or bug fix.
  7. Run bundle exec rake test. If your changes are not 100% covered, go back to step 6.
  8. Commit and push your changes.
  9. 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 (c) 2010 Steve Richert, Erik Michaels-Ober. See LICENSE for details.