Add more contributing guidance.

richlander · richlander · commit 21c183dbbc0c · 2014-10-30T21:10:47.000-07:00
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -21,21 +21,24 @@ let everybody know that you want to work on it.
    is none, create one.
 2. Create a fork in GitHub
 3. Create a branch off the `master` branch. Name it something that that makes
-   sense, such as `issue-123`. This makes it easy for you to figure out what
-   the branch is used for.
+   sense, such as `issue-123` or `githubhandle-issue`. This makes it easy for everyone to figure out what
+   the branch is used for. It also makes it easier to isolate your change from incoming changes from the origin.
 4. Commit your changes and push your changes to GitHub
 5. Create a pull request against the origin's `master` branch
 
 ## DOs and DON'Ts
 
 * **DO** follow our coding style (see below)
-* **DON'T** surprise us with big pull requests. Instead, file an issue and start
-  a discussion so we can agree on a direction before you invest a large amount
-  of time.
 * **DO** include tests when adding new features. When fixing bugs, start with
   adding a test that highlights how the current behavior is broken.
 * **DO** keep the discussions focused. When a new or related topic comes up
   it's often better to create new issue than to side track the discussion.
+* **DO** blog and tweet (or whatever) about your contributions, frequently!
+* **DON'T** surprise us with big pull requests. Instead, file an issue and start
+  a discussion so we can agree on a direction before you invest a large amount
+  of time.
+* **DON'T** commit code that you didn't write. If you find MIT or Apache 2 licensed code that you think is a good fit to add to .NET Core, file an issue and start a discussion before proceeding.
+
 
 ## C# Coding Style
 
