-When contributing code, make sure that your contribution falls under
-the appropriate license. For example, contributions to code licensed
-under MIT X11 code, should be MIT X11 code.
+CLA
+=======
+
+Contributions are now taken under the [.NET Foundation CLA] (https://cla2.dotnetfoundation.org/).
+
+Testing
+=======
+
+Pull requests go through testing on our [Jenkins server][2]. We will
+usually only merge a pull request if it causes no regressions in a
+test run there.
+
+When you submit a pull request, one of two things happens:
+
+* If you are a new contributor, Jenkins will ask for permissions (on
+ the pull request) to test it. A maintainer will reply to approve
+ the test run if they find the patch appropriate. After you have
+ submitted a few patches, a maintainer will whitelist you so that
+ all of your future pull requests are tested automatically.
+* If you are a well-known, whitelisted contributor, Jenkins will go
+ ahead and test your pull request as soon as a test machine is
+ available.
+
+When your pull request has been built, Jenkins will update the build
+status of your pull request. If it succeeded and we like the changes,
+a maintainer will likely merge it. Otherwise, you can amend your pull
+request to fix build breakage and Jenkins will test it again.
+
+[2]: http://jenkins.mono-project.com/