docs/linux_development.md - Issue 1324603002: [Docs] Another round of stylistic fixes.

Side by Side Diff: docs/linux_development.md

Issue 1324603002: [Docs] Another round of stylistic fixes. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 5 years, 3 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

OLD	NEW
1 # Linux Development	1 # Linux Development

2	2

3 Please join us on IRC for the most up-to-date development discussion: `irc.fre enode.net`, `#chromium`	3 **Please join us on IRC for the most up-to-date development discussion:

	4 `irc.freenode.net`, `#chromium`**

4	5

5 ## Checkout and Build	6 ## Checkout and Build

6 See the LinuxBuildInstructions.	7

	8 See the [Linux build instructions](linux_build_instructions.md).

7	9

8 ## What Needs Work	10 ## What Needs Work

9	11

10 Look at the Chromium bug tracker for open Linux issues:	12 Look at the Chromium bug tracker for open Linux issues:

11 http://code.google.com/p/chromium/issues/list?can=2&q=os%3Alinux	13 http://code.google.com/p/chromium/issues/list?can=2&q=os%3Alinux

12	14

13 Issues marked "Available" are ready for someone to claim. To claim an issue, add a comment and then a project member will mark it "Assigned". If none of the "Av ailable" issues seem appropriate, you may be able to help an already claimed ("A ssigned" or "Started") issue, but you'll probably want to coordinate with the cl aimants, to avoid unnecessary duplication of effort.	15 Issues marked "Available" are ready for someone to claim. To claim an issue, add

	16 a comment and then a project member will mark it "Assigned". If none of the

	17 "Available" issues seem appropriate, you may be able to help an already claimed

	18 ("Assigned" or "Started") issue, but you'll probably want to coordinate with the

	19 claimants, to avoid unnecessary duplication of effort.

14	20

15 Issues marked with HelpWanted are a good place to start.	21 Issues marked with HelpWanted are a good place to start.

16	22

17 ### Random TODOs

18

19 We've also marked bits that remain to be done for porting with `TODO(port)` in t he code. If you grep for that you'll likely find plenty of small tasks to get s tarted on.

20

21 ### New Bugs	23 ### New Bugs

22	24

23 If you think you have discovered a new Linux bug, start by [searching for simila r issues](http://code.google.com/p/chromium/issues/list?can=1&q=Linux). When you search, make sure you choose the "All Issues" option, since your bug might have already been fixed, but the default search only looks for open issues. If you c an't find a related bug, please create a [New Issue](http://code.google.com/p/ch romium/issues/entry). Use the linux defect template.	25 If you think you have discovered a new Linux bug, start by

	26 [searching for similar issues](http://code.google.com/p/chromium/issues/list?can =1&q=Linux).

	27 When you search, make sure you choose the "All Issues" option, since your bug

	28 might have already been fixed, but the default search only looks for open

	29 issues. If you can't find a related bug, please create a

	30 [New Issue](https://crbug.com/new). Use the linux defect template.

24	31

25 ## Contributing code	32 ## Contributing code

	33

26 See [ContributingCode](http://dev.chromium.org/developers/contributing-code).	34 See [ContributingCode](http://dev.chromium.org/developers/contributing-code).

27	35

28 ## Debugging	36 ## Debugging

29 See LinuxDebugging.	37

	38 See [linux_debugging.md](linux_debugging.md).

30	39

31 ## Documents	40 ## Documents

32	41

33 LinuxGraphicsPipeline	42 [linux_graphics_pipeline.md](linux_graphics_pipeline.md)

OLD	NEW

« no previous file with comments | « docs/linux_dev_build_as_default_browser.md ('k') | docs/linux_eclipse_dev.md » ('j') | no next file with comments »