Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(74)

Side by Side Diff: tools/telemetry/third_party/webpagereplay/documentation/Contributing.md

Issue 1647513002: Delete tools/telemetry. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 # Contributing
2
3 1. Thanks for considering contributing to Web Page Replay. You're awesome!
4 2. Style Guide - The source code of Web Page Replay follows the [Google
5 Python Style
6 Guide](http://google-styleguide.googlecode.com/svn/trunk/pyguide.html) so you sh ould familiarize yourself with those
7 guidelines. You may also wish to email web-page-replay-dev at
8 googlegroups.com for advice on your change before starting.
9 3. Get the code - Fork this repo and clone it locally.
10 4. Get a review - All submissions, including submissions by project members,
11 require review.
12
13 ## Using rietveld
14
15 1. Make sure that you have a fork of the original repo.
16 2. Make your changes.
17 3. Commit your changes.
18 4. Run 'yes "" |git cl config' (first time only).
19 5. Run 'git cl upload'.
20 6. Once the review is approved, run 'git cl land' to land your changes. This als o
21 pushes your change to your forked branch.
22 7. Login your github account and make a pull request to merge the change from
23 your forked branch to the original repo.
24
25 ## The fine print
26
27 Before we can use your code you have to sign the [Google Individual
28 Contributor License
29 Agreement](http://code.google.com/legal/individual-cla-v1.0.html), which you can do online. This is mainly
30 because you own the copyright to your changes, even after your
31 contribution becomes part of our codebase, so we need your permission to
32 use and distribute your code. We also need to be sure of various other
33 things, for instance that you'll tell us if you know that your code
34 infringes on other people's patents. You don't have to do this until
35 after you've submitted your code for review and a member has approved
36 it, but you will have to do it before we can put your code into our
37 codebase.
38
39 Contributions made by corporations are covered by a different agreement
40 than the one above, the [Software Grant and Corporate Contributor License
41 Agreement](http://code.google.com/legal/corporate-cla-v1.0.html).
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698