| OLD | NEW |
|---|
| 1 Contributing to Skia | 1 Contributing to Skia |
| 2 ==================== | 2 ==================== |
| 3 | 3 |
| 4 Here some ways you can get involved and help us improve Skia. | 4 Here some ways you can get involved and help us improve Skia. |
| 5 | 5 |
| 6 | 6 |
| 7 Report Bugs | 7 Report Bugs |
| 8 ----------- | 8 ----------- |
| 9 | 9 |
| 10 Find bugs to fix or report new bugs in the [Skia issue tracker](http://code.goog
le.com/p/skia/issues/list). | 10 Find bugs to fix or report new bugs in the [Skia issue tracker](http://bug.skia.
org/). |
| 11 You can also search the [Chromium issue tracker](http://code.google.com/p/chromi
um/issues/list) for bugs related to graphics or Skia. | 11 You can also search the [Chromium issue tracker](http://code.google.com/p/chromi
um/issues/list) for bugs related to graphics or Skia. |
| 12 | 12 |
| 13 Test | 13 Test |
| 14 ---- | 14 ---- |
| 15 | 15 |
| 16 Write an application or tool that will exercise the Skia code differently than o
ur | 16 Write an application or tool that will exercise the Skia code differently than o
ur |
| 17 current set of tests and verify that Skia works as expected. Draw something | 17 current set of tests and verify that Skia works as expected. Draw something |
| 18 interesting and profile it to find ways to speed up Skia's implementation. | 18 interesting and profile it to find ways to speed up Skia's implementation. |
| 19 We cannot always fix issues or support every scenario, but we welcome any bugs | 19 We cannot always fix issues or support every scenario, but we welcome any bugs |
| 20 found so we can assess and prioritize them. (If you find _and_ fix a bug, even
better!) | 20 found so we can assess and prioritize them. (If you find _and_ fix a bug, even
better!) |
| (...skipping 18 matching lines...) Expand all Loading... |
| 39 If you are contributing on behalf of a corporation, fill out the [Corporate Cont
ributor License Agreement](https://developers.google.com/open-source/cla/corpora
te) | 39 If you are contributing on behalf of a corporation, fill out the [Corporate Cont
ributor License Agreement](https://developers.google.com/open-source/cla/corpora
te) |
| 40 and send it in as described on that page. | 40 and send it in as described on that page. |
| 41 If it is your first time submitting code or you have not previously done so, add
your | 41 If 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://ski
a.googlesource.com/skia/+/master/AUTHORS) as a part | 42 (or your organization's) name and contact info to the [AUTHORS file](https://ski
a.googlesource.com/skia/+/master/AUTHORS) as a part |
| 43 of your CL. | 43 of your CL. |
| 44 REVIEWERS: Before you LGTM a change, verify that the contributor is listed in th
e AUTHORS file. | 44 REVIEWERS: Before you LGTM a change, verify that the contributor is listed in th
e AUTHORS file. |
| 45 If they are not, a Googler must ensure that the individual or their corporation
has signed the | 45 If they are not, a Googler must ensure that the individual or their corporation
has signed the |
| 46 CLA by searching [go/cla-signers](https://goto.google.com/cla-signers). | 46 CLA by searching [go/cla-signers](https://goto.google.com/cla-signers). |
| 47 Then have an entry added to the AUTHORS file with the CL. | 47 Then have an entry added to the AUTHORS file with the CL. |
| 48 | 48 |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 1461613002:
Update all code site issue tracker links to point to bug.skia.org (Closed)
Base URL: https://skia.googlesource.com/skia@master