Confirm, emeritus
421
edits
Changes
→Project List
===Project List===
* No The following projects have been tentatively greenlit yet, pending milestone clarifications. == 2018 Project List == {| class="standard-table" border="1" style="border-collapse: collapse"|-! Title ! Details ! Skills Needed ! Reporter ! Mentor(s) ! Additional Comments|-| ReSpec | [https://github.com/w3c/respec/ ReSpec] is a JS-based tool used to write W3C Specifications (Web Standards) that is widely used by the Web Standards Community. With 5+ years of development, it's heavily depended upon by the W3C community at large (of which Mozilla is an active participant). ReSpec's code is in need of some modernization, optimizations, and bug fixes - and we could use your help! In this project, you would have the opportunity to make ReSpec's UI more accessible, making it leaner and faster using distributed processing with Web Workers, and/or adding new features to make the lives of W3C spec Editor's better. | Languages or skills needed: JavaScript, HTML, CSS. | Marcos Caceres (Mozilla)| Marcos Caceres (Mozilla)| ReSpec offers students the opportunity to work on a large code base that has extensive real world use and impact. The project offers students an extensive range of problems to tackle, from UI design, to concurrent processing (using Web Workers to do distributed text processing), dealing with accessibility and internationalization, writing and learning about unit and integration tests, security, code review, etc. - as well as exposure to the W3C and the web standards community, this project also aims at teaching students about how web standards are put together. To determine if this is a project you would like to be part of, see the [https://github.com/w3c/respec/issues/ list of issues] you could work on. It's a great opportunity to learn about all aspects of open source software development, but with the freedom to take on small to large challenges over the Summer (depending on your skill level and level of confidence). About the mentor: Marcos Caceres is a Staff Engineer at Mozilla who has been working on Web Standards for over a decade. Marcos is the lead maintainer of ReSpec. Marcos has extensive experience mentoring developers and has previously successfully mentor a GSO student. |-| D3D11 backend for gfx-rs HAL| [https://github.com/gfx-rs/gfx gfx-rs] is a graphics abstraction library written in Rust and currently used for prototyping and investigation of [https://www.khronos.org/blog/khronos-announces-the-vulkan-portability-initiative Vulkan Portability] and [https://www.w3.org/community/gpu/ WebGPU] by Mozilla. The Hardware Abstraction Layer (HAL) of gfx-rs currently supports Vulkan, D3D12, Metal, and OpenGL. We want it to be powering [https://github.com/servo/webrender/ WebRender] for Firefox Quantum and Servo, and since WebRender currently runs on D3D11 (through [https://chromium.googlesource.com/angle/angle/+/master/README.md Angle]), we need to provide a native D3D11 backend. The implementation can be based off the existing D3D11 backend of [https://github.com/gfx-rs/gfx/tree/pre-ll/src/backend/dx11 gfx-rs pre-HAL], and the main challenge is porting the code, optimizing, and testing it.| Candidates should be familiar with Rust as well as low-level graphics development. Not having D3D11-specific experience is acceptable, given the willingness to learn it and a properly setup Windows development environment.| Dzmitry Malyshau (Mozilla)| Dzmitry Malyshau (Mozilla)| gfx-rs is one of the foundational projects in Rust gamedev/graphics, with rich history and wide range of users. We have an active community that encourages learning and curiosity in how graphics works down to the hardware. This is not a Mozilla project, but it may become a key component in Firefox Quantum for the ability to run natively on different platforms, while utilizing the fine-grained control of the graphics/compute workloads exposed by the low-level APIs.|-| Servo: Prototype ways of splitting up the script crate| [https://github.com/servo/servo/ Servo] is a web rendering engine written in Rust. One specific module contains a huge amount of code that is expensive to compile all at once. This project is intended to explore ways of splitting it into separate modules to achieve better build performance without breaking the complex set of interdependencies that exist in the code.| Candidates should be familiar with Rust, in particular using it in projects made of multiple crates and relying on features like traits and associated types.| [https://mozillians.org/en-US/u/jdm/ Josh Matthews] (Mozilla)| [https://mozillians.org/en-US/u/jdm/ Josh Matthews] (Mozilla)| [https://github.com/servo/servo/wiki/Prototype-ways-of-splitting-the-script-crate Full project description page]|-| web-platform-tests: Improve test manifest workflow and performance| [https://github.com/w3c/web-platform-tests/ web-platform-tests] is a project for writing a cross-browser test suite, which is used across all major browser engines. The list of tests is stored in a JSON manifest file which is slow to generate and which we currently check in to the Firefox repo. These things create a poor developer experience. The goal of the project is to move to a system where the manifest is downloaded on demand for Firefox developers, and then to explore ways to speed up manifest generation such as employing parallelism or moving performance hotspots to Rust. | Candidates should be confident programming in Python.| [https://github.com/jgraham James Graham] (Mozilla)| [https://github.com/jgraham James Graham] (Mozilla)|-| WasmFiddle| [https://wasdk.github.io/WasmFiddle/ WasmFiddle] is a web application that facilitates learning of the WebAssembly and its usage in the browser. The goal is to create a learning tool that will allow user to quickly start a project that uses WebAssembly, learn based on examples, explore existing popular toolchains (emscripten, rust, etc), etc. The project will be similar to what jsfiddle, jsbin, or codepen proposes, but with additional elements specific to WebAssembly only, e.g. a code generation from C/C++ languages or how the code will be compiled by the browser and run in native machine code.| Languages or skills needed: JavaScript, HTML, CSS, WebAssembly. Suggested additional technologies: React, Rust, C++.| Yury Delendik (Mozilla)| Yury Delendik (Mozilla)| The project involves extending the functionality of the existing WasmFiddle/WasmExplorer projects to:* control, inspect and understand every part of the WebAssembly compilation pipeline;* don’t hide details or add magic build steps;* users can create, modify, fork and share fiddles, to reduce friction, no accounts;* influence JavaScript developers through well-thought out examples, best practices and templates;* add support for many languages: C/C++/Rust/etc;* create environments where users can play and have fun with: WebGL, Physics, Games, Audio Synthesizers|-| Pontoon's path to first contribution| Pontoon is Mozilla's localization tool, used by hundreds of contributors to translate Firefox, mozilla.org, and many other Mozilla products. It is critical to shipping Firefox to as many users as possible, all around the world. This year, we would like to improve the experience of first-time users of Pontoon. Your task would consist of defining a "path to first contribution", and making it as smooth as possible. That mainly involves adding a tutorial to walk users through the translation interface and reworking the landing page, all of that using recent front-end technologies in a fast-evolving application.| JavaScript, HTML, CSS, Python, UX. Django and React are pluses| [https://mozillians.org/en-US/u/adrian/ Adrian Gaudebert] (Mozilla)| [https://mozillians.org/en-US/u/adrian/ Adrian Gaudebert] (Mozilla)||-| AOM - accessibility API| [https://github.com/WICG/aom/blob/gh-pages/explainer.md AOM] is JavaScript API designed to help the authors to make the web pages accessible, i.e. make them usable by the assisstive technologies such as screen readers, screen magnifiers and others. AOM specification is inspired by [https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA ARIA] standard, an HTML 5 extension, used to add semantics to the web pages. If you are familiar with ARIA, then you can think of AOM as JavaScript ARIA. The AOM proposal (phase 1) was already implemented in Chrome under a flag, and you can help do the same in Firefox.| Languages or skills needed: C++. | Alexander Surkov (Mozilla)| Alexander Surkov (Mozilla)| This project is the opportunity to hack on the heart of Mozilla Firefox, the Gecko engine. It involves working with a large code base and solving a wide variety of problems, from the solution architecture to finding efficient ways to implement it. If you want to learn about Gecko and accessibility, that's the right place. AOM has the potential of becoming a new standard in making the web page accessible next few years. You can help to happen it sooner.|-| metricsgraphics - zooming and brushing| [https://github.com/mozilla/metricsgraphics metricsgraphics] is JavaScript library designed to help with the presentation of interactive visualization. It is used extensively both inside and outside Mozilla. This project would be about adding a set of zooming and brushing features to facilitate the exploration of large and/or noisy datasets, such as in the [https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder Perfherder] or [https://github.com/mozilla/missioncontrol/ Mission Control] projects. Detailed project description to come.| Languages or skills needed: JavaScript, HTML/SVG| William Lachance (Mozilla)| William Lachance (Mozilla)| |-| Ailurus Notebook| The [Ailurus Notebook|https://github.com/mozilla/javascript-notebook] is a pure client-side browser-based IDE and publication tool for scientific computing and computational inquiry using web technologies (HTML, CSS, Javascript, WebAssembly). It provides a Jupyter-style notebook interface, granting scientists full access to the power of the DOM and browser APIs within a familiar iterative workflow, and with zero overhead -- absolutely no software installation and configuration is required, so people can seamlessly learn from and extend the work of others. Students will contribute to: extending the functionality of the notebook; making the notebook code more robust and performant; helping to shape the user experience; and creating example notebooks.| JS; HTML; CSS; React/Redux; familiarity with at least one scientific computing language preferred (ex: MATLAB, Mathematica, Julia, Numpy/Scipy, R, etc). Science/math background is a major plus.| Brendan Colloran (bcolloran@mozilla.com)| Brendan Colloran (bcolloran@mozilla.com)| In addition to helping to build the notebook, actively dogfooding it will be an essential part of our work. This means that students with a scientific and/or applied math background will be encouraged to build example notebooks that demonstrate visualizations, simulations, data analyses, etc., on topics of their choosing. In addition to mentoring students on software development, we will provide mentorship in scientific computing and data science.||-| Improved Pulse Inspector Backend| [https://github.com/taskcluster/taskcluster-rfcs/issues/104 More details here]. The idea is to create a backend service that will allow browser-side applications like [https://tools.taskcluster.net/pulse-inspector/ pulse inspector] to listen to arbitrary [http://pulseguardian.mozilla.org/ Pulse] messages.| JavaScript (server-side), AMQP, WebSockets| Dustin Mitchell (Mozilla)| Jonas Jensen (Mozilla) / Eli (Perelman Mozilla)| This project can largely be a generic read-only websocket proxy for RabbitMQ, refer to our [https://github.com/taskcluster/taskcluster-rfcs/issues/104 issue for more details].|-| Redash - Improve user experience of [https://sql.telemetry.mozilla.org STMO]| Mozilla runs an [https://sql.telemetry.mozilla.org/ instance] of the Open Source project [https://github.com/getredash/redash Redash], a data analysis and dashboarding tool that has been customized and configured for use with a number of the Firefox organization's data sets. It provides low barrier access to the vast amount of Firefox Telemetry data (and others) to make product decisions for Firefox and others projects.| Languages or skills needed: Python, JavaScript, HTML| [https://mozillians.org/en-US/u/jezdez/ Jannis Leidel (jezdez)] (Mozilla)| [https://mozillians.org/en-US/u/jezdez/ Jannis Leidel (jezdez)] (Mozilla)| Knowing SQL or having experience with data analysis is not a hard requirement to work on user experience improvements of the Redash tool itself. Instead this GSoC project is targeted at web developers who enjoy improving tools that have a great impact on how Firefox is developed. Please check back soonalso see the [https://docs.telemetry.mozilla.org/ Firefox data documentation] for a more detailed [https://docs.telemetry.mozilla.org/tools/stmo.html introduction into Mozilla's Redash instance]. A goal of this GSoC project is to upstream all improvements made to the upstream Redash project when possible.|-| Automatically detect web compatibility issues| Build a tool to automatically detect web compatibility issues using machine learning tools.| Python (knowing Keras or having experience with machine learning is a plus)| [mailto:marco@mozilla.com Marco (:marco)] (Mozilla)| [mailto:marco@mozilla.com Marco (:marco)] (Mozilla)| The project involves collecting data (screenshots of websites in different browsers), labeling it, training a neural network to automatically detect when a website is rendered differently in different browsers.|-| Autogeneration of style structs in Servo's style system| Prototype how to run [https://github.com/rlhunt/cbindgen cbindgen] on Servo's style system [https://github.com/servo/servo/tree/master/components/style/values values module] to auto-generate style struct definitions for C++ and Rust, which would enable the removal of 5k+ [https://github.com/servo/servo/blob/master/components/style/properties/gecko.mako.rs lines] of unsafe and slow Rust <-> C++ conversion code. This can be done on a per-struct basis, so prototyping the general mechanism with a simple one like [https://github.com/servo/servo/blob/master/components/style/properties/longhand/color.mako.rs color] would be the first step, migrating more and more as time goes on.| Primarily Rust (though no need to be really advanced), probably a bit Python for build system integration, and basic C++ since it needs to get generated.| It may need to move the style::values component into a standalone crate as a prerequisite for some of the most complex structs, but that should be easy.| [https://github.com/emilio emilio]| [https://github.com/emilio emilio]||-| Timely Security Analytics| InfoSec uses the Mozilla Defense Platform, MozDef to aggregate logs and alert on time series. This project seeks to create a structure for extract, transform, load operations (ETL) to process these time series events using MapReduce. | Languages or skills needed: Python, Scala, Javascript, ETL, AWS/GCP, Data Science Fundamentals, Apache Spark, Pig, or other big data.| [https://mozillians.org/en-US/u/akrug/ Andrew Krug :akrug (mozilla)| [https://mozillians.org/en-US/u/akrug/ Andrew Krug :akrug (mozilla)[https://mozillians.org/en-US/u/michalpurzynski/] Michal Purzynski :michal` (mozilla)| Aggregation of disparate sources of data: NSM, CloudTrail, etc. into spark. Real-time alerts over large quantities of data. |-| C++ Static Analysis| Add new checkers specific to our base code.| Strong C++ experience and clang infrastructure.| [mailto:s@mozilla.com Sylvestre]| [mailto:andi@mozilla.com Andi]| In order to tackle issues during the development phase, Mozilla wrote a [https://hg.mozilla.org/mozilla-central/file/tip/build/clang-plugin bunch of static analyzers checkers] based on [http://clang.llvm.org/extra/clang-tidy/ clang-tidy]. In this project, we will focus on writing more checkers (either generic to C/C++ or specific to Gecko programming patterns). |-| Download Spam Protection for Firefox| In Firefox, we want websites to go through a permission prompt if they want to initiate several downloads in an automated (not user-initiated) fashion. The project will involve implementing a permission prompt, implementing the logic of when it should be triggered, and collecting data (via telemetry, etc) on how users interact with the prompt in order to verify how the feature behaves.| Good JavaScript experience and a basic understand of how the web works.| [mailto:jhofmann@mozilla.com Johann (:johannh)]| [mailto:nhnt11@mozilla.com Nihanth (:nhnt11)]| A more detailed description can be found [https://bugzilla.mozilla.org/show_bug.cgi?id=1306334#c2 here]|-| ..your project here!||||||}
