Permalink
Browse files

Adds contributing file [ci skip]

  • Loading branch information...
1 parent da758de commit 7940c5ec806b864048325d01ebef2b54c1fb26fc @ryanatwork ryanatwork committed Sep 17, 2012
Showing with 41 additions and 43 deletions.
  1. +40 −0 CONTRIBUTING.mkd
  2. +1 −43 README.md
View
@@ -0,0 +1,40 @@
+Here are some ways *you* can contribute:
+
+* by using alpha, beta, and prerelease versions
+* by reporting bugs
+* by suggesting new features
+* by [translating to a new language][locales]
+* 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
+
+[locales]: https://github.com/democrats/voter-registration/tree/master/config/locales
+[issues]: https://github.com/democrats/voter-registration/issues
+
+## Submitting an Issue
+We use the [GitHub issue tracker][issues] 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 issue 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.
+
+[gist]: https://gist.github.com/
+
+## Submitting a Pull Request
+1. Fork the project.
+2. Create a topic branch. (`git checkout -b my_awesome_branch`)
+3. Implement your feature or bug fix.
+4. Add tests for your feature or bug fix.
+5. Run `bundle exec rake spec`. If your changes are not 100% covered, go back
+ to step 4.
+6. Commit your changes. (`git commit -am "Added some cool things"`)
+7. Push to the branch (`git push origin my_awesome_branch`)
+8. Submit a [pull request](https://help.github.com/articles/using-pull-requests/)
+
+
View
@@ -66,49 +66,7 @@ implementations:
* Ruby 1.9.3
## Contributing
-In the spirit of [free software][free-sw], **everyone** is encouraged to help
-improve this project.
-
-[free-sw]: http://www.fsf.org/licensing/essays/free-sw.html
-
-Here are some ways *you* can contribute:
-
-* by using alpha, beta, and prerelease versions
-* by reporting bugs
-* by suggesting new features
-* by [translating to a new language][locales]
-* 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
-
-[locales]: https://github.com/democrats/voter-registration/tree/master/config/locales
-[issues]: https://github.com/democrats/voter-registration/issues
-
-## Submitting an Issue
-We use the [GitHub issue tracker][issues] 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 issue 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.
-
-[gist]: https://gist.github.com/
-
-## Submitting a Pull Request
-1. Fork the project.
-2. Create a topic branch. (`git checkout -b my_awesome_branch`)
-3. Implement your feature or bug fix.
-4. Add tests for your feature or bug fix.
-5. Run `bundle exec rake spec`. If your changes are not 100% covered, go back
- to step 4.
-6. Commit your changes. (`git commit -am "Added some cool things"`)
-7. Push to the branch (`git push origin my_awesome_branch`)
-8. Submit a [pull request](https://help.github.com/articles/using-pull-requests/)
+Check out [contributing](contributing.mkd) for ways that you can contribute
## Documentation

0 comments on commit 7940c5e

Please sign in to comment.