@@ -1,11 +1,20 @@
1# Contributing to Elm
1# Contributing to Elm
3−Thanks helping with the development of Elm! **Here's how you can help.**
3+Thanks helping with the development of Elm! This document
4+describes the basic standards for opening pull requests:
5−## Opening a PR
6+## Branches
7−The master branch of Elm is used for tagging releases, and the dev branch is
8+ * The master branch of Elm is for tagging previous releases
9+ and non-breaking changes, like bug fixes. This branch is
10+ handy for folks who want to build the most recent public
8−where the most active development occurs.
13+ * The dev branch is where the most active development occurs.
14+ It is the home of the next release of the compiler so new
15+ features and improvements get merged there.
17+## Opening a pull request
10**Please open PRs against the [dev branch of
19**Please open PRs against the [dev branch of
11Elm](http://github.com/evancz/elm/tree/dev) whenever possible.** Changes that
20Elm](http://github.com/evancz/elm/tree/dev) whenever possible.** Changes that
@@ -22,5 +31,5 @@ sure that your changes maintain this compatibility.
23## Licensing
32## Licensing
25−You should sign the [contributor agreement](Contributor Agreement.docx?raw=true)
34+You should sign the [contributor agreement](ContributorAgreement.pdf)
26and send it to <info@elm-lang.org> before opening your pull request.
35and send it to <info@elm-lang.org> before opening your pull request.