https://wiki.mozilla.org/api.php?action=feedcontributions&user=MykMelez&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T23:30:20ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1204601GitHub/Gecko Repositories2018-11-29T16:33:41Z<p>MykMelez: refer to gecko-projects with a consistent org prefix</p>
<hr />
<div>= Gecko Repositories on GitHub =<br />
<br />
There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko.<br />
<br />
== mozilla/gecko-dev ==<br />
<br />
mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
== mozilla/gecko-projects ==<br />
<br />
mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is maintained and synchronized similarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
As with gecko-dev, no commits are made in Git on gecko-projects.<br />
<br />
== mozilla/gecko ==<br />
<br />
mozilla/gecko is a mirror of a single Mercurial repository, mozilla-central as well as CVS history (in the "cvs" branch, which can be attached to the "central" branch via <code>git fetch origin 'refs/replace/*:refs/replace/*'</code>). It doesn't include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo.<br />
<br />
=== Integrating mozilla-central and CVS History ===<br />
<br />
mozilla/gecko integrates the mozilla-central and CVS histories via [https://git-scm.com/docs/git-replace Git replace]. To traverse the combined history of those repos, clone/fetch mozilla/gecko, then fetch replacement refs via this command:<br />
<br />
<code>git fetch origin 'refs/replace/*:refs/replace/*'</code><br />
<br />
(Replace "origin" with the name of your mozilla/gecko remote, if it differs.)<br />
<br />
Then common Git commands (diff, log, bisect, etc.) will behave as if the oldest commit on the "central" branch (e18f9a3) is the newest commit on the "cvs" branch (3ec464b), and you can traverse history accordingly.<br />
<br />
Note that the GitHub website doesn't support the replacement ref, presumably because it depends on libgit2, which doesn't support replacement refs per [https://github.com/libgit2/libgit2/issues/1730 issue 1730]. So you can't traverse the combined history of both branches transparently on the GitHub website.<br />
<br />
=== Using mozilla/gecko With try/inbound ===<br />
<br />
Note that cloning mozilla/gecko doesn't fetch git-cinnabar metadata, so you can't use it to push to Mercurial repositories like try and inbound unless you also fetch mozilla-central using git-cinnabar. Thus, for developers that need to push to such repos, it's better to clone mozilla-central via git-cinnabar directly (unless you need CVS history).<br />
<br />
(This may change with git-cinnabar 0.5.0, which is in beta as of this writing.)</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1197153GitHub/Gecko Repositories2018-07-11T20:32:49Z<p>MykMelez: explain that/why GitHub doesn't support replacement ref</p>
<hr />
<div>= Gecko Repositories on GitHub =<br />
<br />
There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko.<br />
<br />
== mozilla/gecko-dev ==<br />
<br />
mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
== gecko-projects ==<br />
<br />
mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is maintained and synchronized similarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
As with gecko-dev, no commits are made in Git on gecko-projects.<br />
<br />
== mozilla/gecko ==<br />
<br />
mozilla/gecko is a mirror of a single Mercurial repository, mozilla-central as well as CVS history (in the "cvs" branch, which can be attached to the "central" branch via <code>git fetch origin 'refs/replace/*:refs/replace/*'</code>). It doesn't include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo.<br />
<br />
=== Integrating mozilla-central and CVS History ===<br />
<br />
mozilla/gecko integrates the mozilla-central and CVS histories via [https://git-scm.com/docs/git-replace Git replace]. To traverse the combined history of those repos, clone/fetch mozilla/gecko, then fetch replacement refs via this command:<br />
<br />
<code>git fetch origin 'refs/replace/*:refs/replace/*'</code><br />
<br />
(Replace "origin" with the name of your mozilla/gecko remote, if it differs.)<br />
<br />
Then common Git commands (diff, log, bisect, etc.) will behave as if the oldest commit on the "central" branch (e18f9a3) is the newest commit on the "cvs" branch (3ec464b), and you can traverse history accordingly.<br />
<br />
Note that the GitHub website doesn't support the replacement ref, presumably because it depends on libgit2, which doesn't support replacement refs per [https://github.com/libgit2/libgit2/issues/1730 issue 1730]. So you can't traverse the combined history of both branches transparently on the GitHub website.<br />
<br />
=== Using mozilla/gecko With try/inbound ===<br />
<br />
Note that cloning mozilla/gecko doesn't fetch git-cinnabar metadata, so you can't use it to push to Mercurial repositories like try and inbound unless you also fetch mozilla-central using git-cinnabar. Thus, for developers that need to push to such repos, it's better to clone mozilla-central via git-cinnabar directly (unless you need CVS history).<br />
<br />
(This may change with git-cinnabar 0.5.0, which is in beta as of this writing.)</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1193350GitHub/Gecko Repositories2018-05-07T15:31:23Z<p>MykMelez: add command to connect "cvs" branch to "central" branch</p>
<hr />
<div>= Gecko Repositories on GitHub =<br />
<br />
There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko.<br />
<br />
== mozilla/gecko-dev ==<br />
<br />
mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
== gecko-projects ==<br />
<br />
mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is maintained and synchronized similarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
As with gecko-dev, no commits are made in Git on gecko-projects.<br />
<br />
== mozilla/gecko ==<br />
<br />
mozilla/gecko is a mirror of a single Mercurial repository, mozilla-central as well as CVS history (in the "cvs" branch, which can be attached to the "central" branch via <code>git fetch origin 'refs/replace/*:refs/replace/*'</code>). It doesn't include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo.<br />
<br />
=== Integrating mozilla-central and CVS History ===<br />
<br />
mozilla/gecko integrates the mozilla-central and CVS histories via [https://git-scm.com/docs/git-replace Git replace]. To traverse the combined history of those repos, clone/fetch mozilla/gecko, then fetch replacement refs via this command:<br />
<br />
<code>git fetch origin 'refs/replace/*:refs/replace/*'</code><br />
<br />
(Replace "origin" with the name of your mozilla/gecko remote, if it differs.)<br />
<br />
Then common Git commands (diff, log, bisect, etc.) will behave as if the oldest commit on the "central" branch (e18f9a3) is the newest commit on the "cvs" branch (3ec464b), and you can traverse history accordingly.<br />
<br />
=== Using mozilla/gecko With try/inbound ===<br />
<br />
Note that cloning mozilla/gecko doesn't fetch git-cinnabar metadata, so you can't use it to push to Mercurial repositories like try and inbound unless you also fetch mozilla-central using git-cinnabar. Thus, for developers that need to push to such repos, it's better to clone mozilla-central via git-cinnabar directly (unless you need CVS history).<br />
<br />
(This may change with git-cinnabar 0.5.0, which is in beta as of this writing.)</div>MykMelezhttps://wiki.mozilla.org/index.php?title=All_Hands/SanFrancisco2018&diff=1191641All Hands/SanFrancisco20182018-04-02T20:08:49Z<p>MykMelez: correct walking distance from hotel to Exploratorium (from 1.7 miles, which is the driving distance, to 1.5 miles, which is the correct walking distance)</p>
<hr />
<div>'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style! <br />
<br />
'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''<br />
<br />
=='''Dates, Location and Weather'''==<br />
Monday, June 11 - Friday, June 15, 2018 (travel days are Monday the 11th & Saturday the 16th) in San Francisco, CA.<br />
<br />
We are staying at [http://www.marriott.com/hotels/travel/sfodt-san-francisco-marriott-marquis/ San Francisco Marriott Marquis].<br />
<br />
''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to be pre-approved and pre-arranged.''<br />
<br />
Weather:<br />
* National Weather Service: [http://forecast.weather.gov/MapClick.php?smap=1&lat=37.785&lon=-122.410&unit=1&mp=1 forecast in ⁰C], [http://forecast.weather.gov/MapClick.php?smap=1&lat=37.785&lon=-122.410&mp=1 forecast in ⁰F]<br />
* Temperatures ''in downtown San Francisco'' in late June are likely to have nighttime lows around 10-13 ⁰C / 50-56 ⁰F and daytime highs around 16-24 ⁰C / 61-75 ⁰F. But the weather is very occasionally warmer with highs around 27⁰C / 81⁰F.<br />
* Weather in San Francisco in the summer is variable; it can become substantially cooler and foggier in the late afternoon; be prepared for temperatures to fall to 13⁰C / 56⁰F and the winds to pick up in the afternoon. Be prepared by carrying a warmer layer with you.<br />
* Weather in other parts of the Bay Area can be much warmer than in San Francisco, even if you're only traveling 15km away. Look at the weather forecasts for where you're going. It's entirely possible for it to be 19⁰C / 66⁰F in San Francisco and simultaneously be 32⁰C / 90⁰F in Orinda. But if you're right on the ocean, the air temperature is likely to match the water temperature, which is probably around 12⁰C / 54⁰F.<br />
<br />
=='''Registration'''==<br />
This is an invitation-only event.<br />
<br />
Advance registration is required. Attendees, guests and local guests will need to wear their event badge at all times, including to evening events.<br />
<br />
=====New Hires=====<br />
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.<br />
<br />
Monday, May 7 is the deadline for hiring. Friday, May 11 is the deadline that all new hires who must travel to the all hands but be registered and have travel booked. Friday, May 18 is the deadline for Bay Area/local new hires who do not need hotel or to travel need to be registered. All new hires must start on or before May 29.<br />
<br />
==== Contributors participation ====<br />
The process for this is [[All Hands/SanFrancisco2018/Contributor_nominations|outlined on this page]]. <br />
<br />
All nominations will be done by employees, with a coordinator from each of the Firefox/Product, Emerging Technologies, Marketing, Open Innovation and People parts of the organization. There will be no open call for nominations from contributors or volunteer Mozillians.<br />
<br />
Please note: The information on this wiki primarily applies to fulltime and contractor staff. If you have questions about how specifics apply to you, please email groter@mozilla.com and bmark@mozilla.com.<br />
<br />
=='''Week at a Glance'''==<br />
=====Monday=====<br />
Monday is primarily your travel day. You'll be able to pick up your registration stuff between 12:00 pm and 9:00 pm, as well as attend the Welcome Reception at the City View at Meteron from 6:00 pm - 9:00 pm. <br />
<br />
=====Tuesday=====<br />
We'll start Tuesday with a Plenary session.<br />
<br />
=====Friday=====<br />
Our closing party with be at the Exploratorium from 7:00 pm- 11:00 pm. We'll provide transportation to/from the hotel & venue + if the weather is nice, you could walk (about 1.5 miles).<br />
<br />
=====Saturday=====<br />
Departure day only. No scheduled activities.<br />
<br />
===San Francisco All Hands Event Calendar===<br />
Link coming soon. Events will be live by early May. <br />
<br />
=====Create an account=====<br />
We don’t recommend using the same email & password as anything like bank accounts, etc. We care about your security!<br />
<br />
If you already have a Sched account from past All Hands, it still works, just log in with that.<br />
<br />
=====Add items to your calendar=====<br />
Just hit the circle on any agenda item to add it to your calendar (you do need to have an account & be logged in to do this)<br />
<br />
You can also share a link to meetings to invite others. Go into the meeting and copy the short link. You can email that out to anyone and they can quickly add it to their calendar. <br />
<br />
=====Subscribe to GCal Calendar Link=====<br />
Click on the mobile phone on the right hand side of the screen. All the calendar options are available here. <br />
You have the option to choose ALL meetings or YOUR meetings. Unless you have 400 items on your calendar, just select your calendar. It will add anything on your calendar to your GCal (also an option for Outlook and iCal). It syncs once per day.<br />
<br />
The "only syncs once per day" only applies to Google Calendar. With almost all other clients (like Apple Calendar, Outlook, or the calendar app on your phone) you can set the refresh interval, and Sched's instructions recommend 1 hour.<br />
<br />
Warning: This is a link that utilizes your username for the .ics file.<br />
<br />
=====From Mobile=====<br />
Visit from any mobile device - bookmark or add to your homescreen for quick access. There is a bonus icon you get by doing this. It caches the last time you opened the page offline and refreshes anytime you are connected.<br />
<br />
=====Cool things=====<br />
'''Filters'''<br />
<br />
We have better (much needed) filtering functionality. You can filter by:<br />
Departments (ex: Firefox)<br />
AND<br />
Functional Teams (ex: Dev Tools or EngOps)<br />
<br />
*Search by Room, Speaker/Leader<br />
<br />
'''Further Filtering'''<br />
*Audience - who should be there (ex: Team only or Invite)<br />
*Homerooms (you can quickly see what is happening in homerooms, by team) - why do you care? If you have a cross team meeting in their room, its a quick way to search<br />
*Views - Lots of view options. It defaults to the simple view, but there are quite a few options.<br />
<br />
=='''Food & Drink'''==<br />
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday. <br />
<br />
Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.<br />
<br />
===Monday Night===<br />
We will provide dinner at the Welcome Reception from 6:00 pm - 9:00 pm at City View by Meteron at the Welcome Reception. Since most of Monday is a travel day, you'll be on your own for meals except dinner. <br />
<br />
===Tuesday, Wednesday & Thursday Nights===<br />
Tuesday, Wednesday and Thursday evenings will be of your own to structure as you wish. Given how much you all seemed to like a more flexible dining experience, these three evenings will be of your own to structure as you wish.<br />
<br />
Here is how this will work:<br />
<br />
For each of these three evenings, once your meetings have concluded, you and your team, friends, new acquaintances, are free to explore San Francisco and to find somewhere great to eat that suits you. Each of you can expense a total of $180 over the three days (or $60/night).<br />
<br />
This amount includes:<br />
* Meal cost, including tax & gratuity<br />
* Any beverages<br />
* Transportation to/from the restaurant<br />
* Conversion fees (for credit cards) or cash withdrawal fees<br />
<br />
Anything over the $180 for the three evenings will be your own expense. The fine print:<br />
* If your team is hosting an evening event 1 of the 3 nights and the payment is coordinated (meaning, you don’t have to open your wallet and pay), you can expense up to $120 for the other 2 nights ($60 for each of the 2 nights you did have to open your wallet and pay).<br />
* You will be asked (later) to submit a San Francisco only expense report. You can submit ONE report for San Francisco only and must be submitted no later than August 31, 2017.<br />
* If your manager approves expenses above the $60 per night, that expense will go directly to your travel budget in your cost center.<br />
<br />
Volunteer Contributors & Interns will have a separate process that will be communicated directly.<br />
<br />
===Friday Night===<br />
We will provide dinner at the Closing Party from 7:00 pm - 11:00 pm at The Exploratorium.<br />
<br />
====What you need====<br />
Your SF All Hands name badge and Identification (you may be carded for alcohol).<br />
<br />
=='''Photos'''==<br />
==== Red Lanyards ====<br />
If you see someone with a red lanyard, please don't take photos of them. They have opted out of being in photography. We'll have these available at the registration desk.<br />
<br />
=='''Safety & Security'''==<br />
=====Meeting Security=====<br />
You'll need to have your badge on at all times in the hotel, as will your partners, vendors and family members anytime they are in the spaces.<br />
<br />
=====Device Security=====<br />
If you are traveling to the San Francisco All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)<br />
<br />
We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.<br />
<br />
=====Safety Tips=====<br />
SF Travel team also has some [https://sftravel.ent.box.com/s/p2ve63e1ctn74e0ai2x48mmgr9fdlvul tips about safety] in the city, including safety numbers and local hospitals.<br />
<br />
=='''Hotel'''==<br />
Hotel rooms are reserved for all employees & volunteers to stay all week, including employees based in San Francisco (just as if we were somewhere you don't live). We are hopeful Mozilla-locals will stay with the rest of us in the hotel - it's really part of what makes these events great. You will have the option to opt out of hotel in registration if you are local to the Bay Area and wish to commute. <br />
<br />
A few things to note:<br />
*Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US-resort standard and we aren't able to waive it (we tried). Please reach out to mozilla@shworldwide.com if this creates a hardship for you.<br />
*If you have any changes or questions about your reservation, email mozilla@shworldwide.com. The hotel cannot make changes to All Hands reservations (other than to add your guests - see #4) so we’d like very much if you didn’t try (it complicates things).<br />
*If you have guests joining you for all or part of the week, you will be responsible for adding them to your reservation (and covering any additional fees). To do this, you will need your confirmation number(s) and to know how old your kids are. Details on how to add them will come a few weeks after registration closes. <br />
<br />
====Payment on Check-in====<br />
Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US hotel standard and we aren't able to waive it (we tried).<br />
<br />
We recommend providing a credit card. You can provide a debit card, but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating. <br />
<br />
====Pre/post====<br />
Links will be provided when you are invited to register in mid-April to book hotel 3 days pre and 3 days post at our negotiated rate. The pre/post reservations will require the use of an LDAP email* so we can link them to your All Hands reservation. Rooms booked by any method except this link will not be linked to your main reservation. <br />
<br />
Rates start $179+tax/fees & for double occupancy.<br />
<br />
====Parking====<br />
Self-Parking is available at several lots nearby. The Marriott Marquis offers valet only - please do not park valet. Mozilla will not reimburse for parking, plan to commute the way you normally would in the city. If you have questions about parking, email bmark@mozilla.com.<br />
<br />
=='''Travel'''==<br />
Booking travel is now open. Please book itineraries by Friday, April 13, 2018. <br />
<br />
====Arriving Early/Departing Late Guidelines====<br />
<br />
Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, June 11 and leave on Saturday, June 16. Here are some exceptions: <br />
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, June 8 and Monday, June 18, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).<br />
* If you plan to spend some extra personal time in San Francisco (choosing to arrive before Monday, June 11 or depart after Saturday, June 16), you'll need to create an itinerary in Egencia for standard dates/locations within the San Francisco June 2018 Portal and compare to the custom dates you'd like. Please share the difference via email to bmark@mozilla.com before submitting the flight. You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of SFO w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.<br />
* If you are attending the Monday Core Influencer's event (by invite).<br />
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is no unilateral "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).<br />
<br />
====Booking Family Travel====<br />
Once travel has opened to staff, you may book family, whether they will accompany you on your flight or join us later; and you have two options: Direct or through Egencia. <br />
<br />
If you choose to book family through Egencia, please first book your own flight and then call Egencia with your airline confirmation number (staff do have to go through Egencia). Otherwise, you can book family direct (either through the airline or through another third party) and call the ticketing airline(s) with both confirmation numbers and ask them to link your reservations, so they know you are traveling together. They should also be able to assign seats together. You will avoid the limited hours Egencia offers and avoid paying their ticketing fee. <br />
<br />
If you prefer to book your family through Egencia, you can pay (including the Egencia booking fees) and coordinate with your own travel (recommend to book and then call/email Egencia with your itinerary number to match for family). Note that booking through Egencia does not put you on the same reservation, nor guarantee the reservations will be linked (you would still need to call the airline to link them). <br />
* '''Call:''' +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm EST. If you call outside these hours, you will get an after hours agent, who may not be as helpful. <br />
<br />
====Travel Insurance====<br />
Mozilla provides emergency medical accident and illness cover for all global MoCo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com. <br />
<br />
Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.<br />
<br />
=====''Air Travel Fine Print''=====<br />
Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.<br />
<br />
Mozilla will not reimburse for Business/First class upgrades or tickets. <br />
<br />
Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.<br />
<br />
=====Airport Shuttle=====<br />
All Mozillians and guests who have flights arriving anytime on Monday, June 11th in San Francisco International Airport (SFO) and out on Saturday, June 16th, will be transferred to the hotel. If you arrive into another airport (OAK or SJC) or on a different date, ground transportation is on your own.<br />
<br />
'''Arrivals to San Francisco International Airport (SFO)'''<br />
<br />
The airport has four terminals: Terminal 1, 2 & 3, and the International Terminal. For domestic flights In Terminals 1, 2 & 3 and the International Terminal (there are domestic flights), everyone will be greeted at the bottom of the escalator in the baggage claim for your terminal (even if you have no checked bags). Please identify yourself to the greeter and they will direct you to the shuttles for your terminal. <br />
<br />
For International Flights into the International terminal, you will collect your luggage and pass through customs. Once through customs, you will walk directly out to the main lobby, where you’ll find a greeter and they will direct your to your shuttle.<br />
<br />
Transfer time from the airport to the hotel is approximately 40-60 minutes.<br />
<br />
'''Departures from San Francisco International Airport (SFO)'''<br />
<br />
Everyone departing on Saturday, June 16th, will receive transportation to SFO. You will be met by transportation staff in the Marriott hotel lobby and assisted onto the shuttles. <br />
<br />
If you have questions about arrivals or departures, please email mozilla@shworldwide.com.<br />
<br />
====Alternate Transportation Options====<br />
For those arriving or departing on dates other than June 11 and 16. <br />
*[http://www.bart.gov/stations/powl BART] goes from SFO to the Powell Street Station for $8.95. Tickets can be purchased at the airport or in advance. <br />
*[http://www.samtrans.com/schedulesandmaps/timetables/292.html SamTrans bus Route 292] goes from SFO to Mission St. & 5th St. only for [http://www.samtrans.com/fares/farechart.html $2.25 (inbound) or $4 (outbound)].<br />
*[https://www.supershuttle.com/locations/sanfranciscosfo/ Super Shuttle]. Shared shuttle service. Book in advance. <br />
<br />
Other options can be found on the [https://www.flysfo.com/to-from/ground-transportation SFO website].<br />
<br />
====Mountain View Office Shuttle====<br />
We will provide a shuttle from the Mountain View office on Monday, June 11th (1:00 pm and 3:00 pm). They will depart from the main entrance. We will return to Mountain View on Saturday, June 16 (10:00 am and 12:30 pm). They will depart the Marriott. <br />
<br />
You can get dropped off or park at the office until 10:00 pm Sunday, June17. There will be normal security patrols however, you should remove valuables from view and secure your vehicle.<br />
<br />
====From the Bay Area but not taking the Mountain View Office Shuttle?====<br />
Our expectation is that you commute to the hotel just as you would to the office in the Bay Area. If you normally take the BART or MUNI, do that. If you normally drive and pay for parking - that's up to you but hotel parking is not a reimbursable expense for the All Hands.<br />
<br />
=='''Accessibility'''==<br />
<br />
'''Marriott Marquis'''<br />
<br />
The guestroom tower has accessible elevators, and accessible rooms (on request). The main entrance and pathway to hotel registration are accessible. All meeting space can be access via elevators. <br />
<br />
====Evenings====<br />
The Monday Night reception is at City View, which is located on the 4th floor of the METREON and is accessible from the ground floor via 2 passenger elevators and escalators. There is ADA access from all building entrances as well.. The Friday Night Party is at [https://www.exploratorium.edu/visit/accessibility Exploratorium], which has access to all levels by elevator. <br />
<br />
=='''Immigration'''==<br />
'''Any''' questions on immigration should be sent to immigration@mozilla.com.<br />
<br />
If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing times constantly change.<br />
<br />
Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview. Current estimated processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/<br />
<br />
Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:<br />
<br />
*Intend to enter the United States for 90 days or less for business, pleasure or transit<br />
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html<br />
*Have authorization to travel via the Electronic System for Travel Authorization: https://esta.cbp.dhs.gov/<br />
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)<br />
*Have a return or onward ticket<br />
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas<br />
<br />
=====Employee Travel FAQ=====<br />
This [https://mana.mozilla.org/wiki/display/PR/Travel+FAQ FAQ] addresses questions about how to handle security concerns and electronic devices at the border and how to engage with US Customs & Border Protection (CBP). While it specifically focuses on concerns related to travel to the United States, much of this guidance is applicable to travel elsewhere. Mana access required.<br />
<br />
=====Pocket Letter=====<br />
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register online. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.<br />
<br />
=====ESTA Point of Contact=====<br />
In the ESTA application you need to give a "U.S. Point of Contact Information". <br />
<br />
Please list Casey McGill as your US Point of Contact.<br />
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028<br />
<br />
=='''San Francisco All Hands Expense Policy'''==<br />
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. San Francisco All Hands Expense Report)<br />
<br />
2. It must contain only those expenses relative to the All Hands Event (5-10 days of pre-post activity only)<br />
<br />
3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses<br />
<br />
4. The deadline to submit the San Francisco All Hands Expense Report is '''July 31, 2018'''.<br />
<br />
5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved. <br />
<br />
'''The intention of our all hands are to centrally organize a structure that includes:'''<br />
*Meals (two/day + snacks)<br />
*Transportation^<br />
*Accommodations<br />
*Some number of social events<br />
<br />
Due to the nature of the San Francisco, employees will be expensing specific meals. The amount that can be expensed will be communicated and expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants. <br />
<br />
^Transportation for those based in the Bay Area is limited to "commuting" as you normally would. Expenses for commuting are not reimbursable. We have provided shuttles from the MV office for those based in the south bay. For those who that doesn't make sense to use, commute using your normal means. We will not reimburse for hotel parking. <br />
<br />
=====Cell phone reimbursement policy=====<br />
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense. <br />
<br />
=====Internet reimbursement policy=====<br />
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons. <br />
<br />
If you have questions about any of this, please reach out to bmark@mozilla.com<br />
<br />
=='''Families/Guests in San Francisco'''==<br />
<br />
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Family should not join you during your work sessions and meals. Please note that what we are able to do for families varies by each location. <br />
<br />
====Quick summary logistics====<br />
<br />
'''Air Travel''': Family travel can be booked/coordinated through Egencia by calling direct; or on your own. Employees do need to book via Egencia regardless of how families are booked.<br />
<br />
'''Hotel''': They are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates. Once hotel reservations are made, we will provide a link or contact add guests.<br />
<br />
Meals: Breakfast will be provided to All Hands registered guests, for lunch families are on their own. They are invited to join our Monday & Friday evening festivities, we just ask that you let us know they'll be there in registration.<br />
<br />
=='''Extracurricular Activities'''==<br />
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Firefox/Roadmap&diff=1191631Firefox/Roadmap2018-04-02T18:33:04Z<p>MykMelez: fix typo</p>
<hr />
<div><section begin=summary />{{RoadmapSummary<br />
|icon=Firefox-med-logo.png<br />
|pagelocation=Firefox/Roadmap<br />
|pagetitle=Firefox Product Roadmap<br />
|owner=Asa Dotzler<br />
|updated=<br />
|description=Firefox is a key expression of Mozilla's [https://www.mozilla.org/en-US/mission/ mission] and [https://www.mozilla.org/en-US/about/manifesto/ manifesto]; it represents our vision of a people-centric web experience, as well as a platform and tooling that make it possible to do amazing things with the web.<br />
}}<section end=summary /><br />
<br />
__NOTOC__<br />
<br />
'''<big>In 2018 Firefox browsers will be fast, personal, mobile, and opinionated.</big>'''<br />
<br />
No strategy can capture everything we're doing with the Firefox browsers over the next year, but this document covers the key focus areas: making Firefox browsers even faster, making them more personal, supercharging mobile, and getting opinionated on behalf of users. (All dates are estimates and subject to change.)<br />
<br />
To accomplish fast, Mozilla will continue the Quantum effort, replacing Gecko internal components with those prototyped in the Servo engine and updating and re-writing other areas of Firefox for performance and reliability.<br />
<br />
To become more personal, Mozilla will invest in making browser extensions easier to build, discover and use with more APIs, and changes to both the browser and the Mozilla add-ons service that expose add-ons to more people.<br />
<br />
On the mobile front, Firefox Klar will be getting the Quantum treatment with performance optimizations and re-writes, Firefox for iOS will be tuned for iPads and gain on-by-default Tracking Protection, and Firefox for FireTV will continue to mature. <br />
<br />
Last but not least, in 2018, Firefox will get more opinionated. People on the web deserve a browser that represents people first, a browser that isn't neutral when it comes to advertising, tracking and other dark patterns on the web.<br />
<br />
<br />
<hr><br />
<br />
<br />
=== Fast ===<br />
<br />
People love fast. 2017 was all about making Firefox faster and that's why we called it Firefox Quantum. There's still more room to improve and in 2018 Mozilla will continue to focus on speed. Bringing another significant component over from our research and development engine, Servo, will improve how smooth websites render. Updates to our content painting system will allow the main thread, and thus the browser UI and focused tab, to stay responsive, and changes to our networking stack will result in faster page loads.<br />
<br />
<br />
[https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/ WebRender]: With WebRender, we want web apps to run at a silky smooth 60 frames per second (FPS) no matter how big the display is or how much of the page is changing from frame to frame. Initial releases will be for selected Nvidia GPUs. (Firefox 64)<br />
<br />
[https://mozillagfx.wordpress.com/2018/01/09/retained-display-lists/ Retained Display List]: Gecko will retain the display list between paints, only building a new display list for the parts of the page that changed since we last painted and then merge the new list into the old to get an updated list. (Firefox 60)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1307504 Race Cache with Network]: When we detect that disk IO may be slow, we send a network request in parallel, and we use the first response that comes back. For users with slow spinning disks and a low latency network, the result would be faster loads. (Firefox 59)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1188435 TCP fast open]: a TCP extension to speed up the opening of successive TCP connections between two endpoints. (Firefox 60)<br />
<br />
[https://mikeconley.ca/blog/2018/01/11/making-tab-switching-faster-in-firefox-with-tab-warming/ Tab Warming]: "Tab warming" is what we're calling the process of pre-emptively rendering the layers for a tab, and preemptively uploading them to the compositor, when we're pretty sure you're likely to switch to that tab (61)<br />
<br />
[https://mozillagfx.wordpress.com/2017/12/05/off-main-thread-painting/ Off Main Thread Painting]: With OMTP the visual state of the page is still computed on the main thread, but the potentially costly task of rasterization is passed off to a designated “rasterization thread”, and the main thread can carry on and stay responsive. (Firefox 58 on Windows, 59 on Mac)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1425602 Async Blocklist Loading]: With async blocklist loading users will see faster startup times. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1385403 OOP Extensions for Mac] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1357487 Linux]: We've already shipped out of process extensions for Windows leading to faster page loads and more browser responsiveness. This year we'll catch up on Mac and Linux. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1371255 Replace storage.local] implementation: For improved extension performance, we will replace the storage.local implementation with something more efficient. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1361474 Interpreter ICs]: This will improve interpreter speed increasing the performance of JavaScript on sites and apps. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1336227 Faster startup first paint]: Firefox will show a browser window as soon as possible after startup, not waiting on the full stack to load. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1401624 Object-biased NaN Boxing]: a lot of code containing small loops do not benefit from any sort of optimization strategy. With Object-biased NaN boxing, we will see improved web page JavaScript performance. (2018)<br />
<br />
=== Personal ===<br />
<br />
Firefox has always been the most customizable browser available. This year, we're investing to make Firefox the best option for users to tailor their web experiences to their needs. We'll provide new APIs to make extensions and themes more capable and we'll add features in the browser and at addons.mozilla.org that help people discover and use add-ons that will make a difference. <br />
<br />
<br />
Context-aware AMO: People arrive at AMO for different reasons and with different levels of experience. We'll use the signals we receive to better assist the user with what they came for. (Q4)<br />
<br />
[https://blog.mozilla.org/data/2017/12/09/add-on-recommendations-for-firefox-users-a-prototype-recommender-system-leveraging-existing-data-sources/ Telemetry-Aware Add-on Recommender (TAAR)]: we will integrate our add-on recommender with addons.mozilla.org and within Firefox in places like Discovery Pane. (Q4)<br />
<br />
Contextual Feature Recommender: CFR is a system that proactively delivers personalized Firefox feature and extension recommendations to users based on their behaviour. (Q4)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1330328 Expanded Theme Support, and Element Theming Support in Extensions]: Firefox will become more themeable allowing users to customize additional browser components such as [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1330328&hide_resolved=1 sidebars, popups and scroll bars] (Q3) In addition, more APIs will be added to allow themed components to respond to different browser states such as active, inactive, focused and mouse-hover. (Q3)<br />
<br />
More Extension APIs: Firefox extensions will become more capable with additional features for tab management and organization, including a full implementation of [https://wiki.mozilla.org/WebExtensions/TabHiding Tab Hiding] (61) and [https://bugzilla.mozilla.org/show_bug.cgi?id=1437098 User Scripts] (61) APIs. Two other highly requested feature areas, [https://bugzilla.mozilla.org/show_bug.cgi?id=1215064 Toolbars] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1340930 Secure Overlays] (Q4) will land an initial set of development APIs, while other feature areas such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1427928 Session Management], Bookmark Management (Q3) and [https://bugzilla.mozilla.org/buglist.cgi?component=WebExtensions%3A%20Android&component=WebExtensions%3A%20Compatibility&component=WebExtensions%3A%20Developer%20Tools&component=WebExtensions%3A%20Experiments&component=WebExtensions%3A%20Frontend&component=WebExtensions%3A%20General&component=WebExtensions%3A%20Request%20Handling&component=WebExtensions%3A%20Storage&component=WebExtensions%3A%20Themes&component=WebExtensions%3A%20Untriaged&product=Toolkit&resolution=---&short_desc=clipboard&short_desc_type=allwordssubstr&list_id=14066067 Clipboard Interaction] (Q2) will be rounded out with incremental APIs.<br />
<br />
User-created Themes: In addition to installing themes from Mozilla Add-ons website, Firefox users will be able to easily design, use, and share their own unique browser themes. (October)<br />
<br />
Provide Firefox installers to non-Firefox users visiting AMO. Instead of offering an “Install” button to a non-Firefox client viewing add-ons on AMO, a stub installer may be offered that provides the user with Firefox and the add-on viewed. (May)<br />
<br />
[https://mozilla-lockbox.github.io/ Lockbox] integration with Firefox: Mozilla's new password manager will integrate with Firefox and Firefox accounts allowing users to take their passwords beyond the browser. (2018)<br />
<br />
Multi-factor auth for Firefox Accounts: Firefox Accounts will get multi-factor auth via Time-based One-Time Passwords. (Q2)<br />
<br />
Account Recovery for Firefox Accounts: offer users a first version of our account recovery mechanism which allows users to recover their encrypted data even if they've forgotten their password. (Q3)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1325870 Language Switching]: Provide an interface for users to switch languages and make language pack discovery and installation part of the Firefox UX. (63)<br />
<br />
[https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment Policy Manager]: Firefox will allow computer administrators to customize features (e.g. proxy, default bookmarks, etc.) for their users. The policy manager supports two implementations: A policies.json file in the distribution directory or Windows GPO. (Firefox 60)<br />
<br />
=== Mobile ===<br />
<br />
In 2017 we focused almost totally on making desktop Firefox blazing fast with the Quantum effort. This year we expand our focus to include more mobile work, with new products like Lockbox, and targeted feature updates that will make all of our mobile apps silky smooth, more powerful, and a joy to use whether it's Firefox for Android, Firefox for iOS, Firefox for FireTV, or Firefox Focus and Klar.<br />
<br />
<br />
[https://wiki.mozilla.org/Mobile/GeckoView#Bugs Transition Klar to GeckoView]: Currently, the Firefox Klar browser uses WebView to render sites. We're moving to GeckoView, which will bring WebAssembly, WebRTC, WebGL 2, WebVR, and other emerging, modern web technologies to the Klar browser (Q3). <br />
<br />
Klar Features: Klar will also gain Search and Autocomplete (May), anti-fingerprinting, an A/B testing framework, and Contextual hints (July)<br />
<br />
Stylo in Firefox for Android: Firefox for Android will be getting some “Quantum” treatment with the incorporation of the Stylo CSS engine. (60)<br />
<br />
Firefox for iOS will gain [https://bugzilla.mozilla.org/show_bug.cgi?id=1433453 Drag and Drop from other applications], [https://bugzilla.mozilla.org/show_bug.cgi?id=1433455 Full Hardware Keyboard support], Tracking Protection enabled by default in an upcoming release in early April. More updates and navigational improvements, specifically for iPad will be coming up later in the summer.<br />
<br />
Updates for Firefox Focus for Android: Firefox Focus will get Search and Autocomplete (May), Request Desktop Site, an A/B testing framework, Contextual hints (July), Find in page and more ad and tracker blocking (December).<br />
<br />
Firefox for FireTV matures: Firefox for FireTV will gain custom tiles (Q1), parental controls, Pocket video feed, request desktop site (Q2), and a custom keyboard with Awesomebar powers. (Q3)<br />
<br />
Lockbox Mobile apps: People will be able to access their saved passwords in an iOS app with an Android app to follow. (2018)<br />
<br />
<br />
=== Opinionated === <br />
<br />
The web has grown and changed dramatically over the last two decades and not all for the better. Trackers, intrusive ads and other dark patterns threaten to drive people away from the open web and that's not good for people browsing or publishing. Over the next year or so, Firefox will take a stand against tracking, intrusive ads, and other dark patterns on the web by blocking the worst content and more clearly communicating the privacy and other protections the browser offers. <br />
<br />
<br />
Filter certain types of ads by default: Firefox will offer users a simple ad filtering option. We're in the early stages still, researching types of advertisements that should be blocked by default. (Q3)<br />
<br />
Block ad re-targeting: We are working on blocking cross-domain tracking. Details to follow. (Q3)<br />
<br />
New Privacy Controls: We will bring all of our key privacy controls into a single location in the product making them more discoverable and putting users in control of their data privacy experience. (Q3)<br />
<br />
Tracking Protection Improvements: We would like to make tracking protection more fine-grained allowing users to turn on or off specific types of tracker. We will also opportunistically block trackers when page load performance is adversely impacted. (Q3)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1368744 Global permissions management]: Permission prompts, especially for notifications, have gotten out of control and users must deny them individually at every site that offers them. Firefox will provide users with a way to disable permission prompts globally for Location, Camera, Microphone, and Notifications. (Firefox 59) <br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1382574 Block video auto-play]: Firefox will provide users with a way to block video auto-play that doesn't break websites. (62)<br />
<br />
[https://github.com/mozilla/blurts-server Breach Alerts]: Breach alerts will inform a user if a site they've visited has been breached and will ask if the user wants to have their account checked to determine if it was compromised. If it was compromised, some helpful information will be presented to the user. (October)<br />
<br />
<br />
=== Web Platform and Tooling advancements ===<br />
<br />
The roadmap described above focuses primarily on the Firefox consumer products. Web developers will not be left out and will see significant improvements to the Firefox web platform and our developer and designer tooling. <br />
<br />
<br />
Web Components: Implementations of the new consensus-based [https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM Shadow DOM] and [https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements Custom Elements] are expected to ship in Firefox 63<br />
<br />
[https://jakearchibald.com/2017/es-modules-in-browsers/ ES6 Modules]: Allows you to use native ECMAScript modules, for example defining modules with <script type="module">, defining fallback scripts with <script nomodule>, and importing code features that have been exported from modules. (60)<br />
<br />
[https://wiki.mozilla.org/TPE-Layout/Dashboard#CSS_Shapes CSS Shapes]: CSS Shapes can be applied to floats. A circle shape on a float will cause inline content to wrap around the circle shape instead of the float's bounding box. (61)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1302685 Variable Fonts] (OpenType Font Variations): the technology enables a single font file to behave like multiple fonts. (61) <br />
<br />
[https://groups.google.com/forum/#!msg/mozilla.dev.platform/tsevyqfBHLE/lccldWNNBwAJ Web Authentication]: an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. (60)<br />
<br />
[https://www.w3.org/TR/pointerevents/ W3C Pointer Events]: creates a single DOM event model to handle pointing input devices such as a mouse, pen/stylus or touch. (59)<br />
<br />
<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1433716 3-Panel Inspector]: This feature allows the Rules view to detach into its own dedicated panel. As result, developers have the ability to author and debug CSS at the same time.(61)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1242029 Shapes Path Editor]: The Shape Path Editor is a developer tool that allows modification of CSS Shapes and Clip Paths right in the browser. In Firefox 61 the platform will support the Shape Outside CSS property and we will extend the tool to go with the platform feature.(61)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1280059 New Font Tooling]: In Firefox 61, the layout team introduces support for Variable Fonts. We take this opportunity to rethink Firefox' fonts tooling and provide a new experience to developers working on both variable and non-variable fonts. (61 through 63, shipped in steps)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1409965 Flexbox Inspector]: The Flexbox Inspector will allow developers to highlight and debug the flexbox layout model. In later releases (66) we will add separate tools to analyze Alignment and Sizing of elements. (64)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=devtools-app-panel-m1 Service Workers panel]: developers need to have a solid Service Worker debugging experience that matches Chrome's experience so they can make sure their apps work in Firefox. (61)<br />
<br />
Source Maps Excellence: Source Maps are the translation layer for developers to transform and minify their original code with modern tools while keeping it debuggable. Going beyond what any browser currently provides, our tools will map variables and correctly step through original code. (61)<br />
<br />
Framework Support: Attract back modern web app developers into our tools by matching up how devtools represent frameworks (components, state, errors, callstacks, etc) to the mental models of developers (Q3)<br />
<br />
Context-based Devtools Feature Recommendation: Recommend features and extensions based on developers' technologies to level users up into advanced features and developer extensions for a stickier experience. (Q3)<br />
<br />
Onboarding for Chrome devtools users: Show users switching from Chrome around; what's cool, what's different from Chrome and what's new. (Q3)<br />
<br />
Performance Profiling for GeckoView: Enable the performance tooling that made Quantum Flow a success for the GeckoView project (61)<br />
<br />
Remote Debugging: Support mobile push needs a solid mobile debugging experience, by replacing WebIDE with a modern and well integrated flow that doesn't get in the way. (62/63)<br />
<br />
<br />
<hr><br />
<br />
=== Firefox Product Roadmap Timeline (click image to view the spreadsheet) ===<br />
<br />
<br />
[[File:Firefox-timeline-2018-03-21.png|800px|Firefox Timeline|link=https://docs.google.com/spreadsheets/d/1U1IxTOlsaBcRsnJv0XAaVqQLU4otB6h2lG0NDcvWG-E/edit?usp=sharing]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Firefox/Roadmap&diff=1191629Firefox/Roadmap2018-04-02T18:30:34Z<p>MykMelez: fix typo</p>
<hr />
<div><section begin=summary />{{RoadmapSummary<br />
|icon=Firefox-med-logo.png<br />
|pagelocation=Firefox/Roadmap<br />
|pagetitle=Firefox Product Roadmap<br />
|owner=Asa Dotzler<br />
|updated=<br />
|description=Firefox is a key expression of Mozilla's [https://www.mozilla.org/en-US/mission/ mission] and [https://www.mozilla.org/en-US/about/manifesto/ manifesto]; it represents our vision of a people-centric web experience, as well as a platform and tooling that make it possible to do amazing things with the web.<br />
}}<section end=summary /><br />
<br />
__NOTOC__<br />
<br />
'''<big>In 2018 Firefox browsers will be fast, personal, mobile, and opinionated.</big>'''<br />
<br />
No strategy can capture everything we're doing with the Firefox browsers over the next year, but this document covers the key focus areas: making Firefox browsers even faster, making them more personal, supercharging mobile, and getting opinionated on behalf of users. (All dates are estimates and subject to change.)<br />
<br />
To accomplish fast, Mozilla will continue the Quantum effort, replacing Gecko internal components with those prototyped in the Servo engine and updating and re-writing other areas of Firefox for performance and reliability.<br />
<br />
To become more personal, Mozilla will invest in making browser extensions easier to build, discover and use with more APIs, and changes to both the browser and the Mozilla add-ons service that expose add-ons to more people.<br />
<br />
On the mobile front, Firefox Klar will be getting the Quantum treatment with performance optimizations and re-writes, Firefox for iOS will be tuned for iPads and gain on-by-default Tracking Protection, and Firefox for FireTV will continue to mature. <br />
<br />
Last but not least, in 2018, Firefox will get more opinionated. People on the web deserve a browser that represents people first, a browser that isn't neutral when it comes to advertising, tracking and other dark patterns on the web.<br />
<br />
<br />
<hr><br />
<br />
<br />
=== Fast ===<br />
<br />
People love fast. 2017 was all about making Firefox faster and that's why we called it Firefox Quantum. There's still more room to improve and in 2018 Mozilla will continue to focus on speed. Bringing another significant component over from our research and development engine, Servo, will improve how smooth websites render. Updates to our content painting system will allow the main thread, and thus the browser UI and focused tab, to stay responsive, and changes to our networking stack will result in faster page loads.<br />
<br />
<br />
[https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/ WebRender]: With WebRender, we want web apps to run at a silky smooth 60 frames per second (FPS) no matter how big the display is or how much of the page is changing from frame to frame. Initial releases will be for selected Nvidia GPUs. (Firefox 64)<br />
<br />
[https://mozillagfx.wordpress.com/2018/01/09/retained-display-lists/ Retained Display List]: Gecko will retain the display list between paints, only building a new display list for the parts of the page that changed since we last painted and then merge the new list into the old to get an updated list. (Firefox 60)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1307504 Race Cache with Network]: When we detect that disk IO may be slow, we send a network request in parallel, and we use the first response that comes back. For users with slow spinning disks and a low latency network, the result would be faster loads. (Firefox 59)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1188435 TCP fast open]: a TCP extension to speed up the opening of successive TCP connections between two endpoints. (Firefox 60)<br />
<br />
[https://mikeconley.ca/blog/2018/01/11/making-tab-switching-faster-in-firefox-with-tab-warming/ Tab Warming]: "Tab warming" is what we're calling the process of pre-emptively rendering the layers for a tab, and preemptively uploading them to the compositor, when we're pretty sure you're likely to switch to that tab (61)<br />
<br />
[https://mozillagfx.wordpress.com/2017/12/05/off-main-thread-painting/ Off Main Thread Painting]: With OMTP the visual state of the page is still computed on the main thread, but the potentially costly task of rasterization is passed off to a designated “rasterization thread”, and the main thread can carry on and stay responsive. (Firefox 58 on Windows, 59 on Mac)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1425602 Async Blocklist Loading]: With async blocklist loading users will see faster startup times. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1385403 OOP Extensions for Mac] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1357487 Linux]: We've already shipped out of process extensions for Windows leading to faster page loads and more browser responsiveness. This year we'll catch up on Mac and Linux. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1371255 Replace storage.local] implementation: For improved extension performance, we will replace the storage.local implementation with something more efficient. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1361474 Interpreter ICs]: This will improve interpreter speed increasing the performance of JavaScript on sites and apps. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1336227 Faster startup first paint]: Firefox will show a browser window as soon as possible after startup, not waiting on the full stack to load. (2018)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1401624 Object-biased NaN Boxing]: a lot of code containing small loops do not benefit from any sort of optimization strategy. With Object-biased NaN boxing, we will see improved web page JavaScript performance. (2018)<br />
<br />
=== Personal ===<br />
<br />
Firefox has always been the most customizable browser available. This year, we're investing to make Firefox the best option for users to tailor their web experiences to their needs. We'll provide new APIs to make extensions and themes more capable and we'll add features in the browser and at addons.mozilla.org that help people discover and use add-ons that will make a difference. <br />
<br />
<br />
Context-aware AMO: People arrive at AMO for different reasons and with different levels of experience. We'll use the signals we receive to better assist the user with what they came for. (Q4)<br />
<br />
[https://blog.mozilla.org/data/2017/12/09/add-on-recommendations-for-firefox-users-a-prototype-recommender-system-leveraging-existing-data-sources/ Telemetry-Aware Add-on Recommender (TAAR)]: we will integrate our add-on recommender with addons.mozilla.org and within Firefox in places like Discovery Pane. (Q4)<br />
<br />
Contextual Feature Recommender: CFR is a system that proactively delivers personalized Firefox feature and extension recommendations to users based on their behaviour. (Q4)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1330328 Expanded Theme Support, and Element Theming Support in Extensions]: Firefox will become more themeable allowing users to customize additional browser components such as [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1330328&hide_resolved=1 sidebars, popups and scroll bars] (Q3) In addition, more APIs will be added to allow themed components to respond to different browser states such as active, inactive, focused and mouse-hover. (Q3)<br />
<br />
More Extension APIs: Firefox extensions will become more capable with additional features for tab management and organization, including a full implementation of [https://wiki.mozilla.org/WebExtensions/TabHiding Tab Hiding] (61) and [https://bugzilla.mozilla.org/show_bug.cgi?id=1437098 User Scripts] (61) APIs. Two other highly requested feature areas, [https://bugzilla.mozilla.org/show_bug.cgi?id=1215064 Toolbars] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1340930 Secure Overlays] (Q4) will land an initial set of development APIs, while other feature areas such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1427928 Session Management], Bookmark Management (Q3) and [https://bugzilla.mozilla.org/buglist.cgi?component=WebExtensions%3A%20Android&component=WebExtensions%3A%20Compatibility&component=WebExtensions%3A%20Developer%20Tools&component=WebExtensions%3A%20Experiments&component=WebExtensions%3A%20Frontend&component=WebExtensions%3A%20General&component=WebExtensions%3A%20Request%20Handling&component=WebExtensions%3A%20Storage&component=WebExtensions%3A%20Themes&component=WebExtensions%3A%20Untriaged&product=Toolkit&resolution=---&short_desc=clipboard&short_desc_type=allwordssubstr&list_id=14066067 Clipboard Interaction] (Q2) will be rounded out with incremental APIs.<br />
<br />
User-created Themes: In addition to installing themes from Mozilla Add-ons website, Firefox users will be able to easily design, use, and share their own unique browser themes. (October)<br />
<br />
Provide Firefox installers to non-Firefox users visiting AMO. Instead of offering an “Install” button to a non-Firefox client viewing add-ons on AMO, a stub installer may be offered that provides the user with Firefox and the add-on viewed. (May)<br />
<br />
[https://mozilla-lockbox.github.io/ Lockbox] integration with Firefox: Mozilla's new password manager will integrate with Firefox and Firefox accounts allowing users to take their passwords beyond the browser. (2018)<br />
<br />
Multi-factor auth for Firefox Accounts: Firefox Accounts will get multi-factor auth via Time-based One-Time Passwords. (Q2)<br />
<br />
Account Recovery for Firefox Accounts: offer users a first version of our account recovery mechanism which allows users to recover their encrypted data even if they've forgotten their password. (Q3)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1325870 Language Switching]: Provide an interface for users to switch languages and make language pack discovery and installation part of the Firefox UX. (63)<br />
<br />
[https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment Policy Manager]: Firefox will allow computer administrators to customize features (e.g. proxy, default bookmarks, etc.) for their users. The policy manager supports two implementations: A policies.json file in the distribution directory or Window GPO. (Firefox 60)<br />
<br />
<br />
=== Mobile ===<br />
<br />
In 2017 we focused almost totally on making desktop Firefox blazing fast with the Quantum effort. This year we expand our focus to include more mobile work, with new products like Lockbox, and targeted feature updates that will make all of our mobile apps silky smooth, more powerful, and a joy to use whether it's Firefox for Android, Firefox for iOS, Firefox for FireTV, or Firefox Focus and Klar.<br />
<br />
<br />
[https://wiki.mozilla.org/Mobile/GeckoView#Bugs Transition Klar to GeckoView]: Currently, the Firefox Klar browser uses WebView to render sites. We're moving to GeckoView, which will bring WebAssembly, WebRTC, WebGL 2, WebVR, and other emerging, modern web technologies to the Klar browser (Q3). <br />
<br />
Klar Features: Klar will also gain Search and Autocomplete (May), anti-fingerprinting, an A/B testing framework, and Contextual hints (July)<br />
<br />
Stylo in Firefox for Android: Firefox for Android will be getting some “Quantum” treatment with the incorporation of the Stylo CSS engine. (60)<br />
<br />
Firefox for iOS will gain [https://bugzilla.mozilla.org/show_bug.cgi?id=1433453 Drag and Drop from other applications], [https://bugzilla.mozilla.org/show_bug.cgi?id=1433455 Full Hardware Keyboard support], Tracking Protection enabled by default in an upcoming release in early April. More updates and navigational improvements, specifically for iPad will be coming up later in the summer.<br />
<br />
Updates for Firefox Focus for Android: Firefox Focus will get Search and Autocomplete (May), Request Desktop Site, an A/B testing framework, Contextual hints (July), Find in page and more ad and tracker blocking (December).<br />
<br />
Firefox for FireTV matures: Firefox for FireTV will gain custom tiles (Q1), parental controls, Pocket video feed, request desktop site (Q2), and a custom keyboard with Awesomebar powers. (Q3)<br />
<br />
Lockbox Mobile apps: People will be able to access their saved passwords in an iOS app with an Android app to follow. (2018)<br />
<br />
<br />
=== Opinionated === <br />
<br />
The web has grown and changed dramatically over the last two decades and not all for the better. Trackers, intrusive ads and other dark patterns threaten to drive people away from the open web and that's not good for people browsing or publishing. Over the next year or so, Firefox will take a stand against tracking, intrusive ads, and other dark patterns on the web by blocking the worst content and more clearly communicating the privacy and other protections the browser offers. <br />
<br />
<br />
Filter certain types of ads by default: Firefox will offer users a simple ad filtering option. We're in the early stages still, researching types of advertisements that should be blocked by default. (Q3)<br />
<br />
Block ad re-targeting: We are working on blocking cross-domain tracking. Details to follow. (Q3)<br />
<br />
New Privacy Controls: We will bring all of our key privacy controls into a single location in the product making them more discoverable and putting users in control of their data privacy experience. (Q3)<br />
<br />
Tracking Protection Improvements: We would like to make tracking protection more fine-grained allowing users to turn on or off specific types of tracker. We will also opportunistically block trackers when page load performance is adversely impacted. (Q3)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1368744 Global permissions management]: Permission prompts, especially for notifications, have gotten out of control and users must deny them individually at every site that offers them. Firefox will provide users with a way to disable permission prompts globally for Location, Camera, Microphone, and Notifications. (Firefox 59) <br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1382574 Block video auto-play]: Firefox will provide users with a way to block video auto-play that doesn't break websites. (62)<br />
<br />
[https://github.com/mozilla/blurts-server Breach Alerts]: Breach alerts will inform a user if a site they've visited has been breached and will ask if the user wants to have their account checked to determine if it was compromised. If it was compromised, some helpful information will be presented to the user. (October)<br />
<br />
<br />
=== Web Platform and Tooling advancements ===<br />
<br />
The roadmap described above focuses primarily on the Firefox consumer products. Web developers will not be left out and will see significant improvements to the Firefox web platform and our developer and designer tooling. <br />
<br />
<br />
Web Components: Implementations of the new consensus-based [https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM Shadow DOM] and [https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements Custom Elements] are expected to ship in Firefox 63<br />
<br />
[https://jakearchibald.com/2017/es-modules-in-browsers/ ES6 Modules]: Allows you to use native ECMAScript modules, for example defining modules with <script type="module">, defining fallback scripts with <script nomodule>, and importing code features that have been exported from modules. (60)<br />
<br />
[https://wiki.mozilla.org/TPE-Layout/Dashboard#CSS_Shapes CSS Shapes]: CSS Shapes can be applied to floats. A circle shape on a float will cause inline content to wrap around the circle shape instead of the float's bounding box. (61)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1302685 Variable Fonts] (OpenType Font Variations): the technology enables a single font file to behave like multiple fonts. (61) <br />
<br />
[https://groups.google.com/forum/#!msg/mozilla.dev.platform/tsevyqfBHLE/lccldWNNBwAJ Web Authentication]: an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. (60)<br />
<br />
[https://www.w3.org/TR/pointerevents/ W3C Pointer Events]: creates a single DOM event model to handle pointing input devices such as a mouse, pen/stylus or touch. (59)<br />
<br />
<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1433716 3-Panel Inspector]: This feature allows the Rules view to detach into its own dedicated panel. As result, developers have the ability to author and debug CSS at the same time.(61)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1242029 Shapes Path Editor]: The Shape Path Editor is a developer tool that allows modification of CSS Shapes and Clip Paths right in the browser. In Firefox 61 the platform will support the Shape Outside CSS property and we will extend the tool to go with the platform feature.(61)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1280059 New Font Tooling]: In Firefox 61, the layout team introduces support for Variable Fonts. We take this opportunity to rethink Firefox' fonts tooling and provide a new experience to developers working on both variable and non-variable fonts. (61 through 63, shipped in steps)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=1409965 Flexbox Inspector]: The Flexbox Inspector will allow developers to highlight and debug the flexbox layout model. In later releases (66) we will add separate tools to analyze Alignment and Sizing of elements. (64)<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=devtools-app-panel-m1 Service Workers panel]: developers need to have a solid Service Worker debugging experience that matches Chrome's experience so they can make sure their apps work in Firefox. (61)<br />
<br />
Source Maps Excellence: Source Maps are the translation layer for developers to transform and minify their original code with modern tools while keeping it debuggable. Going beyond what any browser currently provides, our tools will map variables and correctly step through original code. (61)<br />
<br />
Framework Support: Attract back modern web app developers into our tools by matching up how devtools represent frameworks (components, state, errors, callstacks, etc) to the mental models of developers (Q3)<br />
<br />
Context-based Devtools Feature Recommendation: Recommend features and extensions based on developers' technologies to level users up into advanced features and developer extensions for a stickier experience. (Q3)<br />
<br />
Onboarding for Chrome devtools users: Show users switching from Chrome around; what's cool, what's different from Chrome and what's new. (Q3)<br />
<br />
Performance Profiling for GeckoView: Enable the performance tooling that made Quantum Flow a success for the GeckoView project (61)<br />
<br />
Remote Debugging: Support mobile push needs a solid mobile debugging experience, by replacing WebIDE with a modern and well integrated flow that doesn't get in the way. (62/63)<br />
<br />
<br />
<hr><br />
<br />
=== Firefox Product Roadmap Timeline (click image to view the spreadsheet) ===<br />
<br />
<br />
[[File:Firefox-timeline-2018-03-21.png|800px|Firefox Timeline|link=https://docs.google.com/spreadsheets/d/1U1IxTOlsaBcRsnJv0XAaVqQLU4otB6h2lG0NDcvWG-E/edit?usp=sharing]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1182510GitHub/Gecko Repositories2017-10-18T23:25:48Z<p>MykMelez: add link to Git replace command docs</p>
<hr />
<div>= Gecko Repositories on GitHub =<br />
<br />
There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko.<br />
<br />
== mozilla/gecko-dev ==<br />
<br />
mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
== gecko-projects ==<br />
<br />
mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is maintained and synchronized similarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
As with gecko-dev, no commits are made in Git on gecko-projects.<br />
<br />
== mozilla/gecko ==<br />
<br />
mozilla/gecko is a mirror of a single Mercurial repository, mozilla-central as well as CVS history (in the "cvs" branch). It doesn't include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo.<br />
<br />
=== Integrating mozilla-central and CVS History ===<br />
<br />
mozilla/gecko integrates the mozilla-central and CVS histories via [https://git-scm.com/docs/git-replace Git replace]. To traverse the combined history of those repos, clone/fetch mozilla/gecko, then fetch replacement refs via this command:<br />
<br />
<code>git fetch origin 'refs/replace/*:refs/replace/*'</code><br />
<br />
(Replace "origin" with the name of your mozilla/gecko remote, if it differs.)<br />
<br />
Then common Git commands (diff, log, bisect, etc.) will behave as if the oldest commit on the "central" branch (e18f9a3) is the newest commit on the "cvs" branch (3ec464b), and you can traverse history accordingly.<br />
<br />
=== Using mozilla/gecko With try/inbound ===<br />
<br />
Note that cloning mozilla/gecko doesn't fetch git-cinnabar metadata, so you can't use it to push to Mercurial repositories like try and inbound unless you also fetch mozilla-central using git-cinnabar. Thus, for developers that need to push to such repos, it's better to clone mozilla-central via git-cinnabar directly (unless you need CVS history).<br />
<br />
(This may change with git-cinnabar 0.5.0, which is in beta as of this writing.)</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1182507GitHub/Gecko Repositories2017-10-18T23:14:45Z<p>MykMelez: describe new central/CVS history integration in mozilla/gecko</p>
<hr />
<div>= Gecko Repositories on GitHub =<br />
<br />
There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko.<br />
<br />
== mozilla/gecko-dev ==<br />
<br />
mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
== gecko-projects ==<br />
<br />
mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is maintained and synchronized similarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
As with gecko-dev, no commits are made in Git on gecko-projects.<br />
<br />
== mozilla/gecko ==<br />
<br />
mozilla/gecko is a mirror of a single Mercurial repository, mozilla-central as well as CVS history (in the "cvs" branch). It doesn't include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo.<br />
<br />
=== Integrating mozilla-central and CVS History ===<br />
<br />
mozilla/gecko integrates the mozilla-central and CVS histories via Git replace. To traverse the combined history of those repos, clone/fetch mozilla/gecko, then fetch replacement refs via this command:<br />
<br />
<code>git fetch origin 'refs/replace/*:refs/replace/*'</code><br />
<br />
(Replace "origin" with the name of your mozilla/gecko remote, if it differs.)<br />
<br />
Then common Git commands (diff, log, bisect, etc.) will behave as if the oldest commit on the "central" branch (e18f9a3) is the newest commit on the "cvs" branch (3ec464b), and you can traverse history accordingly.<br />
<br />
=== Using mozilla/gecko With try/inbound ===<br />
<br />
Note that cloning mozilla/gecko doesn't fetch git-cinnabar metadata, so you can't use it to push to Mercurial repositories like try and inbound unless you also fetch mozilla-central using git-cinnabar. Thus, for developers that need to push to such repos, it's better to clone mozilla-central via git-cinnabar directly (unless you need CVS history).<br />
<br />
(This may change with git-cinnabar 0.5.0, which is in beta as of this writing.)</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1182503GitHub/Gecko Repositories2017-10-18T22:55:18Z<p>MykMelez: update structure of page</p>
<hr />
<div>= Gecko Repositories on GitHub =<br />
<br />
There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko.<br />
<br />
== mozilla/gecko-dev ==<br />
<br />
mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
== gecko-projects ==<br />
<br />
mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is maintained and synchronized similarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
As with gecko-dev, no commits are made in Git on gecko-projects.<br />
<br />
== mozilla/gecko ==<br />
<br />
mozilla/gecko is a mirror of a single Mercurial repository: mozilla-central. It doesn't include CVS history, nor does it include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo. He hasn't publicized it or otherwise explored the extent to which it's helpful, and it might in fact be better for such developers to clone mozilla-central via git-cinnabar directly.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2017-07-10&diff=1175384WeeklyUpdates/2017-07-102017-07-10T18:01:58Z<p>MykMelez: add Benjamin Dahse intro</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (19:00 UTC) <br />
* https://air.mozilla.org/channels/project-meeting/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
<br />
* [https://mozillians.org/u/bobchao/ Bob Chao], [https://mozillians.org/u/n.srushtika/ Srushtika Neelakantam], [https://mozillians.org/u/mte90/ Daniele Scasciafratte] and [https://mozillians.org/u/dvigneshwer/ Vigneshwer Dhinakaran] for their great work and support during the last quarter to the Rust, WebVR and WebExtensions local communities as part of the [https://blog.mozilla.org/mozillareps/2017/07/10/reps-mobilizer-experiment/ Reps Mobilizers Experiment]. An inpiration to everyone!<br />
* Thanks to all the Tech Speakers who've been out and about this summer, esp those who were out giving talks over the week of the All-Hands<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
* [[Add-ons/Contribute/Triage#Next_Meeting|Add-ons Good First Bugs Triage]]<br />
** 17:00 UTC, ACE Vidyo Room<br />
<br />
* [[Add-ons/Contribute/Triage#Next_Meeting|WebExtension APIs Triage]]<br />
** 17:30 UTC, ACE Vidyo Room<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
* '''[https://indiewebcamp.com/events/2017-07-12-homebrew-website-club Homebrew Website Club Meetup]''' (nearly every Wednesday somewhere)<br/><strong>Be a part of the open web with your own website.</strong><br />
** '''Berlin (GERMANY)''', <br/>'''Nürnberg (GERMANY)''', <br/>'''Virtual EU (UTC+2)''', <br/>'''Birmingham (ENGLAND)''', <br/>'''Brighton (ENGLAND)''', <br/>'''London (ENGLAND)''', <br/>'''Baltimore (<abbr title="Maryland">MD</abbr>)''', <br/>'''Virtual US (UTC-4)''', <br/>'''Bellingham (<abbr title="Washington">WA</abbr>)''', <br/>'''Portland (<abbr title="Oregon">OR</abbr>)''', <br/>'''San Francisco''' (@[[MozSF]] commons hosted by Tantek)<br />
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!<br />
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote><p>Create or update your personal web site!<br/>Share what you've gotten working.</p><p>Join a community with like-minded interests. <br/>Bring friends that want a personal site!</p></blockquote> Any questions? See '''[https://indiewebcamp.com/events/2017-07-12-homebrew-website-club the wiki page for details]''' <br/>or join IRC: https://indieweb.org/discuss<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
* Thursday, 20 July 2017: '''Working Across Personality Types: The Introvert-Extrovert Survival Guide'''<br />
* Location + Time: Mozilla San Francisco + [https://air.mozilla.org/july-speaker-series-are-you-an-introvert-working-across-personality-types-2017-07-20/ Air Mozilla] @ 10am PT / 1pm ET / 5pm UT<br />
* Topic: <br />
<BLOCKQUOTE><p>Over the past year several hundred staff at Mozilla have used the [https://www.insights.com/ Insights Discovery] tool to better learn about their individual personality temperaments, and to be more effective on their teams.</p><br />
<br />
<p>How can these types of tests help us? What’s the real science behind them? Can they be abused? Or are there ways they can help us work together better? Join us for a very interactive session where with some exercises to help us explore how our (and our team’s) MBTI preferences can help us work together better, regardless of job description, culture, or demographics.</p></BLOCKQUOTE><br />
<br />
* Hosts: [https://www.linkedin.com/in/mfrassica Matt Frassica], [https://www.linkedin.com/in/tylerhaugen Tyler Haugen] & [https://mozillians.org/en-US/u/lshapiro/ Larissa Shapiro]<br />
* Speaker: [https://www.linkedin.com/in/jenniferselbylong Jennifer Selby-Long]<br />
* [https://wiki.mozilla.org/Speaker_Series#Thursday.2C_20_July_2017:_Working_Across_Personality_Types:_The_Introvert-Extrovert_Survival_Guide_with_Jennifer_Selby-Long Details]<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Yuliya Gorlovetsky<br />
| Assoc. Creative Director<br />
| Zilla Slab font available<br />
| SF<br />
| Yes<br />
| Yuliya to screenshare<br />
| [https://blog.mozilla.org/opendesign/zilla-slab-common-language-shared-font/ Blog post] <br />
[https://github.com/mozilla/zilla-slab/releases/tag/v1.0/ Github] <br />
[https://fonts.google.com/specimen/Zilla+Slab/ Google Fonts]<br />
|-<br />
| Sam Burton<br />
| Director, Insights / Mozilla Foundation<br />
| New research done in collaboration with Caribou Digital: “Paying Attention to the Poor: Digital Advertising in Emerging Markets.” <br />
| Toronto<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| [https://blog.mozilla.org/blog/2017/07/06/new-research-ad-supported-internet-feasible-emerging-markets/ Blog post] / [http://cariboudigital.net/new/wp-content/uploads/2017/07/Paying-Attention-to-the-Poor.pdf Full research report]<br />
|-<br />
| Michael Van Kleeck<br />
| Enterprise Solutions Architect<br />
| The MinIT! <br />
| MozPDX<br />
| No<br />
| n/a<br />
| 1. Identity and Access Management Update- Mozillians.org migrated to ParSys AWS infrastructure<br/>2. Nightly downloads encouraged on SSO Landing Page <br/> 3. SF All Hands- Community/staff collaboration tools- use cases defined, work beginning!<br/><br />
|-<br />
| Liz Hull<br />
| Social Team<br />
| Firefox + HitRecord: TMI video collaboration<br />
| PDX<br />
| no<br />
| Let's watch this video! [https://www.facebook.com/Firefox/videos/10158978500490022/]<br />
| [https://www.hitrecord.org/challenges/3258247/ Project page to get involved] /<br />
|-<br />
| Mike Hoye<br />
| It's Complicated<br />
| UCOSP - The Undergraduate Capstone Open Source Project.<br />
| MoTo<br />
| no<br />
| none<br />
| SOON<br />
|-<br />
| Asa Dotzler<br />
| Firefox Roadmap <br />
| Weekly Firefox Update<br />
| MTV<br />
| no<br />
| na<br />
| https://wiki.mozilla.org/Firefox/Roadmap/Updates#2017-07-10<br />
|-<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! ''Who is being introduced?''<br />
! ''Who are you? (the introducer)''<br />
! ''Where are you doing the introduction?''<br />
! ''Where are they from?''<br />
! ''How will they be part of Mozilla?''<br />
|-<br />
<!-- Insert new rows here --><br />
| Hassan Ali<br />
| Greg Arndt<br />
| Remote<br />
| Toronto<br />
| Taskcluster, Engineering Operations<br />
|-<br />
| Benjamin Dahse<br />
| Brendan Dahl<br />
| SF<br />
| Aarhus University, Denmark<br />
| Browser Architecture<br />
|}<br />
<br />
= Fireside Chat =<br />
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.<br />
<br />
===This Week===<br />
<br />
'''Name''', "Title"<br />
<br />
===Topics===<br />
<br />
You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=All_Hands/SanFrancisco2018&diff=1172815All Hands/SanFrancisco20182017-06-06T17:32:34Z<p>MykMelez: correct dates</p>
<hr />
<div>'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style! <br />
<br />
'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''<br />
<br />
=='''Dates, Location and Weather'''==<br />
Monday, June 11 - Friday, June 15, 2018 (travel days are Monday the 11th & Saturday the 16th) in San Francisco, CA.<br />
<br />
We are staying at [http://www.marriott.com/hotels/travel/sfodt-san-francisco-marriott-marquis/ San Francisco Marriott Marquis].<br />
<br />
''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to be pre-approved and pre-arranged.''<br />
<br />
=='''Registration'''==<br />
This is an invite-only event.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=All_Hands/Cancun&diff=1172814All Hands/Cancun2017-06-06T17:31:38Z<p>MykMelez: correct dates</p>
<hr />
<div>'''What is it?''' -- Multiple team meetings, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style! <br />
<br />
'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''<br />
<br />
=='''Dates, Location and Weather'''==<br />
Monday, December 11 - Friday, December 15, 2017 (travel days are Monday the 11th & Saturday the 16th*) in Cancun, Mexico.<br />
<br />
We are staying at [http://www.moonpalacecancun.com/en Moon Palace Resort]. <br />
<br />
''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose. This needs to pre-approved and pre-arranged.''<br />
<br />
=='''Registration'''==<br />
This is an invite-only event. <br />
<br />
=='''Health & Safety'''==<br />
We recognize that some of you may have concerns about certain health issues such as the Zika virus.<br />
<br />
We encourage you to talk to you manager and HRBP if you have concerns about traveling to Mexico.<br />
<br />
You may visit the Centers for Disease Control and Prevention (CDC) [https://wwwnc.cdc.gov/travel/notices/alert/zika-virus-mexico website for more information]. Information from the Mexico Tourism Board (who stays very up to date on any topics related to travel to Mexico), can be found [http://www.journeymexico.com/wp-content/uploads/2016/09/Mexico-Tourism-Board-%E2%80%93-Facts-About-Zika-%E2%80%93-October-10-2016.pdf here].<br />
<br />
====From the resort====<br />
There have been no reported incidences of the Zika virus at any Palace Resorts property nor in the vicinity of the destinations our properties are located. However, the company recommends guests consider suggestions from the Centers for Disease Control and Prevention (CDC) including covering exposed skin, using EPA-registered insect repellents and sleeping in air conditioned rooms.<br />
<br />
As scientific investigations are ongoing to determine more details surrounding the Zika virus, Palace Resorts will continue normal operations while vigilantly monitoring for relevant and conclusive information to be released. Furthermore, Palace Resorts will maintain our strict fumigation and pest control procedures which are managed by an external professional company. The Government keeps their own prevention activities and they do it stronger on the rainy seasons. <br />
<br />
[https://drive.google.com/open?id=0BxpoaXUTHH24TF9zOWl0c2xLMm0weWJ4YmJqdm5MSEsxNHpj Media Q&A]<br />
<br />
[https://drive.google.com/open?id=0BxpoaXUTHH24c2pORWN6RDE2V0tJVTd1TmU0eUpUWE1DWXpF Zika in Mexico]<br />
<br />
=='''Travel Insurance'''==<br />
Mozilla provides emergency medical accident and illness cover for all global employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com. <br />
<br />
Mozilla does not cover travel insurance for volunteers.<br />
<br />
=='''Immigration'''==<br />
'''Any''' questions on immigration should be sent to immigration@mozilla.com.<br />
<br />
Transit Visa<br />
https://travel.state.gov/content/visas/en/other/transit.html<br />
<br />
=====Pocket Letter=====<br />
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register online. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub/Gecko_Repositories&diff=1171909GitHub/Gecko Repositories2017-05-24T15:59:45Z<p>MykMelez: initial version describing various Gecko repositories on GitHub</p>
<hr />
<div>There are several repositories in the [https://github.com/mozilla/ "mozilla" organization on GitHub] that contain the Gecko source code, in particular [https://github.com/mozilla/gecko-dev mozilla/gecko-dev], [https://github.com/mozilla/gecko-projects mozilla/gecko-projects], and [https://github.com/mozilla/gecko mozilla/gecko].<br />
<br />
gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day.<br />
<br />
gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is similarly maintained and synchronized. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)<br />
<br />
No commits are made in Git on gecko-dev or gecko-projects. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.<br />
<br />
mozilla/gecko, on the other hand, is a mirror of a single Mercurial repository: mozilla-central. It doesn't include CVS history, nor does it include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.<br />
<br />
More generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the former, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. Whereas it isn't obvious how to report an issue with the latter.<br />
<br />
(Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo. He hasn't publicized it or otherwise explored the extent to which it's helpful, and it might in fact be better for such developers to clone mozilla-central via git-cinnabar directly.)</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Modules/Core&diff=1162141Modules/Core2017-02-07T17:36:31Z<p>MykMelez: update obsolete reference to dev-embedding forum</p>
<hr />
<div><noinclude><br />
'''Only module owners may edit this page.''' <br />
<br />
They may:<br />
<br />
* update any information about their module except the name of the owner<br />
* add or remove sub-modules<br />
* change the owner of a sub-module <br />
* add emeritus owners or peers<br />
<br />
Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br />
</noinclude><br />
{{Module<br />
|name=Accessibility<br />
|description=Support for platform accessibility APIs. Accessibility APIs are used by 3rd party software like screen readers, screen magnifiers, and voice dictation software, which need information about document content and UI controls, as well as important events like changes of focus.<br />
|owner=[mailto:surkov.alexander@gmail.com Alexander Surkov]<br />
|peers=[mailto:bolterbugz@gmail.com David Bolter], [mailto:trev.saunders@gmail.com Trevor Saunders], [mailto:marco.zehe@googlemail.com Marco Zehe]<br />
|ownersemeritus=[mailto:aaron@moonset.net. Aaron Leventhal]<br />
|peersemeritus=[mailto:ginn.chen@oracle.com Ginn Chen], Evan Yan<br />
|group=dev-accessibility<br />
|source_dirs=accessible/<br />
|url=http://www.mozilla.org/access/<br />
|components=Core::Disability Access APIs<br />
}}<br />
<br />
{{Module<br />
|name=Browser WebAPI<br />
|description=Web API for rendering apps, browser windows and widgets.<br />
|owner=[mailto:kchen@mozilla.com Kan-Ru Chen]<br />
|peers=[mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:fabrice@mozilla.com Fabrice Desré]<br />
|group=dev-webapi<br />
|source_dirs=dom/browser-element/<br />
|url=<br />
|components=Core::DOM<br />
}}<br />
<br />
{{Module<br />
|name=Build and Release Tools<br />
|description=Tools related to build and release automation and configuration of release builds.<br />
|owner=[mailto:nthomas@mozilla.com Nick Thomas]<br />
|peers=[mailto:bhearsum@mozilla.com Ben Hearsum], [mailto:coop@mozilla.com Chris Cooper]<br />
|group=release-engineering<br />
|source_dirs=browser/config/mozconfigs/, mobile/android/config/mozconfigs/, xulrunner/config/mozconfigs/, b2g/config/, tools/update-packaging/<br />
|url=https://wiki.mozilla.org/ReleaseEngineering<br />
|components=Release Engineering::*<br />
}}<br />
<br />
{{Module<br />
|name=Build Config<br />
|description=The build system for Gecko and several mozilla.org hosted Gecko-based applications.<br />
|owner=[mailto:gps@mozilla.com Gregory Szorc] (:gps)<br />
|peers=[mailto:mh@glandium.org Mike Hommey] (:glandium), [mailto:mshal@mozilla.com Mike Shal] (:mshal), [mailto:ted@mielczarek.org Ted Mielczarek] (:ted), [mailto:cmanchester@mozilla.com Chris Manchester](:chmanchester), [mailto:nfroyd@mozilla.com Nathan Froyd] (:froydnj), [mailto:rgiles@mozilla.com Ralph Giles] (:rillian)<br />
|ownersemeritus=Ted Mielczarek (2008-[https://blog.mozilla.org/ted/2013/03/07/gregory-szorc-is-now-the-build-config-module-owner/ 2013]), Benjamin Smedberg (???-[http://benjamin.smedbergs.us/blog/2008-04-30/more-changing-of-the-guard-ted-mielczarek/ 2008]), <br />
|group=dev-builds<br />
|source_dirs=build/, config/, python/mozbuild, tools/cross-commit, tools/cvs2hg-import.py, tools/cvsmgmt/, tools/elf-dynstr-gc/, tools/trees.pl, browser/config/mozconfigs/, mobile/config/mozconfigs/, xulrunner/config/mozconfigs/<br />
|url=http://www.mozilla.org/build/<br />
|components=Core::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=Code Analysis and Debugging Tools<br />
|description=Tools for debugging Mozilla code or for analyzing speed, memory use, and other characteristics of it.<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=<br />
|group=dev-performance<br />
|source_dirs=tools/codesighs/, tools/debug/, tools/dreftool/, tools/dumpdeps/, tools/footprint/, tools/jprof/, tools/leaky/, tools/memory/, tools/module-deps/, tools/performance/, tools/post_compile/, tools/preloader/, tools/rb/, tools/reorder/, tools/trace-malloc/, tools/uuiddeps/, <br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Content HTTP Headers<br />
|description=HTTP headers related to content, e.g. User-Agent, Content-Type, Accept. (Transport-related headers are the responsibility of the Necko module owner.)<br />
|owner=[mailto:gerv@mozilla.org Gervase Markham]<br />
|peers=[mailto:lmandel@mozilla.com Lawrence Mandel]<br />
|group=dev-platform<br />
|source_dirs= <br />
|url=https://developer.mozilla.org/en/Gecko_user_agent_string_reference<br />
|components=Core::Networking: HTTP<br />
}}<br />
<br />
{{Module<br />
|name=Content Security<br />
|description=Native content-based security features, including: Content Security Policy (CSP), Mixed Content Blocker (MCB), Subresource Integrity (SRI) and CORS.<br />
|owner=[mailto:ckerschbaumer@mozilla.com Christoph Kerschbaumer]<br />
|peers=[mailto:francois@mozilla.com François Marier], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:tvyas@mozilla.com Tanvi Vyas], [mailto:dveditz@mozilla.com Dan Veditz], [mailto:mozilla@sidstamm.com Sid Stamm] <br />
|group=dev-security<br />
|source_dirs=dom/security<br />
|components=Core::DOM: Security<br />
}}<br />
<br />
{{Module<br />
|name=Cookies and Permissions<br />
|description=<br />
|owner=Monica Chew<br />
|peers=[mailto:josh@joshmatthews.com Josh Matthews], [mailto:ehsan@mozilla.com Ehsan Akhgari], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dwitte@gmail.com Dan Witte], [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:sdwilsh@shawnwilsher.com Shawn Wilsher (ping on irc)]<br />
|group=dev-tech-network<br />
|source_dirs=extensions/cookie/, netwerk/cookie/<br />
|url=<br />
|components=Core::Networking: Cookies<br />
}}<br />
{{Module<br />
|name=Cycle Collector<br />
|description=Code to break and collect objects within reference cycles<br />
|owner=[https://mozillians.org/en-US/u/mccr8/ Andrew McCreight]<br />
|peers=Peter Van der Beken, Olli Pettay, David Baron<br />
|source_dirs=xpcom/base/nsCycleCollector.* and some support headers<br />
|components=Core::XPCOM<br />
|group=dev-platform<br />
}}<br />
{{Module<br />
|name=C++/Rust usage, tools, and style<br />
|description=Aspects of C++ use such as language feature usage, standard library versions/usage, compiler/toolchain versions, formatting and naming style, and aspects of Rust use as needs arise<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:bballo@mozilla.com Botond Ballo], [mailto:nfroyd@mozilla.com Nathan Froyd], [mailto:glandium@mozilla.com Mike Hommey], [mailto:jwalden@mozilla.com Jeff Walden]<br />
|source_dirs=non-third-party C++ and Rust code in the tree<br />
|components=Various components<br />
|group=dev-platform<br />
}}<br />
{{Module<br />
|name=docshell<br />
|description=<br />
|owner=[mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|peers=[mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:jst@mozilla.org Johnny Stenback], [mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:justin.lebar@gmail.com Justin Lebar]<br />
|group=dev-tech-layout<br />
|source_dirs=docshell/, uriloader/<br />
|url=<br />
|components=Core::Document Navigation<br />
}}<br />
<br />
{{Module<br />
|name=Device Storage<br />
|description=Support for the device storage API<br />
|owner=[https://mozillians.org/u/dhylands/ Dave Hylands] (:dhylands), [mailto:jvarga@mozilla.com Jan Varga] (:janv)<br />
|peers=<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner] (:dougt)<br />
|group=dev-tech-dom<br />
|source_dirs=dom/devicestorage/, dom/interfaces/devicestorage/<br />
|url=https://developer.mozilla.org/en-US/docs/WebAPI/Device_Storage<br />
|components=Core::DOM: Device Interfaces<br />
}}<br />
<br />
{{Module<br />
|name=Document Object Model<br />
|description=<br />
|owner=[mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:bent.mozilla@gmail.com Ben Turner], [mailto:mounir@lamouri.fr Mounir Lamouri (still active, but slower to respond than previously)], [mailto:me@kylehuey.com Kyle Huey], [mailto:hsivonen@iki.fi Henri Sivonen], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:baku@mozilla.com Andrea Marchesini],<br />
[mailto:ehsan@mozilla.com Ehsan Akhgari], [mailto:bkelly@mozilla.com Ben Kelly], [mailto:billm@mozilla.com Bill McCloskey], [mailto:kyle@nonpolynomial.com Kyle Machulis]<br />
|peersemeritus=[mailto:justin.lebar@gmail.com Justin Lebar]<br />
|group=dev-tech-dom<br />
|source_dirs=dom/*, except directories covered by other modules<br />
|url=http://developer.mozilla.org/en/docs/DOM<br />
|components=Core::DOM, Core::DOM: CSS Object Model, Core::DOM: Core & HTML<br />
}}<br />
<br />
{{Module<br />
|name=Event Handling<br />
|description=DOM Events and Event Handling <br />
|owner=[mailto:olli@pettay.fi Olli Pettay], [mailto:masayuki@d-toybox.com Masayuki Nakano]<br />
|group=dev-platform<br />
|source_dirs=dom/events and event handling related code elsewhere <br />
|url=http://developer.mozilla.org/en/docs/DOM<br />
|components=Core::DOM: Events, Core::Event Handling<br />
}}<br />
<br />
{{Module<br />
|name=Web Workers<br />
|description=<br />
|owner=[mailto:bent.mozilla@gmail.com Ben Turner]<br />
|peers=[mailto:mrbkap@mozilla.com Blake Kaplan], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:me@kylehuey.com Kyle Huey], [mailto:baku@mozilla.com Andrea Marchesini], [mailto:bkelly@mozilla.com Ben Kelly]<br />
|group=dev-platform<br />
|source_dirs=dom/workers/<br />
|url=https://developer.mozilla.org/En/Using_web_workers<br />
|components=Core::DOM: Workers<br />
}}<br />
<br />
{{Module<br />
|name=IndexedDB<br />
|description=<br />
|owner=[mailto:bent.mozilla@gmail.com Ben Turner]<br />
|peers=[mailto:jonas@sicking.cc Jonas Sicking], [mailto:me@kylehuey.com Kyle Huey], [mailto:jvarga@mozilla.com Jan Varga], [mailto:btseng@mozilla.com Bevis Tseng]<br />
|group=dev-platform<br />
|source_dirs=dom/indexedDB/<br />
|url=https://developer.mozilla.org/en/IndexedDB<br />
|components=Core::DOM: IndexedDB<br />
}}<br />
<br />
{{Module<br />
|name=Editor<br />
|description=<br />
|owner=[mailto:masayuki@d-toybox.com Masayuki Nakano]<br />
|peers=[mailto:ayg@aryeh.name Aryeh Gregor]<br />
|ownersemeritus=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|group=dev-platform<br />
|source_dirs=editor/<br />
|url=http://www.mozilla.org/editor/<br />
|components=Core::Editor<br />
}}<br />
<br />
{{Module<br />
|name=Embedding<br />
|description=Gecko embedding APIs and frameworks<br />
|owner=[mailto:myk@mykzilla.org Myk Melez]<br />
|ownersemeritus=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:doug.turner@gmail.com Doug Turner]<br />
|peers=[mailto:bdahl@mozilla.com Brendan Dahl], [mailto:tbsaunde@tbsaunde.org Trevor Saunders]<br />
|peersemeritus=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-platform<br />
|source_dirs=embedding/<br />
|url=<br />
|components=Core::Embedding: APIs<br />
}}<br />
<br />
{{Module<br />
|name=Find As You Type<br />
|description=Find As You Type (formerly called Type Ahead Find) is a feature that allows quick web page navigation when you type a succession of characters in the body of the displayed page (not in an edit box of or drop down list). Currently seeks new owner.<br />
|owner=<br />
|peers=<br />
|group=dev-accessibility<br />
|source_dirs=extensions/typeaheadfind/<br />
|url=http://www.mozilla.org/access/type-ahead/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Geolocation<br />
|description=Implementation of the Geolocation W3C Spec, location provider apis, and wifi scanning code.<br />
|owner=[mailto:josh@joshmatthews.net Josh Matthews], [mailto:kchen@mozilla.com Kan-Ru Chen]<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner], Garvan Keeley<br />
|peers=<br />
|group=dev-tech-dom<br />
|source_dirs=dom/geolocation, dom/system/, netwerk/wifi<br />
|url=https://developer.mozilla.org/En/Using_geolocation<br />
|components=Core::Geolocation<br />
}}<br />
<br />
{{Module<br />
|name=Global Key Bindings<br />
|description=Global hot keys in Mozilla for the browser, editor, mail-news and widgets. Does not include underlined menu accelerators and the like, as those are part of i18n.<br />
|owner=Aaron Leventhal<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|group=dev-accessibility<br />
|source_dirs=dom/xbl/builtin/<br />
|url=http://www.mozilla.org/projects/ui/accessibility/mozkeyintro.html<br />
|components=Core::Keyboard: Navigation<br />
}}<br />
<br />
{{Module<br />
|name=Graphics<br />
|description=Mozilla graphics API<br />
|owner=[mailto:jrmuizel@mozilla.com Jeff Muizelaar](Thebes, QCMS, YCbCr, Cairo/Pixman, Regions, OS X, Other)<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:jdrew@mozilla.com Joe Drew], [mailto:vladimir@pobox.com Vladimir Vukicevic], [mailto:bas.schouten@live.nl Bas Schouten](Layers, Windows), [mailto:bjacob@mozilla.com Benoit Jacob](gfx/gl), [mailto:bgirard@mozilla.com Benoit Girard](Compositor, Performance), [mailto:ajuma.bugzilla@alijuma.com Ali Juma], [mailto:jgilbert@mozilla.com Jeff Gilbert](WebGL, ANGLE), [mailto:george@mozilla.com George Wright](Canvas2D, Skia), [mailto:mwoodrow@mozilla.com Matt Woodrow](Layers API), [mailto:jdaggett@mozilla.com John Daggett](text/fonts), [mailto:jfkthame@googlemail.com Jonathan Kew](text/fonts), [mailto:nsilva@mozilla.com Nicolas Silva](MozSurface), [mailto:ncameron@mozilla.com Nick Cameron], [mailto:sikeda@mozilla.com Sotaro Ikeda](B2G), [mailto:snorp@mozilla.com James Willcox](Android), [mailto:clord@mozilla.com Christopher Lord], [mailto:mstange@themasta.com Markus Stange](OS X), [mailto:lsalzman@mozilla.com Lee Salzman], [mailto:mchang@mozilla.com Mason Chang], [mailto:dvander@mozilla.com David Anderson]<br />
|group=dev-platform<br />
|source_dirs=gfx/, dom/canvas/<br />
|url=https://wiki.mozilla.org/Platform/GFX https://wiki.mozilla.org/Gecko:Layers https://wiki.mozilla.org/Gecko:2DGraphicsSketch<br />
|components=Core::Graphics, Core::Graphics: Layers, Core::Graphics: Text, Core::GFX: Color Management, Core::Canvas: 2D, Core::Canvas: WebGL<br />
}}<br />
<br />
{{Module<br />
|name=APZ (Graphics submodule)<br />
|description=Asynchronous panning and zooming<br />
|owner=[mailto:kgupta@mozilla.com Kartikaya Gupta]<br />
|peers=[mailto:bballo@mozilla.com Botond Ballo], [mailto:tnikkel@mozilla.com Timothy Nikkel], [mailto:dvander@mozilla.com David Anderson], [mailto:mstange@mozilla.com Markus Stange]<br />
|group=dev-platform<br />
|source=gfx/layers/apz<br />
|url=https://wiki.mozilla.org/Platform/GFX/APZ<br />
|components=Core::Panning and Zooming<br />
}}<br />
<br />
{{Module<br />
|name=Moz2D (Graphics submodule)<br />
|description=Platform independent 2D graphics API<br />
|owner=[mailto:bschouten@mozilla.com Bas Schouten]<br />
|peers=[mailto:jmuizelaar@mozilla.com Jeff Muizelaar], [mailto:gwright@mozilla.com George Wright], [mailto:jwatt@mozilla.com Jonathan Watt]<br />
|group=dev-platform<br />
|source=gfx/2d<br />
|url=https://wiki.mozilla.org/Platform/GFX/Moz2D<br />
|components=Core::Graphics<br />
}}<br />
<br />
{{Module<br />
|name=Legacy HTML Parser<br />
|description=<br />
|owner=[mailto:mrbkap@gmail.com Blake Kaplan]<br />
|peers=[mailto:dbaron@dbaron.org David Baron], [mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken], [mailto:rbs@maths.uq.edu.au rbs@maths.uq.edu.au]<br />
|group=dev-tech-dom<br />
|source_dirs=parser/htmlparser<br />
|url=http://www.mozilla.org/newlayout/doc/parser.html<br />
|components=Core::HTML: Parser<br />
}}<br />
<br />
{{Module<br />
|name=HAL<br />
|description=Hardware Abstraction Layer<br />
|owner=[https://mozillians.org/u/dhylands/ Dave Hylands]<br />
|peers=[mailto:gsvelto@mozilla.com Gabriele Svelto]<br />
|group=dev-platform<br />
|source_dirs=hal/<br />
|components=Core::Hardware Abstraction Layer (HAL)<br />
}}<br />
<br />
{{Module<br />
|name=HTML Parser<br />
|description=The HTML Parser transforms HTML source code into a DOM. It conforms to the HTML specification, and is mostly translated automatically from Java to C++.<br />
|owner=[mailto:hsivonen@iki.fi Henri Sivonen]<br />
|peers=<br />
|group=dev-tech-dom<br />
|source_dirs=parser/html<br />
|url=http://about.validator.nu/<br />
|components=Core::HTML: Parser<br />
}}<br />
<br />
{{Module<br />
|name=I18N Library<br />
|description=<br />
|owner=[mailto:jshin1987@gmail.com Jungshik Shin], [mailto:smontagu@smontagu.org Simon Montagu]<br />
|peers=[mailto:VYV03354@nifty.ne.jp Masatoshi Kimura]<br />
|group=dev-i18n<br />
|source_dirs=intl/<br />
|url=http://mozilla.org/projects/intl/index.html<br />
|components=Core::Internationalization<br />
}}<br />
<br />
{{Module<br />
|name=ImageLib<br />
|description=<br />
|owner=[mailto:seth@mozilla.com Seth Fowler]<br />
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:jmuizelaar@mozilla.com Jeff Muizelaar], [mailto:jlebar@mozilla.com Justin Lebar], [mailto:tnikkel@gmail.com Timothy Nikkel]<br />
|group=dev-platform<br />
|source_dirs=media/libjpeg/, media/libpng/, image/, modules/zlib/<br />
|url=<br />
|components=Core::ImageLib<br />
}}<br />
<br />
{{Module<br />
|name=IPC<br />
|description=Message-passing between threads and processes<br />
|owner=[mailto:wmccloskey@mozilla.com Bill McCloskey]<br />
|peers=[mailto:danderson@mozilla.com David Anderson], [mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:bent.mozilla@gmail.com Ben Turner], [mailto:jld@mozilla.com Jed Davis]<br />
|group=dev-platform<br />
|source_dirs=ipc/glue/, ipc/ipdl/, ipc/chromium/<br />
|url=<br />
|components=Core::IPC}}<br />
<br />
{{Module<br />
|name=JavaScript<br />
|description=JavaScript engine (SpiderMonkey)<br />
|owner=[mailto:jorendorff@mozilla.com Jason Orendorff]<br />
|peers=[mailto:jdemooij@mozilla.com Jan de Mooij], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:nnethercote@mozilla.com Nick Nethercote], [mailto:jwalden@mit.edu Jeff Walden], [mailto:hv1989@gmail.com Hannes Verschore], [mailto:kvijayan@mozilla.com Kannan Vijayan], [mailto:shu@mozilla.com Shu-yu Guo], [mailto:evilpies@gmail.com Tom Schuster], [mailto:bhackett1024@gmail.com Brian Hackett], [mailto:till@tillschneidereit.net Till Schneidereit], [mailto:efaust@mozilla.com Eric Faust], [mailto:nfitzgerald@mozilla.com Nick Fitzgerald], [mailto:luke@mozilla.com Luke Wagner], [mailto:arai.unmht@gmail.com Tooru Fujisawa], [mailto:sunfish@mozilla.com Dan Gohman], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:nmatsakis@mozilla.com Niko Matsakis], [mailto:ejpbruel@mozilla.com Eddy Bruel], [mailto:danderson@mozilla.com David Anderson], [mailto:igor@mir2.org Igor Bukanov], [mailto:brendan@mozilla.org Brendan Eich], Andreas Gal<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/src<br />
|url=http://www.mozilla.org/js/spidermonkey,<br />
http://developer.mozilla.org/en/docs/About_JavaScript<br />
|components=Core::JavaScript Engine<br />
}}<br />
<br />
{{Module<br />
|name=JavaScript JIT<br />
|description=JavaScript engine's JIT compilers (IonMonkey, Baseline)<br />
|owner=[mailto:jdemooij@mozilla.com Jan de Mooij]<br />
|peers=[mailto:danderson@mozilla.com David Anderson], [mailto:bbouvier@mozilla.com Benjamin Bouvier], [mailto:shu@mozilla.com Shu-yu Guo], [mailto:bhackett1024@gmail.com Brian Hackett], [mailto:nicolas.b.pierron@mozilla.com Nicolas Pierron], [mailto:evilpies@gmail.com Tom Schuster], [mailto:sstangl@mozilla.com Sean Stangl], [mailto:hv1989@gmail.com Hannes Verschore], [mailto:kvijayan@mozilla.com Kannan Vijayan], [mailto:luke@mozilla.com Luke Wagner]<br />
|group=dev-tech-js-engine-internals<br />
|source_dirs=js/src/jit<br />
|url=http://www.mozilla.org/js/spidermonkey<br />
|components=Core::JavaScript Engine: JIT<br />
}}<br />
<br />
{{Module<br />
|name=JavaScript Debugger Backend<br />
|description=JavaScript debugging hooks<br />
|owner=[mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:rginda@hacksrus.com Rob Ginda]<br />
|group=dev-apps-js-debugger<br />
|source_dirs=js/jsd/<br />
|url=http://www.mozilla.org/js/jsd<br />
|components=Other Applications::Venkman JS Debugger<br />
}}<br />
<br />
{{Module<br />
|name=jsat<br />
|description=Javascript screen reader that is used in Android and B2G<br />
|owner=[mailto:eitan@monotonous.org Eitan Isaacson]<br />
|peers=[mailto:yzenevich@mozilla.com Yura Zenevich]<br />
|group=dev-accessibility<br />
|source_dirs=accessible/jsat/<br />
|url=http://www.mozilla.org/access/<br />
|components=Core::Disability Access APIs<br />
}}<br />
<br />
{{Module<br />
|name=js-ctypes<br />
|description=A foreign function interface which allows privileged JS code to interact with binary code without using XPCOM/XPConnect.<br />
|owner=[mailto:jorendorff@mozilla.com Jason Orendorff]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:bobbyholley@gmail.com Bobby Holley]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/src/ctypes/<br />
|url=https://wiki.mozilla.org/JSctypes<br />
|components=Core::js-ctypes<br />
}}<br />
<br />
{{Module<br />
|name=js-tests<br />
|description=JavaScript test suite<br />
|owner=[mailto:bclary@bclary.com Bob Clary]<br />
|peers=<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/tests/<br />
|url=http://www.mozilla.org/js/tests/library.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Layout Engine<br />
|description=rendering tree construction, layout (reflow), etc.<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dholbert@mozilla.com Daniel Holbert], [mailto:jfkthame@gmail.com Jonathan Kew], [mailto:tnikkel@gmail.com Timothy Nikkel], [mailto:matt.woodrow@gmail.com Matt Woodrow], [mailto:xidorn+moz@upsuper.org Xidorn Quan]<br />
|group=dev-tech-layout<br />
|source_dirs=layout/%, layout/base/, layout/build/, layout/doc/, layout/forms/, layout/generic/, layout/html/, layout/printing/, layout/tables/, layout/tools/<br />
|url=http://mozilla.org/newlayout/doc/ ,<br />
http://lxr.mozilla.org/mozilla/source/layout/doc/<br />
|components=Core::Layout, Core::Layout: Block and Inline, Core::Layout: Floats, Core::Layout: Form Controls, Core::Layout: HTML Frames, Core::Layout: Images, Core::Layout: Misc Code, Core::Layout: R & A Pos, Core::Layout: Tables, Core::Layout: Text, Core::Print Preview, Core::Printing: Output<br />
}}<br />
<br />
{{Module<br />
|name=libjar<br />
|description=The JAR handling code (protocol handler, stream implementation, and zipreader/zipwriter).<br />
|owner=[mailto:mwu@mozilla.com Michael Wu]<br />
|peers=[mailto:aklotz@mozilla.com Aaron Klotz]<br />
|group=dev-platform<br />
|source_dirs=modules/libjar<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=MathML<br />
|description=MathML is a low-level specification for describing mathematics which provides a foundation for the inclusion of mathematical expressions in Web pages.<br />
|owner=[mailto:karlt+@karlt.net Karl Tomlinson]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=dev-tech-mathml<br />
|source_dirs=layout/mathml/<br />
|url=http://www.mozilla.org/projects/mathml/<br />
|components=Core::MathML<br />
}}<br />
<br />
{{Module<br />
|name=Media Playback<br />
|description=HTML Media APIs, including Media Source Extensions and non-MSE video/audio element playback, and Encrypted Media Extensions. (WebRTC and WebAudio not included).<br />
|owner=[mailto:cpearce@mozilla.com Chris Pearce]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:ajones@mozilla.com Anthony Jones], [mailto:kinetik@flim.org Matthew Gregan], [mailto:eflores@mozilla.com Edwin Flores], [mailto:jyavenard@mozilla.com Jean-Yves Avenard], [mailto:gsquelart@mozilla.com Gerald Squelart], [mailto:rgiles@mozilla.com Ralph Giles], [mailto:jwwang@mozilla.com JW Wang]<br />
|group=dev-media<br />
|source_dirs=dom/media, media/gmp-clearkey/, media/libcubeb/, media/libnestegg/, media/libogg/, media/libopus/, media/libstagefright/, media/libtheora/, media/libtremor/, media/libvorbis/, media/libvpx/, media/omx-plugin/, media/rlz/<br />
|url=<br />
|components=Core::Audio/Video<br />
}}<br />
<br />
{{Module<br />
|name=Media Transport<br />
|description=Pluggable transport for real-time media<br />
|owner=[mailto:ekr@rtfm.com Eric Rescorla]<br />
|peers=[mailto:bcampen@mozilla.com Byron Campen], [mailto:abr@mozilla.com Adam Roach], [mailto:nohlmeier@mozilla.com Nils Ohlmeier]<br />
|group=dev-media<br />
|source_dirs=media/mtransport<br />
|url=<br />
|components=Core::WebRTC::Networking<br />
}}<br />
<br />
{{Module<br />
|name=Memory Allocator<br />
|description=Most things related to memory allocation in Gecko, including jemalloc, replace-malloc, DMD (dark matter detector), logalloc, etc.<br />
|owner=[mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|peers=[mailto:n.nethercote@gmail.com Nicholas Nethercote]<br />
|group=dev-platform<br />
|source_dirs=memory/<br />
|components=Core::DMD, Core::jemalloc<br />
}}<br />
<br />
{{Module<br />
|name=mfbt<br />
|description=mfbt is a collection of headers, macros, data structures, methods, and other functionality available for use and reuse throughout all Mozilla code (including SpiderMonkey and Gecko more broadly).<br />
|owner=[mailto:jwalden@mit.edu Jeff Walden]<br />
|peers=[mailto:froydnj@mozilla.com Nathan Froyd], [mailto:Ms2ger@gmail.com Ms2ger], [mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|group=dev-platform<br />
|source_dirs=mfbt/<br />
|url=<br />
|components=Core::MFBT<br />
}}<br />
<br />
{{Module<br />
|name=mozApps API & UI<br />
|description=Implementation of the navigator.mozApps API<br />
|owner=[mailto:fabrice@mozilla.com Fabrice Desré], [mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:myk@mozilla.org Myk Melez], [mailto:mar.castelluccio@studenti.unina.it Marco Castelluccio], [mailto:ferjmoreno@gmail.com Fernando Jiménez]<br />
|group=dev-webapi<br />
|source_dirs=dom/apps/, dom/interfaces/apps, product specific files implementing UI hooks.<br />
|url=<br />
|components=Core::DOM: Apps<br />
}}<br />
<br />
{{Module<br />
|name=Mozglue<br />
|description=Glue library containing various low-level functionality, including a dynamic linker for Android, a DLL block list for Windows, etc.<br />
|owner=[mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|peers=[mailto:froydnj@mozilla.com Nathan Froyd] (mozglue/linker), [mailto:kgupta@mozilla.com Kartikaya Gupta] (mozglue/android), [mailto:nchen@mozilla.com Jim Chen] (mozglue/android)<br />
|group=dev-platform<br />
|source_dirs=mozglue/<br />
|components=Core::mozglue<br />
}}<br />
<br />
{{Module<br />
|name=mozilla-toplevel<br />
|description=The top level directory for the mozilla tree.<br />
|owner=[mailto:brendan@mozilla.org Brendan Eich]<br />
|peers=<br />
|group=<br />
|source_dirs=tools/README<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Necko<br />
|description=The Mozilla Networking Library<br />
|owner=[mailto:mcmanus@ducksong.com Patrick McManus]<br />
|peers= [mailto:jduell.mcbugs@gmail.com Jason Duell], [mailto:honzab.moz@firemni.cz Honza Bambas], [mailto:mnovotny@mozilla.com Michal Novotny], [mailto:hurley@mozilla.com Nick Hurley], [mailto:dd.mozilla@gmail.com Dragana Damjanovic ],[mailto:valentin.gosu@gmail.com Valentin Gosu],[mailto:daniel@haxx.se Daniel Stenberg ]<br />
|peersemeritus= [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:sworkman@mozilla.com Steve Workman], [mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|group=dev-tech-network<br />
|source_dirs=netwerk/%, netwerk/base/, netwerk/build/, netwerk/cache/, netwerk/dns/, netwerk/locales/, netwerk/mime/, netwerk/protocol/, netwerk/resources/, netwerk/socket/, netwerk/streamconv/, netwerk/system/, netwerk/test/, netwerk/testserver/<br />
|url=http://www.mozilla.org/projects/netlib/, https://developer.mozilla.org/en/Necko<br />
|components=Core::Networking, Core::Networking: Cache, Core::Networking: Cookies, Core::Networking: FTP, Core::Networking: File, Core::Networking: HTTP, Core::Networking: JAR, Core::Networking: Websockets<br />
}}<br />
<br />
{{Module<br />
|name=NSPR<br />
|description=Netscape Portable Runtime<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:wtc@google.com Wan-Teh Chang], [mailto:mh@glandium.org Mike Hommey], [mailto:kaie@kuix.de Kai Engert]<br />
|group=dev-tech-nspr<br />
|source_dirs=nsprpub/<br />
|url=http://www.mozilla.org/projects/nspr/<br />
http://www.mozilla.org/projects/nspr/reference/html/<br />
http://www.mozilla.org/projects/nspr/release-notes/<br />
|components=NSPR<br />
}}<br />
<br />
{{Module<br />
|name=PDF<br />
|description=Rendering code to display documents encoded in the ISO 32000-1 `PDF' format.<br />
|owner=Chris Jones, Andreas Gal<br />
|peers=[mailto:aadib@mozilla.com Artur Adib], [mailto:bdahl@mozilla.com Brendan Dahl], [mailto:vnicolas@mozilla.com Vivien Nicolas]<br />
|group=dev-platform<br />
|source_dirs=media/pdf/<br />
|url=https://github.com/mozilla/pdf.js<br />
|components=Core::PDF<br />
}}<br />
<br />
{{Module<br />
|name=Plugins<br />
|description= NPAPI Plugin support.<br />
|owner=[mailto:jmathies@mozilla.com Jim Mathies]<br />
|peers=[mailto:jst@mozilla.org Johnny Stenback], [mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:joshmoz@gmail.com Josh Aas]<br />
|peersemeritus=[mailto:john@pointysoftware.net John Schoenick], [mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=<br />
|source_dirs=dom/plugins/, modules/plugin/<br />
|url=https://wiki.mozilla.org/Plugins<br />
|components=Core::Plug-ins<br />
}}<br />
<br />
{{Module<br />
|name=Preferences<br />
|description=Preference library<br />
|owner=<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-platform<br />
|source_dirs=modules/libpref/<br />
|url=<br />
|components=Core::Preferences: Backend<br />
}}<br />
<br />
{{Module<br />
|name=Private Browsing<br />
|description=Implementation of the Private Browsing mode, and the integration of other modules with Private Browsing APIs.<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:josh@joshmatthews.net Josh Matthews]<br />
|group=dev-platform<br />
|source_dirs=Implementation and consumers of Private Browsing APIs in nsILoadContext, nsIPrivateBrowsingChannel, PrivateBrowsingUtils.jsm and the related glue code. <br />
|url=https://wiki.mozilla.org/Private_Browsing<br />
|components=Firefox::Private Browsing<br />
}}<br />
<br />
{{Module<br />
|name=Privilege Manager<br />
|description="caps"<br />
|owner=[mailto:bobbyholley@gmail.com Bobby Holley]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dveditz@mozilla.com Dan Veditz], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-tech-dom<br />
|source_dirs=caps/<br />
|url=http://www.mozilla.org/projects/security/components/index.html<br />
|components=Core::Security: CAPS<br />
}}<br />
<br />
{{Module<br />
|name=Push Notifications<br />
|description=Push is a way for application developers to send messages to their web applications.<br />
|owners=<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner]<br />
|peers=[mailto:nsm.nikhil@gmail.com Nikhil Marathe], [mailto:kcambridge@mozilla.com Kit Cambridge], [mailto:martin.thomson@gmail.com Martin Thomson], [mailto:ddamjanovic@mozilla.com Dragana Damjanovic]<br />
|group=<br />
|source_dirs=dom/push, dom/simplepush<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=PyXPCOM<br />
|description=The Python to XPCOM bridge.<br />
|owner=Todd Whiteman<br />
|peers=[mailto:mhammond@skippinet.com.au Mark Hammond]<br />
|group=<br />
|source_dirs=extension/python<br />
|url=https://developer.mozilla.org/en/PyXPCOM<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=RDF<br />
|description=<br />
|owner=[mailto:axel@pike.org Axel Hecht]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-tech-rdf<br />
|source_dirs=rdf/<br />
|url=http://www.mozilla.org/rdf/doc/<br />
|components=Core::RDF<br />
}}<br />
<br />
{{Module<br />
|name=security<br />
|description=Crypto/PKI code, including NSS (Network Security Services) and JSS (NSS for Java)<br />
|owner=[mailto:rrelyea@redhat.com Bob Relyea], [mailto:ttaubert@mozilla.com Tim Taubert]<br />
|peers=[mailto:emaldona@redhat.com Elio Maldonado], [mailto:kaie@kuix.de Kai Engert], [mailto:ryan.sleevi@gmail.com Ryan Sleevi], [mailto:ekr@rtfm.com Eric Rescorla], [mailto:franziskuskiefer@gmail.com Franziskus Kiefer], [mailto:martin.thomson@gmail.com Martin Thomson], [mailto:wtc@google.com Wan-Teh Chang]<br />
|group=dev-tech-crypto<br />
|source_dirs=dbm/, security/coreconf/, security/dbm/, security/jss/, security/nss/, security/tinderbox/, security/tinderlight/<br />
|url=http://mozilla.org/projects/security/pki/<br />
|components=NSS, JSS, Core::Security, Core::Security: S/MIME<br />
}}<br />
<br />
{{Module<br />
|name=Security - Mozilla PSM Glue<br />
|description=Personal Security Manager<br />
|owner=[mailto:dkeeler@mozilla.com David Keeler]<br />
|peers=[mailto:honzab.moz@firemni.cz Honza Bambas], [mailto:cykesiopka.bmo@gmail.com Cykesiopka]<br />
|group=dev-tech-crypto<br />
|source_dirs=security/manager/<br />
|url=<br />
|components=Core::Security: PSM, Core::Security: UI<br />
}}<br />
<br />
{{Module<br />
|name=Static analysis & rewriting for C++<br />
|description=Tools for checking C++ code looking for problems at compile time, plus tools for automated rewriting of C++ code.<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:sfink@mozilla.com Steve Fink], [mailto:michael@thelayzells.com Michael Layzell], [mailto:jrmuizel@mozilla.com Jeff Muizelaar], [mailto:birunthan@mohanathas.com Birunthan Mohanathas]<br />
|group=dev-platform<br />
|source_dirs=build/clang-plugin, tools/rewriting among other out of tree tools<br />
|url=<br />
|components=Core::Rewriting & Analysis<br />
}}<br />
{{Module<br />
|name=storage<br />
|description=Storage APIs with a SQLite backend<br />
|owner=[mailto:mak77@bonardo.net Marco Bonardo]<br />
|peers=[mailto:bugmail@asutherland.org Andrew Sutherland], [mailto:jvarga@mozilla.com Jan Varga]<br />
|group=dev-platform<br />
|source_dirs=db/sqlite3/, storage/<br />
|url=http://developer.mozilla.org/en/docs/Storage<br />
|components=Toolkit::Storage, Core::SQL<br />
}}<br />
<br />
{{Module<br />
|name=String<br />
|description=<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:jlebar@mozilla.com Justin Lebar]<br />
|group=dev-tech-xpcom<br />
|source_dirs=string/, xpcom/string/<br />
|url=https://developer.mozilla.org/En/Mozilla_internal_string_guide<br />
|components=Core::String<br />
}}<br />
<br />
{{Module<br />
|name=Style System<br />
|description=CSS style sheet handling; style data computation<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:cam@mcc.id.au Cameron McCormack]<br />
|group=dev-tech-layout<br />
|source_dirs=layout/style/<br />
|url=https://wiki.mozilla.org/Gecko:Overview#Style_System<br />
|components=Core::CSS Parsing and Computation<br />
}}<br />
<br />
{{Module<br />
|name=SVG<br />
|description=Scalable Vector Graphics<br />
|owner=[mailto:jwatt@jwatt.org Jonathan Watt]<br />
|peers=[mailto:longsonr@gmail.com Robert Longson], [mailto:robert@ocallahan.org Robert O'Callahan], [mailto:dholbert@mozilla.com Daniel Holbert], [mailto:birtles@gmail.com Brian Birtles]<br />
|group=dev-tech-svg<br />
|source_dirs=dom/svg/, layout/svg/, dom/smil/<br />
|url=https://developer.mozilla.org/en-US/docs/Web/SVG<br />
|components=Core::SVG<br />
}}<br />
<br />
{{Module<br />
|name=Tamarin<br />
|description=VM for ActionScript and JavaScript<br />
|owner=Edwin Smith, [mailto:jodyer@adobe.com Jeff Dyer]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:stejohns@adobe.com Steven Johnson], [mailto:tierney@adobe.com Erik Tierney], [mailto:treilly@adobe.com Tom Reilly]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/tamarin<br />
|url=http://www.mozilla.org/projects/tamarin/<br />
http://wiki.mozilla.org/tamarin/<br />
http://hg.mozilla.org/tamarin-central/<br />
http://hg.mozilla.org/tamarin-tracing/<br />
|components=Tamarin<br />
}}<br />
<br />
{{Module<br />
|name=Test Harness<br />
|description=In-tree test infrastructure and tools. Harnesses include, XPCShell, Mochitest (& Chrome), Reftest, JsREftest, Compiled Code Tests, Robocop, Mozmill, Marionette, Firefox UI Tests. Requests for new harnesses should go to Testing::General.<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:dbaron@dbaron.org David Baron] (reftest), [mailto:jwalden@mit.edu Jeff Walden] (httpd.js, jsreftest), Rob Campbell (mochitest, mochitest chrome, marionette), [mailto:jmaher@mozilla.com Joel Maher] (reftest, mochitest, jsreftest), [mailto:ctalbert@mozilla.com Clint Talbert] (reftest, compiled code, mozmill), [mailto:geoffbrown@mozilla.com Geoff Brown] (robocop), [mailto:hskupin@mozilla.com Henrik Skupin] (Marionette, Firefox UI tests), [mailto:ato@mozilla.com Andreas Tolfsen] (marionette), [mailto:jgriffin Jonathan Griffin] (marionette), [mailto:dburns@mozilla.com David Burns] (marionette) [mailto:dminor@mozilla.com Dan Minor], [mailto:mjzffr@gmail.com Maja Frydrychowicz] (Marionette, Firefox UI tests), <br />
<br />
|group=dev-quality<br />
|source_dirs=/testing<br />
|url=http://wiki.mozilla.org/SoftwareTesting<br />
|components=Testing::General, Testing::Mochitest, Testing::Mochitest Chrome, Testing::Marionette, Testing::Mozmill, Testing::Reftest, Testing::XPCShell Harness, Testing::httpd.js<br />
}}<br />
<br />
{{Module<br />
|name=Testing Infrastructure<br />
|description=Testing tools and infrastructure for Mozilla projects, harnesses for automated tests, stand-alone test tools. Talos, Graph Server, Mozbase, Pulse, WOO, Bughunter, SUTAgent, Eideticker<br />
|owner=[mailto:jmaher@mozilla.com Joel Maher]<br />
|peers=[mailto:bclary@bclary.com Bob Clary], [mailto:bhearsum@mozilla.com Ben Hearsum], [mailto:ccooper@deadsquid.com Chris Cooper], [mailto:ctalbert@mozilla.com Clint Talbert], [mailto:robert@roberthelmer.com Robert Helmer], [mailto:jmaher@mozilla.com Joel Maher], Rob Campbell, [mailto:wlach@mozilla.com William Lachance], [mailto:jeads@mozilla.com Jonathan Eads], [mailto:jgriffin Jonathan Griffin], [mailto:bmoss@mozilla.com Bob Moss], [mailto:mcote@mozilla.com Mark Côté]<br />
|group=dev-quality<br />
|source_dirs=testing/, tools/httptester/, tools/page-loader/, tools/test-harness/, tools/tests/, tools/testserver/, tools/testy/<br />
|url=http://wiki.mozilla.org/SoftwareTesting<br />
|components=Testing::Infrastructure<br />
}}<br />
<br />
{{Module<br />
|name=JS Marionette<br />
|description=NodeJS test harness, marionette client, and other utilities for running marionette tests (submodule of Test Infrastructure)<br />
|owner=[mailto:jlal@mozilla.com James Lal] <lightsofapollo>, [mailto:gaye@mozilla.com Gareth Aye] <gaye><br />
|peers=[mailto:aus@mozilla.com Ghislain "Aus" Lacroix] <auswerk><br />
|source_dirs=gaia/tests/jsmarionette<br />
|components=Testing::JSMarionette<br />
|group=dev-gaia<br />
}}<br />
<br />
{{Module<br />
|name=XPCShell Test Harness<br />
|description=The XPCShell Harness<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:jmaher@mozilla.com Joel Maher]<br />
|source_dirs=testing/xpcshell<br />
|components=Testing::XPCShell Harness<br />
}}<br />
<br />
{{Module<br />
|name=Update Service<br />
|description=server code for Mozilla Update services (aus, addons, pfs)<br />
|owner=Mike Morgan<br />
|peers=[mailto:jscott@mozilla.com Justin Scott], [mailto:shaver@mozilla.org Mike Shaver], [mailto:wclouser@mozilla.com Will Clouser]<br />
|group=dev-amo<br />
|source_dirs=webtools/addons/, webtools/aus/, webtools/update/<br />
|url=http://wiki.mozilla.org/wiki/AMO<br />
|components=AUS::Administration, AUS::Systems<br />
}}<br />
<br />
{{Module<br />
|name=View System<br />
|description=The View Manager is responsible for handling "heavyweight" rendering (some clipping, compositing) and event handling tasks.<br />
|owner=[mailto:mstange@themasta.com Markus Stange]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dbaron@dbaron.org David Baron]<br />
|group=dev-tech-layout<br />
|source_dirs=view/<br />
|url=<br />
|components=Core::Layout: View Rendering<br />
}}<br />
<br />
{{Module<br />
|name=Web Audio<br />
|description=Support for the W3C Web Audio API specification.<br />
|owner=[mailto:padenot@mozilla.com Paul Adenot]<br />
|ownersemeritus=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:karlt+@karlt.net Karl Tomlinson]<br />
|group=dev-platform<br />
|source_dirs=dom/media/webaudio<br />
|url=https://wiki.mozilla.org/Web_Audio_API<br />
|components=Core::Web Audio<br />
}}<br />
<br />
{{Module<br />
|name=Web Painting<br />
|description=painting, display lists, and layer construction<br />
|owner=[mailto:matt.woodrow@gmail.com Matt Woodrow]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:dbaron@dbaron.org David Baron], [mailto:tnikkel@gmail.com Timothy Nikkel], [mailto:mstange@themasta.com Markus Stange]<br />
|group=dev-tech-layout<br />
|source_dirs= layout/painting, the display list and layer related methods on nsIFrame and its subclasses<br />
|url=http://mozilla.org/newlayout/doc/ ,<br />
http://lxr.mozilla.org/mozilla/source/layout/doc/<br />
|components=Core::Layout: Web Painting<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC<br />
|description=WebRTC is responsible for realtime audio and video communication, as well as related issues like low-level camera and microphone access<br />
|owner=[mailto:rjesup@mozilla.com Randell Jesup]<br />
|peers=[mailto:ekr@mozilla.com Eric Rescorla], [mailto:bcampen@mozilla.com Byron Campen] [mailto:abr@mozilla.com Adam Roach]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=N/A (see submodules "WebRTC Media" and "WebRTC Signaling")<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC<br />
}}<br />
<br />
{{Module<br />
|name=Widget<br />
|description=<br />
|owner=[mailto:vladimir@pobox.com Vladimir Vukicevic]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peersemeritus=[mailto:pavlov@pavlov.net Stuart Parmenter], <br />
|group=dev-platform<br />
|source_dirs=widget/, widget/xpwidgets/<br />
|url=<br />
|components=Core::Drag and Drop, Core::Widget, Core::Printing: Setup<br />
}}<br />
<br />
{{Module<br />
|name=Widget - Android<br />
|description=The Android Port<br />
|owner=[mailto:blassey.bugs@lassey.us Brad Lassey]<br />
|peers=[mailto:jwillcox@mozilla.com James Willcox]<br />
|group=dev-platforms-mobile<br />
|source_dirs=widget/android/, embedding/android<br />
|url=<br />
|components=Core::Widget: Android<br />
}}<br />
<br />
{{Module<br />
|name=Widget - GTK<br />
|description=supported X widgetry and gfx<br />
|owner=[mailto:karlt+@karlt.net Karl Tomlinson]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=dev-platform<br />
|source_dirs=widget/gtk/, widget/gtk2/, widget/gtksuperwin/, widget/gtkxtbin/<br />
|url=http://www.mozilla.org/unix/, http://www.gtk.org, http://www.mozilla.org/ports/gtk/<br />
|components=Core::Widget: Gtk<br />
}}<br />
<br />
{{Module<br />
|name=Widget - OS X<br />
|description= Gecko's OS X compatibility layer.<br />
|owner=[mailto:mstange@themasta.com Markus Stange]<br />
|peers=[mailto:joshmoz@gmail.com Josh Aas], [mailto:bgirard@mozilla.com Benoit Girard], [mailto:spohl@mozilla.com Stephen Pohl], [mailto:smichaud@pobox.com Steven Michaud]<br />
|group=dev-platform<br />
|source_dirs=widget/cocoa/<br />
|url=<br />
|components=Core::Widget: Cocoa<br />
}}<br />
<br />
{{Module<br />
|name=Widget - Windows<br />
|description=Windows widgets and desktop integration<br />
|owner=[mailto:jmathies@mozilla.com Jim Mathies]<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:vladimir@pobox.com Vladimir Vukicevic], [mailto:jmathies@mozilla.com Jim Mathies]<br />
|peersemeritus=[mailto:blassey@mozilla.com Brad Lassey], [mailto:netzen@gmail.com Brian Bondy], [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:doug.turner@gmail.com Doug Turner], [mailto:timeless@mozdev.org Josh 'timeless' Soref], [mailto:robarnold@cmu.edu Rob Arnold]<br />
|group=dev-platform<br />
|source_dirs=widget/windows/<br />
|url=<br />
|components=Core::Widget: Win32<br />
}}<br />
<br />
{{Module<br />
|name=XBL<br />
|description=eXtensible Binding Language<br />
|owner=[mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|peers=[mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|ownersemeritus=[mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xbl<br />
|source_dirs=dom/xbl/<br />
|url=http://www.mozilla.org/projects/xbl/<br />
|components=Core::XBL<br />
}}<br />
<br />
{{Module<br />
|name=XML<br />
|description=XML in Mozilla, including XML, XHTML, Namespaces in XML, Associating Style Sheets with XML Documents, XML Linking and XML Extras. XML-related things that are not covered by more specific projects.<br />
|owner=[mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-tech-xml<br />
|source_dirs=dom/xml/, extensions/xmlextras/, parser/expat/<br />
|url=http://www.mozilla.org/newlayout/xml/<br />
|components=Core::XML<br />
}}<br />
<br />
{{Module<br />
|name=XPApps<br />
|description=Cross-Platform Applications, mostly Navigator front end and application shell.<br />
|owner=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|peers=[mailto:dean_tessman@hotmail.com Dean Tessman], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-apps-seamonkey<br />
|source_dirs=xpfe/<br />
|url=http://www.mozilla.org/xpapps/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPCOM<br />
|description=The cross-platform object model and core data structures.<br />
|owner=[https://mozillians.org/en-US/u/froydnj/ Nathan Froyd]<br />
|peers=[https://mozillians.org/en-US/u/bsmedberg/ Benjamin Smedberg], [mailto:erahm@mozilla.com Eric Rahm]<br />
|peersemeritus=[https://mozillians.org/en-US/u/dougt/ Doug Turner]<br />
|group=dev-platform<br />
|source_dirs=startupcache/, xpcom/%, xpcom/base/, xpcom/build/, xpcom/components/, xpcom/ds/, xpcom/glue/, xpcom/proxy/, xpcom/sample/, xpcom/stub/, xpcom/tests/, xpcom/threads/, xpcom/tools/, xpcom/windbgdlg/<br />
|url=http://developer.mozilla.org/en/XPCOM<br />
|components=Core::XPCOM<br />
}}<br />
<br />
{{Module<br />
|name=XPConnect<br />
|description=Deep Magic<br />
|owner=[mailto:bobbyholley@gmail.com Bobby Holley]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:gkrizsanits@mozilla.com Gabor Krizsanits]<br />
|peersemeritus=[mailto:gal@uci.edu Andreas Gal]<br />
|group=<br />
|source_dirs=js/xpconnect/<br />
|url=<br />
|components=Core::XPConnect<br />
}}<br />
<br />
{{Module<br />
|name=XPIDL<br />
|description=Cross-platform IDL compiler; produces .h C++ header files and .xpt runtime type description files from .idl interface description files.<br />
|owner=[mailto:me@kylehuey.com Kyle Huey]<br />
|peersemeritus=[mailto:shaver@mozilla.org Mike Shaver], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-tech-xpcom<br />
|source_dirs=xpcom/typelib/<br />
|url=http://www.mozilla.org/scriptable/xpidl<br />
http://www.mozilla.org/scriptable<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPInstall<br />
|description=<br />
|owner=[mailto:dveditz@mozilla.com Dan Veditz]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-tech-xpinstall<br />
|source_dirs=xpinstall/<br />
|url=<br />
|components=Core::Installer: XPInstall Engine<br />
}}<br />
<br />
{{Module<br />
|name=xptcall<br />
|description=XPTCall - platform-specific assembly for calling and implementing arbitrary XPCOM interfaces.<br />
|owner=<br />
|ownersemeritus=[mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:shaver@mozilla.org Mike Shaver]<br />
|group=dev-xpcom<br />
|source_dirs=xpcom/reflect/xptcall/<br />
|url=http://www.mozilla.org/scriptable/xptcall-faq.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPToolkit<br />
|description=Cross-platform user interface toolkit<br />
|owner=<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:Jan.Varga@gmail.com Jan Varga]<br />
|group=dev-tech-xul<br />
|source_dirs=dom/xul/, layout/xul/<br />
|url=http://www.mozilla.org/xpfe/<br />
|components=Core::XP Toolkit/Widgets: Menus, Core::XP Toolkit/Widgets: XUL<br />
}}<br />
<br />
{{Module<br />
|name=XSLT Processor<br />
|description=XSLT transformations processor<br />
|owner=[mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:axel@pike.org Axel Hecht], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xslt<br />
|source_dirs=dom/xslt/<br />
|url=http://www.mozilla.org/projects/xslt/, http://www.w3.org/TR/xslt.html<br />
|components=Core::XSLT<br />
}}<br />
<br />
{{Module<br />
|name=XTF<br />
|description=eXtensible Tag Framework<br />
|owner=<br />
|peers=[mailto:alex@croczilla.com alex@croczilla.com], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xbl<br />
|source_dirs=content/xtf/, layout/xtf/<br />
|url=http://www.croczilla.com/bits_and_pieces/xtf/<br />
|components=Core::XTF<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing<br />
|description=Cross platform sandboxing<br />
|owner=[mailto:gcp@mozilla.com Gian-Carlo Pascutto]<br />
|peers=[mailto:bowen@mozilla.com Bob Owen], [mailto:aklotz@mozilla.com Aaron Klotz], [https://mozillians.org/en-US/u/TimAbraldes Tim Abraldes], [mailto:gDestuynder@mozilla.com Guillaume Destuynder], [mailto:bsmedberg@mozilla.com Benjamin Smedberg], [mailto:jld@mozilla.com Jed Davis]<br />
|group=dev-platform <br />
|source_dirs=security/sandbox<br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - Windows <br />
|description=Sandboxing for the Windows platform <br />
|owner=[mailto:bowen@mozilla.com Bob Owen]<br />
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:aklotz@mozilla.com Aaron Klotz], [https://mozillians.org/en-US/u/TimAbraldes Tim Abraldes], [mailto:jimm@mozilla.com Jim Mathies]<br />
|group=dev-platform<br />
|source_dirs=security/sandbox/win <br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - OSX <br />
|description=Sandboxing for the OSX platform <br />
|owner=[mailto:haftandilian@mozilla.com Haik Aftandilian]<br />
|peers=<br />
|group=dev-platform <br />
|source_dirs=security/sandbox/mac <br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - Linux & B2G<br />
|description=Sandboxing for the Linux & B2G platforms<br />
|owner=[mailto:jhector@mozilla.com Julian Hector]<br />
|peers=[mailto:jld@mozilla.com Jed Davis] [mailto:gcp@mozilla.com Gian-Carlo Pascutto]<br />
|group=dev-platform<br />
|source_dirs=security/sandbox/linux<br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
===Submodules===<br />
{{Module<br />
|name=Build Config - Fennec<br />
|description=Submodule of the build config covering Fennec's build system in mobile/android.<br />
|owner=[mailto:nalexander@mozilla.com Nicholas Alexander]<br />
|peers=Same as Build Config<br />
|group=dev-builds<br />
|components=Core::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC Media<br />
|description=Submodule of WebRTC responsible for access to media input devices (microphones, cameras, screen capture), as well as realtime audiovisual codecs and packetization.<br />
|owner=[mailto:rjesup@mozilla.com Randell Jesup]<br />
|peers=[mailto:pkerr@mozilla.com Paul Kerr], [mailto:jib@mozilla.com Jan-Ivar Bruaroey]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=/media/webrtc, /dom/media/webrtc<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC (Audio/Video)<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC Signaling<br />
|description=Submodule of WebRTC responsible for implementation of PeerConnection API, WebRTC identity, and SDP/JSEP handling<br />
|owner=[mailto:bcampen@mozilla.com Byron Campen]<br />
|peers=[mailto:ekr@mozilla.com Eric Rescorla], [mailto:abr@mozilla.com Adam Roach], [mailto:rjesup@mozilla.com Randell Jesup], [mailto:nohlmeier@mozilla.com Nils Ohlmeier]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=/media/webrtc/signaling/<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC (Signaling)<br />
}}<br />
<br />
<br />
<noinclude><br />
<br />
===Unassigned Bugzilla Components===<br />
<br />
The following Bugzilla components in the Core project have not been assigned to a module (this list is not exhaustive):<br />
<br />
<pre><br />
Core::File Handling<br />
Core::Find Backend<br />
Core::Gecko Profiler<br />
Core::General<br />
Core::HTML: Form Submission<br />
Core::History: Global<br />
Core::Image Blocking<br />
Core::JavaScript Debugging APIs<br />
Core::Localization<br />
Core::Nanojit<br />
Core::Networking: Domain Lists<br />
Core::Print Preview<br />
Core::Printing: Output<br />
Core::Printing: Setup<br />
Core::Profile: BackEnd<br />
Core::Profile: Migration<br />
Core::Profile: Roaming<br />
Core::QuickLaunch (AKA turbo mode)<br />
Core::Rewriting and Analysis<br />
Core::Selection<br />
Core::Serializers<br />
Core::Spelling checker<br />
Core::Tracking<br />
Core::Web Services<br />
Core::WebDAV<br />
Core::Widget: OS/2<br />
Core::Widget: Photon<br />
Core::X-remote<br />
Core::XForms<br />
Core::XUL<br />
</pre><br />
</noinclude></div>MykMelezhttps://wiki.mozilla.org/index.php?title=Modules/Core&diff=1162139Modules/Core2017-02-07T17:34:38Z<p>MykMelez: add description for Embedding module</p>
<hr />
<div><noinclude><br />
'''Only module owners may edit this page.''' <br />
<br />
They may:<br />
<br />
* update any information about their module except the name of the owner<br />
* add or remove sub-modules<br />
* change the owner of a sub-module <br />
* add emeritus owners or peers<br />
<br />
Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br />
</noinclude><br />
{{Module<br />
|name=Accessibility<br />
|description=Support for platform accessibility APIs. Accessibility APIs are used by 3rd party software like screen readers, screen magnifiers, and voice dictation software, which need information about document content and UI controls, as well as important events like changes of focus.<br />
|owner=[mailto:surkov.alexander@gmail.com Alexander Surkov]<br />
|peers=[mailto:bolterbugz@gmail.com David Bolter], [mailto:trev.saunders@gmail.com Trevor Saunders], [mailto:marco.zehe@googlemail.com Marco Zehe]<br />
|ownersemeritus=[mailto:aaron@moonset.net. Aaron Leventhal]<br />
|peersemeritus=[mailto:ginn.chen@oracle.com Ginn Chen], Evan Yan<br />
|group=dev-accessibility<br />
|source_dirs=accessible/<br />
|url=http://www.mozilla.org/access/<br />
|components=Core::Disability Access APIs<br />
}}<br />
<br />
{{Module<br />
|name=Browser WebAPI<br />
|description=Web API for rendering apps, browser windows and widgets.<br />
|owner=[mailto:kchen@mozilla.com Kan-Ru Chen]<br />
|peers=[mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:fabrice@mozilla.com Fabrice Desré]<br />
|group=dev-webapi<br />
|source_dirs=dom/browser-element/<br />
|url=<br />
|components=Core::DOM<br />
}}<br />
<br />
{{Module<br />
|name=Build and Release Tools<br />
|description=Tools related to build and release automation and configuration of release builds.<br />
|owner=[mailto:nthomas@mozilla.com Nick Thomas]<br />
|peers=[mailto:bhearsum@mozilla.com Ben Hearsum], [mailto:coop@mozilla.com Chris Cooper]<br />
|group=release-engineering<br />
|source_dirs=browser/config/mozconfigs/, mobile/android/config/mozconfigs/, xulrunner/config/mozconfigs/, b2g/config/, tools/update-packaging/<br />
|url=https://wiki.mozilla.org/ReleaseEngineering<br />
|components=Release Engineering::*<br />
}}<br />
<br />
{{Module<br />
|name=Build Config<br />
|description=The build system for Gecko and several mozilla.org hosted Gecko-based applications.<br />
|owner=[mailto:gps@mozilla.com Gregory Szorc] (:gps)<br />
|peers=[mailto:mh@glandium.org Mike Hommey] (:glandium), [mailto:mshal@mozilla.com Mike Shal] (:mshal), [mailto:ted@mielczarek.org Ted Mielczarek] (:ted), [mailto:cmanchester@mozilla.com Chris Manchester](:chmanchester), [mailto:nfroyd@mozilla.com Nathan Froyd] (:froydnj), [mailto:rgiles@mozilla.com Ralph Giles] (:rillian)<br />
|ownersemeritus=Ted Mielczarek (2008-[https://blog.mozilla.org/ted/2013/03/07/gregory-szorc-is-now-the-build-config-module-owner/ 2013]), Benjamin Smedberg (???-[http://benjamin.smedbergs.us/blog/2008-04-30/more-changing-of-the-guard-ted-mielczarek/ 2008]), <br />
|group=dev-builds<br />
|source_dirs=build/, config/, python/mozbuild, tools/cross-commit, tools/cvs2hg-import.py, tools/cvsmgmt/, tools/elf-dynstr-gc/, tools/trees.pl, browser/config/mozconfigs/, mobile/config/mozconfigs/, xulrunner/config/mozconfigs/<br />
|url=http://www.mozilla.org/build/<br />
|components=Core::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=Code Analysis and Debugging Tools<br />
|description=Tools for debugging Mozilla code or for analyzing speed, memory use, and other characteristics of it.<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=<br />
|group=dev-performance<br />
|source_dirs=tools/codesighs/, tools/debug/, tools/dreftool/, tools/dumpdeps/, tools/footprint/, tools/jprof/, tools/leaky/, tools/memory/, tools/module-deps/, tools/performance/, tools/post_compile/, tools/preloader/, tools/rb/, tools/reorder/, tools/trace-malloc/, tools/uuiddeps/, <br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Content HTTP Headers<br />
|description=HTTP headers related to content, e.g. User-Agent, Content-Type, Accept. (Transport-related headers are the responsibility of the Necko module owner.)<br />
|owner=[mailto:gerv@mozilla.org Gervase Markham]<br />
|peers=[mailto:lmandel@mozilla.com Lawrence Mandel]<br />
|group=dev-platform<br />
|source_dirs= <br />
|url=https://developer.mozilla.org/en/Gecko_user_agent_string_reference<br />
|components=Core::Networking: HTTP<br />
}}<br />
<br />
{{Module<br />
|name=Content Security<br />
|description=Native content-based security features, including: Content Security Policy (CSP), Mixed Content Blocker (MCB), Subresource Integrity (SRI) and CORS.<br />
|owner=[mailto:ckerschbaumer@mozilla.com Christoph Kerschbaumer]<br />
|peers=[mailto:francois@mozilla.com François Marier], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:tvyas@mozilla.com Tanvi Vyas], [mailto:dveditz@mozilla.com Dan Veditz], [mailto:mozilla@sidstamm.com Sid Stamm] <br />
|group=dev-security<br />
|source_dirs=dom/security<br />
|components=Core::DOM: Security<br />
}}<br />
<br />
{{Module<br />
|name=Cookies and Permissions<br />
|description=<br />
|owner=Monica Chew<br />
|peers=[mailto:josh@joshmatthews.com Josh Matthews], [mailto:ehsan@mozilla.com Ehsan Akhgari], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dwitte@gmail.com Dan Witte], [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:sdwilsh@shawnwilsher.com Shawn Wilsher (ping on irc)]<br />
|group=dev-tech-network<br />
|source_dirs=extensions/cookie/, netwerk/cookie/<br />
|url=<br />
|components=Core::Networking: Cookies<br />
}}<br />
{{Module<br />
|name=Cycle Collector<br />
|description=Code to break and collect objects within reference cycles<br />
|owner=[https://mozillians.org/en-US/u/mccr8/ Andrew McCreight]<br />
|peers=Peter Van der Beken, Olli Pettay, David Baron<br />
|source_dirs=xpcom/base/nsCycleCollector.* and some support headers<br />
|components=Core::XPCOM<br />
|group=dev-platform<br />
}}<br />
{{Module<br />
|name=C++/Rust usage, tools, and style<br />
|description=Aspects of C++ use such as language feature usage, standard library versions/usage, compiler/toolchain versions, formatting and naming style, and aspects of Rust use as needs arise<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:bballo@mozilla.com Botond Ballo], [mailto:nfroyd@mozilla.com Nathan Froyd], [mailto:glandium@mozilla.com Mike Hommey], [mailto:jwalden@mozilla.com Jeff Walden]<br />
|source_dirs=non-third-party C++ and Rust code in the tree<br />
|components=Various components<br />
|group=dev-platform<br />
}}<br />
{{Module<br />
|name=docshell<br />
|description=<br />
|owner=[mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|peers=[mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:jst@mozilla.org Johnny Stenback], [mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:justin.lebar@gmail.com Justin Lebar]<br />
|group=dev-tech-layout<br />
|source_dirs=docshell/, uriloader/<br />
|url=<br />
|components=Core::Document Navigation<br />
}}<br />
<br />
{{Module<br />
|name=Device Storage<br />
|description=Support for the device storage API<br />
|owner=[https://mozillians.org/u/dhylands/ Dave Hylands] (:dhylands), [mailto:jvarga@mozilla.com Jan Varga] (:janv)<br />
|peers=<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner] (:dougt)<br />
|group=dev-tech-dom<br />
|source_dirs=dom/devicestorage/, dom/interfaces/devicestorage/<br />
|url=https://developer.mozilla.org/en-US/docs/WebAPI/Device_Storage<br />
|components=Core::DOM: Device Interfaces<br />
}}<br />
<br />
{{Module<br />
|name=Document Object Model<br />
|description=<br />
|owner=[mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:bent.mozilla@gmail.com Ben Turner], [mailto:mounir@lamouri.fr Mounir Lamouri (still active, but slower to respond than previously)], [mailto:me@kylehuey.com Kyle Huey], [mailto:hsivonen@iki.fi Henri Sivonen], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:baku@mozilla.com Andrea Marchesini],<br />
[mailto:ehsan@mozilla.com Ehsan Akhgari], [mailto:bkelly@mozilla.com Ben Kelly], [mailto:billm@mozilla.com Bill McCloskey], [mailto:kyle@nonpolynomial.com Kyle Machulis]<br />
|peersemeritus=[mailto:justin.lebar@gmail.com Justin Lebar]<br />
|group=dev-tech-dom<br />
|source_dirs=dom/*, except directories covered by other modules<br />
|url=http://developer.mozilla.org/en/docs/DOM<br />
|components=Core::DOM, Core::DOM: CSS Object Model, Core::DOM: Core & HTML<br />
}}<br />
<br />
{{Module<br />
|name=Event Handling<br />
|description=DOM Events and Event Handling <br />
|owner=[mailto:olli@pettay.fi Olli Pettay], [mailto:masayuki@d-toybox.com Masayuki Nakano]<br />
|group=dev-platform<br />
|source_dirs=dom/events and event handling related code elsewhere <br />
|url=http://developer.mozilla.org/en/docs/DOM<br />
|components=Core::DOM: Events, Core::Event Handling<br />
}}<br />
<br />
{{Module<br />
|name=Web Workers<br />
|description=<br />
|owner=[mailto:bent.mozilla@gmail.com Ben Turner]<br />
|peers=[mailto:mrbkap@mozilla.com Blake Kaplan], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:me@kylehuey.com Kyle Huey], [mailto:baku@mozilla.com Andrea Marchesini], [mailto:bkelly@mozilla.com Ben Kelly]<br />
|group=dev-platform<br />
|source_dirs=dom/workers/<br />
|url=https://developer.mozilla.org/En/Using_web_workers<br />
|components=Core::DOM: Workers<br />
}}<br />
<br />
{{Module<br />
|name=IndexedDB<br />
|description=<br />
|owner=[mailto:bent.mozilla@gmail.com Ben Turner]<br />
|peers=[mailto:jonas@sicking.cc Jonas Sicking], [mailto:me@kylehuey.com Kyle Huey], [mailto:jvarga@mozilla.com Jan Varga], [mailto:btseng@mozilla.com Bevis Tseng]<br />
|group=dev-platform<br />
|source_dirs=dom/indexedDB/<br />
|url=https://developer.mozilla.org/en/IndexedDB<br />
|components=Core::DOM: IndexedDB<br />
}}<br />
<br />
{{Module<br />
|name=Editor<br />
|description=<br />
|owner=[mailto:masayuki@d-toybox.com Masayuki Nakano]<br />
|peers=[mailto:ayg@aryeh.name Aryeh Gregor]<br />
|ownersemeritus=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|group=dev-platform<br />
|source_dirs=editor/<br />
|url=http://www.mozilla.org/editor/<br />
|components=Core::Editor<br />
}}<br />
<br />
{{Module<br />
|name=Embedding<br />
|description=Gecko embedding APIs and frameworks<br />
|owner=[mailto:myk@mykzilla.org Myk Melez]<br />
|ownersemeritus=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:doug.turner@gmail.com Doug Turner]<br />
|peers=[mailto:bdahl@mozilla.com Brendan Dahl], [mailto:tbsaunde@tbsaunde.org Trevor Saunders]<br />
|peersemeritus=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-embedding<br />
|source_dirs=embedding/<br />
|url=<br />
|components=Core::Embedding: APIs<br />
}}<br />
<br />
{{Module<br />
|name=Find As You Type<br />
|description=Find As You Type (formerly called Type Ahead Find) is a feature that allows quick web page navigation when you type a succession of characters in the body of the displayed page (not in an edit box of or drop down list). Currently seeks new owner.<br />
|owner=<br />
|peers=<br />
|group=dev-accessibility<br />
|source_dirs=extensions/typeaheadfind/<br />
|url=http://www.mozilla.org/access/type-ahead/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Geolocation<br />
|description=Implementation of the Geolocation W3C Spec, location provider apis, and wifi scanning code.<br />
|owner=[mailto:josh@joshmatthews.net Josh Matthews], [mailto:kchen@mozilla.com Kan-Ru Chen]<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner], Garvan Keeley<br />
|peers=<br />
|group=dev-tech-dom<br />
|source_dirs=dom/geolocation, dom/system/, netwerk/wifi<br />
|url=https://developer.mozilla.org/En/Using_geolocation<br />
|components=Core::Geolocation<br />
}}<br />
<br />
{{Module<br />
|name=Global Key Bindings<br />
|description=Global hot keys in Mozilla for the browser, editor, mail-news and widgets. Does not include underlined menu accelerators and the like, as those are part of i18n.<br />
|owner=Aaron Leventhal<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|group=dev-accessibility<br />
|source_dirs=dom/xbl/builtin/<br />
|url=http://www.mozilla.org/projects/ui/accessibility/mozkeyintro.html<br />
|components=Core::Keyboard: Navigation<br />
}}<br />
<br />
{{Module<br />
|name=Graphics<br />
|description=Mozilla graphics API<br />
|owner=[mailto:jrmuizel@mozilla.com Jeff Muizelaar](Thebes, QCMS, YCbCr, Cairo/Pixman, Regions, OS X, Other)<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:jdrew@mozilla.com Joe Drew], [mailto:vladimir@pobox.com Vladimir Vukicevic], [mailto:bas.schouten@live.nl Bas Schouten](Layers, Windows), [mailto:bjacob@mozilla.com Benoit Jacob](gfx/gl), [mailto:bgirard@mozilla.com Benoit Girard](Compositor, Performance), [mailto:ajuma.bugzilla@alijuma.com Ali Juma], [mailto:jgilbert@mozilla.com Jeff Gilbert](WebGL, ANGLE), [mailto:george@mozilla.com George Wright](Canvas2D, Skia), [mailto:mwoodrow@mozilla.com Matt Woodrow](Layers API), [mailto:jdaggett@mozilla.com John Daggett](text/fonts), [mailto:jfkthame@googlemail.com Jonathan Kew](text/fonts), [mailto:nsilva@mozilla.com Nicolas Silva](MozSurface), [mailto:ncameron@mozilla.com Nick Cameron], [mailto:sikeda@mozilla.com Sotaro Ikeda](B2G), [mailto:snorp@mozilla.com James Willcox](Android), [mailto:clord@mozilla.com Christopher Lord], [mailto:mstange@themasta.com Markus Stange](OS X), [mailto:lsalzman@mozilla.com Lee Salzman], [mailto:mchang@mozilla.com Mason Chang], [mailto:dvander@mozilla.com David Anderson]<br />
|group=dev-platform<br />
|source_dirs=gfx/, dom/canvas/<br />
|url=https://wiki.mozilla.org/Platform/GFX https://wiki.mozilla.org/Gecko:Layers https://wiki.mozilla.org/Gecko:2DGraphicsSketch<br />
|components=Core::Graphics, Core::Graphics: Layers, Core::Graphics: Text, Core::GFX: Color Management, Core::Canvas: 2D, Core::Canvas: WebGL<br />
}}<br />
<br />
{{Module<br />
|name=APZ (Graphics submodule)<br />
|description=Asynchronous panning and zooming<br />
|owner=[mailto:kgupta@mozilla.com Kartikaya Gupta]<br />
|peers=[mailto:bballo@mozilla.com Botond Ballo], [mailto:tnikkel@mozilla.com Timothy Nikkel], [mailto:dvander@mozilla.com David Anderson], [mailto:mstange@mozilla.com Markus Stange]<br />
|group=dev-platform<br />
|source=gfx/layers/apz<br />
|url=https://wiki.mozilla.org/Platform/GFX/APZ<br />
|components=Core::Panning and Zooming<br />
}}<br />
<br />
{{Module<br />
|name=Moz2D (Graphics submodule)<br />
|description=Platform independent 2D graphics API<br />
|owner=[mailto:bschouten@mozilla.com Bas Schouten]<br />
|peers=[mailto:jmuizelaar@mozilla.com Jeff Muizelaar], [mailto:gwright@mozilla.com George Wright], [mailto:jwatt@mozilla.com Jonathan Watt]<br />
|group=dev-platform<br />
|source=gfx/2d<br />
|url=https://wiki.mozilla.org/Platform/GFX/Moz2D<br />
|components=Core::Graphics<br />
}}<br />
<br />
{{Module<br />
|name=Legacy HTML Parser<br />
|description=<br />
|owner=[mailto:mrbkap@gmail.com Blake Kaplan]<br />
|peers=[mailto:dbaron@dbaron.org David Baron], [mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken], [mailto:rbs@maths.uq.edu.au rbs@maths.uq.edu.au]<br />
|group=dev-tech-dom<br />
|source_dirs=parser/htmlparser<br />
|url=http://www.mozilla.org/newlayout/doc/parser.html<br />
|components=Core::HTML: Parser<br />
}}<br />
<br />
{{Module<br />
|name=HAL<br />
|description=Hardware Abstraction Layer<br />
|owner=[https://mozillians.org/u/dhylands/ Dave Hylands]<br />
|peers=[mailto:gsvelto@mozilla.com Gabriele Svelto]<br />
|group=dev-platform<br />
|source_dirs=hal/<br />
|components=Core::Hardware Abstraction Layer (HAL)<br />
}}<br />
<br />
{{Module<br />
|name=HTML Parser<br />
|description=The HTML Parser transforms HTML source code into a DOM. It conforms to the HTML specification, and is mostly translated automatically from Java to C++.<br />
|owner=[mailto:hsivonen@iki.fi Henri Sivonen]<br />
|peers=<br />
|group=dev-tech-dom<br />
|source_dirs=parser/html<br />
|url=http://about.validator.nu/<br />
|components=Core::HTML: Parser<br />
}}<br />
<br />
{{Module<br />
|name=I18N Library<br />
|description=<br />
|owner=[mailto:jshin1987@gmail.com Jungshik Shin], [mailto:smontagu@smontagu.org Simon Montagu]<br />
|peers=[mailto:VYV03354@nifty.ne.jp Masatoshi Kimura]<br />
|group=dev-i18n<br />
|source_dirs=intl/<br />
|url=http://mozilla.org/projects/intl/index.html<br />
|components=Core::Internationalization<br />
}}<br />
<br />
{{Module<br />
|name=ImageLib<br />
|description=<br />
|owner=[mailto:seth@mozilla.com Seth Fowler]<br />
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:jmuizelaar@mozilla.com Jeff Muizelaar], [mailto:jlebar@mozilla.com Justin Lebar], [mailto:tnikkel@gmail.com Timothy Nikkel]<br />
|group=dev-platform<br />
|source_dirs=media/libjpeg/, media/libpng/, image/, modules/zlib/<br />
|url=<br />
|components=Core::ImageLib<br />
}}<br />
<br />
{{Module<br />
|name=IPC<br />
|description=Message-passing between threads and processes<br />
|owner=[mailto:wmccloskey@mozilla.com Bill McCloskey]<br />
|peers=[mailto:danderson@mozilla.com David Anderson], [mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:bent.mozilla@gmail.com Ben Turner], [mailto:jld@mozilla.com Jed Davis]<br />
|group=dev-platform<br />
|source_dirs=ipc/glue/, ipc/ipdl/, ipc/chromium/<br />
|url=<br />
|components=Core::IPC}}<br />
<br />
{{Module<br />
|name=JavaScript<br />
|description=JavaScript engine (SpiderMonkey)<br />
|owner=[mailto:jorendorff@mozilla.com Jason Orendorff]<br />
|peers=[mailto:jdemooij@mozilla.com Jan de Mooij], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:nnethercote@mozilla.com Nick Nethercote], [mailto:jwalden@mit.edu Jeff Walden], [mailto:hv1989@gmail.com Hannes Verschore], [mailto:kvijayan@mozilla.com Kannan Vijayan], [mailto:shu@mozilla.com Shu-yu Guo], [mailto:evilpies@gmail.com Tom Schuster], [mailto:bhackett1024@gmail.com Brian Hackett], [mailto:till@tillschneidereit.net Till Schneidereit], [mailto:efaust@mozilla.com Eric Faust], [mailto:nfitzgerald@mozilla.com Nick Fitzgerald], [mailto:luke@mozilla.com Luke Wagner], [mailto:arai.unmht@gmail.com Tooru Fujisawa], [mailto:sunfish@mozilla.com Dan Gohman], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:nmatsakis@mozilla.com Niko Matsakis], [mailto:ejpbruel@mozilla.com Eddy Bruel], [mailto:danderson@mozilla.com David Anderson], [mailto:igor@mir2.org Igor Bukanov], [mailto:brendan@mozilla.org Brendan Eich], Andreas Gal<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/src<br />
|url=http://www.mozilla.org/js/spidermonkey,<br />
http://developer.mozilla.org/en/docs/About_JavaScript<br />
|components=Core::JavaScript Engine<br />
}}<br />
<br />
{{Module<br />
|name=JavaScript JIT<br />
|description=JavaScript engine's JIT compilers (IonMonkey, Baseline)<br />
|owner=[mailto:jdemooij@mozilla.com Jan de Mooij]<br />
|peers=[mailto:danderson@mozilla.com David Anderson], [mailto:bbouvier@mozilla.com Benjamin Bouvier], [mailto:shu@mozilla.com Shu-yu Guo], [mailto:bhackett1024@gmail.com Brian Hackett], [mailto:nicolas.b.pierron@mozilla.com Nicolas Pierron], [mailto:evilpies@gmail.com Tom Schuster], [mailto:sstangl@mozilla.com Sean Stangl], [mailto:hv1989@gmail.com Hannes Verschore], [mailto:kvijayan@mozilla.com Kannan Vijayan], [mailto:luke@mozilla.com Luke Wagner]<br />
|group=dev-tech-js-engine-internals<br />
|source_dirs=js/src/jit<br />
|url=http://www.mozilla.org/js/spidermonkey<br />
|components=Core::JavaScript Engine: JIT<br />
}}<br />
<br />
{{Module<br />
|name=JavaScript Debugger Backend<br />
|description=JavaScript debugging hooks<br />
|owner=[mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:rginda@hacksrus.com Rob Ginda]<br />
|group=dev-apps-js-debugger<br />
|source_dirs=js/jsd/<br />
|url=http://www.mozilla.org/js/jsd<br />
|components=Other Applications::Venkman JS Debugger<br />
}}<br />
<br />
{{Module<br />
|name=jsat<br />
|description=Javascript screen reader that is used in Android and B2G<br />
|owner=[mailto:eitan@monotonous.org Eitan Isaacson]<br />
|peers=[mailto:yzenevich@mozilla.com Yura Zenevich]<br />
|group=dev-accessibility<br />
|source_dirs=accessible/jsat/<br />
|url=http://www.mozilla.org/access/<br />
|components=Core::Disability Access APIs<br />
}}<br />
<br />
{{Module<br />
|name=js-ctypes<br />
|description=A foreign function interface which allows privileged JS code to interact with binary code without using XPCOM/XPConnect.<br />
|owner=[mailto:jorendorff@mozilla.com Jason Orendorff]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:bobbyholley@gmail.com Bobby Holley]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/src/ctypes/<br />
|url=https://wiki.mozilla.org/JSctypes<br />
|components=Core::js-ctypes<br />
}}<br />
<br />
{{Module<br />
|name=js-tests<br />
|description=JavaScript test suite<br />
|owner=[mailto:bclary@bclary.com Bob Clary]<br />
|peers=<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/tests/<br />
|url=http://www.mozilla.org/js/tests/library.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Layout Engine<br />
|description=rendering tree construction, layout (reflow), etc.<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dholbert@mozilla.com Daniel Holbert], [mailto:jfkthame@gmail.com Jonathan Kew], [mailto:tnikkel@gmail.com Timothy Nikkel], [mailto:matt.woodrow@gmail.com Matt Woodrow], [mailto:xidorn+moz@upsuper.org Xidorn Quan]<br />
|group=dev-tech-layout<br />
|source_dirs=layout/%, layout/base/, layout/build/, layout/doc/, layout/forms/, layout/generic/, layout/html/, layout/printing/, layout/tables/, layout/tools/<br />
|url=http://mozilla.org/newlayout/doc/ ,<br />
http://lxr.mozilla.org/mozilla/source/layout/doc/<br />
|components=Core::Layout, Core::Layout: Block and Inline, Core::Layout: Floats, Core::Layout: Form Controls, Core::Layout: HTML Frames, Core::Layout: Images, Core::Layout: Misc Code, Core::Layout: R & A Pos, Core::Layout: Tables, Core::Layout: Text, Core::Print Preview, Core::Printing: Output<br />
}}<br />
<br />
{{Module<br />
|name=libjar<br />
|description=The JAR handling code (protocol handler, stream implementation, and zipreader/zipwriter).<br />
|owner=[mailto:mwu@mozilla.com Michael Wu]<br />
|peers=[mailto:aklotz@mozilla.com Aaron Klotz]<br />
|group=dev-platform<br />
|source_dirs=modules/libjar<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=MathML<br />
|description=MathML is a low-level specification for describing mathematics which provides a foundation for the inclusion of mathematical expressions in Web pages.<br />
|owner=[mailto:karlt+@karlt.net Karl Tomlinson]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=dev-tech-mathml<br />
|source_dirs=layout/mathml/<br />
|url=http://www.mozilla.org/projects/mathml/<br />
|components=Core::MathML<br />
}}<br />
<br />
{{Module<br />
|name=Media Playback<br />
|description=HTML Media APIs, including Media Source Extensions and non-MSE video/audio element playback, and Encrypted Media Extensions. (WebRTC and WebAudio not included).<br />
|owner=[mailto:cpearce@mozilla.com Chris Pearce]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:ajones@mozilla.com Anthony Jones], [mailto:kinetik@flim.org Matthew Gregan], [mailto:eflores@mozilla.com Edwin Flores], [mailto:jyavenard@mozilla.com Jean-Yves Avenard], [mailto:gsquelart@mozilla.com Gerald Squelart], [mailto:rgiles@mozilla.com Ralph Giles], [mailto:jwwang@mozilla.com JW Wang]<br />
|group=dev-media<br />
|source_dirs=dom/media, media/gmp-clearkey/, media/libcubeb/, media/libnestegg/, media/libogg/, media/libopus/, media/libstagefright/, media/libtheora/, media/libtremor/, media/libvorbis/, media/libvpx/, media/omx-plugin/, media/rlz/<br />
|url=<br />
|components=Core::Audio/Video<br />
}}<br />
<br />
{{Module<br />
|name=Media Transport<br />
|description=Pluggable transport for real-time media<br />
|owner=[mailto:ekr@rtfm.com Eric Rescorla]<br />
|peers=[mailto:bcampen@mozilla.com Byron Campen], [mailto:abr@mozilla.com Adam Roach], [mailto:nohlmeier@mozilla.com Nils Ohlmeier]<br />
|group=dev-media<br />
|source_dirs=media/mtransport<br />
|url=<br />
|components=Core::WebRTC::Networking<br />
}}<br />
<br />
{{Module<br />
|name=Memory Allocator<br />
|description=Most things related to memory allocation in Gecko, including jemalloc, replace-malloc, DMD (dark matter detector), logalloc, etc.<br />
|owner=[mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|peers=[mailto:n.nethercote@gmail.com Nicholas Nethercote]<br />
|group=dev-platform<br />
|source_dirs=memory/<br />
|components=Core::DMD, Core::jemalloc<br />
}}<br />
<br />
{{Module<br />
|name=mfbt<br />
|description=mfbt is a collection of headers, macros, data structures, methods, and other functionality available for use and reuse throughout all Mozilla code (including SpiderMonkey and Gecko more broadly).<br />
|owner=[mailto:jwalden@mit.edu Jeff Walden]<br />
|peers=[mailto:froydnj@mozilla.com Nathan Froyd], [mailto:Ms2ger@gmail.com Ms2ger], [mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|group=dev-platform<br />
|source_dirs=mfbt/<br />
|url=<br />
|components=Core::MFBT<br />
}}<br />
<br />
{{Module<br />
|name=mozApps API & UI<br />
|description=Implementation of the navigator.mozApps API<br />
|owner=[mailto:fabrice@mozilla.com Fabrice Desré], [mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:myk@mozilla.org Myk Melez], [mailto:mar.castelluccio@studenti.unina.it Marco Castelluccio], [mailto:ferjmoreno@gmail.com Fernando Jiménez]<br />
|group=dev-webapi<br />
|source_dirs=dom/apps/, dom/interfaces/apps, product specific files implementing UI hooks.<br />
|url=<br />
|components=Core::DOM: Apps<br />
}}<br />
<br />
{{Module<br />
|name=Mozglue<br />
|description=Glue library containing various low-level functionality, including a dynamic linker for Android, a DLL block list for Windows, etc.<br />
|owner=[mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|peers=[mailto:froydnj@mozilla.com Nathan Froyd] (mozglue/linker), [mailto:kgupta@mozilla.com Kartikaya Gupta] (mozglue/android), [mailto:nchen@mozilla.com Jim Chen] (mozglue/android)<br />
|group=dev-platform<br />
|source_dirs=mozglue/<br />
|components=Core::mozglue<br />
}}<br />
<br />
{{Module<br />
|name=mozilla-toplevel<br />
|description=The top level directory for the mozilla tree.<br />
|owner=[mailto:brendan@mozilla.org Brendan Eich]<br />
|peers=<br />
|group=<br />
|source_dirs=tools/README<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Necko<br />
|description=The Mozilla Networking Library<br />
|owner=[mailto:mcmanus@ducksong.com Patrick McManus]<br />
|peers= [mailto:jduell.mcbugs@gmail.com Jason Duell], [mailto:honzab.moz@firemni.cz Honza Bambas], [mailto:mnovotny@mozilla.com Michal Novotny], [mailto:hurley@mozilla.com Nick Hurley], [mailto:dd.mozilla@gmail.com Dragana Damjanovic ],[mailto:valentin.gosu@gmail.com Valentin Gosu],[mailto:daniel@haxx.se Daniel Stenberg ]<br />
|peersemeritus= [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:sworkman@mozilla.com Steve Workman], [mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|group=dev-tech-network<br />
|source_dirs=netwerk/%, netwerk/base/, netwerk/build/, netwerk/cache/, netwerk/dns/, netwerk/locales/, netwerk/mime/, netwerk/protocol/, netwerk/resources/, netwerk/socket/, netwerk/streamconv/, netwerk/system/, netwerk/test/, netwerk/testserver/<br />
|url=http://www.mozilla.org/projects/netlib/, https://developer.mozilla.org/en/Necko<br />
|components=Core::Networking, Core::Networking: Cache, Core::Networking: Cookies, Core::Networking: FTP, Core::Networking: File, Core::Networking: HTTP, Core::Networking: JAR, Core::Networking: Websockets<br />
}}<br />
<br />
{{Module<br />
|name=NSPR<br />
|description=Netscape Portable Runtime<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:wtc@google.com Wan-Teh Chang], [mailto:mh@glandium.org Mike Hommey], [mailto:kaie@kuix.de Kai Engert]<br />
|group=dev-tech-nspr<br />
|source_dirs=nsprpub/<br />
|url=http://www.mozilla.org/projects/nspr/<br />
http://www.mozilla.org/projects/nspr/reference/html/<br />
http://www.mozilla.org/projects/nspr/release-notes/<br />
|components=NSPR<br />
}}<br />
<br />
{{Module<br />
|name=PDF<br />
|description=Rendering code to display documents encoded in the ISO 32000-1 `PDF' format.<br />
|owner=Chris Jones, Andreas Gal<br />
|peers=[mailto:aadib@mozilla.com Artur Adib], [mailto:bdahl@mozilla.com Brendan Dahl], [mailto:vnicolas@mozilla.com Vivien Nicolas]<br />
|group=dev-platform<br />
|source_dirs=media/pdf/<br />
|url=https://github.com/mozilla/pdf.js<br />
|components=Core::PDF<br />
}}<br />
<br />
{{Module<br />
|name=Plugins<br />
|description= NPAPI Plugin support.<br />
|owner=[mailto:jmathies@mozilla.com Jim Mathies]<br />
|peers=[mailto:jst@mozilla.org Johnny Stenback], [mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:joshmoz@gmail.com Josh Aas]<br />
|peersemeritus=[mailto:john@pointysoftware.net John Schoenick], [mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=<br />
|source_dirs=dom/plugins/, modules/plugin/<br />
|url=https://wiki.mozilla.org/Plugins<br />
|components=Core::Plug-ins<br />
}}<br />
<br />
{{Module<br />
|name=Preferences<br />
|description=Preference library<br />
|owner=<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-platform<br />
|source_dirs=modules/libpref/<br />
|url=<br />
|components=Core::Preferences: Backend<br />
}}<br />
<br />
{{Module<br />
|name=Private Browsing<br />
|description=Implementation of the Private Browsing mode, and the integration of other modules with Private Browsing APIs.<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:josh@joshmatthews.net Josh Matthews]<br />
|group=dev-platform<br />
|source_dirs=Implementation and consumers of Private Browsing APIs in nsILoadContext, nsIPrivateBrowsingChannel, PrivateBrowsingUtils.jsm and the related glue code. <br />
|url=https://wiki.mozilla.org/Private_Browsing<br />
|components=Firefox::Private Browsing<br />
}}<br />
<br />
{{Module<br />
|name=Privilege Manager<br />
|description="caps"<br />
|owner=[mailto:bobbyholley@gmail.com Bobby Holley]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dveditz@mozilla.com Dan Veditz], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-tech-dom<br />
|source_dirs=caps/<br />
|url=http://www.mozilla.org/projects/security/components/index.html<br />
|components=Core::Security: CAPS<br />
}}<br />
<br />
{{Module<br />
|name=Push Notifications<br />
|description=Push is a way for application developers to send messages to their web applications.<br />
|owners=<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner]<br />
|peers=[mailto:nsm.nikhil@gmail.com Nikhil Marathe], [mailto:kcambridge@mozilla.com Kit Cambridge], [mailto:martin.thomson@gmail.com Martin Thomson], [mailto:ddamjanovic@mozilla.com Dragana Damjanovic]<br />
|group=<br />
|source_dirs=dom/push, dom/simplepush<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=PyXPCOM<br />
|description=The Python to XPCOM bridge.<br />
|owner=Todd Whiteman<br />
|peers=[mailto:mhammond@skippinet.com.au Mark Hammond]<br />
|group=<br />
|source_dirs=extension/python<br />
|url=https://developer.mozilla.org/en/PyXPCOM<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=RDF<br />
|description=<br />
|owner=[mailto:axel@pike.org Axel Hecht]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-tech-rdf<br />
|source_dirs=rdf/<br />
|url=http://www.mozilla.org/rdf/doc/<br />
|components=Core::RDF<br />
}}<br />
<br />
{{Module<br />
|name=security<br />
|description=Crypto/PKI code, including NSS (Network Security Services) and JSS (NSS for Java)<br />
|owner=[mailto:rrelyea@redhat.com Bob Relyea], [mailto:ttaubert@mozilla.com Tim Taubert]<br />
|peers=[mailto:emaldona@redhat.com Elio Maldonado], [mailto:kaie@kuix.de Kai Engert], [mailto:ryan.sleevi@gmail.com Ryan Sleevi], [mailto:ekr@rtfm.com Eric Rescorla], [mailto:franziskuskiefer@gmail.com Franziskus Kiefer], [mailto:martin.thomson@gmail.com Martin Thomson], [mailto:wtc@google.com Wan-Teh Chang]<br />
|group=dev-tech-crypto<br />
|source_dirs=dbm/, security/coreconf/, security/dbm/, security/jss/, security/nss/, security/tinderbox/, security/tinderlight/<br />
|url=http://mozilla.org/projects/security/pki/<br />
|components=NSS, JSS, Core::Security, Core::Security: S/MIME<br />
}}<br />
<br />
{{Module<br />
|name=Security - Mozilla PSM Glue<br />
|description=Personal Security Manager<br />
|owner=[mailto:dkeeler@mozilla.com David Keeler]<br />
|peers=[mailto:honzab.moz@firemni.cz Honza Bambas], [mailto:cykesiopka.bmo@gmail.com Cykesiopka]<br />
|group=dev-tech-crypto<br />
|source_dirs=security/manager/<br />
|url=<br />
|components=Core::Security: PSM, Core::Security: UI<br />
}}<br />
<br />
{{Module<br />
|name=Static analysis & rewriting for C++<br />
|description=Tools for checking C++ code looking for problems at compile time, plus tools for automated rewriting of C++ code.<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:sfink@mozilla.com Steve Fink], [mailto:michael@thelayzells.com Michael Layzell], [mailto:jrmuizel@mozilla.com Jeff Muizelaar], [mailto:birunthan@mohanathas.com Birunthan Mohanathas]<br />
|group=dev-platform<br />
|source_dirs=build/clang-plugin, tools/rewriting among other out of tree tools<br />
|url=<br />
|components=Core::Rewriting & Analysis<br />
}}<br />
{{Module<br />
|name=storage<br />
|description=Storage APIs with a SQLite backend<br />
|owner=[mailto:mak77@bonardo.net Marco Bonardo]<br />
|peers=[mailto:bugmail@asutherland.org Andrew Sutherland], [mailto:jvarga@mozilla.com Jan Varga]<br />
|group=dev-platform<br />
|source_dirs=db/sqlite3/, storage/<br />
|url=http://developer.mozilla.org/en/docs/Storage<br />
|components=Toolkit::Storage, Core::SQL<br />
}}<br />
<br />
{{Module<br />
|name=String<br />
|description=<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:jlebar@mozilla.com Justin Lebar]<br />
|group=dev-tech-xpcom<br />
|source_dirs=string/, xpcom/string/<br />
|url=https://developer.mozilla.org/En/Mozilla_internal_string_guide<br />
|components=Core::String<br />
}}<br />
<br />
{{Module<br />
|name=Style System<br />
|description=CSS style sheet handling; style data computation<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:cam@mcc.id.au Cameron McCormack]<br />
|group=dev-tech-layout<br />
|source_dirs=layout/style/<br />
|url=https://wiki.mozilla.org/Gecko:Overview#Style_System<br />
|components=Core::CSS Parsing and Computation<br />
}}<br />
<br />
{{Module<br />
|name=SVG<br />
|description=Scalable Vector Graphics<br />
|owner=[mailto:jwatt@jwatt.org Jonathan Watt]<br />
|peers=[mailto:longsonr@gmail.com Robert Longson], [mailto:robert@ocallahan.org Robert O'Callahan], [mailto:dholbert@mozilla.com Daniel Holbert], [mailto:birtles@gmail.com Brian Birtles]<br />
|group=dev-tech-svg<br />
|source_dirs=dom/svg/, layout/svg/, dom/smil/<br />
|url=https://developer.mozilla.org/en-US/docs/Web/SVG<br />
|components=Core::SVG<br />
}}<br />
<br />
{{Module<br />
|name=Tamarin<br />
|description=VM for ActionScript and JavaScript<br />
|owner=Edwin Smith, [mailto:jodyer@adobe.com Jeff Dyer]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:stejohns@adobe.com Steven Johnson], [mailto:tierney@adobe.com Erik Tierney], [mailto:treilly@adobe.com Tom Reilly]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/tamarin<br />
|url=http://www.mozilla.org/projects/tamarin/<br />
http://wiki.mozilla.org/tamarin/<br />
http://hg.mozilla.org/tamarin-central/<br />
http://hg.mozilla.org/tamarin-tracing/<br />
|components=Tamarin<br />
}}<br />
<br />
{{Module<br />
|name=Test Harness<br />
|description=In-tree test infrastructure and tools. Harnesses include, XPCShell, Mochitest (& Chrome), Reftest, JsREftest, Compiled Code Tests, Robocop, Mozmill, Marionette, Firefox UI Tests. Requests for new harnesses should go to Testing::General.<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:dbaron@dbaron.org David Baron] (reftest), [mailto:jwalden@mit.edu Jeff Walden] (httpd.js, jsreftest), Rob Campbell (mochitest, mochitest chrome, marionette), [mailto:jmaher@mozilla.com Joel Maher] (reftest, mochitest, jsreftest), [mailto:ctalbert@mozilla.com Clint Talbert] (reftest, compiled code, mozmill), [mailto:geoffbrown@mozilla.com Geoff Brown] (robocop), [mailto:hskupin@mozilla.com Henrik Skupin] (Marionette, Firefox UI tests), [mailto:ato@mozilla.com Andreas Tolfsen] (marionette), [mailto:jgriffin Jonathan Griffin] (marionette), [mailto:dburns@mozilla.com David Burns] (marionette) [mailto:dminor@mozilla.com Dan Minor], [mailto:mjzffr@gmail.com Maja Frydrychowicz] (Marionette, Firefox UI tests), <br />
<br />
|group=dev-quality<br />
|source_dirs=/testing<br />
|url=http://wiki.mozilla.org/SoftwareTesting<br />
|components=Testing::General, Testing::Mochitest, Testing::Mochitest Chrome, Testing::Marionette, Testing::Mozmill, Testing::Reftest, Testing::XPCShell Harness, Testing::httpd.js<br />
}}<br />
<br />
{{Module<br />
|name=Testing Infrastructure<br />
|description=Testing tools and infrastructure for Mozilla projects, harnesses for automated tests, stand-alone test tools. Talos, Graph Server, Mozbase, Pulse, WOO, Bughunter, SUTAgent, Eideticker<br />
|owner=[mailto:jmaher@mozilla.com Joel Maher]<br />
|peers=[mailto:bclary@bclary.com Bob Clary], [mailto:bhearsum@mozilla.com Ben Hearsum], [mailto:ccooper@deadsquid.com Chris Cooper], [mailto:ctalbert@mozilla.com Clint Talbert], [mailto:robert@roberthelmer.com Robert Helmer], [mailto:jmaher@mozilla.com Joel Maher], Rob Campbell, [mailto:wlach@mozilla.com William Lachance], [mailto:jeads@mozilla.com Jonathan Eads], [mailto:jgriffin Jonathan Griffin], [mailto:bmoss@mozilla.com Bob Moss], [mailto:mcote@mozilla.com Mark Côté]<br />
|group=dev-quality<br />
|source_dirs=testing/, tools/httptester/, tools/page-loader/, tools/test-harness/, tools/tests/, tools/testserver/, tools/testy/<br />
|url=http://wiki.mozilla.org/SoftwareTesting<br />
|components=Testing::Infrastructure<br />
}}<br />
<br />
{{Module<br />
|name=JS Marionette<br />
|description=NodeJS test harness, marionette client, and other utilities for running marionette tests (submodule of Test Infrastructure)<br />
|owner=[mailto:jlal@mozilla.com James Lal] <lightsofapollo>, [mailto:gaye@mozilla.com Gareth Aye] <gaye><br />
|peers=[mailto:aus@mozilla.com Ghislain "Aus" Lacroix] <auswerk><br />
|source_dirs=gaia/tests/jsmarionette<br />
|components=Testing::JSMarionette<br />
|group=dev-gaia<br />
}}<br />
<br />
{{Module<br />
|name=XPCShell Test Harness<br />
|description=The XPCShell Harness<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:jmaher@mozilla.com Joel Maher]<br />
|source_dirs=testing/xpcshell<br />
|components=Testing::XPCShell Harness<br />
}}<br />
<br />
{{Module<br />
|name=Update Service<br />
|description=server code for Mozilla Update services (aus, addons, pfs)<br />
|owner=Mike Morgan<br />
|peers=[mailto:jscott@mozilla.com Justin Scott], [mailto:shaver@mozilla.org Mike Shaver], [mailto:wclouser@mozilla.com Will Clouser]<br />
|group=dev-amo<br />
|source_dirs=webtools/addons/, webtools/aus/, webtools/update/<br />
|url=http://wiki.mozilla.org/wiki/AMO<br />
|components=AUS::Administration, AUS::Systems<br />
}}<br />
<br />
{{Module<br />
|name=View System<br />
|description=The View Manager is responsible for handling "heavyweight" rendering (some clipping, compositing) and event handling tasks.<br />
|owner=[mailto:mstange@themasta.com Markus Stange]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dbaron@dbaron.org David Baron]<br />
|group=dev-tech-layout<br />
|source_dirs=view/<br />
|url=<br />
|components=Core::Layout: View Rendering<br />
}}<br />
<br />
{{Module<br />
|name=Web Audio<br />
|description=Support for the W3C Web Audio API specification.<br />
|owner=[mailto:padenot@mozilla.com Paul Adenot]<br />
|ownersemeritus=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:karlt+@karlt.net Karl Tomlinson]<br />
|group=dev-platform<br />
|source_dirs=dom/media/webaudio<br />
|url=https://wiki.mozilla.org/Web_Audio_API<br />
|components=Core::Web Audio<br />
}}<br />
<br />
{{Module<br />
|name=Web Painting<br />
|description=painting, display lists, and layer construction<br />
|owner=[mailto:matt.woodrow@gmail.com Matt Woodrow]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:dbaron@dbaron.org David Baron], [mailto:tnikkel@gmail.com Timothy Nikkel], [mailto:mstange@themasta.com Markus Stange]<br />
|group=dev-tech-layout<br />
|source_dirs= layout/painting, the display list and layer related methods on nsIFrame and its subclasses<br />
|url=http://mozilla.org/newlayout/doc/ ,<br />
http://lxr.mozilla.org/mozilla/source/layout/doc/<br />
|components=Core::Layout: Web Painting<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC<br />
|description=WebRTC is responsible for realtime audio and video communication, as well as related issues like low-level camera and microphone access<br />
|owner=[mailto:rjesup@mozilla.com Randell Jesup]<br />
|peers=[mailto:ekr@mozilla.com Eric Rescorla], [mailto:bcampen@mozilla.com Byron Campen] [mailto:abr@mozilla.com Adam Roach]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=N/A (see submodules "WebRTC Media" and "WebRTC Signaling")<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC<br />
}}<br />
<br />
{{Module<br />
|name=Widget<br />
|description=<br />
|owner=[mailto:vladimir@pobox.com Vladimir Vukicevic]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peersemeritus=[mailto:pavlov@pavlov.net Stuart Parmenter], <br />
|group=dev-platform<br />
|source_dirs=widget/, widget/xpwidgets/<br />
|url=<br />
|components=Core::Drag and Drop, Core::Widget, Core::Printing: Setup<br />
}}<br />
<br />
{{Module<br />
|name=Widget - Android<br />
|description=The Android Port<br />
|owner=[mailto:blassey.bugs@lassey.us Brad Lassey]<br />
|peers=[mailto:jwillcox@mozilla.com James Willcox]<br />
|group=dev-platforms-mobile<br />
|source_dirs=widget/android/, embedding/android<br />
|url=<br />
|components=Core::Widget: Android<br />
}}<br />
<br />
{{Module<br />
|name=Widget - GTK<br />
|description=supported X widgetry and gfx<br />
|owner=[mailto:karlt+@karlt.net Karl Tomlinson]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=dev-platform<br />
|source_dirs=widget/gtk/, widget/gtk2/, widget/gtksuperwin/, widget/gtkxtbin/<br />
|url=http://www.mozilla.org/unix/, http://www.gtk.org, http://www.mozilla.org/ports/gtk/<br />
|components=Core::Widget: Gtk<br />
}}<br />
<br />
{{Module<br />
|name=Widget - OS X<br />
|description= Gecko's OS X compatibility layer.<br />
|owner=[mailto:mstange@themasta.com Markus Stange]<br />
|peers=[mailto:joshmoz@gmail.com Josh Aas], [mailto:bgirard@mozilla.com Benoit Girard], [mailto:spohl@mozilla.com Stephen Pohl], [mailto:smichaud@pobox.com Steven Michaud]<br />
|group=dev-platform<br />
|source_dirs=widget/cocoa/<br />
|url=<br />
|components=Core::Widget: Cocoa<br />
}}<br />
<br />
{{Module<br />
|name=Widget - Windows<br />
|description=Windows widgets and desktop integration<br />
|owner=[mailto:jmathies@mozilla.com Jim Mathies]<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:vladimir@pobox.com Vladimir Vukicevic], [mailto:jmathies@mozilla.com Jim Mathies]<br />
|peersemeritus=[mailto:blassey@mozilla.com Brad Lassey], [mailto:netzen@gmail.com Brian Bondy], [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:doug.turner@gmail.com Doug Turner], [mailto:timeless@mozdev.org Josh 'timeless' Soref], [mailto:robarnold@cmu.edu Rob Arnold]<br />
|group=dev-platform<br />
|source_dirs=widget/windows/<br />
|url=<br />
|components=Core::Widget: Win32<br />
}}<br />
<br />
{{Module<br />
|name=XBL<br />
|description=eXtensible Binding Language<br />
|owner=[mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|peers=[mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|ownersemeritus=[mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xbl<br />
|source_dirs=dom/xbl/<br />
|url=http://www.mozilla.org/projects/xbl/<br />
|components=Core::XBL<br />
}}<br />
<br />
{{Module<br />
|name=XML<br />
|description=XML in Mozilla, including XML, XHTML, Namespaces in XML, Associating Style Sheets with XML Documents, XML Linking and XML Extras. XML-related things that are not covered by more specific projects.<br />
|owner=[mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-tech-xml<br />
|source_dirs=dom/xml/, extensions/xmlextras/, parser/expat/<br />
|url=http://www.mozilla.org/newlayout/xml/<br />
|components=Core::XML<br />
}}<br />
<br />
{{Module<br />
|name=XPApps<br />
|description=Cross-Platform Applications, mostly Navigator front end and application shell.<br />
|owner=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|peers=[mailto:dean_tessman@hotmail.com Dean Tessman], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-apps-seamonkey<br />
|source_dirs=xpfe/<br />
|url=http://www.mozilla.org/xpapps/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPCOM<br />
|description=The cross-platform object model and core data structures.<br />
|owner=[https://mozillians.org/en-US/u/froydnj/ Nathan Froyd]<br />
|peers=[https://mozillians.org/en-US/u/bsmedberg/ Benjamin Smedberg], [mailto:erahm@mozilla.com Eric Rahm]<br />
|peersemeritus=[https://mozillians.org/en-US/u/dougt/ Doug Turner]<br />
|group=dev-platform<br />
|source_dirs=startupcache/, xpcom/%, xpcom/base/, xpcom/build/, xpcom/components/, xpcom/ds/, xpcom/glue/, xpcom/proxy/, xpcom/sample/, xpcom/stub/, xpcom/tests/, xpcom/threads/, xpcom/tools/, xpcom/windbgdlg/<br />
|url=http://developer.mozilla.org/en/XPCOM<br />
|components=Core::XPCOM<br />
}}<br />
<br />
{{Module<br />
|name=XPConnect<br />
|description=Deep Magic<br />
|owner=[mailto:bobbyholley@gmail.com Bobby Holley]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:gkrizsanits@mozilla.com Gabor Krizsanits]<br />
|peersemeritus=[mailto:gal@uci.edu Andreas Gal]<br />
|group=<br />
|source_dirs=js/xpconnect/<br />
|url=<br />
|components=Core::XPConnect<br />
}}<br />
<br />
{{Module<br />
|name=XPIDL<br />
|description=Cross-platform IDL compiler; produces .h C++ header files and .xpt runtime type description files from .idl interface description files.<br />
|owner=[mailto:me@kylehuey.com Kyle Huey]<br />
|peersemeritus=[mailto:shaver@mozilla.org Mike Shaver], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-tech-xpcom<br />
|source_dirs=xpcom/typelib/<br />
|url=http://www.mozilla.org/scriptable/xpidl<br />
http://www.mozilla.org/scriptable<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPInstall<br />
|description=<br />
|owner=[mailto:dveditz@mozilla.com Dan Veditz]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-tech-xpinstall<br />
|source_dirs=xpinstall/<br />
|url=<br />
|components=Core::Installer: XPInstall Engine<br />
}}<br />
<br />
{{Module<br />
|name=xptcall<br />
|description=XPTCall - platform-specific assembly for calling and implementing arbitrary XPCOM interfaces.<br />
|owner=<br />
|ownersemeritus=[mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:shaver@mozilla.org Mike Shaver]<br />
|group=dev-xpcom<br />
|source_dirs=xpcom/reflect/xptcall/<br />
|url=http://www.mozilla.org/scriptable/xptcall-faq.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPToolkit<br />
|description=Cross-platform user interface toolkit<br />
|owner=<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:Jan.Varga@gmail.com Jan Varga]<br />
|group=dev-tech-xul<br />
|source_dirs=dom/xul/, layout/xul/<br />
|url=http://www.mozilla.org/xpfe/<br />
|components=Core::XP Toolkit/Widgets: Menus, Core::XP Toolkit/Widgets: XUL<br />
}}<br />
<br />
{{Module<br />
|name=XSLT Processor<br />
|description=XSLT transformations processor<br />
|owner=[mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:axel@pike.org Axel Hecht], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xslt<br />
|source_dirs=dom/xslt/<br />
|url=http://www.mozilla.org/projects/xslt/, http://www.w3.org/TR/xslt.html<br />
|components=Core::XSLT<br />
}}<br />
<br />
{{Module<br />
|name=XTF<br />
|description=eXtensible Tag Framework<br />
|owner=<br />
|peers=[mailto:alex@croczilla.com alex@croczilla.com], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xbl<br />
|source_dirs=content/xtf/, layout/xtf/<br />
|url=http://www.croczilla.com/bits_and_pieces/xtf/<br />
|components=Core::XTF<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing<br />
|description=Cross platform sandboxing<br />
|owner=[mailto:gcp@mozilla.com Gian-Carlo Pascutto]<br />
|peers=[mailto:bowen@mozilla.com Bob Owen], [mailto:aklotz@mozilla.com Aaron Klotz], [https://mozillians.org/en-US/u/TimAbraldes Tim Abraldes], [mailto:gDestuynder@mozilla.com Guillaume Destuynder], [mailto:bsmedberg@mozilla.com Benjamin Smedberg], [mailto:jld@mozilla.com Jed Davis]<br />
|group=dev-platform <br />
|source_dirs=security/sandbox<br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - Windows <br />
|description=Sandboxing for the Windows platform <br />
|owner=[mailto:bowen@mozilla.com Bob Owen]<br />
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:aklotz@mozilla.com Aaron Klotz], [https://mozillians.org/en-US/u/TimAbraldes Tim Abraldes], [mailto:jimm@mozilla.com Jim Mathies]<br />
|group=dev-platform<br />
|source_dirs=security/sandbox/win <br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - OSX <br />
|description=Sandboxing for the OSX platform <br />
|owner=[mailto:haftandilian@mozilla.com Haik Aftandilian]<br />
|peers=<br />
|group=dev-platform <br />
|source_dirs=security/sandbox/mac <br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - Linux & B2G<br />
|description=Sandboxing for the Linux & B2G platforms<br />
|owner=[mailto:jhector@mozilla.com Julian Hector]<br />
|peers=[mailto:jld@mozilla.com Jed Davis] [mailto:gcp@mozilla.com Gian-Carlo Pascutto]<br />
|group=dev-platform<br />
|source_dirs=security/sandbox/linux<br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
===Submodules===<br />
{{Module<br />
|name=Build Config - Fennec<br />
|description=Submodule of the build config covering Fennec's build system in mobile/android.<br />
|owner=[mailto:nalexander@mozilla.com Nicholas Alexander]<br />
|peers=Same as Build Config<br />
|group=dev-builds<br />
|components=Core::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC Media<br />
|description=Submodule of WebRTC responsible for access to media input devices (microphones, cameras, screen capture), as well as realtime audiovisual codecs and packetization.<br />
|owner=[mailto:rjesup@mozilla.com Randell Jesup]<br />
|peers=[mailto:pkerr@mozilla.com Paul Kerr], [mailto:jib@mozilla.com Jan-Ivar Bruaroey]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=/media/webrtc, /dom/media/webrtc<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC (Audio/Video)<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC Signaling<br />
|description=Submodule of WebRTC responsible for implementation of PeerConnection API, WebRTC identity, and SDP/JSEP handling<br />
|owner=[mailto:bcampen@mozilla.com Byron Campen]<br />
|peers=[mailto:ekr@mozilla.com Eric Rescorla], [mailto:abr@mozilla.com Adam Roach], [mailto:rjesup@mozilla.com Randell Jesup], [mailto:nohlmeier@mozilla.com Nils Ohlmeier]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=/media/webrtc/signaling/<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC (Signaling)<br />
}}<br />
<br />
<br />
<noinclude><br />
<br />
===Unassigned Bugzilla Components===<br />
<br />
The following Bugzilla components in the Core project have not been assigned to a module (this list is not exhaustive):<br />
<br />
<pre><br />
Core::File Handling<br />
Core::Find Backend<br />
Core::Gecko Profiler<br />
Core::General<br />
Core::HTML: Form Submission<br />
Core::History: Global<br />
Core::Image Blocking<br />
Core::JavaScript Debugging APIs<br />
Core::Localization<br />
Core::Nanojit<br />
Core::Networking: Domain Lists<br />
Core::Print Preview<br />
Core::Printing: Output<br />
Core::Printing: Setup<br />
Core::Profile: BackEnd<br />
Core::Profile: Migration<br />
Core::Profile: Roaming<br />
Core::QuickLaunch (AKA turbo mode)<br />
Core::Rewriting and Analysis<br />
Core::Selection<br />
Core::Serializers<br />
Core::Spelling checker<br />
Core::Tracking<br />
Core::Web Services<br />
Core::WebDAV<br />
Core::Widget: OS/2<br />
Core::Widget: Photon<br />
Core::X-remote<br />
Core::XForms<br />
Core::XUL<br />
</pre><br />
</noinclude></div>MykMelezhttps://wiki.mozilla.org/index.php?title=Modules/Core&diff=1162137Modules/Core2017-02-07T17:28:01Z<p>MykMelez: update peers for Embedding module</p>
<hr />
<div><noinclude><br />
'''Only module owners may edit this page.''' <br />
<br />
They may:<br />
<br />
* update any information about their module except the name of the owner<br />
* add or remove sub-modules<br />
* change the owner of a sub-module <br />
* add emeritus owners or peers<br />
<br />
Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].<br />
</noinclude><br />
{{Module<br />
|name=Accessibility<br />
|description=Support for platform accessibility APIs. Accessibility APIs are used by 3rd party software like screen readers, screen magnifiers, and voice dictation software, which need information about document content and UI controls, as well as important events like changes of focus.<br />
|owner=[mailto:surkov.alexander@gmail.com Alexander Surkov]<br />
|peers=[mailto:bolterbugz@gmail.com David Bolter], [mailto:trev.saunders@gmail.com Trevor Saunders], [mailto:marco.zehe@googlemail.com Marco Zehe]<br />
|ownersemeritus=[mailto:aaron@moonset.net. Aaron Leventhal]<br />
|peersemeritus=[mailto:ginn.chen@oracle.com Ginn Chen], Evan Yan<br />
|group=dev-accessibility<br />
|source_dirs=accessible/<br />
|url=http://www.mozilla.org/access/<br />
|components=Core::Disability Access APIs<br />
}}<br />
<br />
{{Module<br />
|name=Browser WebAPI<br />
|description=Web API for rendering apps, browser windows and widgets.<br />
|owner=[mailto:kchen@mozilla.com Kan-Ru Chen]<br />
|peers=[mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:fabrice@mozilla.com Fabrice Desré]<br />
|group=dev-webapi<br />
|source_dirs=dom/browser-element/<br />
|url=<br />
|components=Core::DOM<br />
}}<br />
<br />
{{Module<br />
|name=Build and Release Tools<br />
|description=Tools related to build and release automation and configuration of release builds.<br />
|owner=[mailto:nthomas@mozilla.com Nick Thomas]<br />
|peers=[mailto:bhearsum@mozilla.com Ben Hearsum], [mailto:coop@mozilla.com Chris Cooper]<br />
|group=release-engineering<br />
|source_dirs=browser/config/mozconfigs/, mobile/android/config/mozconfigs/, xulrunner/config/mozconfigs/, b2g/config/, tools/update-packaging/<br />
|url=https://wiki.mozilla.org/ReleaseEngineering<br />
|components=Release Engineering::*<br />
}}<br />
<br />
{{Module<br />
|name=Build Config<br />
|description=The build system for Gecko and several mozilla.org hosted Gecko-based applications.<br />
|owner=[mailto:gps@mozilla.com Gregory Szorc] (:gps)<br />
|peers=[mailto:mh@glandium.org Mike Hommey] (:glandium), [mailto:mshal@mozilla.com Mike Shal] (:mshal), [mailto:ted@mielczarek.org Ted Mielczarek] (:ted), [mailto:cmanchester@mozilla.com Chris Manchester](:chmanchester), [mailto:nfroyd@mozilla.com Nathan Froyd] (:froydnj), [mailto:rgiles@mozilla.com Ralph Giles] (:rillian)<br />
|ownersemeritus=Ted Mielczarek (2008-[https://blog.mozilla.org/ted/2013/03/07/gregory-szorc-is-now-the-build-config-module-owner/ 2013]), Benjamin Smedberg (???-[http://benjamin.smedbergs.us/blog/2008-04-30/more-changing-of-the-guard-ted-mielczarek/ 2008]), <br />
|group=dev-builds<br />
|source_dirs=build/, config/, python/mozbuild, tools/cross-commit, tools/cvs2hg-import.py, tools/cvsmgmt/, tools/elf-dynstr-gc/, tools/trees.pl, browser/config/mozconfigs/, mobile/config/mozconfigs/, xulrunner/config/mozconfigs/<br />
|url=http://www.mozilla.org/build/<br />
|components=Core::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=Code Analysis and Debugging Tools<br />
|description=Tools for debugging Mozilla code or for analyzing speed, memory use, and other characteristics of it.<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=<br />
|group=dev-performance<br />
|source_dirs=tools/codesighs/, tools/debug/, tools/dreftool/, tools/dumpdeps/, tools/footprint/, tools/jprof/, tools/leaky/, tools/memory/, tools/module-deps/, tools/performance/, tools/post_compile/, tools/preloader/, tools/rb/, tools/reorder/, tools/trace-malloc/, tools/uuiddeps/, <br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Content HTTP Headers<br />
|description=HTTP headers related to content, e.g. User-Agent, Content-Type, Accept. (Transport-related headers are the responsibility of the Necko module owner.)<br />
|owner=[mailto:gerv@mozilla.org Gervase Markham]<br />
|peers=[mailto:lmandel@mozilla.com Lawrence Mandel]<br />
|group=dev-platform<br />
|source_dirs= <br />
|url=https://developer.mozilla.org/en/Gecko_user_agent_string_reference<br />
|components=Core::Networking: HTTP<br />
}}<br />
<br />
{{Module<br />
|name=Content Security<br />
|description=Native content-based security features, including: Content Security Policy (CSP), Mixed Content Blocker (MCB), Subresource Integrity (SRI) and CORS.<br />
|owner=[mailto:ckerschbaumer@mozilla.com Christoph Kerschbaumer]<br />
|peers=[mailto:francois@mozilla.com François Marier], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:tvyas@mozilla.com Tanvi Vyas], [mailto:dveditz@mozilla.com Dan Veditz], [mailto:mozilla@sidstamm.com Sid Stamm] <br />
|group=dev-security<br />
|source_dirs=dom/security<br />
|components=Core::DOM: Security<br />
}}<br />
<br />
{{Module<br />
|name=Cookies and Permissions<br />
|description=<br />
|owner=Monica Chew<br />
|peers=[mailto:josh@joshmatthews.com Josh Matthews], [mailto:ehsan@mozilla.com Ehsan Akhgari], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dwitte@gmail.com Dan Witte], [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:sdwilsh@shawnwilsher.com Shawn Wilsher (ping on irc)]<br />
|group=dev-tech-network<br />
|source_dirs=extensions/cookie/, netwerk/cookie/<br />
|url=<br />
|components=Core::Networking: Cookies<br />
}}<br />
{{Module<br />
|name=Cycle Collector<br />
|description=Code to break and collect objects within reference cycles<br />
|owner=[https://mozillians.org/en-US/u/mccr8/ Andrew McCreight]<br />
|peers=Peter Van der Beken, Olli Pettay, David Baron<br />
|source_dirs=xpcom/base/nsCycleCollector.* and some support headers<br />
|components=Core::XPCOM<br />
|group=dev-platform<br />
}}<br />
{{Module<br />
|name=C++/Rust usage, tools, and style<br />
|description=Aspects of C++ use such as language feature usage, standard library versions/usage, compiler/toolchain versions, formatting and naming style, and aspects of Rust use as needs arise<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:bballo@mozilla.com Botond Ballo], [mailto:nfroyd@mozilla.com Nathan Froyd], [mailto:glandium@mozilla.com Mike Hommey], [mailto:jwalden@mozilla.com Jeff Walden]<br />
|source_dirs=non-third-party C++ and Rust code in the tree<br />
|components=Various components<br />
|group=dev-platform<br />
}}<br />
{{Module<br />
|name=docshell<br />
|description=<br />
|owner=[mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|peers=[mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:jst@mozilla.org Johnny Stenback], [mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:justin.lebar@gmail.com Justin Lebar]<br />
|group=dev-tech-layout<br />
|source_dirs=docshell/, uriloader/<br />
|url=<br />
|components=Core::Document Navigation<br />
}}<br />
<br />
{{Module<br />
|name=Device Storage<br />
|description=Support for the device storage API<br />
|owner=[https://mozillians.org/u/dhylands/ Dave Hylands] (:dhylands), [mailto:jvarga@mozilla.com Jan Varga] (:janv)<br />
|peers=<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner] (:dougt)<br />
|group=dev-tech-dom<br />
|source_dirs=dom/devicestorage/, dom/interfaces/devicestorage/<br />
|url=https://developer.mozilla.org/en-US/docs/WebAPI/Device_Storage<br />
|components=Core::DOM: Device Interfaces<br />
}}<br />
<br />
{{Module<br />
|name=Document Object Model<br />
|description=<br />
|owner=[mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:Olli.Pettay@helsinki.fi Olli Pettay], [mailto:bent.mozilla@gmail.com Ben Turner], [mailto:mounir@lamouri.fr Mounir Lamouri (still active, but slower to respond than previously)], [mailto:me@kylehuey.com Kyle Huey], [mailto:hsivonen@iki.fi Henri Sivonen], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:baku@mozilla.com Andrea Marchesini],<br />
[mailto:ehsan@mozilla.com Ehsan Akhgari], [mailto:bkelly@mozilla.com Ben Kelly], [mailto:billm@mozilla.com Bill McCloskey], [mailto:kyle@nonpolynomial.com Kyle Machulis]<br />
|peersemeritus=[mailto:justin.lebar@gmail.com Justin Lebar]<br />
|group=dev-tech-dom<br />
|source_dirs=dom/*, except directories covered by other modules<br />
|url=http://developer.mozilla.org/en/docs/DOM<br />
|components=Core::DOM, Core::DOM: CSS Object Model, Core::DOM: Core & HTML<br />
}}<br />
<br />
{{Module<br />
|name=Event Handling<br />
|description=DOM Events and Event Handling <br />
|owner=[mailto:olli@pettay.fi Olli Pettay], [mailto:masayuki@d-toybox.com Masayuki Nakano]<br />
|group=dev-platform<br />
|source_dirs=dom/events and event handling related code elsewhere <br />
|url=http://developer.mozilla.org/en/docs/DOM<br />
|components=Core::DOM: Events, Core::Event Handling<br />
}}<br />
<br />
{{Module<br />
|name=Web Workers<br />
|description=<br />
|owner=[mailto:bent.mozilla@gmail.com Ben Turner]<br />
|peers=[mailto:mrbkap@mozilla.com Blake Kaplan], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:me@kylehuey.com Kyle Huey], [mailto:baku@mozilla.com Andrea Marchesini], [mailto:bkelly@mozilla.com Ben Kelly]<br />
|group=dev-platform<br />
|source_dirs=dom/workers/<br />
|url=https://developer.mozilla.org/En/Using_web_workers<br />
|components=Core::DOM: Workers<br />
}}<br />
<br />
{{Module<br />
|name=IndexedDB<br />
|description=<br />
|owner=[mailto:bent.mozilla@gmail.com Ben Turner]<br />
|peers=[mailto:jonas@sicking.cc Jonas Sicking], [mailto:me@kylehuey.com Kyle Huey], [mailto:jvarga@mozilla.com Jan Varga], [mailto:btseng@mozilla.com Bevis Tseng]<br />
|group=dev-platform<br />
|source_dirs=dom/indexedDB/<br />
|url=https://developer.mozilla.org/en/IndexedDB<br />
|components=Core::DOM: IndexedDB<br />
}}<br />
<br />
{{Module<br />
|name=Editor<br />
|description=<br />
|owner=[mailto:masayuki@d-toybox.com Masayuki Nakano]<br />
|peers=[mailto:ayg@aryeh.name Aryeh Gregor]<br />
|ownersemeritus=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|group=dev-platform<br />
|source_dirs=editor/<br />
|url=http://www.mozilla.org/editor/<br />
|components=Core::Editor<br />
}}<br />
<br />
{{Module<br />
|name=Embedding<br />
|description=<br />
|owner=[mailto:myk@mykzilla.org Myk Melez]<br />
|ownersemeritus=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:doug.turner@gmail.com Doug Turner]<br />
|peers=[mailto:bdahl@mozilla.com Brendan Dahl], [mailto:tbsaunde@tbsaunde.org Trevor Saunders]<br />
|peersemeritus=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-embedding<br />
|source_dirs=embedding/<br />
|url=<br />
|components=Core::Embedding: APIs<br />
}}<br />
<br />
{{Module<br />
|name=Find As You Type<br />
|description=Find As You Type (formerly called Type Ahead Find) is a feature that allows quick web page navigation when you type a succession of characters in the body of the displayed page (not in an edit box of or drop down list). Currently seeks new owner.<br />
|owner=<br />
|peers=<br />
|group=dev-accessibility<br />
|source_dirs=extensions/typeaheadfind/<br />
|url=http://www.mozilla.org/access/type-ahead/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Geolocation<br />
|description=Implementation of the Geolocation W3C Spec, location provider apis, and wifi scanning code.<br />
|owner=[mailto:josh@joshmatthews.net Josh Matthews], [mailto:kchen@mozilla.com Kan-Ru Chen]<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner], Garvan Keeley<br />
|peers=<br />
|group=dev-tech-dom<br />
|source_dirs=dom/geolocation, dom/system/, netwerk/wifi<br />
|url=https://developer.mozilla.org/En/Using_geolocation<br />
|components=Core::Geolocation<br />
}}<br />
<br />
{{Module<br />
|name=Global Key Bindings<br />
|description=Global hot keys in Mozilla for the browser, editor, mail-news and widgets. Does not include underlined menu accelerators and the like, as those are part of i18n.<br />
|owner=Aaron Leventhal<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|group=dev-accessibility<br />
|source_dirs=dom/xbl/builtin/<br />
|url=http://www.mozilla.org/projects/ui/accessibility/mozkeyintro.html<br />
|components=Core::Keyboard: Navigation<br />
}}<br />
<br />
{{Module<br />
|name=Graphics<br />
|description=Mozilla graphics API<br />
|owner=[mailto:jrmuizel@mozilla.com Jeff Muizelaar](Thebes, QCMS, YCbCr, Cairo/Pixman, Regions, OS X, Other)<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:jdrew@mozilla.com Joe Drew], [mailto:vladimir@pobox.com Vladimir Vukicevic], [mailto:bas.schouten@live.nl Bas Schouten](Layers, Windows), [mailto:bjacob@mozilla.com Benoit Jacob](gfx/gl), [mailto:bgirard@mozilla.com Benoit Girard](Compositor, Performance), [mailto:ajuma.bugzilla@alijuma.com Ali Juma], [mailto:jgilbert@mozilla.com Jeff Gilbert](WebGL, ANGLE), [mailto:george@mozilla.com George Wright](Canvas2D, Skia), [mailto:mwoodrow@mozilla.com Matt Woodrow](Layers API), [mailto:jdaggett@mozilla.com John Daggett](text/fonts), [mailto:jfkthame@googlemail.com Jonathan Kew](text/fonts), [mailto:nsilva@mozilla.com Nicolas Silva](MozSurface), [mailto:ncameron@mozilla.com Nick Cameron], [mailto:sikeda@mozilla.com Sotaro Ikeda](B2G), [mailto:snorp@mozilla.com James Willcox](Android), [mailto:clord@mozilla.com Christopher Lord], [mailto:mstange@themasta.com Markus Stange](OS X), [mailto:lsalzman@mozilla.com Lee Salzman], [mailto:mchang@mozilla.com Mason Chang], [mailto:dvander@mozilla.com David Anderson]<br />
|group=dev-platform<br />
|source_dirs=gfx/, dom/canvas/<br />
|url=https://wiki.mozilla.org/Platform/GFX https://wiki.mozilla.org/Gecko:Layers https://wiki.mozilla.org/Gecko:2DGraphicsSketch<br />
|components=Core::Graphics, Core::Graphics: Layers, Core::Graphics: Text, Core::GFX: Color Management, Core::Canvas: 2D, Core::Canvas: WebGL<br />
}}<br />
<br />
{{Module<br />
|name=APZ (Graphics submodule)<br />
|description=Asynchronous panning and zooming<br />
|owner=[mailto:kgupta@mozilla.com Kartikaya Gupta]<br />
|peers=[mailto:bballo@mozilla.com Botond Ballo], [mailto:tnikkel@mozilla.com Timothy Nikkel], [mailto:dvander@mozilla.com David Anderson], [mailto:mstange@mozilla.com Markus Stange]<br />
|group=dev-platform<br />
|source=gfx/layers/apz<br />
|url=https://wiki.mozilla.org/Platform/GFX/APZ<br />
|components=Core::Panning and Zooming<br />
}}<br />
<br />
{{Module<br />
|name=Moz2D (Graphics submodule)<br />
|description=Platform independent 2D graphics API<br />
|owner=[mailto:bschouten@mozilla.com Bas Schouten]<br />
|peers=[mailto:jmuizelaar@mozilla.com Jeff Muizelaar], [mailto:gwright@mozilla.com George Wright], [mailto:jwatt@mozilla.com Jonathan Watt]<br />
|group=dev-platform<br />
|source=gfx/2d<br />
|url=https://wiki.mozilla.org/Platform/GFX/Moz2D<br />
|components=Core::Graphics<br />
}}<br />
<br />
{{Module<br />
|name=Legacy HTML Parser<br />
|description=<br />
|owner=[mailto:mrbkap@gmail.com Blake Kaplan]<br />
|peers=[mailto:dbaron@dbaron.org David Baron], [mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken], [mailto:rbs@maths.uq.edu.au rbs@maths.uq.edu.au]<br />
|group=dev-tech-dom<br />
|source_dirs=parser/htmlparser<br />
|url=http://www.mozilla.org/newlayout/doc/parser.html<br />
|components=Core::HTML: Parser<br />
}}<br />
<br />
{{Module<br />
|name=HAL<br />
|description=Hardware Abstraction Layer<br />
|owner=[https://mozillians.org/u/dhylands/ Dave Hylands]<br />
|peers=[mailto:gsvelto@mozilla.com Gabriele Svelto]<br />
|group=dev-platform<br />
|source_dirs=hal/<br />
|components=Core::Hardware Abstraction Layer (HAL)<br />
}}<br />
<br />
{{Module<br />
|name=HTML Parser<br />
|description=The HTML Parser transforms HTML source code into a DOM. It conforms to the HTML specification, and is mostly translated automatically from Java to C++.<br />
|owner=[mailto:hsivonen@iki.fi Henri Sivonen]<br />
|peers=<br />
|group=dev-tech-dom<br />
|source_dirs=parser/html<br />
|url=http://about.validator.nu/<br />
|components=Core::HTML: Parser<br />
}}<br />
<br />
{{Module<br />
|name=I18N Library<br />
|description=<br />
|owner=[mailto:jshin1987@gmail.com Jungshik Shin], [mailto:smontagu@smontagu.org Simon Montagu]<br />
|peers=[mailto:VYV03354@nifty.ne.jp Masatoshi Kimura]<br />
|group=dev-i18n<br />
|source_dirs=intl/<br />
|url=http://mozilla.org/projects/intl/index.html<br />
|components=Core::Internationalization<br />
}}<br />
<br />
{{Module<br />
|name=ImageLib<br />
|description=<br />
|owner=[mailto:seth@mozilla.com Seth Fowler]<br />
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:jmuizelaar@mozilla.com Jeff Muizelaar], [mailto:jlebar@mozilla.com Justin Lebar], [mailto:tnikkel@gmail.com Timothy Nikkel]<br />
|group=dev-platform<br />
|source_dirs=media/libjpeg/, media/libpng/, image/, modules/zlib/<br />
|url=<br />
|components=Core::ImageLib<br />
}}<br />
<br />
{{Module<br />
|name=IPC<br />
|description=Message-passing between threads and processes<br />
|owner=[mailto:wmccloskey@mozilla.com Bill McCloskey]<br />
|peers=[mailto:danderson@mozilla.com David Anderson], [mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:bent.mozilla@gmail.com Ben Turner], [mailto:jld@mozilla.com Jed Davis]<br />
|group=dev-platform<br />
|source_dirs=ipc/glue/, ipc/ipdl/, ipc/chromium/<br />
|url=<br />
|components=Core::IPC}}<br />
<br />
{{Module<br />
|name=JavaScript<br />
|description=JavaScript engine (SpiderMonkey)<br />
|owner=[mailto:jorendorff@mozilla.com Jason Orendorff]<br />
|peers=[mailto:jdemooij@mozilla.com Jan de Mooij], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:nnethercote@mozilla.com Nick Nethercote], [mailto:jwalden@mit.edu Jeff Walden], [mailto:hv1989@gmail.com Hannes Verschore], [mailto:kvijayan@mozilla.com Kannan Vijayan], [mailto:shu@mozilla.com Shu-yu Guo], [mailto:evilpies@gmail.com Tom Schuster], [mailto:bhackett1024@gmail.com Brian Hackett], [mailto:till@tillschneidereit.net Till Schneidereit], [mailto:efaust@mozilla.com Eric Faust], [mailto:nfitzgerald@mozilla.com Nick Fitzgerald], [mailto:luke@mozilla.com Luke Wagner], [mailto:arai.unmht@gmail.com Tooru Fujisawa], [mailto:sunfish@mozilla.com Dan Gohman], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:nmatsakis@mozilla.com Niko Matsakis], [mailto:ejpbruel@mozilla.com Eddy Bruel], [mailto:danderson@mozilla.com David Anderson], [mailto:igor@mir2.org Igor Bukanov], [mailto:brendan@mozilla.org Brendan Eich], Andreas Gal<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/src<br />
|url=http://www.mozilla.org/js/spidermonkey,<br />
http://developer.mozilla.org/en/docs/About_JavaScript<br />
|components=Core::JavaScript Engine<br />
}}<br />
<br />
{{Module<br />
|name=JavaScript JIT<br />
|description=JavaScript engine's JIT compilers (IonMonkey, Baseline)<br />
|owner=[mailto:jdemooij@mozilla.com Jan de Mooij]<br />
|peers=[mailto:danderson@mozilla.com David Anderson], [mailto:bbouvier@mozilla.com Benjamin Bouvier], [mailto:shu@mozilla.com Shu-yu Guo], [mailto:bhackett1024@gmail.com Brian Hackett], [mailto:nicolas.b.pierron@mozilla.com Nicolas Pierron], [mailto:evilpies@gmail.com Tom Schuster], [mailto:sstangl@mozilla.com Sean Stangl], [mailto:hv1989@gmail.com Hannes Verschore], [mailto:kvijayan@mozilla.com Kannan Vijayan], [mailto:luke@mozilla.com Luke Wagner]<br />
|group=dev-tech-js-engine-internals<br />
|source_dirs=js/src/jit<br />
|url=http://www.mozilla.org/js/spidermonkey<br />
|components=Core::JavaScript Engine: JIT<br />
}}<br />
<br />
{{Module<br />
|name=JavaScript Debugger Backend<br />
|description=JavaScript debugging hooks<br />
|owner=[mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:rginda@hacksrus.com Rob Ginda]<br />
|group=dev-apps-js-debugger<br />
|source_dirs=js/jsd/<br />
|url=http://www.mozilla.org/js/jsd<br />
|components=Other Applications::Venkman JS Debugger<br />
}}<br />
<br />
{{Module<br />
|name=jsat<br />
|description=Javascript screen reader that is used in Android and B2G<br />
|owner=[mailto:eitan@monotonous.org Eitan Isaacson]<br />
|peers=[mailto:yzenevich@mozilla.com Yura Zenevich]<br />
|group=dev-accessibility<br />
|source_dirs=accessible/jsat/<br />
|url=http://www.mozilla.org/access/<br />
|components=Core::Disability Access APIs<br />
}}<br />
<br />
{{Module<br />
|name=js-ctypes<br />
|description=A foreign function interface which allows privileged JS code to interact with binary code without using XPCOM/XPConnect.<br />
|owner=[mailto:jorendorff@mozilla.com Jason Orendorff]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:bobbyholley@gmail.com Bobby Holley]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/src/ctypes/<br />
|url=https://wiki.mozilla.org/JSctypes<br />
|components=Core::js-ctypes<br />
}}<br />
<br />
{{Module<br />
|name=js-tests<br />
|description=JavaScript test suite<br />
|owner=[mailto:bclary@bclary.com Bob Clary]<br />
|peers=<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/tests/<br />
|url=http://www.mozilla.org/js/tests/library.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Layout Engine<br />
|description=rendering tree construction, layout (reflow), etc.<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dholbert@mozilla.com Daniel Holbert], [mailto:jfkthame@gmail.com Jonathan Kew], [mailto:tnikkel@gmail.com Timothy Nikkel], [mailto:matt.woodrow@gmail.com Matt Woodrow], [mailto:xidorn+moz@upsuper.org Xidorn Quan]<br />
|group=dev-tech-layout<br />
|source_dirs=layout/%, layout/base/, layout/build/, layout/doc/, layout/forms/, layout/generic/, layout/html/, layout/printing/, layout/tables/, layout/tools/<br />
|url=http://mozilla.org/newlayout/doc/ ,<br />
http://lxr.mozilla.org/mozilla/source/layout/doc/<br />
|components=Core::Layout, Core::Layout: Block and Inline, Core::Layout: Floats, Core::Layout: Form Controls, Core::Layout: HTML Frames, Core::Layout: Images, Core::Layout: Misc Code, Core::Layout: R & A Pos, Core::Layout: Tables, Core::Layout: Text, Core::Print Preview, Core::Printing: Output<br />
}}<br />
<br />
{{Module<br />
|name=libjar<br />
|description=The JAR handling code (protocol handler, stream implementation, and zipreader/zipwriter).<br />
|owner=[mailto:mwu@mozilla.com Michael Wu]<br />
|peers=[mailto:aklotz@mozilla.com Aaron Klotz]<br />
|group=dev-platform<br />
|source_dirs=modules/libjar<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=MathML<br />
|description=MathML is a low-level specification for describing mathematics which provides a foundation for the inclusion of mathematical expressions in Web pages.<br />
|owner=[mailto:karlt+@karlt.net Karl Tomlinson]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=dev-tech-mathml<br />
|source_dirs=layout/mathml/<br />
|url=http://www.mozilla.org/projects/mathml/<br />
|components=Core::MathML<br />
}}<br />
<br />
{{Module<br />
|name=Media Playback<br />
|description=HTML Media APIs, including Media Source Extensions and non-MSE video/audio element playback, and Encrypted Media Extensions. (WebRTC and WebAudio not included).<br />
|owner=[mailto:cpearce@mozilla.com Chris Pearce]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:ajones@mozilla.com Anthony Jones], [mailto:kinetik@flim.org Matthew Gregan], [mailto:eflores@mozilla.com Edwin Flores], [mailto:jyavenard@mozilla.com Jean-Yves Avenard], [mailto:gsquelart@mozilla.com Gerald Squelart], [mailto:rgiles@mozilla.com Ralph Giles], [mailto:jwwang@mozilla.com JW Wang]<br />
|group=dev-media<br />
|source_dirs=dom/media, media/gmp-clearkey/, media/libcubeb/, media/libnestegg/, media/libogg/, media/libopus/, media/libstagefright/, media/libtheora/, media/libtremor/, media/libvorbis/, media/libvpx/, media/omx-plugin/, media/rlz/<br />
|url=<br />
|components=Core::Audio/Video<br />
}}<br />
<br />
{{Module<br />
|name=Media Transport<br />
|description=Pluggable transport for real-time media<br />
|owner=[mailto:ekr@rtfm.com Eric Rescorla]<br />
|peers=[mailto:bcampen@mozilla.com Byron Campen], [mailto:abr@mozilla.com Adam Roach], [mailto:nohlmeier@mozilla.com Nils Ohlmeier]<br />
|group=dev-media<br />
|source_dirs=media/mtransport<br />
|url=<br />
|components=Core::WebRTC::Networking<br />
}}<br />
<br />
{{Module<br />
|name=Memory Allocator<br />
|description=Most things related to memory allocation in Gecko, including jemalloc, replace-malloc, DMD (dark matter detector), logalloc, etc.<br />
|owner=[mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|peers=[mailto:n.nethercote@gmail.com Nicholas Nethercote]<br />
|group=dev-platform<br />
|source_dirs=memory/<br />
|components=Core::DMD, Core::jemalloc<br />
}}<br />
<br />
{{Module<br />
|name=mfbt<br />
|description=mfbt is a collection of headers, macros, data structures, methods, and other functionality available for use and reuse throughout all Mozilla code (including SpiderMonkey and Gecko more broadly).<br />
|owner=[mailto:jwalden@mit.edu Jeff Walden]<br />
|peers=[mailto:froydnj@mozilla.com Nathan Froyd], [mailto:Ms2ger@gmail.com Ms2ger], [mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|group=dev-platform<br />
|source_dirs=mfbt/<br />
|url=<br />
|components=Core::MFBT<br />
}}<br />
<br />
{{Module<br />
|name=mozApps API & UI<br />
|description=Implementation of the navigator.mozApps API<br />
|owner=[mailto:fabrice@mozilla.com Fabrice Desré], [mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:myk@mozilla.org Myk Melez], [mailto:mar.castelluccio@studenti.unina.it Marco Castelluccio], [mailto:ferjmoreno@gmail.com Fernando Jiménez]<br />
|group=dev-webapi<br />
|source_dirs=dom/apps/, dom/interfaces/apps, product specific files implementing UI hooks.<br />
|url=<br />
|components=Core::DOM: Apps<br />
}}<br />
<br />
{{Module<br />
|name=Mozglue<br />
|description=Glue library containing various low-level functionality, including a dynamic linker for Android, a DLL block list for Windows, etc.<br />
|owner=[mailto:mh+mozilla@glandium.org Mike Hommey]<br />
|peers=[mailto:froydnj@mozilla.com Nathan Froyd] (mozglue/linker), [mailto:kgupta@mozilla.com Kartikaya Gupta] (mozglue/android), [mailto:nchen@mozilla.com Jim Chen] (mozglue/android)<br />
|group=dev-platform<br />
|source_dirs=mozglue/<br />
|components=Core::mozglue<br />
}}<br />
<br />
{{Module<br />
|name=mozilla-toplevel<br />
|description=The top level directory for the mozilla tree.<br />
|owner=[mailto:brendan@mozilla.org Brendan Eich]<br />
|peers=<br />
|group=<br />
|source_dirs=tools/README<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Necko<br />
|description=The Mozilla Networking Library<br />
|owner=[mailto:mcmanus@ducksong.com Patrick McManus]<br />
|peers= [mailto:jduell.mcbugs@gmail.com Jason Duell], [mailto:honzab.moz@firemni.cz Honza Bambas], [mailto:mnovotny@mozilla.com Michal Novotny], [mailto:hurley@mozilla.com Nick Hurley], [mailto:dd.mozilla@gmail.com Dragana Damjanovic ],[mailto:valentin.gosu@gmail.com Valentin Gosu],[mailto:daniel@haxx.se Daniel Stenberg ]<br />
|peersemeritus= [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:sworkman@mozilla.com Steve Workman], [mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|group=dev-tech-network<br />
|source_dirs=netwerk/%, netwerk/base/, netwerk/build/, netwerk/cache/, netwerk/dns/, netwerk/locales/, netwerk/mime/, netwerk/protocol/, netwerk/resources/, netwerk/socket/, netwerk/streamconv/, netwerk/system/, netwerk/test/, netwerk/testserver/<br />
|url=http://www.mozilla.org/projects/netlib/, https://developer.mozilla.org/en/Necko<br />
|components=Core::Networking, Core::Networking: Cache, Core::Networking: Cookies, Core::Networking: FTP, Core::Networking: File, Core::Networking: HTTP, Core::Networking: JAR, Core::Networking: Websockets<br />
}}<br />
<br />
{{Module<br />
|name=NSPR<br />
|description=Netscape Portable Runtime<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:wtc@google.com Wan-Teh Chang], [mailto:mh@glandium.org Mike Hommey], [mailto:kaie@kuix.de Kai Engert]<br />
|group=dev-tech-nspr<br />
|source_dirs=nsprpub/<br />
|url=http://www.mozilla.org/projects/nspr/<br />
http://www.mozilla.org/projects/nspr/reference/html/<br />
http://www.mozilla.org/projects/nspr/release-notes/<br />
|components=NSPR<br />
}}<br />
<br />
{{Module<br />
|name=PDF<br />
|description=Rendering code to display documents encoded in the ISO 32000-1 `PDF' format.<br />
|owner=Chris Jones, Andreas Gal<br />
|peers=[mailto:aadib@mozilla.com Artur Adib], [mailto:bdahl@mozilla.com Brendan Dahl], [mailto:vnicolas@mozilla.com Vivien Nicolas]<br />
|group=dev-platform<br />
|source_dirs=media/pdf/<br />
|url=https://github.com/mozilla/pdf.js<br />
|components=Core::PDF<br />
}}<br />
<br />
{{Module<br />
|name=Plugins<br />
|description= NPAPI Plugin support.<br />
|owner=[mailto:jmathies@mozilla.com Jim Mathies]<br />
|peers=[mailto:jst@mozilla.org Johnny Stenback], [mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:joshmoz@gmail.com Josh Aas]<br />
|peersemeritus=[mailto:john@pointysoftware.net John Schoenick], [mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=<br />
|source_dirs=dom/plugins/, modules/plugin/<br />
|url=https://wiki.mozilla.org/Plugins<br />
|components=Core::Plug-ins<br />
}}<br />
<br />
{{Module<br />
|name=Preferences<br />
|description=Preference library<br />
|owner=<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-platform<br />
|source_dirs=modules/libpref/<br />
|url=<br />
|components=Core::Preferences: Backend<br />
}}<br />
<br />
{{Module<br />
|name=Private Browsing<br />
|description=Implementation of the Private Browsing mode, and the integration of other modules with Private Browsing APIs.<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:josh@joshmatthews.net Josh Matthews]<br />
|group=dev-platform<br />
|source_dirs=Implementation and consumers of Private Browsing APIs in nsILoadContext, nsIPrivateBrowsingChannel, PrivateBrowsingUtils.jsm and the related glue code. <br />
|url=https://wiki.mozilla.org/Private_Browsing<br />
|components=Firefox::Private Browsing<br />
}}<br />
<br />
{{Module<br />
|name=Privilege Manager<br />
|description="caps"<br />
|owner=[mailto:bobbyholley@gmail.com Bobby Holley]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dveditz@mozilla.com Dan Veditz], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-tech-dom<br />
|source_dirs=caps/<br />
|url=http://www.mozilla.org/projects/security/components/index.html<br />
|components=Core::Security: CAPS<br />
}}<br />
<br />
{{Module<br />
|name=Push Notifications<br />
|description=Push is a way for application developers to send messages to their web applications.<br />
|owners=<br />
|ownersemeritus=[mailto:doug.turner@gmail.com Doug Turner]<br />
|peers=[mailto:nsm.nikhil@gmail.com Nikhil Marathe], [mailto:kcambridge@mozilla.com Kit Cambridge], [mailto:martin.thomson@gmail.com Martin Thomson], [mailto:ddamjanovic@mozilla.com Dragana Damjanovic]<br />
|group=<br />
|source_dirs=dom/push, dom/simplepush<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=PyXPCOM<br />
|description=The Python to XPCOM bridge.<br />
|owner=Todd Whiteman<br />
|peers=[mailto:mhammond@skippinet.com.au Mark Hammond]<br />
|group=<br />
|source_dirs=extension/python<br />
|url=https://developer.mozilla.org/en/PyXPCOM<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=RDF<br />
|description=<br />
|owner=[mailto:axel@pike.org Axel Hecht]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-tech-rdf<br />
|source_dirs=rdf/<br />
|url=http://www.mozilla.org/rdf/doc/<br />
|components=Core::RDF<br />
}}<br />
<br />
{{Module<br />
|name=security<br />
|description=Crypto/PKI code, including NSS (Network Security Services) and JSS (NSS for Java)<br />
|owner=[mailto:rrelyea@redhat.com Bob Relyea], [mailto:ttaubert@mozilla.com Tim Taubert]<br />
|peers=[mailto:emaldona@redhat.com Elio Maldonado], [mailto:kaie@kuix.de Kai Engert], [mailto:ryan.sleevi@gmail.com Ryan Sleevi], [mailto:ekr@rtfm.com Eric Rescorla], [mailto:franziskuskiefer@gmail.com Franziskus Kiefer], [mailto:martin.thomson@gmail.com Martin Thomson], [mailto:wtc@google.com Wan-Teh Chang]<br />
|group=dev-tech-crypto<br />
|source_dirs=dbm/, security/coreconf/, security/dbm/, security/jss/, security/nss/, security/tinderbox/, security/tinderlight/<br />
|url=http://mozilla.org/projects/security/pki/<br />
|components=NSS, JSS, Core::Security, Core::Security: S/MIME<br />
}}<br />
<br />
{{Module<br />
|name=Security - Mozilla PSM Glue<br />
|description=Personal Security Manager<br />
|owner=[mailto:dkeeler@mozilla.com David Keeler]<br />
|peers=[mailto:honzab.moz@firemni.cz Honza Bambas], [mailto:cykesiopka.bmo@gmail.com Cykesiopka]<br />
|group=dev-tech-crypto<br />
|source_dirs=security/manager/<br />
|url=<br />
|components=Core::Security: PSM, Core::Security: UI<br />
}}<br />
<br />
{{Module<br />
|name=Static analysis & rewriting for C++<br />
|description=Tools for checking C++ code looking for problems at compile time, plus tools for automated rewriting of C++ code.<br />
|owner=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:sfink@mozilla.com Steve Fink], [mailto:michael@thelayzells.com Michael Layzell], [mailto:jrmuizel@mozilla.com Jeff Muizelaar], [mailto:birunthan@mohanathas.com Birunthan Mohanathas]<br />
|group=dev-platform<br />
|source_dirs=build/clang-plugin, tools/rewriting among other out of tree tools<br />
|url=<br />
|components=Core::Rewriting & Analysis<br />
}}<br />
{{Module<br />
|name=storage<br />
|description=Storage APIs with a SQLite backend<br />
|owner=[mailto:mak77@bonardo.net Marco Bonardo]<br />
|peers=[mailto:bugmail@asutherland.org Andrew Sutherland], [mailto:jvarga@mozilla.com Jan Varga]<br />
|group=dev-platform<br />
|source_dirs=db/sqlite3/, storage/<br />
|url=http://developer.mozilla.org/en/docs/Storage<br />
|components=Toolkit::Storage, Core::SQL<br />
}}<br />
<br />
{{Module<br />
|name=String<br />
|description=<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:jlebar@mozilla.com Justin Lebar]<br />
|group=dev-tech-xpcom<br />
|source_dirs=string/, xpcom/string/<br />
|url=https://developer.mozilla.org/En/Mozilla_internal_string_guide<br />
|components=Core::String<br />
}}<br />
<br />
{{Module<br />
|name=Style System<br />
|description=CSS style sheet handling; style data computation<br />
|owner=[mailto:dbaron@dbaron.org David Baron]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:cam@mcc.id.au Cameron McCormack]<br />
|group=dev-tech-layout<br />
|source_dirs=layout/style/<br />
|url=https://wiki.mozilla.org/Gecko:Overview#Style_System<br />
|components=Core::CSS Parsing and Computation<br />
}}<br />
<br />
{{Module<br />
|name=SVG<br />
|description=Scalable Vector Graphics<br />
|owner=[mailto:jwatt@jwatt.org Jonathan Watt]<br />
|peers=[mailto:longsonr@gmail.com Robert Longson], [mailto:robert@ocallahan.org Robert O'Callahan], [mailto:dholbert@mozilla.com Daniel Holbert], [mailto:birtles@gmail.com Brian Birtles]<br />
|group=dev-tech-svg<br />
|source_dirs=dom/svg/, layout/svg/, dom/smil/<br />
|url=https://developer.mozilla.org/en-US/docs/Web/SVG<br />
|components=Core::SVG<br />
}}<br />
<br />
{{Module<br />
|name=Tamarin<br />
|description=VM for ActionScript and JavaScript<br />
|owner=Edwin Smith, [mailto:jodyer@adobe.com Jeff Dyer]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:stejohns@adobe.com Steven Johnson], [mailto:tierney@adobe.com Erik Tierney], [mailto:treilly@adobe.com Tom Reilly]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/tamarin<br />
|url=http://www.mozilla.org/projects/tamarin/<br />
http://wiki.mozilla.org/tamarin/<br />
http://hg.mozilla.org/tamarin-central/<br />
http://hg.mozilla.org/tamarin-tracing/<br />
|components=Tamarin<br />
}}<br />
<br />
{{Module<br />
|name=Test Harness<br />
|description=In-tree test infrastructure and tools. Harnesses include, XPCShell, Mochitest (& Chrome), Reftest, JsREftest, Compiled Code Tests, Robocop, Mozmill, Marionette, Firefox UI Tests. Requests for new harnesses should go to Testing::General.<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:dbaron@dbaron.org David Baron] (reftest), [mailto:jwalden@mit.edu Jeff Walden] (httpd.js, jsreftest), Rob Campbell (mochitest, mochitest chrome, marionette), [mailto:jmaher@mozilla.com Joel Maher] (reftest, mochitest, jsreftest), [mailto:ctalbert@mozilla.com Clint Talbert] (reftest, compiled code, mozmill), [mailto:geoffbrown@mozilla.com Geoff Brown] (robocop), [mailto:hskupin@mozilla.com Henrik Skupin] (Marionette, Firefox UI tests), [mailto:ato@mozilla.com Andreas Tolfsen] (marionette), [mailto:jgriffin Jonathan Griffin] (marionette), [mailto:dburns@mozilla.com David Burns] (marionette) [mailto:dminor@mozilla.com Dan Minor], [mailto:mjzffr@gmail.com Maja Frydrychowicz] (Marionette, Firefox UI tests), <br />
<br />
|group=dev-quality<br />
|source_dirs=/testing<br />
|url=http://wiki.mozilla.org/SoftwareTesting<br />
|components=Testing::General, Testing::Mochitest, Testing::Mochitest Chrome, Testing::Marionette, Testing::Mozmill, Testing::Reftest, Testing::XPCShell Harness, Testing::httpd.js<br />
}}<br />
<br />
{{Module<br />
|name=Testing Infrastructure<br />
|description=Testing tools and infrastructure for Mozilla projects, harnesses for automated tests, stand-alone test tools. Talos, Graph Server, Mozbase, Pulse, WOO, Bughunter, SUTAgent, Eideticker<br />
|owner=[mailto:jmaher@mozilla.com Joel Maher]<br />
|peers=[mailto:bclary@bclary.com Bob Clary], [mailto:bhearsum@mozilla.com Ben Hearsum], [mailto:ccooper@deadsquid.com Chris Cooper], [mailto:ctalbert@mozilla.com Clint Talbert], [mailto:robert@roberthelmer.com Robert Helmer], [mailto:jmaher@mozilla.com Joel Maher], Rob Campbell, [mailto:wlach@mozilla.com William Lachance], [mailto:jeads@mozilla.com Jonathan Eads], [mailto:jgriffin Jonathan Griffin], [mailto:bmoss@mozilla.com Bob Moss], [mailto:mcote@mozilla.com Mark Côté]<br />
|group=dev-quality<br />
|source_dirs=testing/, tools/httptester/, tools/page-loader/, tools/test-harness/, tools/tests/, tools/testserver/, tools/testy/<br />
|url=http://wiki.mozilla.org/SoftwareTesting<br />
|components=Testing::Infrastructure<br />
}}<br />
<br />
{{Module<br />
|name=JS Marionette<br />
|description=NodeJS test harness, marionette client, and other utilities for running marionette tests (submodule of Test Infrastructure)<br />
|owner=[mailto:jlal@mozilla.com James Lal] <lightsofapollo>, [mailto:gaye@mozilla.com Gareth Aye] <gaye><br />
|peers=[mailto:aus@mozilla.com Ghislain "Aus" Lacroix] <auswerk><br />
|source_dirs=gaia/tests/jsmarionette<br />
|components=Testing::JSMarionette<br />
|group=dev-gaia<br />
}}<br />
<br />
{{Module<br />
|name=XPCShell Test Harness<br />
|description=The XPCShell Harness<br />
|owner=[mailto:ted@mielczarek.org Ted Mielczarek]<br />
|peers=[mailto:jmaher@mozilla.com Joel Maher]<br />
|source_dirs=testing/xpcshell<br />
|components=Testing::XPCShell Harness<br />
}}<br />
<br />
{{Module<br />
|name=Update Service<br />
|description=server code for Mozilla Update services (aus, addons, pfs)<br />
|owner=Mike Morgan<br />
|peers=[mailto:jscott@mozilla.com Justin Scott], [mailto:shaver@mozilla.org Mike Shaver], [mailto:wclouser@mozilla.com Will Clouser]<br />
|group=dev-amo<br />
|source_dirs=webtools/addons/, webtools/aus/, webtools/update/<br />
|url=http://wiki.mozilla.org/wiki/AMO<br />
|components=AUS::Administration, AUS::Systems<br />
}}<br />
<br />
{{Module<br />
|name=View System<br />
|description=The View Manager is responsible for handling "heavyweight" rendering (some clipping, compositing) and event handling tasks.<br />
|owner=[mailto:mstange@themasta.com Markus Stange]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:dbaron@dbaron.org David Baron]<br />
|group=dev-tech-layout<br />
|source_dirs=view/<br />
|url=<br />
|components=Core::Layout: View Rendering<br />
}}<br />
<br />
{{Module<br />
|name=Web Audio<br />
|description=Support for the W3C Web Audio API specification.<br />
|owner=[mailto:padenot@mozilla.com Paul Adenot]<br />
|ownersemeritus=[mailto:ehsan@mozilla.com Ehsan Akhgari]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:karlt+@karlt.net Karl Tomlinson]<br />
|group=dev-platform<br />
|source_dirs=dom/media/webaudio<br />
|url=https://wiki.mozilla.org/Web_Audio_API<br />
|components=Core::Web Audio<br />
}}<br />
<br />
{{Module<br />
|name=Web Painting<br />
|description=painting, display lists, and layer construction<br />
|owner=[mailto:matt.woodrow@gmail.com Matt Woodrow]<br />
|peers=[mailto:robert@ocallahan.org Robert O'Callahan], [mailto:dbaron@dbaron.org David Baron], [mailto:tnikkel@gmail.com Timothy Nikkel], [mailto:mstange@themasta.com Markus Stange]<br />
|group=dev-tech-layout<br />
|source_dirs= layout/painting, the display list and layer related methods on nsIFrame and its subclasses<br />
|url=http://mozilla.org/newlayout/doc/ ,<br />
http://lxr.mozilla.org/mozilla/source/layout/doc/<br />
|components=Core::Layout: Web Painting<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC<br />
|description=WebRTC is responsible for realtime audio and video communication, as well as related issues like low-level camera and microphone access<br />
|owner=[mailto:rjesup@mozilla.com Randell Jesup]<br />
|peers=[mailto:ekr@mozilla.com Eric Rescorla], [mailto:bcampen@mozilla.com Byron Campen] [mailto:abr@mozilla.com Adam Roach]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=N/A (see submodules "WebRTC Media" and "WebRTC Signaling")<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC<br />
}}<br />
<br />
{{Module<br />
|name=Widget<br />
|description=<br />
|owner=[mailto:vladimir@pobox.com Vladimir Vukicevic]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|peersemeritus=[mailto:pavlov@pavlov.net Stuart Parmenter], <br />
|group=dev-platform<br />
|source_dirs=widget/, widget/xpwidgets/<br />
|url=<br />
|components=Core::Drag and Drop, Core::Widget, Core::Printing: Setup<br />
}}<br />
<br />
{{Module<br />
|name=Widget - Android<br />
|description=The Android Port<br />
|owner=[mailto:blassey.bugs@lassey.us Brad Lassey]<br />
|peers=[mailto:jwillcox@mozilla.com James Willcox]<br />
|group=dev-platforms-mobile<br />
|source_dirs=widget/android/, embedding/android<br />
|url=<br />
|components=Core::Widget: Android<br />
}}<br />
<br />
{{Module<br />
|name=Widget - GTK<br />
|description=supported X widgetry and gfx<br />
|owner=[mailto:karlt+@karlt.net Karl Tomlinson]<br />
|ownersemeritus=[mailto:robert@ocallahan.org Robert O'Callahan]<br />
|group=dev-platform<br />
|source_dirs=widget/gtk/, widget/gtk2/, widget/gtksuperwin/, widget/gtkxtbin/<br />
|url=http://www.mozilla.org/unix/, http://www.gtk.org, http://www.mozilla.org/ports/gtk/<br />
|components=Core::Widget: Gtk<br />
}}<br />
<br />
{{Module<br />
|name=Widget - OS X<br />
|description= Gecko's OS X compatibility layer.<br />
|owner=[mailto:mstange@themasta.com Markus Stange]<br />
|peers=[mailto:joshmoz@gmail.com Josh Aas], [mailto:bgirard@mozilla.com Benoit Girard], [mailto:spohl@mozilla.com Stephen Pohl], [mailto:smichaud@pobox.com Steven Michaud]<br />
|group=dev-platform<br />
|source_dirs=widget/cocoa/<br />
|url=<br />
|components=Core::Widget: Cocoa<br />
}}<br />
<br />
{{Module<br />
|name=Widget - Windows<br />
|description=Windows widgets and desktop integration<br />
|owner=[mailto:jmathies@mozilla.com Jim Mathies]<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:vladimir@pobox.com Vladimir Vukicevic], [mailto:jmathies@mozilla.com Jim Mathies]<br />
|peersemeritus=[mailto:blassey@mozilla.com Brad Lassey], [mailto:netzen@gmail.com Brian Bondy], [mailto:cbiesinger@gmail.com Christian Biesinger], [mailto:doug.turner@gmail.com Doug Turner], [mailto:timeless@mozdev.org Josh 'timeless' Soref], [mailto:robarnold@cmu.edu Rob Arnold]<br />
|group=dev-platform<br />
|source_dirs=widget/windows/<br />
|url=<br />
|components=Core::Widget: Win32<br />
}}<br />
<br />
{{Module<br />
|name=XBL<br />
|description=eXtensible Binding Language<br />
|owner=[mailto:bzbarsky@mit.edu Boris Zbarsky]<br />
|peers=[mailto:mrbkap@gmail.com Blake Kaplan], [mailto:bobbyholley@gmail.com Bobby Holley], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|ownersemeritus=[mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xbl<br />
|source_dirs=dom/xbl/<br />
|url=http://www.mozilla.org/projects/xbl/<br />
|components=Core::XBL<br />
}}<br />
<br />
{{Module<br />
|name=XML<br />
|description=XML in Mozilla, including XML, XHTML, Namespaces in XML, Associating Style Sheets with XML Documents, XML Linking and XML Extras. XML-related things that are not covered by more specific projects.<br />
|owner=[mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking], [mailto:jst@mozilla.org Johnny Stenback]<br />
|group=dev-tech-xml<br />
|source_dirs=dom/xml/, extensions/xmlextras/, parser/expat/<br />
|url=http://www.mozilla.org/newlayout/xml/<br />
|components=Core::XML<br />
}}<br />
<br />
{{Module<br />
|name=XPApps<br />
|description=Cross-Platform Applications, mostly Navigator front end and application shell.<br />
|owner=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|peers=[mailto:dean_tessman@hotmail.com Dean Tessman], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-apps-seamonkey<br />
|source_dirs=xpfe/<br />
|url=http://www.mozilla.org/xpapps/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPCOM<br />
|description=The cross-platform object model and core data structures.<br />
|owner=[https://mozillians.org/en-US/u/froydnj/ Nathan Froyd]<br />
|peers=[https://mozillians.org/en-US/u/bsmedberg/ Benjamin Smedberg], [mailto:erahm@mozilla.com Eric Rahm]<br />
|peersemeritus=[https://mozillians.org/en-US/u/dougt/ Doug Turner]<br />
|group=dev-platform<br />
|source_dirs=startupcache/, xpcom/%, xpcom/base/, xpcom/build/, xpcom/components/, xpcom/ds/, xpcom/glue/, xpcom/proxy/, xpcom/sample/, xpcom/stub/, xpcom/tests/, xpcom/threads/, xpcom/tools/, xpcom/windbgdlg/<br />
|url=http://developer.mozilla.org/en/XPCOM<br />
|components=Core::XPCOM<br />
}}<br />
<br />
{{Module<br />
|name=XPConnect<br />
|description=Deep Magic<br />
|owner=[mailto:bobbyholley@gmail.com Bobby Holley]<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jst@mozilla.org Johnny Stenback], [mailto:peterv@propagandism.org Peter Van der Beken], [mailto:mrbkap@gmail.com Blake Kaplan], [mailto:gkrizsanits@mozilla.com Gabor Krizsanits]<br />
|peersemeritus=[mailto:gal@uci.edu Andreas Gal]<br />
|group=<br />
|source_dirs=js/xpconnect/<br />
|url=<br />
|components=Core::XPConnect<br />
}}<br />
<br />
{{Module<br />
|name=XPIDL<br />
|description=Cross-platform IDL compiler; produces .h C++ header files and .xpt runtime type description files from .idl interface description files.<br />
|owner=[mailto:me@kylehuey.com Kyle Huey]<br />
|peersemeritus=[mailto:shaver@mozilla.org Mike Shaver], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-tech-xpcom<br />
|source_dirs=xpcom/typelib/<br />
|url=http://www.mozilla.org/scriptable/xpidl<br />
http://www.mozilla.org/scriptable<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPInstall<br />
|description=<br />
|owner=[mailto:dveditz@mozilla.com Dan Veditz]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]<br />
|group=dev-tech-xpinstall<br />
|source_dirs=xpinstall/<br />
|url=<br />
|components=Core::Installer: XPInstall Engine<br />
}}<br />
<br />
{{Module<br />
|name=xptcall<br />
|description=XPTCall - platform-specific assembly for calling and implementing arbitrary XPCOM interfaces.<br />
|owner=<br />
|ownersemeritus=[mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:shaver@mozilla.org Mike Shaver]<br />
|group=dev-xpcom<br />
|source_dirs=xpcom/reflect/xptcall/<br />
|url=http://www.mozilla.org/scriptable/xptcall-faq.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=XPToolkit<br />
|description=Cross-platform user interface toolkit<br />
|owner=<br />
|peers=[mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:Jan.Varga@gmail.com Jan Varga]<br />
|group=dev-tech-xul<br />
|source_dirs=dom/xul/, layout/xul/<br />
|url=http://www.mozilla.org/xpfe/<br />
|components=Core::XP Toolkit/Widgets: Menus, Core::XP Toolkit/Widgets: XUL<br />
}}<br />
<br />
{{Module<br />
|name=XSLT Processor<br />
|description=XSLT transformations processor<br />
|owner=[mailto:peterv@propagandism.org Peter Van der Beken]<br />
|peers=[mailto:axel@pike.org Axel Hecht], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xslt<br />
|source_dirs=dom/xslt/<br />
|url=http://www.mozilla.org/projects/xslt/, http://www.w3.org/TR/xslt.html<br />
|components=Core::XSLT<br />
}}<br />
<br />
{{Module<br />
|name=XTF<br />
|description=eXtensible Tag Framework<br />
|owner=<br />
|peers=[mailto:alex@croczilla.com alex@croczilla.com], [mailto:bzbarsky@mit.edu Boris Zbarsky], [mailto:jonas@sicking.cc Jonas Sicking]<br />
|group=dev-tech-xbl<br />
|source_dirs=content/xtf/, layout/xtf/<br />
|url=http://www.croczilla.com/bits_and_pieces/xtf/<br />
|components=Core::XTF<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing<br />
|description=Cross platform sandboxing<br />
|owner=[mailto:gcp@mozilla.com Gian-Carlo Pascutto]<br />
|peers=[mailto:bowen@mozilla.com Bob Owen], [mailto:aklotz@mozilla.com Aaron Klotz], [https://mozillians.org/en-US/u/TimAbraldes Tim Abraldes], [mailto:gDestuynder@mozilla.com Guillaume Destuynder], [mailto:bsmedberg@mozilla.com Benjamin Smedberg], [mailto:jld@mozilla.com Jed Davis]<br />
|group=dev-platform <br />
|source_dirs=security/sandbox<br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - Windows <br />
|description=Sandboxing for the Windows platform <br />
|owner=[mailto:bowen@mozilla.com Bob Owen]<br />
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:aklotz@mozilla.com Aaron Klotz], [https://mozillians.org/en-US/u/TimAbraldes Tim Abraldes], [mailto:jimm@mozilla.com Jim Mathies]<br />
|group=dev-platform<br />
|source_dirs=security/sandbox/win <br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - OSX <br />
|description=Sandboxing for the OSX platform <br />
|owner=[mailto:haftandilian@mozilla.com Haik Aftandilian]<br />
|peers=<br />
|group=dev-platform <br />
|source_dirs=security/sandbox/mac <br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
{{Module<br />
|name=Sandboxing - Linux & B2G<br />
|description=Sandboxing for the Linux & B2G platforms<br />
|owner=[mailto:jhector@mozilla.com Julian Hector]<br />
|peers=[mailto:jld@mozilla.com Jed Davis] [mailto:gcp@mozilla.com Gian-Carlo Pascutto]<br />
|group=dev-platform<br />
|source_dirs=security/sandbox/linux<br />
|url=https://wiki.mozilla.org/Security/Sandbox <br />
|components=Core::Security: Process Sandboxing<br />
}}<br />
<br />
===Submodules===<br />
{{Module<br />
|name=Build Config - Fennec<br />
|description=Submodule of the build config covering Fennec's build system in mobile/android.<br />
|owner=[mailto:nalexander@mozilla.com Nicholas Alexander]<br />
|peers=Same as Build Config<br />
|group=dev-builds<br />
|components=Core::Build Config<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC Media<br />
|description=Submodule of WebRTC responsible for access to media input devices (microphones, cameras, screen capture), as well as realtime audiovisual codecs and packetization.<br />
|owner=[mailto:rjesup@mozilla.com Randell Jesup]<br />
|peers=[mailto:pkerr@mozilla.com Paul Kerr], [mailto:jib@mozilla.com Jan-Ivar Bruaroey]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=/media/webrtc, /dom/media/webrtc<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC (Audio/Video)<br />
}}<br />
<br />
{{Module<br />
|name=WebRTC Signaling<br />
|description=Submodule of WebRTC responsible for implementation of PeerConnection API, WebRTC identity, and SDP/JSEP handling<br />
|owner=[mailto:bcampen@mozilla.com Byron Campen]<br />
|peers=[mailto:ekr@mozilla.com Eric Rescorla], [mailto:abr@mozilla.com Adam Roach], [mailto:rjesup@mozilla.com Randell Jesup], [mailto:nohlmeier@mozilla.com Nils Ohlmeier]<br />
|peersemeritus=[mailto:ehugg@cisco.com Ethan Hugg]<br />
|group=dev-media<br />
|source_dirs=/media/webrtc/signaling/<br />
|url=https://wiki.mozilla.org/Media/webrtc<br />
|components=Core::WebRTC (Signaling)<br />
}}<br />
<br />
<br />
<noinclude><br />
<br />
===Unassigned Bugzilla Components===<br />
<br />
The following Bugzilla components in the Core project have not been assigned to a module (this list is not exhaustive):<br />
<br />
<pre><br />
Core::File Handling<br />
Core::Find Backend<br />
Core::Gecko Profiler<br />
Core::General<br />
Core::HTML: Form Submission<br />
Core::History: Global<br />
Core::Image Blocking<br />
Core::JavaScript Debugging APIs<br />
Core::Localization<br />
Core::Nanojit<br />
Core::Networking: Domain Lists<br />
Core::Print Preview<br />
Core::Printing: Output<br />
Core::Printing: Setup<br />
Core::Profile: BackEnd<br />
Core::Profile: Migration<br />
Core::Profile: Roaming<br />
Core::QuickLaunch (AKA turbo mode)<br />
Core::Rewriting and Analysis<br />
Core::Selection<br />
Core::Serializers<br />
Core::Spelling checker<br />
Core::Tracking<br />
Core::Web Services<br />
Core::WebDAV<br />
Core::Widget: OS/2<br />
Core::Widget: Photon<br />
Core::X-remote<br />
Core::XForms<br />
Core::XUL<br />
</pre><br />
</noinclude></div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub&diff=1157710GitHub2016-12-22T17:42:10Z<p>MykMelez: remove redundant and obsolete reference to 2FA requirement</p>
<hr />
<div>This page is specifically about [https://github.com/mozilla the "mozilla" organization on github]. There are several other github organizations you may be interested in, cf. the incomplete list [[#other_github|below]].<br />
<div id="contact"><br />
{| class="wikitable"<br />
|-<br />
! [[File:Red_question_mark.png|144px|Send us an email!|link=]] Got a question?<br />
|-<br />
| Email {{emailentry|github-owners|mozilla.org|at=is}} <br /><br />
Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& mozilla.org :: Github: Administration] <br /><br />
irc #github on [[IRC|moznet]]<br />
|}<br />
<br />
== News ==<br />
* As of June 20, 2016, all members [https://groups.google.com/forum/#!topic/mozilla.dev.platform/UmHOOh3qtiM must have 2FA enabled]. You have been notified if this impacts you.<br />
<br />
== Recommendations and FAQ ==<br />
<br />
=== Where should I ask additional questions? ===<br />
* Send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and we'll respond right away! We're also available on #github on irc.<br />
<br />
=== How do I hook up a new 3rd party application to a repository in the mozilla org? ===<br />
{{note|There are now multiple 3rd pary application types. "Integrations" are the new approach and preferred.|gotcha}}<br />
<br />
3rd party applications can easily impact many other repositories than the initial one. For that reason, the following steps are strongly encouraged. Note that there are three ways 3rd party apps can be associated with the entire organization, or a specific repository:<br />
# via a manually configured webhook. This type of installation is not automatically affected by the other approaches.<br />
# via an "Integration", which is connected by "Installing" it into the target. (This is the new, preferred way.)<br />
# via granting access via OAUTH tied to the installer's credentials. (The old way.)<br />
<br />
==== Integrations ====<br />
<br />
Integrations are "Installed" into either the entire organization, or into individual repositories, and are not tied to the permissions of the user who does the installation. Each integration has a documented, granular, access to various of the repository resources. This is good.<br />
<br />
However, the installation can only be done by an organization owner, who may have to do additional housekeeping. This is not so good, so please plan accordingly (you may need to coordinate with [[#contact|GitHub owners]]).<br />
<br />
===== Initial Installation =====<br />
If this is the first time this Integration is being installed in the organization, a few extra checks and coordination are needed. An organization owner will need to perform these steps:<br />
* Determine if the integration previously had an OAUTH version.<br />
** If so, it is likely that installing the integration will disable all repositories in the organization using the OAUTH version of the application.<br />
** Find all current repositories using the classic OAUTH application (this is non-trivial, scripts exist to help)<br />
** Install the Integration for all current repositories, and the new one (organization owner permissions needed.)<br />
<br />
**Please do not install integrations with organization wide scope without first discussing with [[#contact|GitHub owners]].**<br />
<br />
===== Additional Installations or Removals =====<br />
If the integration has already been installed in the organization, the new repository simply needs to be added or removed from the list. An organization owner has to make this change.<br />
<br />
==== OAUTH (classic) Applications ====<br />
# Create yourself a new github user for this repository.<br />
# Make them an admin of the repository(s) temporarily.<br />
# Sign in as the new github user and setup the 3rd party application.<br />
# Log back into your normal account.<br />
# Try to reduce access of that user from an admin of the repository(s) to read only access.<br />
# If (5) doesn't work, at least the 3rd party application will not have access to all of your normal github account's (including private repositories).<br />
<br />
* Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a "Request access" button during the set up flow. You'll need to click that button to request approval. See below for an example:<br />
<br />
<br />
[[File:github_approval.png]]<br />
<br />
* In some cases, the application does not need to be "approved" to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)<br />
<br />
* In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, it is helpful to send the details to the owner's team, either by [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& opening a bug] or [[#contact|email]].<br />
<br />
=== Reviewing owners and permissions ===<br />
As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.<br />
<br />
=== Can I be an Owner of the Mozilla Organization? ===<br />
The Owners group on GitHub has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner, they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.<br />
<br />
=== Can I be a Member of the Mozilla Organization? ===<br />
<div id="join"> </div><br />
==== Contributor Information ====<br />
Good news! You do not need to be a member of the Mozilla organization on GitHub before you can contribute to Mozilla!!!! We have several sites which can help you find the best fit for contribution:<br />
* General [https://www.mozilla.org/en-US/contribute/ volunteering options],<br />
* Or pick from [http://whatcanidoformozilla.org/ these areas],<br />
* Or jump right into [http://www.joshmatthews.net/bugsahoy/ fixing a bug].<br />
* If you're already a contributor (THANK YOU!) looking for a place to have your work recognized (even if not coding related), please see the [https://www.mozilla.org/credits/FAQ Credits FAQ] for inclusion in the [https://www.mozilla.org/credits/ credits].<br />
<br />
Once you're working on a project, the project leaders can help you get access to anything you need.<br />
<br />
==== Team Maintainers & Project Leads ====<br />
<br />
Project owners and team maintainers may find the following information helpful when asking for access for a new team member:<br />
<br />
*With recent GitHub enhancements (2015), we encourage the following (rough) guidelines, which strongly prefers using github teams. As a reminder, all members of the [https://github.com/mozilla/ Mozilla organization on github] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical.<br />
** "Outside Collaborator": repository admins can grant outside collaborator to any GitHub account. "Outside Collaborator" is roughly analogous to "Level 1a" access to Mozilla-hosted repositories.<br />
** "Team Member": team maintainers can add GitHub users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [[#contact|request your addition]] to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.<br />
<br />
{{note| As of June 30, 2016, all members of the Mozilla organization on github '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].|reminder}}<br />
<br />
{{note| Automation accounts are also required to have 2FA enabled. Scripts should use [https://help.github.com/articles/creating-an-access-token-for-command-line-use/ access tokens] with minimum permissions to accomplish the task.}}<br />
<br />
The best way to ask for a Contributor to be invited to the organization is to [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& open a bug] including the contributor's GitHub login, and the team(s) they need access to.<br />
<br />
=== Should I make a separate github organization or just create a repository in an existing one? ===<br />
This is a personal preference. If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details.<br />
<br />
=== Forking vs Transferring ===<br />
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.<br />
<br />
If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:<br />
<br />
{{note|As soon as you transfer, your repository will be in "limbo" (only you will have write access) until you get the assistance of an [[#contact|org admin]] who can make the changes. Please plan in advance if timing is critical.}}<br />
<br />
# If you're not a member of any team, talk to an [[#contact|org admin]].<br />
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.<br />
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.<br />
# Ask an [[#contact|org admin]] to grant team permissions higher than read ('write' and 'admin' are the other choices). (Team maintainers do not have the ability to change a repositories status.)<br />
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on GitHub (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)<br />
<br />
=== Do I need to be an owner to create repositories? ===<br />
No. If a person has read/write access to another repository in that organization they can make more repositories in that organization. However, it's preferred that you create repositories in the context of a team. Teams are created [https://github.com/orgs/mozilla/teams here], if necessary. Once you have created a repo, you can configure it to give rights to members of particular teams.<br />
<br />
=== Are there requirements for when or how I should create a new team? ===<br />
No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).<br />
<br />
On large teams we recommend you separate teams for read/write and repository administration.<br />
<br />
<div id="other_github"></div><br />
=== Is "mozilla" the only github "organization" related to Mozilla? ===<br />
No, there are plenty of Mozilla-related "organizations" on github. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:<br />
{| class="wikitable sortable"<br />
|-<br />
! Organization !! Description !! Contact Owner<br />
|-<br />
| [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || ?<br />
|-<br />
|[https://github.com/mozillabrasil mozillabrasil] || Mozilla Brazil|| ?<br />
|-<br />
| [https://github.com/bugzilla bugzilla] || Bugzilla (the product, not bugzilla.mozilla.org) || #bugzilla<br />
|- <br />
| [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?<br />
|-<br />
| [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?<br />
|-<br />
| [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?<br />
|-<br />
| [https://github.com/mdn mdn] || Mozilla Developer Network || [https://github.com/jwhitlock John Whitlock]<br />
|-<br />
| [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?<br />
|-<br />
| [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?<br />
|-<br />
| [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?<br />
|-<br />
| [https://github.com/mozilla-bteam mozilla-bteam] || Bugzilla.Mozilla.org || #bteam<br />
|-<br />
| [https://github.com/mozilla-cit mozilla-cit] || Mozilla Community Ops || {{Mozillians|tanner|Tanner Filip}} or {{Mozillians|yalam96|Yousef Alam}}<br />
|-<br />
| [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?<br />
|-<br />
| [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?<br />
|-<br />
| [https://github.com/mozilla-iam mozilla-iam] || Mozilla's identity and access management || ?<br />
|-<br />
| [https://github.com/mozilla-platform-ops mozilla-platform-ops] || Mozilla Platform Operations || [[Platform_Operations]]<br />
|-<br />
| [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?<br />
|-<br />
| [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}<br />
|-<br />
| [https://github.com/mozilla-releng mozilla-releng] || Mozilla Release Engineering || #releng<br />
|-<br />
| [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-services owners]<br />
|-<br />
| [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}<br />
|-<br />
| [https://github.com/MozillaTW MozillaTW] || Mozilla Taiwan || ?<br />
|-<br />
| [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?<br />
|-<br />
| [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?<br />
|-<br />
| [https://github.com/MozillaScience MozillaScience] || Mozilla Science Lab || ?<br />
|-<br />
| [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?<br />
|-<br />
| [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}<br />
|-<br />
| [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || {{Mozillian|bclark|Brian Clark}}, {{Mozillian|shobson|Stephanie Hobson}}<br />
|-<br />
| [https://github.com/mozfr mozfr] || Mozilla Francophone || Pascal Chevrel https://mozillians.org/fr/u/pascalc/<br />
|-<br />
| [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?<br />
|-<br />
| [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}<br />
|-<br />
| [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, Jack Moffitt<br />
|-<br />
| [https://github.com/tabulapdf tabulapdf] || Tabula project (extract data from PDF files) || ?<br />
|-<br />
| [https://github.com/webcompat webcompat] || Web Compatibility Team || {{Mozillian|miketaylr|Mike Taylor}}<br />
|-<br />
| [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Pascal Chevrel https://mozillians.org/fr/u/pascalc/<br />
|-<br />
| [https://github.com/taskcluster taskcluster] || [[TaskCluster]] Team || [https://github.com/gregarndt Greg Arndt]<br />
|-<br />
| [https://github.com/MozillaCH MozillaCH] || Mozilla [[Switzerland]] || {{Mozillian|mkohler|Michael Kohler}}, {{Mozillian|freaktechnik|freaktechnik}}<br />
|-<br />
| [https://github.com/mozmar mozmar] || Mozilla [[Marketing]] || {{Mozillian|bensternthal|Benjamin Sternthal}}, {{Mozillian|pmac|Paul McLanahan}}<br />
|-<br />
| [https://github.com/mozilla-payments mozilla-payments] || Implementation of Web Payment APIs || {{Mozillian|Marcos Caceres}}<br />
|}<br />
<br />
=== Are there other unofficial or Mozilla-related repositories hosted on Github? ===<br />
Why, yes! In no particular order:<br />
<br />
* [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer<br />
* [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.<br />
* [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.<br />
* [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters<br />
* [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler<br />
* [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology<br />
* [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.<br />
* [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.<br />
* [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications<br />
* [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests<br />
* [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.<br />
* [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)<br />
* [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.<br />
* [https://github.com/jeffbryner/MozDef https://github.com/jeffbryner/MozDef]: Mozilla Defense Platform.<br />
* [https://github.com/jgraham/webdriver-rust https://github.com/jgraham/webdriver-rust]: WebDriver library for Rust.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates&diff=1149300WeeklyUpdates2016-09-26T18:16:12Z<p>MykMelez: add entry for September 26, 2016</p>
<hr />
<div>:''These updates concern Mozilla as a whole. For the weekly Firefox meetings, see [[Firefox/DeliveryMeetings]], for Gecko progress, see [[Platform#Meeting_Notes]].''<br />
<br />
==Meeting Details==<br />
*Every Monday @ 11:00am Pacific Time (19:00 BST) <br />
*Mozilla HQ, Ten Forward commons area <br />
{{conf|8600}}<br />
*http://air.mozilla.org/ to watch and listen <br />
*join irc.mozilla.org #airmozilla for backchannel discussion<br />
*'''Presenters only''': Vidyo room "Brownbags". Do ''not'' use this room if you're not planning to speak.<br />
<br />
'''Agenda:''' [[WeeklyUpdates/{{#time: Y-m-d | monday}}|Next Week's Agenda]]<br />
<br />
When you call in, you'll be muted by default, to keep phone noise down. Use "*1" (including the star) to unmute yourself if you want to say something. <br />
<br />
Full notes below. <!-- See https://wiki.mozilla.org/WeeklyUpdates/Template for create new page --><br />
<br />
==Meeting Notes==<br />
[[Template:WeeklyUpdates]] - <nowiki>{{subst:WeeklyUpdates}}</nowiki><br />
<!--*[[WeeklyUpdates/Template]]--><br />
<br />
Create a new weekly agenda from the [[Template:WeeklyUpdates|template]]:<br />
<createbox><br />
align=left<br />
type=create<br />
preload=Template:WeeklyUpdates<br />
default={{#time: Y-m-d | monday}}<br />
prefix=WeeklyUpdates/<br />
</createbox><br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2016 <br />
|-<br />
|<br />
* [[WeeklyUpdates/2016-09-26|September 26th, 2016]]<br />
* [[WeeklyUpdates/2016-09-19|September 19th, 2016]]<br />
* [[WeeklyUpdates/2016-09-12|September 12th, 2016]]<br />
* There was no meeting on September 5 because of the US Labor Day holiday.<br />
* [[WeeklyUpdates/2016-08-29|August 29nd, 2016]]<br />
* [[WeeklyUpdates/2016-08-22|August 22nd, 2016]]<br />
* [[WeeklyUpdates/2016-08-15|August 15th, 2016]]<br />
* [[WeeklyUpdates/2016-08-08|August 8th, 2016]]<br />
* [[WeeklyUpdates/2016-08-01|August 1st, 2016]]<br />
* [[WeeklyUpdates/2016-07-25|July 25th, 2016]]<br />
* [[WeeklyUpdates/2016-07-18|July 18th, 2016]]<br />
* [[WeeklyUpdates/2016-07-11|July 11th, 2016]]<br />
* [[WeeklyUpdates/2016-06-27|June 27th, 2016]]<br />
* [[WeeklyUpdates/2016-06-20|June 20th, 2016]]<br />
* [[WeeklyUpdates/2016-06-06|June 6th, 2016]]<br />
* [[WeeklyUpdates/2016-05-23|May 23rd, 2016]]<br />
* [[WeeklyUpdates/2016-05-16|May 16th, 2016]]<br />
* [[WeeklyUpdates/2016-05-09|May 9th, 2016]]<br />
* [[WeeklyUpdates/2016-05-02|May 2nd, 2016]]<br />
* [[WeeklyUpdates/2016-04-25|April 25th, 2016]]<br />
* [[WeeklyUpdates/2016-04-18|April 18th, 2016]]<br />
* [[WeeklyUpdates/2016-04-11|April 11th, 2016]]<br />
* [[WeeklyUpdates/2016-04-04|April 4th, 2016]]<br />
* [[WeeklyUpdates/2016-03-28|March 28th, 2016]]<br />
* [[WeeklyUpdates/2016-03-21|March 21st, 2016]]<br />
* [[WeeklyUpdates/2016-03-14|March 14th, 2016]]<br />
* [[WeeklyUpdates/2016-03-07|March 7th, 2016]]<br />
* [[WeeklyUpdates/2016-02-29|February 29th, 2016]]<br />
* [[WeeklyUpdates/2016-02-22|February 22nd, 2016]]<br />
* [[WeeklyUpdates/2016-02-15|February 15th, 2016]] (no live meeting due to [https://en.wikipedia.org/wiki/Washington's_Birthday Washington's Birthday] Holiday in the US.)<br />
* [[WeeklyUpdates/2016-02-08|February 8th, 2016]]<br />
* [[WeeklyUpdates/2016-02-01|February 1st, 2016]]<br />
* [[WeeklyUpdates/2016-01-25|January 25th, 2016]]<br />
* [[WeeklyUpdates/2016-01-11|January 11th, 2016]]<br />
* [[WeeklyUpdates/2016-01-04|January 4th, 2016]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* [[WeeklyUpdates/2015-12-28|December 28th, 2015]] (no meeting, just announcements)<br />
* December 21st (no meeting)<br />
* [[WeeklyUpdates/2015-12-14|December 14th, 2015]] (no live meeting due to All Hands recovery)<br />
* December 7th (no meeting due to All Hands)<br />
* [[WeeklyUpdates/2015-11-30|November 30th, 2015]]<br />
* [[WeeklyUpdates/2015-11-23|November 23rd, 2015]]<br />
* [[WeeklyUpdates/2015-11-16|November 16th, 2015]]<br />
* [[WeeklyUpdates/2015-11-09|November 9th, 2015]]<br />
* [[WeeklyUpdates/2015-11-02|November 2nd, 2015]]<br />
* [[WeeklyUpdates/2015-10-26|October 26th, 2015]]<br />
* [[WeeklyUpdates/2015-10-19|October 19th, 2015]]<br />
* [[WeeklyUpdates/2015-10-12|October 12th, 2015]]<br />
* [[WeeklyUpdates/2015-10-05|October 5th, 2015]]<br />
* [[WeeklyUpdates/2015-09-28|September 28th, 2015]]<br />
* [[WeeklyUpdates/2015-09-21|September 21st, 2015]]<br />
* [[WeeklyUpdates/2015-09-14|September 14th, 2015]]<br />
* September 7th (No meeting due to Labor Day)<br />
* [[WeeklyUpdates/2015-08-31|August 31st, 2015]]<br />
* [[WeeklyUpdates/2015-08-24|August 24th, 2015]]<br />
* [[WeeklyUpdates/2015-08-17|August 17th, 2015]]<br />
* [[WeeklyUpdates/2015-08-10|August 10th, 2015]]<br />
* [[WeeklyUpdates/2015-08-03|August 3rd, 2015]]<br />
* [[WeeklyUpdates/2015-07-27|July 27th, 2015]]<br />
* [[WeeklyUpdates/2015-07-20|July 20th, 2015]]<br />
* [[WeeklyUpdates/2015-07-13|July 13th, 2015]]<br />
* [[WeeklyUpdates/2015-07-06|July 6th, 2015]]<br />
* [[WeeklyUpdates/2015-06-29|June 29th, 2015]]<br />
* June 22nd, 2015 (no meeting due to All-Hands travel)<br />
* [[WeeklyUpdates/2015-06-15|June 15th, 2015]]<br />
* [[WeeklyUpdates/2015-06-08|June 8th, 2015]]<br />
* [[WeeklyUpdates/2015-06-01|June 1st, 2015]]<br />
* May 25th, 2015 (no meeting due to US Holiday)<br />
* [[WeeklyUpdates/2015-05-18|May 18th, 2015]]<br />
* [[WeeklyUpdates/2015-05-11|May 11th, 2015]]<br />
* [[WeeklyUpdates/2015-05-04|May 4th, 2015]]<br />
* [[WeeklyUpdates/2015-04-27|April 27th, 2015]]<br />
* [[WeeklyUpdates/2015-04-20|April 20th, 2015]]<br />
* [[WeeklyUpdates/2015-04-13|April 13th, 2015]]<br />
* [[WeeklyUpdates/2015-04-06|April 6th, 2015]]<br />
* [[WeeklyUpdates/2015-03-30|March 30th, 2015]]<br />
* [[WeeklyUpdates/2015-03-23|March 23rd, 2015]]<br />
* [[WeeklyUpdates/2015-03-16|March 16th, 2015]]<br />
* [[WeeklyUpdates/2015-03-09|March 9th, 2015]]<br />
* [[WeeklyUpdates/2015-03-02|March 2nd, 2015]]<br />
* [[WeeklyUpdates/2015-02-23|February 23rd, 2015]]<br />
* Feb 16th No meeting due to US Holiday<br />
* [[WeeklyUpdates/2015-02-09|February 9nd, 2015]]<br />
* [[WeeklyUpdates/2015-02-02|February 2nd, 2015]]<br />
* [[WeeklyUpdates/2015-01-26|January 26th, 2015]]<br />
* [[WeeklyUpdates/2015-01-19|January 19th, 2015]]<br />
* [[WeeklyUpdates/2015-01-12|January 12th, 2015]]<br />
* [[WeeklyUpdates/2015-01-05|January 5th, 2015]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2014<br />
|-<br />
|<br />
*[[WeeklyUpdates/2014-12-29|December 29th, 2014]]<br />
*[[WeeklyUpdates/2014-12-15|December 15th, 2014]]<br />
*[[WeeklyUpdates/2014-12-08|December 8th, 2014]]<br />
*[[WeeklyUpdates/2014-11-24|November 24th, 2014]]<br />
*[[WeeklyUpdates/2014-11-17|November 17th, 2014]]<br />
*[[WeeklyUpdates/2014-11-10|November 10th, 2014]]<br />
*[[WeeklyUpdates/2014-11-03|November 3rd, 2014]]<br />
*[[WeeklyUpdates/2014-10-27|October 27th, 2014]]<br />
*[[WeeklyUpdates/2014-10-20|October 20th, 2014]]<br />
*[[WeeklyUpdates/2014-10-13|October 13th, 2014]]<br />
*[[WeeklyUpdates/2014-10-06|October 6th, 2014]]<br />
*[[WeeklyUpdates/2014-09-29|September 29th, 2014]]<br />
*[[WeeklyUpdates/2014-09-22|September 22th, 2014]]<br />
*[[WeeklyUpdates/2014-09-15|September 15th, 2014]]<br />
*[[WeeklyUpdates/2014-09-08|September 8th, 2014]]<br />
*[[WeeklyUpdates/2014-09-01|September 1st, 2014]]<br />
*[[WeeklyUpdates/2014-08-25|August 25, 2014]]<br />
*[[WeeklyUpdates/2014-08-18|August 18, 2014]]<br />
*[[WeeklyUpdates/2014-08-11|August 11, 2014]]<br />
*[[WeeklyUpdates/2014-08-04|August 4, 2014]]<br />
*[[WeeklyUpdates/2014-07-28|July 28, 2014]]<br />
*[[WeeklyUpdates/2014-07-21|July 21, 2014]]<br />
*[[WeeklyUpdates/2014-07-14|July 14, 2014]]<br />
*[[WeeklyUpdates/2014-07-07|July 7, 2014]]<br />
*[[WeeklyUpdates/2014-06-30|June 30, 2014]]<br />
*[[WeeklyUpdates/2014-06-23|June 23, 2014]]<br />
*[[WeeklyUpdates/2014-06-16|June 16, 2014]]<br />
*[[WeeklyUpdates/2014-06-09|June 09, 2014]]<br />
*[[WeeklyUpdates/2014-06-02|June 02, 2014]]<br />
*[[WeeklyUpdates/2014-05-26|May 26, 2014]]<br />
*[[WeeklyUpdates/2014-05-19|May 19, 2014]]<br />
*[[WeeklyUpdates/2014-05-12|May 12, 2014]]<br />
*[[WeeklyUpdates/2014-05-05|May 05, 2014]]<br />
*[[WeeklyUpdates/2014-04-28|April 28, 2014]]<br />
*[[WeeklyUpdates/2014-04-21|April 21, 2014]]<br />
*[[WeeklyUpdates/2014-04-14|April 14, 2014]]<br />
*[[WeeklyUpdates/2014-04-07|April 7, 2014]]<br />
*[[WeeklyUpdates/2014-03-31|March 31, 2014]]<br />
*[[WeeklyUpdates/2014-03-24|March 24, 2014]]<br />
*[[WeeklyUpdates/2014-03-17|March 17, 2014]]<br />
*[[WeeklyUpdates/2014-03-10|March 10, 2014]]<br />
*[[WeeklyUpdates/2014-03-03|March 3, 2014]]<br />
*[[WeeklyUpdates/2014-02-24|February 24, 2014]]<br />
*[[WeeklyUpdates/2014-02-10|February 10, 2014]]<br />
*[[WeeklyUpdates/2014-02-03|February 3, 2014]]<br />
*[[WeeklyUpdates/2014-01-27|January 27, 2014]]<br />
*[[WeeklyUpdates/2014-01-20|January 20, 2014]]<br />
*[[WeeklyUpdates/2014-01-13|January 13, 2014]]<br />
*[[WeeklyUpdates/2014-01-06|January 6, 2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2013 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2013-12-16|December 16, 2013]]<br />
*[[WeeklyUpdates/2013-12-09|December 9, 2013]]<br />
*[[WeeklyUpdates/2013-12-02|December 2, 2013]]<br />
*[[WeeklyUpdates/2013-11-25|November 25, 2013]]<br />
*[[WeeklyUpdates/2013-11-18|November 18, 2013]]<br />
*[[WeeklyUpdates/2013-11-11|November 11, 2013]]<br />
*[[WeeklyUpdates/2013-11-04|November 4, 2013]]<br />
*[[WeeklyUpdates/2013-10-28|October 28, 2013]]<br />
*[[WeeklyUpdates/2013-10-21|October 21, 2013]]<br />
*[[WeeklyUpdates/2013-10-14|October 14, 2013]]<br />
*[[WeeklyUpdates/2013-10-07|October 7, 2013]]<br />
*[[WeeklyUpdates/2013-09-30|September 30, 2013]]<br />
*[[WeeklyUpdates/2013-09-23|September 23, 2013]]<br />
*[[WeeklyUpdates/2013-09-16|September 16, 2013]]<br />
*[[WeeklyUpdates/2013-09-09|September 9, 2013]]<br />
*[[WeeklyUpdates/2013-09-02|September 2, 2013]]<br />
*[[WeeklyUpdates/2013-08-26|August 26, 2013]]<br />
*[[WeeklyUpdates/2013-08-19|August 19, 2013]]<br />
*[[WeeklyUpdates/2013-08-12|August 12, 2013]]<br />
*[[WeeklyUpdates/2013-08-05|August 5, 2013]]<br />
*[[WeeklyUpdates/2013-07-29|July 29, 2013]]<br />
*[[WeeklyUpdates/2013-07-22|July 22, 2013]]<br />
*[[WeeklyUpdates/2013-07-15|July 15, 2013]]<br />
*[[WeeklyUpdates/2013-07-08|July 8, 2013]]<br />
*[[WeeklyUpdates/2013-07-01|July 1, 2013]]<br />
*[[WeeklyUpdates/2013-06-24|June 24, 2013]]<br />
*[[WeeklyUpdates/2013-06-17|June 17, 2013]]<br />
*[[WeeklyUpdates/2013-06-10|June 10, 2013]]<br />
*[[WeeklyUpdates/2013-06-03|June 3, 2013]]<br />
*[[WeeklyUpdates/2013-05-20|May 20, 2013]]<br />
*[[WeeklyUpdates/2013-05-13|May 13, 2013]]<br />
*[[WeeklyUpdates/2013-05-06|May 6, 2013]]<br />
*[[WeeklyUpdates/2013-04-29|April 29, 2013]]<br />
*[[WeeklyUpdates/2013-04-22|April 22, 2013]]<br />
*[[WeeklyUpdates/2013-04-15|April 15, 2013]]<br />
*[[WeeklyUpdates/2013-04-08|April 8, 2013]]<br />
*[[WeeklyUpdates/2013-04-01|April 1, 2013]]<br />
*[[WeeklyUpdates/2013-03-25|March 25, 2013]]<br />
*[[WeeklyUpdates/2013-03-18|March 18, 2013]]<br />
*[[WeeklyUpdates/2013-03-11|March 11, 2013]]<br />
*[[WeeklyUpdates/2013-03-04|March 4, 2013]]<br />
*[[WeeklyUpdates/2013-02-25|February 25, 2013]]<br />
*February 18, 2013 - ''No meeting.'' <br />
*[[WeeklyUpdates/2013-02-11|February 11, 2013]]<br />
*[[WeeklyUpdates/2013-02-04|February 04, 2013]]<br />
*[[WeeklyUpdates/2013-01-28|January 28, 2013]]<br />
*[[WeeklyUpdates/2013-01-21|January 21, 2013]]<br />
*[[WeeklyUpdates/2013-01-14|January 14, 2013]]<br />
*[[WeeklyUpdates/2013-01-07|January 7, 2013]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2012 <br />
|-<br />
|<br />
*December 31, 2012 - ''No meeting.''<br />
*December 24, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-12-17|December 17, 2012]]<br />
*[[WeeklyUpdates/2012-12-10|December 10, 2012]]<br />
*[[WeeklyUpdates/2012-12-03|December 03, 2012]]<br />
*[[WeeklyUpdates/2012-11-26|November 26, 2012]]<br />
*[[WeeklyUpdates/2012-11-19|November 19, 2012]]<br />
*[[WeeklyUpdates/2012-11-12|November 12, 2012]]<br />
*[[WeeklyUpdates/2012-11-05|November 5, 2012]]<br />
*[[WeeklyUpdates/2012-10-29|October 29, 2012]]<br />
*[[WeeklyUpdates/2012-10-22|October 22, 2012]]<br />
*[[WeeklyUpdates/2012-10-15|October 15, 2012]]<br />
*[[WeeklyUpdates/2012-10-08|October 8, 2012]]<br />
*[[WeeklyUpdates/2012-10-01|October 1, 2012]]<br />
*[[WeeklyUpdates/2012-09-24|September 24, 2012]]<br />
*[[WeeklyUpdates/2012-09-17|September 17, 2012]]<br />
*[[WeeklyUpdates/2012-09-10|September 10, 2012]]<br />
*[[WeeklyUpdates/2012-08-27|August 27, 2012]]<br />
*[[WeeklyUpdates/2012-08-20|August 20, 2012]]<br />
*[[WeeklyUpdates/2012-08-13|August 13, 2012]]<br />
*[[WeeklyUpdates/2012-08-06|August 06, 2012]]<br />
*[[WeeklyUpdates/2012-07-30|July 30, 2012]]<br />
*[[WeeklyUpdates/2012-07-23|July 23, 2012]]<br />
*[[WeeklyUpdates/2012-07-16|July 16, 2012]]<br />
*[[WeeklyUpdates/2012-07-09|July 9, 2012]]<br />
*[[WeeklyUpdates/2012-07-02|July 2, 2012]]<br />
*[[WeeklyUpdates/2012-06-25|June 25, 2012]]<br />
*[[WeeklyUpdates/2012-06-18|June 18, 2012]]<br />
*[[WeeklyUpdates/2012-06-11|June 11, 2012]]<br />
*[[WeeklyUpdates/2012-06-04|June 4, 2012]]<br />
*[[WeeklyUpdates/2012-05-28|May 28, 2012]]<br />
*[[WeeklyUpdates/2012-05-21|May 21, 2012]]<br />
*[[WeeklyUpdates/2012-05-14|May 14, 2012]]<br />
*[[WeeklyUpdates/2012-05-07|May 7, 2012]]<br />
*[[WeeklyUpdates/2012-04-30|April 30, 2012]]<br />
*[[WeeklyUpdates/2012-04-23|April 23, 2012]]<br />
*[[WeeklyUpdates/2012-04-16|April 16, 2012]]<br />
*[[WeeklyUpdates/2012-04-09|April 9, 2012]]<br />
*[[WeeklyUpdates/2012-04-02|April 2, 2012]]<br />
*[[WeeklyUpdates/2012-03-26|March 26, 2012]]<br />
*[[WeeklyUpdates/2012-03-19|March 19, 2012]]<br />
*[[WeeklyUpdates/2012-03-12|March 12, 2012]]<br />
*[[WeeklyUpdates/2012-03-05|March 5, 2012]]<br />
*[[WeeklyUpdates/2012-02-27|February 27, 2012]]<br />
*February 20, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-02-13|February 13, 2012]]<br />
*[[WeeklyUpdates/2012-02-06|February 6, 2012]]<br />
*[[WeeklyUpdates/2012-01-30|January 30, 2012]]<br />
*[[WeeklyUpdates/2012-01-23|January 23, 2012]]<br />
*January 16, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-01-09|January 9, 2012]]<br />
*January 2, 2012 - ''No meeting.''<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
*December 26, 2011 - ''No meeting.''<br />
*[[WeeklyUpdates/2011-12-19|December 19, 2011]]<br />
*[[WeeklyUpdates/2011-12-12|December 12, 2011]]<br />
*[[WeeklyUpdates/2011-12-05|December 5, 2011]]<br />
*[[WeeklyUpdates/2011-11-28|November 28, 2011]]<br />
*[[WeeklyUpdates/2011-11-21|November 21, 2011]]<br />
*[[WeeklyUpdates/2011-11-14|November 14, 2011]]<br />
*[[WeeklyUpdates/2011-11-07|November 7, 2011]]<br />
*[[WeeklyUpdates/2011-10-31|October 31, 2011]]<br />
*[[WeeklyUpdates/2011-10-24|October 24, 2011]]<br />
*[[WeeklyUpdates/2011-10-17|October 17, 2011]]<br />
*[[WeeklyUpdates/2011-10-10|October 10, 2011]]<br />
*[[WeeklyUpdates/2011-10-03|October 3, 2011]]<br />
*[[WeeklyUpdates/2011-09-27|September 26, 2011]]<br />
*[[WeeklyUpdates/2011-09-19|September 19, 2011]]<br />
*September 12, 2011 - ''No meeting due to All-Hands week.''<br />
*September 5, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-08-29|August 29, 2011]]<br />
*[[WeeklyUpdates/2011-08-22|August 22, 2011]]<br />
*[[WeeklyUpdates/2011-08-15|August 15, 2011]]<br />
*[[WeeklyUpdates/2011-08-08|August 8, 2011]]<br />
*[[WeeklyUpdates/2011-08-01|August 1, 2011]]<br />
*[[WeeklyUpdates/2011-07-25|July 25, 2011]]<br />
*[[WeeklyUpdates/2011-07-18|July 18, 2011]]<br />
*[[WeeklyUpdates/2011-07-11|July 11, 2011]]<br />
*July 4, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-06-27|June 27, 2011]]<br />
*[[WeeklyUpdates/2011-06-20|June 20, 2011]]<br />
*[[WeeklyUpdates/2011-06-13|June 13, 2011]]<br />
*[[WeeklyUpdates/2011-06-06|June 6, 2011]]<br />
*May 30, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-05-23|May 23, 2011]]<br />
*[[WeeklyUpdates/2011-05-16|May 16, 2011]]<br />
*[[WeeklyUpdates/2011-05-09|May 9, 2011]]<br />
*[[WeeklyUpdates/2011-05-02|May 2, 2011]]<br />
*[[WeeklyUpdates/2011-04-25|April 25, 2011]]<br />
*[[WeeklyUpdates/2011-04-18|April 18, 2011]]<br />
*[[WeeklyUpdates/2011-04-11|April 11, 2011]]<br />
*April 4, 2011 - ''No meeting due to All-Hands week.''<br />
*[[WeeklyUpdates/2011-03-28|March 28, 2011]]<br />
*[[WeeklyUpdates/2011-03-21|March 21, 2011]]<br />
*[[WeeklyUpdates/2011-03-14|March 14, 2011]]<br />
*[[WeeklyUpdates/2011-03-07|March 7, 2011]]<br />
*[[WeeklyUpdates/2011-02-28|February 28, 2011]]<br />
*February 21, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-02-14|February 14, 2011]]<br />
*[[WeeklyUpdates/2011-02-07|February 07, 2011]]<br />
*[[WeeklyUpdates/2011-01-31|January 31, 2011]]<br />
*[[WeeklyUpdates/2011-01-24|January 24, 2011]]<br />
*January 17, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-01-10|January 10, 2011]]<br />
*[[WeeklyUpdates/2011-01-03|January 3, 2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
*December 27, 2010 - ''No meeting due to holiday season.''<br />
*[[WeeklyUpdates/2010-12-20|December 20, 2010]]<br />
*December 13, 2010 - ''No meeting due to Work Week''<br />
*[[WeeklyUpdates/2010-12-06|December 6, 2010]]<br />
*[[WeeklyUpdates/2010-11-29|November 29, 2010]]<br />
*[[WeeklyUpdates/2010-11-22|November 22, 2010]]<br />
*[[WeeklyUpdates/2010-11-15|November 15, 2010]]<br />
*[[WeeklyUpdates/2010-11-08|November 08, 2010]]<br />
*[[WeeklyUpdates/2010-11-01|November 01, 2010]]<br />
*[[WeeklyUpdates/2010-10-25|October 25, 2010]]<br />
*[[WeeklyUpdates/2010-10-18|October 18, 2010]]<br />
*[[WeeklyUpdates/2010-10-11|October 11, 2010]]<br />
*[[WeeklyUpdates/2010-10-04|October 4, 2010]]<br />
*[[WeeklyUpdates/2010-09-27|September 27, 2010]]<br />
*[[WeeklyUpdates/2010-09-20|September 20, 2010]]<br />
*[[WeeklyUpdates/2010-09-13|September 13, 2010]]<br />
*September 6, 2010 - ''No meeting due to US holiday''<br />
*[[WeeklyUpdates/2010-08-30|August 30, 2010]]<br />
*[[WeeklyUpdates/2010-08-23|August 23, 2010]]<br />
*[[WeeklyUpdates/2010-08-16|August 16, 2010]]<br />
*[[WeeklyUpdates/2010-08-09|August 9, 2010]]<br />
*[[WeeklyUpdates/2010-08-02|August 2, 2010]]<br />
*[[WeeklyUpdates/2010-07-26|July 26, 2010]]<br />
*[[WeeklyUpdates/2010-07-19|July 19, 2010]]<br />
*[[WeeklyUpdates/2010-07-12|July 12, 2010]]<br />
*July 5, 2010 - ''No meeting due to summit''<br />
*[[WeeklyUpdates/2010-06-28|June 28, 2010]]<br />
*[[WeeklyUpdates/2010-06-21|June 21, 2010]]<br />
*[[WeeklyUpdates/2010-06-14|June 14, 2010]]<br />
*[[WeeklyUpdates/2010-06-07|June 7, 2010]]<br />
*May 31, 2010 - ''No meeting due to US holiday''<br />
*[[WeeklyUpdates/2010-05-24|May 24, 2010]]<br />
*[[WeeklyUpdates/2010-05-17|May 17, 2010]]<br />
*[[WeeklyUpdates/2010-05-10|May 10, 2010]]<br />
*[[WeeklyUpdates/2010-05-03|May 03, 2010]]<br />
*[[WeeklyUpdates/2010-04-26|April 26, 2010]]<br />
*[[WeeklyUpdates/2010-04-19|April 19, 2010]]<br />
*[[WeeklyUpdates/2010-04-12|April 12, 2010]]<br />
*[[WeeklyUpdates/2010-04-05|April 5, 2010]]<br />
*[[WeeklyUpdates/2010-03-29|March 29, 2010]]<br />
*[[WeeklyUpdates/2010-03-22|March 22, 2010]]<br />
*[[WeeklyUpdates/2010-03-15|March 15, 2010]]<br />
*[[WeeklyUpdates/2010-03-08|March 8, 2010]]<br />
*[[WeeklyUpdates/2010-03-01|March 1, 2010]]<br />
*[[WeeklyUpdates/2010-02-22|February 22, 2010]] <br />
*[[WeeklyUpdates/2010-02-15|February 15, 2010]]- No meeting due to holiday, please leave updates in the wiki.<br />
*[[WeeklyUpdates/2010-02-08|February 8, 2010]] <br />
*[[WeeklyUpdates/2010-02-01|February 1, 2010]]<br />
*[[WeeklyUpdates/2010-01-25|January 25, 2010]]<br />
*[[WeeklyUpdates/2010-01-18|January 18, 2010]]- No meeting due to US holiday, please leaves updates in the wiki.<br />
*[[WeeklyUpdates/2010-01-11|January 11, 2010]]- First meeting using [[WeeklyUpdates/Guidance|new procedures]].<br />
*[[WeeklyUpdates/2010-01-04|January 04, 2010]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2009 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2009-12-28|December 28, 2009]]- No meeting due to holiday. Feel free to leave updates in the Wiki. <br />
*[[WeeklyUpdates/2009-12-21|December 21, 2009]] <br />
*[[WeeklyUpdates/2009-12-14|December 14, 2009]] <br />
*[[WeeklyUpdates/2009-12-07|December 07, 2009]]- No meeting due to all day Mozilla Corp meetings. Feel free to leave updates in the Wiki. <br />
*[[WeeklyUpdates/2009-11-30|November 30, 2009]] <br />
*[[WeeklyUpdates/2009-11-23|November 23, 2009]] <br />
*[[WeeklyUpdates/2009-11-16|November 16, 2009]] <br />
*[[WeeklyUpdates/2009-11-09|November 09, 2009]] <br />
*[[WeeklyUpdates/2009-11-02|November 02, 2009]] - Time Change! 19:00 UTC (11am PST) <br />
*[[WeeklyUpdates/2009-10-26|October 26, 2009]] <br />
*[[WeeklyUpdates/2009-10-19|October 19, 2009]] <br />
*[[WeeklyUpdates/2009-10-12|October 12, 2009]] <br />
*[[WeeklyUpdates/2009-10-05|October 05, 2009]] <br />
*[[WeeklyUpdates/2009-09-28|September 28, 2009]] <br />
*[[WeeklyUpdates/2009-09-21|September 21, 2009]] <br />
*[[WeeklyUpdates/2009-09-14|September 14, 2009]] <br />
*[[WeeklyUpdates/2009-09-07|September 07, 2009]] - No Meeting due to [http://en.wikipedia.org/wiki/Labor_Day Labor Day] Holiday <br />
*[[WeeklyUpdates/2009-08-31|August 31, 2009]] <br />
*[[WeeklyUpdates/2009-08-24|August 24, 2009]] <br />
*[[WeeklyUpdates/2009-08-17|August 17, 2009]] <br />
*[[WeeklyUpdates/2009-08-10|August 10, 2009]] <br />
*[[WeeklyUpdates/2009-08-03|August 03, 2009]] <br />
*[[WeeklyUpdates/2009-07-27|July 27, 2009]] <br />
*[[WeeklyUpdates/2009-07-20|July 20, 2009]] <br />
*[[WeeklyUpdates/2009-07-13|July 13, 2009]] <br />
*[[WeeklyUpdates/2009-07-06|July 06, 2009]] <br />
*[[WeeklyUpdates/2009-06-29|June 29, 2009]] <br />
*[[WeeklyUpdates/2009-06-22|June 22, 2009]] <br />
*[[WeeklyUpdates/2009-06-15|June 15, 2009]] <br />
*[[WeeklyUpdates/2009-06-08|June 08, 2009]] <br />
*[[WeeklyUpdates/2009-06-01|June 01, 2009]] <br />
*[[WeeklyUpdates/2009-05-25|May 25, 2009]] - No meeting due to US Holiday: [http://en.wikipedia.org/wiki/Memorial_day Memorial Day]. Feel free to leave status! <br />
*[[WeeklyUpdates/2009-05-18|May 18, 2009]] <br />
*[[WeeklyUpdates/2009-05-11|May 11, 2009]] <br />
*[[WeeklyUpdates/2009-05-04|May 04, 2009]] <br />
*April 27, 2009 - no update meeting this week due to on-site event <br />
*[[WeeklyUpdates/2009-04-20|April 20, 2009]] <br />
*[[WeeklyUpdates/2009-04-13|April 13, 2009]] <br />
*[[WeeklyUpdates/2009-04-06|April 06, 2009]] <br />
*[[WeeklyUpdates/2009-03-30|March 30, 2009]] <br />
*[[WeeklyUpdates/2009-03-23|March 23, 2009]] <br />
*[[WeeklyUpdates/2009-03-16|March 16, 2009]] <br />
*[[WeeklyUpdates/2009-03-09|March 09, 2009]] <br />
*[[WeeklyUpdates/2009-03-02|March 02, 2009]] <br />
*[[WeeklyUpdates/2009-02-23|February 23, 2009]] <br />
*February 16, 2009 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2009-02-09|February 09, 2009]] <br />
*[[WeeklyUpdates/2009-02-02|February 02, 2009]] <br />
*[[WeeklyUpdates/2009-01-26|January 26, 2009]] <br />
*January 19, 2009 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2009-01-12|January 12, 2009]] <br />
*[[WeeklyUpdates/2009-01-05|January 05, 2009]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2008 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2008-12-29|December 29, 2008]] <br />
*[[WeeklyUpdates/2008-12-22|December 22, 2008]] <br />
*[[WeeklyUpdates/2008-12-15|December 15, 2008]] <br />
*[[WeeklyUpdates/2008-12-08|December 08, 2008]] <br />
*[[WeeklyUpdates/2008-12-01|December 01, 2008]] <br />
*[[WeeklyUpdates/2008-11-24|November 24, 2008]] <br />
*[[WeeklyUpdates/2008-11-17|November 17, 2008]] <br />
*[[WeeklyUpdates/2008-11-10|November 10, 2008]] <br />
*[[WeeklyUpdates/2008-11-03|November 03, 2008]] <br />
*[[WeeklyUpdates/2008-10-27|October 27, 2008]] <br />
*[[WeeklyUpdates/2008-10-20|October 20, 2008]] <br />
*[[WeeklyUpdates/2008-10-13|October 13, 2008]] <br />
*[[WeeklyUpdates/2008-10-06|October 06, 2008]] <br />
*[[WeeklyUpdates/2008-09-29|September 29, 2008]] <br />
*[[WeeklyUpdates/2008-09-22|September 22, 2008]] <br />
*[[WeeklyUpdates/2008-09-15|September 15, 2008]] <br />
*[[WeeklyUpdates/2008-09-08|September 08, 2008]] <br />
*September 01, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-08-25|August 25, 2008]] <br />
*[[WeeklyUpdates/2008-08-18|August 18, 2008]] <br />
*[[WeeklyUpdates/2008-08-11|August 11, 2008]] <br />
*[[WeeklyUpdates/2008-08-04|August 04, 2008]] <br />
*July 28, 2008 - No Meeting due to Summit <br />
*[[WeeklyUpdates/2008-07-21|July 21, 2008]] <br />
*[[WeeklyUpdates/2008-07-14|July 14, 2008]] <br />
*[[WeeklyUpdates/2008-07-07|July 07, 2008]] <br />
*[[WeeklyUpdates/2008-06-30|June 30, 2008]] <br />
*[[WeeklyUpdates/2008-06-23|June 23, 2008]] <br />
*[[WeeklyUpdates/2008-06-16|June 16, 2008]] <br />
*[[WeeklyUpdates/2008-06-09|June 09, 2008]] <br />
*[[WeeklyUpdates/2008-06-02|June 02, 2008]] <br />
*May 26, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-05-19|May 19, 2008]] <br />
*[[WeeklyUpdates/2008-05-12|May 12, 2008]] <br />
*[[WeeklyUpdates/2008-05-05|May 05, 2008]] <br />
*[[WeeklyUpdates/2008-04-28|April 28, 2008]] <br />
*[[WeeklyUpdates/2008-04-21|April 21, 2008]] <br />
*[[WeeklyUpdates/2008-04-14|April 14, 2008]] <br />
*[[WeeklyUpdates/2008-04-07|April 07, 2008]] <br />
*[[WeeklyUpdates/2008-03-31|March 31, 2008]] <br />
*[[WeeklyUpdates/2008-03-24|March 24, 2008]] <br />
*[[WeeklyUpdates/2008-03-17|March 17, 2008]] <br />
*[[WeeklyUpdates/2008-03-10|March 10, 2008]] <br />
*[[WeeklyUpdates/2008-03-03|March 03, 2008]] <br />
*[[WeeklyUpdates/2008-02-25|February 25, 2008]] <br />
*February 18, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-02-11|February 11, 2008]] <br />
*[[WeeklyUpdates/2008-02-04|February 04, 2008]] <br />
*[[WeeklyUpdates/2008-01-28|January 28, 2008]] <br />
*January 21, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-01-14|January 14, 2008]] <br />
*[[WeeklyUpdates/2008-01-07|January 07, 2008]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2007 <br />
|-<br />
|<br />
*December 31, 2007 - No Meeting due to US holiday season <br />
*December 24, 2007 - No Meeting due to US holiday season <br />
*[[WeeklyUpdates/2007-12-17|December 17, 2007]] <br />
*[[WeeklyUpdates/2007-12-10|December 10, 2007]] <br />
*[[WeeklyUpdates/2007-12-03|December 03, 2007]] <br />
*[[WeeklyUpdates/2007-11-26|November 26, 2007]] <br />
*[[WeeklyUpdates/2007-11-19|November 19, 2007]] <br />
*November 12, 2007 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2007-11-05|November 05, 2007]] <br />
*[[WeeklyUpdates/2007-10-29|October 29, 2007]] <br />
*[[WeeklyUpdates/2007-10-22|October 22, 2007]] <br />
*[[WeeklyUpdates/2007-10-15|October 15, 2007]] <br />
*[[WeeklyUpdates/2007-10-08|October 08, 2007]] <br />
*[[WeeklyUpdates/2007-10-01|October 01, 2007]] <br />
*[[WeeklyUpdates/2007-09-24|September 24, 2007]] <br />
*[[WeeklyUpdates/2007-09-17|September 17, 2007]] <br />
*[[WeeklyUpdates/2007-09-10|September 10, 2007]] <br />
*[[WeeklyUpdates/2007-08-27|August 27, 2007]] <br />
*[[WeeklyUpdates/2007-08-20|August 20, 2007]] <br />
*[[WeeklyUpdates/2007-08-13|August 13, 2007]] <br />
*[[WeeklyUpdates/2007-08-06|August 6, 2007]] <br />
*[[WeeklyUpdates/2007-07-30|July 30, 2007]] <br />
*[[WeeklyUpdates/2007-07-23|July 23, 2007]] <br />
*[[WeeklyUpdates/2007-07-16|July 16, 2007]] <br />
*[[WeeklyUpdates/2007-07-09|July 9, 2007]] <br />
*[[WeeklyUpdates/2007-07-02|July 2, 2007]] <br />
*[[WeeklyUpdates/2007-06-25|June 25, 2007]] <br />
*[[WeeklyUpdates/2007-06-18|June 18, 2007]] <br />
*[[WeeklyUpdates/2007-06-11|June 11, 2007]] <br />
*[[WeeklyUpdates/2007-06-04|June 4, 2007]] <br />
*[[WeeklyUpdates/2007-05-21|May 21, 2007]] <br />
*[[WeeklyUpdates/2007-05-14|May 14, 2007]] <br />
*[[WeeklyUpdates/2007-05-07|May 7, 2007]] <br />
*[[WeeklyUpdates/2007-04-30|April 30, 2007]] <br />
*[[WeeklyUpdates/2007-04-23|April 23, 2007]] <br />
*[[WeeklyUpdates/2007-04-16|April 16, 2007]] <br />
*[[WeeklyUpdates/2007-04-09|April 9, 2007]] <br />
*[[WeeklyUpdates/2007-04-02|April 2, 2007]] <br />
*[[WeeklyUpdates/2007-03-26|March 26, 2007]] <br />
*[[WeeklyUpdates/2007-03-19|March 19, 2007]] <br />
*[[WeeklyUpdates/2007-03-12|March 12, 2007]] <br />
*[[WeeklyUpdates/2007-03-05|March 5, 2007]] <br />
*[[WeeklyUpdates/2007-02-26|February 26, 2007]] <br />
*[[WeeklyUpdates/2007-02-12|February 12, 2007]] <br />
*[[WeeklyUpdates/2007-02-05|February 5, 2007]] <br />
*[[WeeklyUpdates/2007-01-29|January 29, 2007]] <br />
*[[WeeklyUpdates/2007-01-22|January 22, 2007]] <br />
*[[WeeklyUpdates/2007-01-08|January 08, 2007]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2006 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2006-12-18|December 18, 2006]] <br />
*[[WeeklyUpdates/2006-12-11|December 11, 2006]] <br />
*[[WeeklyUpdates/2006-12-04|December 4, 2006]] <br />
*[[WeeklyUpdates/2006-11-27|November 27, 2006]] <br />
*[[WeeklyUpdates/2006-11-13|November 13, 2006]] <br />
*[[WeeklyUpdates/2006-11-06|November 6, 2006]] <br />
*[[WeeklyUpdates/2006-10-30|October 30, 2006]] <br />
*[[WeeklyUpdates/2006-10-23|October 23, 2006]] <br />
*[[WeeklyUpdates/2006-10-16|October 16, 2006]] <br />
*[[WeeklyUpdates/2006-10-09|October 9, 2006]] <br />
*[[WeeklyUpdates/2006-10-02|October 2, 2006]] <br />
*[[WeeklyUpdates/2006-09-25|September 25, 2006]] <br />
*[[WeeklyUpdates/2006-09-18|September 18, 2006]] <br />
*[[WeeklyUpdates/2006-09-11|September 11, 2006]] <br />
*September 4, 2006 - No Meeting due to US and Canadian Holiday <br />
*[[WeeklyUpdates/2006-08-28|August 28, 2006]] <br />
*[[WeeklyUpdates/2006-08-21|August 21, 2006]] <br />
*[[WeeklyUpdates/2006-08-14|August 14, 2006]] <br />
*[[WeeklyUpdates/2006-08-07|August 07, 2006]] <br />
*[[WeeklyUpdates/2006-07-31|July 31, 2006]] <br />
*[[WeeklyUpdates/2006-07-24|July 24, 2006]] <br />
*[[WeeklyUpdates/2006-07-17|July 17, 2006]] <br />
*[[WeeklyUpdates/2006-07-10|July 10, 2006]] <br />
*July 3, 2006 - No Meeting due to US Holiday <br />
*June 26, 2006 - No Meeting <br />
*[[WeeklyUpdates/2006-06-19|June 19, 2006]] <br />
*[[WeeklyUpdates/2006-06-12|June 12, 2006]] <br />
*[[WeeklyUpdates/2006-06-05|June 05, 2006]] <br />
*May 29, 2006 -- No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2006-05-22|May 22, 2006]] <br />
*May 15, 2006 -- No Meeting due to XTech 2006 Conference <br />
*[[WeeklyUpdates/2006-05-08|May 08, 2006]] <br />
*[[WeeklyUpdates/2006-05-01|May 01, 2006]] <br />
*[[WeeklyUpdates/2006-04-24|April 24, 2006]] <br />
*[[WeeklyUpdates/2006-04-17|April 17, 2006]] <br />
*[[WeeklyUpdates/2006-04-10|April 10, 2006]] <br />
*[[WeeklyUpdates/2006-04-03|April 03, 2006]] <br />
*[[WeeklyUpdates/2006-03-27|March 27, 2006]]<br />
|}<br />
<br />
''Note: Older [http://www-archive.mozilla.org/status/minutes.html meeting minutes] and [http://www-archive.mozilla.org/status/ status updates] are available on the www.mozilla.org archive site.''<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Projectcallproject&diff=1148297Projectcallproject2016-09-19T19:32:29Z<p>MykMelez: correct the year in which Mozilla staff started meeting</p>
<hr />
<div>== Project Call Project (2016) ==<br />
=== Background ===<br />
The Project Call began when it was attended by a handful of paid staff and contributors who sat around an actual table providing technical updates, discussing blockers and sharing ideas. <br />
<br />
Originally, the Project Call was a private weekly gathering of a group called "Mozilla Staff," comprising Netscape employees dedicated to the Mozilla project, plus a couple of non-Netscape contributors working on Mozilla-related projects at other organizations. It began the early months of 1998.<br />
<br />
Staff's membership ran the gamut from project leads like Brendan and Mitchell to individual contributors like Myk Melez and Asa Dotzler. During the meetings, the group discussed a variety of issues, especially questions of governance. We were also chartered to resolve disputes within the community. More info on Staff is available at http://www-archive.mozilla.org/about/staff.<br />
<br />
After the Mozilla Foundation was founded, the meeting gradually turned into a weekly meeting of MoFo employees, and Staff became moribund (although it continues to exist in vestigial form via the staff@mozilla.org alias, which occasionally receives and redirects some complaint about Mozilla). MoFo then turned into MoFo/MoCo, and at some point we decided to make the meetings public, expanding the intended audience to all Mozillians.<br />
<br />
Today, a decade after it began, the meeting is attended by, on average, 200-300 people each week with ⅔ of that viewing live in Mountain View or other Mozilla offices with some picking it up later. We have no sense of who, staff / volunteers / other, are watching the meetings, other than those we see live in offices or ⅓ of the total. The format of the meeting and agenda have changed only incrementally over the course of its long history and there is some sense, from potch and others, that engagement, as well as actual participation in the meeting, is receding.<br />
<br />
=== Project Overview ===<br />
Part of the internal communications team’s reason-for-being is to build and sustain an internal communications system that enables information and inspiration to get where it needs to get when it needs to get there. To do that, we’re spinning up this project, aimed at re-imagining The Project Call so that it offers real engagement value for its intended audience. We don't know where our research will lead us right now, be we believe there is an opportunity hiding out here somewhere, so we're going to see. <br />
<br />
=== Approach/Strategy ===<br />
Given what we suspect this meeting represents to a subset of the organization (hallmark of our “openness”, communications platform cherished by the old guard, legacy identity with a deep tie to the past), we will approach any sort of change with delicacy and candor. This may mean execution moves more slowly that we’d like, but we will err on the side of “treading lightly” over up-ending an iconic fixture.<br />
<br />
We will also look to support all of our recommendations with data, where possible, and to test small changes over time vs. broad sweeping reform (this approach may change depending upon what the research says). The bulk of the project will be research, likely 80% primary and 20% secondary (best practices in other organizations). This focus on research has the added benefit of allowing any sort of change effort to feel more inclusive.<br />
<br />
=== Goal / Success Metric ===<br />
By EOY 2016, we will have tested a number (exact number TBD) of meaningful changes to the current meeting format and/or content that result in greater immediate audience satisfaction (as measured by a 10% increase in attendance). Longer-term, this project aims to re-imagine The Project Call so that it offers real engagement value for its intended audience, connected to, as well as reinforcing of, a greater communications system internally (longer term measures will be embedded within overall engagement scores). <br />
<br />
=== Project Team ===<br />
Mardi - Responsible<br />
Diane (Lotta) - Accountable <br />
Potch, Lucy/Participation Team, Richard (A/V team), MarComm, current attendees - Consulted<br />
Dave, George, Angela - Informed<br />
<br />
=== Rough Timeline ===<br />
<br />
'''August - September''' (research, listen/discover). Here is where we discover the answers to questions like: Who is the primary or intended audience for this meeting? What is the value of this meeting currently to that group? What changes do you think need to happen in order for the audience to get maximum value out of the meeting? Would you miss it if it was gone? What problem is the meeting solving?<br />
<br />
* Identify key stakeholders + form task team, conduct 2-5 focus group + stakeholder interviews, launch user survey within the meeting (targeted at current audience), survey volunteers + a sample of paid staff.<br />
* Investigate what “other companies” do. Those who run status meetings on a regular basis + those who don’t (or do them in a different way or not at all).<br />
<br />
'''September - ½ October''' <br />
Compile and analyze research<br />
Share with task team and generate recommendations for change, if any.<br />
Vet changes and expected results with larger group (could be all of Mozilla)<br />
<br />
'''½ October - December'''<br />
Test changes<br />
<br />
=== Attendee Survey ===<br />
Open now through September 23rd: https://www.surveygizmo.com/s3/3036557/Mozilla-Project-Call<br />
(we'll post summary results once the survey is closed).</div>MykMelezhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates&diff=1147498WeeklyUpdates2016-09-12T18:11:49Z<p>MykMelez: explaining missing September 5th, 2015 entry</p>
<hr />
<div>:''These updates concern Mozilla as a whole. For the weekly Firefox meetings, see [[Firefox/DeliveryMeetings]], for Gecko progress, see [[Platform#Meeting_Notes]].''<br />
<br />
==Meeting Details==<br />
*Every Monday @ 11:00am Pacific Time (19:00 BST) <br />
*Mozilla HQ, Ten Forward commons area <br />
{{conf|8600}}<br />
*http://air.mozilla.org/ to watch and listen <br />
*join irc.mozilla.org #airmozilla for backchannel discussion<br />
*'''Presenters only''': Vidyo room "Brownbags". Do ''not'' use this room if you're not planning to speak.<br />
<br />
'''Agenda:''' [[WeeklyUpdates/{{#time: Y-m-d | monday}}|Next Week's Agenda]]<br />
<br />
When you call in, you'll be muted by default, to keep phone noise down. Use "*1" (including the star) to unmute yourself if you want to say something. <br />
<br />
Full notes below. <!-- See https://wiki.mozilla.org/WeeklyUpdates/Template for create new page --><br />
<br />
==Meeting Notes==<br />
[[Template:WeeklyUpdates]] - <nowiki>{{subst:WeeklyUpdates}}</nowiki><br />
<!--*[[WeeklyUpdates/Template]]--><br />
<br />
Create a new weekly agenda from the [[Template:WeeklyUpdates|template]]:<br />
<createbox><br />
align=left<br />
type=create<br />
preload=Template:WeeklyUpdates<br />
default={{#time: Y-m-d | monday}}<br />
prefix=WeeklyUpdates/<br />
</createbox><br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2016 <br />
|-<br />
|<br />
* [[WeeklyUpdates/2016-09-12|September 12th, 2016]]<br />
* There was no meeting on September 5 because of the US Labor Day holiday.<br />
* [[WeeklyUpdates/2016-08-29|August 29nd, 2016]]<br />
* [[WeeklyUpdates/2016-08-22|August 22nd, 2016]]<br />
* [[WeeklyUpdates/2016-08-15|August 15th, 2016]]<br />
* [[WeeklyUpdates/2016-08-08|August 8th, 2016]]<br />
* [[WeeklyUpdates/2016-08-01|August 1st, 2016]]<br />
* [[WeeklyUpdates/2016-07-25|July 25th, 2016]]<br />
* [[WeeklyUpdates/2016-07-18|July 18th, 2016]]<br />
* [[WeeklyUpdates/2016-07-11|July 11th, 2016]]<br />
* [[WeeklyUpdates/2016-06-27|June 27th, 2016]]<br />
* [[WeeklyUpdates/2016-06-20|June 20th, 2016]]<br />
* [[WeeklyUpdates/2016-06-06|June 6th, 2016]]<br />
* [[WeeklyUpdates/2016-05-23|May 23rd, 2016]]<br />
* [[WeeklyUpdates/2016-05-16|May 16th, 2016]]<br />
* [[WeeklyUpdates/2016-05-09|May 9th, 2016]]<br />
* [[WeeklyUpdates/2016-05-02|May 2nd, 2016]]<br />
* [[WeeklyUpdates/2016-04-25|April 25th, 2016]]<br />
* [[WeeklyUpdates/2016-04-18|April 18th, 2016]]<br />
* [[WeeklyUpdates/2016-04-11|April 11th, 2016]]<br />
* [[WeeklyUpdates/2016-04-04|April 4th, 2016]]<br />
* [[WeeklyUpdates/2016-03-28|March 28th, 2016]]<br />
* [[WeeklyUpdates/2016-03-21|March 21st, 2016]]<br />
* [[WeeklyUpdates/2016-03-14|March 14th, 2016]]<br />
* [[WeeklyUpdates/2016-03-07|March 7th, 2016]]<br />
* [[WeeklyUpdates/2016-02-29|February 29th, 2016]]<br />
* [[WeeklyUpdates/2016-02-22|February 22nd, 2016]]<br />
* [[WeeklyUpdates/2016-02-15|February 15th, 2016]] (no live meeting due to [https://en.wikipedia.org/wiki/Washington's_Birthday Washington's Birthday] Holiday in the US.)<br />
* [[WeeklyUpdates/2016-02-08|February 8th, 2016]]<br />
* [[WeeklyUpdates/2016-02-01|February 1st, 2016]]<br />
* [[WeeklyUpdates/2016-01-25|January 25th, 2016]]<br />
* [[WeeklyUpdates/2016-01-11|January 11th, 2016]]<br />
* [[WeeklyUpdates/2016-01-04|January 4th, 2016]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2015 <br />
|-<br />
|<br />
* [[WeeklyUpdates/2015-12-28|December 28th, 2015]] (no meeting, just announcements)<br />
* December 21st (no meeting)<br />
* [[WeeklyUpdates/2015-12-14|December 14th, 2015]] (no live meeting due to All Hands recovery)<br />
* December 7th (no meeting due to All Hands)<br />
* [[WeeklyUpdates/2015-11-30|November 30th, 2015]]<br />
* [[WeeklyUpdates/2015-11-23|November 23rd, 2015]]<br />
* [[WeeklyUpdates/2015-11-16|November 16th, 2015]]<br />
* [[WeeklyUpdates/2015-11-09|November 9th, 2015]]<br />
* [[WeeklyUpdates/2015-11-02|November 2nd, 2015]]<br />
* [[WeeklyUpdates/2015-10-26|October 26th, 2015]]<br />
* [[WeeklyUpdates/2015-10-19|October 19th, 2015]]<br />
* [[WeeklyUpdates/2015-10-12|October 12th, 2015]]<br />
* [[WeeklyUpdates/2015-10-05|October 5th, 2015]]<br />
* [[WeeklyUpdates/2015-09-28|September 28th, 2015]]<br />
* [[WeeklyUpdates/2015-09-21|September 21st, 2015]]<br />
* [[WeeklyUpdates/2015-09-14|September 14th, 2015]]<br />
* September 7th (No meeting due to Labor Day)<br />
* [[WeeklyUpdates/2015-08-31|August 31st, 2015]]<br />
* [[WeeklyUpdates/2015-08-24|August 24th, 2015]]<br />
* [[WeeklyUpdates/2015-08-17|August 17th, 2015]]<br />
* [[WeeklyUpdates/2015-08-10|August 10th, 2015]]<br />
* [[WeeklyUpdates/2015-08-03|August 3rd, 2015]]<br />
* [[WeeklyUpdates/2015-07-27|July 27th, 2015]]<br />
* [[WeeklyUpdates/2015-07-20|July 20th, 2015]]<br />
* [[WeeklyUpdates/2015-07-13|July 13th, 2015]]<br />
* [[WeeklyUpdates/2015-07-06|July 6th, 2015]]<br />
* [[WeeklyUpdates/2015-06-29|June 29th, 2015]]<br />
* June 22nd, 2015 (no meeting due to All-Hands travel)<br />
* [[WeeklyUpdates/2015-06-15|June 15th, 2015]]<br />
* [[WeeklyUpdates/2015-06-08|June 8th, 2015]]<br />
* [[WeeklyUpdates/2015-06-01|June 1st, 2015]]<br />
* May 25th, 2015 (no meeting due to US Holiday)<br />
* [[WeeklyUpdates/2015-05-18|May 18th, 2015]]<br />
* [[WeeklyUpdates/2015-05-11|May 11th, 2015]]<br />
* [[WeeklyUpdates/2015-05-04|May 4th, 2015]]<br />
* [[WeeklyUpdates/2015-04-27|April 27th, 2015]]<br />
* [[WeeklyUpdates/2015-04-20|April 20th, 2015]]<br />
* [[WeeklyUpdates/2015-04-13|April 13th, 2015]]<br />
* [[WeeklyUpdates/2015-04-06|April 6th, 2015]]<br />
* [[WeeklyUpdates/2015-03-30|March 30th, 2015]]<br />
* [[WeeklyUpdates/2015-03-23|March 23rd, 2015]]<br />
* [[WeeklyUpdates/2015-03-16|March 16th, 2015]]<br />
* [[WeeklyUpdates/2015-03-09|March 9th, 2015]]<br />
* [[WeeklyUpdates/2015-03-02|March 2nd, 2015]]<br />
* [[WeeklyUpdates/2015-02-23|February 23rd, 2015]]<br />
* Feb 16th No meeting due to US Holiday<br />
* [[WeeklyUpdates/2015-02-09|February 9nd, 2015]]<br />
* [[WeeklyUpdates/2015-02-02|February 2nd, 2015]]<br />
* [[WeeklyUpdates/2015-01-26|January 26th, 2015]]<br />
* [[WeeklyUpdates/2015-01-19|January 19th, 2015]]<br />
* [[WeeklyUpdates/2015-01-12|January 12th, 2015]]<br />
* [[WeeklyUpdates/2015-01-05|January 5th, 2015]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2014<br />
|-<br />
|<br />
*[[WeeklyUpdates/2014-12-29|December 29th, 2014]]<br />
*[[WeeklyUpdates/2014-12-15|December 15th, 2014]]<br />
*[[WeeklyUpdates/2014-12-08|December 8th, 2014]]<br />
*[[WeeklyUpdates/2014-11-24|November 24th, 2014]]<br />
*[[WeeklyUpdates/2014-11-17|November 17th, 2014]]<br />
*[[WeeklyUpdates/2014-11-10|November 10th, 2014]]<br />
*[[WeeklyUpdates/2014-11-03|November 3rd, 2014]]<br />
*[[WeeklyUpdates/2014-10-27|October 27th, 2014]]<br />
*[[WeeklyUpdates/2014-10-20|October 20th, 2014]]<br />
*[[WeeklyUpdates/2014-10-13|October 13th, 2014]]<br />
*[[WeeklyUpdates/2014-10-06|October 6th, 2014]]<br />
*[[WeeklyUpdates/2014-09-29|September 29th, 2014]]<br />
*[[WeeklyUpdates/2014-09-22|September 22th, 2014]]<br />
*[[WeeklyUpdates/2014-09-15|September 15th, 2014]]<br />
*[[WeeklyUpdates/2014-09-08|September 8th, 2014]]<br />
*[[WeeklyUpdates/2014-09-01|September 1st, 2014]]<br />
*[[WeeklyUpdates/2014-08-25|August 25, 2014]]<br />
*[[WeeklyUpdates/2014-08-18|August 18, 2014]]<br />
*[[WeeklyUpdates/2014-08-11|August 11, 2014]]<br />
*[[WeeklyUpdates/2014-08-04|August 4, 2014]]<br />
*[[WeeklyUpdates/2014-07-28|July 28, 2014]]<br />
*[[WeeklyUpdates/2014-07-21|July 21, 2014]]<br />
*[[WeeklyUpdates/2014-07-14|July 14, 2014]]<br />
*[[WeeklyUpdates/2014-07-07|July 7, 2014]]<br />
*[[WeeklyUpdates/2014-06-30|June 30, 2014]]<br />
*[[WeeklyUpdates/2014-06-23|June 23, 2014]]<br />
*[[WeeklyUpdates/2014-06-16|June 16, 2014]]<br />
*[[WeeklyUpdates/2014-06-09|June 09, 2014]]<br />
*[[WeeklyUpdates/2014-06-02|June 02, 2014]]<br />
*[[WeeklyUpdates/2014-05-26|May 26, 2014]]<br />
*[[WeeklyUpdates/2014-05-19|May 19, 2014]]<br />
*[[WeeklyUpdates/2014-05-12|May 12, 2014]]<br />
*[[WeeklyUpdates/2014-05-05|May 05, 2014]]<br />
*[[WeeklyUpdates/2014-04-28|April 28, 2014]]<br />
*[[WeeklyUpdates/2014-04-21|April 21, 2014]]<br />
*[[WeeklyUpdates/2014-04-14|April 14, 2014]]<br />
*[[WeeklyUpdates/2014-04-07|April 7, 2014]]<br />
*[[WeeklyUpdates/2014-03-31|March 31, 2014]]<br />
*[[WeeklyUpdates/2014-03-24|March 24, 2014]]<br />
*[[WeeklyUpdates/2014-03-17|March 17, 2014]]<br />
*[[WeeklyUpdates/2014-03-10|March 10, 2014]]<br />
*[[WeeklyUpdates/2014-03-03|March 3, 2014]]<br />
*[[WeeklyUpdates/2014-02-24|February 24, 2014]]<br />
*[[WeeklyUpdates/2014-02-10|February 10, 2014]]<br />
*[[WeeklyUpdates/2014-02-03|February 3, 2014]]<br />
*[[WeeklyUpdates/2014-01-27|January 27, 2014]]<br />
*[[WeeklyUpdates/2014-01-20|January 20, 2014]]<br />
*[[WeeklyUpdates/2014-01-13|January 13, 2014]]<br />
*[[WeeklyUpdates/2014-01-06|January 6, 2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2013 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2013-12-16|December 16, 2013]]<br />
*[[WeeklyUpdates/2013-12-09|December 9, 2013]]<br />
*[[WeeklyUpdates/2013-12-02|December 2, 2013]]<br />
*[[WeeklyUpdates/2013-11-25|November 25, 2013]]<br />
*[[WeeklyUpdates/2013-11-18|November 18, 2013]]<br />
*[[WeeklyUpdates/2013-11-11|November 11, 2013]]<br />
*[[WeeklyUpdates/2013-11-04|November 4, 2013]]<br />
*[[WeeklyUpdates/2013-10-28|October 28, 2013]]<br />
*[[WeeklyUpdates/2013-10-21|October 21, 2013]]<br />
*[[WeeklyUpdates/2013-10-14|October 14, 2013]]<br />
*[[WeeklyUpdates/2013-10-07|October 7, 2013]]<br />
*[[WeeklyUpdates/2013-09-30|September 30, 2013]]<br />
*[[WeeklyUpdates/2013-09-23|September 23, 2013]]<br />
*[[WeeklyUpdates/2013-09-16|September 16, 2013]]<br />
*[[WeeklyUpdates/2013-09-09|September 9, 2013]]<br />
*[[WeeklyUpdates/2013-09-02|September 2, 2013]]<br />
*[[WeeklyUpdates/2013-08-26|August 26, 2013]]<br />
*[[WeeklyUpdates/2013-08-19|August 19, 2013]]<br />
*[[WeeklyUpdates/2013-08-12|August 12, 2013]]<br />
*[[WeeklyUpdates/2013-08-05|August 5, 2013]]<br />
*[[WeeklyUpdates/2013-07-29|July 29, 2013]]<br />
*[[WeeklyUpdates/2013-07-22|July 22, 2013]]<br />
*[[WeeklyUpdates/2013-07-15|July 15, 2013]]<br />
*[[WeeklyUpdates/2013-07-08|July 8, 2013]]<br />
*[[WeeklyUpdates/2013-07-01|July 1, 2013]]<br />
*[[WeeklyUpdates/2013-06-24|June 24, 2013]]<br />
*[[WeeklyUpdates/2013-06-17|June 17, 2013]]<br />
*[[WeeklyUpdates/2013-06-10|June 10, 2013]]<br />
*[[WeeklyUpdates/2013-06-03|June 3, 2013]]<br />
*[[WeeklyUpdates/2013-05-20|May 20, 2013]]<br />
*[[WeeklyUpdates/2013-05-13|May 13, 2013]]<br />
*[[WeeklyUpdates/2013-05-06|May 6, 2013]]<br />
*[[WeeklyUpdates/2013-04-29|April 29, 2013]]<br />
*[[WeeklyUpdates/2013-04-22|April 22, 2013]]<br />
*[[WeeklyUpdates/2013-04-15|April 15, 2013]]<br />
*[[WeeklyUpdates/2013-04-08|April 8, 2013]]<br />
*[[WeeklyUpdates/2013-04-01|April 1, 2013]]<br />
*[[WeeklyUpdates/2013-03-25|March 25, 2013]]<br />
*[[WeeklyUpdates/2013-03-18|March 18, 2013]]<br />
*[[WeeklyUpdates/2013-03-11|March 11, 2013]]<br />
*[[WeeklyUpdates/2013-03-04|March 4, 2013]]<br />
*[[WeeklyUpdates/2013-02-25|February 25, 2013]]<br />
*February 18, 2013 - ''No meeting.'' <br />
*[[WeeklyUpdates/2013-02-11|February 11, 2013]]<br />
*[[WeeklyUpdates/2013-02-04|February 04, 2013]]<br />
*[[WeeklyUpdates/2013-01-28|January 28, 2013]]<br />
*[[WeeklyUpdates/2013-01-21|January 21, 2013]]<br />
*[[WeeklyUpdates/2013-01-14|January 14, 2013]]<br />
*[[WeeklyUpdates/2013-01-07|January 7, 2013]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2012 <br />
|-<br />
|<br />
*December 31, 2012 - ''No meeting.''<br />
*December 24, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-12-17|December 17, 2012]]<br />
*[[WeeklyUpdates/2012-12-10|December 10, 2012]]<br />
*[[WeeklyUpdates/2012-12-03|December 03, 2012]]<br />
*[[WeeklyUpdates/2012-11-26|November 26, 2012]]<br />
*[[WeeklyUpdates/2012-11-19|November 19, 2012]]<br />
*[[WeeklyUpdates/2012-11-12|November 12, 2012]]<br />
*[[WeeklyUpdates/2012-11-05|November 5, 2012]]<br />
*[[WeeklyUpdates/2012-10-29|October 29, 2012]]<br />
*[[WeeklyUpdates/2012-10-22|October 22, 2012]]<br />
*[[WeeklyUpdates/2012-10-15|October 15, 2012]]<br />
*[[WeeklyUpdates/2012-10-08|October 8, 2012]]<br />
*[[WeeklyUpdates/2012-10-01|October 1, 2012]]<br />
*[[WeeklyUpdates/2012-09-24|September 24, 2012]]<br />
*[[WeeklyUpdates/2012-09-17|September 17, 2012]]<br />
*[[WeeklyUpdates/2012-09-10|September 10, 2012]]<br />
*[[WeeklyUpdates/2012-08-27|August 27, 2012]]<br />
*[[WeeklyUpdates/2012-08-20|August 20, 2012]]<br />
*[[WeeklyUpdates/2012-08-13|August 13, 2012]]<br />
*[[WeeklyUpdates/2012-08-06|August 06, 2012]]<br />
*[[WeeklyUpdates/2012-07-30|July 30, 2012]]<br />
*[[WeeklyUpdates/2012-07-23|July 23, 2012]]<br />
*[[WeeklyUpdates/2012-07-16|July 16, 2012]]<br />
*[[WeeklyUpdates/2012-07-09|July 9, 2012]]<br />
*[[WeeklyUpdates/2012-07-02|July 2, 2012]]<br />
*[[WeeklyUpdates/2012-06-25|June 25, 2012]]<br />
*[[WeeklyUpdates/2012-06-18|June 18, 2012]]<br />
*[[WeeklyUpdates/2012-06-11|June 11, 2012]]<br />
*[[WeeklyUpdates/2012-06-04|June 4, 2012]]<br />
*[[WeeklyUpdates/2012-05-28|May 28, 2012]]<br />
*[[WeeklyUpdates/2012-05-21|May 21, 2012]]<br />
*[[WeeklyUpdates/2012-05-14|May 14, 2012]]<br />
*[[WeeklyUpdates/2012-05-07|May 7, 2012]]<br />
*[[WeeklyUpdates/2012-04-30|April 30, 2012]]<br />
*[[WeeklyUpdates/2012-04-23|April 23, 2012]]<br />
*[[WeeklyUpdates/2012-04-16|April 16, 2012]]<br />
*[[WeeklyUpdates/2012-04-09|April 9, 2012]]<br />
*[[WeeklyUpdates/2012-04-02|April 2, 2012]]<br />
*[[WeeklyUpdates/2012-03-26|March 26, 2012]]<br />
*[[WeeklyUpdates/2012-03-19|March 19, 2012]]<br />
*[[WeeklyUpdates/2012-03-12|March 12, 2012]]<br />
*[[WeeklyUpdates/2012-03-05|March 5, 2012]]<br />
*[[WeeklyUpdates/2012-02-27|February 27, 2012]]<br />
*February 20, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-02-13|February 13, 2012]]<br />
*[[WeeklyUpdates/2012-02-06|February 6, 2012]]<br />
*[[WeeklyUpdates/2012-01-30|January 30, 2012]]<br />
*[[WeeklyUpdates/2012-01-23|January 23, 2012]]<br />
*January 16, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-01-09|January 9, 2012]]<br />
*January 2, 2012 - ''No meeting.''<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
*December 26, 2011 - ''No meeting.''<br />
*[[WeeklyUpdates/2011-12-19|December 19, 2011]]<br />
*[[WeeklyUpdates/2011-12-12|December 12, 2011]]<br />
*[[WeeklyUpdates/2011-12-05|December 5, 2011]]<br />
*[[WeeklyUpdates/2011-11-28|November 28, 2011]]<br />
*[[WeeklyUpdates/2011-11-21|November 21, 2011]]<br />
*[[WeeklyUpdates/2011-11-14|November 14, 2011]]<br />
*[[WeeklyUpdates/2011-11-07|November 7, 2011]]<br />
*[[WeeklyUpdates/2011-10-31|October 31, 2011]]<br />
*[[WeeklyUpdates/2011-10-24|October 24, 2011]]<br />
*[[WeeklyUpdates/2011-10-17|October 17, 2011]]<br />
*[[WeeklyUpdates/2011-10-10|October 10, 2011]]<br />
*[[WeeklyUpdates/2011-10-03|October 3, 2011]]<br />
*[[WeeklyUpdates/2011-09-27|September 26, 2011]]<br />
*[[WeeklyUpdates/2011-09-19|September 19, 2011]]<br />
*September 12, 2011 - ''No meeting due to All-Hands week.''<br />
*September 5, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-08-29|August 29, 2011]]<br />
*[[WeeklyUpdates/2011-08-22|August 22, 2011]]<br />
*[[WeeklyUpdates/2011-08-15|August 15, 2011]]<br />
*[[WeeklyUpdates/2011-08-08|August 8, 2011]]<br />
*[[WeeklyUpdates/2011-08-01|August 1, 2011]]<br />
*[[WeeklyUpdates/2011-07-25|July 25, 2011]]<br />
*[[WeeklyUpdates/2011-07-18|July 18, 2011]]<br />
*[[WeeklyUpdates/2011-07-11|July 11, 2011]]<br />
*July 4, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-06-27|June 27, 2011]]<br />
*[[WeeklyUpdates/2011-06-20|June 20, 2011]]<br />
*[[WeeklyUpdates/2011-06-13|June 13, 2011]]<br />
*[[WeeklyUpdates/2011-06-06|June 6, 2011]]<br />
*May 30, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-05-23|May 23, 2011]]<br />
*[[WeeklyUpdates/2011-05-16|May 16, 2011]]<br />
*[[WeeklyUpdates/2011-05-09|May 9, 2011]]<br />
*[[WeeklyUpdates/2011-05-02|May 2, 2011]]<br />
*[[WeeklyUpdates/2011-04-25|April 25, 2011]]<br />
*[[WeeklyUpdates/2011-04-18|April 18, 2011]]<br />
*[[WeeklyUpdates/2011-04-11|April 11, 2011]]<br />
*April 4, 2011 - ''No meeting due to All-Hands week.''<br />
*[[WeeklyUpdates/2011-03-28|March 28, 2011]]<br />
*[[WeeklyUpdates/2011-03-21|March 21, 2011]]<br />
*[[WeeklyUpdates/2011-03-14|March 14, 2011]]<br />
*[[WeeklyUpdates/2011-03-07|March 7, 2011]]<br />
*[[WeeklyUpdates/2011-02-28|February 28, 2011]]<br />
*February 21, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-02-14|February 14, 2011]]<br />
*[[WeeklyUpdates/2011-02-07|February 07, 2011]]<br />
*[[WeeklyUpdates/2011-01-31|January 31, 2011]]<br />
*[[WeeklyUpdates/2011-01-24|January 24, 2011]]<br />
*January 17, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-01-10|January 10, 2011]]<br />
*[[WeeklyUpdates/2011-01-03|January 3, 2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
*December 27, 2010 - ''No meeting due to holiday season.''<br />
*[[WeeklyUpdates/2010-12-20|December 20, 2010]]<br />
*December 13, 2010 - ''No meeting due to Work Week''<br />
*[[WeeklyUpdates/2010-12-06|December 6, 2010]]<br />
*[[WeeklyUpdates/2010-11-29|November 29, 2010]]<br />
*[[WeeklyUpdates/2010-11-22|November 22, 2010]]<br />
*[[WeeklyUpdates/2010-11-15|November 15, 2010]]<br />
*[[WeeklyUpdates/2010-11-08|November 08, 2010]]<br />
*[[WeeklyUpdates/2010-11-01|November 01, 2010]]<br />
*[[WeeklyUpdates/2010-10-25|October 25, 2010]]<br />
*[[WeeklyUpdates/2010-10-18|October 18, 2010]]<br />
*[[WeeklyUpdates/2010-10-11|October 11, 2010]]<br />
*[[WeeklyUpdates/2010-10-04|October 4, 2010]]<br />
*[[WeeklyUpdates/2010-09-27|September 27, 2010]]<br />
*[[WeeklyUpdates/2010-09-20|September 20, 2010]]<br />
*[[WeeklyUpdates/2010-09-13|September 13, 2010]]<br />
*September 6, 2010 - ''No meeting due to US holiday''<br />
*[[WeeklyUpdates/2010-08-30|August 30, 2010]]<br />
*[[WeeklyUpdates/2010-08-23|August 23, 2010]]<br />
*[[WeeklyUpdates/2010-08-16|August 16, 2010]]<br />
*[[WeeklyUpdates/2010-08-09|August 9, 2010]]<br />
*[[WeeklyUpdates/2010-08-02|August 2, 2010]]<br />
*[[WeeklyUpdates/2010-07-26|July 26, 2010]]<br />
*[[WeeklyUpdates/2010-07-19|July 19, 2010]]<br />
*[[WeeklyUpdates/2010-07-12|July 12, 2010]]<br />
*July 5, 2010 - ''No meeting due to summit''<br />
*[[WeeklyUpdates/2010-06-28|June 28, 2010]]<br />
*[[WeeklyUpdates/2010-06-21|June 21, 2010]]<br />
*[[WeeklyUpdates/2010-06-14|June 14, 2010]]<br />
*[[WeeklyUpdates/2010-06-07|June 7, 2010]]<br />
*May 31, 2010 - ''No meeting due to US holiday''<br />
*[[WeeklyUpdates/2010-05-24|May 24, 2010]]<br />
*[[WeeklyUpdates/2010-05-17|May 17, 2010]]<br />
*[[WeeklyUpdates/2010-05-10|May 10, 2010]]<br />
*[[WeeklyUpdates/2010-05-03|May 03, 2010]]<br />
*[[WeeklyUpdates/2010-04-26|April 26, 2010]]<br />
*[[WeeklyUpdates/2010-04-19|April 19, 2010]]<br />
*[[WeeklyUpdates/2010-04-12|April 12, 2010]]<br />
*[[WeeklyUpdates/2010-04-05|April 5, 2010]]<br />
*[[WeeklyUpdates/2010-03-29|March 29, 2010]]<br />
*[[WeeklyUpdates/2010-03-22|March 22, 2010]]<br />
*[[WeeklyUpdates/2010-03-15|March 15, 2010]]<br />
*[[WeeklyUpdates/2010-03-08|March 8, 2010]]<br />
*[[WeeklyUpdates/2010-03-01|March 1, 2010]]<br />
*[[WeeklyUpdates/2010-02-22|February 22, 2010]] <br />
*[[WeeklyUpdates/2010-02-15|February 15, 2010]]- No meeting due to holiday, please leave updates in the wiki.<br />
*[[WeeklyUpdates/2010-02-08|February 8, 2010]] <br />
*[[WeeklyUpdates/2010-02-01|February 1, 2010]]<br />
*[[WeeklyUpdates/2010-01-25|January 25, 2010]]<br />
*[[WeeklyUpdates/2010-01-18|January 18, 2010]]- No meeting due to US holiday, please leaves updates in the wiki.<br />
*[[WeeklyUpdates/2010-01-11|January 11, 2010]]- First meeting using [[WeeklyUpdates/Guidance|new procedures]].<br />
*[[WeeklyUpdates/2010-01-04|January 04, 2010]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2009 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2009-12-28|December 28, 2009]]- No meeting due to holiday. Feel free to leave updates in the Wiki. <br />
*[[WeeklyUpdates/2009-12-21|December 21, 2009]] <br />
*[[WeeklyUpdates/2009-12-14|December 14, 2009]] <br />
*[[WeeklyUpdates/2009-12-07|December 07, 2009]]- No meeting due to all day Mozilla Corp meetings. Feel free to leave updates in the Wiki. <br />
*[[WeeklyUpdates/2009-11-30|November 30, 2009]] <br />
*[[WeeklyUpdates/2009-11-23|November 23, 2009]] <br />
*[[WeeklyUpdates/2009-11-16|November 16, 2009]] <br />
*[[WeeklyUpdates/2009-11-09|November 09, 2009]] <br />
*[[WeeklyUpdates/2009-11-02|November 02, 2009]] - Time Change! 19:00 UTC (11am PST) <br />
*[[WeeklyUpdates/2009-10-26|October 26, 2009]] <br />
*[[WeeklyUpdates/2009-10-19|October 19, 2009]] <br />
*[[WeeklyUpdates/2009-10-12|October 12, 2009]] <br />
*[[WeeklyUpdates/2009-10-05|October 05, 2009]] <br />
*[[WeeklyUpdates/2009-09-28|September 28, 2009]] <br />
*[[WeeklyUpdates/2009-09-21|September 21, 2009]] <br />
*[[WeeklyUpdates/2009-09-14|September 14, 2009]] <br />
*[[WeeklyUpdates/2009-09-07|September 07, 2009]] - No Meeting due to [http://en.wikipedia.org/wiki/Labor_Day Labor Day] Holiday <br />
*[[WeeklyUpdates/2009-08-31|August 31, 2009]] <br />
*[[WeeklyUpdates/2009-08-24|August 24, 2009]] <br />
*[[WeeklyUpdates/2009-08-17|August 17, 2009]] <br />
*[[WeeklyUpdates/2009-08-10|August 10, 2009]] <br />
*[[WeeklyUpdates/2009-08-03|August 03, 2009]] <br />
*[[WeeklyUpdates/2009-07-27|July 27, 2009]] <br />
*[[WeeklyUpdates/2009-07-20|July 20, 2009]] <br />
*[[WeeklyUpdates/2009-07-13|July 13, 2009]] <br />
*[[WeeklyUpdates/2009-07-06|July 06, 2009]] <br />
*[[WeeklyUpdates/2009-06-29|June 29, 2009]] <br />
*[[WeeklyUpdates/2009-06-22|June 22, 2009]] <br />
*[[WeeklyUpdates/2009-06-15|June 15, 2009]] <br />
*[[WeeklyUpdates/2009-06-08|June 08, 2009]] <br />
*[[WeeklyUpdates/2009-06-01|June 01, 2009]] <br />
*[[WeeklyUpdates/2009-05-25|May 25, 2009]] - No meeting due to US Holiday: [http://en.wikipedia.org/wiki/Memorial_day Memorial Day]. Feel free to leave status! <br />
*[[WeeklyUpdates/2009-05-18|May 18, 2009]] <br />
*[[WeeklyUpdates/2009-05-11|May 11, 2009]] <br />
*[[WeeklyUpdates/2009-05-04|May 04, 2009]] <br />
*April 27, 2009 - no update meeting this week due to on-site event <br />
*[[WeeklyUpdates/2009-04-20|April 20, 2009]] <br />
*[[WeeklyUpdates/2009-04-13|April 13, 2009]] <br />
*[[WeeklyUpdates/2009-04-06|April 06, 2009]] <br />
*[[WeeklyUpdates/2009-03-30|March 30, 2009]] <br />
*[[WeeklyUpdates/2009-03-23|March 23, 2009]] <br />
*[[WeeklyUpdates/2009-03-16|March 16, 2009]] <br />
*[[WeeklyUpdates/2009-03-09|March 09, 2009]] <br />
*[[WeeklyUpdates/2009-03-02|March 02, 2009]] <br />
*[[WeeklyUpdates/2009-02-23|February 23, 2009]] <br />
*February 16, 2009 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2009-02-09|February 09, 2009]] <br />
*[[WeeklyUpdates/2009-02-02|February 02, 2009]] <br />
*[[WeeklyUpdates/2009-01-26|January 26, 2009]] <br />
*January 19, 2009 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2009-01-12|January 12, 2009]] <br />
*[[WeeklyUpdates/2009-01-05|January 05, 2009]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2008 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2008-12-29|December 29, 2008]] <br />
*[[WeeklyUpdates/2008-12-22|December 22, 2008]] <br />
*[[WeeklyUpdates/2008-12-15|December 15, 2008]] <br />
*[[WeeklyUpdates/2008-12-08|December 08, 2008]] <br />
*[[WeeklyUpdates/2008-12-01|December 01, 2008]] <br />
*[[WeeklyUpdates/2008-11-24|November 24, 2008]] <br />
*[[WeeklyUpdates/2008-11-17|November 17, 2008]] <br />
*[[WeeklyUpdates/2008-11-10|November 10, 2008]] <br />
*[[WeeklyUpdates/2008-11-03|November 03, 2008]] <br />
*[[WeeklyUpdates/2008-10-27|October 27, 2008]] <br />
*[[WeeklyUpdates/2008-10-20|October 20, 2008]] <br />
*[[WeeklyUpdates/2008-10-13|October 13, 2008]] <br />
*[[WeeklyUpdates/2008-10-06|October 06, 2008]] <br />
*[[WeeklyUpdates/2008-09-29|September 29, 2008]] <br />
*[[WeeklyUpdates/2008-09-22|September 22, 2008]] <br />
*[[WeeklyUpdates/2008-09-15|September 15, 2008]] <br />
*[[WeeklyUpdates/2008-09-08|September 08, 2008]] <br />
*September 01, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-08-25|August 25, 2008]] <br />
*[[WeeklyUpdates/2008-08-18|August 18, 2008]] <br />
*[[WeeklyUpdates/2008-08-11|August 11, 2008]] <br />
*[[WeeklyUpdates/2008-08-04|August 04, 2008]] <br />
*July 28, 2008 - No Meeting due to Summit <br />
*[[WeeklyUpdates/2008-07-21|July 21, 2008]] <br />
*[[WeeklyUpdates/2008-07-14|July 14, 2008]] <br />
*[[WeeklyUpdates/2008-07-07|July 07, 2008]] <br />
*[[WeeklyUpdates/2008-06-30|June 30, 2008]] <br />
*[[WeeklyUpdates/2008-06-23|June 23, 2008]] <br />
*[[WeeklyUpdates/2008-06-16|June 16, 2008]] <br />
*[[WeeklyUpdates/2008-06-09|June 09, 2008]] <br />
*[[WeeklyUpdates/2008-06-02|June 02, 2008]] <br />
*May 26, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-05-19|May 19, 2008]] <br />
*[[WeeklyUpdates/2008-05-12|May 12, 2008]] <br />
*[[WeeklyUpdates/2008-05-05|May 05, 2008]] <br />
*[[WeeklyUpdates/2008-04-28|April 28, 2008]] <br />
*[[WeeklyUpdates/2008-04-21|April 21, 2008]] <br />
*[[WeeklyUpdates/2008-04-14|April 14, 2008]] <br />
*[[WeeklyUpdates/2008-04-07|April 07, 2008]] <br />
*[[WeeklyUpdates/2008-03-31|March 31, 2008]] <br />
*[[WeeklyUpdates/2008-03-24|March 24, 2008]] <br />
*[[WeeklyUpdates/2008-03-17|March 17, 2008]] <br />
*[[WeeklyUpdates/2008-03-10|March 10, 2008]] <br />
*[[WeeklyUpdates/2008-03-03|March 03, 2008]] <br />
*[[WeeklyUpdates/2008-02-25|February 25, 2008]] <br />
*February 18, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-02-11|February 11, 2008]] <br />
*[[WeeklyUpdates/2008-02-04|February 04, 2008]] <br />
*[[WeeklyUpdates/2008-01-28|January 28, 2008]] <br />
*January 21, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-01-14|January 14, 2008]] <br />
*[[WeeklyUpdates/2008-01-07|January 07, 2008]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2007 <br />
|-<br />
|<br />
*December 31, 2007 - No Meeting due to US holiday season <br />
*December 24, 2007 - No Meeting due to US holiday season <br />
*[[WeeklyUpdates/2007-12-17|December 17, 2007]] <br />
*[[WeeklyUpdates/2007-12-10|December 10, 2007]] <br />
*[[WeeklyUpdates/2007-12-03|December 03, 2007]] <br />
*[[WeeklyUpdates/2007-11-26|November 26, 2007]] <br />
*[[WeeklyUpdates/2007-11-19|November 19, 2007]] <br />
*November 12, 2007 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2007-11-05|November 05, 2007]] <br />
*[[WeeklyUpdates/2007-10-29|October 29, 2007]] <br />
*[[WeeklyUpdates/2007-10-22|October 22, 2007]] <br />
*[[WeeklyUpdates/2007-10-15|October 15, 2007]] <br />
*[[WeeklyUpdates/2007-10-08|October 08, 2007]] <br />
*[[WeeklyUpdates/2007-10-01|October 01, 2007]] <br />
*[[WeeklyUpdates/2007-09-24|September 24, 2007]] <br />
*[[WeeklyUpdates/2007-09-17|September 17, 2007]] <br />
*[[WeeklyUpdates/2007-09-10|September 10, 2007]] <br />
*[[WeeklyUpdates/2007-08-27|August 27, 2007]] <br />
*[[WeeklyUpdates/2007-08-20|August 20, 2007]] <br />
*[[WeeklyUpdates/2007-08-13|August 13, 2007]] <br />
*[[WeeklyUpdates/2007-08-06|August 6, 2007]] <br />
*[[WeeklyUpdates/2007-07-30|July 30, 2007]] <br />
*[[WeeklyUpdates/2007-07-23|July 23, 2007]] <br />
*[[WeeklyUpdates/2007-07-16|July 16, 2007]] <br />
*[[WeeklyUpdates/2007-07-09|July 9, 2007]] <br />
*[[WeeklyUpdates/2007-07-02|July 2, 2007]] <br />
*[[WeeklyUpdates/2007-06-25|June 25, 2007]] <br />
*[[WeeklyUpdates/2007-06-18|June 18, 2007]] <br />
*[[WeeklyUpdates/2007-06-11|June 11, 2007]] <br />
*[[WeeklyUpdates/2007-06-04|June 4, 2007]] <br />
*[[WeeklyUpdates/2007-05-21|May 21, 2007]] <br />
*[[WeeklyUpdates/2007-05-14|May 14, 2007]] <br />
*[[WeeklyUpdates/2007-05-07|May 7, 2007]] <br />
*[[WeeklyUpdates/2007-04-30|April 30, 2007]] <br />
*[[WeeklyUpdates/2007-04-23|April 23, 2007]] <br />
*[[WeeklyUpdates/2007-04-16|April 16, 2007]] <br />
*[[WeeklyUpdates/2007-04-09|April 9, 2007]] <br />
*[[WeeklyUpdates/2007-04-02|April 2, 2007]] <br />
*[[WeeklyUpdates/2007-03-26|March 26, 2007]] <br />
*[[WeeklyUpdates/2007-03-19|March 19, 2007]] <br />
*[[WeeklyUpdates/2007-03-12|March 12, 2007]] <br />
*[[WeeklyUpdates/2007-03-05|March 5, 2007]] <br />
*[[WeeklyUpdates/2007-02-26|February 26, 2007]] <br />
*[[WeeklyUpdates/2007-02-12|February 12, 2007]] <br />
*[[WeeklyUpdates/2007-02-05|February 5, 2007]] <br />
*[[WeeklyUpdates/2007-01-29|January 29, 2007]] <br />
*[[WeeklyUpdates/2007-01-22|January 22, 2007]] <br />
*[[WeeklyUpdates/2007-01-08|January 08, 2007]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2006 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2006-12-18|December 18, 2006]] <br />
*[[WeeklyUpdates/2006-12-11|December 11, 2006]] <br />
*[[WeeklyUpdates/2006-12-04|December 4, 2006]] <br />
*[[WeeklyUpdates/2006-11-27|November 27, 2006]] <br />
*[[WeeklyUpdates/2006-11-13|November 13, 2006]] <br />
*[[WeeklyUpdates/2006-11-06|November 6, 2006]] <br />
*[[WeeklyUpdates/2006-10-30|October 30, 2006]] <br />
*[[WeeklyUpdates/2006-10-23|October 23, 2006]] <br />
*[[WeeklyUpdates/2006-10-16|October 16, 2006]] <br />
*[[WeeklyUpdates/2006-10-09|October 9, 2006]] <br />
*[[WeeklyUpdates/2006-10-02|October 2, 2006]] <br />
*[[WeeklyUpdates/2006-09-25|September 25, 2006]] <br />
*[[WeeklyUpdates/2006-09-18|September 18, 2006]] <br />
*[[WeeklyUpdates/2006-09-11|September 11, 2006]] <br />
*September 4, 2006 - No Meeting due to US and Canadian Holiday <br />
*[[WeeklyUpdates/2006-08-28|August 28, 2006]] <br />
*[[WeeklyUpdates/2006-08-21|August 21, 2006]] <br />
*[[WeeklyUpdates/2006-08-14|August 14, 2006]] <br />
*[[WeeklyUpdates/2006-08-07|August 07, 2006]] <br />
*[[WeeklyUpdates/2006-07-31|July 31, 2006]] <br />
*[[WeeklyUpdates/2006-07-24|July 24, 2006]] <br />
*[[WeeklyUpdates/2006-07-17|July 17, 2006]] <br />
*[[WeeklyUpdates/2006-07-10|July 10, 2006]] <br />
*July 3, 2006 - No Meeting due to US Holiday <br />
*June 26, 2006 - No Meeting <br />
*[[WeeklyUpdates/2006-06-19|June 19, 2006]] <br />
*[[WeeklyUpdates/2006-06-12|June 12, 2006]] <br />
*[[WeeklyUpdates/2006-06-05|June 05, 2006]] <br />
*May 29, 2006 -- No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2006-05-22|May 22, 2006]] <br />
*May 15, 2006 -- No Meeting due to XTech 2006 Conference <br />
*[[WeeklyUpdates/2006-05-08|May 08, 2006]] <br />
*[[WeeklyUpdates/2006-05-01|May 01, 2006]] <br />
*[[WeeklyUpdates/2006-04-24|April 24, 2006]] <br />
*[[WeeklyUpdates/2006-04-17|April 17, 2006]] <br />
*[[WeeklyUpdates/2006-04-10|April 10, 2006]] <br />
*[[WeeklyUpdates/2006-04-03|April 03, 2006]] <br />
*[[WeeklyUpdates/2006-03-27|March 27, 2006]]<br />
|}<br />
<br />
''Note: Older [http://www-archive.mozilla.org/status/minutes.html meeting minutes] and [http://www-archive.mozilla.org/status/ status updates] are available on the www.mozilla.org archive site.''<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Apps&diff=1136744Apps2016-06-11T00:02:26Z<p>MykMelez: update to reflect end of WADI</p>
<hr />
<div><br />
== Web App Developer Initiative ==<br />
<br />
In 2015, Mozilla launched an initiative to energize web app development, the Web App Developer Initiative (WADI). The initiative focused on several emerging Web APIs -- [http://www.w3.org/TR/service-workers/ service workers], [http://www.w3.org/TR/push-api/ web push], and the [http://www.w3.org/TR/appmanifest/ W3C web app manifest] -- and invited the participation of browser makers, web frameworks, cloud service providers, and content providers.<br />
<br />
The WADI initiative has now ended, but Mozilla continues to develop and evangelize these and other modern web app development technologies along with the other participants. What unites all these disparate parties is a belief in the power of web apps that work reliably with bad networks, reengage users with notifications, and can be installed like native apps. We believe developers will use these technologies to deliver experiences that will redefine the role of the web.<br />
<br />
For more information about these APIs and their availability in Mozilla products, see the [https://developer.mozilla.org/en-US/Apps Mozilla Developer Network's App Center] and [https://platform-status.mozilla.org/ Firefox Platform Status].</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Marketplace/FutureofMarketplaceFAQ&diff=1134929Marketplace/FutureofMarketplaceFAQ2016-05-30T17:36:24Z<p>MykMelez: describe alternative to Marketplace/runtimes</p>
<hr />
<div>{{Marketplace_banner}}<br />
= The Future of Marketplace FAQ =<br />
As of March 29, 2016, the Firefox Marketplace will no longer support Android, Desktop, Tablets, or payments of any kind (paid apps or in-app payments). Payments are being deactivated, and the Web Runtime is being removed in [[RapidRelease/Calendar|Firefox 47]] for Android and [[RapidRelease/Calendar|Firefox 48]] for Windows, Mac OS X, and Linux.<br />
<br />
; Q. What does it mean for applications already in Firefox Marketplace?<br />
: Applications in Marketplace that are compatible with Firefox OS will continue to work on Firefox OS; if they are also compatible with other platforms (like Desktop or Android), then they stop working on those platforms. If the app is not listed as compatible with Firefox OS, it will be disabled (not listed in the catalog), but still accessible to the owner on the developer portal.<br />
<br />
; Q. What does it mean for new applications submitted to marketplace?<br />
: Marketplace will discontinue submission of apps for Desktop, Android, and Tablets on March 29, 2016. It will also remove the Paid Apps options to the submission process. We will continue to review apps submitted for Firefox OS. (We will also discontinue the special submission process for China and for low memory devices, but those changes are already live.)<br />
<br />
; Q. Why is this happening in March?<br />
: This is to give developers time to make changes to their apps while the Firefox release schedule continues once Developer Edition of Firefox 47 is out. (For reference, Firefox 47's timetable is roughly: 2016/01/25 Nightly &#8594; 2016/03/07 Aurora &#8594; 2016/04/18 Beta &#8594; 2016/06/06 Release.)<br />
<br />
; Q. Where will applications be hosted if marketplace is shut down?<br />
: Marketplace is not shutting down. Packaged apps will continue to be hosted on Marketplace and continue to serve Firefox OS users at least until January 2018. Future plans will be reviewed around mid-2017.<br />
<br />
; Q. If I am a developer with a paid app or have in-app payments in my app, what should I do?<br />
: You have several choices: you can make your app free, you can use another payment provider for in-app payments, or you can do nothing -- if you do nothing, your app will be disabled.<br />
<br />
To change your app to free, login to the [https://marketplace.firefox.com/developers developer portal], select your app, and change your app to free by selecting the Free tab, then the Compatibility tab under the Edit Listing area, and changing it to Free for Firefox OS.<br />
<br />
; Q. What's the alternative to Marketplace and the Web Runtime for distribution of modern web apps?<br />
<br />
[https://developer.mozilla.org/en-US/Apps/Progressive Progressive Web Apps] use existing and emerging web technologies to create compelling app-like experiences on the Web without requiring a dedicated application runtime and distribution channel.<br />
<br />
Progressive Web Apps work in any browser, gaining capabilities like advanced offline caching, push notifications, homescreen icons, and fullscreen mode in modern browsers; while gracefully degrading to regular web apps in older ones.<br />
<br />
Firefox has begun to implement support for Progressive Web Apps. For more information about them, see [https://developer.mozilla.org/en-US/Apps/Progressive App center > Progressive Web Apps] on the Mozilla Developer Network, [https://developers.google.com/web/progressive-web-apps/ Progressive Web Apps] on Google Developers, and [https://infrequently.org/2015/06/progressive-apps-escaping-tabs-without-losing-our-soul/ Progressive Web Apps: Escaping Tabs Without Losing Our Soul] on Alex Russell's blog.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2016-05-23&diff=1133899WeeklyUpdates/2016-05-232016-05-23T17:58:15Z<p>MykMelez: thank potch</p>
<hr />
<div><br />
{{WeeklyUpdateNav}}<br />
* Every Monday @ 11:00am Pacific Time (19:00 UTC) <br />
* http://air.mozilla.org/ to watch and listen<br />
* join irc.mozilla.org #airmozilla for backchannel discussion<br />
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak. <br />
{{conf|8600}}<br />
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==<br />
<br />
Thanks to potch for fearlessly leading this meeting every week!<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
* <p>''' [https://quality.mozilla.org/event/bug-triage-day-111/ Weekly Bug Triage Day] '''</p><br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
* <p>''' [https://quality.mozilla.org/event/bug-verification-day-118/ Weekly Bug Verification Day] '''</p><br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<p>'''Monthly Speaker Series: Interview with [http://kk.org Kevin Kelly]</p><br />
<p>Join us at '''10:30am PT / 1:30pm ET / 6:30pm UTC on [https://air.mozilla.org/twelve-technology-forces-shaping-the-next-30-years-interview-with-kevin-kelly/ Air Mozilla] and at our Mozilla San Francisco Commons''' to hear Wired Founder & Senior Maverick and Futurist [http://kk.org/ Kevin Kelly] share on "Twelve Technology Forces Shaping the Next 30 Years." A few teasers:</p><br />
<p><ul><br />
<li>Augmented and virtual reality experiences that are closely woven into every mundane daily activity.</li><br />
<li>Seamlessly-merged media, as books, web pages, videos, and commentary commingle and are constantly updated in real-time.</li><br />
<li>Artificial intelligence embedded in everything, everywhere.</li><br />
<li>Ubiquitous and irrepressible surveillance.</li></ul></p><br />
<br />
<p>Our own [https://mozillians.org/en-US/u/jjensen/ John Jensen] will draw off of Kelly's upcoming book, "[http://www.amazon.com/Inevitable-Understanding-Technological-Forces-Future/dp/0525428089 The Inevitable]," to interview Kevin about these longer-term trends, and what they mean for mozilla.</p><br />
<br />
<p>Full details on the [[Speaker_Series#Thursday.2C_May_26_.40_Mozilla_SF_-_10:30am_PT_.2F_1:30pm_ET_.2F_6:30pm_UTC_.2B_Air_Mozilla|Speaker Series page]].* </p>'''<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<p>Last Day for Dino Tank submissions for London http://mozilladinotank.tumblr.com</p><br />
<br />
=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===<br />
<br />
=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Speakers ==<br />
<br />
The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.<br />
<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME Presenter]<br />
! Title<br />
! Topic<br />
! Location<br />
! Sharing<br />
! Media<br />
! More Details<br />
|-<br />
| Who Are You?<br />
| What Do You Do?<br />
| What are you going to talk about?<br />
| Where are you presenting from? (Moz Space, your house, space)<br />
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Tim Murray <br />
| Creative Director<br />
| Update on Brand Identity work<br />
| SF Commons <br />
| No<br />
| https://docs.google.com/a/mozilla.com/presentation/d/1-qZA9aItF-xoIJ0EYg9lurt8xrqPXuGncOcxqIciPHw/edit?usp=sharing<br />
|- <br />
|Potch<br />
|View Source 2016 Berlin and Seattle Announcement!<br />
|MTV<br />
|www.viewsourceconf.org<br />
|<br />
|Take advantage of your View Source 2016 Mozilla Employee discount mozillaemployeeten<br />
|We’re excited to announce two Mozilla View Source Conferences this year: September 12th-14th in Berlin and November 1st-3rd in Seattle. View Source is a technical conference for web creators, by web creators.Find out more about the conference (and get tickets) at the website: http://viewsourceconf.org. To keep up with speaker announcements and calls for proposals, follow us on Twitter: http://twitter.com/viewsourceconf. Our hashtag is: #ViewSource<br />
|-<br />
| [https://mozillians.org/u/lshapiro Larissa Shapiro]<br />
| 15 Outreachy Participants, 8 countries, three minutes! <br />
| Introducing the summer 2016 Outreachy cohort!<br />
| MTV<br />
| <br />
| <br />
| https://wiki.mozilla.org/Outreachy<br />
|}<br />
<br />
= Welcome! =<br />
<br />
Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.<br />
<br />
== Introducing New Volunteers ==<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! [https://mozillians.org/u/USERNAME New Volunteer]<br />
! [https://mozillians.org/u/USERNAME Introduced by]<br />
! Speaker location<br />
! New Volunteer location<br />
! Will be working on<br />
|-<br />
| ''Who is the new volunteer?''<br />
| ''Who will be introducing that person?''<br />
| ''Where is the introducer?''<br />
| ''Where will the new person be contributing from?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Introducing New Hires ==<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! New Hire location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''Where is the introducer?''<br />
| ''Where will the new person be working from?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
| Alexander Salkever<br />
| Jascha Kaykas-Wolff<br />
| San Francisco<br />
| San Francisco<br />
| Marketing<br />
|-<br />
| Izette Sher Herrera<br />
| Winnie Aoieong<br />
| San Francisco<br />
| San Francisco<br />
| Finance<br />
|-<br />
| Jennifer Magana<br />
| Ari Jaaksi<br />
| Mountain View<br />
| Mountain View <br />
| Steering Committee<br />
|-<br />
| Diane Hosfelt<br />
| Jack Moffitt<br />
| Albuquerque, NM (remote)<br />
| UK (remote)<br />
| Research - Servo<br />
|-<br />
| Manish Goregaokar<br />
| Jack Moffitt<br />
| Albuquerque, NM (remote)<br />
| Mumbai (remote)<br />
| Research - Servo<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table wikitable"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! New Hire location<br />
! Will be working on<br />
|-<br />
| Daniel Etcovitch<br />
| Brian Smith<br />
| MV<br />
| MV<br />
| Legal<br />
|-<br />
| Sam Fang<br />
| Maria Popova<br />
| MV<br />
| SF<br />
| Product Management<br />
|-<br />
| Jonathan Almeida<br />
| Michael Comella<br />
| MV<br />
| SF<br />
| Mobile UI<br />
|-<br />
| Scott Carr<br />
| Aaron Turon<br />
| MV<br />
| SF<br />
| Rust<br />
|-<br />
| Jaideep Bhoosreddy<br />
| Gabriel Luong<br />
| MV<br />
| SF<br />
| Content Tools<br />
|-<br />
| Matthew Wes<br />
| Marshall Erwin<br />
| MV<br />
| MV<br />
| Legal<br />
|-<br />
| Hassan Ali<br />
| Eli Perelman<br />
| Vidyo<br />
| SF<br />
| Engineering Operations<br />
|-<br />
| Nathan Hakkakzadeh<br />
| Gregory Szorc<br />
| MV<br />
| SF<br />
| Build System<br />
|-<br />
| Purushotham Swaminathan<br />
| Katie Parlante<br />
| MV<br />
| MV<br />
| Firefox Measurement <br />
|-<br />
| Cameron Swords<br />
| Aaron Turon<br />
| MV<br />
| SF<br />
| Rust<br />
|-<br />
| Maximillian Von Briesen<br />
| Brian Grinstead<br />
| MV<br />
| MV<br />
| Firefox Content Tools<br />
|-<br />
| Francesco Polizzi<br />
| Chris More<br />
| MV<br />
| MV<br />
| FFX Product Marketing<br />
|-<br />
| Dominick Namis<br />
| Janis Greenspan<br />
| MV<br />
| SF<br />
| Brand Engagement <br />
|-<br />
| Emily Shirtz <br />
| Michael Ham <br />
| MV<br />
| SF<br />
| Brand Engagement <br />
|-<br />
| Josephine Kao <br />
| Michael Ham<br />
| MV<br />
| SF<br />
| Brand Engagement <br />
|-<br />
|}<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Connected Devices ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== Web QA ====<br />
<br />
==== QA Community ====<br />
<br />
=== Engineering Productivity (Automation & Tools) ===<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]<br />
<br />
==== PR ====<br />
<br />
==== Events ====<br />
<br />
==== Social Support ====<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Apps/WebRT&diff=1126531Apps/WebRT2016-04-07T16:46:42Z<p>MykMelez: simplify structure</p>
<hr />
<div>The Web Runtime project built application runtimes that enabled users to install and run Open Web Apps on Android, Windows, Mac, and Linux. The runtime for desktop OSes shipped as part of Firefox for Desktop in 2012, while the runtime for Android shipped as part of Firefox for Android in 2013. Both projects were explicitly ended in 2015, and the runtimes were removed from Firefox in 2016.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Apps/WebRT&diff=1126502Apps/WebRT2016-04-07T15:48:07Z<p>MykMelez: explain fate of runtimes</p>
<hr />
<div>= Web Runtime =<br />
<br />
== Overview ==<br />
<br />
The Web Runtime project built application runtimes that enabled users to install and run Open Web Apps on Android, Windows, Mac, and Linux. The runtime for desktop OSes shipped as part of Firefox for Desktop in 2012, while the runtime for Android shipped as part of Firefox for Android in 2013. Both projects were explicitly ended in 2015, and the runtimes were removed from Firefox in 2016.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=MozillaBuild&diff=1126147MozillaBuild2016-04-05T17:32:59Z<p>MykMelez: correct capitalization of Mintty</p>
<hr />
<div>=== Overview ===<br />
MozillaBuild is a meta-installer that provides everything needed to build Mozilla on Windows, sans Visual C++. Its source lives in https://hg.mozilla.org/mozilla-build/. Bugs should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=MozillaBuild mozilla.org :: MozillaBuild]. For information about building Mozilla on Win32, [https://developer.mozilla.org/en/docs/Windows_Build_Prerequisites see the Mozilla Developer Center page].<br />
<br />
=== Current Version ===<br />
The current version of MozillaBuild is 2.2.0. It is available on [https://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe ftp.mozilla.org].<br />
<br />
=== To Upgrade From A Previous Version ===<br />
<br />
Upgrading from an earlier MozillaBuild installation is straightforward but each step is important.<br />
<br />
# Delete your current MozillaBuild environment by moving your MozillaBuild folder into the trash. If you can't remove the existing installation, you probably have a terminal open or ssh-agent running. Terminate that process and try again.<br />
# Install the new MozillaBuild release. <br />
# If you had previously enabled Mintty, you will need to do so again by adding <tt>SET USE_MINTTY=1</tt> to the top of start-shell.bat.<br />
# Run <tt>./mach mercurial-setup --update-only</tt> to ensure that the version-control-tools repository is current (<b>Mercurial extensions may break otherwise</b>).<br />
# Clobber any trees you have by running <tt>./mach clobber</tt> (<b>build errors may occur otherwise</b>).<br />
<br />
=== Release Notes ===<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/j4MUKzoDOlQ/gHH7w495AgAJ MozillaBuild 2.2.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/qpO21XQaNV8/-D5mNKqnCAAJ MozillaBuild 2.1.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/xJjMtp1_GV0/-zVzSMuDNVcJ MozillaBuild 2.0.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/XnFg0p1DJVI/laRQeGJDviwJ MozillaBuild 1.11.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/rslz21w1vng/P0jvA5y4vL4J MozillaBuild 1.10.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/cUqsdWEWIcw/HDyhJMz3-ysJ MozillaBuild 1.9.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/_9U6160_oyA/dWWpklVicwkJ MozillaBuild 1.8.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/XRecAHF-H28/aSbrdKJLUNoJ MozillaBuild 1.7]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/J3sBNBU1SvY/THhkqOCAvvYJ MozillaBuild 1.6]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/s7PsRYJyHbI/AsLz9dVgwIUJ MozillaBuild 1.5.1]: added YASM for WebM code in Firefox 4.<br />
* [http://blog.mozilla.com/ted/2010/07/22/mozillabuild-1-5/ MozillaBuild 1.5]: Mercurial 1.5.4, Python 2.6.5, and support for Visual Studio 2010.<br />
* [http://blog.mozilla.com/ted/2009/07/24/mozillabuild-1-4/ MozillaBuild 1.4]: Windows x64 compatibility and other.<br />
* [http://blog.mozilla.com/ted/2008/06/16/mozillabuild-13/ MozillaBuild 1.3]<br />
* [[MozillaBuild:ReleaseNotes:1.2]]<br />
<br />
There are no release notes for 1.1 and below.<br />
<br />
=== Historic Versions ===<br />
Old versions of MozillaBuild can also be found on [https://ftp.mozilla.org/pub/mozilla/libraries/win32/ ftp.mozilla.org].</div>MykMelezhttps://wiki.mozilla.org/index.php?title=MozillaBuild&diff=1126144MozillaBuild2016-04-05T17:30:59Z<p>MykMelez: correct the command used to enable MinTTY</p>
<hr />
<div>=== Overview ===<br />
MozillaBuild is a meta-installer that provides everything needed to build Mozilla on Windows, sans Visual C++. Its source lives in https://hg.mozilla.org/mozilla-build/. Bugs should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=MozillaBuild mozilla.org :: MozillaBuild]. For information about building Mozilla on Win32, [https://developer.mozilla.org/en/docs/Windows_Build_Prerequisites see the Mozilla Developer Center page].<br />
<br />
=== Current Version ===<br />
The current version of MozillaBuild is 2.2.0. It is available on [https://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe ftp.mozilla.org].<br />
<br />
=== To Upgrade From A Previous Version ===<br />
<br />
Upgrading from an earlier MozillaBuild installation is straightforward but each step is important.<br />
<br />
# Delete your current MozillaBuild environment by moving your MozillaBuild folder into the trash. If you can't remove the existing installation, you probably have a terminal open or ssh-agent running. Terminate that process and try again.<br />
# Install the new MozillaBuild release. <br />
# If you had previously enabled minTTY, you will need to do so again by adding <tt>SET USE_MINTTY=1</tt> to the top of start-shell.bat.<br />
# Run <tt>./mach mercurial-setup --update-only</tt> to ensure that the version-control-tools repository is current (<b>Mercurial extensions may break otherwise</b>).<br />
# Clobber any trees you have by running <tt>./mach clobber</tt> (<b>build errors may occur otherwise</b>).<br />
<br />
=== Release Notes ===<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/j4MUKzoDOlQ/gHH7w495AgAJ MozillaBuild 2.2.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/qpO21XQaNV8/-D5mNKqnCAAJ MozillaBuild 2.1.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/xJjMtp1_GV0/-zVzSMuDNVcJ MozillaBuild 2.0.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/XnFg0p1DJVI/laRQeGJDviwJ MozillaBuild 1.11.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/rslz21w1vng/P0jvA5y4vL4J MozillaBuild 1.10.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/cUqsdWEWIcw/HDyhJMz3-ysJ MozillaBuild 1.9.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/_9U6160_oyA/dWWpklVicwkJ MozillaBuild 1.8.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/XRecAHF-H28/aSbrdKJLUNoJ MozillaBuild 1.7]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/J3sBNBU1SvY/THhkqOCAvvYJ MozillaBuild 1.6]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/s7PsRYJyHbI/AsLz9dVgwIUJ MozillaBuild 1.5.1]: added YASM for WebM code in Firefox 4.<br />
* [http://blog.mozilla.com/ted/2010/07/22/mozillabuild-1-5/ MozillaBuild 1.5]: Mercurial 1.5.4, Python 2.6.5, and support for Visual Studio 2010.<br />
* [http://blog.mozilla.com/ted/2009/07/24/mozillabuild-1-4/ MozillaBuild 1.4]: Windows x64 compatibility and other.<br />
* [http://blog.mozilla.com/ted/2008/06/16/mozillabuild-13/ MozillaBuild 1.3]<br />
* [[MozillaBuild:ReleaseNotes:1.2]]<br />
<br />
There are no release notes for 1.1 and below.<br />
<br />
=== Historic Versions ===<br />
Old versions of MozillaBuild can also be found on [https://ftp.mozilla.org/pub/mozilla/libraries/win32/ ftp.mozilla.org].</div>MykMelezhttps://wiki.mozilla.org/index.php?title=MozillaBuild&diff=1126143MozillaBuild2016-04-05T17:30:22Z<p>MykMelez: move 'enable MinTTY' step above steps that require being in the shell already</p>
<hr />
<div>=== Overview ===<br />
MozillaBuild is a meta-installer that provides everything needed to build Mozilla on Windows, sans Visual C++. Its source lives in https://hg.mozilla.org/mozilla-build/. Bugs should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=MozillaBuild mozilla.org :: MozillaBuild]. For information about building Mozilla on Win32, [https://developer.mozilla.org/en/docs/Windows_Build_Prerequisites see the Mozilla Developer Center page].<br />
<br />
=== Current Version ===<br />
The current version of MozillaBuild is 2.2.0. It is available on [https://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe ftp.mozilla.org].<br />
<br />
=== To Upgrade From A Previous Version ===<br />
<br />
Upgrading from an earlier MozillaBuild installation is straightforward but each step is important.<br />
<br />
# Delete your current MozillaBuild environment by moving your MozillaBuild folder into the trash. If you can't remove the existing installation, you probably have a terminal open or ssh-agent running. Terminate that process and try again.<br />
# Install the new MozillaBuild release. <br />
# If you had previously enabled minTTY, you will need to do so again by adding <tt>USE_MINTTY=1</tt> to the top of start-shell.bat.<br />
# Run <tt>./mach mercurial-setup --update-only</tt> to ensure that the version-control-tools repository is current (<b>Mercurial extensions may break otherwise</b>).<br />
# Clobber any trees you have by running <tt>./mach clobber</tt> (<b>build errors may occur otherwise</b>).<br />
<br />
=== Release Notes ===<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/j4MUKzoDOlQ/gHH7w495AgAJ MozillaBuild 2.2.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/qpO21XQaNV8/-D5mNKqnCAAJ MozillaBuild 2.1.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/xJjMtp1_GV0/-zVzSMuDNVcJ MozillaBuild 2.0.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/XnFg0p1DJVI/laRQeGJDviwJ MozillaBuild 1.11.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/rslz21w1vng/P0jvA5y4vL4J MozillaBuild 1.10.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/cUqsdWEWIcw/HDyhJMz3-ysJ MozillaBuild 1.9.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/_9U6160_oyA/dWWpklVicwkJ MozillaBuild 1.8.0]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/XRecAHF-H28/aSbrdKJLUNoJ MozillaBuild 1.7]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/J3sBNBU1SvY/THhkqOCAvvYJ MozillaBuild 1.6]<br />
* [https://groups.google.com/d/msg/mozilla.dev.platform/s7PsRYJyHbI/AsLz9dVgwIUJ MozillaBuild 1.5.1]: added YASM for WebM code in Firefox 4.<br />
* [http://blog.mozilla.com/ted/2010/07/22/mozillabuild-1-5/ MozillaBuild 1.5]: Mercurial 1.5.4, Python 2.6.5, and support for Visual Studio 2010.<br />
* [http://blog.mozilla.com/ted/2009/07/24/mozillabuild-1-4/ MozillaBuild 1.4]: Windows x64 compatibility and other.<br />
* [http://blog.mozilla.com/ted/2008/06/16/mozillabuild-13/ MozillaBuild 1.3]<br />
* [[MozillaBuild:ReleaseNotes:1.2]]<br />
<br />
There are no release notes for 1.1 and below.<br />
<br />
=== Historic Versions ===<br />
Old versions of MozillaBuild can also be found on [https://ftp.mozilla.org/pub/mozilla/libraries/win32/ ftp.mozilla.org].</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub&diff=1125147GitHub2016-03-31T16:36:08Z<p>MykMelez: fix table structure bug</p>
<hr />
<div>This page is specifically about [https://github.com/mozilla the "mozilla" organization on github]. There are several other github organizations you may be interested in, cf. the incomplete list [[#other_github|below]].<br />
<div id="contact"><br />
{| class="wikitable"<br />
|-<br />
! [[File:Red_question_mark.png|144px|Send us an email!|link=]] Got a question?<br />
|-<br />
| Email {{emailentry|github-owners|mozilla.org|at=is}} <br /><br />
Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& mozilla.org :: Github: Administration] <br /><br />
irc #github on [[IRC|moznet]]<br />
|}<br />
<br />
== Recommendations and FAQ ==<br />
<br />
=== Where should I ask additional questions? ===<br />
* Send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and we'll respond right away! We're also available on #github on irc.<br />
<br />
=== How do I hook up a new 3rd party application to a repository in the mozilla org? ===<br />
3rd party applications can easily impact many other repositories than the initial one. For that reason, the following steps are strongly encouraged:<br />
# Create yourself a new github user for this repository.<br />
# Make them an admin of the repository(s) temporarily.<br />
# Sign in as the new github user and setup the 3rd party application.<br />
# Log back into your normal account.<br />
# Try to reduce access of that user from an admin of the repository(s) to read only access.<br />
# If (5) doesn't work, at least the 3rd party application will not have access to all of your normal github account's (including private repositories).<br />
<br />
* Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a "Request access" button during the set up flow. You'll need to click that button to request approval. See below for an example:<br />
<br />
[[File:github_approval.png]]<br />
<br />
* In some cases, the application does not need to be "approved" to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)<br />
<br />
* In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, it is helpful to send the details to the owner's team, either by [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& opening a bug] or [[#contact|email]].<br />
<br />
=== Reviewing owners and permissions ===<br />
As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.<br />
<br />
=== Can I be an Owner of the Mozilla Organization? ===<br />
The Owners group on github has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.<br />
<br />
All owners '''must''' have 2FA enabled for their GitHub login. (Everyone else ''should''.)<br />
<br />
=== Can I be a Member of the Mozilla Organization? ===<br />
With recent github enhancements (2015), we encourage the following (rough) guidelines, which strongly prefers using github teams. As a reminder, all members of the [https://github.com/mozilla/ Mozilla organization on github] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical.<br />
* "Outside Collaborator": repository admins can grant outside collaborator to any github account. "Outside Collaborator" is roughly analogous to "Level 1a" access to Mozilla hosted repositories.<br />
* "Team Member": team maintainers can add github users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [[#contact|request your addition] to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.<br />
<br />
=== Should I make a separate github organization or just create a repository in an existing one? ===<br />
This is a personal preference. If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details.<br />
<br />
=== Forking vs Transferring ===<br />
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.<br />
<br />
If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:<br />
<br />
# If you're not a member of any team, talk to an [[#contact|org admin]].<br />
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.<br />
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.<br />
# Ask an [[#contact|org admin]] to grant team permissions higher than read ('write' and 'admin' are the other choices). (Team maintainers do not have the ability to change a repositories status.)<br />
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on Github (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)<br />
<br />
=== Do I need to be an owner to create repositories? ===<br />
No. If a person has read/write access to another repository in that organization they can make more repositories in that organization. However, it's preferred that you create repositories in the context of a team.<br />
<br />
=== Are there requirements for when or how I should create a new team? ===<br />
No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).<br />
<br />
On large teams we recommend you separate teams for read/write and repository administration.<br />
<br />
<div id="other_github"></div><br />
=== Is "mozilla" the only github "organization" related to Mozilla? ===<br />
No, there are plenty of Mozilla-related "organizations" on github. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:<br />
{| class="wikitable sortable"<br />
|-<br />
! Organization !! Description !! Contact Owner<br />
|-<br />
| [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || ?<br />
|-<br />
| [https://github.com/bugzilla bugzilla] || Bugzilla (the product) - read-only mirror || ?<br />
|- <br />
| [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?<br />
|-<br />
| [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?<br />
|-<br />
| [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?<br />
|-<br />
| [https://github.com/mdn mdn] || Mozilla Developer Network || {{Mozillian|groovecoder|Luke Crouch}}<br />
|-<br />
| [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?<br />
|-<br />
| [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?<br />
|-<br />
| [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?<br />
|-<br />
| [https://github.com/mozilla-cit mozilla-cit] || Mozilla Community Ops || {{Mozillians|tanner|Tanner Filip}} or {{Mozillians|yalam96|Yousef Alam}}<br />
|-<br />
| [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?<br />
|-<br />
| [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?<br />
|-<br />
| [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?<br />
|-<br />
| [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}<br />
|-<br />
| [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-services owners]<br />
|-<br />
| [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}<br />
|-<br />
| [https://github.com/MozillaTW MozillaTW] || Mozilla Taiwan || ?<br />
|-<br />
| [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?<br />
|-<br />
| [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?<br />
|-<br />
| [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?<br />
|-<br />
| [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}<br />
|-<br />
| [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || ?<br />
|-<br />
| [https://github.com/mozfr mozfr] || Mozilla Francophone || Pascal Chevrel https://mozillians.org/fr/u/pascalc/<br />
|-<br />
| [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?<br />
|-<br />
| [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}<br />
|-<br />
| [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, Jack Moffitt<br />
|-<br />
| [https://github.com/tabulapdf tabulapdf] || Tabula project (extract data from PDF files) || ?<br />
|-<br />
| [https://github.com/webcompat webcompat] || Web Compatibility Team || {{Mozillian|miketaylr|Mike Taylor}}<br />
|-<br />
| [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Pascal Chevrel https://mozillians.org/fr/u/pascalc/<br />
|-<br />
| [https://github.com/taskcluster taskcluster] || [[TaskCluster]] Team || {{Mozillian|sdeckelmann|Selena Deckelmann}}<br />
|}<br />
<br />
=== Are there other unofficial or Mozilla-related repositories hosted on Github? ===<br />
Why, yes! In no particular order:<br />
<br />
* [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer<br />
* [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.<br />
* [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.<br />
* [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters<br />
* [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler<br />
* [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology<br />
* [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.<br />
* [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.<br />
* [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications<br />
* [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests<br />
* [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.<br />
* [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)<br />
* [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.<br />
* [https://github.com/jeffbryner/MozDef MozDef]: Mozilla Defense Platform.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Buildbot/Talos/Running&diff=1122488Buildbot/Talos/Running2016-03-16T18:46:16Z<p>MykMelez: add syntax for Windows w/Mintty</p>
<hr />
<div>= Running Talos Tests =<br />
<br />
== Using mach ==<br />
<br />
First, make sure that firefox is already compiled. Then, execute the mach command in the top source directory. Let’s try running the chromez test suite. The list of valid suites are in the [http://mxr.mozilla.org/mozilla-central/source/testing/talos/talos.json talos.json] file.<br />
<br />
./mach talos-test --suite chromez<br />
<br />
== I have a patch for Talos, what tests to I run? ==<br />
<br />
If you are making changes to talos obviously running the tests locally will be the first step. The next logical step is to run the tests on Try server (try: -b o -p all -u none -t all).<br />
<br />
=== Testing Locally ===<br />
<br />
Testing locally involves running some subset of the Talos tests on<br />
desktop and possibly mobile. Obviously not all permutations of tests<br />
and the ways of running them can be tried, so common sense should be<br />
used as to what is run. You may also want to run Talos' internal<br />
unittests: http://hg.mozilla.org/build/talos/file/tip/tests<br />
<br />
You should tailor your choice of tests to pick those that cover what<br />
you've changed programmatically, but in general you should probably<br />
run at least one startup test and one pageloader test. A good<br />
baseline might be:<br />
<br />
# refer to [[#Running_locally_-_Source_Code|running locally]] for more details<br />
talos -n -d -a tresize:tsvgx -e `which firefox` --develop<br />
<br />
=== Testing on Try Server ===<br />
<br />
There are three scenarios that are needed for testing talos on try server:<br />
* Firefox Developer: testing your Firefox changes for performance issues<br />
* Talos Validation: testing your already reviewed and landed patches to the Talos toolchain in production<br />
* Talos Developer: testing patches to Talos which have not been reviewed or landed<br />
<br />
For the purposes of Talos development we will ignore the Firefox Developer scenario and discuss the two scenarios regarding Talos toolchain development. In fact, the process is similar for both, lets get started:<br />
<br />
First off, you need to edit [[http://dxr.mozilla.org/mozilla-central/source/testing/talos/talos.json?from=talos.json&case=true#1 testing/talos/talos.json]] in your Firefox tree, what is of most importance is:<br />
"talos.zip": {<br />
"url": "http://talos-bundles.pvt.build.mozilla.org/zips/talos.49b74c08dad4.zip",<br />
"path": ""<br />
},<br />
"global": {<br />
"talos_repo": "https://hg.mozilla.org/build/talos",<br />
"talos_revision": "5e18c3e56875"<br />
}<br />
<br />
Android 4.0 tests use "talos.zip:, and all desktop platforms use the "global" section. You can see in global there are 2 fields, "talos_repo" and "talos_revision".<br />
<br />
In the Talos Validation scenario, you only need to change "talos_revision" to be the revision of [[http://hg.mozilla.org/build/talos talos]] that your change is.<br />
<br />
For the Talos Developer scenario, you would edit "global" to look like this:<br />
"global": {<br />
"talos_repo": "http://hg.mozilla.org/users/jmaher_mozilla.com/tpain",<br />
"talos_revision": "default"<br />
}<br />
<br />
There are 2 key points here:<br />
* the repo is pointing to a [[https://developer.mozilla.org/en-US/docs/Creating_Mercurial_User_Repositories user repo]] which contains a full copy of the talos repo and all local changes made<br />
* the revision is pointing at "default"<br />
<br />
''NOTE: there is a trick with using "default" as the revision, it allows you to check in changes and then retrigger a job on try. This avoids the need to push a new revision to try and wait for a build.''<br />
<br />
Finally if you are validating a push or adjusting something that should or will affect Android Talos, then you need to [[http://hg.mozilla.org/build/talos/file/5e18c3e56875/create_talos_zip.py create a new talos.zip]], ftp that to a people.mozilla.org directory, and then edit the talos.zip section of talos.json to reference it.<br />
<br />
Once you have talos.json changed, you just need to select the proper [[http://trychooser.pub.build.mozilla.org/ try chooser]] syntax.<br />
<br />
== Are my numbers ok ==<br />
<br />
The best way to answer this question is to push to try server and compare the reported numbers from the logs (use Treeherder as a log parser) and compare that with the [[http://graphs.mozilla.org/ graph server]]. I recommend using Treeherder to open the link to the graphs. <br />
<br />
If you are planning on landing on mozilla-central, look at tests from mozilla-central. Be aware of PGO vs Non PGO and e10s vs Non e10s. Treeherder makes this a moderately pain free process (i.e. about 30 minutes).<br />
<br />
== Using try server ==<br />
<br />
If you have access to generate try builds you can also have performance tests run against a custom version of talos. The performance results will be generated on the same machines that generate the talos results for all check-ins on all branches. This involves a few steps:<br />
<br />
=== Testing changes to talos properly ===<br />
* Create a [https://developer.mozilla.org/en-US/docs/Creating_Mercurial_User_Repositories?redirectlocale=en-US&redirectslug=Publishing_Mercurial_Clones user repo] with talos, commit and push your changes<br />
* Check out a copy of Mozilla central<br />
* Modify the file "testing/talos/talos.json" to point to your user repo and put the changeset as 'default'.<br />
** For android, change the location of talos.zip<br />
<br />
=== Pushing to try ===<br />
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer#How_to_push_to_try Push] this change to try server using the right syntax (you can use TryChooser to help with this: recommended is to test talos thoroughly, but standard unit tests can be skipped)<br />
* Try server will give you results for a single data point (I recommend hitting retrigger a few times to get at least 3 data points for each test). Graph server is not very useful for viewing your try push data, we have two options for aiding in this effort:<br />
** [[http://hg.mozilla.org/build/talos/file/tip/talos/compare.py compare.py]]: clone talos, setup the virtualenv, run "python compare.py --help", normally I run "python compare.py --revision <rev>" where <rev> is the revision of my try push<br />
** [[http://compare-talos.mattn.ca/ compare-talos]]: Browse to the [http://hg.mozilla.org/build/talos/file/tip/talos/compare.py url], enter your try server revision, then enter a revision of the branch you are comparing to, you can then browser the delta for each summary and individual test page.<br />
<br />
A bit more information can be found in this [http://armenzg.blogspot.com/2011/12/taloszip-talosjson-and-you.html blog post] from armenzg.<br />
<br />
== Running locally - Source Code ==<br />
<br />
* Note: you must first have setuptools installed on your system<br />
* apt-get install python-setuptools # linux<br />
* https://pypi.python.org/pypi/setuptools # download and install for all operating systems<br />
<br />
* you also need virtualenv installed on your system<br />
* pip install virtualenv # http://www.virtualenv.org/en/latest/virtualenv.html#installation<br />
<br />
For the majority of the tests, we include test files and tools out of the box. You will need the [https://developer.mozilla.org/en-US/docs/Simple_Firefox_build mozilla-central code base]:<br />
<br />
* '''clone talos:'''<br />
hg clone http://hg.mozilla.org/mozilla-central<br />
<br />
* '''setup talos'''<br />
cd mozilla-central/testing/talos<br />
virtualenv .<br />
. bin/activate (On Windows: Scripts\activate.bat or . Scripts/activate)<br />
python setup.py develop<br />
<br />
<br />
* '''run tests:'''<br />
talos --develop --executablePath pathtofirefox --activeTests tart<br />
# Note: this will open and close the browser real fast for the warmup, then run the test<br />
** --develop indicates to run in develop mode and store the results in local.json + local.out<br />
** --executablePath tells Talos where the firefox installation we want to run is located<br />
*** we have pathtofirefox as an example, you can use '~/mozilla/objdir/dist/bin/firefox' or whatever the full path is to your firefox executable that will be running the tests.<br />
** --activeTests is a list of tests we want to run separated by ':'. In this example, we are running the tart test .<br />
** --output is the new config file we want to generate<br />
You can use `talos --help` to get a complete list of options<br />
<br />
'''Tip: Run ''find . | xargs touch'' to clear operating system caches between talos runs. This significantly improves the consistency of the results.'''<br />
<br />
If you're looking to run remote talos, instructions are at: https://wiki.mozilla.org/Mobile/Fennec/Android#talos<br />
<br />
''talos --print-tests'' may be used to display the descriptions and run-time parameters of tests<br />
<br />
We do not include the tp5 or similar pagesets for legal restrictions.<br />
<br />
== How Talos is Run in Production ==<br />
<br />
* buildbot constructs commands to launch mozharness, ex:<br />
/tools/buildbot/bin/python scripts/scripts/talos_script.py --suite chromez --add-option --webServer,localhost --branch-name Mozilla-Inbound-Non-PGO --system-bits 64 --cfg talos/linux_config.py --download-symbols ondemand --use-talos-json --blob-upload-branch Mozilla-Inbound-Non-PGO<br />
<br />
* mozharness [https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/talos.py talos.py] downloads common tools, the talos source, pagesets and run the install commands.<br />
<br />
* talos [https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/run_tests.py run_tests.py] is invoked with commandline options which then runs the test as you would locally<br />
<br />
* Talos will run the tests and measured results which are uploaded to [http://graphs.mozilla.org/ graphserver] (after being suitably averaged per-page for Pageloader tests)<br />
** (Talos also uploads raw results to [https://treeherder.mozilla.org/perf.html#/graphs PerfHerder])<br />
<br />
* the graphserver performs averaging across the pageset (for Pageloader tests) or across cycles (for Startup tests) and returns a number via HTTP to Talos which is then printed to the log<br />
<br />
* [https://treeherder.mozilla.org/ Treeherder] receives the name of the suite from buildbot. These are correlated to Treeherder letters via [https://github.com/mozilla/treeherder-service/blob/master/treeherder/etl/buildbot.py]. The computed results from graphserver are scraped from the log and displayed when a Treeherder suite letter is clicked.<br />
<br />
=== The Test Machines ===<br />
<br />
Here is a [[https://wiki.mozilla.org/Buildbot/Talos/Misc#Hardware_Profile_of_machines_used_in_automation description of the specs]] for the machines we use. For more information, please see the [https://wiki.mozilla.org/ReferencePlatforms#Build_Reference_Platforms Test Reference Platforms].<br />
<br />
=== Running Tp the Automation Way ===<br />
In our automation, we run beneath many more restrictions than normal users. One of those restrictions is that our automation machines are walled off from the real-world networks. Because of this, and because we want to test pure page-loading and rendering time of Firefox, we serve the pages from localhost using a built in python webserver thus eliminating all network latency and uncertainty. You've probably noticed this if you looked at the talos/page_load_test/tp4.manifest.<br />
<br />
To do this, we construct full downloads of sites in our manifest and they are placed on the automation slave at run time. Because we cannot at this time distribute our full page load test set, I'll walk through how these are set up and show you how to make your own. Note that our next version of the page load set will be distributable, so soon this won't be an issue.<br />
<br />
In the meantime, here's the instructions:<br />
<ol><br />
<li>Use the following wget command to fetch a page and everything it links to in order to have a complete page for offline use: <pre>wget -p -k -H -E -erobots=off --no-check-certificate -U "Mozilla/5.0 (firefox)" --restrict-file-names=windows --restrict-file-names=nocontrol $URL -o outputlog.txt</pre><br />
</li><br />
</ol></div>MykMelezhttps://wiki.mozilla.org/index.php?title=Marketplace/FutureofMarketplaceFAQ&diff=1120000Marketplace/FutureofMarketplaceFAQ2016-03-04T01:00:48Z<p>MykMelez: correct Fx release in which desktop Web Runtime will be removed</p>
<hr />
<div>= The Future of Marketplace FAQ =<br />
As of March 29, 2016, the Firefox Marketplace will no longer support Android, Desktop, Tablets, or payments of any kind (paid apps or in-app payments). Payments are being deactivated, and the Web Runtime is being removed in [[RapidRelease/Calendar|Firefox 47]] for Android and [[RapidRelease/Calendar|Firefox 48]] for Windows, Mac OS X, and Linux.<br />
<br />
; Q. What does it mean for applications already in Firefox Marketplace?<br />
: Applications in Marketplace that are compatible with Firefox OS will continue to work on Firefox OS; if they are also compatible with other platforms (like Desktop or Android), then they stop working on those platforms. If the app is not listed as compatible with Firefox OS, it will be disabled (not listed in the catalog), but still accessible to the owner on the developer portal.<br />
<br />
; Q. What does it mean for new applications submitted to marketplace?<br />
: Marketplace will discontinue submission of apps for Desktop, Android, and Tablets on March 29, 2016. It will also remove the Paid Apps options to the submission process. We will continue to review apps submitted for Firefox OS. (We will also discontinue the special submission process for China and for low memory devices, but those changes are already live.)<br />
<br />
; Q. Why is this happening in March?<br />
: This is to give developers time to make changes to their apps while the Firefox release schedule continues once Developer Edition of Firefox 47 is out. (For reference, Firefox 47's timetable is roughly: 2016/01/25 Nightly &#8594; 2016/03/07 Aurora &#8594; 2016/04/18 Beta &#8594; 2016/06/06 Release.)<br />
<br />
; Q. Where will applications be hosted if marketplace is shut down?<br />
: Marketplace is not shutting down. Packaged apps will continue to be hosted on Marketplace and continue to serve Firefox OS users at least until January 2018. Future plans will be reviewed around mid-2017.<br />
<br />
; Q. If I am a developer with a paid app or have in-app payments in my app, what should I do?<br />
: You have several choices: you can make your app free, you can use another payment provider for in-app payments, or you can do nothing -- if you do nothing, your app will be disabled.<br />
<br />
To change your app to free, login to the [https://marketplace.firefox.com/developers developer portal], select your app, and change your app to free by selecting the Free tab, then the Compatibility tab under the Edit Listing area, and changing it to Free for Firefox OS.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=GitHub&diff=1115358GitHub2016-02-01T23:58:30Z<p>MykMelez: clarify and link to Mozilla organization</p>
<hr />
<div>This page is specifically about [https://github.com/mozilla the "mozilla" organization on github]. There are several other github organizations you may be interested in, cf. the incomplete list [[#other_github|below]].<br />
<div id="contact"><br />
{| class="wikitable"<br />
|-<br />
! [[File:Red_question_mark.png|144px|Send us an email!|link=]] Got a question?<br />
|-<br />
| Email {{emailentry|github-owners|mozilla.org|at=is}} <br /><br />
Bugzilla [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& mozilla.org :: Github: Administration] <br /><br />
irc #github on [[IRC|moznet]]<br />
|}<br />
<br />
== Recommendations and FAQ ==<br />
<br />
=== Where should I ask additional questions? ===<br />
* Send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and we'll respond right away! We're also available on #github on irc.<br />
<br />
=== How do I hook up a new 3rd party application to a repository in the mozilla org? ===<br />
* Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a "Request access" button during the set up flow. You'll need to click that button to request approval. See below for an example:<br />
<br />
[[File:github_approval.png]]<br />
<br />
* In some cases, the application does not need to be "approved" to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)<br />
<br />
* In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, it is helpful to send the details to the owner's team, either by [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& opening a bug] or [[#contact|email]].<br />
<br />
=== Reviewing owners and permissions ===<br />
As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.<br />
<br />
=== Can I be an Owner of the Mozilla Organization? ===<br />
The Owners group on github has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.<br />
<br />
=== Can I be a Member of the Mozilla Organization? ===<br />
With recent github enhancements (2015), we encourage the following (rough) guidelines, which strongly prefers using github teams. As a reminder, all members of the [https://github.com/mozilla/ Mozilla organization on github] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical.<br />
* "Outside Collaborator": repository admins can grant outside collaborator to any github account. "Outside Collaborator" is roughly analogous to "Level 1a" access to Mozilla hosted repositories.<br />
* "Team Member": team maintainers can add github users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [[#contact|request your addition] to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.<br />
<br />
=== Should I make a separate github organization or just create a repository in an existing one? ===<br />
This is a personal preference. If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details.<br />
<br />
=== Forking vs Transferring ===<br />
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.<br />
<br />
If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:<br />
<br />
# If you're not a member of any team, talk to an [[#contact|org admin]].<br />
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.<br />
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.<br />
# Ask an [[#contact|org admin]] to grant team permissions higher than read ('write' and 'admin' are the other choices). (Team maintainers do not have the ability to change a repositories status.)<br />
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on Github (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)<br />
<br />
=== Do I need to be an owner to create repositories? ===<br />
No. If a person has read/write access to another repository in that organization they can make more repositories in that organization. However, it's preferred that you create repositories in the context of a team.<br />
<br />
=== Are there requirements for when or how I should create a new team? ===<br />
No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).<br />
<br />
On large teams we recommend you separate teams for read/write and repository administration.<br />
<br />
<div id="other_github"></div><br />
=== Is "mozilla" the only github "organization" related to Mozilla? ===<br />
No, there are plenty of Mozilla-related "organizations" on github. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:<br />
{| class="wikitable sortable"<br />
|-<br />
! Organization !! Description !! Contact Owner<br />
|-<br />
| [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || ?<br />
|-<br />
| [https://github.com/bugzilla bugzilla] || Bugzilla (the product) - read-only mirror || ?<br />
|- <br />
| [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?<br />
|-<br />
| [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?<br />
|-<br />
| [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?<br />
|-<br />
| [https://github.com/mdn mdn] || Mozilla Developer Network || {{Mozillian|groovecoder|Luke Crouch}}<br />
|-<br />
| [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?<br />
|-<br />
| [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?<br />
|-<br />
| [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?<br />
|-<br />
| [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?<br />
|-<br />
| [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?<br />
|-<br />
| [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?<br />
|-<br />
| [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}<br />
|-<br />
| [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-services owners]<br />
|-<br />
| [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}<br />
|-<br />
| [https://github.com/MozillaTW MozillaTW] || Mozilla Taiwan || ?<br />
|-<br />
| [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?<br />
|-<br />
| [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?<br />
|-<br />
| [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?<br />
|-<br />
| [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}<br />
|-<br />
| [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || ?<br />
|-<br />
| [https://github.com/mozfr mozfr] || Mozilla Francophone || Pascal Chevrel https://mozillians.org/fr/u/pascalc/<br />
|-<br />
| [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?<br />
|-<br />
| [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}<br />
|-<br />
| [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, Jack Moffitt<br />
|-<br />
| [https://github.com/tabulapdf tabulapdf] || Tabula project (extract data from PDF files) || ?<br />
|-<br />
| [https://github.com/webcompat webcompat] || Web Compatibility Team || {{Mozillian|miketaylr|Mike Taylor}}<br />
|-<br />
| [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Pascal Chevrel https://mozillians.org/fr/u/pascalc/<br />
|}<br />
<br />
=== Are there other unofficial or Mozilla-related repositories hosted on Github? ===<br />
Why, yes! In no particular order:<br />
<br />
* [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer<br />
* [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.<br />
* [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.<br />
* [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters<br />
* [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler<br />
* [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology<br />
* [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.<br />
* [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.<br />
* [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications<br />
* [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests<br />
* [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.<br />
* [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)<br />
* [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.<br />
* [https://github.com/jeffbryner/MozDef MozDef]: Mozilla Defense Platform.</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Apps&diff=1109582Apps2015-12-16T22:03:33Z<p>MykMelez: correct bug number</p>
<hr />
<div>(this page previously contained [https://wiki.mozilla.org/index.php?title=Apps&oldid=1078657 information about Firefox OS Apps])<br />
<br />
== Web App Developer Initiative ==<br />
<br />
In 2015, Mozilla is launching a new initiative to energize mobile web app development. This initiative is part of a broad trend that includes browser makers, web frameworks, cloud service providers, and top 100 content providers. We don't yet agree on what to call these new web apps, but we do agree on their potential. What unites all these disparate parties is a belief in the combined power of several new web standards. By making web apps that work offline and can reengage users, we believe developers will deliver experiences that will redefine the role of the web on mobile devices.<br />
<br />
In the short term, we are focused on the combination of several API's -- [http://www.w3.org/TR/service-workers/ service workers], [http://www.w3.org/TR/push-api/ web push], and the [http://www.w3.org/TR/appmanifest/ W3C app app manifest].<br />
<br />
== Reading List ==<br />
<br />
* [https://paul.kinlan.me/living-with-web-apps/ Paul Kinlin, "Living with Web Apps"]<br />
** In this post, Paul gives an hour-by-hour journal of a day using only web content on his smartphone. Along the way he offers a list of "ten deadly sins of a mobile web app" along with other reflections on his experience.<br />
<br />
* [https://infrequently.org/2015/06/progressive-apps-escaping-tabs-without-losing-our-soul/ Alex Russell, "Progressive Apps: Escaping Tabs without Losing our Soul"]<br />
** Alex lays out his best practices for modern web development based around responsive design and single-page apps, and moves on to how the addition of offlining and "save to home screen" capabilities enrich the mobile web.<br />
<br />
* [https://www.youtube.com/watch?v=iZZdhTUP5qg Alex Komoroske and Elisabeth Morant, "The Next Generation Mobile Web"]<br />
** In this 40 minute Google I/O talk, Alex and Elisabeth show examples using these new API's, especially concentrating on how web push creates exciting new opportunities for user reengagement.<br />
<br />
== 2015 Q3 Deliverables ==<br />
<br />
In Q3, our goals for WADI engineering were (1) to transition off our legacy projects, (2) to educate ourselves about serviceworkers and web push, and (3) to plan for Q4. We had roughly a month of Q3 to work with. We accomplished these goals by encouraging each engineer to build small prototypes and sharing what we learned in a daily standup. These prototypes led to our presentation in the Firefox OS all-hands, a Github Universe talk, as well as the filing of several important platform and product bugs (and fixing of one!).<br />
<br />
* https://firekey.org/<br />
* https://brendandahl.github.io/pdfcollection/<br />
* https://marco-c.github.io/watchy/#/series<br />
* https://mozilla.github.io/high-fidelity/#/podcasts<br />
<br />
== 2015 Q4 Deliverables ==<br />
<br />
In Q4, we will prepare for the launch of both Web Push and Service Workers in Firefox 44 by building one or two serious progressive apps and the infrastructure they require. We'll focus our engineers on one or two projects at a time, so we build team cohesion and benefit from collaboration. We'll carefully scope these projects so we can really hit them out of the park. Our tight focus, coupled with conference talks and blog posts, will make these apps useful references, helping build developer awareness for the launch of serviceworkers and push in Firefox 44. As we build real product code with automated tests, we explore the limits of our platform, find its bugs, and gather the knowledge we need to plan for the beginning of 2016.<br />
<br />
=== Oghliner ===<br />
<br />
Ship v1 of Oghliner, a library/tool to offline web apps using Service Workers and deploy them to GitHub Pages. We will base this on top of several existing open source projects, including sw-precache from the Chrome team (https://github.com/GoogleChrome/sw-precache).<br />
* Oghliner v1 - https://github.com/mozilla/oghliner<br />
<br />
=== Platatus ===<br />
<br />
Ship MVP of at least one serious offline/progressive web app. We need to explore the space of possible use cases – to help developers, to find bugs in the implementation, to expand our own understanding. Much of the work of building even simple demo apps is app-related and not related to the underlying technologies. The leading candidate is Platatus, an app that offers a detailed, data-driven view of Mozilla's progress on delivering the technologies behind Progressive Web apps.<br />
* Platatus MVP - https://github.com/mozilla/platatus - minimal viable prototype of reference app that describes standardization/implementation status of web platform features<br />
<br />
=== Service Worker Cookbook ===<br />
<br />
Create a cookbook of self-contained code snippets showing how to use Service Workers to achieve various kinds of cacheing and push notification use cases.<br />
<br />
* https://serviceworker-cookbook.herokuapp.com/<br />
* https://github.com/mozilla/serviceworker-cookbook<br />
<br />
== Bug tracking ==<br />
<br />
These are bugs we've identified as critical to our ability to deploy these technologies to developers. We use [https://bugzilla.mozilla.org/show_bug.cgi?id=1201717 bug 1201717] to track them.<br />
<br />
<bugzilla><br />
{<br />
"blocks": "1201717"<br />
}<br />
</bugzilla></div>MykMelezhttps://wiki.mozilla.org/index.php?title=MOSS/Foundational_Technology/Projects_We_Use&diff=1103293MOSS/Foundational Technology/Projects We Use2015-10-29T17:10:55Z<p>MykMelez: add self (Myk Melez) as contact for SlimerJS</p>
<hr />
<div>This is an incomplete list of the free software and open source projects Mozilla relies upon. As a starting point, it lists each project along with a short statement of how we depend on it. Where practical it would also be helpful to identify a Mozillian most closely associated with our use of each project, as next steps will involve contacting each one to find out more about how we can best provide support.<br />
<br />
This is a work in progress - please contribute to this list.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project !! Description !! Contact within Mozilla<br />
|-<br />
| [https://angularjs.org/ angular.js] || Used by A-Team for web apps (eg Treeherder) || Member of Jonathan Griffin's team<br />
|-<br />
| [https://httpd.apache.org Apache Server] || Used by A-Team for web apps || Member of Jonathan Griffin's team<br />
|-<br />
| [https://github.com/ansible/ansible Ansible] || Used by IT (netops) and A-Team to manage deployments || jbarnell , GPS?<br />
|-<br />
| [https://babeljs.io/ BabelJS] || JavaScript compiler, Used by Gaia, TaskCluster team || Selena Deckelmann<br />
|-<br />
| [https://pypi.python.org/pypi/blessings/ Blessings] || Terminal formatting lib used by mozilla-central build process || Erik Rose<br />
|-<br />
| [http://getbootstrap.com/ Bootstrap] || HTML/CSS/JS framework, used by many of Mozilla's sites. || Webdev<br />
|-<br />
| [https://bro.org bro] || The Bro Network Security Monitor || Michal Purzynski<br />
|-<br />
| [http://buildbot.net/ BuildBot] || The base system currently in use for release automation ''(due to be replaced by Task Cluster)'' || Chris AtLee<br />
|-<br />
| [http://bugzilla.org/ Bugzilla] (upstream) || The base Bugzilla on that we customize for Mozilla's use || Glob<br />
|-<br />
| [http://www.celeryproject.org/ Celery] || Distributed task queue. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| [http://ckeditor.com/ CKEditor] || WYSIWYG editor on MDN || <br />
|-<br />
| [http://www.llvm.org Clang/LLVM] || C/C++ compiler and infrastructure || Ehsan Akhgari <br />
|-<br />
| [https://codemirror.net/ CodeMirror] || Used in DevTools, [https://thimble.mozilla.org Thimble], and other online code tools || David Humphrey/Simon Wex<br />
|-<br />
| [https://conemu.github.io/ ConEmu] || Console emulator for Windows. Used by devs running Windows. || Ed Morley<br />
|-<br />
| [https://www.debian.org/ Debian] || Used on many developer boxes || Unknown (maybe Sylvestre Ledru) or glandium<br />
|-<br />
| [https://discourse.org Discourse] || [https://discourse.mozilla-community.org Community], [https://discourse.webmaker.org/ Webmaker], [https://discourse.mozilla-advocacy.org/ Advocacy], et al || [[IT/Community/WG/Discourse|Community Ops]] (Yousef Alam or Tanner Filip)<br />
|-<br />
| [https://djangoproject.com Django] || Backend web framework used on many of our websites, including addons.mozilla.org, marketplace.mozilla.org, support.mozilla.org, Input, Snippets, MDN (Mozilla Developer Network), mozilla.org, Treeherder || Andy McKay and Jannis Leidel are (or have been) on the [https://www.djangoproject.com/foundation/ Django Software Foundation] board, Jannis is core team member<br />
|-<br />
| [http://www.django-rest-framework.org Django REST framework] || API framework. Used by various Mozilla sites including MDN, Firefox marketplace, mozilla.org, support.mozilla.com. || Andy McKay and Jannis Leidel<br />
|-<br />
| [https://github.com/docker/docker Docker] || Used by release engineering for Linux build and test containers and by ateam for managing test and production services. Used by many Mozilla websites as well such as addons.mozilla.org, marketplace.mozilla.org. (Plus docker-compose and docker machine) || Member of Selena Deckelmann's team <br />
|-<br />
| [https://www.elastic.co/products/elasticsearch elasticsearch] || Search engine for various web sites and analytics || Erik Rose<br />
|-<br />
| [http://www.gnu.org/software/emacs/ emacs] || Programmable editor used by many developers || —<br />
|-<br />
| [https://github.com/ether/etherpad-lite Etherpad] || Used for meeting notes, etc || JP Schneider<br />
|-<br />
| [https://flake8.readthedocs.org/ flake8] || Wrapper around Python linters. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| [http://flask.pocoo.org/ Flask] || Python web framework || Erik Rose<br />
|-<br />
| [https://fortawesome.github.io/Font-Awesome/ Font Awesome] || Font and CSS toolkit, used by many of Mozilla's sites. || Webdev<br />
|-<br />
| [http://gcc.gnu.org GCC] || C/C++ compiler and infrastructure || Unknown<br />
|-<br />
| [https://git-scm.com/ Git] || Version control system - https://git.mozilla.org || Unknown <br />
|-<br />
| [http://gunicorn.org/ gunicorn] || Python WSGI HTTP Server. Used by Treeherder, Socorro, Pontoon. || Webdev<br />
|-<br />
| [http://www.freedesktop.org/wiki/Software/HarfBuzz/ HarfBuzz] || International text shaping engine used in Firefox/Servo || Platform team<br />
|-<br />
| [http://hunspell.sourceforge.net/ Hunspell] || Spellchecking engine || Unknown<br />
|-<br />
| [https://github.com/hunspell/hyphen/ Hyphen] || Hyphenation library || Unknown<br />
|-<br />
| [https://theintern.github.io/intern/ Intern] || Intern is a complete test system for JavaScript designed to help you write and run consistent, high-quality test cases for your JavaScript libraries and applications. || jrgm/vladikoff<br />
|-<br />
| [http://canonware.com/jemalloc/ jemalloc] || Memory allocation library || We can ask glandium<br />
|-<br />
| [http://jenkins-ci.org/ Jenkins CI] || Continuous integration system used by WebQA and EE || Unknown<br />
|-<br />
| [https://jquery.com/ jQuery] || JavaScript library, used by many of Mozilla's sites. || Webdev<br />
|-<br />
| [http://kombu.readthedocs.org/ Kombu] || Messaging library for Python. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| libjpeg-turbo || JPEG decoding library || Jeff Muizelaar <br />
|-<br />
| [http://www.libpng.org/pub/png/libpng.html libpng] || PNG decoding library || Jeff Muizelaar <br />
|-<br />
| libvpx (Google) || Library for support of Google’s VP* family of codecs || Tim Terriberry <br />
|-<br />
| Linux || OS kernel used in Firefox OS || Unknown <br />
|-<br />
| [https://lodash.com/ lodash] || JavaScript utility library, used by many of Mozilla's sites. || Webdev<br />
|-<br />
| [https://www.list.org/ Mailman] || [https://mail.mozilla.org/listinfo Mailing lists] || Unknown<br />
|-<br />
| [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] || You are reading this on a wiki || Sheeri Cabral<br />
|-<br />
| [https://www.mercurial-scm.org/ Mercurial] || Version control system and source code management || GPS <br />
|-<br />
| [https://github.com/kumar303/mohawk Mohawk] || Python library for Hawk HTTP authorization. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| [http://mozdef.com mozdef] || Security event monitoring and incident response || Jeff Bryner<br />
|-<br />
| [http://www.mingw.org/wiki/msys msys] || Used to build Firefox on Windows. Note: It's likely best we support the newer MSYS2 project instead: https://github.com/msys2 || Unknown<br />
|-<br />
| [https://www.mysql.com/ MySQL] || Open source relational DB used by many developers, including AMO, SUMO, Input, bugzilla, releng, adminstered by IT || Sheeri Cabral<br />
|-<br />
| [https://www.nagios.org/ Nagios] || IT management system. Used for notifications of system failures || Sheeri Cabral, Ashish V.<br />
|-<br />
| [http://netsniff-ng.org/ netsniff-ng] || Linux networking toolkit || Michal Purzynski<br />
|-<br />
| nICEr || Library for traversing firewalls || Unknown <br />
|-<br />
| [https://nixos.org NixOS] || Reproducible Linux distribution. Used by some developers and for running benchmarks on Firefox OS for AreWeFastYet || Nicolas B. Pierron<br />
|-<br />
| [https://nodejs.org Node.js] || JavaScript runtime for server side applications, command line utilities || Nick Desaulniers<br />
|-<br />
| nrappkit || Toolkit for building standalone applications || Unknown <br />
|-<br />
| OpenH264 (Cisco) || H.264 video library || Unknown <br />
|-<br />
| [http://openresty.org OpenResty] || a fast web app server by extending nginx, used by cloudops || Benson Wong (mostlygeek)<br />
|-<br />
| [http://www.openssh.com/ OpenSSH] || Remote server management, secure transport for Git and Mercurial || Unknown<br />
|-<br />
|-<br />
| [http://www.openLDAP.org/ OpenLDAP] || User management used by Infra || :jabba?<br />
|-<br />
|-<br />
| [http://www.inspircd.org/ inspircd] || Irc server used by mozilla || Unknown<br />
|-<br />
| [http://openssl.org/ OpenSSL] || Cryptograpahy and TLS Toolkit || Nick Desaulniers<br />
|-<br />
| [https://www.owasp.org/index.php/ZAP OWASP ZAP] || Web security testing tool used by security and QA teams || Simon Bennetts (psiinon)<br />
|-<br />
| [https://owncloud.org/ Owncloud] || Open platform to host your cloud under your control || Some communities have been using it to host files under their control (ask Nukeador)<br />
|-<br />
| [https://pypi.python.org/pypi/parsimonious/ Parsimonious] || Parsing lib used by DXR and a few other sites (I think) || Erik Rose<br />
|-<br />
| [https://github.com/mozilla/pdf.js PDF.js] || Used as the PDF Viewer in Firefox and Firefox OS || Brendan Dahl, Yury Delendik<br />
|-<br />
| [https://github.com/PyCQA/pep8 pep8] || Python linter. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| [https://www.perl.org/ Perl] || Used by Bugzilla || Member of Jonathan Griffin's team<br />
|-<br />
| [https://phalconphp.com/ Phalcon PHP Framework] || Phalcon is an open source web framework delivered as a C extension for the PHP language providing high performance and lower resource consumption. || Andres Gutierrez is one of the [https://phalconphp.com/en/team core developers] of Phalcon and its inspiration.<br />
|-<br />
| [https://github.com/pypa/pip pip] || Python package tool. Used by all Python projects. || Erik Rose and Jannis Leidel, Jannis is core team member ([https://www.pypa.io/ PyPA])<br />
|-<br />
| [http://piwik.org/ Piwik] || Analytic software that gives you the control and respects privacy || Some communities have been using it to avoid GA analytics (Ask Nukeador)<br />
|-<br />
| [http://cmusphinx.sourceforge.net/ Pocketsphinx] || Speech recognition toolkit embedded into Firefox OS|| André Natal<br />
|-<br />
| [http://www.postgresql.org/ PostgreSQL] || Open source relational DB used by many developers, adminstered by IT || Selena Deckelmann<br />
|-<br />
| [https://github.com/PrismJS/prism Prism.js] || Syntax highlighting on code samples on MDN || <br />
|-<br />
| [https://github.com/puppetlabs/puppet Puppet] || System administration tool || Member of Amy Rich's team<br />
|-<br />
| [https://github.com/pyflakes/pyflakes pyflakes] || Python linter. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| [http://pytest.org/ pytest] || Python testing tool. Used by Treeherder and others. || Member of Jonathan Griffin's team<br />
|-<br />
| Python || Scripting language || [http://python.org/psf/ Python Software Foundation], Selena Deckelmann is a former board member<br />
|-<br />
| [https://pypi.python.org/pypi/pyelasticsearch/ pyelasticsearch] || Python client for elasticsearch || Erik Rose<br />
|-<br />
| [https://www.rabbitmq.com/ RabbitMQ] || Distributed Queue, used by Socorro, Pulse (all our publicly available build/test/commit information flows through this), Treeherder, addons.mozilla.org (with Celery), marketplace.mozilla.org (with Celery) || Selena Deckelmann<br />
|-<br />
| [https://readthedocs.org/ Read the Docs] || Hosted automatically-built documentation, used by Cloud Services and a wide variety of mozilla Github projects || Ben Bangert, Jannis Leidel, Gervase Markham<br />
|-<br />
| [http://python-requests.org/ Requests] || "Python HTTP Requests for Humans". Used by many many Mozilla Python projects. || Member of Jonathan Griffin's team<br />
|-<br />
| [https://www.reviewboard.org/ Review Board] || The base of MozReview, the new review tool being developed to replace Splinter || Steven MacLeod, Mike Conley<br />
|-<br />
| [http://www.seleniumhq.org/ Selenium] || Browser test driver || stephend/AutomatedTester or jrgm/vladikoff<br />
|-<br />
| [https://slimerjs.org/ SlimerJS] || Scriptable browser, based on Gecko, used for functional tests in some few Mozilla projects ( [[PluotSorbet]], some FxOS apps ? and others ?) || Myk Melez<br />
|-<br />
| [https://www.sqlite.org/ SQLite] || File-based database || khuey<br />
|-<br />
| [http://learnboost.github.io/stylus/ Stylus] || CSS Pre-processor on several sites || webdev<br />
|-<br />
| [https://subversion.apache.org/ Subversion] || https://svn.mozilla.org ''(Planning to decommission in near future)'' || Unknown<br />
|-<br />
| [http://http://suricata-ids.org/ suricata] || IDS / IPS / NSM engine || Michal Purzynski<br />
|-<br />
| [https://travis-ci.org/ Travis] || Continuous integration system used by several teams (eg Treeherder) || Jonathan Griffin's team <br />
|-<br />
| [https://github.com/mitchellh/vagrant Vagrant]|| Build and distribute dev envs, used by Treeherder and others || Member of Jonathan Griffin's team<br />
|-<br />
| [http://valgrind.org/ Valgrind] || Memory error detection and profiling of C and C++ code || jseward, njn<br />
|-<br />
| [http://vim.org/ vim] || editor used by many developers || —<br />
|-<br />
| [https://github.com/w3c/web-platform-tests web-platform-tests] || Testcases and tooling for cross-browser testing of web-platform APIs || jgraham<br />
|-<br />
| [http://www.webrtc.org WebRTC.org] || Components to support real-time communication in browsers and mobile applications || Randell Jesup <br />
|-<br />
| [http://www.wordpress.org WordPress] || Powers our blogs, blog.mozilla.org || Craig Cook <br />
|-<br />
| [https://xiph.org Xiph.Org] || Media codecs ship in Firefox, encoding tools || Ralph Giles<br />
<br />
|}</div>MykMelezhttps://wiki.mozilla.org/index.php?title=Apps&diff=1099931Apps2015-10-09T19:02:26Z<p>MykMelez: add Platatus deliverable; describe both deliverables</p>
<hr />
<div>(this page previously contained [https://wiki.mozilla.org/index.php?title=Apps&oldid=1078657 information about Firefox OS Apps])<br />
<br />
== Web App Developer Initiative ==<br />
<br />
In 2015, Mozilla is launching a new initiative focused on the combination of several API's -- [http://www.w3.org/TR/service-workers/ service workers], [http://www.w3.org/TR/push-api/ web push], and the [http://www.w3.org/TR/appmanifest/ W3C app app manifest]. We believe the combination of these technologies is a platform with which we can offer developers some capabilities unmatched by native app ecosystems.<br />
<br />
== Reading List ==<br />
<br />
* [https://paul.kinlan.me/living-with-web-apps/ Paul Kinlin, "Living with Web Apps"]<br />
** In this post, Paul gives an hour-by-hour journal of a day using only web content on his smartphone. Along the way he offers a list of "ten deadly sins of a mobile web app" along with other reflections on his experience.<br />
<br />
* [https://infrequently.org/2015/06/progressive-apps-escaping-tabs-without-losing-our-soul/ Alex Russell, "Progressive Apps: Escaping Tabs without Losing our Soul"]<br />
** Alex lays out his best practices for modern web development based around responsive design and single-page apps, and moves on to how the addition of offlining and "save to home screen" capabilities enrich the mobile web.<br />
<br />
* [https://www.youtube.com/watch?v=iZZdhTUP5qg Alex Komoroske and Elisabeth Morant, "The Next Generation Mobile Web"]<br />
** In this 40 minute Google I/O talk, Alex and Elisabeth show examples using these new API's, especially concentrating on how web push creates exciting new opportunities for user reengagement.<br />
<br />
== 2015 Q3 Demoes ==<br />
<br />
* https://firekey.org/<br />
* https://brendandahl.github.io/pdfcollection/<br />
* https://marco-c.github.io/watchy/#/series<br />
<br />
== 2015 Q4 Deliverables ==<br />
<br />
* Oghliner v1 - https://github.com/mozilla/oghliner - initial version of a template/tool for offlining web apps and deploying them to GitHub Pages<br />
* Platatus MVP - https://github.com/mozilla/platatus - minimal viable prototype of reference app that describes standardization/implementation status of web platform features</div>MykMelezhttps://wiki.mozilla.org/index.php?title=ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer&diff=1085175ReleaseEngineering/Mozharness/How to run tests as a developer2015-07-16T16:49:43Z<p>MykMelez: add --test-packages-url to list of non-required flags</p>
<hr />
<div>'''NOTE: If running a job does not easily run locally for you; don't hesitate to just stop (no need to try to fix it), [https://wiki.mozilla.org/ReleaseEngineering/How_To/Request_a_slave ask for a loaner so you can make progress] and file a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness here] for us to debug (please attach logs/log_info.log).'''<br />
<br />
'''NOTE: You can now use your LDAP credentials to authenticate and download the files that are behind Http authentication (e.g. pvtbuilds).'''<br />
<br />
= Brief intro =<br />
Remember that there are jobs that download builds and run tests or performance tests, hence, requiring --installer-url and/or --test-url.<br />
Other jobs, simply create a build or run code analysis, hence, do not need --installer-url and/or --test-url.<br />
<br />
To read more about mozharness you can reach these:<br />
* https://developer.mozilla.org/en-US/docs/Mozharness_FAQ<br />
* https://wiki.mozilla.org/ReleaseEngineering/Mozharness<br />
<br />
= Known issues =<br />
* Android emulator tests download a copy of the Android SDK from tooltool. Only Mozilla employees are authorized to download these files; non-employees will encounter a failure on download, but can easily work around the issue by skipping the download and using a local copy of the Android SDK.<br />
<br />
= Run mozharness ... =<br />
== ...on your local machine ==<br />
Follow all the steps mentioned in "Common steps".<br />
<br />
== ...on a loaner machine ==<br />
* <font color='red'>Don't use --cfg developer_config.py</font><br />
* Use --no-read-buildbot-config instead<br />
* If the job is...<br />
** A build job: nothing to append<br />
** A test job: append --installer-url and --test-url<br />
** A talos job: append --installer-url<br />
<br />
Also add these variables:<br />
* export '''DISPLAY=:0''' # I think it applied for Linux hosts<br />
* export '''MOZ_UPLOAD_DIR=/builds/slave/test/build/blobber_upload_dir'''<br />
** This will allow your job to upload files to blobber<br />
<br />
== ...with binaries from your objdir ==<br />
TODO: I believe --installer-path instead of --installer-url can be used with --cfg dev_config.py, however, we have to verify this and document it properly.<br />
<br />
If you figure it out please add it here and we will review it.<br />
<br />
== Common steps ==<br />
=== Step 1 - Clone Mozharness ===<br />
Clone Mozharness:<br />
hg clone http://hg.mozilla.org/build/mozharness scripts<br />
<br />
=== Step 2 - Create a tooltool token (fetches artifacts for you) ===<br />
With the new tooltool, you need to create a token to run mozharness on your development machine.<br />
<br />
Steps:<br />
* Go [https://api.pub.build.mozilla.org/tokenauth here]<br />
* Issue a new user token with tooltool.download.public and tooltool.download.internal selected<br />
* The token will only be shown once<br />
* Place it in /builds/relengapi.tok<br />
<br />
=== Step 3 - Find the command in the log ===<br />
In the job in treeherder you can search for '''"Run as scripts/scripts"''' and you should see how exactly the command was run in production and you can add the options mentioned above.<br />
<br />
NOTE: Don't forget to prepend ''python'' before the command.<br />
<br />
=== Step 4 - Append --cfg developer_config.py ===<br />
<br />
{{warning|If you have a loaned machine from Release Engineering, do not use this config.<br/>This config is meant to be used only when you're running mozharness on your local machine.<br/>(<small>[[How_to_run_tests_as_a_developer#...on_a_loaner_machine|More Information]]</small>)}}<br />
<br />
This activates the LDAP authentication for private files.<br />
It also removes --read-buildbot-configs from the list of actions.<br />
<br />
== Unit/talos tests steps ==<br />
If you're trying to reproduce a unit test suite or a talos suite follow this last step. Otherwise, go to the "Build and other jobs" section.<br />
<br />
=== Step 5 - Append --installer-url and/or --test-url and/or --test-packages-url ===<br />
Append ''--installer-url'' and/or ''--test-url'' and/or ''--test-packages-url''. You can find the right values on the log:<br />
<pre><br />
08:14:31 INFO - Found installer url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tar.bz2.<br />
08:14:31 INFO - Found test url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tests.zip.<br />
…<br />
17:51:04 INFO - Found a test packages url https://queue.taskcluster.net/v1/task/XHPBpieOSeO2e44zhkw64A/artifacts/public/build/test_packages.json.<br />
</pre><br />
<br />
NOTICE: Talos jobs do not require --test-url.<br />
<br />
== Build and other jobs ==<br />
You don't have to use --installer-url, --test-url, or --test-packages-url.<br />
<br />
Right now I have not been able to run too many of these jobs on my local machine since it requires setting up mock_mozilla and each of these jobs can have their own set of environments.<br />
<br />
We have filed {{bug|1067354}} to improve this situation.<br />
<br />
Please ask in #releng for assistance as it might be possible to run the job locally with an extra brain. Otherwise, you will need to loan a machine.<br />
<br />
= Filing bugs =<br />
If you have tried mozharness and it is not doing what you need then [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness file a bug] and CC :armenzg.<br />
<br />
= Example =<br />
We start with this production command:<br />
/tools/buildbot/bin/python scripts/scripts/b2g_emulator_unittest.py --cfg b2g/emulator_automation_config.py --test-suite mochitest --this-chunk 1 --total-chunks 9 --blob-upload-branch mozilla-central --download-symbols ondemand<br />
<br />
and we end up with this developer-friendly command:<br />
python scripts/scripts/b2g_emulator_unittest.py --cfg b2g/emulator_automation_config.py --test-suite mochitest --this-chunk 1 --total-chunks 9 --blob-upload-branch mozilla-central --download-symbols ondemand \<br />
--cfg developer_config.py \<br />
--installer-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-emulator/20140910173159/emulator.tar.gz \<br />
--test-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-emulator/20140910173159/b2g-35.0a1.en-US.android-arm.tests.zip<br />
<br />
= Other examples =<br />
== Running Mozharness with a local version of Talos and Firefox on Linux ==<br />
<br />
These instructions can be more general, but this should be a useful starting point for any similar configuration.<br />
This allows you to use '''your own objdir''' instead of downloading an installer and a tests.zip.<br />
<br />
<pre><br />
python scripts/talos_script.py --cfg configs/talos/linux_config_local.py<br />
</pre><br />
<br />
Create the file configs/talos/linux_config_local.py<br />
<br />
<pre><br />
PYTHON = '/home/v/work/talos2/bin/python' <br />
VENV_PATH = '/home/v/work/talos2'<br />
FIREFOX = "/home/v/work/gecko-dev/obj-linux-optimized/dist/bin/firefox"<br />
<br />
config = { <br />
"talos_json": "talos.json",<br />
"use_talos_json": True,<br />
"suite": "custom",<br />
"python_webserver": True,<br />
"binary_path": FIREFOX,<br />
"log_name": "talos",<br />
"buildbot_json_path": "buildprops.json", #optional<br />
"virtualenv_path": VENV_PATH,<br />
"default_actions": [<br />
"clobber",<br />
"run-tests",<br />
], <br />
}<br />
</pre><br />
<br />
talos.json<br />
<br />
<pre><br />
{ <br />
"global": {<br />
"talos_repo": "/home/v/work/talos2",<br />
"talos_revision": "tip"<br />
},<br />
"suites": {<br />
"custom": {<br />
"tests": ["ts"]<br />
}<br />
},<br />
"mobile-suites": {<br />
}<br />
}<br />
</pre><br />
<br />
Use this (and enable it in the config) if you want to simulate a try syntax commit message.<br />
<br />
buildprops.json<br />
<pre><br />
{ <br />
"sourcestamp": {<br />
"changes": [ {<br />
"comments": "try: simulated try parameters go here",<br />
"files": [ {"name":""} ]<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
= Deprecated =<br />
== Step 3 - B) Create a buildprops.json ==<br />
In the previous section we mention to use --installer-url as well as --test-url, this is not necessary if you create a file called buildprops.json since the URLs are already specified inside of it.<br />
You can find the information you need by loading a tbpl log and looking for ''"08:14:31 INFO - Using buildbot properties"''.<br />
Don't try to make sense of it. Just copy it without the datestamps (I know, it sucks).<br />
<br />
== Step 4 - B) --no-read-buildbot-config ==<br />
Append --no-read-buildbot-config to the command.<br />
A developer config removes the action "read-buildbot-config" from the list of actions.<br /><br />
Some jobs could work with just this and not need a developer config, however, this is unlikely.<br />
<br />
== Step 4 - Use a developer config ==<br />
You should be able to simply add --cfg foo_dev.py to the line that is run in production and make it easier for a developer to run the tests (e.g. --cfg android/androidarm.py --cfg android/androidarm'''_dev.py'''). All the files are under the ''configs'' directory.<br />
<br />
If there's not a developer config available read the section "How to add a developer config".<br />
<br />
== How to create a developer config ==<br />
Developer configs, if appended after a production config, will overwrite the values on the production config.<br /><br />
<br />
Developer configs have these things in common:<br />
* They have the same name as the production one but instead end with '''"_dev.py"'''<br />
* They overwrite the '''"exes"''' dict with an empty dict<br />
** This allows to use the binaries in your personal $PATH rather than infra-centric paths<br />
* They overwrite the '''"default_actions"''' list<br />
** The main reason is to remove the action called read-buildbot-configs<br />
** WARNING: A production config could add new actions and should be added to the developer config upon review.<br />
* They fix URLs to point to the right public reachable domains<br />
** WARNING: This should be fixed in the future as they can fall out of sync with production</div>MykMelezhttps://wiki.mozilla.org/index.php?title=ReleaseEngineering/Mozharness/How_to_run_tests_as_a_developer&diff=1084190ReleaseEngineering/Mozharness/How to run tests as a developer2015-07-10T20:27:15Z<p>MykMelez: add --test-packages-url</p>
<hr />
<div>'''NOTE: If running a job does not easily run locally for you; don't hesitate to just stop (no need to try to fix it), [https://wiki.mozilla.org/ReleaseEngineering/How_To/Request_a_slave ask for a loaner so you can make progress] and file a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness here] for us to debug (please attach logs/log_info.log).'''<br />
<br />
'''NOTE: You can now use your LDAP credentials to authenticate and download the files that are behind Http authentication (e.g. pvtbuilds).'''<br />
<br />
= Brief intro =<br />
Remember that there are jobs that download builds and run tests or performance tests, hence, requiring --installer-url and/or --test-url.<br />
Other jobs, simply create a build or run code analysis, hence, do not need --installer-url and/or --test-url.<br />
<br />
To read more about mozharness you can reach these:<br />
* https://developer.mozilla.org/en-US/docs/Mozharness_FAQ<br />
* https://wiki.mozilla.org/ReleaseEngineering/Mozharness<br />
<br />
= Known issues =<br />
* Android emulator tests download a copy of the Android SDK from tooltool. Only Mozilla employees are authorized to download these files; non-employees will encounter a failure on download, but can easily work around the issue by skipping the download and using a local copy of the Android SDK.<br />
<br />
= Run mozharness ... =<br />
== ...on your local machine ==<br />
Follow all the steps mentioned in "Common steps".<br />
<br />
== ...on a loaner machine ==<br />
* <font color='red'>Don't use --cfg developer_config.py</font><br />
* Use --no-read-buildbot-config instead<br />
* If the job is...<br />
** A build job: nothing to append<br />
** A test job: append --installer-url and --test-url<br />
** A talos job: append --installer-url<br />
<br />
Also add these variables:<br />
* export '''DISPLAY=:0''' # I think it applied for Linux hosts<br />
* export '''MOZ_UPLOAD_DIR=/builds/slave/test/build/blobber_upload_dir'''<br />
** This will allow your job to upload files to blobber<br />
<br />
== ...with binaries from your objdir ==<br />
TODO: I believe --installer-path instead of --installer-url can be used with --cfg dev_config.py, however, we have to verify this and document it properly.<br />
<br />
If you figure it out please add it here and we will review it.<br />
<br />
== Common steps ==<br />
=== Step 1 - Clone Mozharness ===<br />
Clone Mozharness:<br />
hg clone http://hg.mozilla.org/build/mozharness scripts<br />
<br />
=== Step 2 - Create a tooltool token (fetches artifacts for you) ===<br />
With the new tooltool, you need to create a token to run mozharness on your development machine.<br />
<br />
Steps:<br />
* Go [https://api.pub.build.mozilla.org/tokenauth here]<br />
* Issue a new user token with tooltool.download.public and tooltool.download.internal selected<br />
* The token will only be shown once<br />
* Place it in /builds/relengapi.tok<br />
<br />
=== Step 3 - Find the command in the log ===<br />
In the job in treeherder you can search for '''"Run as scripts/scripts"''' and you should see how exactly the command was run in production and you can add the options mentioned above.<br />
<br />
NOTE: Don't forget to prepend ''python'' before the command.<br />
<br />
=== Step 4 - Append --cfg developer_config.py ===<br />
<br />
{{warning|If you have a loaned machine from Release Engineering, do not use this config.<br/>This config is meant to be used only when you're running mozharness on your local machine.<br/>(<small>[[How_to_run_tests_as_a_developer#...on_a_loaner_machine|More Information]]</small>)}}<br />
<br />
This activates the LDAP authentication for private files.<br />
It also removes --read-buildbot-configs from the list of actions.<br />
<br />
== Unit/talos tests steps ==<br />
If you're trying to reproduce a unit test suite or a talos suite follow this last step. Otherwise, go to the "Build and other jobs" section.<br />
<br />
=== Step 5 - Append --installer-url and/or --test-url and/or --test-packages-url ===<br />
Append ''--installer-url'' and/or ''--test-url'' and/or ''--test-packages-url''. You can find the right values on the log:<br />
<pre><br />
08:14:31 INFO - Found installer url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tar.bz2.<br />
08:14:31 INFO - Found test url http://ftp.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-inbound-linux32_gecko/1400225075/en-US/b2g-32.0a1.en-US.linux-i686.tests.zip.<br />
…<br />
17:51:04 INFO - Found a test packages url https://queue.taskcluster.net/v1/task/XHPBpieOSeO2e44zhkw64A/artifacts/public/build/test_packages.json.<br />
</pre><br />
<br />
NOTICE: Talos jobs do not require --test-url.<br />
<br />
== Build and other jobs ==<br />
You don't have to use --installer-url or --test-url.<br />
<br />
Right now I have not been able to run too many of these jobs on my local machine since it requires setting up mock_mozilla and each of these jobs can have their own set of environments.<br />
<br />
We have filed {{bug|1067354}} to improve this situation.<br />
<br />
Please ask in #releng for assistance as it might be possible to run the job locally with an extra brain. Otherwise, you will need to loan a machine.<br />
<br />
= Filing bugs =<br />
If you have tried mozharness and it is not doing what you need then [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness file a bug] and CC :armenzg.<br />
<br />
= Example =<br />
We start with this production command:<br />
/tools/buildbot/bin/python scripts/scripts/b2g_emulator_unittest.py --cfg b2g/emulator_automation_config.py --test-suite mochitest --this-chunk 1 --total-chunks 9 --blob-upload-branch mozilla-central --download-symbols ondemand<br />
<br />
and we end up with this developer-friendly command:<br />
python scripts/scripts/b2g_emulator_unittest.py --cfg b2g/emulator_automation_config.py --test-suite mochitest --this-chunk 1 --total-chunks 9 --blob-upload-branch mozilla-central --download-symbols ondemand \<br />
--cfg developer_config.py \<br />
--installer-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-emulator/20140910173159/emulator.tar.gz \<br />
--test-url http://pvtbuilds.pvt.build.mozilla.org/pub/mozilla.org/b2g/tinderbox-builds/mozilla-central-emulator/20140910173159/b2g-35.0a1.en-US.android-arm.tests.zip<br />
<br />
= Other examples =<br />
== Running Mozharness with a local version of Talos and Firefox on Linux ==<br />
<br />
These instructions can be more general, but this should be a useful starting point for any similar configuration.<br />
This allows you to use '''your own objdir''' instead of downloading an installer and a tests.zip.<br />
<br />
<pre><br />
python scripts/talos_script.py --cfg configs/talos/linux_config_local.py<br />
</pre><br />
<br />
Create the file configs/talos/linux_config_local.py<br />
<br />
<pre><br />
PYTHON = '/home/v/work/talos2/bin/python' <br />
VENV_PATH = '/home/v/work/talos2'<br />
FIREFOX = "/home/v/work/gecko-dev/obj-linux-optimized/dist/bin/firefox"<br />
<br />
config = { <br />
"talos_json": "talos.json",<br />
"use_talos_json": True,<br />
"suite": "custom",<br />
"python_webserver": True,<br />
"binary_path": FIREFOX,<br />
"log_name": "talos",<br />
"buildbot_json_path": "buildprops.json", #optional<br />
"virtualenv_path": VENV_PATH,<br />
"default_actions": [<br />
"clobber",<br />
"run-tests",<br />
], <br />
}<br />
</pre><br />
<br />
talos.json<br />
<br />
<pre><br />
{ <br />
"global": {<br />
"talos_repo": "/home/v/work/talos2",<br />
"talos_revision": "tip"<br />
},<br />
"suites": {<br />
"custom": {<br />
"tests": ["ts"]<br />
}<br />
},<br />
"mobile-suites": {<br />
}<br />
}<br />
</pre><br />
<br />
Use this (and enable it in the config) if you want to simulate a try syntax commit message.<br />
<br />
buildprops.json<br />
<pre><br />
{ <br />
"sourcestamp": {<br />
"changes": [ {<br />
"comments": "try: simulated try parameters go here",<br />
"files": [ {"name":""} ]<br />
}<br />
]<br />
}<br />
}<br />
</pre><br />
<br />
= Deprecated =<br />
== Step 3 - B) Create a buildprops.json ==<br />
In the previous section we mention to use --installer-url as well as --test-url, this is not necessary if you create a file called buildprops.json since the URLs are already specified inside of it.<br />
You can find the information you need by loading a tbpl log and looking for ''"08:14:31 INFO - Using buildbot properties"''.<br />
Don't try to make sense of it. Just copy it without the datestamps (I know, it sucks).<br />
<br />
== Step 4 - B) --no-read-buildbot-config ==<br />
Append --no-read-buildbot-config to the command.<br />
A developer config removes the action "read-buildbot-config" from the list of actions.<br /><br />
Some jobs could work with just this and not need a developer config, however, this is unlikely.<br />
<br />
== Step 4 - Use a developer config ==<br />
You should be able to simply add --cfg foo_dev.py to the line that is run in production and make it easier for a developer to run the tests (e.g. --cfg android/androidarm.py --cfg android/androidarm'''_dev.py'''). All the files are under the ''configs'' directory.<br />
<br />
If there's not a developer config available read the section "How to add a developer config".<br />
<br />
== How to create a developer config ==<br />
Developer configs, if appended after a production config, will overwrite the values on the production config.<br /><br />
<br />
Developer configs have these things in common:<br />
* They have the same name as the production one but instead end with '''"_dev.py"'''<br />
* They overwrite the '''"exes"''' dict with an empty dict<br />
** This allows to use the binaries in your personal $PATH rather than infra-centric paths<br />
* They overwrite the '''"default_actions"''' list<br />
** The main reason is to remove the action called read-buildbot-configs<br />
** WARNING: A production config could add new actions and should be added to the developer config upon review.<br />
* They fix URLs to point to the right public reachable domains<br />
** WARNING: This should be fixed in the future as they can fall out of sync with production</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080968PluotSorbet2015-06-19T22:38:41Z<p>MykMelez: wordsmith elevator pitch</p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet is a [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible virtual machine written in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/pluotsorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/pluotsorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/pluotsorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/pluotsorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/pluotsorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/pluotsorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/pluotsorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/pluotsorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
== Contact Us ==<br />
<br />
Chat with us in the [http://mibbit.com/?channel=%23pluotsorbet&server=irc.mozilla.org #pluotsorbet] channel on [http://irc.mozilla.org/ Mozilla's IRC network (irc.mozilla.org)].<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}[1] JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=All_Hands/2015_Whistler/ScienceFairDemos&diff=1080921All Hands/2015 Whistler/ScienceFairDemos2015-06-19T16:13:55Z<p>MykMelez: change name of project from j2me.js to PluotSorbet</p>
<hr />
<div>Who and what will you see at the first-ever [[Coincidental_work_weeks/2015_Whistler#Mozilla-Wide_.27Science_Fair.27_.28.26_Drink.29 |Work Week Science Fair]]? Let us count the demos:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Project Name !! Project Description !! What You'll See and Learn !! Contact<br />
|-<br />
| [https://github.com/gasolin/BlocklyDuino BlocklyDuino] || An open source project that provide the web-based visual programming editor for Arduino. || People will be able to blink LED, control servo by rotation controller, change LED color via stacking coding blocks and flash code to Arduino board. [https://www.youtube.com/watch?v=u2Fp0KpWxik Example]. || [https://hacks.mozilla.org/author/fredlin/ Fred Lin]<br />
|-<br />
| Compositor-driven video timing || By moving video frame timing to the compositor we can make video playback smoother, especially for 60fps video. We can demo this by playing a specially crafted 60fps video of alternating cyan and magenta frames, which clearly shows color flashes whenever a frame is dropped or duplicated. || We can show people how Gecko with these changes gets much smoother 60fps video than older Gecko, or Chrome. || [http://robert.ocallahan.org/ Robert O'Callahan]<br />
|-<br />
| Connecting Donors with our Mission || We'll showcase some donor letters and ask you to send a message back to fundraising || We'll reflect on how our work and our personal values have contributed to letters of appreciation from donors. We do this: 1) to celebrate our donors 2) to celebrate our colleagues 3) to make our colleagues aware of their very real role in fundraising! We need to develop a MoFo case statement AND stewardship report for donors who gave in 2014 and this exercise will start to uncover potential contributors and some stories we wouldn't otherwise find. || [https://ca.linkedin.com/in/rebeccadaviescfre Rebecca Davies]<br />
|-<br />
| Electrolysis || We'll demo some performance improvements e10s brings to the browser and generally answer any questions people have. || Learn how e10s is helping to improve the quality of the browser. || [http://www.mathies.com/ Jim Mathies]<br />
|-<br />
| Firefox Hello || Firefox Hello long term vision. Many think of Firefox Hello as just a Video calling tool but we want it to become the best way to share the web with others. || Our demo will help people understand the Hello vision and how we intend to deliver it. || [https://uk.linkedin.com/pub/dan-horner/1/966/159 Dan Horner]<br />
|-<br />
| Firefox for iOS || We will be showing Firefox for iOS on iPhone and iPad. || Try out the latest build and see what we have been working on. || [https://mozillians.org/en-US/u/st3fan/ Stefan Arentz]<br />
|-<br />
| Firefox OS for TV || Firefox OS TV and the key experiences / features || What's Firefox OS on TV like? Check out the new form factor and see how Mozilla can build a better Firefox product experience || [https://mozillians.org/en-US/u/jcheng/ Joe Cheng]<br />
|-<br />
| FoxEye || We will demo how modern computer vision and image processing can change the Web. We will show some image processing abilities through OpenCV.js. And also some video processing through WebCam. || This cutting edge Web technology will inspire the creativeness of the Web developers on image processing and computer vision area. This framework demonstrates a worker based model which allow the Web developers to fully utilize multi-core machine. || [https://www.linkedin.com/pub/chia-hung-tai/36/8b6/712?trk=pub-pbmap Chia-hung Tai]<br />
|-<br />
| Games & VR || The Games and VR teams would like to demo the latest and greatest games and immersive experiences from the bleeding edge of the web. || Attendees will get their hands on the bleeding edge of gaming and immersive experiences built on the open web. They'll learn what's possible today, what's coming next, and how they can start to build their own gaming and immersive experiences today using web technologies they already know and love. || [https://twitter.com/joshcarpenter Josh Carpenter]<br />
|-<br />
| Gecko for iOS || A ported Gecko running iOS: showing a simple browser embedding running on an unmodified iPhone 6. || Technical details of the port, App Store guideline nonsense, bad jokes. || [https://mozillians.org/en-US/u/ted/ Ted Mielczarek] <br />
|-<br />
| [https://github.com/mozilla/pluotsorbet PluotSorbet] ||PluotSorbet implements a Java-compatible virtual machine and J2ME-compatible platform in JavaScript. It enables you to run J2ME apps, a.k.a. midlets, on Firefox OS! || Learn what PluotSorbet is, how it works, and the benefits of using it to make more apps available for Firefox OS. You'll also learn where we can use help and how to get involved. || [https://mozillians.org/en-US/u/myk/ Myk Melez]<br />
|-<br />
| Localizing via a web editor || I'll show the current status of Aisle, a plugin for Cloud9 to localize Firefox. || You'll learn how to bring translation-specific problems together with editing source code. And there's a plan on how to make that great. || [[User:AxelHecht|Axel Hecht]]<br />
|-<br />
| [http://mig.mozilla.org Mozilla InvestiGator (MIG)] || MIG is a platform to perform investigative surgery on remote endpoints. It enables investigators to obtain information from large numbers of systems in parallel, thus accelerating investigation of incidents and day-to-day operations security. || The capabilities of MIG as deployed at Mozilla today, and how to use the platform to help with their daily tasks. || [https://mozillians.org/en-US/u/jvehent/ Julien Vehent]<br />
|-<br />
| MozReview || MozReview is a code-review platform tightly integrated with Mozilla's infrastructure to optimize developer productivity. || How to use MozReview and why, and where we're going with it. || [https://mozillians.org/en-US/u/mcote/ Mark Côté]<br />
|-<br />
| Password Manager || Improvements to the password manager used by Firefox desktop and Android since the beginning of the year. Find out how to get involved by reporting websites where the password manager doesn't work or creating per-site recipes to fix them. || Learn what types of issues have been fixed to get a better understanding about what should work. Discover how to get involved by reporting websites where the password manager doesn't work or creating per-site recipes to fix them. || [https://mozillians.org/en-US/u/MattN/ Matthew Noorenberghe]<br />
|-<br />
| Perfherder || Perfherder is a new project, part of Treeherder, which will aims to: (1) detect, manage performance regressions in Firefox and Firefox for Android as detected by the Talos benchmarking tool; and (2) help Firefox developers evaluate the effect that their patches have on performance by providing tools for performing a side-by-side comparison on performance measures for specific revisions. [https://treeherder.mozilla.org/perf.html#/compare?originalProject=mozilla-inbound&originalRevision=64f9806c4c16&newProject=mozilla-inbound&newRevision=2f4eb23c6d7c Example]. [https://wiki.mozilla.org/Auto-tools/Projects/Perfherder Project landing page].|| The primary target audience for the demo are likely developers. You will learn: (1) How Perfherder will be used for performance sheriffing in the future (performance sheriffs will soon be linking to perfherder graphs and comparisons when filing bugs about performance regressions). (2) How to use Perfherder's comparison view to evaluate a build you submitted to try. The project is just beginning to come together, feedback from a broad cross section of the Firefox developer community would be extremely valuable. || [https://mozillians.org/en-US/u/wlach/ William Lachance]<br />
|-<br />
| [[FirefoxOS/Pinning_the_Web|Pinning the Web]] || Pinning the Web is an experimental UI for Firefox OS which removes the artificial distinction between web apps and web sites and allows you to pin any web site or web page to your device, in a novel new way. || See a demo video of this in action and play with a prototype. || [https://mozillians.org/en-US/u/bfrancis/ Ben Francis] <br />
|-<br />
| Raptor || Raptor: The next generation FxOS performance measurement tool || What Raptor is, how it works, where it is running, and how to run Raptor tests locally. || [https://mozillians.org/en-US/u/rwood/ Rob Wood]<br />
|-<br />
| Research at MoFo || We will demo one year of ethnographic and design research at Mozilla Foundation, and show how we learned from users across the world to build Webmaker.<br />
|| One year of research in Kenya, Bangladesh, Brazil and India illustrate how people perceive and engage with the web there and what it means for Mozilla. Learn about different perceptions and usage of the web, through different cultures. Details [https://docs.google.com/document/d/1gXagCb61vMRsmX4rJkakNT1hIgFY3Eu3I2j1ED_0uEk/edit here]. || [https://mozillians.org/en-US/u/Lau/ Laura de Reynal]<br />
|-<br />
| ServiceNow || We'll show ServiceNow, our Service Desk and WPR ticketing tools and answer questions. || Learn how to quickly and easily use ServiceNow as well as tips & tricks of navigating the system and make customize it. || [https://mozillians.org/en-US/u/vdoan/ Vien Doan]<br />
|-<br />
| Shipping Firefox to the World! || Learn how we ship Firefox to the world! Release Engineering will present the systems that turn open source code into the software installed on computers everywhere. We provide a publicly available "try server" where anyone who contributes to Firefox can test out their changes in our build environment. We'll discuss the systems that automate releases, tools that enable build creation and monitoring and our plans for the future. || Learn about the system for producing Firefox binaries and installers, and the people that run this environment. If you are a new developer or want to contribute to Firefox core development, learn about the tryserver and how to test your code. If you're already a contributor, come learn about upcoming changes to our build and test pipeline, and ways you can contribute and use that pipeline directly yourself. || [https://mozillians.org/en-US/u/sdeckelmann/ Selena Deckelmann]<br />
|-<br />
| Teach The Web with Mozilla Clubs || Mozilla is making it easy to teach others digital skills and web literacy through our [http://teach.mozilla.org new offering]. We recently launched "Mozilla Clubs" as a way to organize local teaching and learning all year-round. Building off the success of Mozilla's successful Maker Party campaign, Mozilla Clubs are a great way to provide sustained local engagement, train up local leaders, and take our mission of spreading web literacy and digital opportunity to the next level. || Learn how to start your own local Mozilla Club and hear stories about our new Regional Co-ordinators and Club Captains. Get inspired by stories of how teaching and learning can provide new opportunities for community contribution and serving Mozilla's mission. || [https://mozillians.org/en-US/u/thornet/ Michelle Thorne]<br />
|-<br />
| [https://thecount.paas.allizom.org/ TheCount] || TheCount is a marketplace for open web apps based on the Firefox Marketplace. It uses the Marketplace API to retrieve that catalog. It also provides statistics about the catalog, such as number of user ratings, popularity of JS frameworks. || * How to use the Marketplace API * Which frameworks and permissions app developers are using * What it's like building apps in Ember || [https://mozillians.org/en-US/u/bwalker/ Bill Walker]<br />
|-<br />
| The Joy of Coding: Tales from a Livehacker || I will explain how I livehack on Air Mozilla every Wednesday, and what technology / techniques I use to make it happen. I'll explain my tiny helper app "Wacky Morning DJ" that I use to play sounds. || Learn how to livehack and get more livehackers up on Air Mozilla! || [https://mozillians.org/en-US/u/mconley/ Mike Conley]<br />
|-<br />
| Webmaker for Android || The Mozilla Foundation's new Webmaker app for Android, which will have just shipped to the Google Play store. It makes it easy for anyone to create simple apps, pages and local content directly from their phone. || Learn how to create using Webmaker for Android and how that relates to Mozilla's mission to spread digital opportunity -- especially for the web's next billion users. And also how to make use of Webmaker to teach and inspire others as part of your work with Mozilla. || [https://twitter.com/secretrobotron Bobby Richter]<br />
[https://mozillians.org/en-US/u/thisandagain/ Andrew Sliwinski]<br />
|-<br />
| [https://www.indiegogo.com/projects/corozal-web-training-camp%20and%20here%20http://xulforge.com/blog/2015/01/webmakering-in-belize/ Webmaker in the Belizean Jungle] || In Dec 2014/Jan 2015, 4 Mozillians organized a trip to Cerros, in the Belizian jungle to teach 30 kids how to use the web. Over the course of 1 week, we taught them about the structure of the web, privacy, coding, showed them how to use Firefox phones (which they got to keep). By the end they all had their own blogs. We will have lots of photos from the event as well as handwritten feedback sheets from the kids detailing what they learned. Participants were [https://mozillians.org/en-US/u/mruttley/ Matthew Ruttley], [https://mozillians.org/en-US/u/scaraveo/ Shane Caraveo], [https://mozillians.org/en-US/u/jorgev/ Jorge Villalobos] and it was initiated by [https://mozillians.org/en-US/u/ChristopherArnold/ Christopher Arnold]. || Learn: How to participate in future trips * How to teach kids who have very little experience and access to technology * How to give fun lessons with very limited technology and slow internet access * Which online tools work and don't work in this setting (Etherpad, webIDE etc) || [https://mozillians.org/en-US/u/mruttley/ Matthew Ruttley]<br />
|-<br />
| [http://WoT.js WoT.js] || WoT.js is a framework helped people use Web technology to build a IoT(Internet of Things) application easier and faster. [https://github.com/evanxd/wot-pong Wot Pong] is an example application. In it, we create the classic [http://en.wikipedia.org/wiki/Pong Pong] game with a LED matrix and a FxOS device. Demo video [https://www.youtube.com/watch?v=OSrhkYNAbv4 here]. || 1. How to build a WoT application with WoT.js. 2. How to build a Arduino project with WoT.js. 3. Have fun with the WoT Pong. Try to win the computer player! || [https://github.com/evanxd Evan Tseng]<br />
|-<br />
| WebRTC and media tricks. || Combinations of new and cool features in WebRTC, Web Audio and our media subsystem. || New capabilities in Media, especially combinations of features like WebAudio, canvas, and WebRTC || [https://twitter.com/mairereavy Maire Reavy]<br />
|-<br />
| [http://linuxpoetry.com/blog/22 Docker Based Try Builds] || Releng is moving to a docker based infrastructure (for Linux builds), which will make it easy for developers to play with the same environments that we use to handle their try pushes. || 1. How to launch a docker based Try job locally/remotely. 2. Where to find the docker images (in tree). 3. How to attach to your job container and use it for debugging builds. || [https://twitter.com/mrrrgn Morgan Phillips (mrrrgn_)]<br />
|-<br />
|}</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080847PluotSorbet2015-06-18T23:37:46Z<p>MykMelez: /* Contact Us */</p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet implements a Java-compatible virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible platform in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/pluotsorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/pluotsorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/pluotsorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/pluotsorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/pluotsorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/pluotsorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/pluotsorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/pluotsorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
== Contact Us ==<br />
<br />
Chat with us in the [http://mibbit.com/?channel=%23pluotsorbet&server=irc.mozilla.org #pluotsorbet] channel on [http://irc.mozilla.org/ Mozilla's IRC network (irc.mozilla.org)].<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}[1] JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080846PluotSorbet2015-06-18T23:37:07Z<p>MykMelez: add contact info</p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet implements a Java-compatible virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible platform in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/pluotsorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/pluotsorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/pluotsorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/pluotsorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/pluotsorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/pluotsorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/pluotsorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/pluotsorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
== Contact Us ==<br />
<br />
Chat with us in the [http://mibbit.com/?channel=%23PluotSorbet&server=irc.mozilla.org #pluotsorbet] channel on [http://irc.mozilla.org/ Mozilla's IRC network (irc.mozilla.org)].<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}[1] JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080714PluotSorbet2015-06-17T20:48:23Z<p>MykMelez: </p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet implements a Java-compatible virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible platform in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/pluotsorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/pluotsorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/pluotsorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/pluotsorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/pluotsorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/pluotsorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/pluotsorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/pluotsorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}[1] JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080708PluotSorbet2015-06-17T19:02:15Z<p>MykMelez: </p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet implements a Java-compatible virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible platform written in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/pluotsorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/pluotsorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/pluotsorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/pluotsorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/pluotsorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/pluotsorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/pluotsorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/pluotsorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}[1] JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080707PluotSorbet2015-06-17T18:55:43Z<p>MykMelez: </p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet implements a Java-compatible virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible platform written in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/PluotSorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/PluotSorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/PluotSorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/PluotSorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/PluotSorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/PluotSorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/PluotSorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/PluotSorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}[1] JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080706PluotSorbet2015-06-17T18:54:30Z<p>MykMelez: change references from j2me.js to PluotSorbet</p>
<hr />
<div>__NOTOC__<br />
Welcome to the PluotSorbet project!<br />
<br />
PluotSorbet implements a Java-compatible virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME]-compatible platform written in JavaScript<sup>[[#JavaScript|[1]]]</sup>. The goal of PluotSorbet is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep PluotSorbet simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run PluotSorbet in your [https://github.com/mozilla/PluotSorbet/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/PluotSorbet/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for PluotSorbet, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/PluotSorbet<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/PluotSorbet/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/PluotSorbet/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/PluotSorbet thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/PluotSorbet/blob/master/README.md#profiling several different tools] to assess and improve the performance of PluotSorbet, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/PluotSorbet/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
<hr><br />
''<small>{{anchor|JavaScript}}JavaScript is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. and other countries, used under license.</small>''</div>MykMelezhttps://wiki.mozilla.org/index.php?title=J2me.js&diff=1080188J2me.js2015-06-15T21:06:55Z<p>MykMelez: MykMelez moved page J2me.js to PluotSorbet</p>
<hr />
<div>#REDIRECT [[PluotSorbet]]</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1080187PluotSorbet2015-06-15T21:06:54Z<p>MykMelez: MykMelez moved page J2me.js to PluotSorbet</p>
<hr />
<div>__NOTOC__<br />
Welcome to the j2me.js project! j2me.js is a Java virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME platform] written in JavaScript. The goal of j2me.js is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep j2me.js simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run j2me.js in your [https://github.com/mozilla/j2me.js/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/j2me.js/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for j2me.js, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/j2me.js<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/j2me.js/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/j2me.js/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/j2me.js thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/j2me.js/blob/master/README.md#profiling several different tools] to assess and improve the performance of j2me.js, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/j2me.js/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
== Contact Us ==<br />
<br />
* the [http://mibbit.com/?channel=%23j2me.js&server=irc.mozilla.org #j2me.js] IRC channel on [http://irc.mozilla.org/ Mozilla's IRC network].</div>MykMelezhttps://wiki.mozilla.org/index.php?title=All_Hands/2015_Whistler/jam_band&diff=1071520All Hands/2015 Whistler/jam band2015-05-01T17:36:34Z<p>MykMelez: add myself to list</p>
<hr />
<div>== Work Week Jam Session ==<br />
<br />
The idea is to have a selection of musical equipment available in a room during the work week. Mozillians who play instruments can come down get together with other musicians and either Jam something or work on a specific tune whether it's original material or a cover. We'd be looking for singers, guitarists, bassists, drummers etc.<br />
<br />
The idea is that we'd rehearse during downtime in the evenings so that we could play a set at the end of the week.<br />
<br />
Before we get this idea off the ground the first part of this is finding out if people are interested in doing this and if there is enough interest from Mozilla musicians.<br />
<br />
If you want to chat about the setup, songs, ... join #musicians on the Mozilla IRC.<br />
<br />
=== Activity location ===<br />
<br />
Rainbow Theatre, Lower Level, Whistler Conference Centre<br />
<br />
=== Times activity will be available ===<br />
<br />
Roughly 6pm till about 11.30pm, Tuesday/Wednesday/Thursday.<br />
<br />
==== Tuesday 23rd June participants ====<br />
<br />
'''Key holder''':<br />
<br />
Other attendees: <br />
<br />
==== Wednesday 24rd June participants ====<br />
<br />
'''Key holder''':<br />
<br />
Other attendees:<br />
<br />
==== Thursday 25rd June participants ====<br />
<br />
'''Key holder''':<br />
<br />
Other attendees: <br />
<br />
=== Track list ===<br />
<br />
Put the details of any tracks you're interested in covering so other like-minded musicians can have a listen and maybe work out some of the parts. Put your name too so we know what day you're playing.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! irc nick !! What you'll be doing/playing !! Song/Track + Artist !! Resources (e.g. audio (e.g spotify) etc) !! interested?<br />
|-<br />
| Chris Mills || chrismills || drums || Something by Black Sabbath, Metallica or the Dead Kennedys, cos it's easy to play drums to || Trawl on Youtube ||<br />
|-<br />
| Chris Mills || chrismills || singing || Something by Pearl Jam or Alice in Chains, as I can sing this stuff fairly well, e.g. Alive, Even Flow, Rooster || Trawl on Youtube ||<br />
|- <br />
| Chris Mills || chrismills || singing || "Bullet in the Head" by Rage against the Machine, as I know the words off by heart and wouldn't mind giving it a go || https://www.youtube.com/watch?v=v5NeyI4-fdI || gfritzsche<br />
|- <br />
| Chris Mills || chrismills || singing or drums || I'd also love to do some Zappa, although the ones I can sing are the really offensive ones ;-). Playing something really techie like Zomby Woof would be awesome if we could get it right || https://www.youtube.com/watch?v=cYUdgszl6Xo ||<br />
|-<br />
| Francisco Picolini || francjp || guitar || Anything of Alice in Chains, Mad Season. Some stuff from Pearl Jam, Stone temple pilots, Blind Melon, Nirvana. Suck my kiss, Under the bridge (RHCP); Naked (Reef); Roxanne (The Police); Zero, Bullet with Butterfly wings (Smashing Pumpkins); Cover me (Candlebox); Pure massacre (Silverchair) || || deimidis<br />
|- <br />
| Stuart Colville || muffinresearch || guitar || Chank by John Scofield, Time is Tight: Booker T & the MGs, Inner City Blues: Reuben Wilson version, Cosmik Debris: Zappa || Chank: https://open.spotify.com/track/4PYwx2Mt2Jhuzqs6iZCdqc Time is tight: https://open.spotify.com/track/70m9hcxrqayJ9inXuUnjBe inner city blues: https://open.spotify.com/track/6gfXD2urCWjN1HkjymhEsP Zapp - Cosmik debris https://open.spotify.com/track/6VC0m8b8xWf671JApr8L7X|| ||<br />
|-<br />
| Myk Melez || myk || drums || I'd love to take a well-known rock or pop song and punk it up. Paint It Black by the Rolling Stones, Teenage Dream by Katy Perry, etc. It can be ironic or sincere, as long as it's punk! || Prior Art: [https://www.youtube.com/watch?v=cb3WYwHsfr4 7 Seconds - 99 Red Balloons], [https://www.youtube.com/watch?t=20&v=2sGJl2LNFaE Bodyjar - Hazy Shade Of Winter], [https://www.youtube.com/watch?v=a2MZyKvNMBg Bad Religion - Christmas Songs], and [https://www.youtube.com/playlist?list=PL764355715E1CB6BC everything by Me First and the Gimme Gimmes]. ||<br />
|}<br />
<br />
=== Raw participant list ===<br />
<br />
If you're keen to play please add your name and details to this table:<br />
<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! irc nick !! Instruments !! Musical interests || Bringing own instrument<br />
|-<br />
| Joe Cheng || jcheng || Drums || Rock but open to anything || No, I can bring drumsticks ;)<br />
|-<br />
| Stuart Colville || muffinresearch || Guitar, Bass, Digeridu || Jamming/improv + covers || No <br />
|-<br />
| Chad Weiner || chadw || Bass/Vocals || I'm in a Phish tribute band so...let's call it jamming/improv || No<br />
|-<br />
| Eli Perelman || Eli || Drums || Jamming/improv + covers || No (maybe an auxiliary electronic pad)<br />
|-<br />
| Chris Mills || chrismills || Drum kit, hand drums/percussion (e.g. Djembe), vocals, lyric ideas, guitar (badly) || Whatever comes up. I mainly love metal/prog/punk/horrible noise, but I am very open minded. || I could bring hand drums, but not drum kit ;-)<br />
|-<br />
| Paul McLanahan || pmac || Guitar, Vocals || ALL THE THINGS! (I'll try anyway) || No<br />
|-<br />
| Daniel Maher || phrawzty || percussion, berimbau, vocals, lyrics || down for whatever || [http://www.korg.com/us/products/drums/wavedrum_global_edition/ wavedrum] (maybe) <br />
|-<br />
| David Durst || ddurst || keyboards || preferably not pop, but that's me || (I wish) No<br />
|-<br />
| Michal Dziewonski || vesper| || drums, karaoke-grade vocals || jamming and post-sludge electronic ambient ;) || Nope, I can bring drum sticks, though<br />
|-<br />
| Alon Zakai || azakai || Guitar (mostly but not only classical/nylon-string) || Rock, Bach, anything else || No<br />
|-<br />
| Dan Gohman || sunfish || keyboards, backup vocals, non-drumset percussion, schlagenfrappe || I'll try just about anything but preferrably no ukeleles || No<br />
|-<br />
| Mark Reid || mreid || Guitar, Bass || * || No, though I could possibly bring a little pedalboard for some fx & tuning<br />
|-<br />
| Rehan Dalal || rdalal || Guitar, Vox || I'm open to anything || Yes, I'll have my baritone Strat. Will need an amp.<br />
|-<br />
| Gerv Markham || gerv || Vocals || Happy to try anything || Yes :-) <br />
|-<br />
| Georg Fritzsche || gfritzsche || Bass || jamming, funky stuff, rock, odd rythms || No<br />
|-<br />
| Syd Polk || sydpolk || soprano or alto sax + flute || jazz, classical, soul, funk, r&b || yes<br />
|-<br />
| Jb Piacentino || jb || Vocals || About anything, pref rock || Sure!<br />
|-<br />
| Nihanth Subramanya || nhnt11 || Guitar || Blues/rock, but probably anything else as well. || No :(<br />
|-<br />
| Matthew Ruttley || mruttley || Classical Guitar but can stretch to others || Early Music, Lute, Swing, Contemporary classical || No<br />
|-<br />
| Myk Melez || myk || Drums || I like both kinds of music. || Not likely.<br />
|-<br />
| Jeremie Patonnier || Jeremie || Guitar || Jamming (Rock, Funk, Jazz, whatever) || No :( <br />
|-<br />
| Justin Terry || jterry || Guitar (Electric/Acoustic) & Mandolin || Classic, Funk, Folk, Indie, Jam, most things || Bringing my Mandolin, but would love to jam on a guitar too!<br />
|-<br />
| Bill Walker || bwalker || Keyboards, backup vocals || Jazz standards and rock covers || Will bring jazz fakebook PDF's<br />
|-<br />
| Francisco Picolini || francjp || Guitar (electric/acoustic) || Grunge, Indie, Rock || nop, unless I can buy something there :(<br />
|-<br />
| Mark Jeffries || mjeffries || Bass Guitar/vocals || Many styles, but enjoy rock || Yes - The Steinberger does not incur the ire of the TSA ;) Will need an amp, BTW.<br />
|-<br />
| Guillermo Movia || deimidis || Vocal, percussion || covers, grunge, Led Zeppelin, NIN, Beatles || No <br />
|-<br />
| Caitlin Galimidi || c8o || Vocals, Acoustic Guitar (rhythm, poorly) || jazz, electronic, singer-songwriter, rock and country vocals || mic, vocal amp, acoustic guitar, and conga (Toca) <br />
|-<br />
| Example || Example || Example || Example || <br />
|}<br />
<br />
=== Instrument Hire List Draft ===<br />
<br />
Here's what we'd likely need to hire. Note: Don't add to this it'll be updated based on the table above.<br />
If you're a brass/woodwind player it'll probably be possible to bring an instrument as the size wouldn't be too much of a problem (That is assuming we're not talking about tubas :)).<br />
<br />
{| class="wikitable"<br />
|-<br />
! Description !! Quantity<br />
|-<br />
| PA + Mixer (this will be room-size dependent, but make it big enough to handle drum input + all the possible inputs below) || 1<br />
|-<br />
| Vocal/Instrument Mics + stands + leads || 8<br />
|-<br />
| Electric Guitars + guitar stands + strap || 3<br />
|-<br />
| Acoustic (ElectroAcoustic) Guitars (at least 1 of which has nylon strings) + acoustic stands + strap || 3<br />
|-<br />
| Bass Guitar + stand + strap (one 4 string bass and one 5 string, perhaps? Make sure at least one is 4 string) || 2<br />
|-<br />
| Bass Amp (at least 2x10"/2x12"? e.g. SWR Redhead) || 1<br />
|-<br />
| Guitar Amp (Fender Deluxe or similar) || 2<br />
|-<br />
| Keyboard + stand + stool (something that can do good electric / acoustic piano / organ sounds) || 1<br />
|-<br />
| Full drum kit + stool, with double bass drum pedal? || 2<br />
|-<br />
| Kick drum mic || 2<br />
|-<br />
| Hand percussion (bongos, tambourine, cajón, etc.) || ?<br />
|-<br />
| Spare strings for all the guitars and basses || ?<br />
|}<br />
<br />
We are unable to rent:<br />
Digeridu<br />
Berimbau<br />
Schlagenfrappe</div>MykMelezhttps://wiki.mozilla.org/index.php?title=All_Hands/2015_Whistler/jam_band&diff=1069156All Hands/2015 Whistler/jam band2015-04-20T04:51:52Z<p>MykMelez: add self to list of interested musicians</p>
<hr />
<div>== Work Week Jam Session (TBD / Draft) ==<br />
<br />
The idea is to have a selection of musical equipment available in a room during the work week. Mozillians who play instruments can come down get together with other musicians and either Jam something or work on a specific tune whether it's original material or a cover. We'd be looking for singers, guitarists, bassists, drummers etc.<br />
<br />
The idea is that we'd rehearse during downtime in the evenings so that we could play a set at the end of the week.<br />
<br />
Before we get this idea off the ground the first part of this is finding out if people are interested in doing this and if there is enough interest from Mozilla musicians.<br />
<br />
If you're keen to play please add your name and details to this table:<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! irc nick !! Instruments !! Musical interests || Bringing own instrument<br />
|-<br />
| Stuart Colville || muffinresearch || Guitar, Bass, Digeridu || Jamming/improv + covers || No <br />
|-<br />
| Chad Weiner || chadw || Bass/Vocals || I'm in a Phish tribute band so...let's call it jamming/improv || No<br />
|-<br />
| Eli Perelman || Eli || Drums || Jamming/improv + covers || No (maybe an auxiliary electronic pad)<br />
|-<br />
| Chris Mills || chrismills || Drum kit, hand drums/percussion (e.g. Djembe), vocals, lyric ideas, guitar (badly) || whatever comes up || I could bring hand drums, but not drum kit ;-)<br />
|-<br />
| Paul McLanahan || pmac || Guitar, Vocals || ALL THE THINGS! (I'll try anyway) || No<br />
|-<br />
| Daniel Maher || phrawzty || percussion, berimbau, vocals, lyrics || down for whatever || [http://www.korg.com/us/products/drums/wavedrum_global_edition/ wavedrum] (maybe) <br />
|-<br />
| David Durst || ddurst || keyboards || preferably not pop, but that's me || (I wish) No<br />
|-<br />
| Michal Dziewonski || vesper| || drums, karaoke-grade vocals || jamming and post-sludge electronic ambient ;) || Nope, I can bring drum sticks, though<br />
|-<br />
| Alon Zakai || azakai || Guitar (mostly but not only classical/nylon-string) || Rock, Bach, anything else || No<br />
|-<br />
| Dan Gohman || sunfish || keyboards, backup vocals, non-drumset percussion, schlagenfrappe || I'll try just about anything but preferrably no ukeleles || No<br />
|-<br />
| Mark Reid || mreid || Guitar, Bass || * || No, though I could possibly bring a little pedalboard for some fx & tuning<br />
|-<br />
| Rehan Dalal || rdalal || Guitar, Vox || I'm open to anything || Yes, I'll have my baritone Strat. Will need an amp.<br />
|-<br />
| Gerv Markham || gerv || Vocals || Happy to try anything || Yes :-) <br />
|-<br />
| Georg Fritzsche || gfritzsche || Bass || jamming, funky stuff, rock, odd rythms || No<br />
|-<br />
| Syd Polk || sydpolk || soprano or alto sax + flute || jazz, classical, soul, funk, r&b || yes<br />
|-<br />
| Jb Piacentino || jb || Vocals || About anything, pref rock || Sure!<br />
|-<br />
| Nihanth Subramanya || nhnt11 || Guitar || Blues/rock, but probably anything else as well. || No :(<br />
|-<br />
| Matthew Ruttley || mruttley || Classical Guitar but can stretch to others || Early Music, Lute, Swing, Contemporary classical || No<br />
|-<br />
| Myk Melez || myk || Drums || I like both kinds of music. || Not likely.<br />
|-<br />
| Example || Example || Example || Example || <br />
|}<br />
<br />
=== Instrument Hire List Draft ===<br />
<br />
Here's what we'd likely need to hire. Note: Don't add to this it'll be updated based on the table above.<br />
If you're a brass/woodwind player it'll probably be possible to bring an instrument as the size wouldn't be too much of a problem (That is assuming we're not talking about tubas :)).<br />
<br />
{| class="wikitable"<br />
|-<br />
! Description !! Quantity<br />
|-<br />
| PA + Mixer (this will be room-size dependent) || 1<br />
|-<br />
| Vocal/Instrument Mics + stands + leads || 5<br />
|-<br />
| Electric Guitars + guitar stands + strap || 2<br />
|-<br />
| Acoustic (ElectroAcoustic) Guitars (at least 1 of which has nylon strings) + acoustic stands + strap || 3<br />
|-<br />
| Bass Guitar + stand + strap || 1<br />
|-<br />
| Bass Amp || 1<br />
|-<br />
| Guitar Amp (Fender Deluxe or similar) || 2<br />
|-<br />
| Keyboard + stand (something that can do good electric / acoustic piano sounds) || 1<br />
|-<br />
| Full drum kit + stool || 1<br />
|-<br />
| Hand percussion (bongos, tambourine, cajón, etc.) || ?<br />
|-<br />
| Kick drum mic || 1<br />
|}<br />
<br />
We are unable to rent:<br />
Digeridu<br />
Berimbau<br />
Schlagenfrappe</div>MykMelezhttps://wiki.mozilla.org/index.php?title=PluotSorbet&diff=1057235PluotSorbet2015-02-20T18:37:41Z<p>MykMelez: </p>
<hr />
<div>__NOTOC__<br />
Welcome to the j2me.js project! j2me.js is a Java virtual machine and [http://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition J2ME platform] written in JavaScript. The goal of j2me.js is to run [http://en.wikipedia.org/wiki/MIDlet MIDlets] in web apps without a native plugin.<br />
<br />
We keep j2me.js simple and small by leveraging existing Java code as much as possible, including the [http://en.wikipedia.org/wiki/PhoneME phoneME reference implementation], and implement as little as possible in JavaScript.<br />
<br />
You can run j2me.js in your [https://github.com/mozilla/j2me.js/blob/master/README.md#desktop desktop browser] (we develop with Firefox and Chrome), in the SpiderMonkey command-line tool, [https://github.com/mozilla/j2me.js/blob/master/README.md#firefoxos-device-or-emulator in the Firefox OS Simulator, or on a Firefox OS device].<br />
<br />
== Source Code ==<br />
<br />
You can find all the source code for j2me.js, plus detailed instructions on how to build and run it, at:<br />
<br />
https://github.com/mozilla/j2me.js<br />
<br />
== Bug Reporting ==<br />
<br />
Please report bugs at [https://github.com/mozilla/j2me.js/issues/new our GitHub repository].<br />
<br />
== Automated Testing ==<br />
<br />
We run [https://github.com/mozilla/j2me.js/blob/master/README.md#tests automated tests based on CasperJS and SlimerJS] on every commit to our GitHub repository, [https://travis-ci.org/mozilla/j2me.js thanks to Travis]. You can run them locally with `make test`.<br />
<br />
== Performance Profiling ==<br />
<br />
We're using [https://github.com/mozilla/j2me.js/blob/master/README.md#profiling several different tools] to assess and improve the performance of j2me.js, including both JavaScript and Java profiling. See the GitHub README for more details.<br />
<br />
== Compilation ==<br />
<br />
We've created an [https://github.com/mozilla/j2me.js/blob/master/README.md#compiling-with-aot-compiler ahead-of-time (AOT) compiler] to compile some Java code at build time.<br />
<br />
== Contact Us ==<br />
<br />
* the [http://mibbit.com/?channel=%23j2me.js&server=irc.mozilla.org #j2me.js] IRC channel on [http://irc.mozilla.org/ Mozilla's IRC network].</div>MykMelez