Changes for community PRs

Author: Eilon

CONTRIBUTING.md

@@ -1,11 +1,12 @@
-## How to contribute
+# How to contribute
 
-One of the easiest ways to contribute is to participate in discussions and discuss issues.
+One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
 
-## General feedback and discussions?
 
+## General feedback and discussions?
 Please start a discussion on the [Home repo issue tracker](https://github.com/aspnet/Home/issues).
 
+
 ## Bugs and feature requests?
 Please log a new issue in the appropriate GitHub repo. Here are some of the most common repos:
 
@@ -18,6 +19,7 @@ Please log a new issue in the appropriate GitHub repo. Here are some of the most
 
 The full repo list is [here](https://github.com/aspnet).
 
+
 ## Other discussions
 Our team members also monitor several other discussion forums:
 
@@ -27,7 +29,6 @@ Our team members also monitor several other discussion forums:
 
 
 ## Filing issues
-
 When filing issues, please use our [bug filing templates](https://github.com/aspnet/Home/wiki/Functional-bug-template).
 The best way to get your bug fixed is to be as detailed as you can be about the problem.
 Providing a minimal project with steps to reproduce the problem is ideal.
@@ -42,6 +43,29 @@ Here are questions you can answer before you file a bug to make sure you're not
 
 GitHub supports [markdown](http://github.github.com/github-flavored-markdown/), so when filing bugs make sure you check the formatting before clicking submit.
 
+
 ## Contributing code and content
+You will need to sign a [Contributor License Agreement](https://cla.msopentech.com) before submitting your pull request. To complete the Contributor License Agreement (CLA), you will need to submit a request via the form and then electronically sign the Contributor License Agreement when you receive the email containing the link to the document. This needs to only be done once for any Microsoft Open Technologies OSS project.
+
+Make sure you can build the code. Familiarize yourself with the project workflow and our coding conventions. If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests.
+
+Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that all code submissions will be rigorously reviewed and tested by the ASP.NET and Entity Framework teams, and only those that meet an extremely high bar for both quality and design/roadmap appropriateness will be merged into the source.
+
+Here's a few things you should always do when making changes to the code base:
+
+**Commit/Pull Request Format**
+
+```
+Summary of the changes (Less than 80 chars)
+ - Detail 1
+ - Detail 2
+
+#bugnumber (in this specific format)
+```
+
+**Tests**
 
-We are actively working to allow community code and content contributions. We can't accept code and content contributions yet, but check back soon for updates.
+-  Tests need to be provided for every bug/feature that is completed.
+-  Tests only need to be present for issues that need to be verified by QA (e.g. not tasks)
+-  If there is a scenario that is far too hard to test there does not need to be a test for it.
+  - "Too hard" is determined by the team as a whole.