site/dev/contrib/index.md - Issue 1579593002: docs: Fix link to 'How to submit a patch'.

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

Issue 1579593002: docs: Fix link to 'How to submit a patch'. (Closed) Base URL: https://skia.googlesource.com/skia.git@master

Patch Set: Created 4 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 | « no previous file | no next file » | no next file with comments »

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://bug.skia. org/).	10 Find bugs to fix or report new bugs in the [Skia issue tracker](http://bug.skia. org/).

(...skipping 10 matching lines...) Expand all Loading...
21	21

22 Contribute Code	22 Contribute Code

23 ---------------	23 ---------------

24	24

25 Whether you develop a new feature or a fix for an existing bug in the Skia code base,	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	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:	27 can speed up the review process:

28 Keep your code submissions small and targeted.	28 Keep your code submissions small and targeted.

29 When possible, have a fellow contributor review your change in advance of submis sion.	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	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).	31 skia-discuss ahead of development. For more information, see [How to submit a p atch](./contrib/submit).

32	32

33 For background on the project and an outline of the types of roles interested pa rties	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).	34 can take on, see [Project Roles](../../roles).

35	35

36 Anyone contributing code to Skia must sign a Contributor License Agreement and e nsure	36 Anyone contributing code to Skia must sign a Contributor License Agreement and e nsure

37 they are listed in the AUTHORS file:	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.	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)	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