Update CONTRIB.md

Marc Cohen · Marc Cohen · commit 66fd93369d08 · 2013-01-15T20:47:32.000-08:00
diff --git a/CONTRIB.md b/CONTRIB.md
@@ -21,10 +21,11 @@ Follow either of the two links above to access the appropriate CLA and instructi
 
 ## Submitting an Enhancement
 
-1. Sign a Contributor License Agreement (see details above).
+
 1. Submit an enhancement issue to the repo in question. This ensures that work isn't being duplicated and communicating your plan early also generally leads to better patches.
 1. The repo owner will respond to your enhancement issue promptly. Instructional value is the top priority when evaluating enhancements for this collection of repos. 
-1. If your enhancement issue is accepted, fork the desired repo, make your code changes and test your enhancement.
+1. If your enhancement issue is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
+1. fork the desired repo, make your code changes and test your enhancement.
 1. Ensure that your code adheres to the existing style in the sample to which you are contributing. Refer to the [Google Cloud Platform Samples Style Guide](https://github.com/GoogleCloudPlatform/Home/wiki/STYLE.html) for the recommended coding standards for this organization. In the event the existing style conflicts with the recommended style, the former takes precedence over the latter.
 1. Ensure that your code has an appropriate set of unit tests, which you have executed.
 1. Submit a pull request. A pull request should address one issue in the repo. Please don't mix more than one logical change per pull request, because it makes the history hard to follow.
@@ -34,8 +35,8 @@ Follow either of the two links above to access the appropriate CLA and instructi
 1. Sign a Contributor License Agreement (see details above).
 1. Submit an enhancement issue to the GoogleCloudPlatform/Template repo.
 1. The repo owner will respond to your enhancement issue promptly. Instructional value is the top priority when evaluating new app proposals for this collection of repos. 
-1. If your proposal is accepted, build your app in your own repo.
-1. Follow this naming convention for your new repo:
+1. If your proposal is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
+1. Create your own repo for your app following this naming convention:
     * {product}-{app-name}-{language}
     * products: appengine, compute, storage, bigquery, prediction, cloudsql
     * example:  appengine-guestbook-python
