Chromium Code Reviews Chromium Code Reviews
Issue 1309473002:
WIP: Migrate Wiki content over to src/docs (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Key note | |
| 2 | |
| 3 Thanks for your interest in the GSoC 2010 for Chromium. Before applying, make su re you have checked out, built chromium and run the unit\_tests. Visit http://de v.chromium.org/ for the guidelines. Once you've done that (and not before), feel free to contact your potential mentor on the chromium irc channel. | |
|
Bons
2015/08/20 20:16:50
propose deletion due to this doc being 5 years old
| |
| 4 | |
| 5 We'd like to see you take an idea and flesh it out as much as possible, demonstr ating how you'd accomplish it within the context of the Chromium codebase and ho w long it would take you. Please do not just copy and paste the project idea and submit that as your proposal, as that does not demonstrate any knowledge of Chr omium and gives us very little to go on. The more detail and specifics you provi de, the better chance you have at being accepted. If providing this level of det ail proves too difficult, it might be a good indication you would have significa nt trouble during the Summer. | |
| 6 Projects | |
| 7 | |
| 8 # Chromium Projects | |
| 9 Email: chromium-dev@chromium.org | |
| 10 IRC: irc.freenode.net #chromium | |
| 11 | |
| 12 ## Improve BiDi support in WebKit and Chromium | |
| 13 | |
| 14 **Contact/Mentor**: Jeremy Moskovich (jeremy@chromium.org)<br> | |
| 15 <b>Difficulty</b>: varied<br> | |
| 16 <br> | |
| 17 There remain a number of issues with BiDi language support in WebKit & Chromium. The tasks involved cover a variety of of areas of the code, a list of open BiD i issues can be found in WebKit & Chromium bug trackers.<br> | |
| 18 <br> | |
| 19 Some sample tasks:<br> | |
| 20 <ul><li>Add support for auto-directionality to Chromium textboxes - easy<br> | |
| 21 </li><li>Layout tests for WebKit BiDi issues - easy<br> | |
| 22 </li><li>Support split/directional caret when editing bidi text - hard<br> | |
| 23 </li><li>Better BiDi support in Chromium omnibox - medium</li></ul> | |
| 24 | |
| 25 <h2>Port C/C++ Libraries and Applications to Native Client</h2> | |
| 26 | |
| 27 <b>Contact/Mentor</b>: Brad Chen (bradchen@google.com)<br> | |
| 28 <b>Difficulty</b>: varied<br> | |
| 29 <br> | |
| 30 Native Client adds native code execution capabilities to Chromium and other brow sers. For this project, we would like to port interesting native applications an d libraries to Native Client. Examples of libraries that have already been porte d include Cairo, QT, Mesa and ImageMagick. We've also ported a couple languages (Ruby, Lua, Awk) and are working on porting the game Nexuiz.<br> | |
| 31 <br> | |
| 32 <h2>Frontend for build status</h2> | |
| 33 | |
| 34 <b>Contact/Mentor</b>: Marc-Antoine Ruel (maruel@chromium.org)<br> | |
| 35 <b>Difficulty</b>: easy<br> | |
| 36 <b>Areas</b>: python, HTML, canvas, AJAX, doesn't require C++ experience.<br> | |
| 37 <br> | |
| 38 The Chromium team uses a <a href='http://src.chromium.org/viewvc/chrome/trunk/to ols/buildbot'>forked</a> 0.7.12 <a href='http://github.com/nsylvain/buildbot/'>v ersion</a> of <a href='http://buildbot.net'>buildbot</a>. Buildbot is used by <a href='http://build.webkit.org'>webkit</a> among <a href='http://buildbot.net/tr ac/wiki/SuccessStories'>others</a> and mozilla is actively contributing to it to wards 0.8.0.<br> | |
| 39 <br> | |
| 40 We are writing a buildbot <a href='http://src.chromium.org/viewvc/chrome/trunk/t ools/aebuild'>frontend</a> on <a href='http://code.google.com/appengine/docs/pyt hon/gettingstarted/'>AppEngine</a> in<br> | |
| 41 python to separate status serving from the actual builds control. It uses <a hre f='http://www.djangoproject.com'>django</a>.<br> | |
| 42 <br> | |
| 43 We have an open ended position for a frontend project. We'd like to have someone to write new awesome presentations interfaces using newer HTML technologies ins tead of prerendering them server-side. The tasks are:<br> | |
| 44 <ul><li>an AJAX-y Canvas-based <a href='http://build.chromium.org/buildbot/water fall/waterfall'>waterfall</a> to replace the <a href='http://github.com/djmitche /buildbot/blob/master/buildbot/status/web/waterfall.py'>current</a> table based one.<br> | |
| 45 </li><li>Figure out a new original way to present information from the try serve r useful for both the <a href='http://tryconsole.appspot.com'>users</a> (<a href ='http://codereview.chromium.org/517046'>sources</a>) and the try server <a href ='http://build.chromium.org/buildbot/try-server/waterfall'>maintainer</a> and is efficient server-side. We assume it'd require 2 differents layouts but better i deas are welcome.<br> | |
| 46 </li><li>(optional) Make the <a href='http://build.chromium.org/buildbot/waterfa ll/console'>console</a> view work with git.</li></ul> | |
| 47 | |
| 48 As specified above, most of the work will be happening <a href='http://src.chrom ium.org/viewvc/chrome/trunk/tools/aebuild'>http://src.chromium.org/viewvc/chrome /trunk/tools/aebuild</a>.<br> | |
| 49 <br> | |
| 50 <i>Bonus points if the new presentation layers are usable on a cell phone.</i> | |
| 51 | |
| 52 <h2>(Mac) AppleScript support</h2> | |
| 53 | |
| 54 <b>Contact/Mentor</b>: Mike Pinkerton (pinkerton@chromium.org)<br> | |
| 55 <b>Difficulty</b>: medium<br> | |
| 56 <b>Areas</b>: C++, Objective-C, Cocoa, AppleScript<br> | |
| 57 <br> | |
| 58 Many third-party applications utilize AppleScript to automate user tasks and col lect information from running applications, however Chromium is mostly left out as there is very little AppleScript support beyond the basic "open url" event. F or starters, we would like to add a full suite for tab and window actions, follo wed by whatever else seems appropriate.<br> | |
| 59 <br> | |
| 60 Chromium has a concept of an "automation proxy" which is used primarily from aut omated UI tests to drive the browser from an external process (C++ or python). T his AutomationProxy object is a good starting point.<br> | |
| 61 <br> | |
| 62 <h2>(Mac) Improve Drag and Drop Experience</h2> | |
| 63 | |
| 64 <b>Contact/Mentor</b>: Mike Pinkerton (pinkerton@chromium.org)<br> | |
| 65 <b>Difficulty</b>: medium<br> | |
| 66 <b>Areas</b>: C++, Objective-C, Cocoa<br> | |
| 67 <br> | |
| 68 The drag and drop experience in Mac Chromium is substandard in various areas:<br > | |
| 69 <br> | |
| 70 <ul><li>Dragging text and links from the web contents doesn't show a transparent thumbnail like in other apps<br> | |
| 71 </li><li>HTML5 drag-n-drop has no preview images either<br> | |
| 72 </li><li>Dragging bookmarks around on the bookmark bar should move others out of the way, like the tab strip.</li></ul> | |
| 73 | |
| 74 <h2>(Mac) Fixing ColorSync issues, fully enable pixel tests on 10.5 and 10.6</h2 > | |
| 75 | |
| 76 <b>Contact/Mentor</b>: Mike Pinkerton (pinkerton@chromium.org)<br> | |
| 77 <b>Difficulty</b>: medium<br> | |
| 78 <b>Areas</b>: C++, Objective-C, Cocoa, WebKit, ColorSync<br> | |
| 79 <br> | |
| 80 Pixel tests for WebKit layout tests are currently enabled for Mac OS X but due t o color differences caused by both our own color space bugs and factors beyond o ur control (HITheme vs. Cocoa scrollbar drawing differences), many are disabled. The following needs doing:<br> | |
| 81 <br> | |
| 82 <ul><li>Solving the remaining color space issues on 10.5 and 10.6 that cause rea l bugs in incorrectly rendering images and colors<br> | |
| 83 </li><li>Weed out which tests fail due to real bugs and which fail due to theme drawing issues.<br> | |
| 84 </li><li>Rebaselining tests that were baselined assuming the buggy behavior<br> | |
| 85 </li><li>Propagate fixes into our Skia->NSImage conversion so favicons and other images have the correct colors on all OS versions.</li></ul> | |
| 86 | |
| 87 While this may not sound like a glamourous job, rendering correctness and fideli ty is the cornerstone of the Chromium project. Contributions here improve the en tire project and directly impact all users.<br> | |
| 88 <br> | |
| 89 <h2>(Mac) Access Web Content Via Accessibility Framework</h2> | |
| 90 | |
| 91 <b>Contact/Mentor</b>: Mike Pinkerton (pinkerton@chromium.org)<br> | |
| 92 <b>Difficulty</b>: hard<br> | |
| 93 <b>Areas</b>: C++, Objective-C, Cocoa, WebKit<br> | |
| 94 <br> | |
| 95 While the Chromium UI can easily be connected to Apple's Accessibility Framework , making web content accessible is much more difficult. Chromium's multi-process architecture means that the web content and the browser exist in separate proce sses, thus IPC must be used to fetch the web content. The bigger problem is that IPC from the browser process cannot be synchronous as any delays in responding by the renderer would block the browser's user interface. As a result, the brows er can not simply ask for the content when the A11y Framework desires the conten t. We need a different solution.<br> | |
| 96 <br> | |
| 97 Some work along these lines has been started, but not much is actively in progre ss. This work involves plumbing between the browser and WebCore and would probab ly benefit all platforms, not just Mac OS X.<br> | |
| 98 <br> | |
| 99 <h2>Extension for Creating Custom Stylesheets</h2> | |
| 100 <b>Contact:</b> Rachel Shearer (rshearer@google.com) <br> | |
| 101 <b>Difficulty:</b> medium <br> | |
| 102 <b>Areas:</b> WebKit, AJAX, Chromium Extensions <br> | |
| 103 | |
| 104 A Chromium extension that helps users create their own CSS style-sheets. The ext ension should allow users to identify a piece of content on the page, hit a key to bring up a simple widget that tweaks the look of that content -- font, bgcolo r, fgcolor, font-style -- apply the update to the page, and if the user likes it , generate a CSS rule that would create that effect. This would be a nice way t o interactively and incrementally build up a CSS stylesheet that matches the us er's needs. Relates to <a href='http://src.chromium.org/viewvc/chrome?view=rev&r evision=40882'>http://src.chromium.org/viewvc/chrome?view=rev&revision=40882 </a> | |
| 105 | |
| 106 <h2>Settings for font and color customization</h2> | |
| 107 <b>Contact</b>: Jonas Klink (klink@chromium.org)<br> | |
| 108 <b>Difficulty</b>: medium<br> | |
| 109 <b>Areas</b>: C++, WebKit<br> | |
| 110 | |
| 111 Users need a way to customize the appearance of Chromium, including setting defa ult and minimum font size, font face, as well as override foreground/background color and link/visited link color. If possible, we'd also like to provide a mode to respect system colors/fonts, such as High Contrast mode.<br> | |
| 112 <br> | |
| 113 For related issues, see <a href='http://crbug.com/92'>issue92</a> and <a href='h ttp://crbug.com/7417'>issue7417</a>.<br> | |
| 114 <br> | |
| 115 <h2>(Linux) Improve KDE support</h2> | |
| 116 <b>Contact</b>: Evan Martin (evan@chromium.org)<br> | |
| 117 <b>Areas</b>: C++, KDE, Qt<br> | |
| 118 | |
| 119 Though we've made an attempt to work ok with KDE, most of the team uses GNOME so we still have a variety of <a href='http://code.google.com/p/chromium/issues/li st?q=label:KDE'>issues on KDE systems</a>. I'd like to mentor someone who is ex perienced with KDE through polishing the Chrome experience for KDE users. Aside from that bug list, I'd like to hear other ideas of ways to improve our KDE int egration. (Note: rewriting the UI entirely in Qt is way too large for a SoC pro ject.)<br> | |
| 120 <br> | |
| 121 <h2>(Linux) Better support for tiling/tabbed window managers</h2> | |
| 122 <b>Contact</b>: Evan Martin (evan@chromium.org)<br> | |
| 123 <b>Areas</b>: C++, X11<br> | |
| 124 | |
| 125 Chrome's tab strip ends up looking redundant when your window manager itself pro vides a tab strip. But Chrome knows more than a normal app about the way its ta bs ought to behave: depending on how you interact with a page, new tabs should b e opened "next to" the current tab or "on the right". I'd like to see a proposa l for a way to better integrate Chrome into such a system (perhaps allowing X cl ients to expose additional metadata about where their new windows belong?) as we ll as an implementation in at least two different window managers (if you only i mplement it in one, bugs in the implementation become hard coded into the spec). <br> | |
| 126 <br> | |
| 127 <h1>Chromium OS Projects</h1> | |
| 128 Email: chromium-os-dev@chromium.org<br> | |
| 129 IRC: irc.freenode.net #chromium-os<br> | |
| 130 <br> | |
| 131 See <a href='http://code.google.com/p/chromium-os/wiki/GoogleSummerOfCode2010'>t he Chromium OS page</a> for projects. | |
| OLD | NEW |
