Listed some rules for PRs in the contributing file
+Rules
+=====
+1. Only through Pull Requests can you submit changes or additions to the code
+2. Every Pull Request has to be reviewed by two team members
+3. New code should be covered 100% by unit tests
+4. Code should pass the `pylint` style check
+5. Functions, classes, methods should have a `Google-style docstring`.
+6. Larger new features should come with an example and narrative documentation.
-What's expected of a Pull Request
-=================================
-1. Non-trivial additions or changes to outputs or behavior should come with new or changed unit tests.
-2. Existing unit tests and other checks should pass.
+HIGHLY RECOMMENDED
+==================
+
+1. Commit often (every 10-30 minutes when you're coding)
+2. Open a Pull Request for your feature branch as soon as you start on it. This way the team can see your intentions
+and give your feedback early on, avoiding dissapointing news after you've put in a lot of work.
+
