Confirm
514
edits
Changes
added round 15 projcts
{{Admon/note| Applications for Outreachy Winter 2017 are now open. Check out our Round 14 interns have been announced15 projects below. Visit [https://wiki.gnome.org/Outreachy/2017/MayAugust#Participating_Organizations The GNOME wiki] to see the list and learn more about general program logistics}} <br />
Mozilla has participated in the Outreachy program for several years. The goals of the program are to increase participation from under-represented groups in free and open source software. Participation is open:
* [[GNOME OPW Handbook]]
* [http://kernelnewbies.org/OPWMentor Information for mentors, from Linux Kernel project]
==Outreachy Program Cohort: Round 15 (December 2017 - March 2018)==
===JSON-e Everywhere===
'''Mentor:''' [https://mozillians.org/en-US/u/dustin/ Dustin Mitchell] <br />
'''IRC:'''dustin
'''Project Description:'''
Taskcluster is the task-execution platform which will soon handle all
build, test, and release work for Mozilla projects. We are working to
radically simplify how tasks are created to support the incredible
diversity of projects we want to support.
As part of that work, we have developed a small templating language,
JSON-e (https://taskcluster.github.io/json-e/) and we are working on
using that language to define tasks across the platform. This project
involves finishing that work, specifically:
* Support JSON-e to define tasks in taskcluster-hooks
* Support listening for pulse messages in taskcluster-hooks
* Replace mozilla-taskcluster with per-repository hooks
* Support JSON-e to define tasks in Github repositories
* Lots of smaller updates, fixes, and new features
This project will involve work in Python and Javascript (server-side,
not browser), using both Git and Mercurial repositories. You may even
get a chance to make some changes to the Firefox source code itself.
The tasks involve understanding how things work now, how we would like
them to work, and how to get them there rather than deeply technical
algorithm implementation. They will probably change as we learn more
-- no plan survives breakfast. It turns out most of software
engineering is like that!
Taskcluster involves its Outreachy participants as full members of the
team. You will work with other Mozillians where your work overlaps
with theirs, and you are encouraged to attend and participate in team
meetings and irc conversations. We will provide you with all the help
and support you need. You can see some of our community of
contributors at https://docs.taskcluster.net/people.
===Add-ons Linter===
'''Mentor:''' Christopher Grebs <br />
'''IRC:''' cgrebs
'''Project Description'''
The add-ons linter project aims to find common issues within with a web-extension both used as a development tool and as at the point of submission via https://addons.mozilla.org (AMO). It aims to guide Add-on developers to avoid common mistakes and potential security vulnerabilities.
The linter is written in JavaScript and runs under Node.js. A potential mentee should already have a good understanding of JavaScript and be familiar with ES2015+ syntax. The linter is heavily unit tested so it would be expected that all patches would maintain the current level of code-coverage.
This list contains suggestions issues that could be of interest. Each item is a discrete piece of work. The list features largest items first.
Localization: Add-on developers come from many different countries and regions. We’d like to setup the linter to be fully localized in the same list of countries as https://addons.mozilla.org (AMO). See the following issues for an idea for what’s involved https://github.com/mozilla/addons-linter/issues/1535
Migrate to Await/Async - the linter currently makes heavy use of promises. The newer Await/Async syntax makes code easier to read and understand. See the issues for additional details as to what is involved https://github.com/mozilla/addons-linter/issues/1536. This task requires a good understanding of promises and their various nuances.
Improving validation. There’s several areas where the validation the linter currently provides could be improved here’s a few suggested areas to start:
Improve the feedback given to developers about icon usage: See https://github.com/mozilla/addons-linter/labels/component%3A%20icons for more details.
Permissions. The linter could do more to inform the developer of relevant information related to the permissions they have asked for in the manifest.json. See this label for more information https://github.com/mozilla/addons-linter/labels/component%3A%20permissions
Improve issues related to schema validation. See https://github.com/mozilla/addons-linter/labels/component%3A%20schema for more details.
==Outreachy Program Cohort: Round 14 (May 30 -Aug 30, 2017)==
