1# Contributing 2 31. Thanks for considering contributing to Web Page Replay. You're awesome! 42. Style Guide - The source code of Web Page Replay follows the [Google 5Python Style 6Guide](http://google-styleguide.googlecode.com/svn/trunk/pyguide.html) so you should familiarize yourself with those 7guidelines. You may also wish to email web-page-replay-dev at 8googlegroups.com for advice on your change before starting. 93. Get the code - Fork this repo and clone it locally. 104. Get a review - All submissions, including submissions by project members, 11require review. 12 13## Using rietveld 14 151. Make sure that you have a fork of the original repo. 162. Make your changes. 173. Commit your changes. 184. Run 'yes "" |git cl config' (first time only). 195. Run 'git cl upload'. 206. Once the review is approved, run 'git cl land' to land your changes. This also 21pushes your change to your forked branch. 227. Login your github account and make a pull request to merge the change from 23your forked branch to the original repo. 24 25## The fine print 26 27Before we can use your code you have to sign the [Google Individual 28Contributor License 29Agreement](http://code.google.com/legal/individual-cla-v1.0.html), which you can do online. This is mainly 30because you own the copyright to your changes, even after your 31contribution becomes part of our codebase, so we need your permission to 32use and distribute your code. We also need to be sure of various other 33things, for instance that you'll tell us if you know that your code 34infringes on other people's patents. You don't have to do this until 35after you've submitted your code for review and a member has approved 36it, but you will have to do it before we can put your code into our 37codebase. 38 39Contributions made by corporations are covered by a different agreement 40than the one above, the [Software Grant and Corporate Contributor License 41Agreement](http://code.google.com/legal/corporate-cla-v1.0.html). 42