|
2 | 2 |
|
3 | 3 | ## Contributor License Agreements |
4 | 4 |
|
5 | | -We'd love to accept your sample apps and patches! Before we can take them, we have to jump a couple of legal hurdles. |
| 5 | +We'd love to accept your sample apps and patches! Before we can take them, we |
| 6 | +have to jump a couple of legal hurdles. |
6 | 7 |
|
7 | | -Please fill out either the individual or corporate Contributor License Agreement (CLA). |
| 8 | +Please fill out either the individual or corporate Contributor License Agreement |
| 9 | +(CLA). |
8 | 10 |
|
9 | | - * If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html). |
10 | | - * If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html). |
| 11 | + * If you are an individual writing original source code and you're sure you |
| 12 | + own the intellectual property, then you'll need to sign an [individual CLA] |
| 13 | + (http://code.google.com/legal/individual-cla-v1.0.html). |
| 14 | + * If you work for a company that wants to allow you to contribute your work, |
| 15 | + then you'll need to sign a [corporate CLA] |
| 16 | + (http://code.google.com/legal/corporate-cla-v1.0.html). |
11 | 17 |
|
12 | | -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. |
| 18 | +Follow either of the two links above to access the appropriate CLA and |
| 19 | +instructions for how to sign and return it. Once we receive it, we'll be able to |
| 20 | +accept your pull requests. |
13 | 21 |
|
14 | 22 | ## Contributing A Patch |
15 | 23 |
|
16 | 24 | 1. Submit an issue describing your proposed change to the repo in question. |
17 | 25 | 1. The repo owner will respond to your issue promptly. |
18 | | -1. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above). |
| 26 | +1. If your proposed change is accepted, and you haven't already done so, sign a |
| 27 | + Contributor License Agreement (see details above). |
19 | 28 | 1. Fork the desired repo, develop and test your code changes. |
20 | | -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. |
| 29 | +1. Ensure that your code adheres to the existing style in the sample to which |
| 30 | + you are contributing. Refer to the |
| 31 | + [Google Cloud Platform Samples Style Guide] |
| 32 | + (https://github.com/GoogleCloudPlatform/Template/wiki/style.html) for the |
| 33 | + recommended coding standards for this organization. |
21 | 34 | 1. Ensure that your code has an appropriate set of unit tests which all pass. |
22 | 35 | 1. Submit a pull request. |
23 | 36 |
|
24 | 37 | ## Contributing A New Sample App |
25 | 38 |
|
26 | | -1. Submit an issue to the GoogleCloudPlatform/Template repo describing your proposed sample app. |
27 | | -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. |
28 | | -1. If your proposal is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above). |
| 39 | +1. Submit an issue to the GoogleCloudPlatform/Template repo describing your |
| 40 | + proposed sample app. |
| 41 | +1. The Template repo owner will respond to your enhancement issue promptly. |
| 42 | + Instructional value is the top priority when evaluating new app proposals for |
| 43 | + this collection of repos. |
| 44 | +1. If your proposal is accepted, and you haven't already done so, sign a |
| 45 | + Contributor License Agreement (see details above). |
29 | 46 | 1. Create your own repo for your app following this naming convention: |
30 | 47 | * {product}-{app-name}-{language} |
31 | 48 | * products: appengine, compute, storage, bigquery, prediction, cloudsql |
32 | 49 | * example: appengine-guestbook-python |
33 | | - * For multi-product apps, concatenate the primary products, like this: compute-appengine-demo-suite-python. |
34 | | - * For multi-language apps, concatenate the primary languages like this: appengine-sockets-python-java-go. |
35 | | -1. Clone the README.md, CONTRIB.md and LICENSE files from the GoogleCloudPlatform/Template repo. |
36 | | -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. |
| 50 | + * For multi-product apps, concatenate the primary products, like this: |
| 51 | + compute-appengine-demo-suite-python. |
| 52 | + * For multi-language apps, concatenate the primary languages like this: |
| 53 | + appengine-sockets-python-java-go. |
| 54 | + |
| 55 | +1. Clone the README.md, CONTRIB.md and LICENSE files from the |
| 56 | + GoogleCloudPlatform/Template repo. |
| 57 | +1. Ensure that your code adheres to the existing style in the sample to which |
| 58 | + you are contributing. Refer to the |
| 59 | + [Google Cloud Platform Samples Style Guide] |
| 60 | + (https://github.com/GoogleCloudPlatform/Template/wiki/style.html) for the |
| 61 | + recommended coding standards for this organization. |
37 | 62 | 1. Ensure that your code has an appropriate set of unit tests which all pass. |
38 | | -1. Submit a request to fork your repo in GoogleCloudPlatform organizationt via your proposal issue. |
| 63 | +1. Submit a request to fork your repo in GoogleCloudPlatform organizationt via |
| 64 | + your proposal issue. |
0 commit comments