OLD | NEW |
(Empty) | |
| 1 Contributing to Skia |
| 2 ==================== |
| 3 |
| 4 Here some ways you can get involved and help us improve Skia. |
| 5 |
| 6 |
| 7 Report Bugs |
| 8 ----------- |
| 9 |
| 10 Find bugs to fix or report new bugs in the [Skia issue tracker](http://code.goog
le.com/p/skia/issues/list). You can also search the [Chromium issue tracker](ht
tp://code.google.com/p/chromium/issues/list) for bugs related to graphics or Ski
a. |
| 11 |
| 12 Test |
| 13 ---- |
| 14 |
| 15 Write an application or tool that will exercise the Skia code differently than o
ur current set of tests and verify that Skia works as expected. Draw something
interesting and profile it to find ways to speed up Skia's implementation. We c
annot always fix issues or support every scenario, but we welcome any bugs found
so we can assess and prioritize them. (If you find _and_ fix a bug, even bette
r!) |
| 16 |
| 17 Contribute Code |
| 18 --------------- |
| 19 |
| 20 Whether you develop a new feature or a fix for an existing bug in the Skia code
base, you will need a committer to review and approve the change. There are som
e steps that can speed up the review process: Keep your code submissions small
and targeted. When possible, have a fellow contributor review your change in ad
vance of submission. Propose new features to the project leads by opening an en
hancement or posting to skia-discuss ahead of development. For more information
, see [How to submit a patch](./submit). |
| 21 |
| 22 For background on the project and an outline of the types of roles interested pa
rties can take on, see [Project Roles](../../roles). |
| 23 |
| 24 Anyone contributing code to Skia must sign a Contributor License Agreement and e
nsure they are listed in the AUTHORS file: |
| 25 Individual contributors can complete the [Individual Contributor License Agreeme
nt](https://developers.google.com/open-source/cla/individual) online. If you ar
e contributing on behalf of a corporation, fill out the [Corporate Contributor L
icense Agreement](https://developers.google.com/open-source/cla/corporate) and s
end it in as described on that page. |
| 26 If it is your first time submitting code or you have not previously done so, add
your (or your organization's) name and contact info to the [AUTHORS file](https
://skia.googlesource.com/skia/+/master/AUTHORS) as a part of your CL. |
| 27 REVIEWERS: Before you LGTM a change, verify that the contributor is listed in th
e AUTHORS file. If they are not, a Googler must ensure that the individual or t
heir corporation has signed the CLA by searching [go/cla-signers](https://goto.g
oogle.com/cla-signers). Then have an entry added to the AUTHORS file with the C
L. |
| 28 |
OLD | NEW |