Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(94)

Side by Side Diff: site/dev/contrib/index.md

Issue 844433004: Add Contributing to Skia section of docs (Closed) Base URL: https://skia.googlesource.com/skia.git@master
Patch Set: fix code block on flatten page Created 5 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « site/dev/contrib/flatten.md ('k') | site/dev/contrib/patch.md » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(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).
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
13 Test
14 ----
15
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
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
20 found so we can assess and prioritize them. (If you find _and_ fix a bug, even better!)
21
22 Contribute Code
23 ---------------
24
25 Whether you develop a new feature or a fix for an existing bug in the Skia code base,
26 you will need a committer to review and approve the change. There are some step s that
27 can speed up the review process:
28 Keep your code submissions small and targeted.
29 When possible, have a fellow contributor review your change in advance of submis sion.
30 Propose new features to the project leads by opening a feature bug or posting to
31 skia-discuss ahead of development. For more information, see [How to submit a p atch](./submit).
32
33 For background on the project and an outline of the types of roles interested pa rties
34 can take on, see [Project Roles](../../roles).
35
36 Anyone contributing code to Skia must sign a Contributor License Agreement and e nsure
37 they are listed in the AUTHORS file:
38 Individual contributors can complete the [Individual Contributor License Agreeme nt](https://developers.google.com/open-source/cla/individual) online.
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.
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
43 of your CL.
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
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.
48
OLDNEW
« no previous file with comments | « site/dev/contrib/flatten.md ('k') | site/dev/contrib/patch.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698