@@ -2,6 +2,10 @@ An introductory overview of the compiler is available [here](https://www.youtube
22
33Pull requests are encouraged.
44
5+## Finding Issues to Work On
6+
7+If you would like to contribute, please consider the issues in the current milestone first. If you are a new contributor, you may want to have a go at the ["easy" issues](https://github.com/purescript/purescript/labels/easy) to get started.
8+
59## Pull Requests
610
711Please follow the following guidelines:
@@ -9,12 +13,10 @@ Please follow the following guidelines:
913- Add at least a test to `examples/passing/` and possibly to `examples/failing`.
1014- Build the binaries and libs with `cabal build`
1115- Install the binaries and libs with `cabal install`.
12−- Run `cabal configure --enable-tests && cabal build && cabal test` to build the test suite. You will need `npm`, `node`, and `bower` on your PATH to run the tests.
16+- Run `cabal configure --enable-tests && cabal build && cabal test` to build the test suite. You will need `npm` and `node` on your PATH to run the tests.
1317- Build the core libraries by running the script in `core-tests`.
1418
15−If you would like to contribute, please consider the issues in the current milestone first. If you are a new contributor, you may want to have a go at the ["easy" issues](https://github.com/purescript/purescript/labels/easy) to get started.
16−
17−Finally, if you have made code changes and would like to be included in the copyright notice in the cabal file, please include that change in your pull request.
19+## Code Review
1820
1921To prevent core libraries from getting broken, every change must be reviewed. A pull request will be merged as long as one other team member has verified the changes.
2022