Merge pull request GoogleCloudPlatform#15 from lesv/patch-1

We don't take full samples as a contribution.

Author: amygdala

CONTRIB.md

@@ -33,32 +33,3 @@ accept your pull requests.
  recommended coding standards for this organization.
 1. Ensure that your code has an appropriate set of unit tests which all pass.
 1. Submit a pull request.
-
-## Contributing A New Sample App
-
-1. Submit an issue to the GoogleCloudPlatform/Template repo describing your
- proposed sample app.
-1. The Template 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, 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
- * For multi-product apps, concatenate the primary products, like this:
- compute-appengine-demo-suite-python.
- * For multi-language apps, concatenate the primary languages like this:
- appengine-sockets-python-java-go.
-
-1. Clone the README.md, CONTRIB.md and LICENSE files from the
- GoogleCloudPlatform/Template repo.
-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/Template/wiki/style.html) for the
- recommended coding standards for this organization.
-1. Ensure that your code has an appropriate set of unit tests which all pass.
-1. Submit a request to fork your repo in GoogleCloudPlatform organizationt via
- your proposal issue.