Browse files

Move information about contributing to CONTRIBUTING.md

  • Loading branch information...
1 parent d214197 commit e32bb87017310e4d1ce8e5915ba2cf898a7a1061 @lautis committed Sep 24, 2012
Showing with 18 additions and 14 deletions.
  1. +17 −0 CONTRIBUTING.md
  2. +1 −14 README.md
View
17 CONTRIBUTING.md
@@ -0,0 +1,17 @@
+# Contributing to Uglifier
+
+Any contributions to Uglifier are welcome, whether they are feedback, bug reports, or - even better - pull requests.
+
+## Reporting issues
+
+Uglifier uses the [GitHub issue tracker](https://github.com/lautis/uglifier/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 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, **MultiJSON engine** and **ExecJS runtime**. Ideally, a bug report should include a pull request with failing specs.
+
+## Contributing to uglifier
+
+* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
+* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
+* Fork the project
+* Start a feature/bugfix branch
+* Commit and push until you are happy with your contribution
+* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
View
15 README.md
@@ -58,20 +58,7 @@ Uglifier uses [stitch](https://github.com/sstephenson/stitch) to compile UglifyJ
node build.js
-## Submitting an issue
-
-Uglifier uses the [GitHub issue tracker](https://github.com/lautis/uglifier/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 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, **MultiJSON engine** and **ExecJS runtime**. Ideally, a bug report should include a pull request with failing specs.
-
-## Contributing to uglifier
-
-* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
-* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
-* Fork the project
-* Start a feature/bugfix branch
-* Commit and push until you are happy with your contribution
-* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
-* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
-
+See [CONTRIBUTING](https://github.com/lautis/uglifier/blob/master/CONTRIBUTING.md) for details about contributing to Uglifier.
## Copyright

0 comments on commit e32bb87

Please sign in to comment.