Changes

Jump to: navigation, search

Telemetry/Experiments

22 bytes removed, 14:48, 18 September 2015
clean up docs
=== Repository and Reviews ===
Experiments must be developed in the public [http://hg.mozilla.org/webtools/telemetry-experiment-server telemetry experiment server] source repository and must be reviewed just as if they were part of Firefox on mozilla-central. If an experiment adds special data collection, that data collection must be [[Firefox/Data Collection|documented and reviewed]] as normal.
To request reviews, file a bug against the [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20Health%20Report&component=Client%3A%20Desktop Firefox Health Report product, Desktop Client component].
Unlike other restartless extensions, experiments must have a top-level <code>manifest.json</code> file. The <code>manifest.json</code> format is not currently documented, though examples can be found by looking at past experiments [http://hg.mozilla.org/webtools/telemetry-experiment-server in the telemetry-experiment-server mercurial repo].
In particular, note that the <code>name</code> field is visible to end users, so it should be  === <code>DOCUMENTATION</code> file === A DOCUMENTATION file must be included with the experiment, detailing the URL endpoints accurate and data/data format used by the experimentnot confusing.
=== Extension Lifecycle ===
Use Most experiments live for a fixed period and are uninstalled by the bootstrap.js <code>startup</code> method to kick off experiments, rather than experiment system at the <code>install</code> method, so that end date or after the experiment will try again if it's aborted by Firefox shutting downspecified elapsed time.
Experiments must A few experiments are intended to collect data once and then uninstall themself. These experiments should uninstall themselves when done, which must include cleaning up resources and by calling <code>Experiments.disableExperiment("FROM_API")</code>.
== Staging ==
Confirm, emeritus
1,217
edits

Navigation menu