docs/linux_development.md - Issue 1309473002: WIP: Migrate Wiki content over to src/docs

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: docs/linux_development.md

Issue 1309473002: WIP: Migrate Wiki content over to src/docs (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 5 years, 4 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
(Empty)
	1 # Linux Development

	2

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

	4

	5 ## Checkout and Build

	6 See the LinuxBuildInstructions.

	7

	8 ## What Needs Work

	9

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

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

	12

	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.

	14

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

	16

	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

	22

	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.

	24

	25 ## Contributing code

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

	27

	28 ## Debugging

	29 See LinuxDebugging.

	30

	31 ## Documents

	32

	33 LinuxGraphicsPipeline

OLD	NEW

« docs/linux_chromium64.md ('K') | « docs/linux_dev_build_as_default_browser.md ('k') | docs/linux_eclipse_dev.md » ('j') | docs/linux_make_build.md » ('J')