Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Remove old contribution guidelines.

  • Loading branch information...
commit afaf72bbc47d12a8c6d1b1bd07599a24243fcc01 1 parent 76127ea
Gabe Berke-Williams gabebw authored
Showing with 0 additions and 38 deletions.
  1. +0 −38 CONTRIBUTION_GUIDELINES.rdoc
38 CONTRIBUTION_GUIDELINES.rdoc
View
@@ -1,38 +0,0 @@
-We love pull requests. Here's a quick guide:
-
-1. Fork the repo.
-
-2. Run the tests. We only take pull requests with passing tests, and it's great
-to know that you have a clean slate: `bundle && rake`
-
-3. Add a test for your change. Only refactoring and documentation changes
-require no new tests. If you are adding functionality or fixing a bug, we need
-a test!
-
-4. Make the test pass.
-
-5. Push to your fork and submit a pull request.
-
-
-At this point you're waiting on us. We like to at least comment on, if not
-accept, pull requests within a week. We may suggest some changes or
-improvements or alternatives.
-
-Some things that will increase the chance that your pull request is accepted,
-taken straight from the Ruby on Rails guide:
-
-* Use Rails idioms and helpers
-* Include tests that fail without your code, and pass with it
-* Update the documentation, the surrounding one, examples elsewhere, guides,
- whatever is affected by your contribution
-
-Syntax:
-
-* Two spaces, no tabs.
-* No trailing whitespace. Blank lines should not have any space.
-* Prefer &&/|| over and/or.
-* MyClass.my_method(my_arg) not my_method( my_arg ) or my_method my_arg.
-* a = b and not a=b.
-* Follow the conventions you see used in the source already.
-
-And in case we didn't emphasize it enough: we love tests!
Please sign in to comment.
Something went wrong with that request. Please try again.