+made as an MIT/X11 license which grants us the same rights, but
+involves no paperwork. For the latter case, please specify on your
+commit(s) that you are licensing the changes under MIT/X11.
+
+For other parts of the project that are dual-licensed, please state
+on your commit(s) what license you are contributing the changes under.
+
+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.