1Contributing to Skia
2====================
3
4Here some ways you can get involved and help us improve Skia.
5
6
7Report Bugs
8-----------
9
10Find bugs to fix or report new bugs in the [Skia issue tracker](http://bug.skia.org/).
11You can also search the [Chromium issue tracker](http://code.google.com/p/chromium/issues/list) for bugs related to graphics or Skia.
12
13Test
14----
15
16Write an application or tool that will exercise the Skia code differently than our
17current set of tests and verify that Skia works as expected.  Draw something
18interesting and profile it to find ways to speed up Skia's implementation.
19We cannot always fix issues or support every scenario, but we welcome any bugs
20found so we can assess and prioritize them.  (If you find _and_ fix a bug, even better!)
21
22Contribute Code
23---------------
24
25Whether you develop a new feature or a fix for an existing bug in the Skia code base,
26you will need a committer to review and approve the change.  There are some steps that
27can speed up the review process:
28Keep your code submissions small and targeted.
29When possible, have a fellow contributor review your change in advance of submission.
30Propose new features to the project leads by opening a feature bug or posting to
31skia-discuss ahead of development.  For more information, see [How to submit a patch](./contrib/submit).
32
33For background on the project and an outline of the types of roles interested parties
34can take on, see [Project Roles](../../roles).
35
36Anyone contributing code to Skia must sign a Contributor License Agreement and ensure
37they are listed in the AUTHORS file:
38Individual contributors can complete the [Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual) online.
39If you are contributing on behalf of a corporation, fill out the [Corporate Contributor License Agreement](https://developers.google.com/open-source/cla/corporate)
40and send it in as described on that page.
41If it is your first time submitting code or you have not previously done so, add your
42(or your organization's) name and contact info to the [AUTHORS file](https://skia.googlesource.com/skia/+/master/AUTHORS) as a part
43of your CL.
44REVIEWERS: Before you LGTM a change, verify that the contributor is listed in the AUTHORS file.
45If they are not, a Googler must ensure that the individual or their corporation has signed the
46CLA by searching [go/cla-signers](https://goto.google.com/cla-signers).
47Then have an entry added to the AUTHORS file with the CL.
48
49