Adding contributing file as per https://github.com/blog/1184-contributing-guidelines

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644 (file)
index 0000000..2ebc634
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,29 @@
+Contributing
+============
+
+To contribute, fork the library and install these npm packages.
+
+    npm install jshint uglify-js nodeunit
+
+You can add tests to the files in `/test/moment` or add a new test file if you are adding a new feature.
+
+To run the tests, do `make test` to run all tests, `make test-moment` to test the core library, and `make test-lang` to test all the languages.
+
+To check the filesize, you can use `make size`.
+
+To minify all the files, use `make moment` to minify moment, `make langs` to minify all the lang files, or just `make` to minfy everything.
+
+If your code passes the unit tests (including the ones you wrote), submit a pull request.
+
+Submitting pull requests
+========================
+
+Moment.js now uses [git-flow](https://github.com/nvie/gitflow). If you're not familiar with git-flow, please read up on it, you'll be glad you did.
+
+When submitting new features, please create a new feature branch using `git flow feature start <name>` and submit the pull request to the `develop` branch.
+
+Pull requests for enhancements for features should be submitted to the `develop` branch as well.
+
+When submitting a bugfix, please check if there is an existing bugfix branch. If the latest stable version is `1.5.0`, the bugfix branch would be `hotfix/1.5.1`. All pull requests for bug fixes should be on a `hotfix` branch, unless the bug fix depends on a new feature.
+
+The `master` branch should always have the latest stable version. When bugfix or minor releases are needed, the develop/hotfix branch will be merged into master and released.

diff --git a/readme.md b/readme.md
index a03792113e38697cb96710bb3c8fb98062c92291..4c3b61074fc84051f07cb2fcf765ca3307349002 100755 (executable)
--- a/readme.md
+++ b/readme.md
@@ -22,36 +22,6 @@ There are a few things being deprecated in the 1.6.0 release.
 3. The way to customize am/pm strings is being changed. This would only affect you if you created a custom language file. For more information, see [this issue](https://github.com/timrwood/moment/pull/222).
 
 
-Contributing
-============
-
-To contribute, fork the library and install these npm packages.
-
-    npm install jshint uglify-js nodeunit
-
-You can add tests to the files in `/test/moment` or add a new test file if you are adding a new feature.
-
-To run the tests, do `make test` to run all tests, `make test-moment` to test the core library, and `make test-lang` to test all the languages.
-
-To check the filesize, you can use `make size`.
-
-To minify all the files, use `make moment` to minify moment, `make langs` to minify all the lang files, or just `make` to minfy everything.
-
-If your code passes the unit tests (including the ones you wrote), submit a pull request.
-
-Submitting pull requests
-========================
-
-Moment.js now uses [git-flow](https://github.com/nvie/gitflow). If you're not familiar with git-flow, please read up on it, you'll be glad you did.
-
-When submitting new features, please create a new feature branch using `git flow feature start <name>` and submit the pull request to the `develop` branch.
-
-Pull requests for enhancements for features should be submitted to the `develop` branch as well.
-
-When submitting a bugfix, please check if there is an existing bugfix branch. If the latest stable version is `1.5.0`, the bugfix branch would be `hotfix/1.5.1`. All pull requests for bug fixes should be on a `hotfix` branch, unless the bug fix depends on a new feature.
-
-The `master` branch should always have the latest stable version. When bugfix or minor releases are needed, the develop/hotfix branch will be merged into master and released.
-
 Changelog
 =========
 
@@ -162,11 +132,11 @@ Added _date.lang() support.
 Added support for passing multiple formats to try to parse a date. _date("07-10-1986", ["MM-DD-YYYY", "YYYY-MM-DD"]);
 Made parse from string and single format 25% faster.
 
-### 0.5.2 
+### 0.5.2
 
 Buxfix for [issue 8](https://github.com/timrwood/underscore.date/pull/8) and [issue 9](https://github.com/timrwood/underscore.date/pull/9).
 
-### 0.5.1 
+### 0.5.1
 
 Buxfix for [issue 5](https://github.com/timrwood/underscore.date/pull/5).
 
@@ -177,11 +147,11 @@ Removed `_date.now()`, as it is a duplicate of `_date()` with no parameters.
 Removed `_date.isLeapYear(yearNuumber)`. Use `_date([yearNumber]).isLeapYear()` instead.
 Exposed customization options through the `_date.relativeTime`, `_date.weekdays`, `_date.weekdaysShort`, `_date.months`, `_date.monthsShort`, and `_date.ordinal` variables instead of the `_date.customize()` function.
 
-### 0.4.1 
+### 0.4.1
 
 Added date input formats for input strings.
 
-### 0.4.0 
+### 0.4.0
 
 Added underscore.date to npm. Removed dependancies on underscore.
 
@@ -191,7 +161,7 @@ Added `'z'` and `'zz'` to `_.date().format()`. Cleaned up some redundant code to
 
 ### 0.3.1
 
-Cleaned up the namespace. Moved all date manipulation and display functions to the _.date() object. 
+Cleaned up the namespace. Moved all date manipulation and display functions to the _.date() object.
 
 ### 0.3.0
 
@@ -225,4 +195,4 @@ copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
\ No newline at end of file
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.