1*e47783fdSXin LiWant to contribute? Great! First, read this page (including the small print at the end). 2*e47783fdSXin Li 3*e47783fdSXin Li### Before you contribute 4*e47783fdSXin LiBefore we can use your code, you must sign the 5*e47783fdSXin Li[Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1) 6*e47783fdSXin Li(CLA), which you can do online. The CLA is necessary mainly because you own the 7*e47783fdSXin Licopyright to your changes, even after your contribution becomes part of our 8*e47783fdSXin Licodebase, so we need your permission to use and distribute your code. We also 9*e47783fdSXin Lineed to be sure of various other things—for instance that you'll tell us if you 10*e47783fdSXin Liknow that your code infringes on other people's patents. You don't have to sign 11*e47783fdSXin Lithe CLA until after you've submitted your code for review and a member has 12*e47783fdSXin Liapproved it, but you must do it before we can put your code into our codebase. 13*e47783fdSXin LiBefore you start working on a larger contribution, you should get in touch with 14*e47783fdSXin Lius first through the issue tracker with your idea so that we can help out and 15*e47783fdSXin Lipossibly guide you. Coordinating up front makes it much easier to avoid 16*e47783fdSXin Lifrustration later on. 17*e47783fdSXin Li 18*e47783fdSXin Li### Code reviews 19*e47783fdSXin LiAll submissions, including submissions by project members, require review. We 20*e47783fdSXin Liuse Github pull requests for this purpose. 21*e47783fdSXin Li 22*e47783fdSXin Li### The small print 23*e47783fdSXin LiContributions made by corporations are covered by a different agreement than 24*e47783fdSXin Lithe one above, the Software Grant and Corporate Contributor License Agreement. 25