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