Personal tools

Community:SummerOfCode14:Brainstorming

From MozillaWiki

Jump to: navigation, search

Mozilla community members - submit proposals here for 2014 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the official list.) The absolute last deadline for submitting ideas in time to help us get accepted by Google is February 14th.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the official list of ideas. This page is full of weird and whacky ideas, some of which are still on here for a reason - it could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You can, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.

Contents

How To Write A Good Project Proposal

Before adding an proposal to this list, please consider the following:

  • Be specific. It's hard to understand the impact of, or the size of, vague proposals.
  • Consider size. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
  • Do your research. Support the idea with well-researched links.
  • Don't morph other people's ideas. If you have a related idea, place it next to the existing one, or add a comment.
  • Insert only your own name into the Mentor column, and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.
  • Check back regularly. The administrators may have questions about your idea that you will need to answer.
  • Know when to give up. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.

Suggestion List

Here are the ideas lists from previous years.

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

Mozilla Platform (Gecko)

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox

Title Details Skills Needed Reporter Mentor(s) Comments
Render large PNG images For data visualization web sites like SegAnnDB need to display large PNG images, but as this test shows, Firefox does not render very large PNG images. A bug has been filed and this bug could perhaps be fixed by a Google Summer of Code student. unknown tdhock

Firefox for Android

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox OS / Boot2Gecko

Title Details Skills Needed Reporter Mentor(s) Comments
Implementation of a default Voice Recorder app There is no built in voice/sound recorder app in gaia, as stated in Bug 877286. The taking of memos shouldn't be left to external apps. The goal would be to create such an app for the built-in package. An addon for the Music app is also considered. Familiarity with gaia and a good knowledge of CSS, Javascript and HTML5 is needed. Should have a fairly good idea about hosted app structure and UI layout. Understanding of the Media Recording API is a plus, but can be caught up on the fly. Vedad Hadžić
Math virtual keyboard Firefox OS has native support to MathML (probably the best one if some patchs already in Firefox (Desktop) Nightly was apply) and because of that is suitable to use in mathematical classes. Unfortunately, there is a lack of tools to edit MathML and a good start will be have a special virtual keyboard. For example, a math virtual keyboard will improve the user experience with this demo. Good knowledge of CSS, Javascript, HTML5 (MathML included), LaTeX. Understanding of the default keyboard can be caught up on the fly. Raniere Silva

Mozilla Open Badges

Title Details Skills Needed Reporter Mentor(s) Comments

Thunderbird

Title Details Skills Needed Reporter Mentor(s) Comments


Calendar

Title Details Skills Needed Reporter Mentor(s) Comments

SeaMonkey

Title Details Skills Needed Reporter Mentor(s) Comments

NSS (Network Security Services)

Title Details Skills Needed Reporter Mentor(s) Comments

Bugzilla

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox Support (SUMO)

Title Details Skills Needed Reporter Mentor(s) Comments

QA

Title Details Skills Needed Reporter Mentor(s) Comments

Automation & Tools

Title Details Skills Needed Reporter Mentor(s) Comments

Documentation

Title Details Skills Needed Reporter Mentor(s) Comments

Mozilla Developer Network

Title Details Skills Needed Reporter Mentor(s) Comments

Mozilla IT and Infrastructure

Title Details Skills Needed Reporter Mentor(s) Comments

Persona / BrowserID

Title Details Skills Needed Reporter Mentor(s) Comments

Sync / Services

Title Details Skills Needed Reporter Mentor(s) Comments

Developer Tools

Title Details Skills Needed Reporter Mentor(s) Comments

Add-on SDK

Title Details Skills Needed Reporter Mentor(s) Comments

Foundation

Title Details Skills Needed Reporter Mentor(s) Comments

Release Engineering

Title Details Skills Needed Reporter Mentor(s) Comments

Instantbird

Title Details Skills Needed Reporter Mentor(s) Comments
Single window UI: Goal: Provide an alternative UI that works well in a single window.

To design and implement a single-window UI that does not require a separate contact list and makes good use of the available space when the window is full-screen. Avenues to explore are e.g. multiple side-by-side chats (extending what is currently possible with tabs), and automatic resizing of conversations. The student should bring a good (if not complete) vision for this project, demonstrated via mockups in the application.

JavaScript, XPCOM, XUL Florian Quèze

Emscripten

Title Details Skills Needed Reporter Mentor(s) Comments

Rust

Title Details Skills Needed Reporter Mentor(s) Comments

Servo

Title Details Skills Needed Reporter Mentor(s) Comments

Security Engineering

Title Details Skills Needed Reporter Mentor(s) Comments


Localization

Title Details Skills Needed Reporter Mentor(s) Comments
Mozilla Verbatim and Pootle Implement APIs on Verbatim for retrieving the untranslated string information and existing translations if any. Use machine learning and data mining concepts to translate the strings using existing localization intelligence from the large amount of tranlated strings and implement a web application to translate the strings.

Localization plays a major role in Mozilla in spreading its vision of an open and literate web. Localizers are major contributors in making the open source products from Mozilla like Firefox and websites available in 30+ languages, this involves a lot of data being generated in the translation followed by a review process of these translated string. The project aims to use existing database of translations for a particular string and use rating factors and other rating methods to figure out the best translation to a particular string. Also this project can use automatic translation since the data generated by the users over many years can be used for mining and then processing for translation of strings.

This project could also be used in localization of the documentation present on MDN into different languages for the world to use. A feed can be built onto MDN requesting the to be localized content as paragraphs of data and then localizing them using the automatic localization features.

Benefits

Localization time can be saved More time can be spent in localized string verification than in localization thus giving higher quality localizations.


Short Term Goals

To make a machine learning integration with Mozilla’s localization platform.


Long Term Goal

To export the project into a full fledged stand alone application with links to various localization platforms like Transifex, Pootle etc.., thus enhancing the localization features of many open source software projects.

An enhancement to the 2010 Localization machine learning project implemented by Gautam Akiwate.

  • Understanding of open webservices APIs
  • Python (Django) / JavaScript
  • Familiarity with a library used for quickly generating a web UI to a server-side Python script
Sudheesh Singanamalla Soumya Deb
L10n Dashboard

Project Brief

A dashboard for keeping track of l10n statistics for various projects in a single place with ease of access for localizers and project co-ordinators in mind. As an added feature the Dashboard can be developed in a mobile friendly responsive layout.


Problem Statement

Mozilla has a very large number of simultaneous localization projects, each using a different localization tool. As such, there is no central entity where localizers can go to, to find a list of all the projects that they contribute to, and find detailed statistics (completion status, contribution metrics, etc.) across individual projects.

Too many URLs and translation systems to remember along with keeping track of all updates / statistics across various projects is quite a big manual process at the moment. Having all these in a single place would allow contributors / locale leads to take quicker and better informed decisions about which projects to prioritize while working.


High-Level Project Goals

  • The system should provide a consolidated view for l10n statistics across projects and provide easy access to individual projects.
  • The system should be capable of data visualization for real time data gathered from multiple sources, to provide enhanced reporting capabilities.
  • The dashboard should be a double ended one: i.e. have separate views for organizations/maintainers and individuals.
  • It has to be modularized, so as to separate the view from the back-end stores.
  • It needs to be easily deploy-able to enable individual teams to directly plug it to their own repositories and use it.
  • The system has to be easily extendable to allow for easy modifications, as well as be light, efficient and user friendly.
  • Pootle, Transifex etc. translation system APIs.
  • HTML5, CSS3, JS.
  • Data visualization tools.
Sayak Sarkar Sayak Sarkar
  • A basic prototype of the project can be found here.

Build system

Title Details Skills Needed Reporter Mentor(s) Comments
Inotify/watchman daemon for mach Issues to be solved
  • ./mach build is slow unless you specify a list of changed files
  • hg qref is slow
  • ./mach build does not always work when applied to a single file for incremental. Some js/xul files need a build of the folder or parent folder.

Using inotify or watchman, keep track of the files being changed in the source dirs. This can be done in two ways:

Directly integrate it with mach and provide it with a mode where it reads the last-updated files from a log of the daemon and builds just those. Or, integrate it with qref (some partial solutions for this already exist), possibly as a Mercurial extension and make hg read the files to be changed from the active patch. This only deals with changes being added, if a patch is popped or a change is removed from a patch, there needs to be a mechanism to notice this as well.

Further speed improvements can be made using this.

Original idea credit: @ckitching

make / python / familiarity with mozilla (firefox, mainly) codebase Manishearth Soumya Deb

Security Assurance

Title Details Skills Needed Reporter Mentor(s) Comments

Mozilla Science Lab

Title Details Skills Needed Reporter Mentor(s) Comments