* [http://kernelnewbies.org/OPWMentor Information for mentors, from Linux Kernel project]
==Upcoming Current Outreachy ProgramCohort: Round 12 (June-August 2016)==
== Key Dates =Make Firefox look great on desktop! [no longer taking applicants] ===* February 22 Applications are open!Mentor: [https://mozillians.org/en-US/u/Gijs/ Gijs Kruitbosch]* February 28 Mentor applications closeParticipant: [https://mozillians.org/en-US/u/Rakhi/ Rakhi Sharma]* March 22 [http://rakhisharma.github.io/Verbose-Journal/ Participant Applications dueBlog] Firefox for desktop is used by hundreds of millions of people every day. We control what it looks like using CSS, XUL (a markup language that's a bit like HTML), and JavaScript. There's also a small amount of C++ here and there. For this project, the participant will help to address a number of styling problems where Firefox does not currently look its best. = For Future Applicants = * Next Outreachy round is Winter 2016-17. Keep in touch by reading here or on gnome.org/outreachy to learn application deadlines.
== Application Process ==
To get a feel for things before the project begins, you can open up the Browser Toolbox and ""inspect"" the UI of the browser. From there you can use MXR (http://mxr.mozilla.org/) to go from searching for some text on a button you see in the user interface to finding the code that is executed when the button is clicked.
===Make Firefox look great on desktop! [no longer taking applicants] ===
*Mentor: [https://mozillians.org/en-US/u/Gijs/ Gijs Kruitbosch]
Firefox for desktop is used by hundreds of millions of people every day. We control what it looks like using CSS, XUL (a markup language that's a bit like HTML), and JavaScript. There's also a small amount of C++ here and there.
For this project, we'd like your help to address a number of styling problems where Firefox does not currently look its best. First we would show you around the codebase we have. We'd show you how the JS, CSS and UI is organized, and some of the different configurations in which people use Firefox. You would then be responsible for things like:
* Making sure the separators between Firefox's tabs look good and appear in the right places;
* Fixing arrow panels to appear at a consistent distance from their anchor points;
* Improving our support for Windows' High Contrast themes;
* Adjusting the styling of complex toolbar buttons such as the bookmarks button;
* Creating better-looking <select> popups in Firefox with process separation;
You'd mostly be writing JS and CSS, though being comfortable with some of the other technologies we use will be helpful.
Want to get started? You can:
* use the [https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox Browser Toolbox] to have a look around a regular install of Firefox for our CSS and markup;
* [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build set up the source tree] and [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds create an "artifact build" of Firefox] so you can quickly change CSS, test it and submit patches;
* submit patches for one of the [https://mzl.la/1WWxOcZ outreachy 'easy' theme bugs].
===Web Platform Test Crime Scene Investigation===
