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