| andybons | 3322f76 | 2015-08-24 21:37:09 | [diff] [blame^] | 1 | # Linux Development |
| 2 | |
| 3 | **Please join us on IRC for the most up-to-date development discussion: `irc.freenode.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 "Available" issues seem appropriate, you may be able to help an already claimed ("Assigned" or "Started") issue, but you'll probably want to coordinate with the claimants, 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 the code. If you grep for that you'll likely find plenty of small tasks to get started on. |
| 20 | |
| 21 | ### New Bugs |
| 22 | |
| 23 | If you think you have discovered a new Linux bug, start by [searching for similar 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 can't find a related bug, please create a [New Issue](http://code.google.com/p/chromium/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 |
