Update CONTRIB.md

Marc Cohen · Marc Cohen · commit f677c5af651f · 2013-01-15T20:03:01.000-08:00
diff --git a/CONTRIB.md b/CONTRIB.md
@@ -11,11 +11,20 @@ Please fill out either the individual or corporate Contributor License Agreement
 
 Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.
 
-## Submitting Patches
+## Submitting a Bug Fix
 
 1. Sign a Contributor License Agreement (see details above).
-1. Coordinate your plans with team members that are listed on the repo in question. This ensures that work isn't being duplicated and communicating your plan early also generally leads to better patches.
-1. Fork the desired repo, make and test your changes
+1. Fork the desired repo, make code changes and test your bug fix.
+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.
+
+## 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. 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.
