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