<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.mozilla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Janx</id>
	<title>MozillaWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.mozilla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Janx"/>
	<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/Special:Contributions/Janx"/>
	<updated>2026-11-17T01:23:27Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.17</generator>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1217055</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1217055"/>
		<updated>2019-08-27T16:02:49Z</updated>

		<summary type="html">&lt;p&gt;Janx: Update reviewbot and upliftbot owner emails&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || &lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || cdenizet@mozilla.com || rest || api-key || https://github.com/mozilla/relman-auto-nag/&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || moc@mozilla.com || rest || api-key || git-internal/puppet/modules/moc_bug_queuemon&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| reviewbot@mozilla.com || babadie@mozilla.com || Unknown || api-key; mozreview-token; phabricator-token || https://github.com/mozilla/release-services/tree/master/src/staticanalysis/bot&lt;br /&gt;
|-&lt;br /&gt;
| upliftbot@mozilla.com || babadie@mozilla.com || rest || api-key; phabricator-token || https://github.com/mozilla/release-services/tree/master/src/uplift/bot&lt;br /&gt;
|-&lt;br /&gt;
| wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync&lt;br /&gt;
|-&lt;br /&gt;
| release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use&lt;br /&gt;
|-&lt;br /&gt;
| foxsec-pytest@mozilla.com || abahnken@mozilla.com || rest; xmlrpc || api-key || https://github.com/mozilla-services/pytest-services&lt;br /&gt;
|-&lt;br /&gt;
| experimenter@mozilla.com || jbuckley@mozilla.com || rest || api-key || https://github.com/mozilla/experimenter&lt;br /&gt;
|-&lt;br /&gt;
| bugmail@firebot.glob.uno || glob@mozilla.com || rest || anon || https://github.com/globau/firebot&lt;br /&gt;
|-&lt;br /&gt;
| bteam-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard&lt;br /&gt;
|-&lt;br /&gt;
| conduit-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard/tree/conduit&lt;br /&gt;
|- &lt;br /&gt;
| jitbugs@mozilla.bugs || mgaudet@mozilla.com || n/a || n/a || Watchable Account for JavaScript JIT Bug Reviews&lt;br /&gt;
|-&lt;br /&gt;
| relops-bug-generator@mozilla.com || jwatkins@mozilla.com || n/a || n/a || Automated Bug Generation for RelOps&lt;br /&gt;
|-&lt;br /&gt;
| mozilla-apprentice@mcc.id.au || cam@mcc.id.au || rest || api-key || https://github.com/heycam/wg-tracker&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1199922</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1199922"/>
		<updated>2018-08-23T15:37:17Z</updated>

		<summary type="html">&lt;p&gt;Janx: Add upliftbot&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| bug.autolander@gmail.com   || emorley@moco (ish; informal) || rest || Username/password || https://github.com/mozilla/autolander&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || &lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || Unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || moc@mozilla.com || rest || api-key || git-internal/puppet/modules/moc_bug_queuemon&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| secbugstats@mozilla.bugs || dylan@mozilla.com || bzapi || api-key || [[BMO/SecBugStats]]&lt;br /&gt;
|-&lt;br /&gt;
| reviewbot@mozilla.com || jan@mozilla.com || Unknown || api-key; mozreview-token; phabricator-token || https://github.com/mozilla/release-services/tree/master/src/staticanalysis/bot&lt;br /&gt;
|-&lt;br /&gt;
| upliftbot@mozilla.com || jan@mozilla.com || rest || api-key; phabricator-token || https://github.com/mozilla/release-services/tree/master/src/uplift/bot&lt;br /&gt;
|-&lt;br /&gt;
| wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync&lt;br /&gt;
|-&lt;br /&gt;
| release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use&lt;br /&gt;
|-&lt;br /&gt;
| foxsec-pytest@mozilla.com || abahnken@mozilla.com || rest; xmlrpc || api-key || https://github.com/mozilla-services/pytest-services&lt;br /&gt;
|-&lt;br /&gt;
| experimenter@mozilla.com || jbuckley@mozilla.com || rest || api-key || https://github.com/mozilla/experimenter&lt;br /&gt;
|-&lt;br /&gt;
| bugmail@firebot.glob.uno || glob@mozilla.com || rest || anon || https://github.com/globau/firebot&lt;br /&gt;
|-&lt;br /&gt;
| bteam-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard&lt;br /&gt;
|-&lt;br /&gt;
| conduit-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard/tree/conduit&lt;br /&gt;
|- &lt;br /&gt;
| jitbugs@mozilla.bugs || mgaudet@mozilla.com || n/a || n/a || Watchable Account for JavaScript JIT Bug Reviews&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1199921</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1199921"/>
		<updated>2018-08-23T15:36:10Z</updated>

		<summary type="html">&lt;p&gt;Janx: Fix reviewbot repo link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| bug.autolander@gmail.com   || emorley@moco (ish; informal) || rest || Username/password || https://github.com/mozilla/autolander&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || &lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || Unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || moc@mozilla.com || rest || api-key || git-internal/puppet/modules/moc_bug_queuemon&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| secbugstats@mozilla.bugs || dylan@mozilla.com || bzapi || api-key || [[BMO/SecBugStats]]&lt;br /&gt;
|-&lt;br /&gt;
| reviewbot@mozilla.com || jan@mozilla.com || Unknown || api-key; mozreview-token; phabricator-token || https://github.com/mozilla/release-services/tree/master/src/staticanalysis/bot&lt;br /&gt;
|-&lt;br /&gt;
| wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync&lt;br /&gt;
|-&lt;br /&gt;
| release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use&lt;br /&gt;
|-&lt;br /&gt;
| foxsec-pytest@mozilla.com || abahnken@mozilla.com || rest; xmlrpc || api-key || https://github.com/mozilla-services/pytest-services&lt;br /&gt;
|-&lt;br /&gt;
| experimenter@mozilla.com || jbuckley@mozilla.com || rest || api-key || https://github.com/mozilla/experimenter&lt;br /&gt;
|-&lt;br /&gt;
| bugmail@firebot.glob.uno || glob@mozilla.com || rest || anon || https://github.com/globau/firebot&lt;br /&gt;
|-&lt;br /&gt;
| bteam-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard&lt;br /&gt;
|-&lt;br /&gt;
| conduit-dashboard@bmo.tld || glob@mozilla.com || rest || api-key || https://github.com/globau/bteam-dashboard/tree/conduit&lt;br /&gt;
|- &lt;br /&gt;
| jitbugs@mozilla.bugs || mgaudet@mozilla.com || n/a || n/a || Watchable Account for JavaScript JIT Bug Reviews&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Engineering_Workflow/Road_Map&amp;diff=1193262</id>
		<title>Engineering Workflow/Road Map</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Engineering_Workflow/Road_Map&amp;diff=1193262"/>
		<updated>2018-05-03T16:07:20Z</updated>

		<summary type="html">&lt;p&gt;Janx: Typo: s/Lango/Lando/&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Engineering Workflow Road Map =&lt;br /&gt;
&lt;br /&gt;
These are the improvements and new services we are currently working on and others that we are considering for the near future (1-2 years).  It is subject to change.&lt;br /&gt;
&lt;br /&gt;
== Current ==&lt;br /&gt;
&lt;br /&gt;
=== Phabricator integration ===&lt;br /&gt;
&lt;br /&gt;
Although our [[Phabricator]] instance has been up since September 2017, there has been ongoing work to integrate it into our tools, most notably [[BMO]].  There is a tracking bug ({{bug|1381498}}) for the remaining work before we announce general availability and start encouraging people to move over.&lt;br /&gt;
&lt;br /&gt;
The last remaining item of note is forking Arcanist so that it works with git-cinnabar ({{bug|1443375}}).&lt;br /&gt;
&lt;br /&gt;
Impact:&lt;br /&gt;
* One sole tool for review, which allows the Engineering Workflow to concentrate its efforts, and eliminates the need for contributors to learn several tools.&lt;br /&gt;
* A more intuitive interface than BMO and MozReview, with a contemporary look to appeal to new contributors.&lt;br /&gt;
* Some integration with existing tools and processes, balancing complexity and disruption.&lt;br /&gt;
* Excellent support from Phabricator&#039;s developers ([https://phacility.com Phacility]) and a large user community.&lt;br /&gt;
&lt;br /&gt;
=== Lando ===&lt;br /&gt;
&lt;br /&gt;
[https://lando.services.mozilla.com Lando] is the new automatic code-landing tool integrated with Phabricator.  It is (or at least will be) functionally similar to MozReview&#039;s Autoland but is designed to be more maintainable and extensible by being less tightly coupled to the review tool.&lt;br /&gt;
&lt;br /&gt;
Impact:&lt;br /&gt;
* One-button landing which can be initiated by anyone with appropriate SCM access.&lt;br /&gt;
* Queues landings if the trees are closed.&lt;br /&gt;
* Becomes a common gateway to mozilla-central (and other repos) which allows more process and security improvements (see below).&lt;br /&gt;
&lt;br /&gt;
=== Vendor manifests ===&lt;br /&gt;
&lt;br /&gt;
Provide a common structure, process, and tools for managing third-party code in mozilla-central.  An [https://groups.google.com/forum/?pli=1#!topic/mozilla.dev.platform/-B8MECCeJnM Intent to Require] was posted to dev.platform on 2018/04/10 and finalized on 2018/10/18.  Follow the tracking bug ({{bug|1454867}}) for progress.&lt;br /&gt;
&lt;br /&gt;
Impact:&lt;br /&gt;
* Third-party code in mozilla-central is obvious and easy to find.&lt;br /&gt;
* Standard processes to increase predictability of updates to third-party code.&lt;br /&gt;
* Tools to ease updates to third-party code.&lt;br /&gt;
&lt;br /&gt;
== Future ==&lt;br /&gt;
&lt;br /&gt;
=== Enforced reviewers ===&lt;br /&gt;
&lt;br /&gt;
=== Intent-to-land ===&lt;br /&gt;
&lt;br /&gt;
=== Lando Try support ===&lt;br /&gt;
&lt;br /&gt;
=== Lando confidential-revision support ===&lt;br /&gt;
&lt;br /&gt;
=== Lando stacked landing ===&lt;br /&gt;
&lt;br /&gt;
=== cinnabar-less Git(Hub) gecko-dev support ===&lt;br /&gt;
&lt;br /&gt;
=== Lando headless client API support ===&lt;br /&gt;
&lt;br /&gt;
=== Lando and Phabricator backout support ===&lt;br /&gt;
&lt;br /&gt;
=== Transplant service improvements ===&lt;br /&gt;
&lt;br /&gt;
=== Lando Git support ===&lt;br /&gt;
&lt;br /&gt;
=== Auth0 integration with BMO ===&lt;br /&gt;
&lt;br /&gt;
=== Markdown in BMO ===&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1189726</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1189726"/>
		<updated>2018-03-05T15:27:00Z</updated>

		<summary type="html">&lt;p&gt;Janx: :review now also uses an API key&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| bug.autolander@gmail.com   || emorley@moco (ish; informal) || rest || Username/password || https://github.com/mozilla/autolander&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || Unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || pradcliffe@mozilla.com || rest || api-key || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| secbugstats@mozilla.bugs || dylan@mozilla.com || bzapi || api-key || [[BMO/SecBugStats]]&lt;br /&gt;
|-&lt;br /&gt;
| reviewbot@mozilla.com || jan@mozilla.com || Unknown || api-key; mozreview-token; phabricator-token || https://github.com/mozilla-releng/services/tree/master/src/shipit_static_analysis&lt;br /&gt;
|-&lt;br /&gt;
| wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync&lt;br /&gt;
|-&lt;br /&gt;
| release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1189725</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1189725"/>
		<updated>2018-03-05T15:06:05Z</updated>

		<summary type="html">&lt;p&gt;Janx: Update :reviewbot&amp;#039;s used credentials (MozReview + Phabricator tokens; no BMO API key)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| bug.autolander@gmail.com   || emorley@moco (ish; informal) || rest || Username/password || https://github.com/mozilla/autolander&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || Unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || pradcliffe@mozilla.com || rest || api-key || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| secbugstats@mozilla.bugs || dylan@mozilla.com || bzapi || api-key || [[BMO/SecBugStats]]&lt;br /&gt;
|-&lt;br /&gt;
| reviewbot@mozilla.com || jan@mozilla.com || Unknown || Tokens (MozReview + Phabricator) || https://github.com/mozilla-releng/services/tree/master/src/shipit_static_analysis&lt;br /&gt;
|-&lt;br /&gt;
| wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync&lt;br /&gt;
|-&lt;br /&gt;
| release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1189721</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1189721"/>
		<updated>2018-03-05T15:03:45Z</updated>

		<summary type="html">&lt;p&gt;Janx: Update :reviewbot&amp;#039;s email address&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| bug.autolander@gmail.com   || emorley@moco (ish; informal) || rest || Username/password || https://github.com/mozilla/autolander&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || Unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || pradcliffe@mozilla.com || rest || api-key || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| secbugstats@mozilla.bugs || dylan@mozilla.com || bzapi || api-key || [[BMO/SecBugStats]]&lt;br /&gt;
|-&lt;br /&gt;
| reviewbot@mozilla.com || jan@mozilla.com || Unknown || api-key || https://github.com/mozilla-releng/services/tree/master/src/shipit_static_analysis&lt;br /&gt;
|-&lt;br /&gt;
| wptsync@mozilla.bugs || jgraham@mozilla.com || rest || api-key || https://github.com/mozilla/wpt-sync&lt;br /&gt;
|-&lt;br /&gt;
| release+phabricator@mozilla.com || sfraser@mozilla.com || rest || api-key || Unknown / Phabricator use&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1187480</id>
		<title>BMO/Bot Registry</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=BMO/Bot_Registry&amp;diff=1187480"/>
		<updated>2018-01-24T14:10:24Z</updated>

		<summary type="html">&lt;p&gt;Janx: Add :reviewbot&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Some times you want a BMO account that is not a real person.&lt;br /&gt;
That&#039;s okay -- in fact it is a good security measure!&lt;br /&gt;
&lt;br /&gt;
However this comes with some problems -- if we (the bmo admins) can&#039;t tell who owns a bot,&lt;br /&gt;
and we have to make a decision that might break we have no way of informing the owner except&lt;br /&gt;
to break it and wait to hear back. This list below is by no means mandatory, but if you fill it out,&lt;br /&gt;
we can help avoid future breakages!&lt;br /&gt;
&lt;br /&gt;
If you include a link to the repo, things can be even smoother.&lt;br /&gt;
&lt;br /&gt;
Additionally, if your bot misbehaves, we can tell you about it rather than just blocking it. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Bot Bugmail !! Owner Bugmail !! API (xmlrpc, jsonrpc, bzapi, or rest) !! Token or API Key!! Repo&lt;br /&gt;
|-&lt;br /&gt;
| pulsebot@bots.tld || mh+mozilla@glandium.org || rest || api-key || https://github.com/glandium/pulsebot/&lt;br /&gt;
|-&lt;br /&gt;
| bug.autolander@gmail.com   || emorley@moco (ish; informal) || rest || Username/password || https://github.com/mozilla/autolander&lt;br /&gt;
|-&lt;br /&gt;
| treeherderbugbot@gmail.com || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || xmlrpc || Username/password || [https://github.com/github/github-services/blob/master/lib/services/bugzilla.rb GitHub&#039;s Bugzilla integration]&lt;br /&gt;
|-&lt;br /&gt;
| intermittent-bug-filer@mozilla.bugs || [https://lists.mozilla.org/listinfo/tools-treeherder tools-treeherder] || rest || api-key || https://github.com/mozilla/treeherder&lt;br /&gt;
|-&lt;br /&gt;
| orangefactor@bots.tld   || auto-tools@moco || rest || api-key || https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
|-&lt;br /&gt;
| webops-kanban@mozilla.bugs || atoll || Unknown || Token || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| triagebot-api@mozilla.bugs || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| bznag@mozilla.bugs         || mhoye@mozilla.com || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| mozilla+bugcloser@davedash.com || Unknown || Unknown || Token (github) || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| release-mgmt-account-bot@mozilla.tld || Unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| slaveapi@mozilla.releng.tld || release@mozilla.com || Unknown || Unknown || https://github.com/mozilla/build-slaveapi&lt;br /&gt;
|-&lt;br /&gt;
| flow2bugs@netops.bugs || unknown || Unknown || Unknown || Unknown&lt;br /&gt;
|- &lt;br /&gt;
| webcompat-bugs@mozilla.bugs || miket@mozilla.com || rest || api-key || TBD&lt;br /&gt;
|-&lt;br /&gt;
| pulgasaur@mozilla.bugs || peterbe@mozilla.com || rest || api-key || https://github.com/mozilla/github-bugzilla-pr-linker&lt;br /&gt;
|-&lt;br /&gt;
| moc-queue-bot@mozilla.bugs || pradcliffe@mozilla.com || rest || api-key || Unknown&lt;br /&gt;
|-&lt;br /&gt;
| omphalos@mozilla.bugs || mgoodwin@mozilla.com || rest || api-key || https://github.com/mozilla/OneCRL-Tools&lt;br /&gt;
|-&lt;br /&gt;
| bug-husbandry-bot@mozilla.bugs || ehumphries@moco || rest || api-key || [[Bugmasters/Projects/Bug_Handling/Bug_Husbandry]]&lt;br /&gt;
|-&lt;br /&gt;
| secbugstats@mozilla.bugs || dylan@mozilla.com || bzapi || api-key || [[BMO/SecBugStats]]&lt;br /&gt;
|-&lt;br /&gt;
| jankeromnes+clangbot@mozilla.com || jan@mozilla.com || Unknown || api-key || https://github.com/mozilla-releng/services/tree/master/src/shipit_static_analysis&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Conduit/Tech_Stack&amp;diff=1175675</id>
		<title>EngineeringProductivity/Projects/Conduit/Tech Stack</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Conduit/Tech_Stack&amp;diff=1175675"/>
		<updated>2017-07-13T14:53:59Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Javascript */ mention ES6&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Our Technologies =&lt;br /&gt;
&lt;br /&gt;
The following is a non-exhaustive lists of the technologies the team primarily uses. When developing a new system, especially under tight time constraints, it is a good idea to stick with these technologies.&lt;br /&gt;
&lt;br /&gt;
== Programming Languages ==&lt;br /&gt;
&lt;br /&gt;
=== Python (3.5+) ===&lt;br /&gt;
&lt;br /&gt;
Python is our team&#039;s primary programming language. It is a versatile language which is both easy to learn and powerful. Much of our team&#039;s previously developed software is built with Python.&lt;br /&gt;
&lt;br /&gt;
Python 3 is the preferred version as it is the future of Python development and most libraries are compatible.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* Python has &#039;&#039;good enough&#039;&#039; performance for most tasks and is adequate until measurements show otherwise.&lt;br /&gt;
* There are many existing Python services interacting with Mozilla&#039;s various systems, which may serve as examples.&lt;br /&gt;
&lt;br /&gt;
The following is a set of python libraries commonly used by our team (It&#039;s best to have a concrete reason when considering an alternative library that is not listed here):&lt;br /&gt;
&lt;br /&gt;
* click&lt;br /&gt;
* connexion&lt;br /&gt;
* Django&lt;br /&gt;
* Flask&lt;br /&gt;
* Kombu&lt;br /&gt;
* pytest&lt;br /&gt;
* requests&lt;br /&gt;
* SQLalchemy&lt;br /&gt;
&lt;br /&gt;
=== Python (2.7.x) ===&lt;br /&gt;
&lt;br /&gt;
Python 2 is used where version 3 is inappropriate. This includes the following locations:&lt;br /&gt;
&lt;br /&gt;
* Mercurial extensions (mercurial&#039;s python 3 support is incomplete 2017-06-16)&lt;br /&gt;
* Scripts packaged with the Firefox build environment&lt;br /&gt;
* Modifications to existing systems built with Python 2&lt;br /&gt;
&lt;br /&gt;
=== Javascript ===&lt;br /&gt;
&lt;br /&gt;
Javascript (ES6) is used by our team for building client side web applications.&lt;br /&gt;
&lt;br /&gt;
== Supporting Services ==&lt;br /&gt;
&lt;br /&gt;
=== uWSGI ===&lt;br /&gt;
&lt;br /&gt;
uWSGI is our preferred WSGI server/gateway.&lt;br /&gt;
&lt;br /&gt;
=== PostgreSQL ===&lt;br /&gt;
&lt;br /&gt;
PostgreSQL is our preferred database.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* Traditional RDBMS&#039; are well understood by our development team&lt;br /&gt;
* Our operations team is more experienced with SQL systems vs newer NOSQL databases&lt;br /&gt;
* PostgreSQL can fulfill a similar role to NOSQL databases using the built-in JSON data types.&lt;br /&gt;
* There are mature libraries and tools for working with PostgreSQL&lt;br /&gt;
* Performance characteristics are well understood and adequate&lt;br /&gt;
&lt;br /&gt;
=== Redis ===&lt;br /&gt;
&lt;br /&gt;
Redis is the preferred choice for in-memory storage of data. It performs comparably with memcached in traditional caching scenarios but also supports more powerful data types.&lt;br /&gt;
&lt;br /&gt;
Redis is also suitable as a persistent data store when configured correctly. This is at the expense of some performance, but may be used as such where it makes sense.&lt;br /&gt;
&lt;br /&gt;
=== Amazon SNS/SQS ===&lt;br /&gt;
&lt;br /&gt;
Amazon&#039;s notification and messaging services are the preferred choice when a reliable internal message queue is required. &lt;br /&gt;
&lt;br /&gt;
=== RabbitMQ (Mozilla&#039;s Pulse) ===&lt;br /&gt;
&lt;br /&gt;
Messages which are relevant to a wider audience may be published to Mozilla&#039;s Pulse service. While it is possible to use Pulse for non-sensitive internal messages, Amazon SNS/SQS is preferred.&lt;br /&gt;
&lt;br /&gt;
== Conceptual Choices ==&lt;br /&gt;
&lt;br /&gt;
=== OpenAPI (Swagger) ===&lt;br /&gt;
&lt;br /&gt;
=== RESTful ===&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2017-03-06&amp;diff=1164662</id>
		<title>EngineeringProductivity/Meetings/2017-03-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2017-03-06&amp;diff=1164662"/>
		<updated>2017-03-06T12:20:42Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Newsgroup and Blog Posts */ mention two new Janitor posts&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** deepasrijit1105 added layout/tools/reftest to the flake8 linter in {{bug|1280572}}&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
* [ahal] [https://ahal.ca/blog/2017/fuzzy-try-chooser/ A course of action for replacing try syntax]&lt;br /&gt;
* [ahal] [https://ahal.ca/blog/2017/mercurial-absorb/ Absorbing changes into a commit series with Mercurial]&lt;br /&gt;
* [janx] [https://janitor.technology/blog/ Janitor News #7; Janitor Alpha 0.0.7 is Live]&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2017-02-06&amp;diff=1161985</id>
		<title>EngineeringProductivity/Meetings/2017-02-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2017-02-06&amp;diff=1161985"/>
		<updated>2017-02-06T17:08:27Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Notices, Highlights, Roundtable */ mention Firefox IDE&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
* No meeting on Feb 20, US holiday&lt;br /&gt;
* Updated 2017 OKR&#039;s - https://docs.google.com/document/d/1jY7-bCR-ra7jnC06YvGySe_Fqb8lw3dyizNOYPluyOk/edit&lt;br /&gt;
** Priorities&lt;br /&gt;
**# Data center migration (TaskCluster, move services to AWS, implement disaster recovery)&lt;br /&gt;
**# TaskCluster OSX (must be done by end of June due to data center migration)&lt;br /&gt;
**# Quantum Suport&lt;br /&gt;
**# Security (primarily Autoland for Q1/Q2)&lt;br /&gt;
**# Aurora Plan&lt;br /&gt;
**# Intermittent Oranges (Project Stockwell, auto classify, manifest view in Treeherder)&lt;br /&gt;
**# Block Bad Commits (improved code coverage, static analysis, Try usage)&lt;br /&gt;
**# TaskCluster Linux&lt;br /&gt;
**# TaskCluster Windows&lt;br /&gt;
**# ShipIt (releng only)&lt;br /&gt;
* [janx] Centralizing access to our tools &amp;amp; services in a Janitor-based Firefox IDE?&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
About: Sheriffing - January Edition :) https://groups.google.com/forum/#!topic/mozilla.dev.platform/1Yobxt-5vjc&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2017-01-09&amp;diff=1158943</id>
		<title>EngineeringProductivity/Meetings/2017-01-09</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2017-01-09&amp;diff=1158943"/>
		<updated>2017-01-09T11:55:52Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Notices, Highlights, Roundtable */ ask for more JS interviewers for Janitor summer internship&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
* Welcome Israel Madueme!&lt;br /&gt;
* Google Summer of Code, https://wiki.mozilla.org/Community:SummerOfCode17:Brainstorming&lt;br /&gt;
** Deadline to submit proposals is February 6&lt;br /&gt;
* Deadline to submit Global Wellness expenses is this Friday, January 13&lt;br /&gt;
* Deliverables and OKR&#039;s in 2017&lt;br /&gt;
** [https://docs.google.com/document/d/1OcQWksoBXmjXTTUXMqfqtlEQj4nQefXXV2kz7areUWs/edit Release &amp;amp; Productivity OKR&#039;s for 2017]&lt;br /&gt;
** [https://docs.google.com/spreadsheets/d/1xGa5tc0Ies5Hz6JTxv6FhD2bxy_JLUFF3uR7EXBDR7w/edit#gid=0 Engineering Productivity OKR&#039;s for Q1]&lt;br /&gt;
* Looking for 2-3 more JS interviewers to help choose an A-Team summer intern:&lt;br /&gt;
** [https://careers.mozilla.org/position/gh/500057 Internship offer] (look for &amp;quot;Engineering Productivity Intern&amp;quot;)&lt;br /&gt;
** Jan will mentor, Maja and Will already volunteered for interviews (thanks!)&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [https://groups.google.com/forum/#!topic/mozilla.tools.bmo/YLGLdzdNucI Changing the default bug view for BMO] (dkl) (also [https://groups.google.com/forum/#!topic/mozilla.dev.platform/_AFaUi3JQhs cross-posted to dev.platform])&lt;br /&gt;
* [https://emceeaich.dreamwidth.org/198575.html How To Tag Comments in Bugzilla So We Can Respond Appropriately] (emceeaich)&lt;br /&gt;
* [https://groups.google.com/forum/#!topic/mozilla.governance/q9B3gPKq4uI Changes to etiquette.html in bugzilla.mozilla.org] (emceeaich)&lt;br /&gt;
* [https://emceeaich.dreamwidth.org/199563.html BMO Roadmap for the 1st Half of 2017] (emceeaich)&lt;br /&gt;
* [https://mrcote.info/ BMO in 2016] (mcote)&lt;br /&gt;
* [https://groups.google.com/forum/#!topic/mozilla.tools.bmo/tp4dSwUfKSA Moratorium on custom bug-entry form development] (mcote)&lt;br /&gt;
* [https://groups.google.com/forum/#!topic/mozilla.tools/KihdAlunkvo New process for Release &amp;amp; Productivity in 2017: RFCs] (wlach)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-11-14&amp;diff=1154604</id>
		<title>EngineeringProductivity/Meetings/2016-11-14</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-11-14&amp;diff=1154604"/>
		<updated>2016-11-14T18:04:12Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Other Project Updates */ mention Janitor on Activate&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
* The future of issue tracking and code review at Mozilla&lt;br /&gt;
* 2017 planning update&lt;br /&gt;
* Hawaii Team Events&lt;br /&gt;
* Treeherder file- or manifest-based UI&lt;br /&gt;
** Discussing during the next Treeherder meeting, Wednesday 9am PST, A-Team Vidyo room&lt;br /&gt;
** Doc for discussion: https://docs.google.com/document/d/1jaxLMCzZOiril0eCBvCjwqQ8IS0ITa-32Kkmyt27kJs/edit#heading=h.jmxr0jhy3sqr&lt;br /&gt;
* Release &amp;amp; Productivity Q4 OKR Tracking&lt;br /&gt;
** https://docs.google.com/a/mozilla.com/spreadsheets/d/1p3wTY_QmdRHJGGEoIvJh42bf4sgaakoV6p4Q-oh_0eA/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [https://janitor.technology/blog/ Janitor News—November 2016] (janx)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
* We&#039;re working with Brian King from Participation to bring the Janitor to all Mozilla Spaces around the world by adding it to https://activate.mozilla.community/ (janx, forgot to mention this in the newsletter above)&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-11-14&amp;diff=1154589</id>
		<title>EngineeringProductivity/Meetings/2016-11-14</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-11-14&amp;diff=1154589"/>
		<updated>2016-11-14T17:21:12Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Newsgroup and Blog Posts */ Added this November&amp;#039;s Janitor newsletter&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
* The future of issue tracking and code review at Mozilla&lt;br /&gt;
* 2017 planning update&lt;br /&gt;
* Hawaii Team Events&lt;br /&gt;
* Release &amp;amp; Productivity Q4 OKR Tracking&lt;br /&gt;
** https://docs.google.com/a/mozilla.com/spreadsheets/d/1p3wTY_QmdRHJGGEoIvJh42bf4sgaakoV6p4Q-oh_0eA/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [https://janitor.technology/blog/ Janitor News—November 2016] (janx)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153096</id>
		<title>EngineeringProductivity/Meetings/2016-10-31</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153096"/>
		<updated>2016-10-31T16:55:03Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Holidays and Trips */ (be more specific about bank holidays)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Francesco Pischedda [:fpsd] - Fixed |mach lint| to ensure the same versions of flake8 are used locally as are used in automation ({{bug|1285555}})&lt;br /&gt;
* [jgriffin] Platform Operations has a new name - Release and Productivity&lt;br /&gt;
* [jgriffin] Remember to submit your name for about:credits in Firefox - https://docs.google.com/forms/d/e/1FAIpQLSfgez4NGkespvSVblBkMDjWnsZm9PQQH41vbAnkOFQRGl30JQ/viewform&lt;br /&gt;
** https://www.mozilla.org/credits/&lt;br /&gt;
* [jgriffin] Recognition program reminder&lt;br /&gt;
** https://goo.gl/forms/qhwxYKVn59p5qoqn1&lt;br /&gt;
* [jgriffin] Hawaii Electives&lt;br /&gt;
** Our Electives are now Firefox Sessions, will be held at other times during the day&lt;br /&gt;
* [jgriffin] Q4 Deliverables&lt;br /&gt;
** Please submit the status of your October deliverable in workday by the end of the week&lt;br /&gt;
** Please submit a new deliverable for November-December by Monday, Nov 7&lt;br /&gt;
** Current Q4 OKR&#039;s for Release &amp;amp; Productivity: https://docs.google.com/a/mozilla.com/spreadsheets/d/1XFnRw8fe3i9_0jtVCoWFredW7h_KzKIcRApgmX8VAi4/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [http://wlach.github.io/blog/2016/10/slow-treeherder-fast-treeherder/ Slow Treeherder, fast Treeherder] (wlach)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [janx] Off Nov 1 and 11 (bank holidays in France), remoting Nov 4 to 10 in Santorini (Greece)&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;br /&gt;
&lt;br /&gt;
* [ekyle] Do we have a distributed process monitor? One with remote workers that can trigger jobs, and monitor them?  Monit?&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153094</id>
		<title>EngineeringProductivity/Meetings/2016-10-31</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153094"/>
		<updated>2016-10-31T16:47:23Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Holidays and Trips */ (shorter sentence)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Francesco Pischedda [:fpsd] - Fixed |mach lint| to ensure the same versions of flake8 are used locally as are used in automation ({{bug|1285555}})&lt;br /&gt;
* [jgriffin] Platform Operations has a new name - Release and Productivity&lt;br /&gt;
* [jgriffin] Remember to submit your name for about:credits in Firefox - https://docs.google.com/forms/d/e/1FAIpQLSfgez4NGkespvSVblBkMDjWnsZm9PQQH41vbAnkOFQRGl30JQ/viewform&lt;br /&gt;
** https://www.mozilla.org/credits/&lt;br /&gt;
* [jgriffin] Recognition program reminder&lt;br /&gt;
** https://goo.gl/forms/qhwxYKVn59p5qoqn1&lt;br /&gt;
* [jgriffin] Hawaii Electives&lt;br /&gt;
** Our Electives are now Firefox Sessions, will be held at other times during the day&lt;br /&gt;
* [jgriffin] Q4 Deliverables&lt;br /&gt;
** Please submit the status of your October deliverable in workday by the end of the week&lt;br /&gt;
** Please submit a new deliverable for November-December by Monday, Nov 7&lt;br /&gt;
** Current Q4 OKR&#039;s for Release &amp;amp; Productivity: https://docs.google.com/a/mozilla.com/spreadsheets/d/1XFnRw8fe3i9_0jtVCoWFredW7h_KzKIcRApgmX8VAi4/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [http://wlach.github.io/blog/2016/10/slow-treeherder-fast-treeherder/ Slow Treeherder, fast Treeherder] (wlach)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [janx] Off Nov 1 and 11 (French holidays), remoting Nov 4 to 10 in Santorini (Greece)&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;br /&gt;
&lt;br /&gt;
* [ekyle] Do we have a distributed process monitor? One with remote workers that can trigger jobs, and monitor them?  Monit?&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153093</id>
		<title>EngineeringProductivity/Meetings/2016-10-31</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153093"/>
		<updated>2016-10-31T16:46:11Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Holidays and Trips */ (shorter dates)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Francesco Pischedda [:fpsd] - Fixed |mach lint| to ensure the same versions of flake8 are used locally as are used in automation ({{bug|1285555}})&lt;br /&gt;
* [jgriffin] Platform Operations has a new name - Release and Productivity&lt;br /&gt;
* [jgriffin] Remember to submit your name for about:credits in Firefox - https://docs.google.com/forms/d/e/1FAIpQLSfgez4NGkespvSVblBkMDjWnsZm9PQQH41vbAnkOFQRGl30JQ/viewform&lt;br /&gt;
** https://www.mozilla.org/credits/&lt;br /&gt;
* [jgriffin] Recognition program reminder&lt;br /&gt;
** https://goo.gl/forms/qhwxYKVn59p5qoqn1&lt;br /&gt;
* [jgriffin] Hawaii Electives&lt;br /&gt;
** Our Electives are now Firefox Sessions, will be held at other times during the day&lt;br /&gt;
* [jgriffin] Q4 Deliverables&lt;br /&gt;
** Please submit the status of your October deliverable in workday by the end of the week&lt;br /&gt;
** Please submit a new deliverable for November-December by Monday, Nov 7&lt;br /&gt;
** Current Q4 OKR&#039;s for Release &amp;amp; Productivity: https://docs.google.com/a/mozilla.com/spreadsheets/d/1XFnRw8fe3i9_0jtVCoWFredW7h_KzKIcRApgmX8VAi4/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [http://wlach.github.io/blog/2016/10/slow-treeherder-fast-treeherder/ Slow Treeherder, fast Treeherder] (wlach)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [janx] Off Nov 1 and 11 (French holidays), remoting in Santorini (Greece) from Nov 4 to 10&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;br /&gt;
&lt;br /&gt;
* [ekyle] Do we have a distributed process monitor? One with remote workers that can trigger jobs, and monitor them?  Monit?&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153092</id>
		<title>EngineeringProductivity/Meetings/2016-10-31</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-31&amp;diff=1153092"/>
		<updated>2016-10-31T16:45:30Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Holidays and Trips */ add French holidays and trip to Santorini&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Francesco Pischedda [:fpsd] - Fixed |mach lint| to ensure the same versions of flake8 are used locally as are used in automation ({{bug|1285555}})&lt;br /&gt;
* [jgriffin] Platform Operations has a new name - Release and Productivity&lt;br /&gt;
* [jgriffin] Remember to submit your name for about:credits in Firefox - https://docs.google.com/forms/d/e/1FAIpQLSfgez4NGkespvSVblBkMDjWnsZm9PQQH41vbAnkOFQRGl30JQ/viewform&lt;br /&gt;
** https://www.mozilla.org/credits/&lt;br /&gt;
* [jgriffin] Recognition program reminder&lt;br /&gt;
** https://goo.gl/forms/qhwxYKVn59p5qoqn1&lt;br /&gt;
* [jgriffin] Hawaii Electives&lt;br /&gt;
** Our Electives are now Firefox Sessions, will be held at other times during the day&lt;br /&gt;
* [jgriffin] Q4 Deliverables&lt;br /&gt;
** Please submit the status of your October deliverable in workday by the end of the week&lt;br /&gt;
** Please submit a new deliverable for November-December by Monday, Nov 7&lt;br /&gt;
** Current Q4 OKR&#039;s for Release &amp;amp; Productivity: https://docs.google.com/a/mozilla.com/spreadsheets/d/1XFnRw8fe3i9_0jtVCoWFredW7h_KzKIcRApgmX8VAi4/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
&lt;br /&gt;
* [http://wlach.github.io/blog/2016/10/slow-treeherder-fast-treeherder/ Slow Treeherder, fast Treeherder] (wlach)&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [janx] Off November 1 and 11 (French holidays), remoting in Santorini (Greece) from November 4 to 10&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;br /&gt;
&lt;br /&gt;
* [ekyle] Do we have a distributed process monitor? One with remote workers that can trigger jobs, and monitor them?  Monit?&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-17&amp;diff=1151524</id>
		<title>EngineeringProductivity/Meetings/2016-10-17</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-17&amp;diff=1151524"/>
		<updated>2016-10-17T17:21:13Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Notices, Highlights, Roundtable */ add item about RRA&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
* [jgriffin] Hawaii meetings&lt;br /&gt;
** Electives&lt;br /&gt;
*** Intermittent Oranges (jmaher, wlach, gbrown)&lt;br /&gt;
*** Developer productivity hacks, signups: https://docs.google.com/spreadsheets/d/15KONopoJ8YrQrvSBvHeHsOnJ5Vt9DOK89RqNBJ_lmUU/edit#gid=0&lt;br /&gt;
* [jgriffin] Deliverables and OKR&#039;s, part II&lt;br /&gt;
** Current OKR&#039;s for Platform Ops: https://docs.google.com/a/mozilla.com/spreadsheets/d/19SX3WLbxj9KDYbdnhbZ1JoRf-mV77WQxsK0uu-6xdMY/edit?usp=sharing&lt;br /&gt;
* [janx] Completed RRA for Janitor, and it was very helpful&lt;br /&gt;
** (Rapid Risk Analysis = ~30-45min high level discussion with security)&lt;br /&gt;
** Take aways:&lt;br /&gt;
*** More red flags than expected, having RRA early on can be very useful, e.g. during design&lt;br /&gt;
*** Protecting developer credentials on shared infra is hard&lt;br /&gt;
*** Janitor will probably be capped to SCM Level 1&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
* [mcote] [https://mrcote.info/blog/2016/10/12/mozreview-ui-refactoring/ MozReview UI Refactoring]&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-03&amp;diff=1149946</id>
		<title>EngineeringProductivity/Meetings/2016-10-03</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-03&amp;diff=1149946"/>
		<updated>2016-10-03T17:03:57Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Notices, Highlights, Roundtable */ don&amp;#039;t edit mcote&amp;#039;s entry&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Prabhjyot Sodhi (:psd) for adding testing/mochitest to the flake8 linter, and for starting work to add a new mozlint formatter&lt;br /&gt;
** Francesco Pischedda (:fpsd) for adding testing/mozbase to the flake8 linter (and fixing over 2000 lint errors in the process)&lt;br /&gt;
* [jgriffin] &amp;quot;Electives&amp;quot; for Hawaii&lt;br /&gt;
* [mcote] [[Security/Guidelines/Web_Security|Guidelines on web security]]&lt;br /&gt;
** [janx] Mozilla Observatory can help: https://observatory.mozilla.org/&lt;br /&gt;
* [jgriffin] Please add notes about progress and accomplishments for Q3 to https://docs.google.com/document/d/1iWAybhvGqeq9JimW5Mb_k9OIkVUBCEXhHK5g6LGczMo/edit#heading=h.7ijtimhv7d2b so I can write the team Quarterly Update&lt;br /&gt;
* [jgriffin] Q3 wrapup; Q4 planning&lt;br /&gt;
** OKR docs: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=61251893&lt;br /&gt;
** Q4 OKR&#039;s for Platform Operations: https://docs.google.com/spreadsheets/d/1_3342TYxZMaDTnGDpMFH5t53jCehnAPzL6u5ChuXbks/edit?usp=sharing&lt;br /&gt;
** Deliverables by month&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
* https://gbrownmozilla.wordpress.com/2016/09/30/firefox-for-android-performance-measures-q3-check-up-2/&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
Please update https://goo.gl/pGWqqc with the status of your Q3 deliverables. &lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [rwood] - pto October 3rd-17th incl.&lt;br /&gt;
* [wlach] - pto October 3rd-5th&lt;br /&gt;
* [jgriffin] - in PDX for Security Roadmap work week Oct 4 - 6&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-03&amp;diff=1149945</id>
		<title>EngineeringProductivity/Meetings/2016-10-03</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-03&amp;diff=1149945"/>
		<updated>2016-10-03T17:02:24Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Notices, Highlights, Roundtable */ add my name next to my note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Prabhjyot Sodhi (:psd) for adding testing/mochitest to the flake8 linter, and for starting work to add a new mozlint formatter&lt;br /&gt;
** Francesco Pischedda (:fpsd) for adding testing/mozbase to the flake8 linter (and fixing over 2000 lint errors in the process)&lt;br /&gt;
* [jgriffin] &amp;quot;Electives&amp;quot; for Hawaii&lt;br /&gt;
* [mcote]&lt;br /&gt;
** [[Security/Guidelines/Web_Security|Guidelines on web security]]&lt;br /&gt;
** [janx] Mozilla Observatory can help: https://observatory.mozilla.org/&lt;br /&gt;
* [jgriffin] Please add notes about progress and accomplishments for Q3 to https://docs.google.com/document/d/1iWAybhvGqeq9JimW5Mb_k9OIkVUBCEXhHK5g6LGczMo/edit#heading=h.7ijtimhv7d2b so I can write the team Quarterly Update&lt;br /&gt;
* [jgriffin] Q3 wrapup; Q4 planning&lt;br /&gt;
** OKR docs: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=61251893&lt;br /&gt;
** Q4 OKR&#039;s for Platform Operations: https://docs.google.com/spreadsheets/d/1_3342TYxZMaDTnGDpMFH5t53jCehnAPzL6u5ChuXbks/edit?usp=sharing&lt;br /&gt;
** Deliverables by month&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
* https://gbrownmozilla.wordpress.com/2016/09/30/firefox-for-android-performance-measures-q3-check-up-2/&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
Please update https://goo.gl/pGWqqc with the status of your Q3 deliverables. &lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [rwood] - pto October 3rd-17th incl.&lt;br /&gt;
* [wlach] - pto October 3rd-5th&lt;br /&gt;
* [jgriffin] - in PDX for Security Roadmap work week Oct 4 - 6&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-03&amp;diff=1149944</id>
		<title>EngineeringProductivity/Meetings/2016-10-03</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Meetings/2016-10-03&amp;diff=1149944"/>
		<updated>2016-10-03T17:00:45Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Notices, Highlights, Roundtable */ add link to Mozilla Observatory&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Notices, Highlights, Roundtable =&lt;br /&gt;
* Significant Contributions&lt;br /&gt;
** Prabhjyot Sodhi (:psd) for adding testing/mochitest to the flake8 linter, and for starting work to add a new mozlint formatter&lt;br /&gt;
** Francesco Pischedda (:fpsd) for adding testing/mozbase to the flake8 linter (and fixing over 2000 lint errors in the process)&lt;br /&gt;
* [jgriffin] &amp;quot;Electives&amp;quot; for Hawaii&lt;br /&gt;
* [mcote]&lt;br /&gt;
** [[Security/Guidelines/Web_Security|Guidelines on web security]]&lt;br /&gt;
** Mozilla Observatory can help: https://observatory.mozilla.org/&lt;br /&gt;
* [jgriffin] Please add notes about progress and accomplishments for Q3 to https://docs.google.com/document/d/1iWAybhvGqeq9JimW5Mb_k9OIkVUBCEXhHK5g6LGczMo/edit#heading=h.7ijtimhv7d2b so I can write the team Quarterly Update&lt;br /&gt;
* [jgriffin] Q3 wrapup; Q4 planning&lt;br /&gt;
** OKR docs: https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=61251893&lt;br /&gt;
** Q4 OKR&#039;s for Platform Operations: https://docs.google.com/spreadsheets/d/1_3342TYxZMaDTnGDpMFH5t53jCehnAPzL6u5ChuXbks/edit?usp=sharing&lt;br /&gt;
** Deliverables by month&lt;br /&gt;
&lt;br /&gt;
= Newsgroup and Blog Posts =&lt;br /&gt;
* https://gbrownmozilla.wordpress.com/2016/09/30/firefox-for-android-performance-measures-q3-check-up-2/&lt;br /&gt;
&lt;br /&gt;
= Goal Updates =&lt;br /&gt;
&lt;br /&gt;
Please update https://goo.gl/pGWqqc with the status of your Q3 deliverables. &lt;br /&gt;
&lt;br /&gt;
= Other Project Updates =&lt;br /&gt;
&lt;br /&gt;
= Holidays and Trips =&lt;br /&gt;
* [rwood] - pto October 3rd-17th incl.&lt;br /&gt;
* [wlach] - pto October 3rd-5th&lt;br /&gt;
* [jgriffin] - in PDX for Security Roadmap work week Oct 4 - 6&lt;br /&gt;
&lt;br /&gt;
= Misc =&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148281</id>
		<title>EngineeringProductivity/Projects/Everything</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148281"/>
		<updated>2016-09-19T17:46:58Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Janitor */ s/Try/Treeherder/&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Project Table ==&lt;br /&gt;
&lt;br /&gt;
The project table has been moved to https://wiki.mozilla.org/EngineeringProductivity/Projects&lt;br /&gt;
&lt;br /&gt;
== Motivation == &lt;br /&gt;
&lt;br /&gt;
This page is to help diagram all the various things the A*Team has built and continue to support.  &lt;br /&gt;
&lt;br /&gt;
The plan is to draw high level components/systems, and links between them, so it is easier to see how all the parts work together.  Hopefully this diagram will be clickable so the reader can get more detail on each of the components.&lt;br /&gt;
&lt;br /&gt;
Something like [https://wiki.mozilla.org/images/f/f3/Releng_flow_onepage_treeclose_reasons.pdf what RelEng has], but without all the internals.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Template can be found below&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== The List ==&lt;br /&gt;
&lt;br /&gt;
=== ActiveData ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Buildbot JSON logs&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
** OrangeFactor&lt;br /&gt;
** Perfherder &lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
** Structured Logs from Tests&lt;br /&gt;
** Talos&lt;br /&gt;
** Text logs (for buildbot and mozharness steps only)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Query endpoint: http://activedata.allizom.org/query&lt;br /&gt;
** Query Tool: http://activedata.allizom.org/tools/query.html&lt;br /&gt;
&lt;br /&gt;
=== AlertManager ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; -https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** mozilla.dev.tree-management alerts from graph server&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** webUI for organizing and taking action on these alerts.&lt;br /&gt;
&lt;br /&gt;
=== Autoland ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview/autoland.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - http://hg.mozilla.org/hgcustom/version-control-tools/file/tip/autoland&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:mcote], [:glob]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** MozReview UI &amp;amp; MozReview repo&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** Commits land on the repository of record (or try)&lt;br /&gt;
** Status reported to MozReview&lt;br /&gt;
&lt;br /&gt;
=== Autophone ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/AutoPhone&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/autophone/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://phonedash.mozilla.org/ (used by who?)&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla / BMO ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bmo.readthedocs.io&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla-bteam/bmo&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Mark Cote, David Lawrence, Dylan Hardison&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Web UI&lt;br /&gt;
** WebServices API (REST, XMLRPC, JSONRPC)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://bugzilla.mozilla.org (bug reporters, developers, etc)&lt;br /&gt;
** Pulse, Bugzfeed (via the [[https://wiki.mozilla.org/BMO/ChangeNotificationSystem]])&lt;br /&gt;
** BMO Push service (custom notifications for specific applications)&lt;br /&gt;
&lt;br /&gt;
=== BugzFeed ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[BMO/ChangeNotificationSystem]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/bugzfeed&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO via [[Auto-tools/Projects/Pulse|Pulse]]&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** WebSocket servers:&lt;br /&gt;
*** bugzfeed.mozilla.org&lt;br /&gt;
*** bugzfeed-dev.allizom.org&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla/ES Cluster ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/BMO/ElasticSearch&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/Bugzilla-ETL&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** Bugzilla (direct database access)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version&lt;br /&gt;
&lt;br /&gt;
=== Buildbot ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** builder slaves&lt;br /&gt;
** tester slaves&lt;br /&gt;
** https://wiki.mozilla.org/ReleaseEngineering/BuildAPI ??&lt;br /&gt;
** JSON Logs: http://builddata.pub.build.mozilla.org/builddata/buildjson/&lt;br /&gt;
&lt;br /&gt;
=== C++ Code Coverage ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bugzilla.mozilla.org/show_bug.cgi?id=890116&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* Used to be possible to trigger code coverage builds with &#039;try: -b o -p linux64-cc -u all -t none&#039;, but I think this is broken now. Probably isn&#039;t terribly hard to revive this. Needs further investigation.&lt;br /&gt;
&lt;br /&gt;
=== charts.mozilla.org ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/charts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** BMO/ES Cluster (https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://charts.mozilla.org (for management)&lt;br /&gt;
&lt;br /&gt;
=== CodeCoverage ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/CodeCoverage&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** &#039;&#039;&#039;UI&#039;&#039;&#039; - https://github.com/chinhodado/codecoverage_presenter&lt;br /&gt;
** &#039;&#039;&#039;ETL&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData-ETL/blob/dev/activedata_etl/transforms/jscov_to_es.py&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com, klahnakoski@mozilla.com, chmanchester@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Various tests have been configured with a code coverage option&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** ActiveData - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
** http://chinhodado.github.io/codecoverage_presenter/&lt;br /&gt;
&lt;br /&gt;
=== Datazilla (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - See Treeherder&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** data pushed from Talos (see Graph Server)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** charts at https://datazilla.mozilla.org&lt;br /&gt;
** raw results at https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob&lt;br /&gt;
&lt;br /&gt;
=== DevelopmentMetrics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/DevelopmentMetrics&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/MoDevMetrics&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Bugzilla/ES Cluster&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** various charts and dashboards&lt;br /&gt;
&lt;br /&gt;
=== DevTools Harness ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - Needs project page!&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ted.mielczarek]&lt;br /&gt;
&lt;br /&gt;
=== dzAlerts (retired)===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Alerts&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/datazilla-alerts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Datazilla web service (https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob)&lt;br /&gt;
** Eideticket web service (http://eideticker.mozilla.org)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** fxos-perf-alerts@mozilla.org (b2g sheriffs?)&lt;br /&gt;
&lt;br /&gt;
=== Eideticker (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Project_Eideticker#Documentation&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/eideticker&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - William Lachance, Dave Hunt&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Nightly/inbound b2g and android builds.&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Eideticker dashboard (http://eideticker.mozilla.org)&lt;br /&gt;
&lt;br /&gt;
=== Janitor ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mana.mozilla.org/wiki/display/ateam/Janitor&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jankeromnes/janitor, https://github.com/jankeromnes/dockerfiles&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Jan Keromnes [:janx]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** (none yet)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://janitor.technology&lt;br /&gt;
** BMO: new patches uploaded by users&lt;br /&gt;
** Treeherder: new pushes from users&lt;br /&gt;
** Docker Hub: image updates https://hub.docker.com/u/janx/&lt;br /&gt;
&lt;br /&gt;
=== m21s ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/m21s&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - see project page&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:whimboo]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Mozmill release tests&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** &#039;Firefox Greenlight Tests&#039; in Marionette, reporting to Treeherder&lt;br /&gt;
&lt;br /&gt;
=== Marionette ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Marionette&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:AutomatedTester][:ato]&lt;br /&gt;
* &#039;&#039;&#039;What&#039;&#039;&#039; - Mozilla&#039;s native WebDriver implementation&lt;br /&gt;
&lt;br /&gt;
=== Mozharness ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Mozharness&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/mozharness/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:armenzg]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** command-line invocation via buildbot or locally&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039; &lt;br /&gt;
** build/test logs consumed by buildbot, Treeherder, TBPL&lt;br /&gt;
&lt;br /&gt;
=== MozReview (Review Board) ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - various pieces of https://hg.mozilla.org/hgcustom/version-control-tools; see docs for more.&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote, glob, smacleod&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** reviewboard-hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** Various repositories via Autoland&lt;br /&gt;
&lt;br /&gt;
=== OrangeFactor ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/OrangeFactor]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :jgriffin, :mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** buildbot messages (using pulse)&lt;br /&gt;
** build logs&lt;br /&gt;
** comments from TBPL&lt;br /&gt;
** bugzilla bug data&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://brasstacks.mozilla.com/orangefactor/&lt;br /&gt;
** email status [War on Orange]&lt;br /&gt;
&lt;br /&gt;
=== Ouija ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Ouija&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/dminor/ouija.git&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - dminor, jmaher&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** https://hg.mozilla.org/&lt;br /&gt;
** tbpl.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://54.215.155.53&lt;br /&gt;
&lt;br /&gt;
=== Perfherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/treeherder/tree/master/treeherder/perf&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :wlach&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** PERFHERDER_DATA&lt;br /&gt;
*** schema  https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json&lt;br /&gt;
*** example http://wrla.ch/blog/2015/11/perfherder-onward/&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/perf.html#/graphs&lt;br /&gt;
&lt;br /&gt;
=== Pulse ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - development library: https://hg.mozilla.org/automation/mozillapulse&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems &lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems&lt;br /&gt;
** https://pulse.mozilla.org/&lt;br /&gt;
&lt;br /&gt;
=== PulseGuardian ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse/PulseGuardian&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulseguardian/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Persona (for auth) (soon to be Okta or TaskCluster auth)&lt;br /&gt;
** Pulse&lt;br /&gt;
** Web UI&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse&lt;br /&gt;
** Email notifications&lt;br /&gt;
&lt;br /&gt;
=== PulseTranslator ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator/blob/master/README.md&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jgriffin@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Pulse exchange/build&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
&lt;br /&gt;
=== Structured Logging ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mozbase.readthedocs.org/en/latest/loggingreporting.html, https://wiki.mozilla.org/Auto-tools/Projects/Structured_Logging&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:jgraham]&lt;br /&gt;
&lt;br /&gt;
=== Talos ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Buildbot/Talos&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/talos&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build for desktop or android&lt;br /&gt;
** commandline (done via mozharness now) to specify which test(s) to run&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** log file with raw data&lt;br /&gt;
** uploaded summarization of data to graph server&lt;br /&gt;
** uploaded raw data to datazilla&lt;br /&gt;
&lt;br /&gt;
Can be referred to as what is run by buildbot or by tbpl since this is the only performance test run on our per revision CI system.  Other tools are run at a different cadence.&lt;br /&gt;
&lt;br /&gt;
=== TBPL (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Sheriffing/TBPL]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/webtools/tbpl/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [[Sheriffing/TBPL#Developer_Contacts]]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
&lt;br /&gt;
=== Test Informant ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Test-Informant&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - See project page&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build notifications via pulse&lt;br /&gt;
** test manifests in tests.zip&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** reports at e.g., http://brasstacks.mozilla.com/testreports/weekly&lt;br /&gt;
&lt;br /&gt;
=== Treeherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder#Source_and_Docs]]&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:camd][:mdoglio][:edmorley]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Pushlog from hg.mozilla.org via json-pushes&lt;br /&gt;
** Build/tests from Buildbot via buildapi&lt;br /&gt;
** Direct pushes via ``treeherder-client``&lt;br /&gt;
** Build/tests from Taskcluster (under development)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/&lt;br /&gt;
** https://treeherder.mozilla.org/api/&lt;br /&gt;
&lt;br /&gt;
=== web-platform-tests ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wptrunner.readthedocs.org/en/latest/, Needs project page?&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** https://github.com/w3c/web-platform-tests/&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/README.md&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/tests/README.md &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:jgraham]&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Use the EMPTY TEMPLATE to add more entries.  Include ones you know about, even if you can not fill them.&lt;br /&gt;
&lt;br /&gt;
=== EXAMPLE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - some wiki, or read the docs to learn more &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - link to code, if it makes sense&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - for ekyle to contact if he has questions&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; -&lt;br /&gt;
** automated resources&lt;br /&gt;
** services consumed&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** automated services provided&lt;br /&gt;
** dashboards (and teams that consume them)&lt;br /&gt;
&lt;br /&gt;
=== EMPTY TEMPLATE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148279</id>
		<title>EngineeringProductivity/Projects/Everything</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148279"/>
		<updated>2016-09-19T17:44:57Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Janitor */ Refactor Outputs/Services&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Project Table ==&lt;br /&gt;
&lt;br /&gt;
The project table has been moved to https://wiki.mozilla.org/EngineeringProductivity/Projects&lt;br /&gt;
&lt;br /&gt;
== Motivation == &lt;br /&gt;
&lt;br /&gt;
This page is to help diagram all the various things the A*Team has built and continue to support.  &lt;br /&gt;
&lt;br /&gt;
The plan is to draw high level components/systems, and links between them, so it is easier to see how all the parts work together.  Hopefully this diagram will be clickable so the reader can get more detail on each of the components.&lt;br /&gt;
&lt;br /&gt;
Something like [https://wiki.mozilla.org/images/f/f3/Releng_flow_onepage_treeclose_reasons.pdf what RelEng has], but without all the internals.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Template can be found below&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== The List ==&lt;br /&gt;
&lt;br /&gt;
=== ActiveData ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Buildbot JSON logs&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
** OrangeFactor&lt;br /&gt;
** Perfherder &lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
** Structured Logs from Tests&lt;br /&gt;
** Talos&lt;br /&gt;
** Text logs (for buildbot and mozharness steps only)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Query endpoint: http://activedata.allizom.org/query&lt;br /&gt;
** Query Tool: http://activedata.allizom.org/tools/query.html&lt;br /&gt;
&lt;br /&gt;
=== AlertManager ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; -https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** mozilla.dev.tree-management alerts from graph server&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** webUI for organizing and taking action on these alerts.&lt;br /&gt;
&lt;br /&gt;
=== Autoland ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview/autoland.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - http://hg.mozilla.org/hgcustom/version-control-tools/file/tip/autoland&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:mcote], [:glob]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** MozReview UI &amp;amp; MozReview repo&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** Commits land on the repository of record (or try)&lt;br /&gt;
** Status reported to MozReview&lt;br /&gt;
&lt;br /&gt;
=== Autophone ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/AutoPhone&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/autophone/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://phonedash.mozilla.org/ (used by who?)&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla / BMO ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bmo.readthedocs.io&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla-bteam/bmo&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Mark Cote, David Lawrence, Dylan Hardison&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Web UI&lt;br /&gt;
** WebServices API (REST, XMLRPC, JSONRPC)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://bugzilla.mozilla.org (bug reporters, developers, etc)&lt;br /&gt;
** Pulse, Bugzfeed (via the [[https://wiki.mozilla.org/BMO/ChangeNotificationSystem]])&lt;br /&gt;
** BMO Push service (custom notifications for specific applications)&lt;br /&gt;
&lt;br /&gt;
=== BugzFeed ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[BMO/ChangeNotificationSystem]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/bugzfeed&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO via [[Auto-tools/Projects/Pulse|Pulse]]&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** WebSocket servers:&lt;br /&gt;
*** bugzfeed.mozilla.org&lt;br /&gt;
*** bugzfeed-dev.allizom.org&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla/ES Cluster ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/BMO/ElasticSearch&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/Bugzilla-ETL&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** Bugzilla (direct database access)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version&lt;br /&gt;
&lt;br /&gt;
=== Buildbot ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** builder slaves&lt;br /&gt;
** tester slaves&lt;br /&gt;
** https://wiki.mozilla.org/ReleaseEngineering/BuildAPI ??&lt;br /&gt;
** JSON Logs: http://builddata.pub.build.mozilla.org/builddata/buildjson/&lt;br /&gt;
&lt;br /&gt;
=== C++ Code Coverage ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bugzilla.mozilla.org/show_bug.cgi?id=890116&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* Used to be possible to trigger code coverage builds with &#039;try: -b o -p linux64-cc -u all -t none&#039;, but I think this is broken now. Probably isn&#039;t terribly hard to revive this. Needs further investigation.&lt;br /&gt;
&lt;br /&gt;
=== charts.mozilla.org ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/charts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** BMO/ES Cluster (https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://charts.mozilla.org (for management)&lt;br /&gt;
&lt;br /&gt;
=== CodeCoverage ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/CodeCoverage&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** &#039;&#039;&#039;UI&#039;&#039;&#039; - https://github.com/chinhodado/codecoverage_presenter&lt;br /&gt;
** &#039;&#039;&#039;ETL&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData-ETL/blob/dev/activedata_etl/transforms/jscov_to_es.py&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com, klahnakoski@mozilla.com, chmanchester@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Various tests have been configured with a code coverage option&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** ActiveData - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
** http://chinhodado.github.io/codecoverage_presenter/&lt;br /&gt;
&lt;br /&gt;
=== Datazilla (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - See Treeherder&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** data pushed from Talos (see Graph Server)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** charts at https://datazilla.mozilla.org&lt;br /&gt;
** raw results at https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob&lt;br /&gt;
&lt;br /&gt;
=== DevelopmentMetrics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/DevelopmentMetrics&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/MoDevMetrics&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Bugzilla/ES Cluster&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** various charts and dashboards&lt;br /&gt;
&lt;br /&gt;
=== DevTools Harness ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - Needs project page!&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ted.mielczarek]&lt;br /&gt;
&lt;br /&gt;
=== dzAlerts (retired)===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Alerts&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/datazilla-alerts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Datazilla web service (https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob)&lt;br /&gt;
** Eideticket web service (http://eideticker.mozilla.org)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** fxos-perf-alerts@mozilla.org (b2g sheriffs?)&lt;br /&gt;
&lt;br /&gt;
=== Eideticker ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Project_Eideticker#Documentation&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/eideticker&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - William Lachance, Dave Hunt&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Nightly/inbound b2g and android builds.&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Eideticker dashboard (http://eideticker.mozilla.org)&lt;br /&gt;
&lt;br /&gt;
=== Janitor ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mana.mozilla.org/wiki/display/ateam/Janitor&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jankeromnes/janitor, https://github.com/jankeromnes/dockerfiles&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Jan Keromnes [:janx]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** (none yet)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://janitor.technology&lt;br /&gt;
** Try: new pushes from users&lt;br /&gt;
** BMO: new patches uploaded by users&lt;br /&gt;
** Docker Hub: project-image updates https://hub.docker.com/u/janx/&lt;br /&gt;
&lt;br /&gt;
=== m21s ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/m21s&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - see project page&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:whimboo]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Mozmill release tests&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** &#039;Firefox Greenlight Tests&#039; in Marionette, reporting to Treeherder&lt;br /&gt;
&lt;br /&gt;
=== Marionette ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Marionette&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:AutomatedTester][:ato]&lt;br /&gt;
* &#039;&#039;&#039;What&#039;&#039;&#039; - Mozilla&#039;s native WebDriver implementation&lt;br /&gt;
&lt;br /&gt;
=== Mozharness ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Mozharness&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/mozharness/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:armenzg]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** command-line invocation via buildbot or locally&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039; &lt;br /&gt;
** build/test logs consumed by buildbot, Treeherder, TBPL&lt;br /&gt;
&lt;br /&gt;
=== MozReview (Review Board) ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - various pieces of https://hg.mozilla.org/hgcustom/version-control-tools; see docs for more.&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote, glob, smacleod&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** reviewboard-hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** Various repositories via Autoland&lt;br /&gt;
&lt;br /&gt;
=== OrangeFactor ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/OrangeFactor]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :jgriffin, :mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** buildbot messages (using pulse)&lt;br /&gt;
** build logs&lt;br /&gt;
** comments from TBPL&lt;br /&gt;
** bugzilla bug data&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://brasstacks.mozilla.com/orangefactor/&lt;br /&gt;
** email status [War on Orange]&lt;br /&gt;
&lt;br /&gt;
=== Ouija ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Ouija&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/dminor/ouija.git&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - dminor, jmaher&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** https://hg.mozilla.org/&lt;br /&gt;
** tbpl.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://54.215.155.53&lt;br /&gt;
&lt;br /&gt;
=== Perfherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/treeherder/tree/master/treeherder/perf&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :wlach&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** PERFHERDER_DATA&lt;br /&gt;
*** schema  https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json&lt;br /&gt;
*** example http://wrla.ch/blog/2015/11/perfherder-onward/&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/perf.html#/graphs&lt;br /&gt;
&lt;br /&gt;
=== Pulse ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - development library: https://hg.mozilla.org/automation/mozillapulse&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems &lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems&lt;br /&gt;
** https://pulse.mozilla.org/&lt;br /&gt;
&lt;br /&gt;
=== PulseGuardian ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse/PulseGuardian&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulseguardian/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Persona (for auth) (soon to be Okta or TaskCluster auth)&lt;br /&gt;
** Pulse&lt;br /&gt;
** Web UI&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse&lt;br /&gt;
** Email notifications&lt;br /&gt;
&lt;br /&gt;
=== PulseTranslator ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator/blob/master/README.md&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jgriffin@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Pulse exchange/build&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
&lt;br /&gt;
=== Structured Logging ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mozbase.readthedocs.org/en/latest/loggingreporting.html, https://wiki.mozilla.org/Auto-tools/Projects/Structured_Logging&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:jgraham]&lt;br /&gt;
&lt;br /&gt;
=== Talos ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Buildbot/Talos&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/talos&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build for desktop or android&lt;br /&gt;
** commandline (done via mozharness now) to specify which test(s) to run&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** log file with raw data&lt;br /&gt;
** uploaded summarization of data to graph server&lt;br /&gt;
** uploaded raw data to datazilla&lt;br /&gt;
&lt;br /&gt;
Can be referred to as what is run by buildbot or by tbpl since this is the only performance test run on our per revision CI system.  Other tools are run at a different cadence.&lt;br /&gt;
&lt;br /&gt;
=== TBPL (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Sheriffing/TBPL]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/webtools/tbpl/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [[Sheriffing/TBPL#Developer_Contacts]]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
&lt;br /&gt;
=== Test Informant ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Test-Informant&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - See project page&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build notifications via pulse&lt;br /&gt;
** test manifests in tests.zip&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** reports at e.g., http://brasstacks.mozilla.com/testreports/weekly&lt;br /&gt;
&lt;br /&gt;
=== Treeherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder#Source_and_Docs]]&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:camd][:mdoglio][:edmorley]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Pushlog from hg.mozilla.org via json-pushes&lt;br /&gt;
** Build/tests from Buildbot via buildapi&lt;br /&gt;
** Direct pushes via ``treeherder-client``&lt;br /&gt;
** Build/tests from Taskcluster (under development)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/&lt;br /&gt;
** https://treeherder.mozilla.org/api/&lt;br /&gt;
&lt;br /&gt;
=== web-platform-tests ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wptrunner.readthedocs.org/en/latest/, Needs project page?&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** https://github.com/w3c/web-platform-tests/&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/README.md&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/tests/README.md &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:jgraham]&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Use the EMPTY TEMPLATE to add more entries.  Include ones you know about, even if you can not fill them.&lt;br /&gt;
&lt;br /&gt;
=== EXAMPLE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - some wiki, or read the docs to learn more &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - link to code, if it makes sense&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - for ekyle to contact if he has questions&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; -&lt;br /&gt;
** automated resources&lt;br /&gt;
** services consumed&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** automated services provided&lt;br /&gt;
** dashboards (and teams that consume them)&lt;br /&gt;
&lt;br /&gt;
=== EMPTY TEMPLATE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148278</id>
		<title>EngineeringProductivity/Projects/Everything</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148278"/>
		<updated>2016-09-19T17:42:39Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Janitor */ +New&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Project Table ==&lt;br /&gt;
&lt;br /&gt;
The project table has been moved to https://wiki.mozilla.org/EngineeringProductivity/Projects&lt;br /&gt;
&lt;br /&gt;
== Motivation == &lt;br /&gt;
&lt;br /&gt;
This page is to help diagram all the various things the A*Team has built and continue to support.  &lt;br /&gt;
&lt;br /&gt;
The plan is to draw high level components/systems, and links between them, so it is easier to see how all the parts work together.  Hopefully this diagram will be clickable so the reader can get more detail on each of the components.&lt;br /&gt;
&lt;br /&gt;
Something like [https://wiki.mozilla.org/images/f/f3/Releng_flow_onepage_treeclose_reasons.pdf what RelEng has], but without all the internals.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Template can be found below&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== The List ==&lt;br /&gt;
&lt;br /&gt;
=== ActiveData ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Buildbot JSON logs&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
** OrangeFactor&lt;br /&gt;
** Perfherder &lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
** Structured Logs from Tests&lt;br /&gt;
** Talos&lt;br /&gt;
** Text logs (for buildbot and mozharness steps only)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Query endpoint: http://activedata.allizom.org/query&lt;br /&gt;
** Query Tool: http://activedata.allizom.org/tools/query.html&lt;br /&gt;
&lt;br /&gt;
=== AlertManager ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; -https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** mozilla.dev.tree-management alerts from graph server&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** webUI for organizing and taking action on these alerts.&lt;br /&gt;
&lt;br /&gt;
=== Autoland ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview/autoland.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - http://hg.mozilla.org/hgcustom/version-control-tools/file/tip/autoland&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:mcote], [:glob]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** MozReview UI &amp;amp; MozReview repo&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** Commits land on the repository of record (or try)&lt;br /&gt;
** Status reported to MozReview&lt;br /&gt;
&lt;br /&gt;
=== Autophone ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/AutoPhone&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/autophone/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://phonedash.mozilla.org/ (used by who?)&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla / BMO ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bmo.readthedocs.io&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla-bteam/bmo&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Mark Cote, David Lawrence, Dylan Hardison&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Web UI&lt;br /&gt;
** WebServices API (REST, XMLRPC, JSONRPC)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://bugzilla.mozilla.org (bug reporters, developers, etc)&lt;br /&gt;
** Pulse, Bugzfeed (via the [[https://wiki.mozilla.org/BMO/ChangeNotificationSystem]])&lt;br /&gt;
** BMO Push service (custom notifications for specific applications)&lt;br /&gt;
&lt;br /&gt;
=== BugzFeed ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[BMO/ChangeNotificationSystem]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/bugzfeed&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO via [[Auto-tools/Projects/Pulse|Pulse]]&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** WebSocket servers:&lt;br /&gt;
*** bugzfeed.mozilla.org&lt;br /&gt;
*** bugzfeed-dev.allizom.org&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla/ES Cluster ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/BMO/ElasticSearch&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/Bugzilla-ETL&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** Bugzilla (direct database access)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version&lt;br /&gt;
&lt;br /&gt;
=== Buildbot ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** builder slaves&lt;br /&gt;
** tester slaves&lt;br /&gt;
** https://wiki.mozilla.org/ReleaseEngineering/BuildAPI ??&lt;br /&gt;
** JSON Logs: http://builddata.pub.build.mozilla.org/builddata/buildjson/&lt;br /&gt;
&lt;br /&gt;
=== C++ Code Coverage ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bugzilla.mozilla.org/show_bug.cgi?id=890116&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* Used to be possible to trigger code coverage builds with &#039;try: -b o -p linux64-cc -u all -t none&#039;, but I think this is broken now. Probably isn&#039;t terribly hard to revive this. Needs further investigation.&lt;br /&gt;
&lt;br /&gt;
=== charts.mozilla.org ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/charts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** BMO/ES Cluster (https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://charts.mozilla.org (for management)&lt;br /&gt;
&lt;br /&gt;
=== CodeCoverage ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/CodeCoverage&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** &#039;&#039;&#039;UI&#039;&#039;&#039; - https://github.com/chinhodado/codecoverage_presenter&lt;br /&gt;
** &#039;&#039;&#039;ETL&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData-ETL/blob/dev/activedata_etl/transforms/jscov_to_es.py&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com, klahnakoski@mozilla.com, chmanchester@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Various tests have been configured with a code coverage option&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** ActiveData - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
** http://chinhodado.github.io/codecoverage_presenter/&lt;br /&gt;
&lt;br /&gt;
=== Datazilla (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - See Treeherder&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** data pushed from Talos (see Graph Server)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** charts at https://datazilla.mozilla.org&lt;br /&gt;
** raw results at https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob&lt;br /&gt;
&lt;br /&gt;
=== DevelopmentMetrics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/DevelopmentMetrics&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/MoDevMetrics&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Bugzilla/ES Cluster&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** various charts and dashboards&lt;br /&gt;
&lt;br /&gt;
=== DevTools Harness ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - Needs project page!&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ted.mielczarek]&lt;br /&gt;
&lt;br /&gt;
=== dzAlerts (retired)===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Alerts&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/datazilla-alerts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Datazilla web service (https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob)&lt;br /&gt;
** Eideticket web service (http://eideticker.mozilla.org)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** fxos-perf-alerts@mozilla.org (b2g sheriffs?)&lt;br /&gt;
&lt;br /&gt;
=== Eideticker ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Project_Eideticker#Documentation&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/eideticker&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - William Lachance, Dave Hunt&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Nightly/inbound b2g and android builds.&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Eideticker dashboard (http://eideticker.mozilla.org)&lt;br /&gt;
&lt;br /&gt;
=== Janitor ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mana.mozilla.org/wiki/display/ateam/Janitor&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jankeromnes/janitor, https://github.com/jankeromnes/dockerfiles&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Jan Keromnes [:janx]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** (none yet)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://janitor.technology&lt;br /&gt;
** New try pushes&lt;br /&gt;
** New patches uploaded to BMO&lt;br /&gt;
** Developer images on https://hub.docker.com/u/janx/&lt;br /&gt;
&lt;br /&gt;
=== m21s ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/m21s&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - see project page&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:whimboo]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Mozmill release tests&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** &#039;Firefox Greenlight Tests&#039; in Marionette, reporting to Treeherder&lt;br /&gt;
&lt;br /&gt;
=== Marionette ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Marionette&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:AutomatedTester][:ato]&lt;br /&gt;
* &#039;&#039;&#039;What&#039;&#039;&#039; - Mozilla&#039;s native WebDriver implementation&lt;br /&gt;
&lt;br /&gt;
=== Mozharness ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Mozharness&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/mozharness/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:armenzg]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** command-line invocation via buildbot or locally&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039; &lt;br /&gt;
** build/test logs consumed by buildbot, Treeherder, TBPL&lt;br /&gt;
&lt;br /&gt;
=== MozReview (Review Board) ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - various pieces of https://hg.mozilla.org/hgcustom/version-control-tools; see docs for more.&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote, glob, smacleod&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** reviewboard-hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** Various repositories via Autoland&lt;br /&gt;
&lt;br /&gt;
=== OrangeFactor ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/OrangeFactor]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :jgriffin, :mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** buildbot messages (using pulse)&lt;br /&gt;
** build logs&lt;br /&gt;
** comments from TBPL&lt;br /&gt;
** bugzilla bug data&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://brasstacks.mozilla.com/orangefactor/&lt;br /&gt;
** email status [War on Orange]&lt;br /&gt;
&lt;br /&gt;
=== Ouija ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Ouija&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/dminor/ouija.git&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - dminor, jmaher&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** https://hg.mozilla.org/&lt;br /&gt;
** tbpl.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://54.215.155.53&lt;br /&gt;
&lt;br /&gt;
=== Perfherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/treeherder/tree/master/treeherder/perf&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :wlach&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** PERFHERDER_DATA&lt;br /&gt;
*** schema  https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json&lt;br /&gt;
*** example http://wrla.ch/blog/2015/11/perfherder-onward/&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/perf.html#/graphs&lt;br /&gt;
&lt;br /&gt;
=== Pulse ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - development library: https://hg.mozilla.org/automation/mozillapulse&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems &lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems&lt;br /&gt;
** https://pulse.mozilla.org/&lt;br /&gt;
&lt;br /&gt;
=== PulseGuardian ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse/PulseGuardian&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulseguardian/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Persona (for auth) (soon to be Okta or TaskCluster auth)&lt;br /&gt;
** Pulse&lt;br /&gt;
** Web UI&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse&lt;br /&gt;
** Email notifications&lt;br /&gt;
&lt;br /&gt;
=== PulseTranslator ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator/blob/master/README.md&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jgriffin@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Pulse exchange/build&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
&lt;br /&gt;
=== Structured Logging ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mozbase.readthedocs.org/en/latest/loggingreporting.html, https://wiki.mozilla.org/Auto-tools/Projects/Structured_Logging&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:jgraham]&lt;br /&gt;
&lt;br /&gt;
=== Talos ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Buildbot/Talos&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/talos&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build for desktop or android&lt;br /&gt;
** commandline (done via mozharness now) to specify which test(s) to run&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** log file with raw data&lt;br /&gt;
** uploaded summarization of data to graph server&lt;br /&gt;
** uploaded raw data to datazilla&lt;br /&gt;
&lt;br /&gt;
Can be referred to as what is run by buildbot or by tbpl since this is the only performance test run on our per revision CI system.  Other tools are run at a different cadence.&lt;br /&gt;
&lt;br /&gt;
=== TBPL (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Sheriffing/TBPL]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/webtools/tbpl/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [[Sheriffing/TBPL#Developer_Contacts]]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
&lt;br /&gt;
=== Test Informant ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Test-Informant&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - See project page&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build notifications via pulse&lt;br /&gt;
** test manifests in tests.zip&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** reports at e.g., http://brasstacks.mozilla.com/testreports/weekly&lt;br /&gt;
&lt;br /&gt;
=== Treeherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder#Source_and_Docs]]&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:camd][:mdoglio][:edmorley]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Pushlog from hg.mozilla.org via json-pushes&lt;br /&gt;
** Build/tests from Buildbot via buildapi&lt;br /&gt;
** Direct pushes via ``treeherder-client``&lt;br /&gt;
** Build/tests from Taskcluster (under development)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/&lt;br /&gt;
** https://treeherder.mozilla.org/api/&lt;br /&gt;
&lt;br /&gt;
=== web-platform-tests ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wptrunner.readthedocs.org/en/latest/, Needs project page?&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** https://github.com/w3c/web-platform-tests/&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/README.md&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/tests/README.md &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:jgraham]&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Use the EMPTY TEMPLATE to add more entries.  Include ones you know about, even if you can not fill them.&lt;br /&gt;
&lt;br /&gt;
=== EXAMPLE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - some wiki, or read the docs to learn more &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - link to code, if it makes sense&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - for ekyle to contact if he has questions&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; -&lt;br /&gt;
** automated resources&lt;br /&gt;
** services consumed&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** automated services provided&lt;br /&gt;
** dashboards (and teams that consume them)&lt;br /&gt;
&lt;br /&gt;
=== EMPTY TEMPLATE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148277</id>
		<title>EngineeringProductivity/Projects/Everything</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=EngineeringProductivity/Projects/Everything&amp;diff=1148277"/>
		<updated>2016-09-19T17:41:16Z</updated>

		<summary type="html">&lt;p&gt;Janx: Added Janitor to Everything&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Project Table ==&lt;br /&gt;
&lt;br /&gt;
The project table has been moved to https://wiki.mozilla.org/EngineeringProductivity/Projects&lt;br /&gt;
&lt;br /&gt;
== Motivation == &lt;br /&gt;
&lt;br /&gt;
This page is to help diagram all the various things the A*Team has built and continue to support.  &lt;br /&gt;
&lt;br /&gt;
The plan is to draw high level components/systems, and links between them, so it is easier to see how all the parts work together.  Hopefully this diagram will be clickable so the reader can get more detail on each of the components.&lt;br /&gt;
&lt;br /&gt;
Something like [https://wiki.mozilla.org/images/f/f3/Releng_flow_onepage_treeclose_reasons.pdf what RelEng has], but without all the internals.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Template can be found below&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== The List ==&lt;br /&gt;
&lt;br /&gt;
=== ActiveData ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Buildbot JSON logs&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
** OrangeFactor&lt;br /&gt;
** Perfherder &lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
** Structured Logs from Tests&lt;br /&gt;
** Talos&lt;br /&gt;
** Text logs (for buildbot and mozharness steps only)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Query endpoint: http://activedata.allizom.org/query&lt;br /&gt;
** Query Tool: http://activedata.allizom.org/tools/query.html&lt;br /&gt;
&lt;br /&gt;
=== AlertManager ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; -https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jmaher/alert_manager/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** mozilla.dev.tree-management alerts from graph server&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** webUI for organizing and taking action on these alerts.&lt;br /&gt;
&lt;br /&gt;
=== Autoland ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview/autoland.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - http://hg.mozilla.org/hgcustom/version-control-tools/file/tip/autoland&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:mcote], [:glob]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** MozReview UI &amp;amp; MozReview repo&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** Commits land on the repository of record (or try)&lt;br /&gt;
** Status reported to MozReview&lt;br /&gt;
&lt;br /&gt;
=== Autophone ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/AutoPhone&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/autophone/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://phonedash.mozilla.org/ (used by who?)&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla / BMO ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bmo.readthedocs.io&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla-bteam/bmo&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Mark Cote, David Lawrence, Dylan Hardison&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Web UI&lt;br /&gt;
** WebServices API (REST, XMLRPC, JSONRPC)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://bugzilla.mozilla.org (bug reporters, developers, etc)&lt;br /&gt;
** Pulse, Bugzfeed (via the [[https://wiki.mozilla.org/BMO/ChangeNotificationSystem]])&lt;br /&gt;
** BMO Push service (custom notifications for specific applications)&lt;br /&gt;
&lt;br /&gt;
=== BugzFeed ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[BMO/ChangeNotificationSystem]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/bugzfeed&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO via [[Auto-tools/Projects/Pulse|Pulse]]&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** WebSocket servers:&lt;br /&gt;
*** bugzfeed.mozilla.org&lt;br /&gt;
*** bugzfeed-dev.allizom.org&lt;br /&gt;
&lt;br /&gt;
=== Bugzilla/ES Cluster ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/BMO/ElasticSearch&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/Bugzilla-ETL&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** Bugzilla (direct database access)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version&lt;br /&gt;
&lt;br /&gt;
=== Buildbot ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** builder slaves&lt;br /&gt;
** tester slaves&lt;br /&gt;
** https://wiki.mozilla.org/ReleaseEngineering/BuildAPI ??&lt;br /&gt;
** JSON Logs: http://builddata.pub.build.mozilla.org/builddata/buildjson/&lt;br /&gt;
&lt;br /&gt;
=== C++ Code Coverage ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://bugzilla.mozilla.org/show_bug.cgi?id=890116&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* Used to be possible to trigger code coverage builds with &#039;try: -b o -p linux64-cc -u all -t none&#039;, but I think this is broken now. Probably isn&#039;t terribly hard to revive this. Needs further investigation.&lt;br /&gt;
&lt;br /&gt;
=== charts.mozilla.org ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/charts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; - &lt;br /&gt;
** BMO/ES Cluster (https://esfrontline.bugzilla.mozilla.org:443/public_bugs/bug_version)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://charts.mozilla.org (for management)&lt;br /&gt;
&lt;br /&gt;
=== CodeCoverage ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/CodeCoverage&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** &#039;&#039;&#039;UI&#039;&#039;&#039; - https://github.com/chinhodado/codecoverage_presenter&lt;br /&gt;
** &#039;&#039;&#039;ETL&#039;&#039;&#039; - https://github.com/klahnakoski/ActiveData-ETL/blob/dev/activedata_etl/transforms/jscov_to_es.py&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com, klahnakoski@mozilla.com, chmanchester@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Various tests have been configured with a code coverage option&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** ActiveData - https://wiki.mozilla.org/Auto-tools/Projects/ActiveData&lt;br /&gt;
** http://chinhodado.github.io/codecoverage_presenter/&lt;br /&gt;
&lt;br /&gt;
=== Datazilla (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://datazilla.readthedocs.org/en/latest/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - See Treeherder&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** data pushed from Talos (see Graph Server)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** charts at https://datazilla.mozilla.org&lt;br /&gt;
** raw results at https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob&lt;br /&gt;
&lt;br /&gt;
=== DevelopmentMetrics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/DevelopmentMetrics&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/MoDevMetrics&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Bugzilla/ES Cluster&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** various charts and dashboards&lt;br /&gt;
&lt;br /&gt;
=== DevTools Harness ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - Needs project page!&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ted.mielczarek]&lt;br /&gt;
&lt;br /&gt;
=== dzAlerts (retired)===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Alerts&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/klahnakoski/datazilla-alerts&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - klahnakoski@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Datazilla web service (https://datazilla.mozilla.org/talos/refdata/objectstore/json_blob)&lt;br /&gt;
** Eideticket web service (http://eideticker.mozilla.org)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** fxos-perf-alerts@mozilla.org (b2g sheriffs?)&lt;br /&gt;
&lt;br /&gt;
=== Eideticker ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Project_Eideticker#Documentation&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/eideticker&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - William Lachance, Dave Hunt&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Nightly/inbound b2g and android builds.&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Eideticker dashboard (http://eideticker.mozilla.org)&lt;br /&gt;
&lt;br /&gt;
=== Janitor ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mana.mozilla.org/wiki/display/ateam/Janitor&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/jankeromnes/janitor, https://github.com/jankeromnes/dockerfiles&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - Jan Keromnes [:janx]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** (none yet)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://janitor.technology&lt;br /&gt;
** Try pushes&lt;br /&gt;
** New patches uploaded to BMO&lt;br /&gt;
** Docker images on https://hub.docker.com/u/janx/&lt;br /&gt;
&lt;br /&gt;
=== m21s ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/m21s&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - see project page&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:whimboo]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Mozmill release tests&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** &#039;Firefox Greenlight Tests&#039; in Marionette, reporting to Treeherder&lt;br /&gt;
&lt;br /&gt;
=== Marionette ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Marionette&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:AutomatedTester][:ato]&lt;br /&gt;
* &#039;&#039;&#039;What&#039;&#039;&#039; - Mozilla&#039;s native WebDriver implementation&lt;br /&gt;
&lt;br /&gt;
=== Mozharness ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Mozharness&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/mozharness/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:armenzg]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** command-line invocation via buildbot or locally&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039; &lt;br /&gt;
** build/test logs consumed by buildbot, Treeherder, TBPL&lt;br /&gt;
&lt;br /&gt;
=== MozReview (Review Board) ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - http://mozilla-version-control-tools.readthedocs.io/en/latest/mozreview.html&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - various pieces of https://hg.mozilla.org/hgcustom/version-control-tools; see docs for more.&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote, glob, smacleod&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** reviewboard-hg.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** BMO&lt;br /&gt;
** Various repositories via Autoland&lt;br /&gt;
&lt;br /&gt;
=== OrangeFactor ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/OrangeFactor]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/automation/orangefactor/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :jgriffin, :mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** buildbot messages (using pulse)&lt;br /&gt;
** build logs&lt;br /&gt;
** comments from TBPL&lt;br /&gt;
** bugzilla bug data&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://brasstacks.mozilla.com/orangefactor/&lt;br /&gt;
** email status [War on Orange]&lt;br /&gt;
&lt;br /&gt;
=== Ouija ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Ouija&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/dminor/ouija.git&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - dminor, jmaher&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** https://hg.mozilla.org/&lt;br /&gt;
** tbpl.mozilla.org&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** http://54.215.155.53&lt;br /&gt;
&lt;br /&gt;
=== Perfherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/treeherder/tree/master/treeherder/perf&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - :wlach&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** PERFHERDER_DATA&lt;br /&gt;
*** schema  https://github.com/mozilla/treeherder/blob/master/schemas/performance-artifact.json&lt;br /&gt;
*** example http://wrla.ch/blog/2015/11/perfherder-onward/&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/perf.html#/graphs&lt;br /&gt;
&lt;br /&gt;
=== Pulse ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - development library: https://hg.mozilla.org/automation/mozillapulse&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems &lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** a multitude of other systems&lt;br /&gt;
** https://pulse.mozilla.org/&lt;br /&gt;
&lt;br /&gt;
=== PulseGuardian ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Pulse/PulseGuardian&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulseguardian/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - mcote&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Persona (for auth) (soon to be Okta or TaskCluster auth)&lt;br /&gt;
** Pulse&lt;br /&gt;
** Web UI&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse&lt;br /&gt;
** Email notifications&lt;br /&gt;
&lt;br /&gt;
=== PulseTranslator ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator/blob/master/README.md&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://github.com/mozilla/pulsetranslator&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jgriffin@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; &lt;br /&gt;
** Pulse exchange/build&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** Pulse exchange/build/normalized&lt;br /&gt;
&lt;br /&gt;
=== Structured Logging ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://mozbase.readthedocs.org/en/latest/loggingreporting.html, https://wiki.mozilla.org/Auto-tools/Projects/Structured_Logging&lt;br /&gt;
* &#039;&#039;&#039;Contacts&#039;&#039;&#039; - [:chmanchester][:ahal][:jgraham]&lt;br /&gt;
&lt;br /&gt;
=== Talos ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Buildbot/Talos&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/build/talos&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - jmaher@mozilla.com&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build for desktop or android&lt;br /&gt;
** commandline (done via mozharness now) to specify which test(s) to run&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** log file with raw data&lt;br /&gt;
** uploaded summarization of data to graph server&lt;br /&gt;
** uploaded raw data to datazilla&lt;br /&gt;
&lt;br /&gt;
Can be referred to as what is run by buildbot or by tbpl since this is the only performance test run on our per revision CI system.  Other tools are run at a different cadence.&lt;br /&gt;
&lt;br /&gt;
=== TBPL (retired) ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Sheriffing/TBPL]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - https://hg.mozilla.org/webtools/tbpl/&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [[Sheriffing/TBPL#Developer_Contacts]]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
&lt;br /&gt;
=== Test Informant ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wiki.mozilla.org/Auto-tools/Projects/Test-Informant&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - See project page&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:ahal]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** build notifications via pulse&lt;br /&gt;
** test manifests in tests.zip&lt;br /&gt;
* &#039;&#039;&#039;Outputs&#039;&#039;&#039;&lt;br /&gt;
** reports at e.g., http://brasstacks.mozilla.com/testreports/weekly&lt;br /&gt;
&lt;br /&gt;
=== Treeherder ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder]]&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - [[Auto-tools/Projects/Treeherder#Source_and_Docs]]&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:camd][:mdoglio][:edmorley]&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
** Pushlog from hg.mozilla.org via json-pushes&lt;br /&gt;
** Build/tests from Buildbot via buildapi&lt;br /&gt;
** Direct pushes via ``treeherder-client``&lt;br /&gt;
** Build/tests from Taskcluster (under development)&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** https://treeherder.mozilla.org/&lt;br /&gt;
** https://treeherder.mozilla.org/api/&lt;br /&gt;
&lt;br /&gt;
=== web-platform-tests ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - https://wptrunner.readthedocs.org/en/latest/, Needs project page?&lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039;&lt;br /&gt;
** https://github.com/w3c/web-platform-tests/&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/README.md&lt;br /&gt;
** https://github.com/mozilla/gecko-dev/blob/master/testing/web-platform/tests/README.md &lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - [:jgraham]&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Use the EMPTY TEMPLATE to add more entries.  Include ones you know about, even if you can not fill them.&lt;br /&gt;
&lt;br /&gt;
=== EXAMPLE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - some wiki, or read the docs to learn more &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; - link to code, if it makes sense&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - for ekyle to contact if he has questions&lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039; -&lt;br /&gt;
** automated resources&lt;br /&gt;
** services consumed&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
** automated services provided&lt;br /&gt;
** dashboards (and teams that consume them)&lt;br /&gt;
&lt;br /&gt;
=== EMPTY TEMPLATE ===&lt;br /&gt;
* &#039;&#039;&#039;Docs&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Code&#039;&#039;&#039; -&lt;br /&gt;
* &#039;&#039;&#039;Contact&#039;&#039;&#039; - &lt;br /&gt;
* &#039;&#039;&#039;Inputs&#039;&#039;&#039;&lt;br /&gt;
**&lt;br /&gt;
* &#039;&#039;&#039;Outputs/Services&#039;&#039;&#039;&lt;br /&gt;
**&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=User:Janx&amp;diff=1148271</id>
		<title>User:Janx</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=User:Janx&amp;diff=1148271"/>
		<updated>2016-09-19T17:35:09Z</updated>

		<summary type="html">&lt;p&gt;Janx: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hello, I&#039;m Jan Keromnes [:janx]. It&#039;s nice to meet you.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Modules/Other&amp;diff=1097877</id>
		<title>Modules/Other</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Modules/Other&amp;diff=1097877"/>
		<updated>2015-09-28T09:34:51Z</updated>

		<summary type="html">&lt;p&gt;Janx: Now that bug 912121 has landed, all the Devtools code lives in the top-level /devtools/ directory.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Do not edit this page&#039;&#039;&#039; unless either:&lt;br /&gt;
&lt;br /&gt;
# you are a module owner who is:&lt;br /&gt;
#* altering the list of peers in your module&lt;br /&gt;
#* adding or removing a sub-module&lt;br /&gt;
#* changing the owner of one of your sub-modules; or&lt;br /&gt;
# you have agreed a change of owner or module addition/deletion with the Module Ownership Module group, probably via [https://www.mozilla.org/about/forums/#governance mozilla.governance].&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Add-on SDK&lt;br /&gt;
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications&lt;br /&gt;
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]&lt;br /&gt;
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Mark Hammond, Myk Melez, Will Bamberg&lt;br /&gt;
|forum=http://groups.google.com/group/mozilla-labs-jetpack&lt;br /&gt;
|source_dirs=https://github.com/mozilla/addon-sdk&lt;br /&gt;
|url=https://wiki.mozilla.org/Jetpack&lt;br /&gt;
|components=Add-on SDK&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Android Background Services&lt;br /&gt;
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.&lt;br /&gt;
|owner=[mailto:rnewman@mozilla.com Richard Newman]&lt;br /&gt;
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox] &lt;br /&gt;
|forum=mozilla.dev.platforms.mobile &lt;br /&gt;
|source_dirs=https://github.com/mozilla-services/android-sync &lt;br /&gt;
|url=https://wiki.mozilla.org/Android/Services&lt;br /&gt;
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Batucada&lt;br /&gt;
|description=The software platform for the Drumbeat website&lt;br /&gt;
|owner=[mailto:paul@mozillafoundation.org Paul Osman]&lt;br /&gt;
|peers=&lt;br /&gt;
|group=drumbeat-website&lt;br /&gt;
|source_dirs=http://github.com/mozilla/batucada&lt;br /&gt;
|url=http://www.drumbeat.org/project/batucada&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=BrowserID&lt;br /&gt;
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..) &lt;br /&gt;
|owner=[mailto:benadida@mozilla.com Ben Adida]&lt;br /&gt;
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons&lt;br /&gt;
|source_dirs=&lt;br /&gt;
  BrowserID server code: https://github.com/mozilla/browserid,    &lt;br /&gt;
  BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity &lt;br /&gt;
|forum=https://lists.mozilla.org/listinfo/dev-identity &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Camino&lt;br /&gt;
|description=Mac only standalone browser&lt;br /&gt;
|owner=[mailto:pinkerton@aol.net Mike Pinkerton], [mailto:stuart.morgan@alumni.case.edu Stuart Morgan]&lt;br /&gt;
|peers=[mailto:mark@moxienet.com Mark Mentovai], [mailto:smfr@smfr.org Simon Fraser]&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=camino/&lt;br /&gt;
|url=&lt;br /&gt;
|components=Camino&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=ChatZilla&lt;br /&gt;
|description=IRC client&lt;br /&gt;
|owner=[mailto:rginda@hacksrus.com Rob Ginda]&lt;br /&gt;
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]&lt;br /&gt;
|group=dev-apps-chatzilla&lt;br /&gt;
|source_dirs=extensions/irc/&lt;br /&gt;
|url=http://chatzilla.hacksrus.com/&lt;br /&gt;
|components=Other Applications::ChatZilla&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Composer&lt;br /&gt;
|description=Editor/Composer&lt;br /&gt;
|owner=[mailto:daniel@glazman.org Daniel Glazman]&lt;br /&gt;
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh &#039;timeless&#039; Soref]&lt;br /&gt;
|group=dev-tech-editor&lt;br /&gt;
|source_dirs=editor/&lt;br /&gt;
|url=http://www.mozilla.org/editor&lt;br /&gt;
|components=Composer&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Content Services Infrastructure&lt;br /&gt;
|description=A set of data services that allow for content to be served and measured&lt;br /&gt;
|owner=[mailto:oyiptong@mozilla.com Olivier Yiptong]&lt;br /&gt;
|peers=[mailto:dougt@mozilla.org Doug Turner], [mailto:tspurway@mozilla.com Tim Spurway], [mailto:nanjiang@mozilla.com Nan Jiang]&lt;br /&gt;
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx&lt;br /&gt;
|url=https://wiki.mozilla.org/Tiles&lt;br /&gt;
|components=Content Services&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Desktop Runtime&lt;br /&gt;
|description=webapp runtime for desktop&lt;br /&gt;
|owner=[https://mozillians.org/en-US/u/myk/ Myk Melez]&lt;br /&gt;
|peers=[https://mozillians.org/en-US/u/marco/ Marco Castelluccio], [https://mozillians.org/en-US/u/felipe/ Felipe Gomes], [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]&lt;br /&gt;
|forum=dev-webapps&lt;br /&gt;
|source_dirs=webapprt/, toolkit/webapps/&lt;br /&gt;
|url=https://wiki.mozilla.org/Apps/WebRT&lt;br /&gt;
|components=Firefox::Webapp Runtime, Firefox::Web Apps&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Devtools&lt;br /&gt;
|description=Mozilla Developer Tools&lt;br /&gt;
|owner=[mailto:rcampbell@mozilla.com Rob Campbell], [mailto:dcamp@mozilla.com Dave Camp]&lt;br /&gt;
|peers=[mailto:mihai.sucan@gmail.com Mihai Sucan], [mailto:jwalker@mozilla.com Joe Walker], [mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:fayearthur@gmail.com Heather Arthur], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:anton@mozilla.com Anton Kovalyov], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bbenvie@mozilla.com Brandon Benvie], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes]&lt;br /&gt;
|group=dev-developer-tools&lt;br /&gt;
|source_dirs=devtools&lt;br /&gt;
|url=https://wiki.mozilla.org/DevTools&lt;br /&gt;
|components=Firefox::Developer Tools&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Directory SDK&lt;br /&gt;
|description=Tools and SDKs for accessing LDAP Directories.&lt;br /&gt;
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]&lt;br /&gt;
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]&lt;br /&gt;
|group=dev-tech-ldap&lt;br /&gt;
|source_dirs=directory/&lt;br /&gt;
|url=http://www.mozilla.org/directory&lt;br /&gt;
|components=Directory&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=DOM Inspector&lt;br /&gt;
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.&lt;br /&gt;
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]&lt;br /&gt;
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=extensions/inspector/, layout/inspector/&lt;br /&gt;
|url=&lt;br /&gt;
|components=Other Applications::DOM Inspector&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Firefox for Android (Fennec)&lt;br /&gt;
|description=Mobile Web Browser&lt;br /&gt;
|owner=[mailto:mark.finkle@gmail.com Mark Finkle]&lt;br /&gt;
|peers=[mailto:mleibovic@mozilla.com Margaret Leibovic], [mailto:wjohnston@mozilla.com Wes Johnston], [mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:nalexander@mozilla.com Nick Alexander], [https://mozillians.org/en-US/u/myk/ Myk Melez], [mailto:mcomella@mozilla.com Michael Comella]&lt;br /&gt;
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev&lt;br /&gt;
|source_dirs=mobile/&lt;br /&gt;
|url=https://wiki.mozilla.org/Fennec&lt;br /&gt;
|components=Firefox for Android&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Firefox Accounts&lt;br /&gt;
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required. &lt;br /&gt;
|owner=[mailto:ckarlof@mozilla.com Chris Karlof]&lt;br /&gt;
|peers=[mailto:dcoates@mozilla.com Danny Coates], [mailto:zcarter@mozilla.com Zach Carter], [mailto:rfkelly@mozilla.com Ryan Kelly], [mailto:chilts@mozilla.com Andrew Chilton], [mailto:fmarier@mozilla.com Francois Marier], [mailto:smcarthur@mozilla.com Sean McArthur], [mailto:nchapman@mozilla.com Nick Chapman], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:jrgm@mozilla.com John Morrison], [mailto:pdehaan@mozilla.com Peter deHaan]&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client&lt;br /&gt;
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct&lt;br /&gt;
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Firefox for Metro&lt;br /&gt;
|description=Touch-screen-friendly browser for Windows&lt;br /&gt;
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]&lt;br /&gt;
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]&lt;br /&gt;
|forum=https://mail.mozilla.org/listinfo/metro&lt;br /&gt;
|source_dirs=browser/metro&lt;br /&gt;
|url=https://wiki.mozilla.org/Firefox/Metro&lt;br /&gt;
|components=Firefox for Metro&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Loop aka Firefox Hello&lt;br /&gt;
|description=Voice and Video Collaboration System&lt;br /&gt;
|owner=[mailto:abr@mozilla.com Adam Roach]&lt;br /&gt;
|peers=[mailto:standard8@mozilla.com Mark Banner], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]&lt;br /&gt;
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)&lt;br /&gt;
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client&lt;br /&gt;
|url=https://wiki.mozilla.org/Loop&lt;br /&gt;
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Mozilla Location Service (MLS)&lt;br /&gt;
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.&lt;br /&gt;
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]&lt;br /&gt;
|peers=[mailto:vng@mozilla.com Victor Ng]&lt;br /&gt;
|forum=mozilla.dev.geolocation&lt;br /&gt;
|source_dirs=https://github.com/mozilla/ichnaea&lt;br /&gt;
|url=https://location.services.mozilla.com&lt;br /&gt;
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Mozilla Stumbler (&amp;quot;MozStumbler&amp;quot;)&lt;br /&gt;
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).&lt;br /&gt;
|owner=[mailto:gkeeley@mozilla.com Garvan Keeley]&lt;br /&gt;
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]&lt;br /&gt;
|forum=mozilla.dev.geolocation&lt;br /&gt;
|source_dirs=https://github.com/mozilla/MozStumbler &lt;br /&gt;
|url=https://location.services.mozilla.com&lt;br /&gt;
|components=https://github.com/mozilla/MozStumbler/issues&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Sync&lt;br /&gt;
|description=Firefox Sync client&lt;br /&gt;
|owner=[mailto:mconnor@mozilla.com Mike Connor]&lt;br /&gt;
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=services/sync/&lt;br /&gt;
|url=https://wiki.mozilla.org/Services/Process/Code_Review&lt;br /&gt;
|components=Sync&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Party Tool&lt;br /&gt;
|description=PHP-based party tool used for Firefox Party&lt;br /&gt;
|owner=[mailto:rflint@ryanflint.com Ryan Flint]&lt;br /&gt;
|peers=[mailto:morgamic@mozilla.com Mike Morgan], [mailto:reed@reedloden.com Reed Loden]&lt;br /&gt;
|group=dev-apps-webtools&lt;br /&gt;
|source_dirs=webtools/partytool/&lt;br /&gt;
|url=http://wiki.mozilla.org/Webtools:PartyTool&lt;br /&gt;
|components=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Penelope&lt;br /&gt;
|description=Eudora-like functionality and theme added to Thunderbird.&lt;br /&gt;
|owner=[mailto:beckley@qualcomm.com Jeff Beckley]&lt;br /&gt;
|peers=&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=penelope/&lt;br /&gt;
|url=https://wiki.mozilla.org/Penelope&lt;br /&gt;
|components=Penelope&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Popcorn.js&lt;br /&gt;
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web. &lt;br /&gt;
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]&lt;br /&gt;
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]&lt;br /&gt;
|group=dev-popcorn&lt;br /&gt;
|source_dirs= https://github.com/mozilla/popcorn-js/&lt;br /&gt;
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]&lt;br /&gt;
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Popcorn Maker&lt;br /&gt;
|description=An SDK for authoring Popcorn projects.&lt;br /&gt;
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]&lt;br /&gt;
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]&lt;br /&gt;
|group=dev-popcorn&lt;br /&gt;
|source_dirs= https://github.com/mozilla/butter/&lt;br /&gt;
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]&lt;br /&gt;
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Rhino&lt;br /&gt;
|description=JavaScript interpreter/compiler implemented in Java&lt;br /&gt;
|owner=[mailto:greg@apigee.com Greg Brail]&lt;br /&gt;
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]&lt;br /&gt;
|group=dev-tech-js-engine&lt;br /&gt;
|source_dirs=js/rhino/&lt;br /&gt;
|url=http://www.mozilla.org/rhino/&lt;br /&gt;
|components=Rhino&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Standalone Composer&lt;br /&gt;
|description=Standalone editor/composer based on mozilla/toolkit&lt;br /&gt;
|owner=[mailto:daniel@glazman.org Daniel Glazman]&lt;br /&gt;
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]&lt;br /&gt;
|group=dev-tech-editor,dev-apps-other&lt;br /&gt;
|source_dirs=composer/&lt;br /&gt;
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu&lt;br /&gt;
|components=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=URL Classifier&lt;br /&gt;
|description=Database and list-based classification of URL resources,&lt;br /&gt;
such as Tracking Protection and SafeBrowsing.&lt;br /&gt;
|owner=[mailto:gcp@mozilla.com Gian-Carlo Pascutto (client)], [mailto:rtilder@mozilla.com Ryan Tilder (server)]&lt;br /&gt;
|peers=[mailto:francois@mozilla.com François Marier], [mailto:rkelly@mozilla.com Ryan Kelly]&lt;br /&gt;
|group=mozilla.dev.platform&lt;br /&gt;
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar&lt;br /&gt;
|url=&lt;br /&gt;
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation&lt;br /&gt;
|components=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Venkman&lt;br /&gt;
|description=JavaScript Debugger frontend&lt;br /&gt;
|owner=[mailto:rginda@hacksrus.com Rob Ginda]&lt;br /&gt;
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh &#039;timeless&#039; Soref]&lt;br /&gt;
|group=dev-apps-js-debugger&lt;br /&gt;
|source_dirs=extensions/venkman/&lt;br /&gt;
|url=http://www.mozilla.org/projects/venkman&lt;br /&gt;
http://www.hacksrus.com/~ginda/venkman/&lt;br /&gt;
|components=Other Applications::Venkman JS Debugger&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=User:Janx&amp;diff=1092914</id>
		<title>User:Janx</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=User:Janx&amp;diff=1092914"/>
		<updated>2015-08-31T15:51:54Z</updated>

		<summary type="html">&lt;p&gt;Janx: Fix broken link with dummy user page.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hello, I&#039;m Jan Keromnes [:janx]. Nice to meet you.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Modules/Other&amp;diff=1072596</id>
		<title>Modules/Other</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Modules/Other&amp;diff=1072596"/>
		<updated>2015-05-06T14:55:11Z</updated>

		<summary type="html">&lt;p&gt;Janx: Add myself to devtools peers, as instructed by dcamp on IRC.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Do not edit this page&#039;&#039;&#039; unless either:&lt;br /&gt;
&lt;br /&gt;
# you are a module owner who is:&lt;br /&gt;
#* altering the list of peers in your module&lt;br /&gt;
#* adding or removing a sub-module&lt;br /&gt;
#* changing the owner of one of your sub-modules; or&lt;br /&gt;
# you have agreed a change of owner or module addition/deletion with the Module Ownership Module group, probably via [https://www.mozilla.org/about/forums/#governance mozilla.governance].&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Add-on SDK&lt;br /&gt;
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications&lt;br /&gt;
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]&lt;br /&gt;
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Mark Hammond, Myk Melez, Will Bamberg&lt;br /&gt;
|forum=http://groups.google.com/group/mozilla-labs-jetpack&lt;br /&gt;
|source_dirs=https://github.com/mozilla/addon-sdk&lt;br /&gt;
|url=https://wiki.mozilla.org/Jetpack&lt;br /&gt;
|components=Add-on SDK&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Android Background Services&lt;br /&gt;
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.&lt;br /&gt;
|owner=[mailto:rnewman@mozilla.com Richard Newman]&lt;br /&gt;
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox] &lt;br /&gt;
|forum=mozilla.dev.platforms.mobile &lt;br /&gt;
|source_dirs=https://github.com/mozilla-services/android-sync &lt;br /&gt;
|url=https://wiki.mozilla.org/Android/Services&lt;br /&gt;
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Batucada&lt;br /&gt;
|description=The software platform for the Drumbeat website&lt;br /&gt;
|owner=[mailto:paul@mozillafoundation.org Paul Osman]&lt;br /&gt;
|peers=&lt;br /&gt;
|group=drumbeat-website&lt;br /&gt;
|source_dirs=http://github.com/mozilla/batucada&lt;br /&gt;
|url=http://www.drumbeat.org/project/batucada&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=BrowserID&lt;br /&gt;
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..) &lt;br /&gt;
|owner=[mailto:benadida@mozilla.com Ben Adida]&lt;br /&gt;
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons&lt;br /&gt;
|source_dirs=&lt;br /&gt;
  BrowserID server code: https://github.com/mozilla/browserid,    &lt;br /&gt;
  BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity &lt;br /&gt;
|forum=https://lists.mozilla.org/listinfo/dev-identity &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Camino&lt;br /&gt;
|description=Mac only standalone browser&lt;br /&gt;
|owner=[mailto:pinkerton@aol.net Mike Pinkerton], [mailto:stuart.morgan@alumni.case.edu Stuart Morgan]&lt;br /&gt;
|peers=[mailto:mark@moxienet.com Mark Mentovai], [mailto:smfr@smfr.org Simon Fraser]&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=camino/&lt;br /&gt;
|url=&lt;br /&gt;
|components=Camino&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=ChatZilla&lt;br /&gt;
|description=IRC client&lt;br /&gt;
|owner=[mailto:rginda@hacksrus.com Rob Ginda]&lt;br /&gt;
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]&lt;br /&gt;
|group=dev-apps-chatzilla&lt;br /&gt;
|source_dirs=extensions/irc/&lt;br /&gt;
|url=http://chatzilla.hacksrus.com/&lt;br /&gt;
|components=Other Applications::ChatZilla&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Composer&lt;br /&gt;
|description=Editor/Composer&lt;br /&gt;
|owner=[mailto:daniel@glazman.org Daniel Glazman]&lt;br /&gt;
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh &#039;timeless&#039; Soref]&lt;br /&gt;
|group=dev-tech-editor&lt;br /&gt;
|source_dirs=editor/&lt;br /&gt;
|url=http://www.mozilla.org/editor&lt;br /&gt;
|components=Composer&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Desktop Runtime&lt;br /&gt;
|description=webapp runtime for desktop&lt;br /&gt;
|owner=[https://mozillians.org/en-US/u/myk/ Myk Melez]&lt;br /&gt;
|peers=[https://mozillians.org/en-US/u/marco/ Marco Castelluccio], [https://mozillians.org/en-US/u/felipe/ Felipe Gomes], [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]&lt;br /&gt;
|forum=dev-webapps&lt;br /&gt;
|source_dirs=webapprt/, toolkit/webapps/&lt;br /&gt;
|url=https://wiki.mozilla.org/Apps/WebRT&lt;br /&gt;
|components=Firefox::Webapp Runtime, Firefox::Web Apps&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Devtools&lt;br /&gt;
|description=Mozilla Developer Tools&lt;br /&gt;
|owner=[mailto:rcampbell@mozilla.com Rob Campbell], [mailto:dcamp@mozilla.com Dave Camp]&lt;br /&gt;
|peers=[mailto:mihai.sucan@gmail.com Mihai Sucan], [mailto:jwalker@mozilla.com Joe Walker], [mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:fayearthur@gmail.com Heather Arthur], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:anton@mozilla.com Anton Kovalyov], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bbenvie@mozilla.com Brandon Benvie], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes]&lt;br /&gt;
|group=dev-developer-tools&lt;br /&gt;
|source_dirs=browser/devtools, toolkit/devtools&lt;br /&gt;
|url=https://wiki.mozilla.org/DevTools&lt;br /&gt;
|components=Firefox::Developer Tools&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Directory SDK&lt;br /&gt;
|description=Tools and SDKs for accessing LDAP Directories.&lt;br /&gt;
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]&lt;br /&gt;
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]&lt;br /&gt;
|group=dev-tech-ldap&lt;br /&gt;
|source_dirs=directory/&lt;br /&gt;
|url=http://www.mozilla.org/directory&lt;br /&gt;
|components=Directory&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=DOM Inspector&lt;br /&gt;
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.&lt;br /&gt;
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]&lt;br /&gt;
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=extensions/inspector/, layout/inspector/&lt;br /&gt;
|url=&lt;br /&gt;
|components=Other Applications::DOM Inspector&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Fennec&lt;br /&gt;
|description=Mobile Web Browser&lt;br /&gt;
|owner=[mailto:mark.finkle@gmail.com Mark Finkle]&lt;br /&gt;
|peers=[mailto:mbrubeck@mozilla.com Matt Brubeck], [mailto:wjohnston@mozilla.com Wes Johnston], [mailto:lucasr@mozilla.com Lucas Rocha], [mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:mleibovic@mozilla.com Margaret Leibovic], [mailto:rnewman@mozilla.com Richard Newman], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:nalexander@mozilla.com Nick Alexander], [https://mozillians.org/en-US/u/myk/ Myk Melez], [mailto:mcomella@mozilla.com Michael Comella]&lt;br /&gt;
|group=dev-platforms-mobile&lt;br /&gt;
|source_dirs=mobile/&lt;br /&gt;
|url=https://wiki.mozilla.org/Fennec&lt;br /&gt;
|components=Firefox for Android&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Firefox Accounts&lt;br /&gt;
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required. &lt;br /&gt;
|owner=[mailto:ckarlof@mozilla.com Chris Karlof]&lt;br /&gt;
|peers=[mailto:dcoates@mozilla.com Danny Coates], [mailto:zcarter@mozilla.com Zach Carter], [mailto:rfkelly@mozilla.com Ryan Kelly], [mailto:chilts@mozilla.com Andrew Chilton], [mailto:fmarier@mozilla.com Francois Marier], [mailto:smcarthur@mozilla.com Sean McArthur], [mailto:nchapman@mozilla.com Nick Chapman], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:jrgm@mozilla.com John Morrison], [mailto:pdehaan@mozilla.com Peter deHaan]&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client&lt;br /&gt;
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct&lt;br /&gt;
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Firefox for Metro&lt;br /&gt;
|description=Touch-screen-friendly browser for Windows&lt;br /&gt;
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]&lt;br /&gt;
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]&lt;br /&gt;
|forum=https://mail.mozilla.org/listinfo/metro&lt;br /&gt;
|source_dirs=browser/metro&lt;br /&gt;
|url=https://wiki.mozilla.org/Firefox/Metro&lt;br /&gt;
|components=Firefox for Metro&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Loop aka Firefox Hello&lt;br /&gt;
|description=Voice and Video Collaboration System&lt;br /&gt;
|owner=[mailto:abr@mozilla.com Adam Roach]&lt;br /&gt;
|peers=[mailto:standard8@mozilla.com Mark Banner], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]&lt;br /&gt;
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)&lt;br /&gt;
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client&lt;br /&gt;
|url=https://wiki.mozilla.org/Loop&lt;br /&gt;
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Mozilla Location Service (MLS)&lt;br /&gt;
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.&lt;br /&gt;
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]&lt;br /&gt;
|peers=[mailto:vng@mozilla.com Victor Ng]&lt;br /&gt;
|forum=mozilla.dev.geolocation&lt;br /&gt;
|source_dirs=https://github.com/mozilla/ichnaea&lt;br /&gt;
|url=https://location.services.mozilla.com&lt;br /&gt;
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Mozilla Stumbler (&amp;quot;MozStumbler&amp;quot;)&lt;br /&gt;
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).&lt;br /&gt;
|owner=[mailto:gkeeley@mozilla.com Garvan Keeley]&lt;br /&gt;
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]&lt;br /&gt;
|forum=mozilla.dev.geolocation&lt;br /&gt;
|source_dirs=https://github.com/mozilla/MozStumbler &lt;br /&gt;
|url=https://location.services.mozilla.com&lt;br /&gt;
|components=https://github.com/mozilla/MozStumbler/issues&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Sync&lt;br /&gt;
|description=Firefox Sync client&lt;br /&gt;
|owner=[mailto:mconnor@mozilla.com Mike Connor]&lt;br /&gt;
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=services/sync/&lt;br /&gt;
|url=https://wiki.mozilla.org/Services/Process/Code_Review&lt;br /&gt;
|components=Sync&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Party Tool&lt;br /&gt;
|description=PHP-based party tool used for Firefox Party&lt;br /&gt;
|owner=[mailto:rflint@ryanflint.com Ryan Flint]&lt;br /&gt;
|peers=[mailto:morgamic@mozilla.com Mike Morgan], [mailto:reed@reedloden.com Reed Loden]&lt;br /&gt;
|group=dev-apps-webtools&lt;br /&gt;
|source_dirs=webtools/partytool/&lt;br /&gt;
|url=http://wiki.mozilla.org/Webtools:PartyTool&lt;br /&gt;
|components=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Penelope&lt;br /&gt;
|description=Eudora-like functionality and theme added to Thunderbird.&lt;br /&gt;
|owner=[mailto:beckley@qualcomm.com Jeff Beckley]&lt;br /&gt;
|peers=&lt;br /&gt;
|group=&lt;br /&gt;
|source_dirs=penelope/&lt;br /&gt;
|url=https://wiki.mozilla.org/Penelope&lt;br /&gt;
|components=Penelope&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Popcorn.js&lt;br /&gt;
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web. &lt;br /&gt;
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]&lt;br /&gt;
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]&lt;br /&gt;
|group=dev-popcorn&lt;br /&gt;
|source_dirs= https://github.com/mozilla/popcorn-js/&lt;br /&gt;
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]&lt;br /&gt;
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Popcorn Maker&lt;br /&gt;
|description=An SDK for authoring Popcorn projects.&lt;br /&gt;
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]&lt;br /&gt;
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]&lt;br /&gt;
|group=dev-popcorn&lt;br /&gt;
|source_dirs= https://github.com/mozilla/butter/&lt;br /&gt;
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]&lt;br /&gt;
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Rhino&lt;br /&gt;
|description=JavaScript interpreter/compiler implemented in Java&lt;br /&gt;
|owner=[mailto:greg@apigee.com Greg Brail]&lt;br /&gt;
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]&lt;br /&gt;
|group=dev-tech-js-engine&lt;br /&gt;
|source_dirs=js/rhino/&lt;br /&gt;
|url=http://www.mozilla.org/rhino/&lt;br /&gt;
|components=Rhino&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Standalone Composer&lt;br /&gt;
|description=Standalone editor/composer based on mozilla/toolkit&lt;br /&gt;
|owner=[mailto:daniel@glazman.org Daniel Glazman]&lt;br /&gt;
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]&lt;br /&gt;
|group=dev-tech-editor,dev-apps-other&lt;br /&gt;
|source_dirs=composer/&lt;br /&gt;
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu&lt;br /&gt;
|components=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Tracking Protection&lt;br /&gt;
|description=Tracking Protection to improve user privacy and control by expressing user prefs and enforcing them.&lt;br /&gt;
|owner=[mailto:mmc@mozilla.com Monica The-Awesome Chew]&lt;br /&gt;
|peers=[mailto:dougt@mozilla.com Doug Turner], [mailto:mmayo@mozilla.com Mark Mayo]&lt;br /&gt;
|group=mozilla.dev.platform&lt;br /&gt;
|source_dirs=toolkit/components/url-classifier, netwerk/base/src/nsChannelClassifier, https://github.com/mozilla-services/shavar&lt;br /&gt;
|url=https://wiki.mozilla.org/Privacy/Roadmap/Tracking&lt;br /&gt;
|components=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Module&lt;br /&gt;
|name=Venkman&lt;br /&gt;
|description=JavaScript Debugger frontend&lt;br /&gt;
|owner=[mailto:rginda@hacksrus.com Rob Ginda]&lt;br /&gt;
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh &#039;timeless&#039; Soref]&lt;br /&gt;
|group=dev-apps-js-debugger&lt;br /&gt;
|source_dirs=extensions/venkman/&lt;br /&gt;
|url=http://www.mozilla.org/projects/venkman&lt;br /&gt;
http://www.hacksrus.com/~ginda/venkman/&lt;br /&gt;
|components=Other Applications::Venkman JS Debugger&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=DevTools/WiFi_Debugging&amp;diff=1053387</id>
		<title>DevTools/WiFi Debugging</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=DevTools/WiFi_Debugging&amp;diff=1053387"/>
		<updated>2015-02-03T14:45:54Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Toggle Feature Flags */ In Nightly, the pref &amp;quot;devtools.webide.enabled&amp;quot; has been defaulting to &amp;quot;true&amp;quot; for a while now.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Security Warning ==&lt;br /&gt;
&lt;br /&gt;
This page describes how to use the &#039;&#039;&#039;current version&#039;&#039;&#039; of WiFi debugging in the tree (after landing [https://bugzil.la/1000428 bug 1000428]).  There is still much work to be done to make it secure.  If you want more info what the completed version would be like, check out the [https://wiki.mozilla.org/DevTools/WiFi_Debugging/Design design details].&lt;br /&gt;
&lt;br /&gt;
The current version of WiFi debugging is &#039;&#039;&#039;not authenticated or encrypted&#039;&#039;&#039;.  This means that, if you enable it as described below:&lt;br /&gt;
&lt;br /&gt;
* Anyone on the same WiFi network can connect to your device with the DevTools&lt;br /&gt;
* Anyone on the same WiFi network can read your debugging traffic (which can include full requests, responses, etc.)&lt;br /&gt;
&lt;br /&gt;
Because of this, it would be wise to avoid enabling this feature at this time on a device with data that is sensitive or personal in any way.  These issues will be resolved before this feature is available by default.&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
WiFi debugging allows WebIDE to connect to your Firefox OS device via your local WiFi network instead of a USB cable.&lt;br /&gt;
&lt;br /&gt;
The connection experience is generally more straightforward (especially after connecting to a device the first time) than with USB and also more convenient to use since you&#039;re no longer tied down by a cable.&lt;br /&gt;
&lt;br /&gt;
== Toggle Feature Flags ==&lt;br /&gt;
&lt;br /&gt;
Since this feature is still under heavy development, there are few things you must do make it available:&lt;br /&gt;
&lt;br /&gt;
* Firefox Nightly:&lt;br /&gt;
** Set the pref &amp;lt;code&amp;gt;devtools.remote.wifi.scan&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;&lt;br /&gt;
* Firefox OS:&lt;br /&gt;
** Set the pref &amp;lt;code&amp;gt;devtools.remote.wifi.visible&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;&lt;br /&gt;
** Enable Settings -&amp;gt; Developer -&amp;gt; DevTools via Wi-Fi&lt;br /&gt;
&lt;br /&gt;
Also, it&#039;s best to make sure you&#039;re using the latest Firefox Nightly and latest build of Firefox OS from master.&lt;br /&gt;
&lt;br /&gt;
== Connect ==&lt;br /&gt;
&lt;br /&gt;
# Enable WiFi debugging on Firefox OS (Settings -&amp;gt; Developer -&amp;gt; DevTools via Wi-Fi)&lt;br /&gt;
# Open WebIDE in Firefox Nightly (Tools -&amp;gt; Web Developer -&amp;gt; WebIDE)&lt;br /&gt;
# Click &amp;quot;Select Runtime&amp;quot; to open the runtimes panel&lt;br /&gt;
# Your Firefox OS device should show up in the &amp;quot;WiFi Devices&amp;quot; section&lt;br /&gt;
# A connection prompt may appear on device, choose &amp;quot;Accept&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This process will change as we move forward to include device authentication steps when first connecting to a new device.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Mulet&amp;diff=1032791</id>
		<title>Mulet</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Mulet&amp;diff=1032791"/>
		<updated>2014-11-12T13:18:51Z</updated>

		<summary type="html">&lt;p&gt;Janx: typo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
        |\               /|&lt;br /&gt;
        |\\             //|      Mulet is a meant to merge all Firefox OS runtimes that exist on desktop:&lt;br /&gt;
        | \\           // |         - b2g desktop&lt;br /&gt;
        |_=\\         //=_|         - Fx OS simulator addon&lt;br /&gt;
        | _=||       ||=_ |         - Special gaia profile running on Firefox nightly (&amp;quot;DEBUG=1&amp;quot; gaia profiles)&lt;br /&gt;
        \ _=||       ||=_ /         &lt;br /&gt;
         \_ =\&#039;,:;:,&#039;/= _/       Mulet nightly builds are available here:   &lt;br /&gt;
           \__&amp;quot; `:` &amp;quot;__/           http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/&lt;br /&gt;
              )     (            &lt;br /&gt;
             /       \          It requires a gaia profile to startup correctly:   &lt;br /&gt;
            |         |            $ cd ~/gaia&lt;br /&gt;
            |_       _|            $ make&lt;br /&gt;
            (0\     /0)            $ ~/mulet/firefox-bin -profile profile/&lt;br /&gt;
            |         |            &lt;br /&gt;
            `.       .&#039;          You should see gaia automatically loaded in first tab,  &lt;br /&gt;
             |       |           with the devtools showing up on the side.&lt;br /&gt;
             ;       |           &lt;br /&gt;
             :|     |;           You can build it out of mozilla-central with the following mozconfig:&lt;br /&gt;
             &#039;/     \&#039;             ac_add_options --enable-application=b2g/dev&lt;br /&gt;
             (()   ())           &lt;br /&gt;
     ©jgs     \     /           (&#039;&#039;&amp;quot;Mulet&amp;quot;&#039;&#039; comes the french word designating a &amp;quot;mule&amp;quot; and is spelled with only one &#039;&#039;l&#039;&#039;!)&lt;br /&gt;
               `---&#039;&lt;br /&gt;
&lt;br /&gt;
=== Why merge all runtimes? ===&lt;br /&gt;
&lt;br /&gt;
To ensure that everyone: app developers, gaia contributors and platform engineers are all on the same page and use the same environment and runtime.&lt;br /&gt;
Then merging all runtimes allows to share the advantages of all of them.&lt;br /&gt;
Gaia will run with the same feature set than b2g desktop (ie. many features require some glue code that doesn&#039;t exist in Firefox. for example system message API).&lt;br /&gt;
And we will have all devtools working against gaia.&lt;br /&gt;
While sharing the additional features coming from the simulator (rotation support for ex)&lt;br /&gt;
&lt;br /&gt;
=== Where can I download it? ===&lt;br /&gt;
&lt;br /&gt;
Nightly builds are available [http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/ here].&lt;br /&gt;
Look got &#039;&#039;firefox-*&#039;&#039; packages for your platform.&lt;br /&gt;
&lt;br /&gt;
=== How different is mulet compared to the existing runtimes? ===&lt;br /&gt;
&lt;br /&gt;
Compared to b2g desktop, mulet runs within a customized version of Firefox.&lt;br /&gt;
The goal is to seemlessly run b2g within a firefox tab.&lt;br /&gt;
So mulet contains all preferences, settings and glue code that used to exists in b2g desktop.&lt;br /&gt;
&lt;br /&gt;
=== How do I build it? ===&lt;br /&gt;
&lt;br /&gt;
Checkout mozilla-central and use &amp;quot;ac_add_options --enable-application=b2g/dev&amp;quot; in your mozconfig.&lt;br /&gt;
&lt;br /&gt;
=== How do I run FxOS on it? ===&lt;br /&gt;
&lt;br /&gt;
Checkout the gaia repo, then build a regular profile (just run make within your gaia folder).&lt;br /&gt;
Once your gaia profile is built, open mulet with this profile.&lt;br /&gt;
&lt;br /&gt;
  $ cd ~/gaia&lt;br /&gt;
  $ make&lt;br /&gt;
  ...&lt;br /&gt;
  $ cd ~/gecko&lt;br /&gt;
  $ echo &amp;quot;ac_add_options --enable-application=b2g/dev&amp;quot; &amp;gt; mulet&lt;br /&gt;
  $ MOZCONFIG=mulet ./mach build&lt;br /&gt;
  $ MOZCONFIG=mulet ./mach run -profile ~/gaia/profile&lt;br /&gt;
&lt;br /&gt;
Then, if FxOS doesn&#039;t automatically open itself, go to the following URL:&lt;br /&gt;
  chrome://b2g/content/shell.html&lt;br /&gt;
&lt;br /&gt;
=== How do I run tests? ===&lt;br /&gt;
&lt;br /&gt;
Just like on desktop firefox (see [https://developer.mozilla.org/en/docs/Running_automated_tests Running automated tests] on MDN).&lt;br /&gt;
&lt;br /&gt;
=== How to report bugs? ===&lt;br /&gt;
&lt;br /&gt;
Please fill bugs within [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20OS&amp;amp;component=Runtime Firefox OS::Runtime component].&lt;br /&gt;
&lt;br /&gt;
=== What is mulet for a gecko developer? ===&lt;br /&gt;
&lt;br /&gt;
Mulet is a Firefox desktop build, with MOZ_B2G env variable set to 1.&lt;br /&gt;
This variable enables most of the b2g specifics that are built only on FxOS (and not on Fx Desktop).&lt;br /&gt;
It is also built with MOZ_MULET=1 in order to help distinguish Firefox Desktop from Mulet.&lt;br /&gt;
A dedicated folder exists for mulet in mozilla-central, [http://mxr.mozilla.org/mozilla-central/source/b2g/dev/ m-c/b2g/dev], which contains mostly build/configuration files.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Mulet&amp;diff=1032788</id>
		<title>Mulet</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Mulet&amp;diff=1032788"/>
		<updated>2014-11-12T13:17:33Z</updated>

		<summary type="html">&lt;p&gt;Janx: explain how to run tests&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
        |\               /|&lt;br /&gt;
        |\\             //|      Mulet is a meant to merge all Firefox OS runtimes that exist on desktop:&lt;br /&gt;
        | \\           // |         - b2g desktop&lt;br /&gt;
        |_=\\         //=_|         - Fx OS simulator addon&lt;br /&gt;
        | _=||       ||=_ |         - Special gaia profile running on Firefox nightly (&amp;quot;DEBUG=1&amp;quot; gaia profiles)&lt;br /&gt;
        \ _=||       ||=_ /         &lt;br /&gt;
         \_ =\&#039;,:;:,&#039;/= _/       Mulet nightly builds are available here:   &lt;br /&gt;
           \__&amp;quot; `:` &amp;quot;__/           http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/&lt;br /&gt;
              )     (            &lt;br /&gt;
             /       \          It requires a gaia profile to startup correctly:   &lt;br /&gt;
            |         |            $ cd ~/gaia&lt;br /&gt;
            |_       _|            $ make&lt;br /&gt;
            (0\     /0)            $ ~/mulet/firefox-bin -profile profile/&lt;br /&gt;
            |         |            &lt;br /&gt;
            `.       .&#039;          You should see gaia automatically loaded in first tab,  &lt;br /&gt;
             |       |           with the devtools showing up on the side.&lt;br /&gt;
             ;       |           &lt;br /&gt;
             :|     |;           You can build it out of mozilla-central with the following mozconfig:&lt;br /&gt;
             &#039;/     \&#039;             ac_add_options --enable-application=b2g/dev&lt;br /&gt;
             (()   ())           &lt;br /&gt;
     ©jgs     \     /           (&#039;&#039;&amp;quot;Mulet&amp;quot;&#039;&#039; comes the french word designating a &amp;quot;mule&amp;quot; and is spelled with only one &#039;&#039;l&#039;&#039;!)&lt;br /&gt;
               `---&#039;&lt;br /&gt;
&lt;br /&gt;
=== Why merge all runtimes? ===&lt;br /&gt;
&lt;br /&gt;
To ensure that everyone: app developers, gaia contributors and platform engineers are all on the same page and use the same environment and runtime.&lt;br /&gt;
Then merging all runtimes allows to share the advantages of all of them.&lt;br /&gt;
Gaia will run with the same feature set than b2g desktop (ie. many features require some glue code that doesn&#039;t exist in Firefox. for example system message API).&lt;br /&gt;
And we will have all devtools working against gaia.&lt;br /&gt;
While sharing the additional features coming from the simulator (rotation support for ex)&lt;br /&gt;
&lt;br /&gt;
=== Where can I download it? ===&lt;br /&gt;
&lt;br /&gt;
Nightly builds are available [http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central/ here].&lt;br /&gt;
Look got &#039;&#039;firefox-*&#039;&#039; packages for your platform.&lt;br /&gt;
&lt;br /&gt;
=== How different is mulet compared to the existing runtimes? ===&lt;br /&gt;
&lt;br /&gt;
Compared to b2g desktop, mulet runs within a customized version of Firefox.&lt;br /&gt;
The goal is to seemlessly run b2g within a firefox tab.&lt;br /&gt;
So mulet contains all preferences, settings and glue code that used to exists in b2g desktop.&lt;br /&gt;
&lt;br /&gt;
=== How do I build it? ===&lt;br /&gt;
&lt;br /&gt;
Checkout mozilla-central and use &amp;quot;ac_add_options --enable-application=b2g/dev&amp;quot; in your mozconfig.&lt;br /&gt;
&lt;br /&gt;
=== How do I run FxOS on it? ===&lt;br /&gt;
&lt;br /&gt;
Checkout the gaia repo, then build a regular profile (just run make within your gaia folder).&lt;br /&gt;
Once your gaia profile is built, open mulet with this profile.&lt;br /&gt;
&lt;br /&gt;
  $ cd ~/gaia&lt;br /&gt;
  $ make&lt;br /&gt;
  ...&lt;br /&gt;
  $ cd ~/gecko&lt;br /&gt;
  $ echo &amp;quot;ac_add_options --enable-application=b2g/dev&amp;quot; &amp;gt; mulet&lt;br /&gt;
  $ MOZCONFIG=mulet ./mach build&lt;br /&gt;
  $ MOZCONFIG=mulet ./mach run -profile ~/gaia/profile&lt;br /&gt;
&lt;br /&gt;
Then, if FxOS doesn&#039;t automatically open itself, go to the following URL:&lt;br /&gt;
  chrome://b2g/content/shell.html&lt;br /&gt;
&lt;br /&gt;
=== How do I run tests? ===&lt;br /&gt;
&lt;br /&gt;
Just like desktop firefox (see [https://developer.mozilla.org/en/docs/Running_automated_tests Running automated tests] on MDN).&lt;br /&gt;
&lt;br /&gt;
=== How to report bugs? ===&lt;br /&gt;
&lt;br /&gt;
Please fill bugs within [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20OS&amp;amp;component=Runtime Firefox OS::Runtime component].&lt;br /&gt;
&lt;br /&gt;
=== What is mulet for a gecko developer? ===&lt;br /&gt;
&lt;br /&gt;
Mulet is a Firefox desktop build, with MOZ_B2G env variable set to 1.&lt;br /&gt;
This variable enables most of the b2g specifics that are built only on FxOS (and not on Fx Desktop).&lt;br /&gt;
It is also built with MOZ_MULET=1 in order to help distinguish Firefox Desktop from Mulet.&lt;br /&gt;
A dedicated folder exists for mulet in mozilla-central, [http://mxr.mozilla.org/mozilla-central/source/b2g/dev/ m-c/b2g/dev], which contains mostly build/configuration files.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Applications/Tooltool&amp;diff=1026737</id>
		<title>ReleaseEngineering/Applications/Tooltool</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Applications/Tooltool&amp;diff=1026737"/>
		<updated>2014-10-21T01:02:19Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* How to upload files to tooltool */ Clarify tooltool user ID for non-@mozilla.com LDAPs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Tooltool basics =&lt;br /&gt;
&lt;br /&gt;
Tooltool is a client side program written in Python that uses a file manifest in concert with HTTP servers to retrieve sets of files and perform integrity checks on them based on hashcode verification.  The manifests are JSON files which list details of individual files (see below).  Each file is represented in the JSON by a dictionary with the keys “filename”, “digest”, “size” and “algorithm”.&lt;br /&gt;
&lt;br /&gt;
A set of files to be fetched by tooltool is specified via a tooltool manifest, usually a file with tt extension.&lt;br /&gt;
&lt;br /&gt;
The following is an example of a valid tooltool manifest:&lt;br /&gt;
&lt;br /&gt;
  [&lt;br /&gt;
  {&lt;br /&gt;
  &amp;quot;size&amp;quot;: 139308,&lt;br /&gt;
  &amp;quot;digest&amp;quot;: &amp;quot;b2a463249bb3a9e7f2a3604697b000d2393db4f37b623fc099beb8456fbfdb332567013a3131ad138d8633cb19c50a8b77df3990d67500af896cada8b6f698b4&amp;quot;,&lt;br /&gt;
  &amp;quot;algorithm&amp;quot;: &amp;quot;sha512&amp;quot;,&lt;br /&gt;
  &amp;quot;filename&amp;quot;: &amp;quot;file2.pdf&amp;quot;&lt;br /&gt;
  },&lt;br /&gt;
  {&lt;br /&gt;
  &amp;quot;size&amp;quot;: 3017536,&lt;br /&gt;
  &amp;quot;digest&amp;quot;: &amp;quot;630d01a329c70aedb66ae7118d12ff7dc6fe06223d1c27b793e1bacc0ca84dd469ec1a6050184f8d9c35a0636546b0e2e5be08d9b51285e53eb1c9f959fef59d&amp;quot;,&lt;br /&gt;
  &amp;quot;algorithm&amp;quot;: &amp;quot;sha512&amp;quot;,&lt;br /&gt;
  &amp;quot;filename&amp;quot;: &amp;quot;file1.pdf&amp;quot;&lt;br /&gt;
  },&lt;br /&gt;
  {&lt;br /&gt;
  &amp;quot;size&amp;quot;: 3420686,&lt;br /&gt;
  &amp;quot;digest&amp;quot;: &amp;quot;931eb84f798dc9add1a10c7bbd4cc85fe08efda26cac473411638d1f856865524a517209d4c7184d838ee542c8ebc9909dc64ef60f8653a681270ce23524e8e4&amp;quot;,&lt;br /&gt;
  &amp;quot;algorithm&amp;quot;: &amp;quot;sha512&amp;quot;,&lt;br /&gt;
  &amp;quot;filename&amp;quot;: &amp;quot;file3.pdf&amp;quot;&lt;br /&gt;
  }&lt;br /&gt;
  ]&lt;br /&gt;
&lt;br /&gt;
The simplest usecase for tooltool is to provide a manifest and the url of a tooltool server, and run a &amp;quot;fetch&amp;quot; command to download the files mentioned in the manifest:&lt;br /&gt;
&lt;br /&gt;
  python  tooltool.py fetch --url http://tooltool.pub.build.mozilla.org/temp-sm-stuff -m my-manifest.tt&lt;br /&gt;
&lt;br /&gt;
If a manifest name is not provided, tooltool will default to manifest.tt.&lt;br /&gt;
&lt;br /&gt;
Tooltool will build an url for each of the mentioned files concatenating the server url, the hashing algorithm and the file digest, and try to download.&lt;br /&gt;
&lt;br /&gt;
In this example, the urls will be:&lt;br /&gt;
&lt;br /&gt;
  http://tooltool.pub.build.mozilla.org/temp-sm-stuff/sha512/58941214a8334331e52114aab851fc3d8d5da5dd14983f933da8735c24b0ddcac134e8f13692553199c4d9a14a4b3188b62878a30b9d696edda1204666b60837&lt;br /&gt;
  http://tooltool.pub.build.mozilla.org/temp-sm-stuff/sha512/b2a463249bb3a9e7f2a3604697b000d2393db4f37b623fc099beb8456fbfdb332567013a3131ad138d8633cb19c50a8b77df3990d67500af896cada8b6f698b4&lt;br /&gt;
  http://tooltool.pub.build.mozilla.org/temp-sm-stuff/sha512/630d01a329c70aedb66ae7118d12ff7dc6fe06223d1c27b793e1bacc0ca84dd469ec1a6050184f8d9c35a0636546b0e2e5be08d9b51285e53eb1c9f959fef59d&lt;br /&gt;
  http://tooltool.pub.build.mozilla.org/temp-sm-stuff/931eb84f798dc9add1a10c7bbd4cc85fe08efda26cac473411638d1f856865524a517209d4c7184d838ee542c8ebc9909dc64ef60f8653a681270ce23524e8e4&lt;br /&gt;
&lt;br /&gt;
After downloading the files, their digest is verified according to the algorithm specified in the manifest, and they are finally renamed according to the filename specified in the manifest.&lt;br /&gt;
&lt;br /&gt;
The tooltool download servers are simply apache server folders with a flat structure (all files are stored at root level with no subfolders).&lt;br /&gt;
&lt;br /&gt;
There are global options and command arguments.  All terminal interactions after the option parser finishes is done through the Python logging API.  The default is to print logging.INFO and higher messages.  Currently, the following global options exist:&lt;br /&gt;
&lt;br /&gt;
    -q/--quiet tells Tooltool to print only logging.ERROR and higher messages&lt;br /&gt;
    -v/--verbose specifies to print logging.INFO and higher&lt;br /&gt;
    -m/--manifest &amp;lt;file&amp;gt; instructs Tooltool to reference a manifest file located at the specified path&lt;br /&gt;
    -d/--algorithm &amp;lt;algorithm&amp;gt; instructs Tooltool to use the specified algorithm&lt;br /&gt;
    -o/--overwrite tells Tooltool to overwrite a local file if the filename matches the manifest but the hash value is different to the manifest&lt;br /&gt;
    --url specifies the base url to be used for remote operations&lt;br /&gt;
&lt;br /&gt;
= Where&#039;s tooltool code? =&lt;br /&gt;
&lt;br /&gt;
Tooltool&#039;s main dev repo is [https://github.com/mozilla/build-tooltool https://github.com/mozilla/build-tooltool].&lt;br /&gt;
&lt;br /&gt;
The version of tooltool which is actually deployed in our infrastructure is in [https://hg.mozilla.org/build/puppet/modules/packages/templates/ https://hg.mozilla.org/build/puppet/modules/packages/templates/]. The tooltool.py file in the puppet repo should be in sync with the main dev repo (they should be identical, apart from the she-bang line).&lt;br /&gt;
&lt;br /&gt;
= Listing and Validating =&lt;br /&gt;
&lt;br /&gt;
The two most basic commands list a manifest and validate the local files against the manifest.  The list command lists out all of the files in the manifest as well as whether they are present and/or valid.  The return code from listing is zero unless there was an error in listing the files.  Absent or invalid files will still result in an exit code of zero if there was no error in the listing process.  The validate command is used to check if all the files in the manifest are present and valid.  The exit code for validating is zero if all files in the manifest are present and their hash matches the manifest.  It is non-zero if any file is missing locally or the file does not have the same hash as the manifest.&lt;br /&gt;
&lt;br /&gt;
= Other tooltool features =&lt;br /&gt;
&lt;br /&gt;
== The tooltool cache ==&lt;br /&gt;
&lt;br /&gt;
This has been implemented in bug [https://bugzilla.mozilla.org/show_bug.cgi?id=858635 https://bugzilla.mozilla.org/show_bug.cgi?id=858635]&lt;br /&gt;
&lt;br /&gt;
When connecting to a tooltool server to fetch a file, it is now possible to use a local cache specifying the local cache folder with the -c option, e.g.:&lt;br /&gt;
&lt;br /&gt;
  python  tooltool.py fetch --url http://tooltool.pub.build.mozilla.org/temp-sm-stuff -c ~/cache&lt;br /&gt;
&lt;br /&gt;
In the previous example, folder ~/cache will be inspected for artifacts before connecting to the specified tooltool server. If the specified cache folder does not exist, tooltool will create it (if the user running tooltool has permissions to do so!).&lt;br /&gt;
Purging the cache with the purge command&lt;br /&gt;
&lt;br /&gt;
A mechanism to purge the tooltool cache has been implemented as a separate command. Let&#039;s see some examples of purge commands:&lt;br /&gt;
&lt;br /&gt;
  python  tooltool.py purge -c ~/cache&lt;br /&gt;
  python  tooltool.py purge -c ~/cache -s 34&lt;br /&gt;
  python  tooltool.py purge -c ~/cache --size 34&lt;br /&gt;
&lt;br /&gt;
In the first example, we are cleaning up the tooltool cache completely, i.e.: all the content will be wiped out&lt;br /&gt;
&lt;br /&gt;
In the second and third example the extra parameter -s (or, in extended form, --size) is provided, which specifies the number of Gigs we want to be free at the end of the purging process. Tooltool will delete files in the cache folder, starting with the oldest ones, until the specified amount of gigs is free on disk. When there is more free space that the specified gigs when the command is invokes, no files will be deleted at all.&lt;br /&gt;
&lt;br /&gt;
=== Enabling automated tooltool cache purge within purge_build.py ===&lt;br /&gt;
&lt;br /&gt;
Since the purge_builds.py script (within the build-tools repo) is already responsible of clean-up operations, the option of cleaning the tooltool cache has been added to that script as well.&lt;br /&gt;
&lt;br /&gt;
In order for the automated cleanup to take place, two environment variables need to be setup when purge_builds.py is invoked, and namely:&lt;br /&gt;
&lt;br /&gt;
  TOOLTOOL_HOME: the folder containing tooltool.py&lt;br /&gt;
  TOOLTOOL_CACHE: the local folder being used as tooltool cache (which will be cleaned up)&lt;br /&gt;
&lt;br /&gt;
== Using multiple servers with tooltool ==&lt;br /&gt;
&lt;br /&gt;
The original implementation of tooltool supports one single download server: whenever using tooltool to fetch artifacts, a single server was specified and tooltool tried to download the file from that location exclusively.&lt;br /&gt;
&lt;br /&gt;
The need to support multiple server is justified by at least two reasons:&lt;br /&gt;
&lt;br /&gt;
* improve tooltool resiliency in case one server is not available, so that requests are made to a backup server&lt;br /&gt;
* allow the setup of tooltool repositories with different levels of visibility&lt;br /&gt;
&lt;br /&gt;
The following example illustrates how to use tooltool with multiple servers:&lt;br /&gt;
&lt;br /&gt;
  python  tooltool.py fetch --url http://server1.example.com --url http://server2.example.com&lt;br /&gt;
&lt;br /&gt;
In this case, tooltool will try to fetch the desired artifacts from server1 and, in case the server is down or does not serve the desired resource, will try with server2. An arbitrary number of servers is supported by the tooltool client. Of course, in order to use this feature the servers will need to be setup.&lt;br /&gt;
&lt;br /&gt;
See also [https://bugzilla.mozilla.org/show_bug.cgi?id=768123 https://bugzilla.mozilla.org/show_bug.cgi?id=768123].&lt;br /&gt;
&lt;br /&gt;
= How to upload to tooltool =&lt;br /&gt;
&lt;br /&gt;
Tooltool uploads have been traditionally managed by simply scp&#039;ing files to the folder served by the apache instance working as tooltool download server. A new upload mechanism has been implemented to allow better tracking of what is uploaded to tooltool (see [https://bugzilla.mozilla.org/show_bug.cgi?id=772190 &amp;quot;Bug 772190 - tooltool upload mechanism&amp;quot;]).&lt;br /&gt;
&lt;br /&gt;
The new upload procedure allow users to upload artifacts via rsync to a dedicated upload server, contextually providing some metadata about the upload. The artifacts uploaded to the upload servers will then be distributed to the relevant tooltool download servers (and their mirrors, if any) by a separate sync script which is cron&#039;d on the upload server itself.&lt;br /&gt;
&lt;br /&gt;
== Preliminary notes: ==&lt;br /&gt;
&lt;br /&gt;
* The server used for uploads (AKA tooltool upload server) is tooltool-uploads.pub.build.mozilla.org (no VPN required)&lt;br /&gt;
* Currently, artifacts uploaded to the tooltool upload server can be made visible to only one tooltool download server:&lt;br /&gt;
:* Private tooltool download server http://runtime-binaries.pvt.build.mozilla.org/tooltool/sha512&lt;br /&gt;
::* all uploads to /tooltool/uploads/user/pvt on the upload server (more details below) will be visible here&lt;br /&gt;
&lt;br /&gt;
== Pre-requisites to run an upload ==&lt;br /&gt;
&lt;br /&gt;
* You need to be added to the &amp;quot;vpn_tooltooleditors&amp;quot; LDAP group (see below)&lt;br /&gt;
* You need ssh properly configured to access the tooltool upload server; if the key you normally use to access mozilla servers is ~/.ssh/id_rsa, no further setup is needed. If it&#039;s a different one, you will need to add the following entry to your ~/.ssh/config file:&lt;br /&gt;
&lt;br /&gt;
    Host tooltool-uploads.pub.build.mozilla.org&lt;br /&gt;
      IdentityFile /path/to/my_private_key&lt;br /&gt;
      User my_user&lt;br /&gt;
&lt;br /&gt;
Note that &amp;quot;my_user&amp;quot; above is your LDAP username without the &amp;quot;@mozilla.com&amp;quot; part.&lt;br /&gt;
&lt;br /&gt;
* You need rsync installed and available in your PATH (it is used by tooltool to transfer files)&lt;br /&gt;
* You need tooltool! https://github.com/mozilla/build-tooltool/blob/master/tooltool.py&lt;br /&gt;
&lt;br /&gt;
=== How to enable a user to run tooltool uploads by adding him/her to the vpn_tooltooleditors LDAP group ===&lt;br /&gt;
First, request addition to &amp;quot;vpn_tooltooleditors&amp;quot; group, via &amp;quot;Infrastruture &amp;amp; Operations::Infrastructure:LDAP&amp;quot;.&lt;br /&gt;
Once that&#039;s done, it&#039;s an hour or two for the change to propagate from LDAP to Puppet to the upload servers.&lt;br /&gt;
They should request an ACK on the bug from someone in release engineering for that.&lt;br /&gt;
&lt;br /&gt;
== How to upload files to tooltool ==&lt;br /&gt;
&lt;br /&gt;
* Create a local folder (name it as you like) and put in it all the files you want to upload&lt;br /&gt;
* Run the tooltool distribute command (see example below)&lt;br /&gt;
&lt;br /&gt;
That&#039;s it!&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &lt;br /&gt;
  # Folder /Users/$user/upload contains file1.tar.gz, file2.tar.gz and file3.tar.gz&lt;br /&gt;
  tooltool.py distribute --folder /Users/$user/upload --message &amp;quot;Bug 123456 - artifacts needed for this and that&amp;quot; \&lt;br /&gt;
    --user $user --host tooltool-uploads.pub.build.mozilla.org --path &amp;quot;/tooltool/uploads/$user/pvt&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Note that &amp;quot;$user&amp;quot; above is your posix UID, i.e. your LDAP username without the &amp;quot;@mozilla.com&amp;quot; part (or different domain).&lt;br /&gt;
&lt;br /&gt;
The parameters in the previous command are:&lt;br /&gt;
&lt;br /&gt;
  --folder: the folder containing the files you want to upload&lt;br /&gt;
  --message: any comment you may want to write about this upload&lt;br /&gt;
  --user: the user to access the tooltool upload server&lt;br /&gt;
  --host: the upload server host or IP&lt;br /&gt;
  --path: the target folder on the upload server&lt;br /&gt;
&lt;br /&gt;
Use /tooltool/uploads/&amp;lt;your_username&amp;gt;/pvt to upload to the private download server&lt;br /&gt;
&lt;br /&gt;
=== Troubleshooting ===&lt;br /&gt;
&lt;br /&gt;
You may incur in rsync errors like:&lt;br /&gt;
&lt;br /&gt;
    rsync: connection unexpectedly closed (36 bytes received so far) [sender]&lt;br /&gt;
&lt;br /&gt;
In this case, it may help to add the following entries to your ~/.ssh/config file:&lt;br /&gt;
&lt;br /&gt;
    Host tooltool-uploads.pub.build.mozilla.org&lt;br /&gt;
      ServerAliveInterval 5&lt;br /&gt;
      ServerAliveCountMax 120&lt;br /&gt;
&lt;br /&gt;
== What now? ==&lt;br /&gt;
&lt;br /&gt;
You should receive in a few minutes (5 at most, since the sync script processing uploaded files currently runs every 5 minutes) an email confirming that your upload has been correctly processed on the upload server, and the files should appear in the relevant download server with their correct digest (and in all mirrors, if any, setup for the same visibility level).&lt;br /&gt;
&lt;br /&gt;
The default email address used for these notifications is user@mozilla.com, where user is the user you use to access the upload server. If you want a different email address to be used for tooltool upload notifications, that will need to be added to the sync script configuration by somebody in releng.&lt;br /&gt;
&lt;br /&gt;
All metadata about the upload is stored in the upload server.&lt;br /&gt;
&lt;br /&gt;
= Tooltool uploads: the old school =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;This is the old-school, deprecated, manual way to upload artifacts to tooltool. Please use the official procedure described above whenever possible, in order to keep information about what is uploaded, by whom, and why (the manual procedure doesn&#039;t allow to store any metadata about uploads).&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you don&#039;t want to upload from your own laptop (because, eg, you have a slow uplink) you can do this from cruncher.&lt;br /&gt;
&lt;br /&gt;
Access cruncher with your credentials:&lt;br /&gt;
 ME=&amp;quot;your_short_ldap_username&amp;quot; # or `whoami`&lt;br /&gt;
 ssh -A $ME@cruncher.build.mozilla.org&lt;br /&gt;
Download the file and then:&lt;br /&gt;
 scp filename.tar.xz $ME@relengwebadm.private.scl3.mozilla.com:&lt;br /&gt;
Login to relengwebadmn:&lt;br /&gt;
 ssh $ME@relengwebadm.private.scl3.mozilla.com&lt;br /&gt;
And deploy the file to tooltool:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
FILE=~/emulator.zip # or whatever you&#039;re uploading&lt;br /&gt;
export SHA512=`openssl sha512 $FILE | cut -d&#039; &#039; -f2`&lt;br /&gt;
sudo mv -i $FILE /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}&lt;br /&gt;
sudo chmod 644  /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}&lt;br /&gt;
ls -l  /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Add the filename, filesize, and sha512 digest to the bug you are working on.  These can be added to the tooltool manifests later.&lt;br /&gt;
&lt;br /&gt;
= The tooltool sync script =&lt;br /&gt;
&lt;br /&gt;
For the curious, here is a description of what happens on the upload server once an upload is completed.&lt;br /&gt;
&lt;br /&gt;
As we saw so far, tooltool uploaders copy hashed files and manifests to their own upload folders - they have one for each &amp;quot;distribution type&amp;quot;, typically a pub one (to distribute files publicly) and a pvt one (for files to be available to mozilla employees only).&lt;br /&gt;
&lt;br /&gt;
The tooltool sync script serves the purpose of collecting all uploads from individual uploaders and aggregating them per distribution type (public, private), storing some metadata about the uploads themselves. It is supposed to run periodically via crontab to periodically pick new uploads and distribute their content.&lt;br /&gt;
&lt;br /&gt;
== Where is the sync script code? ==&lt;br /&gt;
&lt;br /&gt;
In the main tooltool repo: [https://github.com/mozilla/build-tooltool/blob/master/sync.py https://github.com/mozilla/build-tooltool/blob/master/sync.py]&lt;br /&gt;
&lt;br /&gt;
== Where is the sync script running? ==&lt;br /&gt;
&lt;br /&gt;
The sync scripts is located in /data/releng/src/tooltool/tooltool on relengwebadm.private.scl3.mozilla.com, where configuration (see below) and logs also live.&lt;br /&gt;
&lt;br /&gt;
== How do I deploy a new version of the sync script? ==&lt;br /&gt;
&lt;br /&gt;
Just grab the desired version from the github repo and copy it to the location where sync.py lives (see previous paragraph)&lt;br /&gt;
&lt;br /&gt;
== The sync script configuration ==&lt;br /&gt;
&lt;br /&gt;
The sync script needs a configuration file in json format named config.json, let&#039;s see an example here:&lt;br /&gt;
&lt;br /&gt;
  {&lt;br /&gt;
    &amp;quot;upload_root&amp;quot;: &amp;quot;/mnt/netapp/tooltool_uploads&amp;quot;,&lt;br /&gt;
    &amp;quot;target_folders&amp;quot;: {&amp;quot;pvt&amp;quot;: &amp;quot;/mnt/netapp/relengweb/tooltool/pvt/build/sha512&amp;quot;,&lt;br /&gt;
                       &amp;quot;pub&amp;quot;: &amp;quot;/mnt/netapp/relengweb/tooltool/pub/build/sha512&amp;quot;},&lt;br /&gt;
    &amp;quot;smtp_server&amp;quot;: &amp;quot;localhost&amp;quot;,&lt;br /&gt;
    &amp;quot;smtp_port&amp;quot;: 25,&lt;br /&gt;
    &amp;quot;user_email_mapping&amp;quot;: {&amp;quot;dmitchell&amp;quot;: &amp;quot;dustin@mozilla.com&amp;quot;},&lt;br /&gt;
    &amp;quot;default_domain&amp;quot;: &amp;quot;mozilla.com&amp;quot;,&lt;br /&gt;
    &amp;quot;smtp_from&amp;quot;: &amp;quot;no-reply@mozilla.org&amp;quot;&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;upload_root&#039;&#039;&#039; is the base directory in which all personal uploaders directories are located&lt;br /&gt;
* &#039;&#039;&#039;target_folders&#039;&#039;&#039; for each supported &amp;quot;distribution type&amp;quot; (in this case &amp;quot;pvt&amp;quot; and &amp;quot;pub&amp;quot;), the corresponding local destination folder (where all the files from different uploaders will be collected) is specified here&lt;br /&gt;
* &#039;&#039;&#039;smtp*&#039;&#039;&#039; will be used for notification emails to users after uploads&lt;br /&gt;
* &#039;&#039;&#039;default_domain&#039;&#039;&#039; is used to determine the email address of a user which is not explicitly mentioned in the &amp;quot;user_email_mapping&amp;quot; part: the address will be simply username@defaultdomain&lt;br /&gt;
&lt;br /&gt;
In the case of two uploaders, Alice and Bob; this is how the (tooltool) root folder will look like:&lt;br /&gt;
&lt;br /&gt;
  root&lt;br /&gt;
     alice&lt;br /&gt;
          pub&lt;br /&gt;
          pvt&lt;br /&gt;
     bob&lt;br /&gt;
          pub&lt;br /&gt;
            a-package.TOOLTOOL-PACKAGE               &lt;br /&gt;
            a_package.tt&lt;br /&gt;
            a_package.txt&lt;br /&gt;
          pvt&lt;br /&gt;
&lt;br /&gt;
Each user has two upload folders, one for each supported distribution type. The sync script supports an arbitrary number of distribution types, as far as they are defined in the configuration file in the matching section&lt;br /&gt;
&lt;br /&gt;
In its next execution, the sync script will detect the manifest, check that all referenced hash files are present, verify their integrity, and it will proceed copying the hashed files to the destination provided in the config file. Some upload metadata will be stored in text file.&lt;br /&gt;
&lt;br /&gt;
== The sync script in action ==&lt;br /&gt;
&lt;br /&gt;
[[File:Sync script in action.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
In more detail, the sync script will perform the following actions:&lt;br /&gt;
&lt;br /&gt;
=== Step 1: Copy of hash files to the appropriate destination ===&lt;br /&gt;
&lt;br /&gt;
All files mentioned in package_test1.tt manifest, in Bob&#039;s pub folder, will be hash checked and copied to the destination specified in the conf file (in this case, &amp;quot;/tooltool/servers/pub&amp;quot;). This will make the files available for tooltool downloads.&lt;br /&gt;
&lt;br /&gt;
Please note that in the following circumstances the copy will not occur:&lt;br /&gt;
&lt;br /&gt;
* if at least one of the files mentioned in the manifest are missing (for example in case of a partial upload)&lt;br /&gt;
* if at least one of the hashed files&#039; hashes are different from their filename (hash check failure)&lt;br /&gt;
&lt;br /&gt;
If one of these circumstances occur, the sync script will just log that it is impossible to process the given manifest and send a notification message to the uploader.&lt;br /&gt;
&lt;br /&gt;
=== Step 2: Store locally a copy of the processed manifest ===&lt;br /&gt;
&lt;br /&gt;
After processing a manifest, the sync script with store locally a copy of the processed manifest, prepending the user, the distribution type, and the processing timestamp to its name. The same will be done with the txt file containing comments (if any).&lt;br /&gt;
&lt;br /&gt;
In this example we will have a manifest stored locally (and a corresponding notes file) as&lt;br /&gt;
&lt;br /&gt;
  bob.pvt.2013_10_16-10.20.29.a-package.tt&lt;br /&gt;
  bob.pvt.2013_10_16-10.20.29.a-package.txt&lt;br /&gt;
&lt;br /&gt;
=== Step 3: Rename the processed manifests in the uploader folder as well ===&lt;br /&gt;
&lt;br /&gt;
The content of Bob&#039;s public folder after sync script processed its manifest will be the following:&lt;br /&gt;
&lt;br /&gt;
  /tooltool/uploads/bob/pvt&lt;br /&gt;
      2013_10_16-10.20.29.a-package.tt&lt;br /&gt;
      2013_10_16-10.20.29.a-package.txt&lt;br /&gt;
&lt;br /&gt;
The processed package has been deleted, and only the manifest with the corresponding note is present, with the processing timestamp; this means that the manifest has been successfully processed by the sync script.&lt;br /&gt;
&lt;br /&gt;
=== Step 4: Notify the uploader of success/failure ===&lt;br /&gt;
&lt;br /&gt;
An email will be sent to the uploader, notifying whether the sync process was completed succesfully or failed for some reasons.&lt;br /&gt;
If the sync process fails, the corresponding files will obviously not be available for tooltool downloads.&lt;br /&gt;
&lt;br /&gt;
= Need to download files from tooltool private server? =&lt;br /&gt;
If you want to download a file from tooltool private server and you&#039;re not part of ReleaseEngineering then add your name to {{bug|1019011}}.&lt;br /&gt;
&lt;br /&gt;
That should grant you access to https://secure.pub.build.mozilla.org/tooltool/pvt/build&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Tools/Data_Sources_and_Tools_for_FxOS_Perfomance_Optimization&amp;diff=994495</id>
		<title>Firefox OS/Performance/Tools/Data Sources and Tools for FxOS Perfomance Optimization</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Tools/Data_Sources_and_Tools_for_FxOS_Perfomance_Optimization&amp;diff=994495"/>
		<updated>2014-07-03T16:35:59Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Good performance data is necessary for developers to optimize, debug regressions, and to learn the best practices for developing on our platform.  Therefore it is essential that the Firefox OS Performance team take a look at all of the available performance related data to identify what we have to work with right now and what other performance data we should work to expose in the future.&lt;br /&gt;
&lt;br /&gt;
==Performance Data Sources==&lt;br /&gt;
&lt;br /&gt;
Below is a list of all of the performance data sources we would like to expose to app developers to help with optimization.&lt;br /&gt;
&lt;br /&gt;
===Memory===&lt;br /&gt;
* Global memory usage.&lt;br /&gt;
* Per-process memory usage broken down into USS, RSS, JS objects, etc.&lt;br /&gt;
* GC events.&lt;br /&gt;
* Any relavent GC stats (e.g. how much memory is each generation group).&lt;br /&gt;
* OOM pressure events.&lt;br /&gt;
* OOM killer nice adjustment events.&lt;br /&gt;
&lt;br /&gt;
===Processes===&lt;br /&gt;
* Main thread stalls (i.e. jank).&lt;br /&gt;
* App startup sequence events.&lt;br /&gt;
* Arbitrary &amp;quot;debug&amp;quot; events from content JS.&lt;br /&gt;
* I/O events (e.g. file load start, file load end).&lt;br /&gt;
* Network utilization (upload and download).&lt;br /&gt;
&lt;br /&gt;
===Javascript===&lt;br /&gt;
* JS parse start and end.&lt;br /&gt;
* JS JIT start and end, both baseline and ion.&lt;br /&gt;
* JS JIT bailouts.&lt;br /&gt;
* JS JIT warnings/errors (i.e. JS code from line X to Y has unstable type flow).&lt;br /&gt;
* JS IC invalidations.&lt;br /&gt;
* Globals objects mutation events and what is mutating the object.  (Useful for debugging improper global state mutation bugs).&lt;br /&gt;
* JS function execution tracing.&lt;br /&gt;
&lt;br /&gt;
===Graphics===&lt;br /&gt;
* Layering data.&lt;br /&gt;
* Reflow events.&lt;br /&gt;
* GPU memory information.&lt;br /&gt;
* Frame rate.&lt;br /&gt;
* Frame uniformity (i.e. project butter).&lt;br /&gt;
* Vsync events.&lt;br /&gt;
&lt;br /&gt;
===Hardware===&lt;br /&gt;
* Luminosity.&lt;br /&gt;
* Acceleration.&lt;br /&gt;
* Orientation.&lt;br /&gt;
* Motion.&lt;br /&gt;
* GPS status.&lt;br /&gt;
* GPS coordinates.&lt;br /&gt;
* Bluetooth events.&lt;br /&gt;
* USB events.&lt;br /&gt;
* Touch event latency.&lt;br /&gt;
* Touch events.&lt;br /&gt;
* RIL events.&lt;br /&gt;
* Call start latency.&lt;br /&gt;
* WebRTC video and audio statistics.&lt;br /&gt;
* NFC.&lt;br /&gt;
&lt;br /&gt;
===Data Collection===&lt;br /&gt;
&lt;br /&gt;
Currently, Firefox OS posesses the ability to report out a number of performance related statistics in realtime.  Figure 1 illustrates the current organization of the data gathering and expropriation.&lt;br /&gt;
&lt;br /&gt;
[[File:OnDeviceInstrumentation.png|800px]]&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Figure 1&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is gathered by a set of observers that watch for events/changes in their respective performance areas and then report the changed stats via the observe message system.  The sampling profiler and the child process actors set up observers to receive these events.  The other main source of data is the memory sub-system which is polled by both the profiler and child actors to get memory statistics for each process.&lt;br /&gt;
&lt;br /&gt;
The child process actors handle sending all of the performance data to the parent process actors which forward the data over the remote debugging protocol to the connected host PC.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Tools/Data_Sources_and_Tools_for_FxOS_Perfomance_Optimization&amp;diff=994485</id>
		<title>Firefox OS/Performance/Tools/Data Sources and Tools for FxOS Perfomance Optimization</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Tools/Data_Sources_and_Tools_for_FxOS_Perfomance_Optimization&amp;diff=994485"/>
		<updated>2014-07-03T16:19:00Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Hardware */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Good performance data is necessary for developers to optimize, debug regressions, and to learn the best practices for developing on our platform.  Therefore it is essential that the Firefox OS Performance team take a look at all of the available performance related data to identify what we have to work with right now and what other performance data we should work to expose in the future.&lt;br /&gt;
&lt;br /&gt;
==Performance Data Sources==&lt;br /&gt;
&lt;br /&gt;
Below is a list of all of the performance data sources we would like to expose to app developers to help with optimization.&lt;br /&gt;
&lt;br /&gt;
===Memory===&lt;br /&gt;
* Global memory usage.&lt;br /&gt;
* Per-process memory usage broken down into USS, RSS, JS objects, etc.&lt;br /&gt;
* GC events.&lt;br /&gt;
* Any relavent GC stats (e.g. how much memory is each generation group).&lt;br /&gt;
* OOM pressure events.&lt;br /&gt;
* OOM killer nice adjustment events.&lt;br /&gt;
&lt;br /&gt;
===Processes===&lt;br /&gt;
* Main thread stalls (i.e. jank).&lt;br /&gt;
* App startup sequence events.&lt;br /&gt;
* Arbitrary &amp;quot;debug&amp;quot; events from content JS.&lt;br /&gt;
* I/O events (e.g. file load start, file load end).&lt;br /&gt;
* Network utilization (upload and download).&lt;br /&gt;
&lt;br /&gt;
===Javascript===&lt;br /&gt;
* JS parse start and end.&lt;br /&gt;
* JS JIT start and end, both baseline and ion.&lt;br /&gt;
* JS JIT bailouts.&lt;br /&gt;
* JS JIT warnings/errors (i.e. JS code from line X to Y has unstable type flow).&lt;br /&gt;
* JS IC invalidations.&lt;br /&gt;
* Globals objects mutation events and what is mutating the object.  (Useful for debugging improper global state mutation bugs).&lt;br /&gt;
* JS function execution tracing.&lt;br /&gt;
&lt;br /&gt;
===Graphics===&lt;br /&gt;
* Layering data.&lt;br /&gt;
* Reflow events.&lt;br /&gt;
* GPU memory information.&lt;br /&gt;
* Frame rate.&lt;br /&gt;
* Frame uniformity (i.e. project butter).&lt;br /&gt;
* Vsync events.&lt;br /&gt;
&lt;br /&gt;
===Hardware===&lt;br /&gt;
* Luminosity.&lt;br /&gt;
* Acceleration.&lt;br /&gt;
* Orientation.&lt;br /&gt;
* Motion.&lt;br /&gt;
* GPS status.&lt;br /&gt;
* GPS coordinates.&lt;br /&gt;
* Bluetooth events.&lt;br /&gt;
* USB events.&lt;br /&gt;
* Touch event latency.&lt;br /&gt;
* Touch events.&lt;br /&gt;
* Call start latency.&lt;br /&gt;
* WebRTC video and audio statistics.&lt;br /&gt;
&lt;br /&gt;
===Data Collection===&lt;br /&gt;
&lt;br /&gt;
Currently, Firefox OS posesses the ability to report out a number of performance related statistics in realtime.  Figure 1 illustrates the current organization of the data gathering and expropriation.&lt;br /&gt;
&lt;br /&gt;
[[File:OnDeviceInstrumentation.png|800px]]&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Figure 1&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is gathered by a set of observers that watch for events/changes in their respective performance areas and then report the changed stats via the observe message system.  The sampling profiler and the child process actors set up observers to receive these events.  The other main source of data is the memory sub-system which is polled by both the profiler and child actors to get memory statistics for each process.&lt;br /&gt;
&lt;br /&gt;
The child process actors handle sending all of the performance data to the parent process actors which forward the data over the remote debugging protocol to the connected host PC.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Tools/Data_Sources_and_Tools_for_FxOS_Perfomance_Optimization&amp;diff=994484</id>
		<title>Firefox OS/Performance/Tools/Data Sources and Tools for FxOS Perfomance Optimization</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Tools/Data_Sources_and_Tools_for_FxOS_Perfomance_Optimization&amp;diff=994484"/>
		<updated>2014-07-03T16:14:53Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* Processes */ s/Network bandwidth/Network utilization (upload and download)/&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
Good performance data is necessary for developers to optimize, debug regressions, and to learn the best practices for developing on our platform.  Therefore it is essential that the Firefox OS Performance team take a look at all of the available performance related data to identify what we have to work with right now and what other performance data we should work to expose in the future.&lt;br /&gt;
&lt;br /&gt;
==Performance Data Sources==&lt;br /&gt;
&lt;br /&gt;
Below is a list of all of the performance data sources we would like to expose to app developers to help with optimization.&lt;br /&gt;
&lt;br /&gt;
===Memory===&lt;br /&gt;
* Global memory usage.&lt;br /&gt;
* Per-process memory usage broken down into USS, RSS, JS objects, etc.&lt;br /&gt;
* GC events.&lt;br /&gt;
* Any relavent GC stats (e.g. how much memory is each generation group).&lt;br /&gt;
* OOM pressure events.&lt;br /&gt;
* OOM killer nice adjustment events.&lt;br /&gt;
&lt;br /&gt;
===Processes===&lt;br /&gt;
* Main thread stalls (i.e. jank).&lt;br /&gt;
* App startup sequence events.&lt;br /&gt;
* Arbitrary &amp;quot;debug&amp;quot; events from content JS.&lt;br /&gt;
* I/O events (e.g. file load start, file load end).&lt;br /&gt;
* Network utilization (upload and download).&lt;br /&gt;
&lt;br /&gt;
===Javascript===&lt;br /&gt;
* JS parse start and end.&lt;br /&gt;
* JS JIT start and end, both baseline and ion.&lt;br /&gt;
* JS JIT bailouts.&lt;br /&gt;
* JS JIT warnings/errors (i.e. JS code from line X to Y has unstable type flow).&lt;br /&gt;
* JS IC invalidations.&lt;br /&gt;
* Globals objects mutation events and what is mutating the object.  (Useful for debugging improper global state mutation bugs).&lt;br /&gt;
* JS function execution tracing.&lt;br /&gt;
&lt;br /&gt;
===Graphics===&lt;br /&gt;
* Layering data.&lt;br /&gt;
* Reflow events.&lt;br /&gt;
* GPU memory information.&lt;br /&gt;
* Frame rate.&lt;br /&gt;
* Frame uniformity (i.e. project butter).&lt;br /&gt;
* Vsync events.&lt;br /&gt;
&lt;br /&gt;
===Hardware===&lt;br /&gt;
* Luminosity.&lt;br /&gt;
* Acceleration.&lt;br /&gt;
* Orientation.&lt;br /&gt;
* GPS status.&lt;br /&gt;
* GPS coordinates.&lt;br /&gt;
* Bluetooth events.&lt;br /&gt;
* USB events.&lt;br /&gt;
* Touch event latency.&lt;br /&gt;
* Touch events.&lt;br /&gt;
* Call start latency.&lt;br /&gt;
* WebRTC video and audio statistics.&lt;br /&gt;
&lt;br /&gt;
===Data Collection===&lt;br /&gt;
&lt;br /&gt;
Currently, Firefox OS posesses the ability to report out a number of performance related statistics in realtime.  Figure 1 illustrates the current organization of the data gathering and expropriation.&lt;br /&gt;
&lt;br /&gt;
[[File:OnDeviceInstrumentation.png|800px]]&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Figure 1&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is gathered by a set of observers that watch for events/changes in their respective performance areas and then report the changed stats via the observe message system.  The sampling profiler and the child process actors set up observers to receive these events.  The other main source of data is the memory sub-system which is polled by both the profiler and child actors to get memory statistics for each process.&lt;br /&gt;
&lt;br /&gt;
The child process actors handle sending all of the performance data to the parent process actors which forward the data over the remote debugging protocol to the connected host PC.&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Fosdem:2014:Attendees&amp;diff=911376</id>
		<title>Fosdem:2014:Attendees</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Fosdem:2014:Attendees&amp;diff=911376"/>
		<updated>2014-01-30T23:05:04Z</updated>

		<summary type="html">&lt;p&gt;Janx: added myself&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Gervase Markham&lt;br /&gt;
* Delphine Lebédel&lt;br /&gt;
* Ziggy Maes&lt;br /&gt;
* Monique Brunel&lt;br /&gt;
* Antoine Duparay / Flaburgan&lt;br /&gt;
* Flore Allemandou&lt;br /&gt;
* Dirkjan Ochtman&lt;br /&gt;
* Francisco Picolini&lt;br /&gt;
* Redon Skikuli&lt;br /&gt;
* Elio Qoshi&lt;br /&gt;
* Giannis Konstantinidis&lt;br /&gt;
* Valentin Gosu&lt;br /&gt;
* Stephen John Murphy&lt;br /&gt;
* Alfredos-Panagiotis Damkalis&lt;br /&gt;
* Claire Corgnou&lt;br /&gt;
* Sara Prussak&lt;br /&gt;
* William Duyck&lt;br /&gt;
* Ashickur Rahman&lt;br /&gt;
* Sayak Sarkar&lt;br /&gt;
* Eduardo Urcullú Madrid&lt;br /&gt;
* Soumya Deb&lt;br /&gt;
* Priyanka Nag&lt;br /&gt;
* Srikar Ananthula&lt;br /&gt;
* Axel Hecht&lt;br /&gt;
* Pascal Chevrel&lt;br /&gt;
* Arky&lt;br /&gt;
* Henrik Skupin&lt;br /&gt;
* Dwayne Bailey&lt;br /&gt;
* Adrian Kalla&lt;br /&gt;
* Tomer Cohen&lt;br /&gt;
* Soumya Kanti Chakraborty&lt;br /&gt;
* Sébastien Desvignes&lt;br /&gt;
* Fabien Cazenave (Kazé)&lt;br /&gt;
* Paul Adenot&lt;br /&gt;
* Sylvestre Ledru&lt;br /&gt;
* Mathieu Goessens&lt;br /&gt;
* Anthony Maton&lt;br /&gt;
* Jan Keromnes&lt;br /&gt;
&lt;br /&gt;
See also the list of attendees on ReMo: https://reps.mozilla.org/e/fosdem-2014/&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Identity/Firefox_Accounts&amp;diff=904953</id>
		<title>Identity/Firefox Accounts</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Identity/Firefox_Accounts&amp;diff=904953"/>
		<updated>2014-01-24T16:57:48Z</updated>

		<summary type="html">&lt;p&gt;Janx: /* What Is Firefox Accounts? */ add missing word &amp;quot;a&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{LastUpdated}}&lt;br /&gt;
&lt;br /&gt;
=What Is Firefox Accounts? =&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts is a consumer account system which provides access to services run by Mozilla, such as [https://marketplace.firefox.com/ Firefox Marketplace] and the [https://wiki.mozilla.org/User_Services/Sync next version of Firefox Sync]. A user can sign in with a Firefox Account to all her &amp;quot;Foxes&amp;quot;: Firefox on Desktop, Firefox for Android, and Firefox OS. Signing into a Firefox browser or device gives the user access to integrated Mozilla Services on that browser or device that requires authentication (e.g., Firefox Sync). Longer term we envision that non-Mozilla services and applications will be able to delegate authentication to Firefox Accounts.&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts from a literal, technical perspective is not much to look at. It&#039;s a thin service that does only a few things, e.g.,&lt;br /&gt;
&lt;br /&gt;
* It allows users to create a Firefox Account. &lt;br /&gt;
* It allows existing account holders to authenticate themselves, and perform related operations (reset password, change password, etc.)&lt;br /&gt;
* It provides a delegated authentication API to relying Mozilla services (possibly third services in the future). Just like how Google Drive delegates authentication to Google Accounts, Firefox Marketplace will delegate authentication to Firefox Accounts. &lt;br /&gt;
&lt;br /&gt;
Firefox Accounts itself doesn&#039;t store much about users, and we intend to keep it that way:&lt;br /&gt;
&lt;br /&gt;
* Email address&lt;br /&gt;
* Password verifier&lt;br /&gt;
* User id&lt;br /&gt;
* Sync encryption keys&lt;br /&gt;
* Whether the user has accepted the ToS and PP&lt;br /&gt;
* A log of security events about the user (from where and when logins, passwords resets, etc. happen), and from what devices the user is currently logged in.&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts on it&#039;s own is boring and useless. Firefox Accounts is only interesting and valuable when you start attaching services to it, like Firefox Marketplace, Where&#039;s My Fox, and Firefox Sync. These services will manage their own data, but rely on Firefox Accounts for single sign-on and related authentication services.&lt;br /&gt;
&lt;br /&gt;
=FAQ=&lt;br /&gt;
&lt;br /&gt;
== Will I be required to create a Firefox Account to use Firefox? ==&lt;br /&gt;
&lt;br /&gt;
No, of course not! Firefox Accounts will only be required for Mozilla Services that require authentication, such as Firefox Sync and Firefox Marketplace.&lt;br /&gt;
&lt;br /&gt;
==How does a user create and sign in to a Firefox Account?==&lt;br /&gt;
Firefox Accounts will work much like authentication works just about everywhere else. You create a Firefox Account with a verified email and password. You sign in to Firefox Accounts with your email and password. We are currently evaluating creating and logging in to a Firefox Account with a mobile number.&lt;br /&gt;
&lt;br /&gt;
==Why does Firefox Accounts require me to choose a password?==&lt;br /&gt;
The first relying service we&#039;re targeting with Firefox Accounts is Firefox Sync. Current Firefox Sync encrypts all your data in our servers, and we will continue to do so in the Firefox Accounts backed version of Sync. However, in the FxA backed version of Firefox Sync, we will encrypt your Sync data with a key derived from your Firefox Account password, instead a random key managed by the J-PAKE pairing protocol. This technique of using a password derived sync key is similar to how data protection in [https://support.google.com/chrome/answer/1181035?hl=en&amp;amp;ref_topic=1693469 Chrome Sync] works.&lt;br /&gt;
&lt;br /&gt;
==What is the UX for signing in to a Firefox Account?==&lt;br /&gt;
NOTE: This is a work in progress!&lt;br /&gt;
&lt;br /&gt;
Here are some Lucidchart flow diagrams for FxA: https://www.lucidchart.com/documents/edit/4f34-ef24-52695ddf-8057-72580a00d543&lt;br /&gt;
===Web===&lt;br /&gt;
We anticipate the majority of Firefox Account sign ins and account creations will be driven by flows from Mozilla relying services, such as Firefox Marketplace. We propose relying Mozilla services present account controls and signal the FxA logged in state in the upper right corner of their Web properties:&lt;br /&gt;
&lt;br /&gt;
[[File:Sign-in.png|400px]]&lt;br /&gt;
&lt;br /&gt;
If a user clicks on the &amp;quot;Sign Up&amp;quot; or &amp;quot;Log In&amp;quot; button, it will take her to to a FxA page that will allow her to sign in or create an account. After completing sign in or account creation, she will be redirected back to the relying Mozilla service.&lt;br /&gt;
&lt;br /&gt;
===FxOS===&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
==How do relying Mozilla services authenticate an FxA user?==&lt;br /&gt;
Great question. We&#039;re still working out the details. We&#039;re first going to figure out the [https://wiki.mozilla.org/Identity/Firefox_Accounts/SSO product requirements of SSO with FxA] and go from there.&lt;br /&gt;
&lt;br /&gt;
==How does a user reset her Firefox Account password?==&lt;br /&gt;
Password reset works by responding to an email challenge.&lt;br /&gt;
&lt;br /&gt;
==What&#039;s the difference between Persona and Firefox Accounts?==&lt;br /&gt;
Persona is not intended to provide you with a new account, and it&#039;s not a new account system. Persona is a federated login protocol. You use Persona to log in to relying sites, and it&#039;s not intended that you need to &amp;quot;sign up&amp;quot; for Persona before you can use it. If you would need to sign up for anything, you would need to create an account at an IdP that supports Persona.&lt;br /&gt;
&lt;br /&gt;
One *huge* confusing point about Persona today is a service called the &amp;quot;Persona Fallback&amp;quot;, which serves as a proxy IdP if your actual IdP doesn&#039;t support Persona (or isn&#039;t bridged), which just about every IdP except for Google and Yahoo. In this case, you currently have to sign up for a &amp;quot;Persona Fallback Account&amp;quot; (i.e. choose a password and verify your email) to use Persona. &lt;br /&gt;
&lt;br /&gt;
But a Persona Fallback Account is not a Persona Account, it&#039;s not the long term vision of Persona, and that&#039;s not supposed to be the happy path of the Persona login experience. &lt;br /&gt;
&lt;br /&gt;
More importantly, for the purposes of this question, a Persona Fallback Account is definitely not a Firefox Account.&lt;br /&gt;
&lt;br /&gt;
So why Firefox Accounts and what will one do?&lt;br /&gt;
&lt;br /&gt;
Mozilla needs an account database to deliver a fantastic, integrated experience across all its products. Unfortunately, delivering awesome services involves some less exciting, but still important aspects, like making sure users have had a chance to inspect our terms of service and privacy policies. We must also comply with local laws and regulations, e.g., [http://www.coppa.org/ COPPA]. It would be inconvenient for users to have to verify a terms of service, a privacy policy, and COPPA at each individual Mozilla service. We believe that users should only have to inspect our terms of service, privacy policy, and go through COPPA verification &#039;&#039;&#039;once&#039;&#039;&#039; for all our services. Firefox Accounts enables us to do that. One we get the basics down and enable single sign-on for relying Mozilla Services with your Firefox Account, we hope integrate Firefox Accounts with Persona on the Web and Firefox user agents to make logging in everywhere as painless as it should be.&lt;br /&gt;
&lt;br /&gt;
== What information does Firefox Accounts store about the user? Can I use it to store user data for my application or service? ==&lt;br /&gt;
Firefox Accounts stores limited user information, and only stores information that will deliver significant user value across applications or is tightly related to the user&#039;s identity. It will not store user data for relying services. Relying Mozilla services can use Firefox Accounts for authentication, but application data storage is the responsibility of the individual applications.&lt;br /&gt;
&lt;br /&gt;
Currently, Firefox Accounts stores the user&#039;s email address, a unique identifier, sync encryption key material, and whether you user has read and accepted the terms of service, privacy policy, etc. The existence of a Firefox Account also indicates the user has passed COPPA verification.&lt;br /&gt;
&lt;br /&gt;
Possible future plans:&lt;br /&gt;
* &amp;quot;screen name&amp;quot;&lt;br /&gt;
* avatar&lt;br /&gt;
* mobile number&lt;br /&gt;
&lt;br /&gt;
== Can I use Persona to log in to my Firefox Account? ==&lt;br /&gt;
Not initially, but it&#039;s something we&#039;re investigating to add in the future.&lt;br /&gt;
&lt;br /&gt;
== Can I use my Firefox Account to log in to non-Mozilla services? ==&lt;br /&gt;
Not initially, but it&#039;s something we&#039;re investigating to support in the future.&lt;br /&gt;
&lt;br /&gt;
== Does Firefox Accounts provide email? ==&lt;br /&gt;
No.&lt;br /&gt;
&lt;br /&gt;
== What services will use Firefox Accounts? ==&lt;br /&gt;
Here&#039;s a (probably incomplete) list of services we anticipate you&#039;ll be able to log into with your Firefox Account:&lt;br /&gt;
* Firefox Sync&lt;br /&gt;
* Firefox Marketplace&lt;br /&gt;
* Where&#039;s My Fox?&lt;br /&gt;
* [https://wiki.mozilla.org/User:Dria/PiCL_Future_Ideas crazy future ideas]&lt;br /&gt;
&lt;br /&gt;
== What do these terms mean? ==&lt;br /&gt;
* FTU, FTE: First Time Experience on Firefox OS&lt;br /&gt;
* FxA : Firefox Accounts. It may also refer to a user&#039;s particular Firefox Account.&lt;br /&gt;
* Jelly: A confusing term that refers to a hosted web page that is injected into more native-looking browser UI. An example of this is about:healthreport.&lt;br /&gt;
* Doughnut: The browser code that wraps the &amp;quot;Jelly&amp;quot; and enables it to interact with chrome code in the browser. &lt;br /&gt;
* RP : Relying Party. Services that use Firefox Accounts for authentication and identity. Currently these are limited to services run by Mozilla.&lt;br /&gt;
* PiCL : Profile in the Cloud. This is a deprecated term that was used to refer to Firefox Accounts + attached services (i.e., relying parties).&lt;br /&gt;
&lt;br /&gt;
== Where is the schedule for FxA? ==&lt;br /&gt;
https://wiki.mozilla.org/Identity/Roadmap&lt;br /&gt;
&lt;br /&gt;
== Where is the FxA for Web addition to the Arch section below? ==&lt;br /&gt;
&lt;br /&gt;
== What are the similarities/differences between FxA for Web and the Dev work already being done for desktop and android? ==&lt;br /&gt;
&lt;br /&gt;
== Have a question not covered here? Add it in this section and we&#039;ll answer it! ==&lt;br /&gt;
&lt;br /&gt;
=Architecture=&lt;br /&gt;
[[File:Firefox_Accounts_Architecture.png]]&lt;br /&gt;
&lt;br /&gt;
https://mana.mozilla.org/wiki/display/services/Firefox+Accounts+Architecture&lt;br /&gt;
&lt;br /&gt;
== Cloud Services ==&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts Cloud Services is composed of several sub-services, an &#039;&#039;&#039;auth server&#039;&#039;&#039;, a &#039;&#039;&#039;content server&#039;&#039;&#039;, and a &#039;&#039;&#039;crypto helper&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=== Auth Server ===&lt;br /&gt;
&lt;br /&gt;
The Auth Server provides an HTTP API that:&lt;br /&gt;
&lt;br /&gt;
* authenticates the user&lt;br /&gt;
* enables the user to authenticate to other services via BrowserID assertions&lt;br /&gt;
* enables change and reset password operations&lt;br /&gt;
&lt;br /&gt;
Links:&lt;br /&gt;
* Code: https://github.com/mozilla/fxa-auth-server&lt;br /&gt;
* API documentation: https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md&lt;br /&gt;
* API design document: [[Identity/AttachedServices/KeyServerProtocol]]&lt;br /&gt;
* Dev deployment: https://github.com/mozilla/fxa-auth-server#dev-deployment&lt;br /&gt;
* Python API client (primarily a reference client): https://github.com/warner/picl-spec-crypto&lt;br /&gt;
&lt;br /&gt;
=== Content Server ===&lt;br /&gt;
&lt;br /&gt;
The Content Server hosts static assets (HTML, Javascript, CSS, etc.) that support user interactions with the Firefox Accounts. The responsibilities of the Content Server include:&lt;br /&gt;
&lt;br /&gt;
* hosting Gherkin, a Javascript library that supports interactions with the Auth Server&lt;br /&gt;
* hosting login and create account pages&lt;br /&gt;
* hosting password reset pages&lt;br /&gt;
* hosting landing pages for email verification links&lt;br /&gt;
&lt;br /&gt;
Links:&lt;br /&gt;
* Code: https://github.com/mozilla/fxa-content-server&lt;br /&gt;
* Deployments: &lt;br /&gt;
** dev stable: https://accounts.dev.lcip.org/&lt;br /&gt;
** dev latest: https://accounts.dev.lcip.org/&lt;br /&gt;
** prod: https://accounts.firefox.com/&lt;br /&gt;
&lt;br /&gt;
=== JS Client Library ===&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts provides a Javascript client library for the Web that supports operations with Firefox Accounts. In addition to communicating with the Auth Server, it also performs local key stretching (PBKDF2 and scrypt) on the user&#039;s password before it&#039;s used in the API. It is hosted by the Content Server. This library was at one time called &amp;quot;Gherkin&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Links:&lt;br /&gt;
* Code: https://github.com/mozilla/fxa-js-client-old&lt;br /&gt;
* Future rewrite: https://github.com/mozilla/fxa-js-client&lt;br /&gt;
* Key stretching details: https://wiki.mozilla.org/Identity/AttachedServices/KeyServerProtocol#Client-Side_Key_Stretching&lt;br /&gt;
* Key stretching performance tests: https://wiki.mozilla.org/Identity/AttachedServices/Key_Stretching_Performance_Tests&lt;br /&gt;
&lt;br /&gt;
=== scrypt Helper ===&lt;br /&gt;
&lt;br /&gt;
A portion of the key stretching process uses [http://en.wikipedia.org/wiki/Scrypt scrypt], a password-based key derivation function that uses significant amounts of memory. On memory constrained devices, Firefox Accounts provides a helper service for this portion of the key stretching process.&lt;br /&gt;
&lt;br /&gt;
Links:&lt;br /&gt;
* Code: https://github.com/mozilla/fxa-scrypt-helper&lt;br /&gt;
* Dev deployment: https://scrypt-accounts.dev.lcip.org/&lt;br /&gt;
&lt;br /&gt;
=== Verifier ===&lt;br /&gt;
&lt;br /&gt;
FxA will host its own BID verifier for relying Mozilla service to verify the assertions FxA generates. The reason is that the &amp;lt;code&amp;gt;principal&amp;lt;/code&amp;gt; will be &amp;lt;code&amp;gt;{ email: &amp;lt;user&#039;s real email&amp;gt;, uid: &amp;lt;FxA user id&amp;gt; }&amp;lt;/code&amp;gt;, which is not BID-kosher.&lt;br /&gt;
&lt;br /&gt;
Update (11/14/13): A separate verifier is currently off the table. The proposal is to use the current verifier, with some changes.&lt;br /&gt;
Update (11/15/13): it sure seems like it is back on the table. Can someone confirm?&lt;br /&gt;
&lt;br /&gt;
Discussion:&lt;br /&gt;
* https://github.com/mozilla/fxa-auth-server/issues/292&lt;br /&gt;
* https://github.com/mozilla/fxa-auth-server/pull/275&lt;br /&gt;
* https://groups.google.com/forum/#!topic/mozilla.dev.identity/1ecTUrOFzbQ&lt;br /&gt;
&lt;br /&gt;
== Desktop ==&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts integration on Firefox for Desktop is happening in the [https://tbpl.mozilla.org/?tree=Elm &amp;quot;elm&amp;quot; project branch]. We are also working out of a [https://github.com/mhammond/mozilla-central/tree/experiment/elm-fxaccount-sync github repo] for &amp;quot;pre-elm&amp;quot; experimentation.&lt;br /&gt;
&lt;br /&gt;
Tracking bug:&lt;br /&gt;
* https://bugzilla.mozilla.org/showdependencytree.cgi?id=905997&amp;amp;hide_resolved=1&lt;br /&gt;
&lt;br /&gt;
== Android  ==&lt;br /&gt;
&lt;br /&gt;
Firefox Accounts integration on Firefox for Android is happening in the [https://tbpl.mozilla.org/?tree=Elm &amp;quot;elm&amp;quot; project branch].&lt;br /&gt;
&lt;br /&gt;
Tracking bug:&lt;br /&gt;
* https://bugzilla.mozilla.org/showdependencytree.cgi?id=799726&amp;amp;hide_resolved=1&lt;br /&gt;
&lt;br /&gt;
==  Firefox OS ==&lt;br /&gt;
Implementation of Firefox Accounts in FirefoxOS is committed for b2g v1.4.  This is a collaborative effort working closely with TEF and Telenor engineers. &lt;br /&gt;
&lt;br /&gt;
Demo:&lt;br /&gt;
* https://vimeo.com/79618371&lt;br /&gt;
&lt;br /&gt;
Tracking bug:&lt;br /&gt;
* https://bugzilla.mozilla.org/showdependencytree.cgi?id=941723&amp;amp;hide_resolved=1&lt;br /&gt;
&lt;br /&gt;
Our current line of thought is below and a work-in-progress:&lt;br /&gt;
* UX: https://wiki.mozilla.org/Identity/UX#FXOS&lt;br /&gt;
* https://github.com/SamPenrose/fxa-fxos/blob/master/dependencies.md&lt;br /&gt;
&lt;br /&gt;
===Tracking===&lt;br /&gt;
&amp;lt;onlyinclude&amp;gt;&lt;br /&gt;
&amp;lt;bugzilla&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;blocks&amp;quot;: &amp;quot;941723&amp;quot;,&lt;br /&gt;
    &amp;quot;resolution&amp;quot;: &amp;quot;---&amp;quot;,&lt;br /&gt;
    &amp;quot;include_fields&amp;quot;: &amp;quot;id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/bugzilla&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Operations ==&lt;br /&gt;
For now, here are some useful links about Firefox Accounts Operations:&lt;br /&gt;
* Q3 load testing results: https://id.etherpad.mozilla.org/fxa-q3-load-testing-summary&lt;br /&gt;
* Deployment planning: https://wiki.mozilla.org/Identity/AttachedServices/DeploymentPlanning/&lt;br /&gt;
* Traffic model: https://wiki.mozilla.org/Identity/AttachedServices/DeploymentPlanning/TrafficModel&lt;br /&gt;
* Notes on the operational costs of the Auth Server: https://mail.mozilla.org/pipermail/sync-dev/2013-July/000043.html&lt;br /&gt;
&lt;br /&gt;
=== Deployments ===&lt;br /&gt;
* production (proposed) https://github.com/mozilla/fxa-auth-server/issues/295#issuecomment-28614668&lt;br /&gt;
* stage (proposed): https://github.com/mozilla/fxa-auth-server/issues/295#issuecomment-28725360&lt;br /&gt;
* dev:&lt;br /&gt;
** Auth server: https://api-accounts.dev.lcip.org&lt;br /&gt;
** Auth server (auto-pushed from master): https://api-accounts-latest.dev.lcip.org/&lt;br /&gt;
** Content server: https://accounts.dev.lcip.org/flow&lt;br /&gt;
** Scrypt helper: https://scrypt-accounts.dev.lcip.org&lt;br /&gt;
&lt;br /&gt;
== Metrics ==&lt;br /&gt;
https://wiki.mozilla.org/Identity/Firefox_Accounts/Minimum_Viable_Metrics&lt;br /&gt;
&lt;br /&gt;
== Fraud and Abuse ==&lt;br /&gt;
https://id.etherpad.mozilla.org/fxacct-metrics-fraud-detection&lt;br /&gt;
&lt;br /&gt;
=Resources=&lt;br /&gt;
&lt;br /&gt;
== Mailing Lists ==&lt;br /&gt;
* Firefox Accounts development: https://mail.mozilla.org/listinfo/dev-fxacct&lt;br /&gt;
* Sync development: https://mail.mozilla.org/listinfo/sync-dev&lt;br /&gt;
&lt;br /&gt;
{{FxA Team}}&lt;br /&gt;
&lt;br /&gt;
== Related ==&lt;br /&gt;
* [https://wiki.mozilla.org/Identity/Roadmap Identity Roadmap]&lt;br /&gt;
* [https://wiki.mozilla.org/User_Services/Sync Firefox Sync.next]&lt;br /&gt;
* [https://wiki.mozilla.org/Identity/PiCL Identity and PiCL]&lt;br /&gt;
* [https://wiki.mozilla.org/Identity/UX FxA UX/UI]&lt;br /&gt;
* [https://wiki.mozilla.org/QA/Services/SyncTestPlanV1 QA Team Test Plan]&lt;br /&gt;
* [https://wiki.mozilla.org/Identity/WhatDoesFxAMeanToYou What Does Firefox Accounts Mean To You?]&lt;br /&gt;
&lt;br /&gt;
== Demos ==&lt;br /&gt;
* Firefox Accounts + Firefox Sync on Android: https://vimeo.com/77667079&lt;br /&gt;
* Firefox Accounts + Firefox Sync on Desktop: https://vimeo.com/77717494&lt;/div&gt;</summary>
		<author><name>Janx</name></author>
	</entry>
</feed>