Outreachy/2016/May to August
- 1 Outreachy Program Cohort: Round 12 (May-August 2016)
- 1.1 Enhancements to Python testing tool plugin for generation of HTML reports
- 1.2 Make Firefox look great on desktop!
- 1.3 Project SmartHome prototyping
- 1.4 Webcompat.com Web Application Engineer
- 1.5 Convert Mozmill tests to Marionette
- 1.6 Realtime Push Notifications for Kinto
- 1.7 Test-driven Refactoring of Marionette's Python Test Runner
- 1.8 Content Process Management Tool
- 1.9 Taskcluster tools UI/UX improvements
- 1.10 Automation of Taskcluster Documentation
- 1.11 Fixing some papercuts in the Firefox desktop user interface
- 1.12 Web Platform Test Crime Scene Investigation
- 1.13 Prototype new Firefox features with the Test Pilot team
Outreachy Program Cohort: Round 12 (May-August 2016)
Enhancements to Python testing tool plugin for generation of HTML reports
Inclusive culture is essential to building all kinds of diversity and making diverse people feel welcome in open source projects. We have many groups working on this topic all around Mozilla and other open source communities. This Outreachy participant will engage in community research, documenting best practices and case studies in the development of open inclusive culture.
The participant will be responsible for developing enhancements to pytest-html - a plugin based on the popular Python testing tool pytest, which generates a HTML report based on test results.
Any new enhancements to the plugin must also be accompanied with tests, which will ensure that these new features work in all expected environments, and reduce the chances of regression.
Make Firefox look great on desktop!
For this project, the participant will help to address a number of styling problems where Firefox does not currently look its best.
Project SmartHome prototyping
- Mentors: Kate Glazko and Marcia Knous
- Participant: Manel Rahem
- Participant Blog: https://mermi.github.io
The participant will be involved with Project SmartHome, working on assisting active and ongoing prototyping, integrating logging and metrics into SmartHome work with the collaboration of the metrics team, and helping with user research testing analysis and results.
Webcompat.com Web Application Engineer
Mozilla's Web Compatibility team builds and maintains a web application called webcompat.com that allows individuals to easily report site compatibility issues - and to allow us to better understand the larger picture of compatibility issues affecting Firefox users on the web.
In this Outreachy project, the participant will contribute to one or more of the following projects to help us succeed from a few different angles.
- Design and implement a system that allows site owners and developers to register for notifications (i.e., RSS, E-mail) for issues related to a given domain
- Design and build a user interface that allows bug reporters to identify possible duplicate problems
- Use cutting edge features like Service Workers to enable offline and sync capabilities between the client and server
- Migrate webcompat.com front-end to use ES6 modules (likely powered by something like Babel)
Convert Mozmill tests to Marionette
- Mentor: John Dorlus <email@example.com>, Silne30 on IRC
- Participant: Benjamin "Benny" Forehand, Jr.
- Participant Blog: https://www.bennyjr.xyz/blog and https://benjaminfjr.blogspot.com/
Realtime Push Notifications for Kinto
Kinto is the Mozilla storage solution to backup and sync Firefox Account Users data. It is currently used as a backend for Firefox OS applications and for Firefox and Fennec updates in the Go Faster projects.
Today a notification system allow us to notify Firefox and Fennec users for them to come and get updates.
The participant would extend the notification system to implement realtime updates between devices.
- On the server side we are using Pyramid and Python with a bit of AsyncIO
Test-driven Refactoring of Marionette's Python Test Runner
Marionette's Python Test Runner is slated to become the canonical harness for running most new automated tests for Firefox, but it needs to be lovingly cleaned up and stabilized first. We've already started this work and we're excited to have you help us continue.
We want it to be easy and safe for teams around Mozilla to customize the Test Runner for their needs, so we're writing a suite of tests for the Test Runner itself to prevent breaking any existing automation infrastructure -- i.e. we're testing the thing that runs Firefox tests. Part of your role will be to write more of these tests. While writing tests, you will naturally find areas in the Test Runner code that need to be improved or reorganized in order to be testable in the first place. This is what we mean by "test-driven refactoring".
Other tasks might include:
- Making the test results more informative and easy to read on Treeherder's log viewer.
- Making the tests more convenient to run locally with mach.
Content Process Management Tool
With multi-process Firefox going out the door in the very near future, we're looking at scaling up and tuning the number of content processes that Firefox starts and uses.
Memory usage is something we want to keep an eye on while we do this, so this project is about building a Content Process Management tool that can track real-time memory usage across each process. We might increase the number of uses of the management tool over time, but we'll start with memory management.
Taskcluster tools UI/UX improvements
Taskcluster is the new Mozilla CI that will in future be responsible to run every build and test for Firefox, Firefox TV, rust and other Mozilla projects. We are a small and passionate team engaged to make Taskcluster the best CI ever.
Automation of Taskcluster Documentation
Our task execution platform TaskCluster consists of many small services.
We would like a system to which each component can upload its documentation in a reference format markdown for text, JSON for API references, etc. From the uploaded references we would then generate the entire documentation site.
By uploading documentation and reference files from the services, we can have it automatically update when we deploy new features.
Services already uploads some formal JSON references, but this needs more structure.
- A node.js module for uploading a directory of JSON files + a manifest
- A service generating a static documentation site from uploaded documentation.
Fixing some papercuts in the Firefox desktop user interface
Some of the work will cover:
- Improving entering and exiting of Reader Mode
- Cleaning up the styling of our getting-started tour
- Improving shadows of the dropdowns for the URL and search box
- Increasing legibility of the menubar on Windows 8
- Researching and improving the Windows 10 Start Menu tile for Firefox
- Showing the Windows 10 accent color in the Firefox title bar
Web Platform Test Crime Scene Investigation
- Mentor: Ehsan Akhgari
- Participant: Decky Coss
- Participant Blogs: http://cosstropolis.com/blog and http://cosstropolis.com/blog/feed.xml
We run a lot of automated tests against each revision to Firefox’s code, and we verify that code changes do not cause tests to stop passing. One group of tests, called Web Platform Tests, is shared among all major web browsers, and we have only begun running them recently. As a result, we imported thousands of tests and marked some of them as currently failing, and they have languished in that state. Some of these failures are caused by Firefox not correctly implementing an edge case, while others may be very important problems - as things stand, it's hard to figure out which ones are which. We need your help cleaning up this mess!
Prototype new Firefox features with the Test Pilot team
- Mentors: Jared Hirsch (_6a68 on IRC) and Dave Justice (JSON_voorhees on IRC)
- Participant: Jen Kagan
- Participant blog
The Mozilla Test Pilot team is seeking someone to join a small, enthusiastic team focused around rapidly testing new features in Firefox. The team's process is built around getting feedback frequently and directly from an active user base which allows rapid iteration of the feature design.
In this program, you will participate in a well-documented four step process:
- Lo-Fi Validation: Sketches, ideation, paper prototypes, and user research.
- Prelaunch: Define and build a minimum viable product, establish your testing protocols, and validate the research.
- Active Testing: Launch and test your prototype, collect metrics and feedback, evolve and re-test.
- Sunsetting: Analyze the tests and determine release platforms.
As this program is about rapidly evaluating potential new features, the specifics of what the participant will be developing this summer haven't been settled yet--but ideas are floating around security, privacy, tracking protection, and file transfer. Below are some examples of what the team is currently prototyping as of February 2016:
- Universal Search: adding recommendations from sources around the internet directly into the Awesome Bar.
- Tab Center: rethinking tab management by moving tabs to the side of the browser and making them easier to search.
- Better 404s: Using the Internet Archive's Wayback Machine to replace 404 pages with an older version of the page.
- Page Shot: Enabling smarter sharing of screenshots by copying DOM content as well.