Skip to content

Commit 556c267

Browse files
committed
update to new attachment version and modernize boilerplate
1 parent 7144d01 commit 556c267

File tree

4 files changed

+49
-495
lines changed

4 files changed

+49
-495
lines changed

CONTRIBUTING.md

Lines changed: 27 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,28 @@
1-
# How to become a contributor and submit your own code
2-
3-
## Contributor License Agreements
4-
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.
7-
8-
Please fill out either the individual or corporate Contributor License Agreement
9-
(CLA).
10-
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-
(https://developers.google.com/open-source/cla/individual).
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-
(https://developers.google.com/open-source/cla/corporate).
17-
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.
21-
22-
## Contributing A Patch
23-
24-
1. Submit an issue describing your proposed change to the repo in question.
25-
1. The repo owner will respond to your issue promptly.
26-
1. If your proposed change is accepted, and you haven't already done so, sign a
27-
Contributor License Agreement (see details above).
28-
1. Fork the desired repo, develop and test your code changes.
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.
34-
1. Ensure that your code has an appropriate set of unit tests which all pass.
35-
1. Submit a pull request.
1+
# How to Contribute
362

3+
We'd love to accept your patches and contributions to this project. There are
4+
just a few small guidelines you need to follow.
5+
6+
## Contributor License Agreement
7+
8+
Contributions to this project must be accompanied by a Contributor License
9+
Agreement. You (or your employer) retain the copyright to your contribution;
10+
this simply gives us permission to use and redistribute your contributions as
11+
part of the project. Head over to <https://cla.developers.google.com/> to see
12+
your current agreements on file or to sign a new one.
13+
14+
You generally only need to submit a CLA once, so if you've already submitted one
15+
(even if it was for a different project), you probably don't need to do it
16+
again.
17+
18+
## Code reviews
19+
20+
All submissions, including submissions by project members, require review. We
21+
use GitHub pull requests for this purpose. Consult
22+
[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23+
information on using pull requests.
24+
25+
## Community Guidelines
26+
27+
This project follows [Google's Open Source Community
28+
Guidelines](https://opensource.google/conduct/).

0 commit comments

Comments
 (0)