Mozilla community members - submit proposals here for 2017 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 9th.
Are you a student 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.
- 1 How To Write A Good Project Proposal
- 2 Suggestion List
- 3 Mozilla Platform (Gecko)
- 4 Firefox
- 5 Firefox Developer Tools
- 6 Firefox for Android
- 7 Instantbird
- 8 Open Innovation (Campus Clubs)
- 9 Calendar
- 10 Automation & Tools
- 11 Mozilla Developer Network
- 12 Mozilla IT and Infrastructure
- 13 Foundation
- 14 PDF.js
- 15 Release Engineering
- 16 Rust
- 17 Servo
- 18 Security Engineering
- 19 Thunderbird
- 20 Localization
- 21 Security Assurance
- 22 Mozilla Science Lab
- 23 Thimble
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.
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)
|Livelog Proxy|| Write a server that privileged-clients can open a HTTPS connection to in-order to expose a webhook that http-clients can call.
When normal http-clients access the exposed webhooks the connection will be reverse proxied to the privileged-clients over their out-going connection.
|golang, github, http, web sockets, node.js||:jonasfj||:jonasfj||This is like to ngrok and localtunnel.me, read up on those. For performance reasons server should be written in golang, with client libraries in golang and node.js.|
|about:telemetry redesign||about:telemetry is present on all builds of Firefox as a way for users to view the data being stored and sent via Telemetry. It was built before Firefox had multi-process Telemetry and without a clear design. This has resulted in a confusing HTML UI and barely-comprehensible JS.||webtech (HTML+CSS+JS) and Design||:chutten||:chutten|
Firefox Developer Tools
Firefox for Android
|Implement WebExtension APIs|| WebExtensions are a cross-browser system for developing browser add-ons. Not all APIs are supported by Firefox for Android yet.
The goal of this project is to:
|Matrix protocol support|| Matrix is an open, decentralized protocol for instant messaging (and more!) It has bridges to many other networks and protocol, e.g. IRC, Slack, and more. Initial support for Matrix was added in bug 1199855, but there's a lot to do still:
Open Innovation (Campus Clubs)
|Introducing Calendar Accounts|| Traditionally our calendar extension is organized into a list of calendars, each calendar being implemented by a “provider”, for example local storage or using the CalDAV protocol. The service to manage these calendars maintains a simple list, the entries have no connection to each other.
Some calendar providers would greatly benefit from being able to group calendars into accounts, for example free-busy lookups are usually per-server operations and not per-calendar. It would also open the door for some great new features that have been postponed because they can be implemented cleaner with the notion of accounts.
|Advanced Preferences System|| Today, Lightning preferences can mostly only be set on global level. A different, but smaller set of preferences is available on calendar level, whereas several preferences are currently only available from within the config editor. The goal of this project is to create a preference system like Thunderbird uses it - making most of the preferences available on calendar level with an option to fall back to corresponding globally configured preferences.
|Convert from XUL to HTML|| Lightning has traditionally been using XUL for its user interface. To modernize, we would like to convert dialogs, tab content and other parts of the user interface to HTML. The new components should use web standards as much as possible, avoiding extensive use of third party libraries.
This is a fairly open ended proposal, which requires the applicant to first identify parts of the user interface that would make sense to convert to HTML and put up a timeline how long to spend on each component. Focus should be on the quality of the conversion, not the quantity of components changed.
Automation & Tools
|C++ static analysis||Add new checkers specific to our base code||Strong C++ experience, clang||Sylvestre||Andi||In order to tackle issues during the development phase, Mozilla wrote a bunch of static analyzers checkers based on clang-tidy. In this project, we will focus on writing more checkers (either generic to C/C++ or specific to Gecko programming patterns).|
|JSON in Sqlite||Query JSON Documents stored in Sqlite||Database, SQL, Python||Kyle Lahnakoski||Kyle Lahnakoski||Details|
|Regression localization from stack traces||Tool to blame a patch for causing a newly introduced crash.||C++, Python||Marco||Marco||The project would involve creating a tool that analyzes a set of stack traces, performing the intersection with the Firefox call graph (which can be generated using Clang) and a set of recently committed patches.|
|Improvements for crash clustering||Build a tool to improve crash clustering, currently based on the top method of the stack trace.||Python, C++||Marco||Marco||The project would involve finalizing https://github.com/marco-c/crashsimilarity; testing it more thoroughly; putting it in production.|
Mozilla Developer Network
Mozilla IT and Infrastructure
|Curriculum database for Learning site||Curriculum is currently accessed via the Teaching Activities page of the learning site (https://learning.mozilla.org/en-US/activities ). It's a pretty static experience. Users can browse through a list of modules, but there is no search capability. We have a prototype for a more interactive UX that allows users to search and filter curriculum modules and activities: https://flukeout.github.io/curriculum-search-react/. This project would require implementing the front-end, as well as wiring up the backend database (for which the model has been defined, but the data has not been migrated).||js, html, css, django, python||hannah||gideon||This would be a big win for the curriculum team and for the community members who make good use of our learning/teaching materials. The database could eventually be extended beyond the learning site and support other parts of the network as well.|
|Streams API in PDF.js||Streams API with PDF.js, makes it more faster and memory efficient. Passing data incrementally from worker to main thread increases the speed of processing. Using Streams API instead of xhr in networking reduces the memory usage. Since Streams API is a new technology, using it in PDF.js test Firefox's implementation.||ECMAScript 2015, Web APIs||:yury||:yury||Proposal: https://docs.google.com/document/d/1yTPvPBhGkFn7XUntAt8wdVPckxHovYylNAIJOGnGRXc/edit?usp=sharing|
|Improve Balrog's Admin API||Make Balrog's Admin API simpler and easier for clients to work with by moving to a Swagger-based approach.||python,rest apis||Ben Hearsum||Ben Hearsum|
|Rust + WebAssembly showcase||Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it.||Rust, web development||brson||brson, badboy||cc https://users.rust-lang.org/t/compiling-to-the-web-with-rust-and-emscripten/7627. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-1-md|
|Rust dashboard updates||Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise.||Rust||brson||brson, aturon?, dikaiosune?||Follow on work to https://internals.rust-lang.org/t/the-rust-project-needs-much-better-visibility-into-important-metrics/3367|
|Rust reproducible builds|| Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to
double-check the official Rust builds
|Rust, compilers, systems programming||brson||brson, mw, Manishearth||https://internals.rust-lang.org/t/verifying-rustc-releases-with-reproducible-builds/4502. Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-2-md|
|Abstract the Rust standard library|| The Rust standard library is very portable, but can be very, very portable. Refactor the
standard library to pull out a platform abstraction layer.
|Moderate Rust experience||brson||brson||https://internals.rust-lang.org/t/refactoring-std-for-ultimate-portability/4301|
|Rust cross-platform showcase project||Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post.||Moderate Rust experience||brson||brson|
|rustc micro-optimization bonanza||Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it.||Performance optimization||brson||brson + ?|
|Rust-specific benchmark suite||Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust.||Programming||brson||brson|
|Rust crate semver compatibility tool|| Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates
are obeying semver. This would be a huge boon to the stability of the Rust ecosystem.
|Static analysis||brson||brson, badboy||https://users.rust-lang.org/t/warnings-for-breaking-semver/1415 https://users.rust-lang.org/t/signature-based-api-comparison/2377 . Full proposal: https://gist.github.com/brson/c936d0f5e5ec8c806a41e23e87455665#file-rust-proj-3-md|
|Reconstruct the Rust bootstrap chain|| Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the
Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post.
|Scripting, build systems||brson||acrichto|
See bug 930732 for details. After this is done, we need to see if all existing tests work properly under the new mozmill. Some touches may need to be done. If time is left, some mozmill tests could use some modernization, consolidating duplicated code, etc. Some areas of code also need new test coverage. These cleanup tasks would be proposed by the mentor.
|Design screenshot-based localization interface in Pontoon||We'd like to explore the feasibility of screenshot-based localization process in Pontoon - Mozilla's translation tool. To provide more translation context, each string will be accompanied by a screenshot showing how the string is used in the application. Additionally, localizers will have the ability to navigate and filter strings by screenshots, as well as preview their translations in the localized screenshots.||Web standards and Design. Django is a plus.||:mathjazz||:mathjazz|
TLS 1.3 scanning in Mozilla TLS Observatory
Mozilla TLS Observatory is a hosted service that provides hindsight and compliance checking on the configuration of HTTPS servers. The goal of this project is to improve the service to support scanning TLS 1.3 enabled endpoints, either by improving the existing scanner or writing an entirely new scanner.
Programming skills in C, Bash and Go. Strong understanding of TLS and micro-services architectures.
Mozilla Science Lab
|science.mozilla.org phase 2||Start phase 2 of the Mozilla Science Lab website by implementing||js, html, css, react, django, python||abbycabs||alanmoo||Detailed list and breakdown of all phase 2 work (only the tasks mentioned in details are expected to be completed by the student):|
|Paper Badger - badgr migration & publisher integration|| * Issuing badges to credit authors for their work on academic papers.
||js, Badgr, APIs, authentication, node.js, react||abbycabs||abbycabs||github: https://github.com/mozillascience/paperbadger|
|Study Group participation visualization|| study groups meet all over the world, running regular events share skills, co-work and create community around open science. Right now there's no easy way to see all the study group events.
||js, html, css, python (or another scripting language), data visualization||Zannah||Aurelia||main study group repo: https://github.com/mozillascience/studyGroup|
|Address stability issues within Thimble||Main task: Get Thimble to write directly to AWS instead of writing to a database first.||js, html, css||gideon||gideon||Full list of issues affecting thimble's stability: https://github.com/mozilla/thimble.mozilla.org/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22good%20first%20bug%22%20-label%3A%22assigned%20to%20contributor%22|
|Integrating VR capabilities into Thimble|| Goal: Thimble makes it easy to create multi user VR experiences, allowing the whole classroom to take virtual field trips through student projects.
This is made possible by doing any of these:
|js, html, css||gideon||gideon|| This work would be done in parallel with work done by CDOT on making Thimble a VR experience building tool
thimble repo: https://github.com/mozilla/thimble.mozilla.org
|Thimble and Remote Mentorship|| Goal: Use together.js to enable a multi-user environment on Thimble that is tailored to work as a virtual teaching environment for HTML/CSS/JS
|js, html, css||gideon||gideon||thimble repo: https://github.com/mozilla/thimble.mozilla.org|