126fa459cSmrgWant to contribute? Great! First, read this page (including the small print at 226fa459cSmrgthe end). 326fa459cSmrg 426fa459cSmrg### Before you contribute 526fa459cSmrgBefore we can use your code, you must sign the 626fa459cSmrg[Google Individual Contributor License Agreement] 726fa459cSmrg(https://cla.developers.google.com/about/google-individual) 826fa459cSmrg(CLA), which you can do online. The CLA is necessary mainly because you own the 926fa459cSmrgcopyright to your changes, even after your contribution becomes part of our 1026fa459cSmrgcodebase, so we need your permission to use and distribute your code. We also 1126fa459cSmrgneed to be sure of various other things—for instance that you'll tell us if you 1226fa459cSmrgknow that your code infringes on other people's patents. You don't have to sign 1326fa459cSmrgthe CLA until after you've submitted your code for review and a member has 1426fa459cSmrgapproved it, but you must do it before we can put your code into our codebase. 1526fa459cSmrgBefore you start working on a larger contribution, you should get in touch with 1626fa459cSmrgus first through the issue tracker with your idea so that we can help out and 1726fa459cSmrgpossibly guide you. Coordinating up front makes it much easier to avoid 1826fa459cSmrgfrustration later on. 1926fa459cSmrg 2026fa459cSmrg### Code reviews 2126fa459cSmrgAll submissions, including submissions by project members, require review. We 2226fa459cSmrguse Github pull requests for this purpose. 2326fa459cSmrg 2426fa459cSmrg### The small print 2526fa459cSmrgContributions made by corporations are covered by a different agreement than 2626fa459cSmrgthe one above, the [Software Grant and Corporate Contributor License Agreement] 2726fa459cSmrg(https://cla.developers.google.com/about/google-corporate). 28