The Chromium project has been accepted as a mentoring organization for this awesome program. This means that over the summer, you have the opportunity to work on new and exciting features for Chromium (and supporting projects) and experience browser development first-hand with a mentor from the project and real deadlines.

Full guidelines and details on how to apply can be found on the official gsoc website. To participate, pick an idea off our handy list or suggest one of your own (it's best to discuss it with a mentor first), then write up a proposal on how you'd go about accomplishing the task in the allotted time frame (3 months).

You can find a list of suggested topics here. These are only recommendations though, feel free to stop by our mailing list or irc channel and suggest something new. If you do decide to write your own proposal, we're looking for familiarity with the codebase, and lots of intelligent detail. The more details you can provide, the better!

Student registration runs from the 23rd of March until the 3rd of April. We're looking forward to seeing the project submissions and expanding our community involvement.


The Google Chrome Blog is intended to highlight points of interest to general users, in a way that is accessible to as wide an audience as possible. It's where you will read about new features that have been released, find interesting tips on how to get the most out of Google Chrome, and stay plugged into the product in general. Many of the types of posts that previously would have surfaced here, such as announcements of our spell-checking improvements, will now appear on this new blog instead of the Chromium blog.

Have no fear, the Chromium blog will still exist, but now with a renewed focus on the original purpose of the Chromium blog. The blog will be dedicated to announcements of things that are happening within the Chromium project itself. We've always felt it important that, as an open source product, we do our work in the open (from general and technical discussion groups to code reviews to design docs) and stay in touch with the open source community. We're going to take this opportunity to try to be more communicative about project status, and news of note particularly to the developer community. We hope these changes make for a better experience for you, so please let us know what you think!