Community:SummerOfCode13: Difference between revisions

This page lists all the [[SummerOfCode|Google Summer of Code]] 2013 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode13:Brainstorming|the Brainstorming page]]. This page is locked; contact Gerv with edits.

==Application Advice==

* Read the [http://www.booki.cc/gsocstudentguide/ GSoC Student Guide] and follow its advice.

* Read [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not To Apply For Summer Of Code] and avoid doing the things listed there.

* It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that probably improves your chances a little. However, more than 3 seems like spam.

== Firefox ==

tightly controlled, irreversible-without-password setting, but rather a feature that will make it harder to accidentally break or deteriorate the Firefox experience.

| Good JS skills and ability to work with large codebases. Previous add-on experience is a big plus.

| [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared]

| about:memory has been a very useful tool for us developers to better understand memory consumption in Firefox and help diagnose and fix problems (See the [https://wiki.mozilla.org/Performance/MemShrink MemShrink project]). We would like to make about:memory also useful for web developers and users by providing better data visualization and analysis that will help them understand the footprint of their websites and improve accordingly. You should be able to come up with useful and creative ways to visualize that data and implement those visualization using JS.

| Good JS skills and knowledge/passion for data vizualization. Past work with data visualization is a big plus.

| [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared]

| Fullscreen Mode

| One upcoming Firefox feature is a fullscreen mode that should provide an immersive experience. This mode will provide a streamlined interface as can be seen in this [http://people.mozilla.com/~shorlander/ux-presentation/01-Firefox-Australis-%28Windows%29-%28Fullscreen%29.jpg preliminary mockup]. Features such as a clock and other OS indicators (new APIs have been implemented for these from the WebAPI project) might also be part of the project.

| Great CSS skills are important, and knowledge of XUL/flexbox is a plus. Good JS skills. Past theme development experience would be great.

| [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared]

| Autosuggest Search Engines

| Many websites have search fields that are used many times over, but these websites do not present themselves as search-capable in order to offer itself to be added as a search engine in the browser. [https://bugzilla.mozilla.org/show_bug.cgi?id=335448 Firefox should detect repeated search field usage] and offer that as an option to the user. At a minimum, it should be able to detect it and add an entry with "Add [website]" in the searchbar dropdown (similar to how OpenSearch works). After the detection part is working well, a refined UX for the feature can be discussed and prototyped (but that shouldn't be the focus of the project).

| Great JS skills and understanding of DOM, HTML form fields, and algorithms (db and data structures that will be used to store and search the input field history to detect patterns of search usage)

| [mailto:gsoc@felipc.com Felipe]

|-

| Mailbox-to-Maildir Converter

| C++, although some JS may be necessary

| jcranmer

|}

{| class="standard-table" border="1" style="border-collapse: collapse"

! Comments

|-

|}

{| class="standard-table" border="1" style="border-collapse: collapse"

! Comments

|-

|

|}

| You need to know about JS (good), CSS (basic), HTML (basic)

| Jean-Yves Perrier

| In your application, you should list the tools you would create. You should submit 8 tool ideas, and the ones you will actually do will be agreed at the beginning of the project. Success will be measured if 6 of these tools are implemented, reviewed and live in the MDN.

|}

| [http://www.rust-lang.org/ Rust] is a new compiled programming language that Mozilla is working on. At the moment, Rust programs are tricky to debug when they don't work because they lack debugging symbols. This work has been started, but for many core Rust features the current debugging support is little to none. The goal of this project would be to support building the self-hosted (i.e. written in Rust) compiler with full debugging symbols enabled, and fill out the suite of automated gdb tests to ensure that the debugging support does not regress in the future. The project will require making use of [http://llvm.org/ LLVM]'s [http://llvm.org/docs/SourceLevelDebugging.html source-level debugging features] and building on the debugging support that [https://github.com/mozilla/rust/blob/master/src/librustc/middle/trans/debuginfo.rs already exists in the compiler].

| Rust, LLVM experience beneficial

| Practical experience with Rust is rare. Therefore, any student interested in this project should take some time to become familiar with Rust so that the actual project time is spent on practical work instead of learning the language.

|}

|  

|-

| http://meemoo.org/ is browser-based data flow coding environment. The goal is to bring more people, including children, to the world of open source creative coding with instantly-hackable creative apps that run in the browser. "Hacktivies" are activities that encourage playful exploration with images and code. For this project, you should prototype and design ways to bridge the digital/analog high/low tech code/craft divide. http://meemoo.org/hack-our-apps/ for some examples. A successful proposal will include some creative output made with Meemoo to show understanding of the system.  

| JavaScript, craft, activity design, graphic design, writing  

|  

|}

|

|-

| '''Goal:''' Create a tab that "knows" what conversation you want to open (like the "[http://www.dria.org/wordpress/archives/2008/04/17/628/ awesomebar]").

'''Description:''' The current "Join Chat" dialog is ugly and difficult to use. A user should be able to open a new tab to create a new conversation which will auto-complete fields based on history and server information (e.g. LIST from IRC).

| Monica Chew (mmc), Tanvi Vyas (tanvi)

| This is primarily a quantitative user experience project.

|}