https://wiki.mozilla.org/api.php?action=feedcontributions&user=Jesse&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T08:44:59ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=MathML:OperatorDictionary&diff=1138840MathML:OperatorDictionary2016-07-06T14:52:43Z<p>Jesse: MXR -> DXR</p>
<hr />
<div>The [http://www.w3.org/TR/MathML3/appendixc.html MathML 3 Operator Dictionary] indexes each operator by a character (an unicode code point) in a given form (prefix, infix or postfix). Each operator has the following [http://www.w3.org/TR/MathML3/chapter3.html#presm.mo.attrs attributes]:<br />
<br />
* a priority<br />
* leading and trailing spaces (in 1/18th of em). A value between 0 and 7.<br />
* minsize/maxsize<br />
* properties (fence, separator, stretchy, symmetric, largeop, movablelimits, accent, mirrorable). Mentioned iff it is true.<br />
<br />
Our implementation uses a [https://developer.mozilla.org/en/XUL_Tutorial/Property_Files property file] with entries similar to what is described above. The property name is <tt>operator.\u[NNNN].[form]</tt> where <tt>[NNNN]</tt> is the unicode code point and <tt>[form]</tt> the operator form. The value of the property is a list of several <tt>AttributeName</tt> or <tt>AttributeName:AttributeValue</tt> (depending whether it is a boolean valued attributes or not) separated by whitespaces. Compared to the MathML3 dictionary, we don't include the "priority" attribute but have the additional attribute:<br />
<br />
* direction: horizontal, vertical (XXXfred add updiagonal, downdiagonal later?)<br />
<br />
Finally, the end of the line after a sharp is considered as a comment: we use this to give the glyph or name of the character. Thus, a typical entry is:<br />
<br />
<pre><br />
operator.\u0028.prefix = direction:vertical stretchy fence symmetric lspace:0 rspace:0 # (<br />
</pre><br />
<br />
Our Operator Dictionary is stored in [https://dxr.mozilla.org/mozilla-central/source/layout/mathml/mathfont.properties mathfont.properties].</div>Jessehttps://wiki.mozilla.org/index.php?title=MathML:Home_Page&diff=1138839MathML:Home Page2016-07-06T14:51:20Z<p>Jesse: MXR -> DXR</p>
<hr />
<div>This wiki is used by the contributors to the Mozilla MathML Project to plan and document the development of the MathML implementation and other project related work. For documents on authoring MathML content please see the [https://developer.mozilla.org/en/Mozilla_MathML_Project/Authoring Guidelines for Authoring MathML]. <br />
<br />
== Project goals ==<br />
<br />
*To provide a high quality implementation of Presentation MathML 3 <br />
*To promote flawless interoperability between MathML implementations <br />
*To promote the use of open standards on the Web<br />
<br />
== The Team ==<br />
<br />
* Karl Tomlinson (karlt) - Module Owner<br />
* Robert O'Callahan (roc) - Peer Reviewer<br />
* Frédéric Wang (fredw) - Mentor for newcomers<br />
* Florian Scholz (fscholz) - MDN Documentation Writer<br />
* Raniere Silva (raniere) - MathML and Firefox OS enthusiastic<br />
* Xuan Hu (huxuan) - MathML and LaTeX enthusiastic<br />
<br />
== Meeting Notes ==<br />
In chronological reverse order:<br />
<br />
* 2015<br />
** 2015/09 (canceled)<br />
** 2015/08 (canceled)<br />
** 2015/06 (canceled)<br />
** [http://blog.rgaiacs.com/2015/06/07/mathml_may_meeting.html 2015/05]<br />
** [http://blog.rgaiacs.com/2015/04/13/mathml_april_meeting.html 2015/04]<br />
** [http://blog.rgaiacs.com/2015/03/27/mathml_march_meeting.html 2015/03]<br />
** 2015/02 (canceled)<br />
** [http://blog.rgaiacs.com/2015/01/20/mathml_january_meeting.html 2015/01]<br />
* 2014 <br />
** [http://blog.rgaiacs.com/2014/11/19/mathml_november_meeting.html 2014/11]<br />
** [http://blog.rgaiacs.com/2014/10/10/mathml_october_meeting.html 2014/10]<br />
** [http://blog.rgaiacs.com/2014/09/17/mathml_september_meeting.html 2014/09]<br />
** [http://blog.rgaiacs.com/2014/08/17/mathml_august_meeting.html 2014/08]<br />
** [http://blog.rgaiacs.com/2014/07/27/mathml_july_meeting.html 2014/07]<br />
** [http://blog.rgaiacs.com/2014/06/22/mathml_june_meeting.html 2014/06]<br />
** [http://blog.rgaiacs.com/2014/05/16/mathml_may_meeting.html 2014/05/15]<br />
** [http://blog.rgaiacs.com/2014/04/13/mathml_april_meeting.html 2014/04/10]<br />
** [http://blog.rgaiacs.com/2014/03/13/4th_mathml_meeting.html 2014/03/13]<br />
** [http://blog.rgaiacs.com/2014/02/14/3rd_mathml_meeting.html 2014/02/13]<br />
** [http://blog.rgaiacs.com/2014/01/10/2nd_mathml_meeting.html 2014/01/10]<br />
* 2013<br />
** [http://blog.rgaiacs.com/2013/12/14/mathml_meeting.html 2013/12/14]<br />
<br />
== Getting involved ==<br />
<br />
So you want to get involved in the Mozilla MathML project? Great! There are many ways to contribute to the project and help us improving Mozilla's MathML implementation.<br />
<br />
First you can test [http://www.mozilla.org/en-US/firefox/channel/ Release, Beta or Aurora builds] and [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=MathML report bugs]. You may also want to try the latest MathML developments by downloading experimental [http://www.wg9s.com/mozilla/firefox/ nightly builds with MathML patches applied].<br />
<br />
You can also help up maintaining the [https://developer.mozilla.org/en/MathML MDN pages about MathML]. For example you can pick MathML items from [http://beta.elchi3.de/doctracker/#list=fx&version=--- bugs needed documentation].<br />
<br />
Finally, if you know C++ you can [https://developer.mozilla.org/en/Introduction contribute to the Mozilla codebase]. For instance, [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=component%3Amathml%20bug_mentor%3A%40&list_id=11210216 mentored bugs] or [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=kw%3Astudent-project;list_id=2834929;product=Core;component=MathML student projects]. It is also worth considering [https://bugzilla.mozilla.org/buglist.cgi?keywords=helpwanted;keywords_type=allwords;resolution=---;classification=Components;query_format=advanced;component=MathML;product=Core;list_id=2834935 bugs marked helpwanted].<br />
<br />
Get in touch with other MathML community members in [irc://irc.mozilla.org/mathml #mathml] on [http://irc.mozilla.org irc.mozilla.org].<br />
<br />
== Implementation status ==<br />
<br />
See the [https://developer.mozilla.org/en/Mozilla_MathML_Project/Status status page]. For a general overview of the MathML status in 2013, see the [http://fred-wang.github.io/MozSummitMathML/index.html slides from the innovation fairs of the Mozilla Summit].<br />
<br />
== Roadmap/Priorities ==<br />
<br />
Below is the list of MathML bugs classified according to their '''priority''' field (see [http://dbaron.org/log/20090120-bug-priorities David's suggestion]).<br />
<br />
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=MathML&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&priority=P2&order=Bug+Number P1/P2 MathML bugs] <br />
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=MathML&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P3&order=Bug+Number P3 MathML bugs] <br />
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=MathML&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P4&order=Bug+Number P4 MathML bugs] <br />
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=MathML&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P5&order=Bug+Number P5 MathML bugs] <br />
*[https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=MathML&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=--&order=Bug+Number All other MathML bugs]<br />
<br />
Here is a list of MathML bugs that received votes:<br />
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;votes_type=greaterthan;votes=5;order=bugs.votes;classification=Components;component=MathML;product=Core;resolution=--- MathML Bugs with more than 5 votes]<br />
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;type0-1-0=lessthaneq;field0-1-0=votes;field0-0-0=votes;value0-1-0=5;type0-0-0=greaterthaneq;value0-0-0=1;order=bugs.votes;classification=Components;component=MathML;product=Core;resolution=--- MathML Bugs with from 1 to 5 votes]<br />
<br />
== Planning for MathML ==<br />
<br />
* [[MathML:Open Type MATH Table|Open Type MATH table]]<br />
* New MathML features ({{bug|525772}} and {{bug|534959}}).<br />
* Mozilla Bugs with MathJax ({{bug|687809}}, {{bug|745687}})<br />
* [[MathML:Stretchy|Operator Stretching]]<br />
* [[MathML:Fonts|Font Support]]<br />
* [[MathML:Documentation|MathML documentation]]<br />
* [[MathML:Cleanup|Code cleanup/refactoring]]<br />
<br />
== Last bugs fixed ==<br />
<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla45 mozilla 45] (Firefox 45)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla44 mozilla 44] (Firefox 44)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla43 mozilla 43] (Firefox 43)<br />
<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla42 mozilla 42] (Firefox 42)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla41 mozilla 41] (Firefox 41),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla40 mozilla 40] (Firefox 40),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla39 mozilla 39] (Firefox 39)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla38 mozilla 38] (Firefox 38),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla37 mozilla 37] (Firefox 37),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla36 mozilla 36] (Firefox 36)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla35 mozilla 35] (Firefox 35),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla34 mozilla 34] (Firefox 34), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla33 mozilla 33] (Firefox 33), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla32 mozilla 32] (Firefox 32)<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla31 mozilla 31] (Firefox 31),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla30 mozilla 30] (Firefox 30), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla29 mozilla 29] (Firefox 29), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla28 mozilla 28] (Firefox 28)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla27 mozilla 27] (Firefox 27), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla26 mozilla 26] (Firefox 26), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla25 mozilla 25] (Firefox 25)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla24 mozilla 24] (Firefox 24),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla23 mozilla 23] (Firefox 23), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla22 mozilla 22] (Firefox 22)<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla21 mozilla 21] (Firefox 21),[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla20 mozilla 20] (Firefox 20), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla19 mozilla 19] (Firefox 19)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla18 mozilla 18] (Firefox 18), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla17 mozilla 17] (Firefox 17), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla16 mozilla 16] (Firefox 16)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla15 mozilla 15] (Firefox 15), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla14 mozilla 14] (Firefox 14), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla13 mozilla 13] (Firefox 13)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla12 mozilla 12] (Firefox 12), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla11 mozilla 11] (Firefox 11), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla10 mozilla 10] (Firefox 10)<br />
*[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla9 mozilla 9] (Firefox 9), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla8 mozilla 8] (Firefox 8), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla7 mozilla 7] (Firefox 7)<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla6 mozilla 6] (Firefox 6), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla5 mozilla 5] (Firefox 5), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla2.0b1&target_milestone=mozilla2.0b2&target_milestone=mozilla2.0b3&target_milestone=mozilla2.0b4&target_milestone=mozilla2.0b5&target_milestone=mozilla2.0b6&target_milestone=mozilla2.0b7&target_milestone=mozilla2.0b8&target_milestone=mozilla2.0b9&target_milestone=mozilla2.0b10&target_milestone=mozilla2.0b11&target_milestone=mozilla2.0b12&target_milestone=mozilla2.0 mozilla 2.0] (Firefox 4.0)<br />
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla1.9.3a1&target_milestone=mozilla1.9.3a2&target_milestone=mozilla1.9.3a3&target_milestone=mozilla1.9.3a4&target_milestone=mozilla1.9.3a5&target_milestone=mozilla1.9.3 mozilla 1.9.3] (Firefox 3.7), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla1.9.2a1&target_milestone=mozilla1.9.2b1&target_milestone=mozilla1.9.2 mozilla 1.9.2] (Firefox 3.6), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&target_milestone=mozilla1.9.1a1&target_milestone=mozilla1.9.1a2&target_milestone=mozilla1.9.1b1&target_milestone=mozilla1.9.1b2&target_milestone=mozilla1.9.1b3&target_milestone=mozilla1.9.1b4&target_milestone=mozilla1.9.1&product=Core mozilla 1.9.1] (Firefox 3.5), [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&component=MathML&product=Core&target_milestone=mozilla1.9alpha1&target_milestone=mozilla1.9alpha2&target_milestone=mozilla1.9alpha3&target_milestone=mozilla1.9alpha4&target_milestone=mozilla1.9alpha5&target_milestone=mozilla1.9alpha6&target_milestone=mozilla1.9alpha7&target_milestone=mozilla1.9alpha8&target_milestone=mozilla1.9beta1&target_milestone=mozilla1.9beta2&target_milestone=mozilla1.9beta3&target_milestone=mozilla1.9beta4&target_milestone=mozilla1.9beta5&target_milestone=mozilla1.9 mozilla 1.9] (Firefox 3.0)<br />
<br />
== MathML Source Code ==<br />
<br />
The majority of the MathML code lives in files under the directories: <br />
<br />
* [https://dxr.mozilla.org/mozilla-central/source/content/mathml/content/src/ mozilla/content/mathml/content/src/] <br />
* [https://dxr.mozilla.org/mozilla-central/source/layout/mathml/ mozilla/layout/mathml/]<br />
<br />
MathML tests are available here:<br />
* [https://dxr.mozilla.org/mozilla-central/source/layout/reftests/mathml/ Reftests]<br />
* [https://dxr.mozilla.org/mozilla-central/source/layout/mathml/crashtests/ Crashtests]<br />
* [https://dxr.mozilla.org/mozilla-central/source/layout/mathml/tests/ Mochitests and other tests]<br />
<br />
== Documentation ==<br />
<br />
* [[MathML:OperatorDictionary|Operator Dictionary]]</div>Jessehttps://wiki.mozilla.org/index.php?title=Firefox/Go_Faster/Client_Implementation_Plan&diff=1099257Firefox/Go Faster/Client Implementation Plan2015-10-05T18:58:21Z<p>Jesse: Typo</p>
<hr />
<div>This is a straw-man client implementation plan that covers the main [[Firefox/Go Faster/Client Requirements|Client Requirements]]. The rough set of bugs needed to implement this are called out.<br />
<br />
=Known-good sets=<br />
<br />
To reduce the number of possible configurations thus simplifying QA and dependency issues the client implementation uses the concept of a "known-good set" of system add-ons. This is a list of add-on IDs and versions to run for a particular application.<br />
<br />
Every application package and update will be distributed with a known-good set of system add-ons for that application. Periodically the application will attempt to discover a new known-good set to be installed and used.<br />
<br />
The application will only run with a known-good set of system add-ons enabled or it will not enable any system add-ons and run standalone though since the application ships with a known-good set we should generally never be in this state.<br />
<br />
The only exception is in the case where a developer has installed a version of a system add-on in the profile for testing, in this case it essentially overrides the known-good version for that add-on.<br />
<br />
=Running system add-ons=<br />
<br />
System add-ons will be installed in the user's profile. This assures that client code can install and update add-ons without needing special privileges and that there can only be one client application accessing the add-ons at a time.<br />
<br />
They will be installed in a directory used as a regular add-on install location with a lower priority than the profile install location. This allows developers to test out new versions of system add-ons by installing them using the regular add-ons manager.<br />
<br />
Unlike existing add-on install locations system add-ons will be installed in a filename based on both ID and version, <id>_<version>.xpi. This allows multiple versions of the same add-on to be installed at the same time so if a user is running a developer edition and release version they can rely on different known-good sets.<br />
<br />
* '''Bug: Cache the known-good set of add-ons on a per-install basis'''<br />
* '''Bug: Create a features install location with a lower priority to the profile location which lists the current known-good set of add-ons'''<br />
* '''Bug: Hide system add-ons in the features location from the add-ons manager UI'''<br />
<br />
If a user uninstalls an old build they will be left with a now useless set of system add-ons. Periodically we should check '''<profile>/features''' for unused add-ons. We can update a manifest with the last-used time of the current add-ons and remove ones that haven't been used in a while.<br />
<br />
* '''Bug: Shortly after startup write the current time to the system add-on install location and purge older locations'''<br />
<br />
=Discovering system add-ons=<br />
<br />
By default the add-ons manager will attempt to update system add-ons automatically, this must be disabled so a slightly different mechanism for finding updates can be used.<br />
<br />
* '''Bug: Disable automated updates for the system add-ons location'''<br />
<br />
During runtime the client will periodically make a HTTPS request to a specific URL including data on the application channel, version and OS The manifest returned lists the specific system add-ons that should be used with that application.<br />
<br />
An example response:<br />
<br />
<updates><addons><br />
<addon id="loop@mozilla.org" URL="https://addons.mozilla.org/addons/loop.xpi" version="12"/><br />
<addon id="pdfjs@mozilla.org" URL="https://cdn.addons.mozilla.org/addons/pdfjs.xpi" version="1.4"/><br />
</addons></updates><br />
<br />
If the server returns with an error or malformed XML or the response doesn't include an <addons> section then the result is ignored and the current set of system add-ons is kept. If the <addons> tag is present but empty then it means no system add-ons should be enabled.<br />
<br />
Any add-on versions that are not already available locally are downloaded.<br />
<br />
* '''Bug: Download and install new system add-ons'''<br />
<br />
Once all the add-on versions listed in the manifest are available locally and are verified to be usable with the current application they are copied to a new directory inside <profile>/features and the known-good set is updated with the new set. Any enabled system add-ons not in the set are disabled, any system add-ons in the set not enabled are enabled.<br />
<br />
* '''Bug: Replace the current set of system add-ons with the new known-good set'''<br />
<br />
=Securing system add-ons=<br />
<br />
System add-ons will need to be signed in a way that differentiates them from regular add-ons. This means either using a custom signing certificate or using the AMO signing service. AMO currently has two signing servers set up two sign preliminarily reviewed add-ons and fully reviewed add-ons. Clients can distinguish between the two based on a special string added to the Organizational Unit (OU) of the signing certificate for each add-on. Adding a third signing server that adds a new string to the OU is straightforward but AMO would need some updates to know to pass certain add-ons to that server.<br />
<br />
* '''Bug: Add-ons manager signature checks should enforce special rules for add-ons installed in the system add-ons location'''<br />
<br />
=Bootstrapping=<br />
<br />
In order to give a good experience to users using a new profile or updating after not having used the client in a while the application should ship with a known-good set of system add-ons for that build. This means including the add-ons in installers, packages, dmgs and the update mars for the application.<br />
<br />
* '''Bug: Include system add-ons in application packages and updates'''<br />
<br />
On the startup of a new version of an application the client will replace its known-good set with the new set included in the application.<br />
<br />
* '''Bug: On startup with a new application version switch to the shipped known-good set"<br />
<br />
=Add-on Dependencies=<br />
<br />
Add-on dependencies should be managed at the server side. The client will ensure that only a known-good set of system add-ons runs.</div>Jessehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates&diff=1036216WeeklyUpdates2014-11-24T19:01:53Z<p>Jesse: fix link to 24th</p>
<hr />
<div>:''These updates concern Mozilla as a whole. For the weekly Firefox meetings, see [[Firefox/DeliveryMeetings]], for Gecko progress, see [[Platform#Meeting_Notes]].''<br />
<br />
==Meeting Details==<br />
*Every Monday @ 11:00am Pacific Time (18:00 UTC)<br />
*Mozilla HQ, Ten Forward commons area <br />
{{conf|8600}}<br />
*http://air.mozilla.org/ to watch and listen <br />
*join irc.mozilla.org #airmozilla for backchannel discussion<br />
*'''Presenters only''': Vidyo room "Brownbags". Do ''not'' use this room if you're not planning to speak.<br />
<br />
'''Agenda:''' [[WeeklyUpdates/{{#time: Y-m-d | monday}}|Next Week's Agenda]]<br />
<br />
When you call in, you'll be muted by default, to keep phone noise down. Use "*1" (including the star) to unmute yourself if you want to say something. <br />
<br />
Full notes below. <!-- See https://wiki.mozilla.org/WeeklyUpdates/Template for create new page --><br />
<br />
==Meeting Notes==<br />
[[Template:WeeklyUpdates]] - <nowiki>{{subst:WeeklyUpdates}}</nowiki><br />
<!--*[[WeeklyUpdates/Template]]--><br />
<br />
Create a new weekly agenda from the [[Template:WeeklyUpdates|template]]:<br />
<createbox><br />
align=left<br />
type=create<br />
preload=Template:WeeklyUpdates<br />
default={{#time: Y-m-d | monday}}<br />
prefix=WeeklyUpdates/<br />
</createbox><br />
<br />
{| class="wikitable collapsible" style="width: 100%"<br />
! 2014 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2014-11-24|November 24th, 2014]]<br />
*[[WeeklyUpdates/2014-11-17|November 17th, 2014]]<br />
*[[WeeklyUpdates/2014-11-10|November 10th, 2014]]<br />
*[[WeeklyUpdates/2014-11-03|November 3rd, 2014]]<br />
*[[WeeklyUpdates/2014-10-27|October 27th, 2014]]<br />
*[[WeeklyUpdates/2014-10-20|October 20th, 2014]]<br />
*[[WeeklyUpdates/2014-10-13|October 13th, 2014]]<br />
*[[WeeklyUpdates/2014-10-06|October 6th, 2014]]<br />
*[[WeeklyUpdates/2014-09-29|September 29th, 2014]]<br />
*[[WeeklyUpdates/2014-09-22|September 22th, 2014]]<br />
*[[WeeklyUpdates/2014-09-15|September 15th, 2014]]<br />
*[[WeeklyUpdates/2014-09-08|September 8th, 2014]]<br />
*[[WeeklyUpdates/2014-09-01|September 1st, 2014]]<br />
*[[WeeklyUpdates/2014-08-25|August 25, 2014]]<br />
*[[WeeklyUpdates/2014-08-18|August 18, 2014]]<br />
*[[WeeklyUpdates/2014-08-11|August 11, 2014]]<br />
*[[WeeklyUpdates/2014-08-04|August 4, 2014]]<br />
*[[WeeklyUpdates/2014-07-28|July 28, 2014]]<br />
*[[WeeklyUpdates/2014-07-21|July 21, 2014]]<br />
*[[WeeklyUpdates/2014-07-14|July 14, 2014]]<br />
*[[WeeklyUpdates/2014-07-07|July 7, 2014]]<br />
*[[WeeklyUpdates/2014-06-30|June 30, 2014]]<br />
*[[WeeklyUpdates/2014-06-23|June 23, 2014]]<br />
*[[WeeklyUpdates/2014-06-16|June 16, 2014]]<br />
*[[WeeklyUpdates/2014-06-09|June 09, 2014]]<br />
*[[WeeklyUpdates/2014-06-02|June 02, 2014]]<br />
*[[WeeklyUpdates/2014-05-26|May 26, 2014]]<br />
*[[WeeklyUpdates/2014-05-19|May 19, 2014]]<br />
*[[WeeklyUpdates/2014-05-12|May 12, 2014]]<br />
*[[WeeklyUpdates/2014-05-05|May 05, 2014]]<br />
*[[WeeklyUpdates/2014-04-28|April 28, 2014]]<br />
*[[WeeklyUpdates/2014-04-21|April 21, 2014]]<br />
*[[WeeklyUpdates/2014-04-14|April 14, 2014]]<br />
*[[WeeklyUpdates/2014-04-07|April 7, 2014]]<br />
*[[WeeklyUpdates/2014-03-31|March 31, 2014]]<br />
*[[WeeklyUpdates/2014-03-24|March 24, 2014]]<br />
*[[WeeklyUpdates/2014-03-17|March 17, 2014]]<br />
*[[WeeklyUpdates/2014-03-10|March 10, 2014]]<br />
*[[WeeklyUpdates/2014-03-03|March 3, 2014]]<br />
*[[WeeklyUpdates/2014-02-24|February 24, 2014]]<br />
*[[WeeklyUpdates/2014-02-10|February 10, 2014]]<br />
*[[WeeklyUpdates/2014-02-03|February 3, 2014]]<br />
*[[WeeklyUpdates/2014-01-27|January 27, 2014]]<br />
*[[WeeklyUpdates/2014-01-20|January 20, 2014]]<br />
*[[WeeklyUpdates/2014-01-13|January 13, 2014]]<br />
*[[WeeklyUpdates/2014-01-06|January 6, 2014]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2013 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2013-12-16|December 16, 2013]]<br />
*[[WeeklyUpdates/2013-12-09|December 9, 2013]]<br />
*[[WeeklyUpdates/2013-12-02|December 2, 2013]]<br />
*[[WeeklyUpdates/2013-11-25|November 25, 2013]]<br />
*[[WeeklyUpdates/2013-11-18|November 18, 2013]]<br />
*[[WeeklyUpdates/2013-11-11|November 11, 2013]]<br />
*[[WeeklyUpdates/2013-11-04|November 4, 2013]]<br />
*[[WeeklyUpdates/2013-10-28|October 28, 2013]]<br />
*[[WeeklyUpdates/2013-10-21|October 21, 2013]]<br />
*[[WeeklyUpdates/2013-10-14|October 14, 2013]]<br />
*[[WeeklyUpdates/2013-10-07|October 7, 2013]]<br />
*[[WeeklyUpdates/2013-09-30|September 30, 2013]]<br />
*[[WeeklyUpdates/2013-09-23|September 23, 2013]]<br />
*[[WeeklyUpdates/2013-09-16|September 16, 2013]]<br />
*[[WeeklyUpdates/2013-09-09|September 9, 2013]]<br />
*[[WeeklyUpdates/2013-09-02|September 2, 2013]]<br />
*[[WeeklyUpdates/2013-08-26|August 26, 2013]]<br />
*[[WeeklyUpdates/2013-08-19|August 19, 2013]]<br />
*[[WeeklyUpdates/2013-08-12|August 12, 2013]]<br />
*[[WeeklyUpdates/2013-08-05|August 5, 2013]]<br />
*[[WeeklyUpdates/2013-07-29|July 29, 2013]]<br />
*[[WeeklyUpdates/2013-07-22|July 22, 2013]]<br />
*[[WeeklyUpdates/2013-07-15|July 15, 2013]]<br />
*[[WeeklyUpdates/2013-07-08|July 8, 2013]]<br />
*[[WeeklyUpdates/2013-07-01|July 1, 2013]]<br />
*[[WeeklyUpdates/2013-06-24|June 24, 2013]]<br />
*[[WeeklyUpdates/2013-06-17|June 17, 2013]]<br />
*[[WeeklyUpdates/2013-06-10|June 10, 2013]]<br />
*[[WeeklyUpdates/2013-06-03|June 3, 2013]]<br />
*[[WeeklyUpdates/2013-05-20|May 20, 2013]]<br />
*[[WeeklyUpdates/2013-05-13|May 13, 2013]]<br />
*[[WeeklyUpdates/2013-05-06|May 6, 2013]]<br />
*[[WeeklyUpdates/2013-04-29|April 29, 2013]]<br />
*[[WeeklyUpdates/2013-04-22|April 22, 2013]]<br />
*[[WeeklyUpdates/2013-04-15|April 15, 2013]]<br />
*[[WeeklyUpdates/2013-04-08|April 8, 2013]]<br />
*[[WeeklyUpdates/2013-04-01|April 1, 2013]]<br />
*[[WeeklyUpdates/2013-03-25|March 25, 2013]]<br />
*[[WeeklyUpdates/2013-03-18|March 18, 2013]]<br />
*[[WeeklyUpdates/2013-03-11|March 11, 2013]]<br />
*[[WeeklyUpdates/2013-03-04|March 4, 2013]]<br />
*[[WeeklyUpdates/2013-02-25|February 25, 2013]]<br />
*February 18, 2013 - ''No meeting.'' <br />
*[[WeeklyUpdates/2013-02-11|February 11, 2013]]<br />
*[[WeeklyUpdates/2013-02-04|February 04, 2013]]<br />
*[[WeeklyUpdates/2013-01-28|January 28, 2013]]<br />
*[[WeeklyUpdates/2013-01-21|January 21, 2013]]<br />
*[[WeeklyUpdates/2013-01-14|January 14, 2013]]<br />
*[[WeeklyUpdates/2013-01-07|January 7, 2013]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2012 <br />
|-<br />
|<br />
*December 31, 2012 - ''No meeting.''<br />
*December 24, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-12-17|December 17, 2012]]<br />
*[[WeeklyUpdates/2012-12-10|December 10, 2012]]<br />
*[[WeeklyUpdates/2012-12-03|December 03, 2012]]<br />
*[[WeeklyUpdates/2012-11-26|November 26, 2012]]<br />
*[[WeeklyUpdates/2012-11-19|November 19, 2012]]<br />
*[[WeeklyUpdates/2012-11-12|November 12, 2012]]<br />
*[[WeeklyUpdates/2012-11-05|November 5, 2012]]<br />
*[[WeeklyUpdates/2012-10-29|October 29, 2012]]<br />
*[[WeeklyUpdates/2012-10-22|October 22, 2012]]<br />
*[[WeeklyUpdates/2012-10-15|October 15, 2012]]<br />
*[[WeeklyUpdates/2012-10-08|October 8, 2012]]<br />
*[[WeeklyUpdates/2012-10-01|October 1, 2012]]<br />
*[[WeeklyUpdates/2012-09-24|September 24, 2012]]<br />
*[[WeeklyUpdates/2012-09-17|September 17, 2012]]<br />
*[[WeeklyUpdates/2012-09-10|September 10, 2012]]<br />
*[[WeeklyUpdates/2012-08-27|August 27, 2012]]<br />
*[[WeeklyUpdates/2012-08-20|August 20, 2012]]<br />
*[[WeeklyUpdates/2012-08-13|August 13, 2012]]<br />
*[[WeeklyUpdates/2012-08-06|August 06, 2012]]<br />
*[[WeeklyUpdates/2012-07-30|July 30, 2012]]<br />
*[[WeeklyUpdates/2012-07-23|July 23, 2012]]<br />
*[[WeeklyUpdates/2012-07-16|July 16, 2012]]<br />
*[[WeeklyUpdates/2012-07-09|July 9, 2012]]<br />
*[[WeeklyUpdates/2012-07-02|July 2, 2012]]<br />
*[[WeeklyUpdates/2012-06-25|June 25, 2012]]<br />
*[[WeeklyUpdates/2012-06-18|June 18, 2012]]<br />
*[[WeeklyUpdates/2012-06-11|June 11, 2012]]<br />
*[[WeeklyUpdates/2012-06-04|June 4, 2012]]<br />
*[[WeeklyUpdates/2012-05-28|May 28, 2012]]<br />
*[[WeeklyUpdates/2012-05-21|May 21, 2012]]<br />
*[[WeeklyUpdates/2012-05-14|May 14, 2012]]<br />
*[[WeeklyUpdates/2012-05-07|May 7, 2012]]<br />
*[[WeeklyUpdates/2012-04-30|April 30, 2012]]<br />
*[[WeeklyUpdates/2012-04-23|April 23, 2012]]<br />
*[[WeeklyUpdates/2012-04-16|April 16, 2012]]<br />
*[[WeeklyUpdates/2012-04-09|April 9, 2012]]<br />
*[[WeeklyUpdates/2012-04-02|April 2, 2012]]<br />
*[[WeeklyUpdates/2012-03-26|March 26, 2012]]<br />
*[[WeeklyUpdates/2012-03-19|March 19, 2012]]<br />
*[[WeeklyUpdates/2012-03-12|March 12, 2012]]<br />
*[[WeeklyUpdates/2012-03-05|March 5, 2012]]<br />
*[[WeeklyUpdates/2012-02-27|February 27, 2012]]<br />
*February 20, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-02-13|February 13, 2012]]<br />
*[[WeeklyUpdates/2012-02-06|February 6, 2012]]<br />
*[[WeeklyUpdates/2012-01-30|January 30, 2012]]<br />
*[[WeeklyUpdates/2012-01-23|January 23, 2012]]<br />
*January 16, 2012 - ''No meeting.''<br />
*[[WeeklyUpdates/2012-01-09|January 9, 2012]]<br />
*January 2, 2012 - ''No meeting.''<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2011 <br />
|-<br />
|<br />
*December 26, 2011 - ''No meeting.''<br />
*[[WeeklyUpdates/2011-12-19|December 19, 2011]]<br />
*[[WeeklyUpdates/2011-12-12|December 12, 2011]]<br />
*[[WeeklyUpdates/2011-12-05|December 5, 2011]]<br />
*[[WeeklyUpdates/2011-11-28|November 28, 2011]]<br />
*[[WeeklyUpdates/2011-11-21|November 21, 2011]]<br />
*[[WeeklyUpdates/2011-11-14|November 14, 2011]]<br />
*[[WeeklyUpdates/2011-11-07|November 7, 2011]]<br />
*[[WeeklyUpdates/2011-10-31|October 31, 2011]]<br />
*[[WeeklyUpdates/2011-10-24|October 24, 2011]]<br />
*[[WeeklyUpdates/2011-10-17|October 17, 2011]]<br />
*[[WeeklyUpdates/2011-10-10|October 10, 2011]]<br />
*[[WeeklyUpdates/2011-10-03|October 3, 2011]]<br />
*[[WeeklyUpdates/2011-09-27|September 26, 2011]]<br />
*[[WeeklyUpdates/2011-09-19|September 19, 2011]]<br />
*September 12, 2011 - ''No meeting due to All-Hands week.''<br />
*September 5, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-08-29|August 29, 2011]]<br />
*[[WeeklyUpdates/2011-08-22|August 22, 2011]]<br />
*[[WeeklyUpdates/2011-08-15|August 15, 2011]]<br />
*[[WeeklyUpdates/2011-08-08|August 8, 2011]]<br />
*[[WeeklyUpdates/2011-08-01|August 1, 2011]]<br />
*[[WeeklyUpdates/2011-07-25|July 25, 2011]]<br />
*[[WeeklyUpdates/2011-07-18|July 18, 2011]]<br />
*[[WeeklyUpdates/2011-07-11|July 11, 2011]]<br />
*July 4, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-06-27|June 27, 2011]]<br />
*[[WeeklyUpdates/2011-06-20|June 20, 2011]]<br />
*[[WeeklyUpdates/2011-06-13|June 13, 2011]]<br />
*[[WeeklyUpdates/2011-06-06|June 6, 2011]]<br />
*May 30, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-05-23|May 23, 2011]]<br />
*[[WeeklyUpdates/2011-05-16|May 16, 2011]]<br />
*[[WeeklyUpdates/2011-05-09|May 9, 2011]]<br />
*[[WeeklyUpdates/2011-05-02|May 2, 2011]]<br />
*[[WeeklyUpdates/2011-04-25|April 25, 2011]]<br />
*[[WeeklyUpdates/2011-04-18|April 18, 2011]]<br />
*[[WeeklyUpdates/2011-04-11|April 11, 2011]]<br />
*April 4, 2011 - ''No meeting due to All-Hands week.''<br />
*[[WeeklyUpdates/2011-03-28|March 28, 2011]]<br />
*[[WeeklyUpdates/2011-03-21|March 21, 2011]]<br />
*[[WeeklyUpdates/2011-03-14|March 14, 2011]]<br />
*[[WeeklyUpdates/2011-03-07|March 7, 2011]]<br />
*[[WeeklyUpdates/2011-02-28|February 28, 2011]]<br />
*February 21, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-02-14|February 14, 2011]]<br />
*[[WeeklyUpdates/2011-02-07|February 07, 2011]]<br />
*[[WeeklyUpdates/2011-01-31|January 31, 2011]]<br />
*[[WeeklyUpdates/2011-01-24|January 24, 2011]]<br />
*January 17, 2011 - ''No meeting due to US holiday.''<br />
*[[WeeklyUpdates/2011-01-10|January 10, 2011]]<br />
*[[WeeklyUpdates/2011-01-03|January 3, 2011]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2010 <br />
|-<br />
|<br />
*December 27, 2010 - ''No meeting due to holiday season.''<br />
*[[WeeklyUpdates/2010-12-20|December 20, 2010]]<br />
*December 13, 2010 - ''No meeting due to Work Week''<br />
*[[WeeklyUpdates/2010-12-06|December 6, 2010]]<br />
*[[WeeklyUpdates/2010-11-29|November 29, 2010]]<br />
*[[WeeklyUpdates/2010-11-22|November 22, 2010]]<br />
*[[WeeklyUpdates/2010-11-15|November 15, 2010]]<br />
*[[WeeklyUpdates/2010-11-08|November 08, 2010]]<br />
*[[WeeklyUpdates/2010-11-01|November 01, 2010]]<br />
*[[WeeklyUpdates/2010-10-25|October 25, 2010]]<br />
*[[WeeklyUpdates/2010-10-18|October 18, 2010]]<br />
*[[WeeklyUpdates/2010-10-11|October 11, 2010]]<br />
*[[WeeklyUpdates/2010-10-04|October 4, 2010]]<br />
*[[WeeklyUpdates/2010-09-27|September 27, 2010]]<br />
*[[WeeklyUpdates/2010-09-20|September 20, 2010]]<br />
*[[WeeklyUpdates/2010-09-13|September 13, 2010]]<br />
*September 6, 2010 - ''No meeting due to US holiday''<br />
*[[WeeklyUpdates/2010-08-30|August 30, 2010]]<br />
*[[WeeklyUpdates/2010-08-23|August 23, 2010]]<br />
*[[WeeklyUpdates/2010-08-16|August 16, 2010]]<br />
*[[WeeklyUpdates/2010-08-09|August 9, 2010]]<br />
*[[WeeklyUpdates/2010-08-02|August 2, 2010]]<br />
*[[WeeklyUpdates/2010-07-26|July 26, 2010]]<br />
*[[WeeklyUpdates/2010-07-19|July 19, 2010]]<br />
*[[WeeklyUpdates/2010-07-12|July 12, 2010]]<br />
*July 5, 2010 - ''No meeting due to summit''<br />
*[[WeeklyUpdates/2010-06-28|June 28, 2010]]<br />
*[[WeeklyUpdates/2010-06-21|June 21, 2010]]<br />
*[[WeeklyUpdates/2010-06-14|June 14, 2010]]<br />
*[[WeeklyUpdates/2010-06-07|June 7, 2010]]<br />
*May 31, 2010 - ''No meeting due to US holiday''<br />
*[[WeeklyUpdates/2010-05-24|May 24, 2010]]<br />
*[[WeeklyUpdates/2010-05-17|May 17, 2010]]<br />
*[[WeeklyUpdates/2010-05-10|May 10, 2010]]<br />
*[[WeeklyUpdates/2010-05-03|May 03, 2010]]<br />
*[[WeeklyUpdates/2010-04-26|April 26, 2010]]<br />
*[[WeeklyUpdates/2010-04-19|April 19, 2010]]<br />
*[[WeeklyUpdates/2010-04-12|April 12, 2010]]<br />
*[[WeeklyUpdates/2010-04-05|April 5, 2010]]<br />
*[[WeeklyUpdates/2010-03-29|March 29, 2010]]<br />
*[[WeeklyUpdates/2010-03-22|March 22, 2010]]<br />
*[[WeeklyUpdates/2010-03-15|March 15, 2010]]<br />
*[[WeeklyUpdates/2010-03-08|March 8, 2010]]<br />
*[[WeeklyUpdates/2010-03-01|March 1, 2010]]<br />
*[[WeeklyUpdates/2010-02-22|February 22, 2010]] <br />
*[[WeeklyUpdates/2010-02-15|February 15, 2010]]- No meeting due to holiday, please leave updates in the wiki.<br />
*[[WeeklyUpdates/2010-02-08|February 8, 2010]] <br />
*[[WeeklyUpdates/2010-02-01|February 1, 2010]]<br />
*[[WeeklyUpdates/2010-01-25|January 25, 2010]]<br />
*[[WeeklyUpdates/2010-01-18|January 18, 2010]]- No meeting due to US holiday, please leaves updates in the wiki.<br />
*[[WeeklyUpdates/2010-01-11|January 11, 2010]]- First meeting using [[WeeklyUpdates/Guidance|new procedures]].<br />
*[[WeeklyUpdates/2010-01-04|January 04, 2010]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2009 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2009-12-28|December 28, 2009]]- No meeting due to holiday. Feel free to leave updates in the Wiki. <br />
*[[WeeklyUpdates/2009-12-21|December 21, 2009]] <br />
*[[WeeklyUpdates/2009-12-14|December 14, 2009]] <br />
*[[WeeklyUpdates/2009-12-07|December 07, 2009]]- No meeting due to all day Mozilla Corp meetings. Feel free to leave updates in the Wiki. <br />
*[[WeeklyUpdates/2009-11-30|November 30, 2009]] <br />
*[[WeeklyUpdates/2009-11-23|November 23, 2009]] <br />
*[[WeeklyUpdates/2009-11-16|November 16, 2009]] <br />
*[[WeeklyUpdates/2009-11-09|November 09, 2009]] <br />
*[[WeeklyUpdates/2009-11-02|November 02, 2009]] - Time Change! 19:00 UTC (11am PST) <br />
*[[WeeklyUpdates/2009-10-26|October 26, 2009]] <br />
*[[WeeklyUpdates/2009-10-19|October 19, 2009]] <br />
*[[WeeklyUpdates/2009-10-12|October 12, 2009]] <br />
*[[WeeklyUpdates/2009-10-05|October 05, 2009]] <br />
*[[WeeklyUpdates/2009-09-28|September 28, 2009]] <br />
*[[WeeklyUpdates/2009-09-21|September 21, 2009]] <br />
*[[WeeklyUpdates/2009-09-14|September 14, 2009]] <br />
*[[WeeklyUpdates/2009-09-07|September 07, 2009]] - No Meeting due to [http://en.wikipedia.org/wiki/Labor_Day Labor Day] Holiday <br />
*[[WeeklyUpdates/2009-08-31|August 31, 2009]] <br />
*[[WeeklyUpdates/2009-08-24|August 24, 2009]] <br />
*[[WeeklyUpdates/2009-08-17|August 17, 2009]] <br />
*[[WeeklyUpdates/2009-08-10|August 10, 2009]] <br />
*[[WeeklyUpdates/2009-08-03|August 03, 2009]] <br />
*[[WeeklyUpdates/2009-07-27|July 27, 2009]] <br />
*[[WeeklyUpdates/2009-07-20|July 20, 2009]] <br />
*[[WeeklyUpdates/2009-07-13|July 13, 2009]] <br />
*[[WeeklyUpdates/2009-07-06|July 06, 2009]] <br />
*[[WeeklyUpdates/2009-06-29|June 29, 2009]] <br />
*[[WeeklyUpdates/2009-06-22|June 22, 2009]] <br />
*[[WeeklyUpdates/2009-06-15|June 15, 2009]] <br />
*[[WeeklyUpdates/2009-06-08|June 08, 2009]] <br />
*[[WeeklyUpdates/2009-06-01|June 01, 2009]] <br />
*[[WeeklyUpdates/2009-05-25|May 25, 2009]] - No meeting due to US Holiday: [http://en.wikipedia.org/wiki/Memorial_day Memorial Day]. Feel free to leave status! <br />
*[[WeeklyUpdates/2009-05-18|May 18, 2009]] <br />
*[[WeeklyUpdates/2009-05-11|May 11, 2009]] <br />
*[[WeeklyUpdates/2009-05-04|May 04, 2009]] <br />
*April 27, 2009 - no update meeting this week due to on-site event <br />
*[[WeeklyUpdates/2009-04-20|April 20, 2009]] <br />
*[[WeeklyUpdates/2009-04-13|April 13, 2009]] <br />
*[[WeeklyUpdates/2009-04-06|April 06, 2009]] <br />
*[[WeeklyUpdates/2009-03-30|March 30, 2009]] <br />
*[[WeeklyUpdates/2009-03-23|March 23, 2009]] <br />
*[[WeeklyUpdates/2009-03-16|March 16, 2009]] <br />
*[[WeeklyUpdates/2009-03-09|March 09, 2009]] <br />
*[[WeeklyUpdates/2009-03-02|March 02, 2009]] <br />
*[[WeeklyUpdates/2009-02-23|February 23, 2009]] <br />
*February 16, 2009 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2009-02-09|February 09, 2009]] <br />
*[[WeeklyUpdates/2009-02-02|February 02, 2009]] <br />
*[[WeeklyUpdates/2009-01-26|January 26, 2009]] <br />
*January 19, 2009 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2009-01-12|January 12, 2009]] <br />
*[[WeeklyUpdates/2009-01-05|January 05, 2009]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2008 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2008-12-29|December 29, 2008]] <br />
*[[WeeklyUpdates/2008-12-22|December 22, 2008]] <br />
*[[WeeklyUpdates/2008-12-15|December 15, 2008]] <br />
*[[WeeklyUpdates/2008-12-08|December 08, 2008]] <br />
*[[WeeklyUpdates/2008-12-01|December 01, 2008]] <br />
*[[WeeklyUpdates/2008-11-24|November 24, 2008]] <br />
*[[WeeklyUpdates/2008-11-17|November 17, 2008]] <br />
*[[WeeklyUpdates/2008-11-10|November 10, 2008]] <br />
*[[WeeklyUpdates/2008-11-03|November 03, 2008]] <br />
*[[WeeklyUpdates/2008-10-27|October 27, 2008]] <br />
*[[WeeklyUpdates/2008-10-20|October 20, 2008]] <br />
*[[WeeklyUpdates/2008-10-13|October 13, 2008]] <br />
*[[WeeklyUpdates/2008-10-06|October 06, 2008]] <br />
*[[WeeklyUpdates/2008-09-29|September 29, 2008]] <br />
*[[WeeklyUpdates/2008-09-22|September 22, 2008]] <br />
*[[WeeklyUpdates/2008-09-15|September 15, 2008]] <br />
*[[WeeklyUpdates/2008-09-08|September 08, 2008]] <br />
*September 01, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-08-25|August 25, 2008]] <br />
*[[WeeklyUpdates/2008-08-18|August 18, 2008]] <br />
*[[WeeklyUpdates/2008-08-11|August 11, 2008]] <br />
*[[WeeklyUpdates/2008-08-04|August 04, 2008]] <br />
*July 28, 2008 - No Meeting due to Summit <br />
*[[WeeklyUpdates/2008-07-21|July 21, 2008]] <br />
*[[WeeklyUpdates/2008-07-14|July 14, 2008]] <br />
*[[WeeklyUpdates/2008-07-07|July 07, 2008]] <br />
*[[WeeklyUpdates/2008-06-30|June 30, 2008]] <br />
*[[WeeklyUpdates/2008-06-23|June 23, 2008]] <br />
*[[WeeklyUpdates/2008-06-16|June 16, 2008]] <br />
*[[WeeklyUpdates/2008-06-09|June 09, 2008]] <br />
*[[WeeklyUpdates/2008-06-02|June 02, 2008]] <br />
*May 26, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-05-19|May 19, 2008]] <br />
*[[WeeklyUpdates/2008-05-12|May 12, 2008]] <br />
*[[WeeklyUpdates/2008-05-05|May 05, 2008]] <br />
*[[WeeklyUpdates/2008-04-28|April 28, 2008]] <br />
*[[WeeklyUpdates/2008-04-21|April 21, 2008]] <br />
*[[WeeklyUpdates/2008-04-14|April 14, 2008]] <br />
*[[WeeklyUpdates/2008-04-07|April 07, 2008]] <br />
*[[WeeklyUpdates/2008-03-31|March 31, 2008]] <br />
*[[WeeklyUpdates/2008-03-24|March 24, 2008]] <br />
*[[WeeklyUpdates/2008-03-17|March 17, 2008]] <br />
*[[WeeklyUpdates/2008-03-10|March 10, 2008]] <br />
*[[WeeklyUpdates/2008-03-03|March 03, 2008]] <br />
*[[WeeklyUpdates/2008-02-25|February 25, 2008]] <br />
*February 18, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-02-11|February 11, 2008]] <br />
*[[WeeklyUpdates/2008-02-04|February 04, 2008]] <br />
*[[WeeklyUpdates/2008-01-28|January 28, 2008]] <br />
*January 21, 2008 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2008-01-14|January 14, 2008]] <br />
*[[WeeklyUpdates/2008-01-07|January 07, 2008]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2007 <br />
|-<br />
|<br />
*December 31, 2007 - No Meeting due to US holiday season <br />
*December 24, 2007 - No Meeting due to US holiday season <br />
*[[WeeklyUpdates/2007-12-17|December 17, 2007]] <br />
*[[WeeklyUpdates/2007-12-10|December 10, 2007]] <br />
*[[WeeklyUpdates/2007-12-03|December 03, 2007]] <br />
*[[WeeklyUpdates/2007-11-26|November 26, 2007]] <br />
*[[WeeklyUpdates/2007-11-19|November 19, 2007]] <br />
*November 12, 2007 - No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2007-11-05|November 05, 2007]] <br />
*[[WeeklyUpdates/2007-10-29|October 29, 2007]] <br />
*[[WeeklyUpdates/2007-10-22|October 22, 2007]] <br />
*[[WeeklyUpdates/2007-10-15|October 15, 2007]] <br />
*[[WeeklyUpdates/2007-10-08|October 08, 2007]] <br />
*[[WeeklyUpdates/2007-10-01|October 01, 2007]] <br />
*[[WeeklyUpdates/2007-09-24|September 24, 2007]] <br />
*[[WeeklyUpdates/2007-09-17|September 17, 2007]] <br />
*[[WeeklyUpdates/2007-09-10|September 10, 2007]] <br />
*[[WeeklyUpdates/2007-08-27|August 27, 2007]] <br />
*[[WeeklyUpdates/2007-08-20|August 20, 2007]] <br />
*[[WeeklyUpdates/2007-08-13|August 13, 2007]] <br />
*[[WeeklyUpdates/2007-08-06|August 6, 2007]] <br />
*[[WeeklyUpdates/2007-07-30|July 30, 2007]] <br />
*[[WeeklyUpdates/2007-07-23|July 23, 2007]] <br />
*[[WeeklyUpdates/2007-07-16|July 16, 2007]] <br />
*[[WeeklyUpdates/2007-07-09|July 9, 2007]] <br />
*[[WeeklyUpdates/2007-07-02|July 2, 2007]] <br />
*[[WeeklyUpdates/2007-06-25|June 25, 2007]] <br />
*[[WeeklyUpdates/2007-06-18|June 18, 2007]] <br />
*[[WeeklyUpdates/2007-06-11|June 11, 2007]] <br />
*[[WeeklyUpdates/2007-06-04|June 4, 2007]] <br />
*[[WeeklyUpdates/2007-05-21|May 21, 2007]] <br />
*[[WeeklyUpdates/2007-05-14|May 14, 2007]] <br />
*[[WeeklyUpdates/2007-05-07|May 7, 2007]] <br />
*[[WeeklyUpdates/2007-04-30|April 30, 2007]] <br />
*[[WeeklyUpdates/2007-04-23|April 23, 2007]] <br />
*[[WeeklyUpdates/2007-04-16|April 16, 2007]] <br />
*[[WeeklyUpdates/2007-04-09|April 9, 2007]] <br />
*[[WeeklyUpdates/2007-04-02|April 2, 2007]] <br />
*[[WeeklyUpdates/2007-03-26|March 26, 2007]] <br />
*[[WeeklyUpdates/2007-03-19|March 19, 2007]] <br />
*[[WeeklyUpdates/2007-03-12|March 12, 2007]] <br />
*[[WeeklyUpdates/2007-03-05|March 5, 2007]] <br />
*[[WeeklyUpdates/2007-02-26|February 26, 2007]] <br />
*[[WeeklyUpdates/2007-02-12|February 12, 2007]] <br />
*[[WeeklyUpdates/2007-02-05|February 5, 2007]] <br />
*[[WeeklyUpdates/2007-01-29|January 29, 2007]] <br />
*[[WeeklyUpdates/2007-01-22|January 22, 2007]] <br />
*[[WeeklyUpdates/2007-01-08|January 08, 2007]] <br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! 2006 <br />
|-<br />
|<br />
*[[WeeklyUpdates/2006-12-18|December 18, 2006]] <br />
*[[WeeklyUpdates/2006-12-11|December 11, 2006]] <br />
*[[WeeklyUpdates/2006-12-04|December 4, 2006]] <br />
*[[WeeklyUpdates/2006-11-27|November 27, 2006]] <br />
*[[WeeklyUpdates/2006-11-13|November 13, 2006]] <br />
*[[WeeklyUpdates/2006-11-06|November 6, 2006]] <br />
*[[WeeklyUpdates/2006-10-30|October 30, 2006]] <br />
*[[WeeklyUpdates/2006-10-23|October 23, 2006]] <br />
*[[WeeklyUpdates/2006-10-16|October 16, 2006]] <br />
*[[WeeklyUpdates/2006-10-09|October 9, 2006]] <br />
*[[WeeklyUpdates/2006-10-02|October 2, 2006]] <br />
*[[WeeklyUpdates/2006-09-25|September 25, 2006]] <br />
*[[WeeklyUpdates/2006-09-18|September 18, 2006]] <br />
*[[WeeklyUpdates/2006-09-11|September 11, 2006]] <br />
*September 4, 2006 - No Meeting due to US and Canadian Holiday <br />
*[[WeeklyUpdates/2006-08-28|August 28, 2006]] <br />
*[[WeeklyUpdates/2006-08-21|August 21, 2006]] <br />
*[[WeeklyUpdates/2006-08-14|August 14, 2006]] <br />
*[[WeeklyUpdates/2006-08-07|August 07, 2006]] <br />
*[[WeeklyUpdates/2006-07-31|July 31, 2006]] <br />
*[[WeeklyUpdates/2006-07-24|July 24, 2006]] <br />
*[[WeeklyUpdates/2006-07-17|July 17, 2006]] <br />
*[[WeeklyUpdates/2006-07-10|July 10, 2006]] <br />
*July 3, 2006 - No Meeting due to US Holiday <br />
*June 26, 2006 - No Meeting <br />
*[[WeeklyUpdates/2006-06-19|June 19, 2006]] <br />
*[[WeeklyUpdates/2006-06-12|June 12, 2006]] <br />
*[[WeeklyUpdates/2006-06-05|June 05, 2006]] <br />
*May 29, 2006 -- No Meeting due to US Holiday <br />
*[[WeeklyUpdates/2006-05-22|May 22, 2006]] <br />
*May 15, 2006 -- No Meeting due to XTech 2006 Conference <br />
*[[WeeklyUpdates/2006-05-08|May 08, 2006]] <br />
*[[WeeklyUpdates/2006-05-01|May 01, 2006]] <br />
*[[WeeklyUpdates/2006-04-24|April 24, 2006]] <br />
*[[WeeklyUpdates/2006-04-17|April 17, 2006]] <br />
*[[WeeklyUpdates/2006-04-10|April 10, 2006]] <br />
*[[WeeklyUpdates/2006-04-03|April 03, 2006]] <br />
*[[WeeklyUpdates/2006-03-27|March 27, 2006]]<br />
|}<br />
<br />
''Note: Older [http://www-archive.mozilla.org/status/minutes.html meeting minutes] and [http://www-archive.mozilla.org/status/ status updates] are available on the www.mozilla.org archive site.''<br />
<br />
[[Category:Weekly Updates]]<br />
[[Category:Meeting Notes]]</div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2014-Q3-Goals&diff=994544Platform/2014-Q3-Goals2014-07-03T18:38:05Z<p>Jesse: /* Firefox and Platform Security */</p>
<hr />
<div>=== Platform ===<br />
==== [[Platform/2014-Goals|2014 General Goals]] ====<br />
<br />
=== GFX ===<br />
<br />
=== Layout ===<br />
<br />
<br />
=== Media ===<br />
<br />
<br />
=== DOM ===<br />
* {{ok|Mirror prototype of DOM objects through xray wrappers (peterv)}}<br />
* {{ok|Remove nsDOMClassInfo.cpp}}<br />
* {{ok|Make less-privileged non-Xrayable unwaived opaque from privileged code ({{bug|856067}})}}<br />
* {{ok|Route all JSContext pushing through AutoJSAPI and Implement GetEntryGlobal ({{bug|951991}})}}<br />
<br />
=== WebAPI ===<br />
<br />
=== JS ===<br />
<br />
=== Accessibility ===<br />
* Taking shape: [[Accessibility/Planning/Goals]]<br />
<br />
=== Perf ===<br />
<br />
=== Networking ===<br />
<br />
=== Mobile ===<br />
<br />
=== A*Team ===<br />
<br />
For full list, see [[Auto-tools/Goals/2014Q3|A-Team Goals 2014Q3]]<br />
<br />
'''B2G'''<br />
* {{ok|}} Run a set of performance and correctness tests per-commit to b2g-inbound on Flame devices<br />
* {{ok|}} Get gaia-integration tests running on device<br />
* {{ok|}} Expand the FxOS Certification Suite with 1.4 support, test automation to prevent regressions, and investigation of support for non-phone devices<br />
* {{ok|}} Green up B2G tests on TaskCluster (joint with RelEng)<br />
<br />
'''Developer Productivity'''<br />
* {{ok|}} Deploy ReviewBoard for developers to start using (joint with RelEng)<br />
<br />
'''Performance'''<br />
* {{ok|}} Deploy new Talos tests for tp5o_scroll, webgl, webrtc, and mainthread I/O<br />
* {{ok|}} Get Datazilla alerts to beta mode (full parity with graph server alerts) with reduced noise<br />
* {{ok|}} Get Eideticker running against Android again with increased frequency<br />
* {{ok|}} Run B2G Eideticker against same branch/build combinations as our other on-device perf tests<br />
* {{ok|}} Stand up a Games Benchmarking system for webaudio tests running against Firefox and Chrome<br />
<br />
'''Treeherder'''<br />
* {{ok|}} Deliver performance web service for ingesting and returning performance data <br />
* {{ok|}} Deliver a UI for viewing Talos data<br />
<br />
'''Sheriffing'''<br />
* {{ok|}} Fully transition sheriffing from TBPL to Treeherder<br />
<br />
'''General Automation'''<br />
* {{ok|}} Create weekly reports that describe how many tests have been added/disabled/enabled per suite and platform<br />
* {{ok|}} Move reftest to mozbase<br />
* {{ok|}} Add command executors for Marionette for Java and Python<br />
<br />
'''Bugzilla'''<br />
* {{ok|}} Improve load time of related bugs; can decrease show_bug load times by up to 12%<br />
* {{ok|}} Minify and concatenate JS files<br />
* {{ok|}} Authoritative view for review history<br />
* {{ok|}} Rewrite docs for REST API<br />
<br />
'''Community'''<br />
* {{ok|}} Create good_next_bugs (name can be adjusted) so once contributors are comfortable they can do more serious coding/problem solving on a project they are familiar with<br />
* {{ok|}} Monthly review of mentored bugs and projects<br />
<br />
=== Web Engineering ===<br />
<br />
=== SUMO and Input ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== Release Engineering Operations ===<br />
<br />
=== Developer Services ===<br />
<br />
=== Security & Privacy Engineering ===<br />
''6/30/2014 draft, not yet frozen''<br />
(More details here: [[SecurityEngineering/2014/Q3Goals]])<br />
<br />
==== Content Security ====<br />
* {{new|Gecko Security Hooks: Finish code and debugging for New Channel API, start getting reviews}} (dri=tanvi)<br />
* {{new|Gecko Security Hooks: Create plan for addon compatibility}} (dri=tanvi)<br />
* {{new|CSP: Remove old JS implementation from mozilla-central}} (dri=sstamm)<br />
* {{new|Referer: Finish implementation of <meta> referrer control with volunteer help}} (dri=sstamm)<br />
* {{new|Evangelism: Security Open Mic presentation + blog post about new CSP implementation, maybe again as brown bag.}} (dri=sstamm)<br />
* {{new|''[stretch goal]'' CSP: Fix majority of CSP 1.1 compatibility bugs}} (dri=ckerschb)<br />
<br />
==== Tracking Protection ====<br />
* {{new|Land first implementation of protection in Fx 33/34 off by default.}} (dri=mmc)<br />
<br />
==== Communications Security ====<br />
* {{prev|SSL Error Reporting}} finish first implementation of ssl error reporting feature. (dri=grobinson)<br />
* {{new|Land enforcment of at least 2 more Baseline Requirements in PSM}} (dri=keeler)<br />
* {{new|Create roadmap for Cert Revocation improvements}} (dri=rbarnes)<br />
* {{new|hpkp - implement pinning http header}} (dri=cviecco)<br />
* {{new|''[stretch goal]'' Get CA Program data into one database}} (dri=kathleen)<br />
<br />
=== Firefox and Platform Security ===<br />
<br />
* [https://mana.mozilla.org/wiki/display/~gkwong@mozilla.com/Marifuzz Marifuzz ] fuzzer ported to and running on Flame devices.<br />
* Update ASan and LSan work for DOMFuzzer<br />
* Update "Bounty Stars" document with issues found by external reporters and updating DOMFuzzer to reflect these results.<br />
* Get Clang on RelEng ready for official OS X ASan builds.<br />
* Initial work to move CoreFuzz towards running in cloud environments.<br />
* WebCrypto API fuzzing using Dharma fuzzer. <br />
* Port a portion of WebRTC fuzzing from Frambois fuzzer to Dharma fuzzer.<br />
* Peach: Improving and porting Peach 2 to Python 3.<br />
* Public Mozilla Security Github work: Moving of fuzzing tools from Fuzzing Hg to GitHub, including work to separate harnesses from testcase generation tools.<br />
<br />
=== Games Program ===</div>Jessehttps://wiki.mozilla.org/index.php?title=User:Jesse/NewFrecency&diff=981797User:Jesse/NewFrecency2014-05-22T21:00:51Z<p>Jesse: </p>
<hr />
<div>'''Frecency''' is a measure that combines frequency and recency.<br />
<br />
This page describes a frecency measure based on exponential decay, and a way to store and update this measure efficiently.<br />
<br />
== Problems with the old algorithm ==<br />
https://developer.mozilla.org/en/The_Places_frecency_algorithm <br />
<br />
The use of buckets and sampling cause the following problems:<br />
<br />
* '''Questionable predictions'''<br />
** Non-monotonic: A series of low-value visits can make the computed frecency decrease. (In order to estimate the total value of all visits, the algorithm samples the visit types of the last 10 visits.)<br />
** Discontinuous: There is no reason to believe something special happens 4 days after a visit.<br />
* '''Performance'''<br />
** It requires periodic recomputation.<br />
*** Idle-daily recomputation already uses exponential decay (implemented in {{bug|476299}})<br />
*** On-visit recomputation does not use exponential decay.<br />
* '''Memory, privacy'''<br />
** The algorithm requires storing storing details about multiple visits.<br />
<br />
== Proposed new definition ==<br />
See also http://mathb.in/708, which is the same idea, but perhaps a simpler way of going about it. See also also http://mathb.in/713, which describes how to do a frecency update without bignums.<br />
<br />
The new definition is based on exponential decay. It simplifies the algorithm by removing the need for buckets, sampling, and recomputation. It improves the predictions by making them monotonic and continuous.<br />
<br />
* ''Decay rate constant''<br />
** '''λ''' ≡ (ln 2) / (30 days)<br />
* ''Current value of a visit''<br />
** '''current_visit_value''' ≡ visit_type_points * e^(-λ * visit_age)<br />
* ''URL's frecency score''<br />
** '''s''' ≡ ∑ current_visit_value ''for all visits''<br />
<br />
Both visit scores and total frecency scores decay with a half-life of 1 month. If typing a URL is worth 2 points, then a typed visit a month ago is worth 1 point.<br />
<br />
That takes care of the buckets and sampling. It could be implemented by storing the URL frecency score, and having an idle-daily job that multiplies all scores by (e ^ (-(ln 2) / 30)) = 0.977.<br />
<br />
== Efficient computation ==<br />
But with an additional trick, ''no recomputation is necessary''. The trick is to store in the database something with units of date.<br />
<br />
* ''URL's time until s=1''<br />
** '''t''' = (ln s) / λ<br />
** s = e^(λt)<br />
<br />
With this trick, we can just store '''now() + t''' in the database, and we're done.<br />
* No recomputation is necessary. Decay happens implicitly as '''t''' is stored and computed relative to different '''now()''' dates.<br />
* Sorting by (current) frecency score is equivalent to sorting by reverse date (on which the frecency will be 1).<br />
* Adding a visit just requires converting the date to a score, adding to the score, and converting the score back into date.<br />
* It is no longer necessary to store the visit. If want want, we can just update the last-visit-date and frecency-one-date of the URL without adding another row to the database.<br />
<br />
== What's kept from the current algorithm ==<br />
* Visit type bonuses<br />
* The half-life of 30 days is approximately taken from the current algorithm.<br />
<br />
== Possible disadvantages of the new algorithm ==<br />
* Requires floating point math<br />
* Doesn't emulate the "slowing decay" of the current bucket weights.<br />
** Could be emulated by having two exponential decays with different rates, if desired.<br />
<br />
== Implementation ==<br />
<br />
* Gecko - HTTP cache: [https://hg.mozilla.org/mozilla-central/file/b40296602083/netwerk/cache2/CacheEntry.cpp#l1497 in CacheEntry::BackgroundOp]<br />
* Firefox - URL history: Still uses the old algorithm ([https://bugzilla.mozilla.org/show_bug.cgi?id=704025 bug 704025])</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Meetings/SecurityAssurance/2013-10-22&diff=741484Security/Meetings/SecurityAssurance/2013-10-222013-10-29T20:35:03Z<p>Jesse: </p>
<hr />
<div>{{SecAssuranceMeetingInfo}}<br />
{{TOC right}}<br />
<br />
Moved to Wednesday (this week only)<br />
https://wiki.mozilla.org/Security/Meetings/SecurityAssurance/2013-10-23</div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-07-09&diff=674270Platform/2013-07-092013-07-09T18:20:58Z<p>Jesse: /* Roundtable */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
; Stability<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* Firefox multiple Betas in one week carries on, FF23.0b4 (Desktop) will ship this afternoon<br />
* Firefox 22 [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_22.0 Post-Mortem] was held this morning<br />
** There is no sign of a need for a .1 for this release<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 46 bugs]</big> <small>(37 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 48 bugs]</big> <small>(93 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Build Changes (gps)===<br />
<small>(Build changes of which engineers should be aware.)</small><br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
6.5 hour tree closure planned for Saturday, July 13 from 1200 PDT to 1830 PDT. Master tracker is {{bug|889996}}.<br />
<br />
Summary of work that will be done and the impact:<br />
<br />
* Failover of the new Bugzilla environment will be tested between data centers.<br />
** Impact: Bugzilla (bugs.mozilla.org) may experience brief interruptions in service during the window<br />
<br />
* Buildbot database failover will be tested.<br />
** Impact: trees will be closed, so no negative impact<br />
<br />
* http://build.mozilla.org will move to new releng web cluster<br />
** Impact: may experience a brief interruption in service to build.mozilla.org though none is expected; in addition the trees will be closed so there should be no impact to builds during this time<br />
<br />
* Database servers across the infrastructure will have their masters changed in preparation for upgrades<br />
** Impact: These failovers happen in a couple of seconds, some apps may fail queries during this time causing an HTTP 500 error or needing a client refresh<br />
<br />
* Backend load balancers in SCL3 will be upgraded from 1g to 10g network connectivity<br />
** Impact: some backend databases may experience a few seconds of service interruption, most of these services only impact developer/releng resources that will already be unavailable during the tree closure<br />
<br />
* RelEng firewalls changed to "deny all" for unknown internet traffic (has been allowed & logged).<br />
** Impact: No current tests will be affected (already whitelisted). New tests will be denied access to internet resources, developers will need to coordinate with sheriffs & releng prior to landing.<br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
;Shumway (jet)<br />
* Welcome Michael Bebenita, new Engineering Manager for Research Team (Shumway)<br />
* Shumway requires about:config changes to work well. See:<br />
** https://github.com/mozilla/shumway<br />
* Demo Videos:<br />
** http://www.youtube.com/watch?v=LE2LIFJBptE<br />
** http://www.youtube.com/watch?v=oe1diSzcFiU<br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Working on merging to mozilla-inbound<br />
<br />
===App Tools (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* Hello App Tools!<br />
<br />
===B2G Services (dougt)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Developer Tools (dcamp)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
Remote inspector patches still landing<br />
Investigating an issue with the profiler on metrofx<br />
<br />
===DOM (jst/dougt)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* {{Bug|885366}}: Permissions now displayed in the identity popup/doorhanger<br />
* {{bug|789348}}: we got rid of localstorage use in about:home, finally<br />
* [https://mail.mozilla.org/pipermail/firefox-dev/2013-July/000524.html Australis update]: still working on perf regressions blocking landing.<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* recent landings:<br />
** new crash reporting ui. ({{bug|831972}})<br />
** new start page grid layout / design landed.<br />
** front end polish: [http://scrumbu.gs/p/FireFox-Metro/ scrum IT10]<br />
** continued progress on Async Pan Zoom Controller. ({{bug|869940}})<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
*Patch landed for making fennec behave normally with widget scaling {{bug|803207}}<br />
*SkiaGL: Test-related fixes in the interest of landing in Fx25 {{Bug|885627}}, {{Bug|885623}}, {{Bug|887901}} and other great progress {{Bug|887927}}. More will be landing, soon.<br />
*RSS/Atom feed handling is shipping in Fx23 so finkle landed {{bug|888335}} - Remove support for iGoogle/Reader from feed subscriptions and {{bug|888327}} - Add support for adding feed subscriptions to cloud.feedly.com <br />
*Converging WebRTC: {{bug|874569}}, {{Bug|880437}} <br />
*Lot's of session restore-related landings: {{Bug|889554}}, {{Bug|886123}}, {{Bug|801412}}<br />
<br />
===Firefox OS Browser (blassey)===<br />
* backlog triaged into "scrum-ready" and need-info's for product, UX, l10n, etc.<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox OS Communications (scravag)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Firefox OS Devices/Porting (mchen)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* Last Week<br />
** 1.1 Blocker Bugs<br />
** Bluetooth porting on Bluedroid backend.<br />
*** Discovering is done.<br />
*** To implement the pairing function.<br />
** Assign resources to do JB porting<br />
*** Bug 890144 - Emulating SD Card on Nexus 4<br />
*** Bug 878108 - Support hardware decoding on gonk-JB<br />
*** Bug 871364 - Support camera on gonk-JB (Android 4.2) <br />
** To support the engineering mode issues from Helix.<br />
** To raise the concerns of choosing reference phone - Nexus 4 for Gonk-JB.<br />
* This Week<br />
** 1.1 Blocker Bugs<br />
** To support JB porting.<br />
* Blockers<br />
** None<br />
<br />
===Firefox OS Media Apps (hema)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
* Last Week<br />
** 1.1 bugs: 890394, 887968, 889233, 889238, 890394, 851626, 889167, 874011<br />
** start prototyping lockscreen music control use cases<br />
** finalized agenda for team meetup<br />
** music app prototype<br />
<br />
* This Week<br />
** 1.1 blocking bugs<br />
** tracking meta bug for 1.2 media related user stories (https://bugzilla.mozilla.org/show_bug.cgi?id=890945)<br />
** start work on music status user story for 1.2 (https://bugzilla.mozilla.org/show_bug.cgi?id=891014)<br />
** sync up with api team on inter app communication api and with system team on notification api - dependencies for music controls feature (https://bugzilla.mozilla.org/show_bug.cgi?id=891024)<br />
** ux requirements for image orientation (correction of tilt sensor inaccuracies) - (https://bugzilla.mozilla.org/show_bug.cgi?id=891030)<br />
<br />
* Blockers<br />
none<br />
<br />
===Firefox OS Media Recording (cjku)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
Last week<br />
*Media Recorder<br />
**Preliminary analysis phase<br />
***Write document for B2G HW decode diagram<br />
***Investigate B2G video encoding flow <br />
*WebAudio<br />
**{{bug|882171}} - Optimize the AudioNodeEngine.cpp routines for NEON<br />
*WebRTC<br />
**{{bug|869869}} - e10s for UDP socket<br />
**{{bug|881935}} - SDP: Support negotiation of video resolution<br />
**{{bug|881982}} - ICE: report error on network interface change<br />
**{{bug|881935}} - Support negotiation of video resolution<br />
**Performance evaluation on helix<br />
**Enable HW codec on B2G<br />
***Look into performance diff after using HW codec<br />
***Redirect coding flow into StageFright and using H.264 RTP packet formant.<br />
*Canvas 2D/SkiaGL<br />
**{{bug|869199}} Bad performance of fishie tank<br />
*HW Composer<br />
**{{bug|884188}} High power consumption of youtube<br />
*Prepare b2g GFX introduction tutorial document for new on boards.<br />
*Memory Shrinking<br />
**Analyzing the ratio of the near-read-only anonymous memories<br />
<br />
This week<br />
*Media Recorder<br />
**Preliminary analysis phase. Last week for analysis, move to design phase in the next.<br />
***Define how to create demultiplexer, which StageFright does not export API for this requirment.<br />
***Compare functionality difference between "mozCamera" and "MediaRecording + ImageCapture"<br />
*WebRTC<br />
**Keep fixing E10S and SDP issues.<br />
**Enable HW codec on B2G<br />
*HW Composer<br />
**{{bug|884188}}/{{bug|885345}} HWC can't render small layer due to no gralloc buffer<br />
<br />
===Firefox OS Performance (mlee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
* Last Week<br />
** [http://scrumbu.gs/t/fxos-dev-mlee/2013.06.28/ Sprint 2013.06.28]<br />
*** Completed previous week; closed 16 issues.<br />
*** MMS: Reference Workloads completed and available.<br />
*** Contacts: 887564, 888465, 888498, 884679<br />
*** Clock: 883239, 888007, 881738<br />
*** Camera: 884595<br />
*** Tools: 864751, 886524<br />
*** Other: 887652 (Notes+ GC OOM Support)<br />
** [http://scrumbu.gs/t/fxos-dev-mlee/2013.07.12/ Sprint 2013.07.12]<br />
*** Started but 1st week was only 3 days.<br />
<br />
* This Week<br />
** [http://scrumbu.gs/t/fxos-dev-mlee/2013.07.12/ Sprint 2013.07.12] in progress<br />
*** Calendar: Reference Workloads<br />
*** Contacts: 865750, 879299, 871823, 879698<br />
*** Email: 871826, 886446<br />
*** Music: 871827<br />
*** Profiling: 877522, 884079, 810526<br />
*** Other: 884394 (Notes+ Support)<br />
<br />
* Blockers<br />
** None<br />
<br />
===Firefox OS Productivity (doliver)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}} <br />
<br />
* Last Week<br />
** v1.1 blocking bug fixes: 781443, 813411<br />
** Continued work on porting the Thunderbird fake IMAP server into Gaia to improve email app testability<br />
** Started investigation on why automated Gaia UI tests are failing on Pandaboards<br />
<br />
* This Week<br />
** Productivity team is meeting in Vancouver this week to discuss and prioritize new features and other engineering work for the v1.2 release.<br />
<br />
* Blockers<br />
** None<br />
<br />
===Firefox OS Radio/Bluetooth/GPS (kenhkchang)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
*Last week<br />
**Fix blocked issues, {{bug|874273}}, {{bug|787442}}, {{bug|883746}}, {{bug|850140}}, {{bug|885679}}, {{bug|884238}}, {{bug|883019}}, {{bug|884829}}, and {{bug|880680}}.<br />
**CDMA - <br />
*** Call waiting/switching -[{{bug|822210}}], discuss the design with Gaia dev.<br />
*** OTASP - [{{bug|882983}}], to know what is OTASP.<br />
*** nsIDOMMozMobileCellInfo - [{{bug|882984}}], to provide CDMA cell infomation for geo. <br />
*** Network Mode - [{{bug|881862}}], Gaia dev. is implemeting. We need to provide options for WCDMA/GSM, GSM only, CDMA only, CDMA/Evdo.<br />
*** ECB Mode - [{{bug|887690}}](Gecko part), reviewing. <br />
*** CDMA Info Record - This information will be delivered by network.<br />
****[{{bug|882985}}], to get the more detail information from QC.<br />
****To get UX for Gaia parts.<br />
** Bluetooth - Implement the A2DP 1.2 (Advanced Audio Distribution Profile) [{{bug|807758}}], AVRCP (Audio/Video Remote Control Profile) [{{bug|834553}}], AVRCP 1.3 [{{bug|887623}}], and HFP 1.6 [{{bug|879196}}]<br />
**WAP Push(SI and SL)<br />
***To get UX for Gaia part.<br />
**OMA CP<br />
*** Discuss with partners and PM to know which items are able to be configured.<br />
**NFC<br />
***Study NFC code of what DT provide.<br />
**EAP-SIM<br />
***Send a design document to dev-b2g<br />
***To know the target device.<br />
*This week<br />
**Fix blocked issues, {{bug|885280}}, {{bug|890218}}, {{bug|887745}}, {{bug|890180}}, {{bug|875484}}, and {{bug|886765}}.<br />
**CDMA - To know and clarify the scopes of the following bugs. And if we get enough information, we will start to implement.<br />
*** Call waiting/switching -[{{bug|822210}}], discuss the design in Gaia part.<br />
*** RSSI - [{{bug|835237}}](gecko part), add relative signal information for CDMA/Evdo.<br />
*** OTASP - [{{bug|882983}}], to get the more detail information from QC.<br />
*** nsIDOMMozMobileCellInfo - [{{bug|882984}}], have provided a patch and wait for review.<br />
*** Network Mode - [{{bug|881862}}], Gaia dev. is implemeting.<br />
*** ECB Mode -<br />
****[{{bug|881863}}](Gaia part), to get the more detail information from QC. <br />
****[{{bug|887690}}](Gecko part), reviewing. <br />
** Bluetooth - Implement the A2DP 1.2 (Advanced Audio Distribution Profile) [{{bug|807758}}], AVRCP (Audio/Video Remote Control Profile) [{{bug|834553}}], AVRCP 1.3 [{{bug|887623}}], and HFP 1.6 [{{bug|879196}}]<br />
**WAP Push(SI and SL)<br />
***[{{bug|891249}}]Add fixed MSISDN sender number.<br />
***[{{bug|887157}}]Add Enable and Disable function.<br />
**OMA CP - have to be able to config following items.<br />
*** Modem, it should be owned by modem partner.<br />
*** APN settings - MMS and Browser.<br />
*** Voicemail settings, to get more detail information.<br />
*** Other voice related configuration, to get more detail information.<br />
**NFC<br />
***Study NFC code of what DT provide.<br />
***To study the BT secure paring protocol for NFC.<br />
**WPA-EAP <br />
***[{{bug|883741}}] To move Crypto to WebIDL<br />
<br />
===Firefox OS Systems - Front End (lucas)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Firefox OS Systems - Platform (timdream)===<br />
<!-- {{readonly}} --><br />
** Team is working on v1.1hd (bug 881126), expect to land all this week<br />
** System app engineering planning on-going<br />
<br />
===GFX (milan)===<br />
<br />
* OMTC on the Mac - on by default in Aurora, but will likely turn it back off in a week<br />
** Switching to IO surfaces<br />
* Skia rebase landed<br />
* WebGL 2 work started<br />
* rework of the texture host/client getting close to landing (cleaned up ownership model)<br />
* Core Graphics Moz2D in progress<br />
<br />
===Identity (jedp)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Persona Assertion + RTC PeerConnection is working yay. Focus on landing in m-c and persona github this week.<br />
* FirefoxOS Persona will support primary IdP delegation starting Wednesday<br />
<br />
Ongoing<br />
* FTE sign-in on FirefoxOS - still in design<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
Short week with July 1st as a Canadian holiday, July 4th as US holiday and July 5th as a Mozilla holiday.<br />
<br />
*Last Week<br />
** Compiler (JIT)<br />
*** {{bug|799122}}: Eagerly allocate dense elements for small arrays (10-12% win on Kraken audio-fft and audio-beat-detection)<br />
*** {{bug|889825}}: Allow eliminating more bounds checks (15% win on Kraken imaging-desaturate and 5% on audio-fft)<br />
*** {{bug|888872}}: Fix Ion to track slots/elements pointers for Generational GC (fixed Kraken)<br />
*** Added in two quick hacks to make the current assembler buffer usable for large asm.js modules.<br />
** Garbage Collection<br />
*** n/a<br />
** Front End and Other<br />
*** {{bug|886949}}: Add Number.parseInt and Number.parseFloat<br />
*This Week<br />
** Compiler (JIT)<br />
*** {{bug|864400}}: Optimize ModI for power-of-two divisor - 45% win on Kraken audio-oscillator<br />
** Garbage Collection<br />
*** {{bug|876029}}: re-Land faster memory pressure, by-pass the event queue<br />
*** {{bug|863398}}: re-Land improved GC settings for B2G<br />
** Front End and Other<br />
*** {{bug|890238}}: Memory reporter for ICU<br />
*Blockers<br />
** None<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
Adobe Hackathon this week. Hacking on various CSS work items.<br />
<br />
===Media (mreavy)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
-- {{readonly}} --<br />
* WebRTC:<br />
** Working with the FxOS UX team on getUserMedia (gUM) UX designs for B2G. We're targeting gUM on B2G for v1.2<br />
** Improving the patch on {{Bug|825112}}, which is blocking B2G audio work and media recording, and planning to land it this week.<br />
** Hoping to land the fix for bad audio latency/drift seen with 44100Hz mics, {{Bug|886886}}, by the end of this week.<br />
** Waiting on one audio fix in order to land the major update (the 3.30 branch) to the WebRTC.org import.<br />
* H.264 playback: Still expecting to land {{Bug|860599}} soon (within the next week or so) which fixes many of the H.264 crashes on Android.<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
* {{bug|888373}}: We're adding a new API to determine how the last browser session ended, take a look<br />
* [https://wiki.mozilla.org/Platform/2013-07-02#Performance_.28vladan.29 In-flight projects are in previous report]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
No updates due to short week.<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
* submitted proposal for FxOS manifest versioning<br />
* one r+ for temporary storage, one to go<br />
* DOM/WebAPI/Accessibility/Networking work week this week in Toronto<br />
** plans for NavigationController and appcache<br />
** plans for background services<br />
** necko + gecko = <3<br />
** worker APIs and cycle collector<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
Nothing particularly notable.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 4.00] (Previous Week: 4.73).<br />
* 18 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-07-01&f1=cf_last_resolved&query_format=advanced&list_id=7097326 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability metrics] continue to be pretty good across the board, mobile trunk has high crash rates mostly due to {{bug|890272}}, also because of {{bug|890515}}, both being worked on.<br />
* Looking for data on shipped Firefox OS devices, but not much found so far.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
* [action] lmandel to speak with Brendan Dahl about a PDF.js update for next week<br />
* Australis landing<br />
** Is it still likely to land for Nightly 25 (but be backed out for Aurora 25?)<br />
*** [gavin] Depends on how quickly we sort out perf issues<br />
*** See [https://mail.mozilla.org/pipermail/firefox-dev/2013-July/000524.html weekly Australis update] on [https://mail.mozilla.org/pipermail/firefox-dev/ firefox-dev]<br />
** Can a [https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches project branch] be used as the Australis "backout branch"?<br />
*** Yes<br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-07-09&diff=674264Platform/2013-07-092013-07-09T18:15:50Z<p>Jesse: /* Roundtable */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
; Stability<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* Firefox multiple Betas in one week carries on, FF23.0b4 (Desktop) will ship this afternoon<br />
* Firefox 22 [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_22.0 Post-Mortem] was held this morning<br />
** There is no sign of a need for a .1 for this release<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 46 bugs]</big> <small>(37 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 48 bugs]</big> <small>(93 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Build Changes (gps)===<br />
<small>(Build changes of which engineers should be aware.)</small><br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
6.5 hour tree closure planned for Saturday, July 13 from 1200 PDT to 1830 PDT. Master tracker is {{bug|889996}}.<br />
<br />
Summary of work that will be done and the impact:<br />
<br />
* Failover of the new Bugzilla environment will be tested between data centers.<br />
** Impact: Bugzilla (bugs.mozilla.org) may experience brief interruptions in service during the window<br />
<br />
* Buildbot database failover will be tested.<br />
** Impact: trees will be closed, so no negative impact<br />
<br />
* http://build.mozilla.org will move to new releng web cluster<br />
** Impact: may experience a brief interruption in service to build.mozilla.org though none is expected; in addition the trees will be closed so there should be no impact to builds during this time<br />
<br />
* Database servers across the infrastructure will have their masters changed in preparation for upgrades<br />
** Impact: These failovers happen in a couple of seconds, some apps may fail queries during this time causing an HTTP 500 error or needing a client refresh<br />
<br />
* Backend load balancers in SCL3 will be upgraded from 1g to 10g network connectivity<br />
** Impact: some backend databases may experience a few seconds of service interruption, most of these services only impact developer/releng resources that will already be unavailable during the tree closure<br />
<br />
* RelEng firewalls changed to "deny all" for unknown internet traffic (has been allowed & logged).<br />
** Impact: No current tests will be affected (already whitelisted). New tests will be denied access to internet resources, developers will need to coordinate with sheriffs & releng prior to landing.<br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
;Shumway (jet)<br />
* Welcome Michael Bebenita, new Engineering Manager for Research Team (Shumway)<br />
* Shumway requires about:config changes to work well. See:<br />
** https://github.com/mozilla/shumway<br />
* Demo Videos:<br />
** http://www.youtube.com/watch?v=LE2LIFJBptE<br />
** http://www.youtube.com/watch?v=oe1diSzcFiU<br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Working on merging to mozilla-inbound<br />
<br />
===App Tools (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* Hello App Tools!<br />
<br />
===B2G Services (dougt)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Developer Tools (dcamp)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
Remote inspector patches still landing<br />
Investigating an issue with the profiler on metrofx<br />
<br />
===DOM (jst/dougt)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* {{Bug|885366}}: Permissions now displayed in the identity popup/doorhanger<br />
* {{bug|789348}}: we got rid of localstorage use in about:home, finally<br />
* [https://mail.mozilla.org/pipermail/firefox-dev/2013-July/000524.html Australis update]: still working on perf regressions blocking landing.<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* recent landings:<br />
** new crash reporting ui. ({{bug|831972}})<br />
** new start page grid layout / design landed.<br />
** front end polish: [http://scrumbu.gs/p/FireFox-Metro/ scrum IT10]<br />
** continued progress on Async Pan Zoom Controller. ({{bug|869940}})<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
*Patch landed for making fennec behave normally with widget scaling {{bug|803207}}<br />
*SkiaGL: Test-related fixes in the interest of landing in Fx25 {{Bug|885627}}, {{Bug|885623}}, {{Bug|887901}} and other great progress {{Bug|887927}}. More will be landing, soon.<br />
*RSS/Atom feed handling is shipping in Fx23 so finkle landed {{bug|888335}} - Remove support for iGoogle/Reader from feed subscriptions and {{bug|888327}} - Add support for adding feed subscriptions to cloud.feedly.com <br />
*Converging WebRTC: {{bug|874569}}, {{Bug|880437}} <br />
*Lot's of session restore-related landings: {{Bug|889554}}, {{Bug|886123}}, {{Bug|801412}}<br />
<br />
===Firefox OS Browser (blassey)===<br />
* backlog triaged into "scrum-ready" and need-info's for product, UX, l10n, etc.<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox OS Communications (scravag)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Firefox OS Devices/Porting (mchen)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* Last Week<br />
** 1.1 Blocker Bugs<br />
** Bluetooth porting on Bluedroid backend.<br />
*** Discovering is done.<br />
*** To implement the pairing function.<br />
** Assign resources to do JB porting<br />
*** Bug 890144 - Emulating SD Card on Nexus 4<br />
*** Bug 878108 - Support hardware decoding on gonk-JB<br />
*** Bug 871364 - Support camera on gonk-JB (Android 4.2) <br />
** To support the engineering mode issues from Helix.<br />
** To raise the concerns of choosing reference phone - Nexus 4 for Gonk-JB.<br />
* This Week<br />
** 1.1 Blocker Bugs<br />
** To support JB porting.<br />
* Blockers<br />
** None<br />
<br />
===Firefox OS Media Apps (hema)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
* Last Week<br />
** 1.1 bugs: 890394, 887968, 889233, 889238, 890394, 851626, 889167, 874011<br />
** start prototyping lockscreen music control use cases<br />
** finalized agenda for team meetup<br />
** music app prototype<br />
<br />
* This Week<br />
** 1.1 blocking bugs<br />
** tracking meta bug for 1.2 media related user stories (https://bugzilla.mozilla.org/show_bug.cgi?id=890945)<br />
** start work on music status user story for 1.2 (https://bugzilla.mozilla.org/show_bug.cgi?id=891014)<br />
** sync up with api team on inter app communication api and with system team on notification api - dependencies for music controls feature (https://bugzilla.mozilla.org/show_bug.cgi?id=891024)<br />
** ux requirements for image orientation (correction of tilt sensor inaccuracies) - (https://bugzilla.mozilla.org/show_bug.cgi?id=891030)<br />
<br />
* Blockers<br />
none<br />
<br />
===Firefox OS Media Recording (cjku)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
Last week<br />
*Media Recorder<br />
**Preliminary analysis phase<br />
***Write document for B2G HW decode diagram<br />
***Investigate B2G video encoding flow <br />
*WebAudio<br />
**{{bug|882171}} - Optimize the AudioNodeEngine.cpp routines for NEON<br />
*WebRTC<br />
**{{bug|869869}} - e10s for UDP socket<br />
**{{bug|881935}} - SDP: Support negotiation of video resolution<br />
**{{bug|881982}} - ICE: report error on network interface change<br />
**{{bug|881935}} - Support negotiation of video resolution<br />
**Performance evaluation on helix<br />
**Enable HW codec on B2G<br />
***Look into performance diff after using HW codec<br />
***Redirect coding flow into StageFright and using H.264 RTP packet formant.<br />
*Canvas 2D/SkiaGL<br />
**{{bug|869199}} Bad performance of fishie tank<br />
*HW Composer<br />
**{{bug|884188}} High power consumption of youtube<br />
*Prepare b2g GFX introduction tutorial document for new on boards.<br />
*Memory Shrinking<br />
**Analyzing the ratio of the near-read-only anonymous memories<br />
<br />
This week<br />
*Media Recorder<br />
**Preliminary analysis phase. Last week for analysis, move to design phase in the next.<br />
***Define how to create demultiplexer, which StageFright does not export API for this requirment.<br />
***Compare functionality difference between "mozCamera" and "MediaRecording + ImageCapture"<br />
*WebRTC<br />
**Keep fixing E10S and SDP issues.<br />
**Enable HW codec on B2G<br />
*HW Composer<br />
**{{bug|884188}}/{{bug|885345}} HWC can't render small layer due to no gralloc buffer<br />
<br />
===Firefox OS Performance (mlee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
* Last Week<br />
** [http://scrumbu.gs/t/fxos-dev-mlee/2013.06.28/ Sprint 2013.06.28]<br />
*** Completed previous week; closed 16 issues.<br />
*** MMS: Reference Workloads completed and available.<br />
*** Contacts: 887564, 888465, 888498, 884679<br />
*** Clock: 883239, 888007, 881738<br />
*** Camera: 884595<br />
*** Tools: 864751, 886524<br />
*** Other: 887652 (Notes+ GC OOM Support)<br />
** [http://scrumbu.gs/t/fxos-dev-mlee/2013.07.12/ Sprint 2013.07.12]<br />
*** Started but 1st week was only 3 days.<br />
<br />
* This Week<br />
** [http://scrumbu.gs/t/fxos-dev-mlee/2013.07.12/ Sprint 2013.07.12] in progress<br />
*** Calendar: Reference Workloads<br />
*** Contacts: 865750, 879299, 871823, 879698<br />
*** Email: 871826, 886446<br />
*** Music: 871827<br />
*** Profiling: 877522, 884079, 810526<br />
*** Other: 884394 (Notes+ Support)<br />
<br />
* Blockers<br />
** None<br />
<br />
===Firefox OS Productivity (doliver)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}} <br />
<br />
* Last Week<br />
** v1.1 blocking bug fixes: 781443, 813411<br />
** Continued work on porting the Thunderbird fake IMAP server into Gaia to improve email app testability<br />
** Started investigation on why automated Gaia UI tests are failing on Pandaboards<br />
<br />
* This Week<br />
** Productivity team is meeting in Vancouver this week to discuss and prioritize new features and other engineering work for the v1.2 release.<br />
<br />
* Blockers<br />
** None<br />
<br />
===Firefox OS Radio/Bluetooth/GPS (kenhkchang)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
*Last week<br />
**Fix blocked issues, {{bug|874273}}, {{bug|787442}}, {{bug|883746}}, {{bug|850140}}, {{bug|885679}}, {{bug|884238}}, {{bug|883019}}, {{bug|884829}}, and {{bug|880680}}.<br />
**CDMA - <br />
*** Call waiting/switching -[{{bug|822210}}], discuss the design with Gaia dev.<br />
*** OTASP - [{{bug|882983}}], to know what is OTASP.<br />
*** nsIDOMMozMobileCellInfo - [{{bug|882984}}], to provide CDMA cell infomation for geo. <br />
*** Network Mode - [{{bug|881862}}], Gaia dev. is implemeting. We need to provide options for WCDMA/GSM, GSM only, CDMA only, CDMA/Evdo.<br />
*** ECB Mode - [{{bug|887690}}](Gecko part), reviewing. <br />
*** CDMA Info Record - This information will be delivered by network.<br />
****[{{bug|882985}}], to get the more detail information from QC.<br />
****To get UX for Gaia parts.<br />
** Bluetooth - Implement the A2DP 1.2 (Advanced Audio Distribution Profile) [{{bug|807758}}], AVRCP (Audio/Video Remote Control Profile) [{{bug|834553}}], AVRCP 1.3 [{{bug|887623}}], and HFP 1.6 [{{bug|879196}}]<br />
**WAP Push(SI and SL)<br />
***To get UX for Gaia part.<br />
**OMA CP<br />
*** Discuss with partners and PM to know which items are able to be configured.<br />
**NFC<br />
***Study NFC code of what DT provide.<br />
**EAP-SIM<br />
***Send a design document to dev-b2g<br />
***To know the target device.<br />
*This week<br />
**Fix blocked issues, {{bug|885280}}, {{bug|890218}}, {{bug|887745}}, {{bug|890180}}, {{bug|875484}}, and {{bug|886765}}.<br />
**CDMA - To know and clarify the scopes of the following bugs. And if we get enough information, we will start to implement.<br />
*** Call waiting/switching -[{{bug|822210}}], discuss the design in Gaia part.<br />
*** RSSI - [{{bug|835237}}](gecko part), add relative signal information for CDMA/Evdo.<br />
*** OTASP - [{{bug|882983}}], to get the more detail information from QC.<br />
*** nsIDOMMozMobileCellInfo - [{{bug|882984}}], have provided a patch and wait for review.<br />
*** Network Mode - [{{bug|881862}}], Gaia dev. is implemeting.<br />
*** ECB Mode -<br />
****[{{bug|881863}}](Gaia part), to get the more detail information from QC. <br />
****[{{bug|887690}}](Gecko part), reviewing. <br />
** Bluetooth - Implement the A2DP 1.2 (Advanced Audio Distribution Profile) [{{bug|807758}}], AVRCP (Audio/Video Remote Control Profile) [{{bug|834553}}], AVRCP 1.3 [{{bug|887623}}], and HFP 1.6 [{{bug|879196}}]<br />
**WAP Push(SI and SL)<br />
***[{{bug|891249}}]Add fixed MSISDN sender number.<br />
***[{{bug|887157}}]Add Enable and Disable function.<br />
**OMA CP - have to be able to config following items.<br />
*** Modem, it should be owned by modem partner.<br />
*** APN settings - MMS and Browser.<br />
*** Voicemail settings, to get more detail information.<br />
*** Other voice related configuration, to get more detail information.<br />
**NFC<br />
***Study NFC code of what DT provide.<br />
***To study the BT secure paring protocol for NFC.<br />
**WPA-EAP <br />
***[{{bug|883741}}] To move Crypto to WebIDL<br />
<br />
===Firefox OS Systems - Front End (lucas)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Firefox OS Systems - Platform (timdream)===<br />
<!-- {{readonly}} --><br />
** Team is working on v1.1hd (bug 881126), expect to land all this week<br />
** System app engineering planning on-going<br />
<br />
===GFX (milan)===<br />
<br />
* OMTC on the Mac - on by default in Aurora, but will likely turn it back off in a week<br />
** Switching to IO surfaces<br />
* Skia rebase landed<br />
* WebGL 2 work started<br />
* rework of the texture host/client getting close to landing (cleaned up ownership model)<br />
* Core Graphics Moz2D in progress<br />
<br />
===Identity (jedp)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Persona Assertion + RTC PeerConnection is working yay. Focus on landing in m-c and persona github this week.<br />
* FirefoxOS Persona will support primary IdP delegation starting Wednesday<br />
<br />
Ongoing<br />
* FTE sign-in on FirefoxOS - still in design<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
Short week with July 1st as a Canadian holiday, July 4th as US holiday and July 5th as a Mozilla holiday.<br />
<br />
*Last Week<br />
** Compiler (JIT)<br />
*** {{bug|799122}}: Eagerly allocate dense elements for small arrays (10-12% win on Kraken audio-fft and audio-beat-detection)<br />
*** {{bug|889825}}: Allow eliminating more bounds checks (15% win on Kraken imaging-desaturate and 5% on audio-fft)<br />
*** {{bug|888872}}: Fix Ion to track slots/elements pointers for Generational GC (fixed Kraken)<br />
*** Added in two quick hacks to make the current assembler buffer usable for large asm.js modules.<br />
** Garbage Collection<br />
*** n/a<br />
** Front End and Other<br />
*** {{bug|886949}}: Add Number.parseInt and Number.parseFloat<br />
*This Week<br />
** Compiler (JIT)<br />
*** {{bug|864400}}: Optimize ModI for power-of-two divisor - 45% win on Kraken audio-oscillator<br />
** Garbage Collection<br />
*** {{bug|876029}}: re-Land faster memory pressure, by-pass the event queue<br />
*** {{bug|863398}}: re-Land improved GC settings for B2G<br />
** Front End and Other<br />
*** {{bug|890238}}: Memory reporter for ICU<br />
*Blockers<br />
** None<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
Adobe Hackathon this week. Hacking on various CSS work items.<br />
<br />
===Media (mreavy)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
-- {{readonly}} --<br />
* WebRTC:<br />
** Working with the FxOS UX team on getUserMedia (gUM) UX designs for B2G. We're targeting gUM on B2G for v1.2<br />
** Improving the patch on {{Bug|825112}}, which is blocking B2G audio work and media recording, and planning to land it this week.<br />
** Hoping to land the fix for bad audio latency/drift seen with 44100Hz mics, {{Bug|886886}}, by the end of this week.<br />
** Waiting on one audio fix in order to land the major update (the 3.30 branch) to the WebRTC.org import.<br />
* H.264 playback: Still expecting to land {{Bug|860599}} soon (within the next week or so) which fixes many of the H.264 crashes on Android.<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
* {{bug|888373}}: We're adding a new API to determine how the last browser session ended, take a look<br />
* [https://wiki.mozilla.org/Platform/2013-07-02#Performance_.28vladan.29 In-flight projects are in previous report]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
No updates due to short week.<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
* submitted proposal for FxOS manifest versioning<br />
* one r+ for temporary storage, one to go<br />
* DOM/WebAPI/Accessibility/Networking work week this week in Toronto<br />
** plans for NavigationController and appcache<br />
** plans for background services<br />
** necko + gecko = <3<br />
** worker APIs and cycle collector<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
Nothing particularly notable.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 4.00] (Previous Week: 4.73).<br />
* 18 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-07-01&f1=cf_last_resolved&query_format=advanced&list_id=7097326 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability metrics] continue to be pretty good across the board, mobile trunk has high crash rates mostly due to {{bug|890272}}, also because of {{bug|890515}}, both being worked on.<br />
* Looking for data on shipped Firefox OS devices, but not much found so far.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
* [action] lmandel to speak with Brendan Dahl about a PDF.js update for next week<br />
* Australis landing<br />
** Is it still likely to land for Nightly 25 (but be backed out for Aurora 25?)<br />
*** [gavin] Depends on how quickly we sort out perf issues<br />
** Can a [https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches project branch] be used as the Australis "backout branch"?<br />
*** Yes<br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667986Platform/2013-06-182013-06-18T18:23:42Z<p>Jesse: /* Seceng (mmc) */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
** jst to follow-up with ctalbert and bmoss.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
** RyanVM to file tracking bug for looking into this.<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
** Ready to land, but waiting to land after a branch point<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to land soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
* Firefox desktop team will be having a frontend-perf-focused work week in Toronto next week<br />
* Status update on the new Downloads API: [https://groups.google.com/forum/?fromgroups=&hl=en#!topic/firefox-dev/PNSf1BI3Em8]<br />
* dev.platform post about background tab thumbnailing: [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/OdXL_fX9Rjk]<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
* {{bug|882196}} - Android crash in nsXPCWrappedJS::AddRef top crash (23%) landed yesterday, hasn't made it to nightly yet<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
* New cache code: integrating & debugging initial API and filesystem patches<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in MV Bridge (Mon-Wed) and SF (Thur). Drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
* Lots of big landings planned for "right after Firefox 24 branches"<br />
** XBL refactor, Australis, "major update of WebRTC.org import"<br />
** Can we land these a day apart so each one gets its own Nightly? (For more useful regression ranges, and avoiding pileups that decrease Nightly testing)<br />
* [akeybl] FFOS 1.2 is targeting Gecko 27ish. Have we looked at WebRTC, gUM, audio recording, etc. on a device? Or should we plan to disable and place on the product roadmap?<br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667979Platform/2013-06-182013-06-18T18:18:47Z<p>Jesse: /* Roundtable */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
** jst to follow-up with ctalbert and bmoss.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
** RyanVM to file tracking bug for looking into this.<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
** Ready to land, but waiting to land after a branch point<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to land soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
* Firefox desktop team will be having a frontend-perf-focused work week in Toronto next week<br />
* Status update on the new Downloads API: [https://groups.google.com/forum/?fromgroups=&hl=en#!topic/firefox-dev/PNSf1BI3Em8]<br />
* dev.platform post about background tab thumbnailing: [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/OdXL_fX9Rjk]<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
* {{bug|882196}} - Android crash in nsXPCWrappedJS::AddRef top crash (23%) landed yesterday, hasn't made it to nightly yet<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
* New cache code: integrating & debugging initial API and filesystem patches<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
* Lots of big landings planned for "right after Firefox 24 branches"<br />
** XBL refactor, Australis, "major update of WebRTC.org import"<br />
** Can we land these a day apart so each one gets its own Nightly? (For more useful regression ranges, and avoiding pileups that decrease Nightly testing)<br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667978Platform/2013-06-182013-06-18T18:17:56Z<p>Jesse: /* Roundtable */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
** jst to follow-up with ctalbert and bmoss.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
** RyanVM to file tracking bug for looking into this.<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
** Ready to land, but waiting to land after a branch point<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to land soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
* Firefox desktop team will be having a frontend-perf-focused work week in Toronto next week<br />
* Status update on the new Downloads API: [https://groups.google.com/forum/?fromgroups=&hl=en#!topic/firefox-dev/PNSf1BI3Em8]<br />
* dev.platform post about background tab thumbnailing: [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/OdXL_fX9Rjk]<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
* {{bug|882196}} - Android crash in nsXPCWrappedJS::AddRef top crash (23%) landed yesterday, hasn't made it to nightly yet<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
* New cache code: integrating & debugging initial API and filesystem patches<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
* Lots of big landings planned for "right after Firefox 24 branches"<br />
** XBL refactor, Australis<br />
** Can we land these a day apart so each one gets its own Nightly? (For more useful regression ranges, and avoiding pileups that decrease Nightly testing)<br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667971Platform/2013-06-182013-06-18T18:14:29Z<p>Jesse: /* DOM (jst/dougt) */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
** jst to follow-up with ctalbert and bmoss.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
** RyanVM to file tracking bug for looking into this.<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
** Ready to land, but waiting to land after a branch point<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to land soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
* Firefox desktop team will be having a frontend-perf-focused work week in Toronto next week<br />
* Status update on the new Downloads API: [https://groups.google.com/forum/?fromgroups=&hl=en#!topic/firefox-dev/PNSf1BI3Em8]<br />
* dev.platform post about background tab thumbnailing: [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/OdXL_fX9Rjk]<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
* {{bug|882196}} - Android crash in nsXPCWrappedJS::AddRef top crash (23%) landed yesterday, hasn't made it to nightly yet<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
* New cache code: integrating & debugging initial API and filesystem patches<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667969Platform/2013-06-182013-06-18T18:12:58Z<p>Jesse: /* JS (naveed) */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
** jst to follow-up with ctalbert and bmoss.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
** RyanVM to file tracking bug for looking into this.<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to land soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
* Firefox desktop team will be having a frontend-perf-focused work week in Toronto next week<br />
* Status update on the new Downloads API: [https://groups.google.com/forum/?fromgroups=&hl=en#!topic/firefox-dev/PNSf1BI3Em8]<br />
* dev.platform post about background tab thumbnailing: [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/OdXL_fX9Rjk]<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
* New cache code: integrating & debugging initial API and filesystem patches<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667967Platform/2013-06-182013-06-18T18:12:36Z<p>Jesse: /* Mailing List Threads */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
** jst to follow-up with ctalbert and bmoss.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
** RyanVM to file tracking bug for looking into this.<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Australis still on track to land soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
* Firefox desktop team will be having a frontend-perf-focused work week in Toronto next week<br />
* Status update on the new Downloads API: [https://groups.google.com/forum/?fromgroups=&hl=en#!topic/firefox-dev/PNSf1BI3Em8]<br />
* dev.platform post about background tab thumbnailing: [https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.platform/OdXL_fX9Rjk]<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
* New cache code: integrating & debugging initial API and filesystem patches<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667959Platform/2013-06-182013-06-18T18:08:51Z<p>Jesse: /* Hot Bugs */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
* OSX "code -20" test failures.<br />
** "Code -20" (SIGCHLD) is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-18&diff=667958Platform/2013-06-182013-06-18T18:07:53Z<p>Jesse: /* Hot Bugs */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* No activity in {{bug|874647}} (Find and fix the underlying cause of the Windows XP xpcshell hangs) since it was filed 4 weeks ago. Test suite will be disabled this week.<br />
* OSX "code -20" test failures.<br />
** "Code -20" is an IPC thing that can happen to the parent process after a child process quits<br />
** Currently [https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6861853&short_desc=code%20-20&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&short_desc_type=allwordssubstr 38] bugs on file. Under-represents occurrences as each failure is not always filed.<br />
** Aborts test suite.<br />
** If not a fatal error, can test runner not treat it as such?<br />
*** Or automatically star & retrigger?<br />
; Stability<br />
* {{bug|878449}} - aurora windows topcrash in CCliModalLoop::CCliModalLoop needs help (bbondy can't reproduce)<br />
* {{bug|882433}} - nightly topcrash at js::ion::InlineFrameIteratorMaybeGC needs an owner<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b6 went to build yesterday<br />
** Desktop may ship today<br />
** [tbd] Mobile may need to respin due to {{bug|884300}} – CFI records broken on Linux platforms<br />
* FF22.0 RC went to build overnight<br />
** [tbd] Mobile may need a respin<br />
** No issues on the tracking list that are worrisome; please email early and often if you find something possibly critical (esp. 22 regressions)<br />
* I'd like to hijack this section and direct your attention to [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/s9OW1ZBG7PE "Changing our Standard for Bug Verification"] on dev.planning (>80 posts, go bottom up)<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 51 bugs]</big> <small>(45 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 3 bugs]</big> <small>(22 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* B2G option for installing additional extensions in DEBUG mode landed ({{Bug|879563}}).<br />
* Looking into automated tests for Gaia a11y. (Eitan + Web QA)<br />
* Max's recent braille improvements landed ({{Bug|876475}}).<br />
* Marco Zehe will keynote day 2 (tomorrow) at the PDF Association’s second Technical Conference.<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-06-11#Minutes Last week's meeting]<br />
* [http://jsantell.com/post/places-api-proposal Places API proposal]<br />
* Websockets support coming real soon<br />
* Getting repacks uploaded to AMO {{bug|881387}}<br />
<br />
===B2G Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===B2G Services (dougt)===<br />
* Push notifications will land on desktop soon (q2 goal)<br />
** Will be disabled on Beta+Release until CR or interop<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp/robcee)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Back end of Remote Inspector Landing.<br />
* Back end for Break on DOM in Debugger landing.<br />
<br />
===DOM (jst/dougt)===<br />
* Update on the XBL Refactoring (Blake)<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Australis still on track to soon (beginning of the 25 train)! [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build] and file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&blocked=australis&status_whiteboard=%5BAustralis%3AM%3F%5D bugs]!<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
{{readonly}}<br />
* [http://teamstat.us/#browse/irc.mozilla.org/windev team status updates]<br />
* Continued work on front end polish<br />
* improvements to chrome input selection<br />
* progress being made on getting dev tools/profiler hooked up. ({{bug|850019}})<br />
* Currently hooking up Async Pan Zoom Controller to Metro in ({{bug|849266}} and {{bug|801154}}), Desktop Wiin32 to follow<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* 4 contributors, 7 bugs fixed fixed and 3 are in progress \o/: {{bug|867567}}, {{bug|871524}}, {{bug|877783}}, {{bug|876485}}, {{bug|684380}},{{bug|880661}}, {{bug|802093}}, {{bug|88059}}, {{bug|879088}}, {{bug|877774}} <br />
* We are getting very close to preffing WebRTC {{bug|881875}} on for Android, looks like we need {{Bug|882136}} first, though <br />
* Fixed and uplifted through beta: {{Bug|879651}} - no audio playback on x86<br />
* Thank you, :tn for the fix for {{Bug|876562}} - In Fennec content behind fullscreen content should not be pannable, zoomable, or visible which was uplifted through beta. *Please* test Dynamic URL bar in Fx23 as much as you can.<br />
<br />
===Firefox OS (sicking)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* See [https://wiki.mozilla.org/Platform/2013-06-11#GFX_.28milan.29 previous week]<br />
<br />
===Identity (jedp)===<br />
Ongoing:<br />
* rtc peer connection + persona auth [rseys, jedp]<br />
* firefoxos + persona [ozten, jedp]<br />
* first-time sign-in to firefoxos [skinny, ozten, jedp]<br />
<br />
GSOC Intern<br />
* Akshay Katyal [MrDHat] working on a PiCl client for contacts data sync for firefoxos [mentor=jedp]<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
DONE<br />
* Compiler (JIT)<br />
** {{bug|866878}}: BaselineCompiler: Compile try-finally<br />
<br />
* Garbage Collection<br />
** {{bug|877762}}: GC: Post-barrier cycle collector participants <br />
<br />
* Front End and Other<br />
** {{bug|860838}}: Optimize asm.js FFI calls<br />
** [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink Blog post]<br />
** Finished build/run harness for performance-cliff benchmarks<br />
<br />
DOING <br />
* Compiler<br />
** {{bug|881902}}: Last big part of interpreter stack refactoring - fallout from JM removal<br />
<br />
* Front End and Other <br />
** {{bug|883154}}: Add runtime wide cache for compiled lazy scripts<br />
** Continue prototyping a shared memory implementation for asmjs, with the goal of running an extremely simple threaded program<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}}<br />
* Bugs of interest that landed:<br />
** SVG images are no longer fuzzy when tiled and scaled ({{bug|600207}})<br />
** DOM futures support landed ({{bug|856410}}) - some new CSSOM APIs depend on this<br />
** strongly-typed conversions between coordinate systems ({{bug|880676}})<br />
<br />
===Media (mreavy)===<br />
<br />
* Web Audio work is mostly done, only a few bits of the API remain to be implemented.<br />
* Ehsan has mostly moved away from the Web Audio work, padenot, rillian, karlt and others are helping to finish the rest of the project.<br />
* Basic WebVTT support landed behind a pref. You can test <track> in Nightly now!<br />
* Created [[WebVTT]] wiki page for status and getting-started links.<br />
* This week the WebVTT team is working on adding tests, fixing nits, and planning implementation of the revised WebVTTCue API.<br />
* MediaEncoder interface landed and confirmed to be recording Opus files ([https://bugzilla.mozilla.org/show_bug.cgi?id=868962 Bug 868962]). [https://bugzilla.mozilla.org/show_bug.cgi?id=879688 Bug 879688] tracks all the MediaEncoder work.<br />
* Identified a major cause of growing audio latency in WebRTC (including B2G) on some machines (but not others); working on a solution in {{bug|884365}}<br />
* Temporarily running WebRTC as root on B2G (until E10S changes land) causes performance issues (thread-priority and switching).<br />
* Planning to land major update of WebRTC.org import as soon as 25 opens; already tested on Desktop and B2G. {{Bug|880879}}<br />
<br />
===Necko (dougt/jduell)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* {{bug|497003}}: Off-main thread OnDataDelivery patch bounced: working on fix<br />
** doesn't work if content is gzipped: that will be follow-up. Also followups to support XHR workers, Download manager, imglib<br />
* {{bug|784575}}, {{bug|871452}}: Starting work to allow network traffic to be measured (and choked off to wifi-only) on a per-app basis.<br />
* {{bug|881804}}: Adding interface for speculatively doing DNS and/or prewarming TCP connections based on previous history. In API/design phase.<br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
<br />
* {{bug|853388}}: Add-on manager refactor will tentatively land next week<br />
* {{bug|863475}}: Integrated ARM EXIDX stack unwinding into Breakpad<br />
* {{bug|867762}}: Patch to track all main-thread I/O in profiler has landed. To try it out:<br />
** 1. Stop the profiler<br />
** 2. Make sure that "Main Thread I/O" is checked in the profiler pop-out panel<br />
** 3. Start the profiler<br />
** [http://dblohm7.ca/images/iomarkers.png Sample screenshot]<br />
* Telemetry server backend redesign:<br />
** [https://etherpad.mozilla.org/telemetry-reboot Overview of the work]<br />
** [https://github.com/mreid-moz/telemetry-server telemetry-server github repo]<br />
** [https://github.com/mreid-moz/telemetry-server/blob/master/StorageFormat.md new Telemetry data storage format]<br />
* {{bug|813742}}: Work continues on improving reftest and crashtest suites<br />
* {{bug|883253}}: Investigating potential benefits of using new "volatile ranges" kernel feature on B2G/Android<br />
* {{bug|848358}}: Work continues on Talos regression teststar for tab animation smoothness<br />
* {{bug|865389}}: Adding file "read-ahead" flags to OS.File<br />
<br />
<br />
Blog posts:<br />
<br />
* Aaron Klotz: [http://dblohm7.ca/blog/2013/06/12/detecting-main-thread-i-slash-o-with-sps/ Detecting Main Thread I/O with SPS]<br />
* Irving Reid: [http://www.controlledflight.ca/2013/06/17/add-on-manager-progress-almost-done/ Add-on Manager progress: Almost done!]<br />
<br />
===Seceng (mmc)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Team workweek this week in Bridge, drop by and say hi!<br />
* Sandboxing planning for Q3 going on as we speak (DRI: imelven)<br />
* Please come: Web Security 1.0 training at 12:15 in MTV 10 Forward (DRI: tvyas, rforbes)<br />
** https://air.mozilla.org/web-security-training/<br />
<br />
===WebAPI (overholt)===<br />
{{readonly}}<br />
<br />
Last week:<br />
* patches for IDB temporary storage up for review<br />
* continued work on Promises<br />
* W3C AC meeting<br />
* spec work: Telephony, Fetch, Promises, icons-in-manifests<br />
* WebAPI documentation review<br />
<br />
This week:<br />
* get up to speed with NavigationController<br />
* more work on DataStore API<br />
* review of sync IDB patches<br />
* spec work: Telephony, Fetch, Promises, Keyboard API<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
===Memshrink (njn)===<br />
<br />
A big week.<br />
<br />
* Brian Hackett enabled [https://bugzilla.mozilla.org/show_bug.cgi?id=678037 lazy bytecode]. This avoids generating bytecode (and subsequent objects, shapes and strings) for unexecuted JS functions, which in practice is ~50% of them due to websites' extensive use of libraries such as jQuery. Reduces Firefox's memory consumption by ~5% on common workloads, and significantly reduces pressure on the GC.<br />
<br />
* Nils Maier implemented [https://bugzilla.mozilla.org/show_bug.cgi?id=846019 separate measurement of add-on compartments in about:memory]. This doesn't catch all add-on memory consumption, but it gets a lot of it, especially for JetPack add-ons. People have been wanting this for *years*.<br />
<br />
* The report on [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink's 2nd birthday] includes an updated MemShrink "big ticket items" list. Three old items were crossed off, and three new ones added. Better image handling and generational GC are still #1 and #2, though both have made good progress.<br />
<br />
* [https://blog.mozilla.org/nnethercote/2013/06/15/memshrinks-2nd-birthday/ MemShrink progress report, week 103-104]. Future progress reports will now be every four weeks, rather than every two weeks.<br />
<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 6.36] (Previous Week: 4.10).<br />
* 15 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-06-11&f1=cf_last_resolved&query_format=advanced&list_id=6861825 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* [http://arewestableyet.com/ Stability numbers] continue to look good.<br />
* Trunk saw a number of new crashes in the last days, mostly fixed by now, see [[CrashKill/2013-06-17#Trunk|yesterday's stability meeting]].<br />
* {{Bug|884300}} is an issue that gives us bogus stacks on Linux, including Android, at least on 22 and higher. If you looked at crash stacks recently, be aware of that and re-check once this is fixed.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small></div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-04&diff=663264Platform/2013-06-042013-06-04T18:08:58Z<p>Jesse: /* DOM (jst/dougt) */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* {{bug|876068}} - B2G Windows desktop builds mostly fail, after a "C:\Tools\sdks\v7.0\include\winnt.h(135) : fatal error C1189: #error : 'No Target Architecture'".<br />
** Affects all dep builds. Do we even need these builds?<br />
** Please check with Gaia team before disabling these. I would expect them to be needed. (sicking)<br />
; Stability<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b4 is going to build EOD (mobile may be decoupled)<br />
* We're now more than halfway through the Beta cycle - it's due or die if you've got a tracked bug at this point <br />
* Our most concerning FF22 issues right now are new crash regressions<br />
** {{bug|867226}} – Incomplete framebuffer abort in mozilla::layers::LayerManagerOGL::CreateFBOWithTexture with "error 0x8cdd"<br />
** {{bug|853774}} – crash in imgRequest::GetStatusTracker<br />
** {{bug|863313}} – crash in mozilla::gl::GLContextEGL::MakeCurrentImpl @ libEGL_VIVANTE.so@0x5... with Vivante GC400 or GC800 core running ICS<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 47 bugs]</big> <small>(37 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 30 bugs]</big> <small>(43 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
* Nothing currently planned.<br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
UCOSP - the Undergraduate Capstone Open Source Project - is a final-year credit project for undergrads across Canada, who'll be working in small, geographically distributed teams. We'll be hosting their code sprint in mid-September, but the time to start thinking about projects is much sooner than that! <br />
<br />
Mike Hoye will talk about this for two minutes, just to put the idea in your heads.<br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}}--><br />
Among other things:<br />
* Making excellent progress on adding and polishing braille support (Max Li (intern))<br />
* Implementing a way for Gaia to pull in default extensions via build system. (Eitan)<br />
* Attacking our known test run asserts. (Trevor)<br />
* Deep in debugging life cycle and text bugs. (Alexander)<br />
* Some travel/evangelism in Germany. (Marco)<br />
* Built in screen reader improvements. (Eitan, Yura (volunteer), Marco)<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Kayaking at JSConf<br />
* Last week's [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-05-28#Minutes meeting minutes]<br />
* Places API is nearly done<br />
* Toolbar buttons, sidebars and toolbars APIs are in progress. Coordinating with Australis team<br />
<br />
===Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* New [https://wiki.mozilla.org/Simulator/FirefoxIntegration/ mockups and planning] for integrating the app manager into Firefox<br />
<br />
===B2G Services (dougt/mmayo)===<br />
* Push Notifications<br />
** B2g 1.1<br />
** Android<br />
** Desktop<br />
* Proxy Services<br />
** Email<br />
** Calendar<br />
* Where is my phone<br />
* Location database<br />
** https://wiki.mozilla.org/Services/Location/Roadmaps<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Last devtools meeting: https://etherpad.mozilla.org/ep/pad/view/devtools-meeting/jKxwbHYJDZ<br />
* The browser console has been enabled by default, bugs will get high priority.<br />
* Content process debugging is underway: {{bug|797627}} - review requests will hit other teams, please keep an eye out.<br />
* Remote inspector is progressing: {{bug|remote-inspector}}<br />
<br />
===DOM (jst/dougt)===<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=850065 Incremental cycle collector] (mccr8)<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=845545 Cycle collector per DOM worker thread] (khuey)<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=841442 One Node left to convert to new bindings] (baku)<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=653881 XBL Refactor - May break things]<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
;Last week<br />
* Australis<br />
** Continued work on customization and tabs styling ({{bug|874819}}, {{bug|867675}}, {{bug|875946}}) - see root meta bugs {{bug|732583}} and {{bug|872617}} <br />
** Milestone 6 completes tomorrow. We've got almost all of the customizable widgets done (bookmarks widget and character encoding widget are the two big missing pieces).<br />
** User research team is going to do some focus groups with users on or around June 10th to see what people think of the design.<br />
** Still on track to ship in 25 cycle<br />
** [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build], and please file bugs! Dupes are cheap.<br />
*** For tab related bugs, please file them blocking australis-tabs, and put [Australis:M?] in the whiteboard<br />
*** For toolbar or customization bugs, please file them blocking australis-cust and put [Australis:M?] in the whiteboard<br />
*** For bugs that don't fall into either category, but seem Australis-related, file them blocking australis and put [Australis:M?] in the whiteboard.<br />
<br />
* Performance<br />
** New API added to be able to track reflows ({{bug|453650}})<br />
** Many improvements to new tab opening/preloading to avoid unnecessary layout reflow ({{bug|878801}})<br />
** Tracked down remaining form-history synchronous SQLite users ({{bug|876002}})<br />
* Social<br />
** Landed various fixes to support use of WebRTC in social panels ({{bug|821073}}, {{bug|805684}}, {{bug|836766}}), make social debugging easier ({{bug|820601}})<br />
;Next week<br />
* Australis<br />
** continued work, particularly on customization (new widgets, interaction)<br />
* Performance<br />
** enable new tab page pre-loading<br />
** fix sync's use of old form history API<br />
** determine plan for enabling background tab thumbnailing<br />
;Blocked on<br />
* N/A<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Last week:<br />
** [http://teamstat.us/#browse/irc.mozilla.org/windev team-status] [http://scrumbu.gs/p/FireFox-Metro/ scrum]<br />
** Lots of bug fixes/improvements on front end UI.<br />
** New default browser telemetry added for all platforms (BROWSER_IS_USER_DEFAULT)<br />
** APZC prelim investigation / syncup with other teams<br />
** Software updating from Metro (note addon compat check issue in {{bug|794937}})<br />
* Continuing:<br />
** More front end bug fixes, theming, and polish.<br />
** Sorting out issues with browser registration for automated tests ({{bug|864940}})<br />
** APZC<br />
* Misc:<br />
** Adding a new front end team member (emtwo / Toronto)<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* gfx::Point, gfx::Rect, and gfx::Size can now be typed with units at compile-time. See {{bug|865735}} for initial landing and {{bug|877728}} as an example of how to use it. Some explanation also at https://staktrace.com/spout/entry.php?id=799. Relevant files are at layout/base/Units.h and gfx/2d/{Point,Rect}.h and will be fleshed out as more stuff is converted to be typed.<br />
* {{bug|867517}} Gecko-based WebView for Android landed <br />
** Still need to figure out how we're going to package it for 3rd parties<br />
* {{bug|877203}} New fonts for content (Clear Sans) landed and bounced, may need help figuring out reftest failures<br />
* {{bug|866957}} Collect and report cell tower and WiFi AP info, landed behind a pref<br />
* ANRs (Android chrome-hangs) have been reduced from 21.6 reports/day for first 3 weeks of 23 nightly, down to 13.8 reports/day for first 3 weeks of 24 nightly (36% decrease). This can be attributed to our new ANR reporter and focus on fixing those hangs.<br />
* {{bug|862377}} UI for WebRTC has landed in nightly, which means we plan to turn WebRTC support on by default in Fx24<br />
* {{bug|878123}} and {{bug|878868}} we plan to start shipping x86 support in Beta<br />
<br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Back from a joint "rendering" [https://intranet.mozilla.org/Web_Rendering_Work_Week_May_2013 work week] in Taipei<br />
* Active [https://wiki.mozilla.org/Platform/GFX#Development_Planning work]:<br />
** off main thread image animation<br />
** D2D 1.1<br />
** SkiaGL<br />
** joint work on async pan-zoom on mobile; sorting out metro<br />
<br />
===Identity (jedp)===<br />
<br />
Overview<br />
<br />
* The Native team in Identity is Jed, Austin King, and Zach Carter (50% time)<br />
* Primary efforts: b2g, desktop firefox, WebRTC<br />
* Austin King is working on Persona sign-in to browser UI<br />
* Jed is working on b2g and desktop<br />
* Zach will help out on b2g with device sign-in, looking ahead to picl and identity-attached services<br />
* Ryan Seys joins Identity as a Summer intern, working on Persona auth for WebRTC<br />
** Have met with ekr and bbrittain<br />
* Austin, Jed, and Crystal Beasley (aka Skinny) mini work weekend Friday thru Sunday for native desktop<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
*DONE<br />
**ARM raytrace regression fixed - bug<br />
**JS h264 decoder memory utlization bug fixed<br />
**Exact rooting fuzz bugs<br />
**Started ES6 self-hosted Arrays extras<br />
**Work on getting --ion-eager switch in the browser for fuzzers.<br />
**Landed in inbound a script to import selected subsets (ch06/, intl402/) of ECMAScript's test262 suite, those tests to run every push; landed those subsets in inbound.<br />
**Closed ({{bug|831507 }}) - Adding GGC post-write barriers to baseline compiler code generation.<br />
**Put more work on a well-commented pseudo-implementation of ES6 module loaders. You can see it here: https://people.mozilla.com/~jorendorff/js-loaders/loaders.html<br />
<br />
*DOING<br />
**Increase FFI asm.js call performance<br />
**Static rooting analysis precision improvements<br />
**Green GGC on tbpl <br />
**Implement proxy [[invoke]] trap ({{bug|878605 }})<br />
**Removing unneeded #includes in SpiderMonkey in the hope of speeding up compile times (bug https://bugzilla.mozilla.org/show_bug.cgi?id=634839).<br />
**clean-up memory pressure patches. ({{bug|876029 }}) & ({{bug|869263 }})<br />
**find regression on Sunspider (between May 21st to 29th)<br />
**Bug 878992 - Remove unused TypeObject flag OBJECT_FLAG_UNINLINEABLE which was only relevant for now-defunct JM.<br />
**Bug 859609 - Enable inlining of anonymous lambdas and functions-which-use-their-scope-chains in Ion.<br />
**Begin Asm.js parser<br />
<br />
*BLOCKS<br />
**({{bug|877261 }}) -> ({{bug|869740 }}) -> exactly rooted browser<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* (two weeks ago) we met, with Graphics and Media, in Taipei<br />
* a bunch of the team (dbaron, fantasai, jet, jdaggett, SimonSapin, heycam) at SVG and CSS Working Group meetings this week<br />
* off main thread animations finally has some test coverage, or will very soon ({{bug|788549}}), which is a step towards enabling it on non-B2G platforms<br />
* zoom-in and zoom-out values of CSS cursor property now unprefixed ({{bug|772153}})<br />
* major ongoing projects:<br />
** making CSS Flexbox paginate correctly (so pages using it will print) ({{bug|811024}})<br />
** starting to investigate implementing overflow:fragments ({{bug|874238}})<br />
<br />
===Media (mreavy)===<br />
* WebRTC's first implementation will be going out in Fx 22 Desktop. We believe all release blockers have been eliminated in Beta 4.<br />
** Actively looking at Bug 879213 - occasional audio-only latency issue, where audio noticeably lags video (it may be more common in certain network situations or environments). We believe it affects all products (desktop and mobile).<br />
** TURN support (http://tools.ietf.org/html/rfc5766) is coming in Fx 23.<br />
* Working with the team in Taipei to get WebRTC working on B2G<br />
* WebRTC's work week is next week in Sunnyvale (10 mins from the MV office)<br />
* Ben Brittain is the new intern for WebRTC. He is working on hooking up WebRTC to telemetry<br />
* Made good progress on improving H.264/MP4 playback performance on Win 7/8. There are 2 known bugs related to H.264/MP4 playback:<br />
** Bug 875644 - HE-AAC doesn't work properly (HE-AAC is not very common yet on the web)<br />
** Bug 879099 - Minor regression with color saturation on Nvidia<br />
* Close to finishing gstreamer backend for Linux to enable H.264 playback, but B2G work is taking priority this week<br />
* On track to deliver the first part of MSE (Media Source Extensions) by end of the month (i.e. a first phase of adaptive streaming [chunked multi-bitrate/resolution streaming] support that enables DASH-JS)<br />
* roc: Fixed a few video controls bugs affecting YouTube last week. People are now working on a few different video playback issues with the Youtube app, hoping to have them fixed this week.<br />
<br />
===Necko (dougt/jduell)===<br />
* Update on Disk Cache rewrite (jduell)<br />
* ODA off main thread (sworkman)<br />
* Http2, for real (patrick)<br />
* Fixing youtube hang on B2G<br />
<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* Dhaval Giani is our new intern. He'll be working on adding transparent compression to ext4.<br />
* Avi Halachmi landed VSync support on Windows ({{bug|856427}}). He's now working on improving Talos animation tests ({{bug|854746}} + {{bug|845943}})<br />
* Aaron Klotz is working on a patch to report main-thread NSPR & SQLite I/O to the profiler ({{bug|867762}})<br />
* Irving and Felipe are re-factoring the Addon Manager to store configuration in JSON files instead of SQLite DBs + move I/O operations off the main thread ({{bug|853388}} + {{bug|853389}}).<br />
** [http://www.controlledflight.ca/2013/05/31/saving-browser-state-asynchronously/ Irving's blog post]<br />
* Yoric added a warning when storing prefs >16kb ({{bug|872981}})<br />
* Yoric is working with ttaubert to refactor session store ({{bug|874381}})<br />
* Yoric is working on a pure-async mozIStorageAsyncConnection ({{bug|702559}})<br />
** [http://dutherenverseauborddelatable.wordpress.com/2013/05/24/project-async-responsive-issue-2/ Yoric's blog post]<br />
* Nathan Froyd is working on a new client-side Telemetry design<br />
* Glandium has been making improvements to build. He's moving to Japan, resuming work as contractor on June 25th.<br />
* Julian Seward is working on multi-threaded stack unwinding on Android<br />
** [http://blog.mozilla.org/jseward/2013/06/03/profiler-backend-news-3-june-2013/ Julian's blog post]<br />
* I'm working on reducing amount of startup I/O ({{bug|810156}})<br />
<br />
===Services (connor)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}} <br />
Health Report: desktop stable, gps on PTO; Android underway, part-landed on m-c, still tracking for uplift to 23.<br />
Sync service still working through outage (largely due to hardware failures). Things are improving. Contact mmayo for details.<br />
<br />
===WebAPI (overholt)===<br />
Last week:<br />
* work towards temporary storage for IDB ({{bug|785884}})<br />
* Web Audio security bugs (lots of them)<br />
* shared workers<br />
* [http://annevankesteren.nl/2013/06/london-tag hosted W3C TAG F2F in London]<br />
<br />
This week:<br />
* more work on shared workers<br />
* [https://wiki.mozilla.org/WebAPI/DataStore DataStore API]<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=856410 Futures] (see also https://github.com/slightlyoff/Futures)<br />
* continuing on temporary storage for IDB ({{bug|785884}})<br />
* [https://github.com/sysapps/ SysApps spec work]<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
* Smash those crits.<br />
<br />
===Memshrink (njn)===<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 5.90] (Previous Week: 5.74). 4.32 ignoring resolved/disabled bugs.<br />
* Most frequent oranges are infra-related.<br />
* 13 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-05-28&f1=cf_last_resolved&query_format=advanced&list_id=6719912 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* Between {{bug|831768}} and the Flash 11.7 release, Flash crashes and hangs across all Windows versions (including XP!) are down by almost 50% in Firefox 21 / Flash 11.7 compared to Fx 20 / Flash 11.6!<br />
* [http://arewestableyet.com/ Overall numbers] across channels look pretty good.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
*dev-platform<br />
** [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/k1MW06xRYPo Embracing git usage for Firefox/Gecko development?] (jst)<br />
** [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/ayEbEWT_DL0 Proposal to make Firefox open in the foreground on Mac when launched from terminal] (ehsan)<br />
** [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/2gvnS7kfqdA Code Review Session] (sjohnson)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small><br />
* [http://www.reddit.com/r/MozillaTech/ Reddit MozillaTech]</div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/2013-06-04&diff=663263Platform/2013-06-042013-06-04T18:08:45Z<p>Jesse: /* DOM (jst/dougt) */</p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<br />
<small>[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</small><br />
<br />
<div class="h-event vevent"><br />
'''<span class="p-summary summary">Engineering Meeting</span> Details'''<br />
* <span class="dt-start dtstart">Tuesday <span class="value">{{#time: Y-m-d | {{SUBPAGENAME}} }}</span> - <span class="value">11:00</span> am <abbr class="value" title="-0700">Pacific</abbr></span><br />
{{conf|98411}}<br />
* <span class="location">[https://v.mozilla.com/flex.html?roomdirect.html&key=T2v8Pi8WuTRc Engineering Vidyo Room] / Warp Core / SFO-Boardroom / Tor Commons</span><br />
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel<br />
</div><br />
<br />
==Actions==<br />
<br />
==Hot Bugs==<br />
<small>(Important bugs for which we need to find owners or additional help. If known, please include suggested team or knowledge needed to advance the bug.)</small><br />
; Orange Factor<br />
* {{bug|876068}} - B2G Windows desktop builds mostly fail, after a "C:\Tools\sdks\v7.0\include\winnt.h(135) : fatal error C1189: #error : 'No Target Architecture'".<br />
** Affects all dep builds. Do we even need these builds?<br />
** Please check with Gaia team before disabling these. I would expect them to be needed. (sicking)<br />
; Stability<br />
; Other<br />
<br />
==The Need To Know==<br />
<small>(Release and system issues that may impact engineering this week.)</small><br />
===Notices/Schedule (akeybl/lsblakk/bajaj)===<br />
* FF22b4 is going to build EOD (mobile may be decoupled)<br />
* We're now more than halfway through the Beta cycle - it's due or die if you've got a tracked bug at this point <br />
* Our most concerning FF22 issues right now are new crash regressions<br />
** {{bug|867226}} – Incomplete framebuffer abort in mozilla::layers::LayerManagerOGL::CreateFBOWithTexture with "error 0x8cdd"<br />
** {{bug|853774}} – crash in imgRequest::GetStatusTracker<br />
** {{bug|863313}} – crash in mozilla::gl::GLContextEGL::MakeCurrentImpl @ libEGL_VIVANTE.so@0x5... with Vivante GC400 or GC800 core running ICS<br />
<br />
{| class="wikitable"<br />
|-<br />
| <center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notequals;value0-7-0=%2B;field0-3-0=cf_status_firefox{{AURORA_VERSION}};type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;field0-1-0=cf_status_firefox{{AURORA_VERSION}};field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{AURORA_VERSION}};value0-3-0=unaffected;field0-7-0=cf_tracking_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;value0-6-0=verified%20disabled;value0-1-0=wontfix;type0-3-0=notequals;field0-2-0=cf_status_firefox{{AURORA_VERSION}};field0-5-0=cf_status_firefox{{AURORA_VERSION}};field0-4-0=cf_status_firefox{{AURORA_VERSION}};type0-6-0=notequals;type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;list_id=5004437 47 bugs]</big> <small>(37 bugs last week)</small></center><br />
| <b><center><big>[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notequals;type0-5-0=notequals;value0-5-0=disabled;value0-4-0=verified;list_id=4754086;field0-1-0=cf_status_firefox{{BETA_VERSION}};field0-0-0=cf_tracking_firefox{{BETA_VERSION}};value0-3-0=unaffected;value0-6-0=verified%20disabled;value0-1-0=wontfix;field0-5-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;type0-2-0=notequals;field0-3-0=cf_status_firefox{{BETA_VERSION}};type0-4-0=notequals;columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate;field0-6-0=cf_status_firefox{{BETA_VERSION}};query_format=advanced;value0-2-0=fixed;type0-3-0=notequals;field0-2-0=cf_status_firefox{{BETA_VERSION}};field0-4-0=cf_status_firefox{{BETA_VERSION}};type0-6-0=notequals 30 bugs]</big> <small>(43 bugs last week)</small></center></b><br />
|-<br />
<!-- BIG NUMBER == This week's bug count, SMALL NUMBER IN BRACKETS == Last week's bug count --><br />
! scope="row" | <small>Unresolved Aurora {{AURORA_VERSION}} Trackers (non-security, not tracked for Beta)</small><br />
! scope="row" | <b><small>Unresolved Beta {{BETA_VERSION}} Trackers (non-security)</small></b><br />
|}<br />
<br />
===Upcoming Outages/Upgrades===<br />
<small>(System outages/upgrades and tree closures that impact engineering.)</small><br />
* Nothing currently planned.<br />
<br />
==Key Issues==<br />
<small>(Non team specific issues that impact engineering.)</small><br />
<br />
UCOSP - the Undergraduate Capstone Open Source Project - is a final-year credit project for undergrads across Canada, who'll be working in small, geographically distributed teams. We'll be hosting their code sprint in mid-September, but the time to start thinking about projects is much sooner than that! <br />
<br />
Mike Hoye will talk about this for two minutes, just to put the idea in your heads.<br />
<br />
==Team Stand-ups==<br />
<small>(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)</small><br />
===Accessibility (dbolter)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}}--><br />
Among other things:<br />
* Making excellent progress on adding and polishing braille support (Max Li (intern))<br />
* Implementing a way for Gaia to pull in default extensions via build system. (Eitan)<br />
* Attacking our known test run asserts. (Trevor)<br />
* Deep in debugging life cycle and text bugs. (Alexander)<br />
* Some travel/evangelism in Germany. (Marco)<br />
* Built in screen reader improvements. (Eitan, Yura (volunteer), Marco)<br />
<br />
===Add-on SDK (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Kayaking at JSConf<br />
* Last week's [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-05-28#Minutes meeting minutes]<br />
* Places API is nearly done<br />
* Toolbar buttons, sidebars and toolbars APIs are in progress. Coordinating with Australis team<br />
<br />
===Simulator (dtownsend)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* New [https://wiki.mozilla.org/Simulator/FirefoxIntegration/ mockups and planning] for integrating the app manager into Firefox<br />
<br />
===B2G Services (dougt/mmayo)===<br />
* Push Notifications<br />
** B2g 1.1<br />
** Android<br />
** Desktop<br />
* Proxy Services<br />
** Email<br />
** Calendar<br />
* Where is my phone<br />
* Location database<br />
** https://wiki.mozilla.org/Services/Location/Roadmaps<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Developer Tools (dcamp)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Last devtools meeting: https://etherpad.mozilla.org/ep/pad/view/devtools-meeting/jKxwbHYJDZ<br />
* The browser console has been enabled by default, bugs will get high priority.<br />
* Content process debugging is underway: {{bug|797627}} - review requests will hit other teams, please keep an eye out.<br />
* Remote inspector is progressing: {{bug|remote-inspector}}<br />
<br />
===DOM (jst/dougt)===<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=850065 Incremental cycle collector] (mccr8)<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=845545 Cycle collector per DOM worker thread] (khuey)<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=841442 One Node left to convert to new bindings] (baku)<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=653881 XBL Refactor - May break things]<br />
<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Firefox Desktop (gavin/dolske)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
;Last week<br />
* Australis<br />
** Continued work on customization and tabs styling ({{bug|874819}}, {{bug|867675}}, {{bug|875946}}) - see root meta bugs {{bug|732583}} and {{bug|872617}} <br />
** Milestone 6 completes tomorrow. We've got almost all of the customizable widgets done (bookmarks widget and character encoding widget are the two big missing pieces).<br />
** User research team is going to do some focus groups with users on or around June 10th to see what people think of the design.<br />
** Still on track to ship in 25 cycle<br />
** [http://people.mozilla.org/~jwein/ux-nightly/ Try out a UX build], and please file bugs! Dupes are cheap.<br />
*** For tab related bugs, please file them blocking australis-tabs, and put [Australis:M?] in the whiteboard<br />
*** For toolbar or customization bugs, please file them blocking australis-cust and put [Australis:M?] in the whiteboard<br />
*** For bugs that don't fall into either category, but seem Australis-related, file them blocking australis and put [Australis:M?] in the whiteboard.<br />
<br />
* Performance<br />
** New API added to be able to track reflows ({{bug|453650}})<br />
** Many improvements to new tab opening/preloading to avoid unnecessary layout reflow ({{bug|878801}})<br />
** Tracked down remaining form-history synchronous SQLite users ({{bug|876002}})<br />
* Social<br />
** Landed various fixes to support use of WebRTC in social panels ({{bug|821073}}, {{bug|805684}}, {{bug|836766}}), make social debugging easier ({{bug|820601}})<br />
;Next week<br />
* Australis<br />
** continued work, particularly on customization (new widgets, interaction)<br />
* Performance<br />
** enable new tab page pre-loading<br />
** fix sync's use of old form history API<br />
** determine plan for enabling background tab thumbnailing<br />
;Blocked on<br />
* N/A<br />
<br />
===Firefox Metro (bbondy/jmathies/mbrubeck)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Last week:<br />
** [http://teamstat.us/#browse/irc.mozilla.org/windev team-status] [http://scrumbu.gs/p/FireFox-Metro/ scrum]<br />
** Lots of bug fixes/improvements on front end UI.<br />
** New default browser telemetry added for all platforms (BROWSER_IS_USER_DEFAULT)<br />
** APZC prelim investigation / syncup with other teams<br />
** Software updating from Metro (note addon compat check issue in {{bug|794937}})<br />
* Continuing:<br />
** More front end bug fixes, theming, and polish.<br />
** Sorting out issues with browser registration for automated tests ({{bug|864940}})<br />
** APZC<br />
* Misc:<br />
** Adding a new front end team member (emtwo / Toronto)<br />
<br />
===Firefox Mobile (mfinkle/blassey)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* gfx::Point, gfx::Rect, and gfx::Size can now be typed with units at compile-time. See {{bug|865735}} for initial landing and {{bug|877728}} as an example of how to use it. Some explanation also at https://staktrace.com/spout/entry.php?id=799. Relevant files are at layout/base/Units.h and gfx/2d/{Point,Rect}.h and will be fleshed out as more stuff is converted to be typed.<br />
* {{bug|867517}} Gecko-based WebView for Android landed <br />
** Still need to figure out how we're going to package it for 3rd parties<br />
* {{bug|877203}} New fonts for content (Clear Sans) landed and bounced, may need help figuring out reftest failures<br />
* {{bug|866957}} Collect and report cell tower and WiFi AP info, landed behind a pref<br />
* ANRs (Android chrome-hangs) have been reduced from 21.6 reports/day for first 3 weeks of 23 nightly, down to 13.8 reports/day for first 3 weeks of 24 nightly (36% decrease). This can be attributed to our new ANR reporter and focus on fixing those hangs.<br />
* {{bug|862377}} UI for WebRTC has landed in nightly, which means we plan to turn WebRTC support on by default in Fx24<br />
* {{bug|878123}} and {{bug|878868}} we plan to start shipping x86 support in Beta<br />
<br />
===GFX (milan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* Back from a joint "rendering" [https://intranet.mozilla.org/Web_Rendering_Work_Week_May_2013 work week] in Taipei<br />
* Active [https://wiki.mozilla.org/Platform/GFX#Development_Planning work]:<br />
** off main thread image animation<br />
** D2D 1.1<br />
** SkiaGL<br />
** joint work on async pan-zoom on mobile; sorting out metro<br />
<br />
===Identity (jedp)===<br />
<br />
Overview<br />
<br />
* The Native team in Identity is Jed, Austin King, and Zach Carter (50% time)<br />
* Primary efforts: b2g, desktop firefox, WebRTC<br />
* Austin King is working on Persona sign-in to browser UI<br />
* Jed is working on b2g and desktop<br />
* Zach will help out on b2g with device sign-in, looking ahead to picl and identity-attached services<br />
* Ryan Seys joins Identity as a Summer intern, working on Persona auth for WebRTC<br />
** Have met with ekr and bbrittain<br />
* Austin, Jed, and Crystal Beasley (aka Skinny) mini work weekend Friday thru Sunday for native desktop<br />
<br />
===JS (naveed)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
*DONE<br />
**ARM raytrace regression fixed - bug<br />
**JS h264 decoder memory utlization bug fixed<br />
**Exact rooting fuzz bugs<br />
**Started ES6 self-hosted Arrays extras<br />
**Work on getting --ion-eager switch in the browser for fuzzers.<br />
**Landed in inbound a script to import selected subsets (ch06/, intl402/) of ECMAScript's test262 suite, those tests to run every push; landed those subsets in inbound.<br />
**Closed ({{bug|831507 }}) - Adding GGC post-write barriers to baseline compiler code generation.<br />
**Put more work on a well-commented pseudo-implementation of ES6 module loaders. You can see it here: https://people.mozilla.com/~jorendorff/js-loaders/loaders.html<br />
<br />
*DOING<br />
**Increase FFI asm.js call performance<br />
**Static rooting analysis precision improvements<br />
**Green GGC on tbpl <br />
**Implement proxy [[invoke]] trap ({{bug|878605 }})<br />
**Removing unneeded #includes in SpiderMonkey in the hope of speeding up compile times (bug https://bugzilla.mozilla.org/show_bug.cgi?id=634839).<br />
**clean-up memory pressure patches. ({{bug|876029 }}) & ({{bug|869263 }})<br />
**find regression on Sunspider (between May 21st to 29th)<br />
**Bug 878992 - Remove unused TypeObject flag OBJECT_FLAG_UNINLINEABLE which was only relevant for now-defunct JM.<br />
**Bug 859609 - Enable inlining of anonymous lambdas and functions-which-use-their-scope-chains in Ion.<br />
**Begin Asm.js parser<br />
<br />
*BLOCKS<br />
**({{bug|877261 }}) -> ({{bug|869740 }}) -> exactly rooted browser<br />
<br />
===Layout (jet/dbaron)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
* (two weeks ago) we met, with Graphics and Media, in Taipei<br />
* a bunch of the team (dbaron, fantasai, jet, jdaggett, SimonSapin, heycam) at SVG and CSS Working Group meetings this week<br />
* off main thread animations finally has some test coverage, or will very soon ({{bug|788549}}), which is a step towards enabling it on non-B2G platforms<br />
* zoom-in and zoom-out values of CSS cursor property now unprefixed ({{bug|772153}})<br />
* major ongoing projects:<br />
** making CSS Flexbox paginate correctly (so pages using it will print) ({{bug|811024}})<br />
** starting to investigate implementing overflow:fragments ({{bug|874238}})<br />
<br />
===Media (mreavy)===<br />
* WebRTC's first implementation will be going out in Fx 22 Desktop. We believe all release blockers have been eliminated in Beta 4.<br />
** Actively looking at Bug 879213 - occasional audio-only latency issue, where audio noticeably lags video (it may be more common in certain network situations or environments). We believe it affects all products (desktop and mobile).<br />
** TURN support (http://tools.ietf.org/html/rfc5766) is coming in Fx 23.<br />
* Working with the team in Taipei to get WebRTC working on B2G<br />
* WebRTC's work week is next week in Sunnyvale (10 mins from the MV office)<br />
* Ben Brittain is the new intern for WebRTC. He is working on hooking up WebRTC to telemetry<br />
* Made good progress on improving H.264/MP4 playback performance on Win 7/8. There are 2 known bugs related to H.264/MP4 playback:<br />
** Bug 875644 - HE-AAC doesn't work properly (HE-AAC is not very common yet on the web)<br />
** Bug 879099 - Minor regression with color saturation on Nvidia<br />
* Close to finishing gstreamer backend for Linux to enable H.264 playback, but B2G work is taking priority this week<br />
* On track to deliver the first part of MSE (Media Source Extensions) by end of the month (i.e. a first phase of adaptive streaming [chunked multi-bitrate/resolution streaming] support that enables DASH-JS)<br />
* roc: Fixed a few video controls bugs affecting YouTube last week. People are now working on a few different video playback issues with the Youtube app, hoping to have them fixed this week.<br />
<br />
===Necko (dougt/jduell)===<br />
* Update on Disk Cache rewrite (jduell)<br />
* ODA off main thread (sworkman)<br />
* Http2, for real (patrick)<br />
* Fixing youtube hang on B2G<br />
<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
===Performance (vladan)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
<!-- {{readonly}} --><br />
<br />
* Dhaval Giani is our new intern. He'll be working on adding transparent compression to ext4.<br />
* Avi Halachmi landed VSync support on Windows ({{bug|856427}}). He's now working on improving Talos animation tests ({{bug|854746}} + {{bug|845943}})<br />
* Aaron Klotz is working on a patch to report main-thread NSPR & SQLite I/O to the profiler ({{bug|867762}})<br />
* Irving and Felipe are re-factoring the Addon Manager to store configuration in JSON files instead of SQLite DBs + move I/O operations off the main thread ({{bug|853388}} + {{bug|853389}}).<br />
** [http://www.controlledflight.ca/2013/05/31/saving-browser-state-asynchronously/ Irving's blog post]<br />
* Yoric added a warning when storing prefs >16kb ({{bug|872981}})<br />
* Yoric is working with ttaubert to refactor session store ({{bug|874381}})<br />
* Yoric is working on a pure-async mozIStorageAsyncConnection ({{bug|702559}})<br />
** [http://dutherenverseauborddelatable.wordpress.com/2013/05/24/project-async-responsive-issue-2/ Yoric's blog post]<br />
* Nathan Froyd is working on a new client-side Telemetry design<br />
* Glandium has been making improvements to build. He's moving to Japan, resuming work as contractor on June 25th.<br />
* Julian Seward is working on multi-threaded stack unwinding on Android<br />
** [http://blog.mozilla.org/jseward/2013/06/03/profiler-backend-news-3-june-2013/ Julian's blog post]<br />
* I'm working on reducing amount of startup I/O ({{bug|810156}})<br />
<br />
===Services (connor)===<br />
<!-- Read only update this week? Uncomment the following line--><br />
{{readonly}} <br />
Health Report: desktop stable, gps on PTO; Android underway, part-landed on m-c, still tracking for uplift to 23.<br />
Sync service still working through outage (largely due to hardware failures). Things are improving. Contact mmayo for details.<br />
<br />
===WebAPI (overholt)===<br />
Last week:<br />
* work towards temporary storage for IDB ({{bug|785884}})<br />
* Web Audio security bugs (lots of them)<br />
* shared workers<br />
* [http://annevankesteren.nl/2013/06/london-tag hosted W3C TAG F2F in London]<br />
<br />
This week:<br />
* more work on shared workers<br />
* [https://wiki.mozilla.org/WebAPI/DataStore DataStore API]<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=856410 Futures] (see also https://github.com/slightlyoff/Futures)<br />
* continuing on temporary storage for IDB ({{bug|785884}})<br />
* [https://github.com/sysapps/ SysApps spec work]<br />
<br />
==Quality Programs==<br />
<small>(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)</small><br />
===Critsmash (dbolter)===<br />
* Smash those crits.<br />
<br />
===Memshrink (njn)===<br />
===OrangeFactor (ryanvm)===<br />
* Past week's OrangeFactor: [http://brasstacks.mozilla.com/orangefactor/ 5.90] (Previous Week: 5.74). 4.32 ignoring resolved/disabled bugs.<br />
* Most frequent oranges are infra-related.<br />
* 13 intermittent failures fixed in the last week - [https://bugzilla.mozilla.org/buglist.cgi?keywords_type=allwords&keywords=intermittent-failure%2C%20&resolution=FIXED&o1=greaterthan&v1=2013-05-28&f1=cf_last_resolved&query_format=advanced&list_id=6719912 List] - Thanks!.<br />
<br />
===Stability (kairo/bsmedberg)===<br />
* Between {{bug|831768}} and the Flash 11.7 release, Flash crashes and hangs across all Windows versions (including XP!) are down by almost 50% in Firefox 21 / Flash 11.7 compared to Fx 20 / Flash 11.6!<br />
* [http://arewestableyet.com/ Overall numbers] across channels look pretty good.<br />
<br />
==Roundtable==<br />
<small>(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)</small><br />
<br />
==<Read only beyond this point>==<br />
===Mailing List Threads===<br />
<small>(Threads that are likely to be of interest to engineering from various mailing lists.)</small><br />
*dev-platform<br />
** [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/k1MW06xRYPo Embracing git usage for Firefox/Gecko development?] (jst)<br />
** [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/ayEbEWT_DL0 Proposal to make Firefox open in the foreground on Mac when launched from terminal] (ehsan)<br />
** [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/2gvnS7kfqdA Code Review Session] (sjohnson)<br />
<br />
===Good Reads===<br />
<small>(Links to blog posts, books, videos, etc. that you think will be of interest to others.)</small><br />
* [http://www.reddit.com/r/MozillaTech/ Reddit MozillaTech]</div>Jessehttps://wiki.mozilla.org/index.php?title=Performance/MemShrink&diff=655556Performance/MemShrink2013-05-14T02:46:28Z<p>Jesse: /* Meeting Minutes, Progress Reports and Presentations */</p>
<hr />
<div>MemShrink is a project that aims to reduce the memory consumption of Firefox (on desktop and mobile) and Firefox OS. There are three potential benefits.<br />
<br />
# Speed. Firefox will be faster due to less cache pressure, less paging, and fewer/smaller GC and CC pauses. Changes that reduce memory consumption but make Firefox slower are not desirable.<br />
# Stability. Firefox will suffer fewer aborts/crashes due to virtual or physical memory exhaustion. The former is mostly a problem on 32-bit Windows builds with a 2GB or 4GB virtual memory limit, the latter is mostly a problem on mobile devices that lack swap space.<br />
# Reputation. Fewer people will complain that Firefox is a memory hog and that Mozilla ignores memory usage.<br />
<br />
[http://blog.mozilla.com/nnethercote/2012/02/08/the-benefits-of-reducing-memory-consumption-2/ This blog post] describes these benefits in more detail.<br />
<br />
There are two main ways to reduce memory consumption.<br />
<br />
# "Slim down" memory usage, e.g. make data structures more space-efficient.<br />
# Avoid "leaks". This loose use of the term (which is used throughout this document) includes:<br />
#* True leaks, where memory is lost forever.<br />
#* Lifetime issues, where memory is not reclaimed until you close the page/tab/window/process.<br />
#* Collection heuristic issues (e.g. GC is too infrequent).<br />
#* Bad cache algorithms and poorly tuned caches.<br />
#* Fragmentation.<br />
<br />
Leaks are generally more important, because they are more likely to lead to horrible performance. <br />
<br />
== Meetings ==<br />
Meetings happen every second Tuesday at 2pm Pacific time.<br />
<br />
{{conf|95346}}<br />
* Vidyo: PB&J<br />
* IRC: [irc://irc.mozilla.org/memshrink #memshrink]<br />
* Etherpad: [https://etherpad.mozilla.org/memshrink memshrink] (copied to wiki after the meeting)<br />
<br />
== Meeting Minutes, Progress Reports and Presentations ==<br />
<br />
Meeting dates, meeting minutes, and progress reports.<br />
<br />
{| border="1" cellpadding="2"<br />
! Date !! Minutes !! Progress report<br />
|-<br />
| 2013-05-08 || - || [http://jlebar.com/2013/5/8/MemShrink_process%2C_weeks_97-98.html Week 97--98] (guest post)<br />
|-<br />
| 2013-04-16 || - || [https://blog.mozilla.org/nnethercote/2013/04/17/memshrink-progress-week-95-96/ Week 95--96]<br />
|-<br />
| 2013-04-02 || - || [https://blog.mozilla.org/nnethercote/2013/04/03/memshrink-progress-week-93-94/ Week 93--94]<br />
|-<br />
| 2013-03-19 || - || [https://blog.mozilla.org/nnethercote/2013/03/20/memshrink-progress-week-91-92/ Week 91--92]<br />
|-<br />
| 2013-03-05 || - || [https://blog.mozilla.org/nnethercote/2013/03/07/memshrink-progress-week-89-90/ Week 89--90]<br />
|-<br />
| 2013-02-19 || - || [https://blog.mozilla.org/nnethercote/2013/02/20/memshrink-progress-week-87-88/ Week 87--88]<br />
|-<br />
| 2013-02-05 || - || [https://blog.mozilla.org/nnethercote/2013/02/06/memshrink-progress-week-85-86/ Week 85--86]<br />
|-<br />
| 2013-01-22 || - || [https://blog.mozilla.org/nnethercote/2013/01/23/memshrink-progress-week-83-84/ Week 83--84]<br />
|-<br />
| 2013-01-08 || - || [https://blog.mozilla.org/nnethercote/2013/01/09/memshrink-progress-week-79-82/ Week 79--82]<br />
|-<br />
| 2012-12-11 || - || [https://blog.mozilla.org/nnethercote/2012/12/12/memshrink-progress-week-77-78/ Week 77--78]<br />
|-<br />
| 2012-11-27 || - || [https://blog.mozilla.org/nnethercote/2012/11/28/memshrink-progress-week-75-76/ Week 75--76]<br />
|-<br />
| 2012-11-13 || - || [https://blog.mozilla.org/nnethercote/2012/11/14/memshrink-progress-week-73-74/ Week 73--74]<br />
|-<br />
| 2012-10-30 || - || [https://blog.mozilla.org/nnethercote/2012/10/31/memshrink-progress-week-71-72/ Week 71--72]<br />
|-<br />
| 2012-10-16 || - || [https://blog.mozilla.org/nnethercote/2012/10/17/memshrink-progress-week-69-70/ Week 69--70]<br />
|-<br />
| 2012-10-02 || - || [https://blog.mozilla.org/nnethercote/2012/10/03/memshrink-progress-week-67-68/ Week 67--68]<br />
|-<br />
| 2012-09-18 || - || [https://blog.mozilla.org/nnethercote/2012/09/19/memshrink-progress-week-65-66/ Week 65--66]<br />
|-<br />
| 2012-09-04 || - || [https://blog.mozilla.org/nnethercote/2012/09/05/memshrink-progress-week-63-64/ Week 63--64]<br />
|-<br />
| 2012-08-21 || - || [https://blog.mozilla.org/nnethercote/2012/08/23/memshrink-progress-week-61-62/ Week 61--62]<br />
|-<br />
| 2012-08-07 || - || [https://blog.mozilla.org/nnethercote/2012/08/08/memshrink-progress-week-57-60/ Week 57--60]<br />
|-<br />
| 2012-07-24 || - || -<br />
|-<br />
| 2012-07-10 || - || [https://blog.mozilla.org/nnethercote/2012/07/11/memshrink-progress-week-55-56/ Week 55--56] (includes the second "Big Ticket Items" list)<br />
|-<br />
| 2012-06-26 || - || [http://blog.mozilla.org/nnethercote/2012/06/27/memshrink-progress-week-53-54/ Week 53--54]<br />
|-<br />
| 2012-06-14 || - || [http://blog.mozilla.org/nnethercote/2012/06/15/memshrinks-1st-birthday/ MemShrink's 1st Birthday]<br />
|-<br />
| 2012-06-12 || - || [http://blog.mozilla.org/nnethercote/2012/06/13/memshrink-progress-week-51-52/ Week 51--52]<br />
|-<br />
| 2012-05-29 || - || [http://blog.mozilla.org/nnethercote/2012/05/30/memshrink-progress-week-49-50/ Week 49--50]<br />
|-<br />
| 2012-05-15 || - || [http://blog.mozilla.org/nnethercote/2012/05/16/memshrink-progress-week-47-48/ Week 47--48]<br />
|-<br />
| 2012-05-01 || - || [http://blog.mozilla.org/nnethercote/2012/05/02/memshrink-progress-week-45-46/ Week 45--46]<br />
|-<br />
| 2012-04-17 || - || [http://blog.mozilla.org/nnethercote/2012/04/18/memshrink-progress-week-43-44/ Week 43--44]<br />
|-<br />
| 2012-04-03 || - || [http://blog.mozilla.org/nnethercote/2012/04/04/memshrink-progress-week-42/ Week 42]<br />
|-<br />
| 2012-03-27 || - || [http://blog.mozilla.com/nnethercote/2012/03/28/memshrink-progress-week-41/ Week 41]<br />
|-<br />
| 2012-03-20 || - || [http://blog.mozilla.com/nnethercote/2012/03/21/memshrink-progress-week-40/ Week 40]<br />
|-<br />
| 2012-03-13 || - || [http://blog.mozilla.com/nnethercote/2012/03/14/memshrink-progress-week-39/ Week 39]<br />
|-<br />
| 2012-03-06 || - || [http://blog.mozilla.com/nnethercote/2012/03/07/memshrink-progress-week-38/ Week 38]<br />
|-<br />
| 2012-02-28 || - || [http://blog.mozilla.com/nnethercote/2012/02/29/memshrink-progress-week-37/ Week 37]<br />
|-<br />
| 2012-02-21 || - || [http://blog.mozilla.com/nnethercote/2012/02/22/memshrink-progress-week-36/ Week 36]<br />
|-<br />
| 2012-02-14 || - || [http://blog.mozilla.com/nnethercote/2012/02/15/memshrink-progress-week-35/ Week 35]<br />
|-<br />
| 2012-02-07 || - || [http://blog.mozilla.com/nnethercote/2012/02/08/memshrink-progress-week-34/ Week 34]<br />
|-<br />
| 2012-01-31 || - || [http://blog.mozilla.com/nnethercote/2012/02/01/memshrink-progress-week-33/ Week 33]<br />
|-<br />
| 2012-01-24 || - || [http://blog.mozilla.com/nnethercote/2012/01/25/memshrink-progress-week-32/ Week 32] (includes the first "Big Ticket Items" list)<br />
|-<br />
| 2012-01-17 || - || [http://blog.mozilla.com/nnethercote/2012/01/18/memshrink-progress-week-31/ Week 31]<br />
|-<br />
| 2012-01-10 || - || [http://blog.mozilla.com/nnethercote/2012/01/11/memshrink-progress-week-30/ Week 30]<br />
|-<br />
| 2012-01-03 || - || [http://blog.mozilla.com/nnethercote/2012/01/04/memshrink-progress-weeks-28-29/ Weeks 28--29]<br />
|-<br />
| 2011-12-20 || - || [http://blog.mozilla.com/nnethercote/2011/12/21/memshrink-progress-week-27/ Week 27]<br />
|-<br />
| 2011-12-13 || [[Performance/MemShrink/Meetings/2011-12-13|minutes]] || [http://blog.mozilla.com/nnethercote/2011/12/14/memshrink-progress-week-26/ Week 26]<br />
|-<br />
| 2011-12-06 || [[Performance/MemShrink/Meetings/2011-12-06|minutes]] || [http://blog.mozilla.com/nnethercote/2011/12/07/memshrink-progress-week-25/ Week 25]<br />
|-<br />
| 2011-11-29 || [[Performance/MemShrink/Meetings/2011-11-29|minutes]] || [http://blog.mozilla.com/nnethercote/2011/11/30/memshrink-progress-report-week-24/ Week 24]<br />
|-<br />
| 2011-11-22 || - || [http://blog.mozilla.com/nnethercote/2011/11/23/memshrink-progress-report-week-23/ Week 23]<br />
|-<br />
| 2011-11-15 || - || [http://blog.mozilla.com/nnethercote/2011/11/16/memshrink-progress-report-week-22/ Week 22]<br />
|-<br />
| 2011-11-08 || [[Performance/MemShrink/Meetings/2011-11-08|minutes]] || [http://blog.mozilla.com/nnethercote/2011/11/09/memshrink-progress-week-21/ Week 21]<br />
|- <br />
| 2011-11-01 || [[Performance/MemShrink/Meetings/2011-11-01|minutes]] || [http://blog.mozilla.com/nnethercote/2011/11/02/memshrink-progress-week-20/ Week 20]<br />
|- <br />
| 2011-10-25 || [[Performance/MemShrink/Meetings/2011-10-25|minutes]] || [http://blog.mozilla.com/nnethercote/2011/10/26/memshrink-progress-week-19/ Week 19]<br />
|- <br />
| 2011-10-18 || [[Performance/MemShrink/Meetings/2011-10-18|minutes]] || [http://blog.mozilla.com/nnethercote/2011/10/19/memshrink-progress-weeks-13-18/ Weeks 13--18]<br />
|-<br />
| 2011-10-11 || [[Performance/MemShrink/Meetings/2011-10-11|minutes]] || -<br />
|-<br />
| 2011-10-04 || [[Performance/MemShrink/Meetings/2011-10-04|minutes]] || -<br />
|-<br />
| 2011-09-27 || - || -<br />
|-<br />
| 2011-09-20 || [[Performance/MemShrink/Meetings/2011-09-20|minutes]] || -<br />
|-<br />
| 2011-09-13 || - || -<br />
|-<br />
| 2011-09-06 || [[Performance/MemShrink/Meetings/2011-09-06|minutes]] || [http://blog.mozilla.com/nnethercote/2011/09/07/memshrink-progress-week-12/ Week 12]<br />
|-<br />
| 2011-08-30 || [[Performance/MemShrink/Meetings/2011-08-30|minutes]] || [http://blog.mozilla.com/nnethercote/2011/08/31/memshrink-progress-week-11/ Week 11]<br />
|-<br />
| 2011-08-23 || [[Performance/MemShrink/Meetings/2011-08-23|minutes]] || [http://blog.mozilla.com/nnethercote/2011/08/24/memshrink-progress-week-10/ Week 10]<br />
|-<br />
| 2011-08-16 || [[Performance/MemShrink/Meetings/2011-08-16|minutes]] || [http://blog.mozilla.com/nnethercote/2011/08/17/memshrink-progress-week-9/ Week 9]<br />
|-<br />
| 2011-08-09 || [[Performance/MemShrink/Meetings/2011-08-09|minutes]] || [http://blog.mozilla.com/nnethercote/2011/08/10/memshrink-progress-week-8/ Week 8]<br />
|-<br />
| 2011-08-02 || - || [http://blog.mozilla.com/nnethercote/2011/08/03/memshrink-progress-week-7/ Week 7]<br />
|-<br />
| 2011-07-26 || [[Performance/MemShrink/Meetings/2011-07-26|minutes]] || [http://blog.mozilla.com/nnethercote/2011/07/27/memshrink-progress-week-6/ Week 6]<br />
|-<br />
| 2011-07-19 || [[Performance/MemShrink/Meetings/2011-07-19|minutes]] || [http://blog.mozilla.com/nnethercote/2011/07/20/memshrink-progress-week-5/ Week 5]<br />
|-<br />
| 2011-07-12 || [[Performance/MemShrink/Meetings/2011-07-12|minutes]] || [http://blog.mozilla.com/nnethercote/2011/07/13/memshrink-progress-week-4/ Week 4]<br />
|-<br />
| 2011-07-05 || [[Performance/MemShrink/Meetings/2011-07-05|minutes]] || [http://blog.mozilla.com/nnethercote/2011/07/06/memshrink-progress-week-3/ Week 3]<br />
|-<br />
| 2011-06-28 || - || [http://blog.mozilla.com/nnethercote/2011/06/29/memshrink-progress-week-2/ Week 2]<br />
|-<br />
| 2011-06-21 || - || [http://blog.mozilla.com/nnethercote/2011/06/22/memshrink-progress-week-1/ Week 1]<br />
|-<br />
| 2011-06-14 || - || -<br />
|}<br />
<br />
<br />
Presentations.<br />
<br />
*2012-01-16 [[media:LCA2012.pdf|"Notes on Reducing Firefox's Memory Consumption"]], presented at linux.conf.au Browser MiniConf<br />
<br />
== Bug Tracking ==<br />
<br />
Bugs tracked by the MemShrink project are prioritized by adding one of "MemShrink:P1", "MemShrink:P2" or "MemShrink:P3" to the whiteboard.<br />
<br />
* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=regexp&query_format=advanced&list_id=577353&status_whiteboard=MemShrink%5b%5e%3A%5d&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---&resolution=DUPLICATE Unprioritized MemShrink bugs]. These are triaged regularly in meetings.<br />
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP1&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P1 bugs]. These are discussed regularly in meetings.<br />
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP2&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P2 bugs]. These are discussed occasionally in meetings. P2 is the default priority.<br />
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink%3AP3&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id MemShrink:P3 bugs]. These are discussed rarely in meetings.<br />
<br />
Some other interesting bug lists that overlap with the ones above.<br />
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=463753&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=MemShrink&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id All MemShrink bugs].<br />
* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&list_id=1252875&status_whiteboard=MemShrink&bug_status=UNCONFIRMED&resolution=---&resolution=DUPLICATE Unconfirmed MemShrink bugs]. These are problems reported by users and generally require some kind of additional work to confirm.<br />
* [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&list_id=1252905&status_whiteboard=MemShrink%20mentor&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---&resolution=DUPLICATE MemShrink bugs with a "mentor" annotation]. These are bugs that someone has identified as reasonable easy, and that person is willing to help a newcomer fix the bug.<br />
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=1252950&resolution=---&resolution=DUPLICATE&emailtype1=regexp&status_whiteboard_type=allwordssubstr&emailassigned_to1=1&query_format=advanced&status_whiteboard=MemShrink&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=nobody%40%7Cgeneral%40js.bugs Unassigned MemShrink bugs]. These need someone to work on them.<br />
<br />
== areweslimyet.com ==<br />
<br />
http://arewefastyet.com is a very successful site used to track the performance of Firefox's JavaScript engine. Why was arewefastyet.com so successful? Some key characteristics.<br />
* The benchmarks were easy to choose: everybody already used SS and V8, and then Mozilla released Kraken. They run quickly, too, which is nice for devs, and allows expensive tools (like Cachegrind) to be used.<br />
* The metrics were easy to choose. SS time, V8 time, Kraken time. They can be measured easily, precisely, and fairly repeatably. You can break the total time down into per-benchmark times, which really helps with understanding improvements and regressions. They're easy for devs to run on their own machine.<br />
* There was a well-defined goal: match or beat the other browsers.<br />
<br />
In comparison, for memory consumption there is no good and/or standard benchmark suite; metrics are less clear and harder to measure (especially across different browsers); and most importantly, there's no well-defined goal w.r.t. any benchmarks.<br />
<br />
Nonetheless, we've created a memory benchmark and are tracking Firefox's performance on it over time, to provide a sense of MemShrink progress and detect regressions. It is available at http://areweslimyet.com/.</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Security_Bugs/EncryptedBugmail&diff=638407Security/Security Bugs/EncryptedBugmail2013-03-19T08:14:50Z<p>Jesse: /* 5. How do I make a PGP/GPG public key or get an S/MIME certificate? */</p>
<hr />
<div>Secure Mail will soon by turned on for bugs in the "Security-Sensitive Core Bug" group in Mozilla's [https://bugzilla.mozilla.org Bugzilla]. This bug group includes all reported client security issues that are not web-related. Specifically, this is for general platform, JavaScript engine, Firefox, and Thunderbird code.<br />
<br />
This will change the default Bugzilla email notification for bugs in the "Security-Sensitive Core Bug" group to simply say that a bug has changed, giving no details except for a link to the bug. In order to receive the same bug details for security bugs as normal bugs, Bugzilla users will need to install a PGP-compatible public key or an S/MIME key in Bugzilla.<br />
<br />
For members of the "Security-Sensitive Core Bug" group, you will <u>not</u> be able to reset your password through email without uploading an encryption key. Password resets will only be available by contacting bugzilla-admin@mozilla.org. This is to keep password reset URLs for sensitive accounts from being sent as a cleartext.<br />
<br />
There is basic information on Secure Mail [https://bugzilla.mozilla.org/page.cgi?id=securemail/help.html available] on Bugzilla that explains some of the functionality.<br />
<br />
== Frequently Asked Questions (FAQ) ==<br />
<br />
=== 1. Why are we making this change? ===<br />
<br />
There has been concern for some time that email containing security problems that can affect hundreds of millions of people are being sent to developers and other interested parties as clear text. This means that there is a risk of interception as the email is sent across the Internet or if mail is stored offline on a local machine with the mail client. By switching to encrypted email for security bugs, we lessen the risk of accidental exposure of security issues. <br />
<br />
This change does make it more difficult to read bug mail for security issues in web-hosted mail services but there is always the option of not setting up secure mail for an account and simply going to Bugzilla to view changes in security bugs.<br />
<br />
This change was piloted by the former Infrasec team at Mozilla, which focused on security issues in Web sites and infrastructure, and it was found to work well.<br />
<br />
=== 2. How can I upload a Public Key? ===<br />
<br />
Load your [https://bugzilla.mozilla.org/userprefs.cgi?tab=securemail Secure Mail preferences tab] for Bugzilla. This tab has a textarea where you can enter your PGP/GPG public key or S/MIME certificate.<br />
<br />
=== 3. What if I take no action? ===<br />
<br />
If you do not upload an encryption key and there is an update to a bug in a secure group, you will receive a notification that the bug has changed when it is updated but no details of the change. In order to view the details, you will need to visit the provided link in the e-mail to see the bug on Bugzilla.<br />
<br />
Additionally, without uploading a key, you will not be able to reset your Bugzilla password over e-mail since the mail cannot be encrypted. You will require the assistance of an administrator (bugzilla-admin@mozilla.org) for password resets. (Note: you can still <i>change</i> your password; you just can't retrieve it via URL-to-email if you've forgotten it.)<br />
<br />
Here is a sample email you would receive if you have '''not''' uploaded an encryption key:<br />
<br />
Subject: [Bug 1234] (Secure bug updated)<br />
Date: Thu, 01 Mar 2012 21:21:53 +0000<br />
From: bugzilla-daemon@mozilla.org<br />
To: you@mozilla.com<br />
This email would have contained sensitive information, and you have not set <br />
a PGP/GPG key or SMIME certificate in the "Secure Mail" section of your user <br />
preferences. <br />
In order to receive the full text of similar mails in the future, please <br />
go to: <br />
https://bugzilla.mozilla.org/userprefs.cgi?tab=securemail <br />
and provide a key or certificate.<br />
You can see this bug's current state at: <br />
https://bugzilla.mozilla.org/show_bug.cgi?id=1234<br />
<br />
=== 4. I don't want to see these emails anymore, how do I turn them off? ===<br />
<br />
You can change your preferences for when you wish Bugzilla to send you mail in your [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences tab] for your Bugzilla preferences. This contains a variety of settings for when Bugzilla should send you email and for the components you are watching.<br />
<br />
=== 5. How do I make a PGP/GPG public key or get an S/MIME certificate? ===<br />
<br />
PGP/GPG keys have the advantage of being completely free to create but the disadvantage of being somewhat cumbersome to set up and use in comparison to S/MIME. <br />
<br />
You can read a [http://www.madboa.com/geek/gpg-quickstart/ Quickstart for GPG] or the [http://enigmail.mozdev.org/documentation/gpgsetup.php.html one written by the Enigmail team]. (There is an older [http://straightedgelinux.com/blog/howto/setupgnupg.html Linux-oriented article] as well.)<br />
<br />
PGP/GPG keys uploaded to Bugzilla must be ASCII-armoured (i.e. text, with the first line containing BEGIN PGP PUBLIC KEY) in order to work.<br />
<br />
You can obtain an S/MIME certificate from a number of providers. You can [https://www.startssl.com/?app=12 get a free one from StartCom] or [https://www.verisign.com/digital-id/index.html?tid=gnps pay Verisign] for one. Once you have it, [https://www.startssl.com/?app=25#52 export it from your browser] as a .p12 file and import it into your mail client. S/MIME Keys must be in PEM format - i.e. Base64-encoded text, with the first line containing BEGIN CERTIFICATE. <br />
<br />
In order to upload it to Bugzilla, you will need to convert the<br />
certificate to the PEM format.<br />
<br />
If you have OpenSSL installed and want to use the command line, you can<br />
extract your client certificate from the .p12 file that you have exported:<br />
<br />
openssl pkcs12 -in certificate.p12 -out certificate.pem -nokeys -clcerts<br />
<br />
Another approach is to use Certificate Manager. To open it in Firefox or<br />
Thunderbird, use menu command Edit, Preferences, Advanced, Encryption (or Certificates in Thunderbird), View certificates.<br />
<br />
Now click the "My Certificates" tab, find your own certificate, click "View", click the "Details" tab, click "Export". Save using the suggested default file<br />
format (X.509 Certificate PEM). The file will contain a single certificate, paste the file contents into [https://bugzilla.mozilla.org/userprefs.cgi?tab=securemail the Bugzilla form].<br />
<br />
=== 6. Where can I get more information on setting this up for my mail client? ===<br />
<br />
If you are using Thunderbird, S/MIME is supported out of the box. You can run [http://enigmail.mozdev.org/home/index.php.html Enigmail], a Thunderbird extension, to read GPG encrypted e-mail. Basic setup instructions are [http://enigmail.mozdev.org/documentation/basic.php.html here] for it.<br />
<br />
If you are using OS X's Mail.app, you can use [http://www.gpgtools.org/gpgmail/index.html GPGMail], a GPG-compatible addon.<br />
<br />
Ars Technica has [http://arstechnica.com/apple/guides/2011/10/secure-your-e-mail-under-mac-os-x-and-ios-5-with-smime.ars published an article] on adding S/MIME certificates to Mail.app and iOS devices (and there is another article [http://blog.riobard.com/2010/05/18/sign-encrypt-email here] as well.<br />
<br />
LuxSci FYI has an [http://luxsci.com/blog/installing-smime-and-pgp-encryption-certificates-into-major-email-clients.html article] on configuring Outlook and other email clients to use S/MIME and GPG as well.</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Reviews/ExitFullScreenFocusChange&diff=530604Security/Reviews/ExitFullScreenFocusChange2013-02-26T22:30:09Z<p>Jesse: </p>
<hr />
<div>{{SecReviewInfo<br />
|SecReview name=Don't exit fullscreen when focusing window on different display<br />
|SecReview target=<bugzilla><br />
{<br />
"id":"724554,805613"<br />
}<br />
</bugzilla><br />
}}<br />
{{SecReview<br />
|SecReview feature goal=* Multiple monitors lose fullscreen on focus change<br />
** video full screen in one monitor and work on something else on the other<br />
** or have 2 monitors have different things full screen<br />
** Current plan is to show the full-screen warning again for 4 seconds whenever a full-screen page regains focus.<br />
====Mac Spaces questions====<br />
* Will this allow you to use multiple spaces on a single monitor? (With one in full-screen mode and another showing another app, or another Firefox tab)<br />
** Probably? might need to ask zpao.<br />
* With multiple monitors, mac's concept of spaces and full-screen tends to affect all monitors at once<br />
|SecReview alt solutions=* Showing the warning again for 4 seconds upon return seems like overkill.<br />
** How about just one second?<br />
** How about a smaller warning? (Perhaps a watermark, if we can make it hard to hide)<br />
|SecReview solution chosen=*`<br />
|SecReview threat brainstorming=* The "warning when switching between two full-screen windows" might be defeatable, when a single site is full-screen in both windows (immersive demos and games)<br />
** What if a web page lies about where focus is?<br />
*** It can't prevent mouse clicks <br />
**** Lies about where the mouse cursor is?<br />
** This isn't really worse than the situation with one full-screen window<br />
}}<br />
{{SecReviewActionStatus<br />
|SecReview action item status=None<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Reviews/ExitFullScreenFocusChange&diff=530479Security/Reviews/ExitFullScreenFocusChange2013-02-26T19:43:03Z<p>Jesse: </p>
<hr />
<div>{{SecReviewInfo<br />
|SecReview name=Don't exit fullscreen when focusing window on different display<br />
|SecReview target=<bugzilla><br />
{<br />
"id":"724554"<br />
}<br />
</bugzilla><br />
}}<br />
{{SecReview<br />
|SecReview feature goal=* Multiple monitors lose fullscreen on focus change<br />
** video full screen in one monitor and work on something else on the other<br />
** or have 2 monitors have different things full screen<br />
** Current plan is to show the full-screen warning again for 4 seconds whenever a full-screen page regains focus.<br />
====Mac Spaces questions====<br />
* Will this allow you to use multiple spaces on a single monitor? (With one in full-screen mode and another showing another app, or another Firefox tab)<br />
** Probably? might need to ask zpao.<br />
* With multiple monitors, mac's concept of spaces and full-screen tends to affect all monitors at once<br />
|SecReview alt solutions=* Showing the warning again for 4 seconds upon return seems like overkill.<br />
** How about just one second?<br />
** How about a smaller warning? (Perhaps a watermark, if we can make it hard to hide)<br />
|SecReview solution chosen=*`<br />
|SecReview threat brainstorming=* The "warning when switching between two full-screen windows" might be defeatable, when a single site is full-screen in both windows (immersive demos and games)<br />
** What if a web page lies about where focus is?<br />
*** It can't prevent mouse clicks <br />
**** Lies about where the mouse cursor is?<br />
** This isn't really worse than the situation with one full-screen window<br />
}}<br />
{{SecReviewActionStatus<br />
|SecReview action item status=None<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Reviews/ExitFullScreenFocusChange&diff=530443Security/Reviews/ExitFullScreenFocusChange2013-02-26T19:18:42Z<p>Jesse: </p>
<hr />
<div>{{SecReviewInfo<br />
|SecReview name=Don't exit fullscreen when focusing window on different display<br />
|SecReview target=<bugzilla><br />
{<br />
"id":"724554"<br />
}<br />
</bugzilla><br />
}}<br />
<br />
=== Goal of Feature, what is trying to be achieved (problem solved, use cases, etc) ===<br />
* Multiple monitors lose fullscreen on focus change<br />
** video full screen in one monitor and work on something else on the other<br />
** or have 2 monitors have different things full screen<br />
** Current plan is to show the full-screen warning again for 4 seconds whenever a full-screen page regains focus.<br />
<br />
====Mac Spaces questions====<br />
* Will this allow you to use multiple spaces on a single monitor? (With one in full-screen mode and another showing another app, or another Firefox tab)<br />
** Probably? might need to ask zpao.<br />
* With multiple monitors, mac's concept of spaces and full-screen tends to affect all monitors at once :/<br />
<br />
=== What solutions/approaches were considered other than the proposed solution? ===<br />
* Showing the warning again for 4 seconds upon return seems like overkill.<br />
** How about just one second?<br />
** How about a smaller warning? (Perhaps a watermark, if we can make it hard to hide)<br />
<br />
== Threat Brainstorming ==<br />
* The "warning when switching between two full-screen windows" might be defeatable, when a single site is full-screen in both windows (immersive demos and games)<br />
** What if a web page lies about where focus is?<br />
*** It can't prevent mouse clicks <br />
**** Lies about where the mouse cursor is?<br />
** This isn't really worse than the situation with one full-screen window<br />
<br />
{{SecReviewActionStatus<br />
|SecReview action item status=None<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Reviews/ExitFullScreenFocusChange&diff=530437Security/Reviews/ExitFullScreenFocusChange2013-02-26T19:16:33Z<p>Jesse: </p>
<hr />
<div>{{SecReviewInfo<br />
|SecReview name=Don't exit fullscreen when focusing window on different display<br />
|SecReview target=<bugzilla><br />
{<br />
"id":"724554"<br />
}<br />
</bugzilla><br />
}}<br />
<br />
=== Goal of Feature, what is trying to be achieved (problem solved, use cases, etc) ===<br />
* Multiple monitors lose fullscreen on focus change<br />
** video full screen in one monitor and work on something else on the other<br />
** or have 2 monitors have different things full screen<br />
** Current plan is to show the full-screen warning again for 4 seconds whenever a full-screen page regains focus.<br />
<br />
====Mac Spaces questions====<br />
* Will this allow you to use multiple spaces on a single monitor? (With one in full-screen mode and another showing another app, or another Firefox tab)<br />
** Probably? might need to ask zpao.<br />
* With multiple monitors, mac's concept of spaces and full-screen tends to affect all monitors at once :/<br />
<br />
=== What solutions/approaches were considered other than the proposed solution? ===<br />
* Showing the warning again for 4 seconds upon return seems like overkill.<br />
** How about just one second?<br />
** How about a smaller warning? (Perhaps a watermark, if we can make it hard to hide)<br />
|SecReview threat brainstorming=* The "warning when switching between two full-screen windows" might be defeatable, when a single site is full-screen in both windows (immersive demos and games)<br />
<br />
== Threat Brainstorming ==<br />
* What if a web page lies about where focus is?<br />
** It can't prevent mouse clicks <br />
*** Lies about where the mouse cursor is?<br />
* This isn't really worse than the situation with one full-screen window<br />
<br />
{{SecReviewActionStatus<br />
|SecReview action item status=None<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Reviews/Mouse-Pointer_Lock&diff=530436Security/Reviews/Mouse-Pointer Lock2013-02-26T19:16:30Z<p>Jesse: </p>
<hr />
<div>{{SecReviewInfo<br />
|SecReview name=Extend Pointer Lock (Mouse Lock) for non-fullscreen elements<br />
|SecReview target=<bugzilla><br />
{<br />
"id":"822654"<br />
}<br />
</bugzilla><br />
}}<br />
<br />
=== Goal of Feature, what is trying to be achieved (problem solved, use cases, etc) ===<br />
* Allow pointer lock when not in full screen mode ( https://bugzilla.mozilla.org/show_bug.cgi?id=822654 and https://wiki.mozilla.org/Security/Reviews/Mouse-Pointer_Lock )<br />
* Current plan: in response to a click, a web page may activate a doorhanger "Do you want to allow this site to go into pointer-lock mode?"<br />
** Note that pointer lock comes free with full-screen. Full-screen asks for forgiveness while pointer-lock-alone asks for permission.<br />
* Keeping the existing model for pointer lock during full-screen.<br />
<br />
== Threat Brainstorming ==<br />
* How do we communicate the question of whether to allow pointer lock? The phrase "pointer lock" doesn't really convey the concept, even to users who have seen games use it.<br />
** Chrome says "Disable your mouse cursor"<br />
** "Use your mouse to control something other than your cursor"<br />
* Can users always use Esc to get out?<br />
* What happens if you're in pointer lock and you switch apps or switch tabs?<br />
* What happens to trackpad multi-touch or gestures (scroll, pinch, etc)<br />
** We already have a touch API?<br />
* What happens on devices that have both touch and mouse?<br />
** If you touch outside the content area, you're probably taking focus away, so it will probably disable content lock?<br />
* What effect does it have on touch-only devices?<br />
** Maybe we should tell the page it was denied? A game that wants to support touch will need to listen for touch events.<br />
<br />
{{SecReviewActionStatus<br />
|SecReview action item status=In Progress<br />
|SecReview action items=* Can we make sure that Esc (and cursor keys) cannot be used as a "user-triggered event handler" for the purpose of opening popups etc? Or maybe only a whitelist of keycodes / charcodes (space, enter, printable characters) https://bugzilla.mozilla.org/show_bug.cgi?id=748198<br />
** This will break the Doom case of "Esc opens the menu and releases pointer lock; Esc again closes the menu and regains pointer lock". Games like that will have to use a different keybinding for their in-game menu with a fake cursor, or put an item on the menu for resuming the game. (Just like a full-screen game has to use a key other than Esc for its menu.)<br />
* [mwobensmith?] Test what happens when you have a device with both touch and cursor.<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Bugmasters/Guide&diff=525728Bugmasters/Guide2013-02-21T21:02:36Z<p>Jesse: /* Advanced bugmastery */</p>
<hr />
<div>Welcome, bugmasters! Managing and sorting bugs, or "triaging" can mean many different things to different people and teams. Here are some paths to contribution. <br />
<br />
This page is a rough draft; please help improve it!<br />
<br />
===Starting up as a bugmaster=== <br />
<br />
* Make a [https://bugzilla.mozilla.org bugzilla.mozilla.org] account, and confirm it through email. <br />
* Read the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines bug writing guidelines], which has best practices for bug reports.<br />
* Join us in the irc channel on #bugmasters and introduce yourself. We can help get you started.<br />
* Take a look at some Bugzilla bug lists and individual bugs.<br />
* Download and install the latest nightly build for the product you're testing (e.g. [http://nightly.mozilla.org/ Firefox Nightly]).<br />
* Set up a [http://kb.mozillazine.org/Shortcut_to_a_specific_profile testing profile] for that product, separate from any work or personal profiles you use.<br />
* Become familiar with examples of [[Bugmasters/Guide/Responses|common responses to newly filed bugs]].<br />
* Become familiar with [http://www.squarefree.com/bugzilla/quicksearch-help.html Bugzilla QuickSearch].<br />
<br />
===Beginning bugmastering=== <br />
<br />
If you're new to bugmastering, it will be easiest to tackle early bug triage and tasks such as: <br />
<br />
* Very old bugs that are likely to be already fixed or no longer relevant. Find them and close them, or request more information and tag them "closeme".<br />
* Website bugs that are relatively easy to confirm. (Broken links and so on.) <br />
* Bugs marked in the whiteboard field as dupeme or closeme. <br />
* Bugs in your particular field of expertise. <br />
* Incoming, untriaged bugs. <br />
** Bugs [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem;remaction=run;namedcmd=Bugs%20Filed%20Today;sharer_id=159758;list_id=5631064 reported in the last 24 hours]<br />
** Report for [https://bugzilla.mozilla.org/page.cgi?id=triage_reports.html&action=run&product=Firefox&filter_commenter=1&commenter=reporter&commenter_is=&last=30&last_is=&component=Untriaged Firefox untriaged bugs that are UNCONFIRMED and where the bug reporter is the last commenter]. <br />
<br />
Note that the best way to get started though is to join us on #bugmasters on IRC and we can work with you.<br />
<br />
These are some good ways to test the waters. <br />
<br />
Over time, beginning bugmasters will build up more and more knowledge about how to move bugs from one part of their life cycle to another. As the bugmaster community grows it will be crucial for us to listen to feedback from people with all levels of experience, so we can improve how we work. Please help to improve this page and other documentation!<br />
<br />
===Advanced bugmastery===<br />
<br />
* Ask for [https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html canconfirm permissions] if you have edited or filed at least three bugs that are in good shape.<br />
* Email to ask for editbugs permissions if you find you need to change a field (such as the title) in several bugs, but could not, and had to make the change in comments instead.<br />
<br />
===Branching out as an expert bugmaster=== <br />
Here are some possible ways to dive deeper into bug triage and management. Please add more to this list as we evolve the bugmaster pages! <br />
<br />
* Pick a product or component to specialize in. <br />
* Read its related wiki.mozilla.org pages and MDN pages.<br />
* Join [https://wiki.mozilla.org/IRC#Commonly_Used_Mozilla_IRC_Channels IRC channels] for that area.<br />
* Become familiar with the [https://wiki.mozilla.org/Modules/All module owners and peers].<br />
* Set up [http://bookmaniac.org/thrills-chills-filters-and-bugmail/ bugmail folders and filters] to watch your bugmaster specialty.<br />
* Tag "good first triage" bugs with the whiteboard tag easytriage.<br />
<br />
==More links on triaging and managing bugs== <br />
Miscellaneous documentation and triage instructions, useful for bugmasters. We'll use these to help us overhaul the general triaging and bug workflow. <br />
<br />
===Bugzilla docs=== <br />
* [http://developer.mozilla.org/en/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] from MDN <br />
* [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla etiquette] from BMO <br />
* [https://developer.mozilla.org/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla What to do and what not to do in Bugzilla] from MDN <br />
* [https://developer.mozilla.org/en-US/docs/Bug_writing_guidelines Bug writing guidelines] <br />
* [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/ How to write a proper bug] from QMO <br />
* [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug-part-2/ How to write a proper bug part 2] from QMO <br />
<br />
===Triage docs=== <br />
* [https://wiki.mozilla.org/Modules/All Module owners] <br />
* [https://support.mozilla.org/en-US/kb/answering-questions-support-forum#w_doing-investigation Doing Investigation] For support questions, but often useful for bug triage.<br />
* [https://wiki.mozilla.org/QA/Triage QA/Triage] from 2008/2010 <br />
* [https://wiki.mozilla.org/User:Tyler/Triage_Guidelines Triage guidelines by Tyler] <br />
* [https://wiki.mozilla.org/User:Tyler/BMOsurvival BMO Survival] Another great writeup by Tyler <br />
* [https://developer.mozilla.org/en-US/docs/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] from MDN <br />
* [https://developer.mozilla.org/en/docs/Reducing_testcases Reducing testcases] from MDN <br />
* [https://etherpad.mozilla.org/Firefox18-bug-verification Bug verification days] Mondays in #qa are bug verification days for Firefox Desktop fixed bugs (near end of lifecycle) <br />
* [https://wiki.mozilla.org/QA_SoftVision_Team/Desktop#Bug_triage Softvision triage process]<br />
<br />
===Triage docs for specific teams or modules=== <br />
* [https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs Triaging crash bugs]. Tackle bugs that may have caused a crash. Learn how to find crash bugs, add complete steps to reproduce, a stack trace, and a [https://developer.mozilla.org/en-US/docs/Reducing_testcases reduced testcase] for a crash bug, then tag it for a developer to review. The [https://wiki.mozilla.org/CrashKill/DesktopTriage CraskKill team] triage notes may be helpful.<br />
<br />
* Firefox Triage days (tuesday) https://etherpad.mozilla.org/firefox-triage Backchannel: #fx-team<br />
<br />
* Triaging within a team, for example the SDK/ Jetpack team's triage meetings. https://wiki.mozilla.org/Jetpack/Triage_Process <br />
<br />
* [https://developer.mozilla.org/en-US/docs/Triaging_Networking_Bugs Triaging networking bugs]. An explanation of the networking components, whiteboard tags, and other processes used for triaging by developers in this area of Mozilla. <br />
<br />
* [https://developer.mozilla.org/en-US/docs/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] (this page is a bit out of date)<br />
<br />
===Some Bugmastering communities=== <br />
Here are a few other [http://en.wikipedia.org/wiki/Free_and_open_source_software FLOSS] projects that have bug-focused communities. <br />
* [https://live.gnome.org/Bugsquad Bugsquad] GNOME's Bugsquad community. <br />
* [http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml Bug Wranglers] Gentoo bug wrangler community. <br />
* WikiMedia's [http://www.mediawiki.org/wiki/Bug_management/Triage bug triage pages].</div>Jessehttps://wiki.mozilla.org/index.php?title=Bugmasters/Guide&diff=525635Bugmasters/Guide2013-02-21T19:11:38Z<p>Jesse: /* Starting up as a bugmaster */</p>
<hr />
<div>Welcome, bugmasters! Managing and sorting bugs, or "triaging" can mean many different things to different people and teams. Here are some paths to contribution. <br />
<br />
This page is a rough draft; please help improve it!<br />
<br />
===Starting up as a bugmaster=== <br />
<br />
* Make a [https://bugzilla.mozilla.org bugzilla.mozilla.org] account, and confirm it through email. <br />
* Read the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines bug writing guidelines], which has best practices for bug reports.<br />
* Join us in the irc channel on #bugmasters and introduce yourself. We can help get you started.<br />
* Take a look at some Bugzilla bug lists and individual bugs.<br />
* Download and install the latest nightly build for the product you're testing (e.g. [http://nightly.mozilla.org/ Firefox Nightly]).<br />
* Set up a [http://kb.mozillazine.org/Shortcut_to_a_specific_profile testing profile] for that product, separate from any work or personal profiles you use.<br />
* Become familiar with examples of [[Bugmasters/Guide/Responses|common responses to newly filed bugs]].<br />
* Become familiar with [http://www.squarefree.com/bugzilla/quicksearch-help.html Bugzilla QuickSearch].<br />
<br />
===Beginning bugmastering=== <br />
<br />
If you're new to bugmastering, it will be easiest to tackle early bug triage and tasks such as: <br />
<br />
* Very old bugs that are likely to be already fixed or no longer relevant. Find them and close them, or request more information and tag them "closeme".<br />
* Website bugs that are relatively easy to confirm. (Broken links and so on.) <br />
* Bugs marked in the whiteboard field as dupeme or closeme. <br />
* Bugs in your particular field of expertise. <br />
* Incoming, untriaged bugs. <br />
** Bugs [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem;remaction=run;namedcmd=Bugs%20Filed%20Today;sharer_id=159758;list_id=5631064 reported in the last 24 hours]<br />
** Report for [https://bugzilla.mozilla.org/page.cgi?id=triage_reports.html&action=run&product=Firefox&filter_commenter=1&commenter=reporter&commenter_is=&last=30&last_is=&component=Untriaged Firefox untriaged bugs that are UNCONFIRMED and where the bug reporter is the last commenter]. <br />
<br />
Note that the best way to get started though is to join us on #bugmasters on IRC and we can work with you.<br />
<br />
These are some good ways to test the waters. <br />
<br />
Over time, beginning bugmasters will build up more and more knowledge about how to move bugs from one part of their life cycle to another. As the bugmaster community grows it will be crucial for us to listen to feedback from people with all levels of experience, so we can improve how we work. Please help to improve this page and other documentation!<br />
<br />
===Advanced bugmastery===<br />
<br />
* Ask for [https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html canconfirm permissions] if you have edited or filed at least three bugs that are in good shape.<br />
* Email to ask for editbugs permissions if you find you need to change a field (such as the title) in several bugs, but could not, and had to make the change in comments instead. <br />
<br />
<br />
===Branching out as an expert bugmaster=== <br />
Here are some possible ways to dive deeper into bug triage and management. Please add more to this list as we evolve the bugmaster pages! <br />
<br />
* Pick a product or component to specialize in. <br />
* Read its related wiki.mozilla.org pages and MDN pages.<br />
* Join [https://wiki.mozilla.org/IRC#Commonly_Used_Mozilla_IRC_Channels IRC channels] for that area.<br />
* Become familiar with the [https://wiki.mozilla.org/Modules/All module owners and peers].<br />
* Set up [http://bookmaniac.org/thrills-chills-filters-and-bugmail/ bugmail folders and filters] to watch your bugmaster specialty.<br />
* Tag "good first triage" bugs with the whiteboard tag easytriage.<br />
<br />
==More links on triaging and managing bugs== <br />
Miscellaneous documentation and triage instructions, useful for bugmasters. We'll use these to help us overhaul the general triaging and bug workflow. <br />
<br />
===Bugzilla docs=== <br />
* [http://developer.mozilla.org/en/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] from MDN <br />
* [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla etiquette] from BMO <br />
* [https://developer.mozilla.org/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla What to do and what not to do in Bugzilla] from MDN <br />
* [https://developer.mozilla.org/en-US/docs/Bug_writing_guidelines Bug writing guidelines] <br />
* [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/ How to write a proper bug] from QMO <br />
* [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug-part-2/ How to write a proper bug part 2] from QMO <br />
<br />
===Triage docs=== <br />
* [https://wiki.mozilla.org/Modules/All Module owners] <br />
* [https://support.mozilla.org/en-US/kb/answering-questions-support-forum#w_doing-investigation Doing Investigation] For support questions, but often useful for bug triage.<br />
* [https://wiki.mozilla.org/QA/Triage QA/Triage] from 2008/2010 <br />
* [https://wiki.mozilla.org/User:Tyler/Triage_Guidelines Triage guidelines by Tyler] <br />
* [https://wiki.mozilla.org/User:Tyler/BMOsurvival BMO Survival] Another great writeup by Tyler <br />
* [https://developer.mozilla.org/en-US/docs/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] from MDN <br />
* [https://developer.mozilla.org/en/docs/Reducing_testcases Reducing testcases] from MDN <br />
* [https://etherpad.mozilla.org/Firefox18-bug-verification Bug verification days] Mondays in #qa are bug verification days for Firefox Desktop fixed bugs (near end of lifecycle) <br />
* [https://wiki.mozilla.org/QA_SoftVision_Team/Desktop#Bug_triage Softvision triage process]<br />
<br />
===Triage docs for specific teams or modules=== <br />
* [https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs Triaging crash bugs]. Tackle bugs that may have caused a crash. Learn how to find crash bugs, add complete steps to reproduce, a stack trace, and a [https://developer.mozilla.org/en-US/docs/Reducing_testcases reduced testcase] for a crash bug, then tag it for a developer to review. The [https://wiki.mozilla.org/CrashKill/DesktopTriage CraskKill team] triage notes may be helpful.<br />
<br />
* Firefox Triage days (tuesday) https://etherpad.mozilla.org/firefox-triage Backchannel: #fx-team<br />
<br />
* Triaging within a team, for example the SDK/ Jetpack team's triage meetings. https://wiki.mozilla.org/Jetpack/Triage_Process <br />
<br />
* [https://developer.mozilla.org/en-US/docs/Triaging_Networking_Bugs Triaging networking bugs]. An explanation of the networking components, whiteboard tags, and other processes used for triaging by developers in this area of Mozilla. <br />
<br />
* [https://developer.mozilla.org/en-US/docs/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] (this page is a bit out of date)<br />
<br />
===Some Bugmastering communities=== <br />
Here are a few other [http://en.wikipedia.org/wiki/Free_and_open_source_software FLOSS] projects that have bug-focused communities. <br />
* [https://live.gnome.org/Bugsquad Bugsquad] GNOME's Bugsquad community. <br />
* [http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml Bug Wranglers] Gentoo bug wrangler community. <br />
* WikiMedia's [http://www.mediawiki.org/wiki/Bug_management/Triage bug triage pages].</div>Jessehttps://wiki.mozilla.org/index.php?title=Bugmasters/Guide&diff=525567Bugmasters/Guide2013-02-21T16:49:42Z<p>Jesse: /* Starting up as a bugmaster */</p>
<hr />
<div>Welcome, bugmasters! Managing and sorting bugs, or "triaging" can mean many different things to different people and teams. Here are some paths to contribution. <br />
<br />
This page is a rough draft; please help improve it!<br />
<br />
===Starting up as a bugmaster=== <br />
<br />
* Make a [https://bugzilla.mozilla.org bugzilla.mozilla.org] account, and confirm it through email. <br />
* Read the [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines bug writing guidelines], which has best practices for bug reports.<br />
* Join us in the irc channel on #bugmasters and introduce yourself. We can help get you started.<br />
* Take a look at some Bugzilla bug lists and individual bugs.<br />
* Download and install the latest nightly build for the product you're testing (e.g. [http://nightly.mozilla.org/ Firefox Nightly]).<br />
* Set up a [http://kb.mozillazine.org/Shortcut_to_a_specific_profile testing profile] for that product, separate from any work or personal profiles you use.<br />
* Become familiar with examples of [[Bugmasters/Guide/Responses|common responses to newly filed bugs]].<br />
<br />
===Beginning bugmastering=== <br />
<br />
If you're new to bugmastering, it will be easiest to tackle early bug triage and tasks such as: <br />
<br />
* Very old bugs that are likely to be already fixed or no longer relevant. Find them and close them, or request more information and tag them "closeme".<br />
* Website bugs that are relatively easy to confirm. (Broken links and so on.) <br />
* Bugs marked in the whiteboard field as dupeme or closeme. <br />
* Bugs in your particular field of expertise. <br />
* Incoming, untriaged bugs. <br />
** Bugs [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem;remaction=run;namedcmd=Bugs%20Filed%20Today;sharer_id=159758;list_id=5631064 reported in the last 24 hours]<br />
** Report for [https://bugzilla.mozilla.org/page.cgi?id=triage_reports.html&action=run&product=Firefox&filter_commenter=1&commenter=reporter&commenter_is=&last=30&last_is=&component=Untriaged Firefox untriaged bugs that are UNCONFIRMED and where the bug reporter is the last commenter]. <br />
<br />
Note that the best way to get started though is to join us on #bugmasters on IRC and we can work with you.<br />
<br />
These are some good ways to test the waters. <br />
<br />
Over time, beginning bugmasters will build up more and more knowledge about how to move bugs from one part of their life cycle to another. As the bugmaster community grows it will be crucial for us to listen to feedback from people with all levels of experience, so we can improve how we work. Please help to improve this page and other documentation!<br />
<br />
===Advanced bugmastery===<br />
<br />
* Ask for [https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html canconfirm permissions] if you have edited or filed at least three bugs that are in good shape.<br />
* Email to ask for editbugs permissions if you find you need to change a field (such as the title) in several bugs, but could not, and had to make the change in comments instead. <br />
<br />
<br />
===Branching out as an expert bugmaster=== <br />
Here are some possible ways to dive deeper into bug triage and management. Please add more to this list as we evolve the bugmaster pages! <br />
<br />
* Pick a product or component to specialize in. <br />
* Read its related wiki.mozilla.org pages and MDN pages.<br />
* Join [https://wiki.mozilla.org/IRC#Commonly_Used_Mozilla_IRC_Channels IRC channels] for that area.<br />
* Become familiar with the [https://wiki.mozilla.org/Modules/All module owners and peers].<br />
* Set up [http://bookmaniac.org/thrills-chills-filters-and-bugmail/ bugmail folders and filters] to watch your bugmaster specialty.<br />
* Tag "good first triage" bugs with the whiteboard tag easytriage.<br />
<br />
==More links on triaging and managing bugs== <br />
Miscellaneous documentation and triage instructions, useful for bugmasters. We'll use these to help us overhaul the general triaging and bug workflow. <br />
<br />
===Bugzilla docs=== <br />
* [http://developer.mozilla.org/en/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] from MDN <br />
* [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla etiquette] from BMO <br />
* [https://developer.mozilla.org/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla What to do and what not to do in Bugzilla] from MDN <br />
* [https://developer.mozilla.org/en-US/docs/Bug_writing_guidelines Bug writing guidelines] <br />
* [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/ How to write a proper bug] from QMO <br />
* [https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug-part-2/ How to write a proper bug part 2] from QMO <br />
<br />
===Triage docs=== <br />
* [https://wiki.mozilla.org/Modules/All Module owners] <br />
* [https://support.mozilla.org/en-US/kb/answering-questions-support-forum#w_doing-investigation Doing Investigation] For support questions, but often useful for bug triage.<br />
* [https://wiki.mozilla.org/QA/Triage QA/Triage] from 2008/2010 <br />
* [https://wiki.mozilla.org/User:Tyler/Triage_Guidelines Triage guidelines by Tyler] <br />
* [https://wiki.mozilla.org/User:Tyler/BMOsurvival BMO Survival] Another great writeup by Tyler <br />
* [https://developer.mozilla.org/en-US/docs/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] from MDN <br />
* [https://developer.mozilla.org/en/docs/Reducing_testcases Reducing testcases] from MDN <br />
* [https://etherpad.mozilla.org/Firefox18-bug-verification Bug verification days] Mondays in #qa are bug verification days for Firefox Desktop fixed bugs (near end of lifecycle) <br />
* [https://wiki.mozilla.org/QA_SoftVision_Team/Desktop#Bug_triage Softvision triage process]<br />
<br />
===Triage docs for specific teams or modules=== <br />
* [https://developer.mozilla.org/en-US/docs/Triaging_crash_bugs Triaging crash bugs]. Tackle bugs that may have caused a crash. Learn how to find crash bugs, add complete steps to reproduce, a stack trace, and a [https://developer.mozilla.org/en-US/docs/Reducing_testcases reduced testcase] for a crash bug, then tag it for a developer to review. The [https://wiki.mozilla.org/CrashKill/DesktopTriage CraskKill team] triage notes may be helpful.<br />
<br />
* Firefox Triage days (tuesday) https://etherpad.mozilla.org/firefox-triage Backchannel: #fx-team<br />
<br />
* Triaging within a team, for example the SDK/ Jetpack team's triage meetings. https://wiki.mozilla.org/Jetpack/Triage_Process <br />
<br />
* [https://developer.mozilla.org/en-US/docs/Triaging_Networking_Bugs Triaging networking bugs]. An explanation of the networking components, whiteboard tags, and other processes used for triaging by developers in this area of Mozilla. <br />
<br />
* [https://developer.mozilla.org/en-US/docs/Confirming_unconfirmed_bugs Confirming unconfirmed bugs] (this page is a bit out of date)<br />
<br />
===Some Bugmastering communities=== <br />
Here are a few other [http://en.wikipedia.org/wiki/Free_and_open_source_software FLOSS] projects that have bug-focused communities. <br />
* [https://live.gnome.org/Bugsquad Bugsquad] GNOME's Bugsquad community. <br />
* [http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml Bug Wranglers] Gentoo bug wrangler community. <br />
* WikiMedia's [http://www.mediawiki.org/wiki/Bug_management/Triage bug triage pages].</div>Jessehttps://wiki.mozilla.org/index.php?title=SecurityEngineering/Roadmap&diff=487211SecurityEngineering/Roadmap2012-11-13T20:58:37Z<p>Jesse: </p>
<hr />
<div><small>[[Roadmaps|&lt; Product Roadmaps]] </small> <br />
<br />
<section begin="summary" />{{RoadmapSummary<br />
|icon=larry.png<br />
|pagelocation=Security/Roadmap<br />
|pagetitle=Product Security Feature Roadmap<br />
|owner=[[User:Ladamski|Lucas Adamski]]<br />
|updated=Weekly<br />
|status=Draft<br />
|description=Security at Mozilla can be thought of a set of principles that are reflected in the products we ship, but also in the impact Mozilla has on the entire web. As such our security roadmap should reflect the real security improvements we need to make to our products to reflect the evolving security landscape, but also the ambitious impact we'd like to have on all web users.}}<section end="summary" /> <br />
<br />
{{Draft}} <br />
<br />
<br> <br />
<br />
= Vision =<br />
<br />
Security at Mozilla can be thought of a set of principles that are reflected in the products we ship, but also in the impact Mozilla has on the entire web. <br />
<br />
= Themes and Goals =<br />
<br />
Web users are under constant attack from a wide variety of opponents, many of whom are merely opportunistic, but also by a minority of very clever and determined attackers.&nbsp; To protect users, we need to improve our current products to keep pace with these evolving threats, but we are ultimately limited in what we can do unilaterally within our products.&nbsp; We must also drive innovative solutions that require the participation of other vital players in the web ecosystem, including standards bodies, internet technology vendors, web developers, web admins and web frameworks. <br />
<br />
As such, security engineering at Mozilla has two primary themes:<br />
<br />
*Product Hardening: Protect our users directly from an ever-increasing volume &amp; sophistication of online attacks, by directly improving the products and services we deliver<br />
*Security Leadership: Drive innovative security solutions to enable the wider web ecosystem of web developers, web admins and users to adapt to evolving web technologies and their corresponding security threats.<br />
<br />
Here the concrete goals are segmented into themes. Some goals may potentially fit into multiple themes, but are only identified here under the most relevant one. <br />
<br />
Survey taken in early 2011 to identify and prioritize potential features for our security roadmap. The results of this survey are [https://spreadsheets.google.com/spreadsheet/pub?hl=en&hl=en&key=0AtpjIJJ66IkGdEQwOThzdHVFS0V4aUZUOWoxZXc3alE&output=html available as a Google doc] or as PDF: [[Image:Security roadmap survey.pdf]]. <br />
<br />
'''NOTE:''' these goals are tentative and more may be added or some may be dropped.<br />
<br />
= Roadmap =<br />
'''Items with Feature Pages'''<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 30%;">Feature</td><br />
<td class="header" style="width: 15%;">Team</td><br />
<td class="header" style="width: 15%;">Stage</td><br />
<td class="header" style="width: 20%;">Directly Responsible Individual</td><br />
<td class="header" style="width: 15%;">Theme</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] [[Feature stage::!Complete]] [[Feature roadmap::Security]] OR [[Feature secondary roadmap::Security]]<br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature engineering team#<br />
| ?Feature stage#<br />
| ?Feature feature manager#<br />
| ?Feature theme#<br />
| mainlabel=-<br />
| sort=Feature priority,Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
= Outcomes: =<br />
There are some major outcomes that can be realized by completion of multiple features. These features already show up on the master list above, but this categorizes them into desired outcomes.<br />
<br />
=== HTTPS can be used as default ===<br />
Right now, when users navigate to a web site without specifying the protocol or scheme, Firefox assumes "http" as the scheme. For optimal protection from eavesdropping and for encryption of cookies and other HTTP request data in transit, we should be able to attempt HTTPS and fall back to HTTP only when absolutely necessary.<br />
<br />
This outcome can be realized when Firefox can be changed to default to the HTTPS scheme instead of HTTP.<br />
<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 35%;">Feature</td><br />
<td class="header" style="width: 10%;">Stage</td><br />
<td class="header" style="width: 10%;">Release target</td><br />
<td class="header" style="width: 20%;">Product manager</td><br />
<td class="header" style="width: 20%;">Feature manager</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] <br />
[[Feature name::HSTS Preload List]] OR <br />
[[Feature name::HTTPS (SSL) Google Search]] OR<br />
[[Feature name::OCSP Stapling]] <br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature stage#<br />
| ?Feature version#<br />
| ?Feature product manager#<br />
| ?Feature feature manager#<br />
| mainlabel=-<br />
| sort=Feature priority, Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
=Ideas Not Yet Awesome Enough=<br />
Apparently these ideas are not yet great enough to merit feature pages. If you disagree, you can [[Features/Create new | create a new feature page]] for it! Just make sure to put "Security" in the primary or secondary roadmap field.<br />
<br />
{|class=wikitable<br />
|-<br />
! Item <br />
! Owner<br />
|-<br />
| First-run warning for new plugins<br> <br />
| <br><br />
|-<br />
| [https://wiki.mozilla.org/NPAPI:Pepper2 Plugin sandboxing]<br> <br />
| <br><br />
|-<br />
| Malloc should be infallible<br> <br />
| <br><br />
|-<br />
| TLS&nbsp;1.2 support<br> <br />
| <br><br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=432687 Eviltraps meta-bug] (prevents users from leaving a page)<br> <br />
| <br><br />
|-<br />
| Notify user of malware in their crash signatures<br><br />
| <br><br />
|-<br />
| Expose HSTS&nbsp;and other security browser state to plugins (NPAPI)<br> <br />
| <br><br />
|-<br />
| Ignore autocomplete="off" for password fields<br />
| <br><br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=663566 Content Security Policy revisions]<br />
| Brandon Sterne<br />
|-<br />
| Clickjacking mitigations <br />
| <br />
|-<br />
| X-Content-Type-Options <br />
| <br />
|-<br />
| toStaticHTML <br />
| <br />
|-<br />
| Block DLLs without ASLR <br />
| <br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=677797 Force ASLR or similar mitigations (EMET)]<br />
| <br />
|}<br />
<br />
<br><br />
<br />
=Completed Features=<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 30%;">Feature</td><br />
<td class="header" style="width: 15%;">Team</td><br />
<td class="header" style="width: 15%;">Stage</td><br />
<td class="header" style="width: 20%;">Product Manager</td><br />
<td class="header" style="width: 15%;">Theme</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] [[Feature stage::Complete]] [[Feature roadmap::Security]] OR [[Feature secondary roadmap::Security]] [[Feature stage::Complete]] <br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature engineering team#<br />
| ?Feature stage#<br />
| ?Feature product manager#<br />
| ?Feature theme#<br />
| mainlabel=-<br />
| sort=Feature priority,Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
<br />
=Related Info=<br />
<br />
Links to implementation plan and progress: <br />
<br />
*[[Firefox/Flight Tracking]] <br />
*[[Firefox/Features]]<br />
<br />
Inputs into the security roadmap:<br />
<br />
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=kw:sec-want sec-want bugs] that are both important and complex<br />
<br />
[[Category:Roadmaps]]</div>Jessehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2012-10-08&diff=477353WeeklyUpdates/2012-10-082012-10-08T18:17:57Z<p>Jesse: /* Introducing New Hires */</p>
<hr />
<div><small>[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]</small><br />
<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==<br />
* Everybody who worked on the stub installer, both before and on Friday, when we launched it with a Herculean effort! [stephend]<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
*firefox channel meeting has been changed to 10am pst https://wiki.mozilla.org/Firefox/Channels/Meetings/2012-10-09 <br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
* 3PM PSt we are having a support meeting for mobile and b2g https://etherpad.mozilla.org/mobile-meet-2012-10-10 -satdav<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
* https://quality.mozilla.org/2012/10/sumo-questions-day-thursday-october-11th/ we have got a sumo day for people who is interested all day backend support at #sumo<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
the support mobile meetings will be every wednesday for the next couple of weeks until further notice in michelle luna room<br />
<br />
== Product Status Updates (voice updates) ==<br />
<br />
=== Firefox Desktop ===<br />
''Speaker Location:''<br />
<br />
=== Firefox Mobile ===<br />
''Speaker Location:'' <br />
<br />
=== Thunderbird ===<br />
''Speaker Location:'' <br />
<br />
=== Older Branch Work ===<br />
''Speaker Location:'' <br />
<br />
=== Webmaker ===<br />
''Speaker Location:''<br />
<br />
=== Identity ===<br />
''Speaker Location:''<br />
<br />
=== Services ===<br />
''Speaker Location:''<br />
<br />
=== Firefox OS ===<br />
''Speaker Location:'PDX'<br />
<br />
* Product teams are reviewing the requirements against the specifications and the implementation to ensure we've got every square inch of the OS validatable.<br />
* Development teams focusing on bug fixing and performance, including operation SLIM FAST.<br />
* Dogfooding devices are in, porting in progress.<br />
<br />
=== Grow Mozilla ===<br />
''Speaker Location: Kate in San Fransisco''<br />
<br />
* The deadline to submit a proposal for MozCamp Asia is October 15th. For more information on how to submit a proposal, please see [https://wiki.mozilla.org/MozCampAsia2012/ParticipationProposals here]<br />
* Mozilla Reps: Everything you wanted to know but never dared to ask. [https://reps.mozilla.org Mozilla Reps] Brownbag this Thursday 2012-10-11 13:30 PST in MV.<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Introducing Webmaker, the Product<br />
| Erin Knight (phone)<br />
| Webmaker!<br />
| [http://dl.dropbox.com/u/1605183/webmaker_slides.pdf Slides]<br />
| [http://webmaker.org http://webmaker.org]; [http://erinknight.com http://erinknight.com]; erin@mozillafoundation.org<br />
|-<br />
| Click-to-play plugins and prompting updates<br />
| David Keeler (pdx)<br />
| Plugins<br />
| <br />
| [https://blog.mozilla.org/addons/2012/10/05/prompting-our-users-to-update-their-plugins/ Blog post by Jorge]<br />
|-<br />
|}<br />
<br />
<br />
<br />
=== Introducing New Hires ===<br />
{| class="fullwidth-table"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
| John Bernard<br />
| David Slater<br />
| London<br />
| Carrier and OEM Marketing for Firefox OS<br />
|-<br />
| Karolina Shaw<br />
| Barbara Hueppe<br />
| Berlin<br />
| Communications Manager<br />
|-<br />
| Felix Klock<br />
| David Herman<br />
| France<br />
| Research Engineer<br />
|-<br />
|-<br />
| Massimo Gervasini [:mgerva]<br />
| Chris AtLee<br />
| Vidyo (if possible)<br />
| Making Release Engineering even more awesome<br />
|-<br />
| Justin Wood [:Callek]<br />
| Chris Cooper<br />
| Remote (Phone)<br />
| Tegras and Pandas and testing (oh my)<br />
|-<br />
| Eric Pang [:epang]<br />
| Ian Barlow<br />
| Toronto<br />
| Production Design on Firefox for Android and Firefox OS<br />
|-<br />
| William Chen<br />
| Johnny Stenback<br />
| San Francisco<br />
|<br />
|-<br />
| Nikhil Marathe<br />
| Johnny Stenback<br />
| Mountain View<br />
|<br />
|-<br />
| Matthew Wobensmith<br />
| Bob Moss<br />
| Mountain View<br />
| Security QA<br />
|-<br />
| Erv Thomas<br />
| Mathew Caldwell<br />
| Mountain View<br />
| College Recruiting<br />
|-<br />
| Nikhil Marathe<br />
| Doug Turner<br />
| Mountain View<br />
| Content/DOM<br />
|-<br />
| Aaron Druck<br />
| Todd Simpson<br />
| Mountain View<br />
| User Experience Designer<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new intern?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Roundtable ==<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Services ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
*Affiliates<br />
**Coming soon - [https://bugzilla.mozilla.org/show_bug.cgi?id=760631 bug 760631] - Allow affiliates to link back to a personal website - display website on leaderboard <br />
*Mozillians (automation)<br />
**The team is doing an outstanding job of fixing and refactoring our automation suite. A huge shout our and thank you!<br />
**In discussions to move the project to continuous deployment.<br />
*Socorro<br />
**Milestone 21 shipped Thursday -- [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;target_milestone=21;product=Socorro;list_id=4553745 features/bugs]<br />
**Django-based Socorro is queued for sec review<br />
B2G<br />
*We need help doing manual testing- B2G: browser & email client<br />
<br />
==== QA Community ====<br />
<br />
=== Automation & Tools ===<br />
* BIG FREAKIN NEWS: sut_tools is updated with modern devicemanager and many patches. This gets us 90% of the way towards changes needed to that toolchain to run on the panda boards<br />
* Minimal rooting for Android 2.3 phones up to (and including) 2.3.6 is now a 5 minute, pain free process. Contact bc for details<br />
* Created longer term [https://docs.google.com/spreadsheet/pub?key=0AnQFRWdkAbOVdHNEb1I5azdTNlJGQ05QU0JDT3FSeGc&output=html sheriffing goals]<br />
* We did a hard pivot toward B2G, our [https://wiki.mozilla.org/Auto-tools/Goals/2012Q4 revised goals are up], contact ctalbert if you have comments<br />
* More [https://wiki.mozilla.org/Auto-tools/Automation_Development/Meetings/121008 news here]<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
==== PR ====<br />
*[http://www.computerworld.com/s/article/9232137/Mozilla_previews_Metro_ized_Firefox_for_Windows_8 Mozilla previews 'Metro'-ized Firefox for Windows 8] <br />
*[http://www.ubergizmo.com/2012/10/mozilla-firefox-18-for-metro-preview-released/ Mozilla Firefox 18 for Metro preview released] <br />
*[http://www.webmonkey.com/2012/10/mozilla-takes-on-windows-8-with-firefox-metro-preview/ Mozilla Takes on Windows 8 With ‘Firefox Metro Preview’] <br />
<br />
*[http://securitywatch.pcmag.com/none/303335-mozilla-persona-identity-system-eliminates-passwords Mozilla Persona Identity System Eliminates Passwords] <br />
*[http://www.esecurityplanet.com/network-security/mozillas-persona-single-sign-on-launches-in-beta.html Mozilla's Persona Single Sign-On Launches in Beta]<br />
<br />
==== Events ====<br />
<br />
==== Creative Team ====<br />
<br />
==== Community Marketing ====<br />
<br />
=== Support ===<br />
<br />
=== Metrics ===<br />
<br />
=== Evangelism ===<br />
<br />
=== Labs ===<br />
<br />
=== Apps ===<br />
<br />
=== Developer Tools ===<br />
<br />
=== Add-ons ===<br />
<br />
=== Webdev ===<br />
<br />
=== L10n ===<br />
<br />
=== People Team ===<br />
<br />
=== WebFWD ===<br />
<br />
== Foundation Updates ==</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Meetings/SecurityAssurance/2012-09-18&diff=471698Security/Meetings/SecurityAssurance/2012-09-182012-09-18T23:32:11Z<p>Jesse: /* Agenda */</p>
<hr />
<div>{{SecAssuranceMeetingInfo}}<br />
{{TOC right}}<br />
=Agenda=<br />
* [Jesse] Meeting with Coverity tomorrow: 1pm Mountain View 3A<br />
** [yvan] Goals for meeting should be: get continuously up-to-date scans (which might require us uploading instrumented builds daily), a few new logins, and someone on our side who will look at the scan results.<br />
** [dveditz] My old login works! But the current scan is a year old.<br />
** [dveditz, choller] Let's start with specific warning types (rather than specific areas of the code)<br />
* [Jesse] I have some tweets for @mozsec! Tweet away!<br />
** https://bugzilla.mozilla.org/show_bug.cgi?id=62178<br />
*** security.mixed_content.block_active_content, security.mixed_content.block_display_content<br />
*** Currently a silent block<br />
*** We still need to work on UI for each kind of block, and then block active content by default.<br />
** enablePrivilege removal - link to mrbkap's posts?<br />
*** https://blog.mozilla.org/mrbkap/2012/09/12/security-checks-and-enableprivilege-in-gecko-part-1/<br />
*** https://bugzilla.mozilla.org/show_bug.cgi?id=546848<br />
*** Let's wait for the "what web sites should do now" parts 3 and 4 before tweeting<br />
** UserCSP<br />
*** Tanvi's post https://twitter.com/TanviHacks/status/247855586182582272<br />
* [gkw] Ideas for MozCamp Asia<br />
** asan / valgrind / fuzzing ionmonkey<br />
** Who else wants to go to MozCamp Asia? Yvan, Paul, Curtis, michal`, mgoodwin<br />
* Goals - Please keep status up to date - https://mana.mozilla.org/wiki/display/SECURITY/2012+-+Q3+Goals<br />
* [yvan] Security Deputies<br />
** who will help: mgoodwin, psiinon, curtis<br />
<br />
=Security Review Status (koenig)=<br />
* Completed in Q3 2012: <br />
* Number of Reviews Completed (so far this quarter):51(36)<br />
https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED;chfieldto=Now;chfield=resolution;query_format=advanced;chfieldfrom=2012-06-30;type0-0-0=anywords;component=Security%20Assurance%3A%20Review%20Request;product=mozilla.org;list_id=4428359<br />
* Number of Outstanding Reviews: 144(158)<br />
https://bugzilla.mozilla.org/buglist.cgi?chfieldto=Now;chfield=bug_status;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;component=Security%20Assurance%3A%20Review%20Request;list_id=4428360<br />
=Operations Security Update (Joe Stevensen)=<br />
No Update<br />
=Project Updates =<br />
Please don't leave blank. Add "No Update" if nothing has changed<br />
==Silent updates (rforbes / dveditz)==<br />
== B2G (Paul Theriault, David Chan) ==<br />
* testing is progressing. We are almost ready to write the dom access tests<br />
==Thunderbird (Adam Muntner) ==<br />
==Rust (Jesse Ruderman) ==<br />
==Mobile (Mark Goodwin) ==<br />
* Secreview on Monday for the new updater<br />
==Sync (Simon Bennetts & Adam Muntner) ==<br />
==Services (Simon Bennetts & Adam Muntner) ==<br />
==Social - Pancake (Mark Goodwin) ==<br />
* No update<br />
==Jetpack, Add-on SDK, Add-on Builder (Dan Veditz) ==<br />
==JS (Christian Holler) ==<br />
* IonMonkey landed \o/<br />
* [decoder] Fuzzing with --no-ti on x86/ARM to somewhat resemble ARMv6 configuration<br />
** [gkw] jsfunfuzz already randomly chooses to fuzz w/ --no-ti<br />
==DOM, XPConnect (Jesse Ruderman) ==<br />
==Layout, Style (Jesse Ruderman) ==<br />
==Automation Tools (Gary Kwong) ==<br />
==Web Developer Tools (Mark Goodwin) ==<br />
* Secreview soon for HTML Tree Editor (need to schedule)<br />
* Have been having fun hacking on CSP bits<br />
== Networking (Christoph Diehl) ==<br />
* Fuzzing WebRTC - https://bugzilla.mozilla.org/show_bug.cgi?id=fuzzing-webrtc<br />
== Graphics (Christoph Diehl) ===<br />
* No update<br />
== Networking ( Media / Codecs) ==<br />
== Market (Raymond Forbes) ==<br />
==Firefox APIs (Raymond Forbes) ==<br />
==Payment Flow (Raymond Forbes) ==<br />
==Dynamic API Security Model (Raymond Forbes) ==<br />
==WebRT (Raymond Forbes) ==<br />
==BrowserID ==<br />
== Identity Services (David Chan) ==<br />
==Addons.M.O (Raymond Forbes) ==<br />
==Bugzilla.M.O (Mark Goodwin & Eric Parker) ==<br />
* No updates<br />
==Mozillians (Raymond Forbes) ==<br />
==MDN (Raymond Forbes) ==<br />
==SUMO (Kitsune) () ==<br />
== AddressSanitizer (Christian Holler) ==<br />
* `make check` now green on try<br />
** \o/<br />
* Remaining mochitest-1 blocker patch reviewed, landing soon<br />
* Remaining defects (orange) filed and waiting for fixes</div>Jessehttps://wiki.mozilla.org/index.php?title=SecurityEngineering/Roadmap&diff=469573SecurityEngineering/Roadmap2012-09-11T21:06:55Z<p>Jesse: /* Ideas Not Yet Awesome Enough */</p>
<hr />
<div><small>[[Roadmaps|&lt; Product Roadmaps]] </small> <br />
<br />
<section begin="summary" />{{RoadmapSummary<br />
|icon=larry.png<br />
|pagelocation=Security/Roadmap<br />
|pagetitle=Product Security Feature Roadmap<br />
|owner=[[User:Ladamski|Lucas Adamski]]<br />
|updated=Weekly<br />
|status=Draft<br />
|description=Security at Mozilla can be thought of a set of principles that are reflected in the products we ship, but also in the impact Mozilla has on the entire web. As such our security roadmap should reflect the real security improvements we need to make to our products to reflect the evolving security landscape, but also the ambitious impact we'd like to have on all web users.}}<section end="summary" /> <br />
<br />
{{Draft}} <br />
<br />
<br> <br />
<br />
= Vision =<br />
<br />
Security at Mozilla can be thought of a set of principles that are reflected in the products we ship, but also in the impact Mozilla has on the entire web. <br />
<br />
= Themes and Goals =<br />
<br />
Web users are under constant attack from a wide variety of opponents, many of whom are merely opportunistic, but also by a minority of very clever and determined attackers.&nbsp; To protect users, we need to improve our current products to keep pace with these evolving threats, but we are ultimately limited in what we can do unilaterally within our products.&nbsp; We must also drive innovative solutions that require the participation of other vital players in the web ecosystem, including standards bodies, internet technology vendors, web developers, web admins and web frameworks. <br />
<br />
As such, security engineering at Mozilla has two primary themes:<br />
<br />
*Product Hardening: Protect our users directly from an ever-increasing volume &amp; sophistication of online attacks, by directly improving the products and services we deliver<br />
*Security Leadership: Drive innovative security solutions to enable the wider web ecosystem of web developers, web admins and users to adapt to evolving web technologies and their corresponding security threats.<br />
<br />
Here the concrete goals are segmented into themes. Some goals may potentially fit into multiple themes, but are only identified here under the most relevant one. <br />
<br />
Survey taken in early 2011 to identify and prioritize potential features for our security roadmap. The results of this survey are [https://spreadsheets.google.com/spreadsheet/pub?hl=en&hl=en&key=0AtpjIJJ66IkGdEQwOThzdHVFS0V4aUZUOWoxZXc3alE&output=html available as a Google doc] or as PDF: [[Image:Security roadmap survey.pdf]]. <br />
<br />
'''NOTE:''' these goals are tentative and more may be added or some may be dropped.<br />
<br />
= Roadmap =<br />
'''Items with Feature Pages'''<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 30%;">Feature</td><br />
<td class="header" style="width: 15%;">Team</td><br />
<td class="header" style="width: 15%;">Stage</td><br />
<td class="header" style="width: 20%;">Directly Responsible Individual</td><br />
<td class="header" style="width: 15%;">Theme</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] [[Feature stage::!Complete]] [[Feature roadmap::Security]] OR [[Feature secondary roadmap::Security]]<br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature engineering team#<br />
| ?Feature stage#<br />
| ?Feature feature manager#<br />
| ?Feature theme#<br />
| mainlabel=-<br />
| sort=Feature priority,Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
= Outcomes: =<br />
There are some major outcomes that can be realized by completion of multiple features. These features already show up on the master list above, but this categorizes them into desired outcomes.<br />
<br />
=== HTTPS can be used as default ===<br />
Right now, when users navigate to a web site without specifying the protocol or scheme, Firefox assumes "http" as the scheme. For optimal protection from eavesdropping and for encryption of cookies and other HTTP request data in transit, we should be able to attempt HTTPS and fall back to HTTP only when absolutely necessary.<br />
<br />
This outcome can be realized when Firefox can be changed to default to the HTTPS scheme instead of HTTP.<br />
<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 35%;">Feature</td><br />
<td class="header" style="width: 10%;">Stage</td><br />
<td class="header" style="width: 10%;">Release target</td><br />
<td class="header" style="width: 20%;">Product manager</td><br />
<td class="header" style="width: 20%;">Feature manager</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] <br />
[[Feature name::HSTS Preload List]] OR <br />
[[Feature name::HTTPS (SSL) Google Search]] OR<br />
[[Feature name::OCSP Stapling]] <br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature stage#<br />
| ?Feature version#<br />
| ?Feature product manager#<br />
| ?Feature feature manager#<br />
| mainlabel=-<br />
| sort=Feature priority, Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
=Ideas Not Yet Awesome Enough=<br />
Apparently these ideas are not yet great enough to merit feature pages. If you disagree, you can [[Features/Create new | create a new feature page]] for it! Just make sure to put "Security" in the primary or secondary roadmap field.<br />
<br />
{|class=wikitable<br />
|-<br />
! Item <br />
! Owner<br />
|-<br />
| First-run warning for new plugins<br> <br />
| <br><br />
|-<br />
| [https://wiki.mozilla.org/NPAPI:Pepper2 Plugin sandboxing]<br> <br />
| <br><br />
|-<br />
| Malloc should be infallible<br> <br />
| <br><br />
|-<br />
| TLS&nbsp;1.2 support<br> <br />
| <br><br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=432687 Eviltraps meta-bug] (prevents users from leaving a page)<br> <br />
| <br><br />
|-<br />
| Notify user of malware in their crash signatures<br><br />
| <br><br />
|-<br />
| Expose HSTS&nbsp;and other security browser state to plugins (NPAPI)<br> <br />
| <br><br />
|-<br />
| Ignore autocomplete="off" for password fields<br />
| <br><br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=663566 Content Security Policy revisions]<br />
| Brandon Sterne<br />
|-<br />
| Clickjacking mitigations <br />
| <br />
|-<br />
| X-Content-Type-Options <br />
| <br />
|-<br />
| toStaticHTML <br />
| <br />
|-<br />
| Block DLLs without ASLR <br />
| <br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=677797 Force ASLR or similar mitigations (EMET)]<br />
| <br />
|}<br />
<br />
<br><br />
<br />
=Completed Features=<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 30%;">Feature</td><br />
<td class="header" style="width: 15%;">Team</td><br />
<td class="header" style="width: 15%;">Stage</td><br />
<td class="header" style="width: 20%;">Product Manager</td><br />
<td class="header" style="width: 15%;">Theme</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] [[Feature stage::Complete]] [[Feature roadmap::Security]] OR [[Feature secondary roadmap::Security]] [[Feature stage::Complete]] <br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature engineering team#<br />
| ?Feature stage#<br />
| ?Feature product manager#<br />
| ?Feature theme#<br />
| mainlabel=-<br />
| sort=Feature priority,Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
<br />
=Related Info=<br />
<br />
Links to implementation plan and progress: <br />
<br />
*[[Firefox/Flight Tracking]] <br />
*[[Firefox/Features]]<br />
<br />
Inputs into the security roadmap:<br />
<br />
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=sw%3A%22sg%3Awant%22 sg:want bugs] that are both important and complex<br />
<br />
[[Category:Roadmaps]]</div>Jessehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2012-08-06&diff=458190WeeklyUpdates/2012-08-062012-08-06T18:10:40Z<p>Jesse: /* Firefox Desktop */</p>
<hr />
<div><small>[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]</small><br />
<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==<br />
<br />
* The [https://wiki.mozilla.org/ContributorEngagement Contributor Engagement team] nominates [https://mozillians.org/en-US/u/7bd45639c8 Hugo Acosta] and the [http://www.mozillabolivia.org/ team in Bolivia] for spreading Firefox and helping Firefox become the [http://gs.statcounter.com/#browser-BO-monthly-201106-201208/ #1 browser there!] Efforts have included a social media campaign that Mozilla Hispano contributed to as well.<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
* Grow Mozilla discussion at 10 AM pacific -- a forum for discussing community building at Mozilla<br />
** [[Grow/Meeting_08_09_12|Agenda and dial-in information]] (feel free to add items to the agenda)<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Product Status Updates (voice updates) ==<br />
<br />
=== Firefox Desktop ===<br />
''Speaker Location: MV (johnath)''<br />
* Social: {{bug|764869}}, {{bug|764872}}, {{bug|773351}}, {{bug|770695}}: big pieces of the work that makes Social actually semi-usable have landed. That means that you can test social features using "MoTown" in Nightly builds, by setting social.enabled = true.<br />
* navigator.id DOM and core landed last week, the beginnings of native Persona integration <br />
* Taras' [https://blog.mozilla.org/tglek/2012/07/26/snappy-july-26-go-try-the-gecko-profiler/ weekly performance/snappy update]. Highlights include:<br />
** JS profiling using the built in profiler<br />
** Reducing the cache nuking hit that telemetry tells us we hit on 10-20% of pages<br />
** Also starting to file performance bugs on popular addons<br />
* OMGCDN!<br />
** We are moving to a CDN for initial Firefox downloads. The extra speed improves download success & conversion by 10-20% in some locales!<br />
** Software updates are still using the volunteer mirror network, for now.<br />
<br />
=== Firefox Mobile ===<br />
''Speaker Location: MV (johnath)'' <br />
* Spinning a 14.0.2 to fix jellybean specific crashes<br />
* More testing on ARMv6 to find stability gotchas and minimum requirements<br />
* FF15 (with Tablet support) firming up!<br />
** ''BUT'' has anyone had a lot of hangs with Firefox Beta on Asus Transformers? Let mfinkle/blassey know.<br />
* Scott wrote an [http://jwir3.wordpress.com/2012/07/30/font-inflation-fennec-and-you/ excellent blog post about font inflation]<br />
<br />
=== Thunderbird ===<br />
''Speaker Location:'' <br />
<br />
=== Older Branch Work ===<br />
''Speaker Location:'' <br />
<br />
=== Webmaker ===<br />
''Speaker Location:''<br />
<br />
=== Identity ===<br />
''Speaker Location:''<br />
<br />
=== Services ===<br />
''Speaker Location:''<br />
<br />
=== Firefox OS ===<br />
''Speaker Location: Dietrich''<br />
<br />
* Gaia: Working camera! And photo filters in the Gallery! Animated SVG analog clock and FM Radio dial landed. There are risks in email plumbing, calendar, 1st Run, and settings, some in visual design access and some in implementation. More visual design implementation is landing every day. [https://etherpad.mozilla.org/gaia-meeting-notes Weekly meeting notes].<br />
* Platform: Security review for bluetooth is done. The media stream components of Camera back-end are in review. Cell broadcast was added to v1 requirements. Lots of software update pieces under development and discussion. Lots of E10s work ongoing. [https://etherpad.mozilla.org/b2g-meeting-notes Weekly meeting notes].<br />
* Release: Technical Release Plan sign-offs held on Gecko base, branching, updates and testing. Blockers for internal dogfooding are now tracked with [B2GTest:Blocker].<br />
* QA: Completed ~60% of the Gaia requirements deep dive and added more tests cases for additional feature coverage. Built a webapp on devices that tests battery, geolocation, vibration, fullscreen and orientation. Daily build smoke tests still show critical regressions.<br />
* Triage is now daily. Details in the [https://groups.google.com/d/msg/mozilla.dev.planning/6j-bX_DOytU/JIW1DwiChmwJ weekly meeting schedule announcement].<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Your Title Here<br />
| Your Name Here<br />
| What are you going to talk about?<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Tour Guide<br />
| David Boswell<br />
| Community data<br />
| [http://www.arewegrowingyet.com arewegrowingyet.com] and [https://blog.mozilla.org/community/2012/08/03/coding-contribution-dashboards/ coding contribution dashboards]<br />
| [https://blog.mozilla.org/community/category/data/ Data posts on about:community blog]<br />
|}<br />
<br />
== Introducing New Hires ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
| ''Brendan Colloran''<br />
| ''Gilbert FitzGerald''<br />
| ''Mountain View''<br />
| ''Senior Data Analyst''<br />
|-<br />
| ''Sriharsha Chintalapani (Harsha)''<br />
| ''Gilbert FitzGerald''<br />
| ''Mountain View''<br />
| ''Metrics Software Engineer''<br />
|-<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| Leo Yeykelis<br />
| Mary Trombley<br />
| Mountain View<br />
| User Research<br />
|-<br />
| Valentin Gosu<br />
| Nick Hurley<br />
| Mountain View<br />
| Platform<br />
|-<br />
|}<br />
<br />
== Roundtable ==<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Services ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
<br />
==== QA Community ====<br />
<br />
=== Automation & Tools ===<br />
* Tegras are not rebooting randomly anymore, 39% failure rate on android tests dropped to 13% as of Friday evening. Big thanks to Jmaher, Wlach, and Callek<br />
* [http://brasstacks.mozilla.com/autolog/?tree=b2g&source=autolog Web API and B2G mochitests running again] on new VMs supplied by releng<br />
* Datazilla is alive on production hardware! [https://datazilla.mozilla.org/test https://datazilla.mozilla.org/test]<br />
* Initial plan for a TBPL intermittent failure bug filer (try saying that three times fast... :P) {{bug|779529}}.<br />
* Expect this thursday's Bugzilla.mozilla.org push to include a fix for interdiff {{bug|779862}}<br />
* [https://wiki.mozilla.org/Auto-tools/Meetings/2012-08-05 More Notes Here]<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
==== PR ====<br />
[http://www.techweekeurope.co.uk/news/firefox-quiz-88264 Quiz Of The Week: The Fiery Fox] <br><br />
<br />
[http://www.zdnet.com/smartphone-os-makers-eye-developing-markets-7000001874/ Smartphone OS makers eye developing markets] <br><br />
<br />
[http://www.digitaltrends.com/opinion/state-of-the-web-which-vision-of-an-open-internet-would-you-fight-for/ State of the Web: Which vision of an ‘open Internet’ would you fight for?] <br><br />
<br />
[http://hexus.net/tech/news/software/43185-firefoxs-popular-add-ons-3-billion-downloads/ Firefox’s most popular add-ons from 3 billion downloads] <br><br />
<br />
[http://ostatic.com/blog/new-photos-of-mozillas-mobile-os-have-arrived-online New Photos of Mozilla's Mobile OS Have Arrived Online] <br><br />
<br />
[http://techcrunch.com/2012/07/30/mozilla-confirms-it-will-join-berlins-new-factory-campus/ Mozilla Confirms It Will Join Berlin’s New ‘Factory’ Campus] <br><br />
[http://techcrunch.com/2012/07/31/mozilla-will-nearly-double-sf-office-add-125-people-in-early-2013/ Mozilla Will Nearly Double SF Office, Add 125 People In Early 2013] <br><br />
[http://www.h-online.com/open/news/item/Mozilla-expands-in-Berlin-and-US-1659629.html Mozilla expands in Berlin and US] <br><br />
<br />
==== Events ====<br />
<br />
==== Creative Team ====<br />
<br />
==== Community Marketing ====<br />
<br />
=== Support ===<br />
<br />
=== Metrics ===<br />
<br />
=== Evangelism ===<br />
<br />
=== Labs ===<br />
<br />
=== Apps ===<br />
<br />
=== Developer Tools ===<br />
<br />
=== Add-ons ===<br />
<br />
=== Webdev ===<br />
<br />
=== L10n ===<br />
<br />
=== People Team ===<br />
<br />
=== WebFWD ===<br />
<br />
== Foundation Updates ==</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/BlackHat_2012&diff=453606Security/BlackHat 20122012-07-23T22:07:36Z<p>Jesse: /* Wed Night Dinner Sign Up */</p>
<hr />
<div>= Black Hat & DEFCON 2012 =<br />
This is to track organization and attendees for Black Hat and DEFCON 2012 security conferences this coming Summer.<br />
Black Hat is at Caesars Palace and DEFCON is at the Rio.<br />
<br />
= Dates =<br />
[http://blackhat.com/html/bh-us-12/ Black Hat] is from July 21 through 26, 2012. [http://defcon.org/html/defcon-20/dc-20-index.html DEFCON 20] is from July 26 through 29.<br />
<br />
== Sessions to be covered ==<br />
<br />
=== Black Hat sessions ===<br />
<br />
''July 25''<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Argyroudis Exploiting the jemalloc Memory Allocator: Owning Firefox's Heap] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Rohlf Google Native Client - Analysis Of A Secure Browser Plugin Sandbox] -''Who is attending, if anyone? Name here''<br />
<br />
For Gaia/WebAPI folks some attacks on Chrome extensions that may<br />
have relevance to types of attacks we face on apps.<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Osborn "Advanced Chrome Extension Exploitation - Leveraging API Powers for the Better Evil"] -''Who is attending, if anyone? Name here''<br />
<br />
For the B2G folks there are a couple that might help us with our<br />
phone designs. If nothing else they may inform our testing.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Ridley "Advanced ARM exploitation"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Weinmann "Scaling Up Baseband Attacks: More (Unexpected) Attack Surface"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Miller "Don't Stand So Close To Me: An Analysis of the NFC Attack Surface"] -''Who is attending, if anyone? Name here''<br />
<br />
Defeating ASLR through info leaks, and how to cause them.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Serna "The Info Leak Era on Software Exploitation"] (an example of one he wrote up on Flash is http://seclists.org/bugtraq/2012/Apr/63 ) -''Who is attending, if anyone? Name here''<br />
<br />
New defensive features of Win8 we should consider using. Some may be<br />
compiler/linker features that will help on other versions of<br />
windows, too.<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Miller2 "Exploit Mitigation Improvements in Win 8"]<br />
<br />
For the privacy geeks -- decloaking "private browsing" among other<br />
ways to track people.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Fleischer "Web Tracking for You"]<br />
<br />
A wildcard... Math.random() isn't crytographically secure, could we<br />
be vulnerable to anything like these PHP issues? If you go bring<br />
your open mind and wear your brainstorming hat.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Argyros "PRNG: Pwning Random Number Generators (in PHP applications)"]<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Alonso Owning bad guys and mafia with javascript botnets] - who doesn't love a botnet that uses javascript?<br />
<br />
<br />
''July 26''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Shekyan Hacking with WebSockets] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Shah HTML5 Top 10 Threats – Stealth Attacks and Silent Exploits] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Oh Recent Java Exploitation Trends and Malware] - Java malware, sandboxes, etc.<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Purviance "Blended Threats and JavaScript: A Plan for Permanent Network Compromise"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Sabanal "Digging Deep Into The Flash Sandboxes"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Philput Hacking the Corporate Mind: Using Social Engineering Tactics to Improve Organizational Security Acceptance] - Makes sense for security folks<br />
<br />
=== DEFCON Sessions ===<br />
''July 27''<br />
<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Minozhenko How to Hack VMware vCenter Server in 60 Seconds]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Baldwin https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Baldwin]<br />
<br />
''July 28''<br />
<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Doctorow Beyond the War on General Purpose Computing: What's Inside the Box?] - Cory Doctorow Keynote<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Alonso Owning Bad Guys And Mafia With Javascript Botnets] - Repeat of BH talk if you're interested and missed it.<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Sood Botnets Die Hard - Owned and Operated]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Cannon Into the Droid: Gaining Access to Android User Data]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Floren Hellaphone: Replacing the Java in Android]<br />
<br />
''July 29''<br />
<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Zulla Improving Web Vulnerability Scanning]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Egypt Post Metasploitation: Improving Accuracy and Efficiency in Post Exploitation Using the Metasploit Framework]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Toussain Subterfuge: The Automated Man-in-the-Middle Attack Framework]<br />
<br />
=== dinners/meetups ===<br />
<br />
=== Tuesday Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
<br />
1 Joe Stevensen<br />
2 Eric Parker<br />
3 Guillaume Destuynder<br />
4 Gary Kwong<br />
5 Adam Muntner<br />
6 Ben Kero<br />
7 Brian Hourigan<br />
8 Anthony Hughes<br />
9 Jorge Villalobos<br />
10 Kevin Brosnan<br />
11 John Morrison<br />
12 Al Billings<br />
13 Raymond Forbes<br />
14 Chris Hofmann<br />
<br />
=== Wed Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
1 Joe Stevensen<br />
2 Michael Herny :tinfoil<br />
3 Gary Kwong<br />
4 Ben Kero<br />
5 Brian Hourigan<br />
6 Anthony Hughes<br />
7 Jorge Villalobos<br />
8 Kevin Brosnan<br />
9 Marshall Moutenot<br />
10 John Morrison<br />
11 Al Billings<br />
12 Raymond Forbes<br />
13 Chris Hofmann<br />
14 Jesse Ruderman<br />
<br />
=== Thurs Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Marshall Moutenot<br />
<br />
=== Friday Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Marshall Moutenot<br />
* Raymond Forbes<br />
<br />
=== Sat Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Raymond Forbes<br />
<br />
== Attendees ==<br />
Enter your name below if you plan on attending one or both conferences.<br />
<br />
{| class="wikitable"<br />
! | Name<br />
! Black Hat?<br />
! DEFCON?<br />
! Arrival Date<br />
! Departure Date<br />
|-<br />
|Al Billings<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Raymond Forbes<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Joe Stevensen<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Gary Kwong<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Guillaume Destuynder<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Jorge Villalobos<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Adam Muntner<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Michael Henry :tinfoil<br />
|No (going to BSidesLV)<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Jesse Ruderman<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Anthony Hughes<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|John Morrison :jrgm<br />
|Yes<br />
|No<br />
|2012-07-24<br />
|2012-07-27<br />
|-<br />
|Kevin Brosnan :kbrosnan<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Ben Kero :bkero<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Brian Hourigan :digi<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Marshall Moutenot :mmoutenot<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|}<br />
<br />
== Conference registration numbers for attendees ==<br />
<br />
<br />
== hotel reservation confirmations ==<br />
<br />
<br />
<h2> Flight planning </h2><br />
<table class="fullwidth-table"><br />
<tr><br />
<th> Name<br />
</th><br />
<th> Outbound Flight<br />
</th><br />
<th> Return Flight<br />
</th><br />
<th> Notes<br />
</th></tr><br />
<tr><br />
<td>Joe Stevensen<br />
</td><br />
<td>VX906 Arrives 7/24 14:55<br />
</td><br />
<td>VX905 Departs 7/29 11:00<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Guillaume Destuynder<br />
</td><br />
<td>VX906 Arrives 7/24 14:55<br />
</td><br />
<td>VX905 Departs 7/29 11:00<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Kevin Brosnan<br />
</td><br />
<td>VX906 Arrives 7/24 14:55<br />
</td><br />
<td>VX901 Departs 7/29 09:20<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Al Billings<br />
</td><br />
<td>VX260 Arrives 7/24 13:35<br />
</td><br />
<td>VX915 Departs 7/29 17:30<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Jorge Villalobos<br />
</td><br />
<td>UA1608 Arrives 7/24 22:01<br />
</td><br />
<td>UA1254 Departs 07/29 01:16<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Ben Kero<br />
</td><br />
<td>AS620 Arrives 7/24 20:06<br />
</td><br />
<td>AS621 Departs 7/29 20:50<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Anthony Hughes<br />
</td><br />
<td>WJ1788 Arrives 7/24 12:53<br />
</td><br />
<td>WJ1789 Departs 7/30 13:45<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Marshall Moutenot<br />
</td><br />
<td>SW1797 Arrives 7/24 21:25<br />
</td><br />
<td>SW2352 Departs 7/29 16:05<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td><br />
</td><br />
<td><br />
</td><br />
<td><br />
</td></tr></table></div>Jessehttps://wiki.mozilla.org/index.php?title=Security/BlackHat_2012&diff=453537Security/BlackHat 20122012-07-23T19:12:29Z<p>Jesse: </p>
<hr />
<div>= Black Hat & DEFCON 2012 =<br />
This is to track organization and attendees for Black Hat and DEFCON 2012 security conferences this coming Summer.<br />
Black Hat is at Caesars Palace and DEFCON is at the Rio.<br />
<br />
= Dates =<br />
[http://blackhat.com/html/bh-us-12/ Black Hat] is from July 21 through 26, 2012. [http://defcon.org/html/defcon-20/dc-20-index.html DEFCON 20] is from July 26 through 29.<br />
<br />
== Sessions to be covered ==<br />
<br />
=== Black Hat sessions ===<br />
<br />
''July 25''<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Argyroudis Exploiting the jemalloc Memory Allocator: Owning Firefox's Heap] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Rohlf Google Native Client - Analysis Of A Secure Browser Plugin Sandbox] -''Who is attending, if anyone? Name here''<br />
<br />
For Gaia/WebAPI folks some attacks on Chrome extensions that may<br />
have relevance to types of attacks we face on apps.<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Osborn "Advanced Chrome Extension Exploitation - Leveraging API Powers for the Better Evil"] -''Who is attending, if anyone? Name here''<br />
<br />
For the B2G folks there are a couple that might help us with our<br />
phone designs. If nothing else they may inform our testing.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Ridley "Advanced ARM exploitation"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Weinmann "Scaling Up Baseband Attacks: More (Unexpected) Attack Surface"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Miller "Don't Stand So Close To Me: An Analysis of the NFC Attack Surface"] -''Who is attending, if anyone? Name here''<br />
<br />
Defeating ASLR through info leaks, and how to cause them.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Serna "The Info Leak Era on Software Exploitation"] (an example of one he wrote up on Flash is http://seclists.org/bugtraq/2012/Apr/63 ) -''Who is attending, if anyone? Name here''<br />
<br />
New defensive features of Win8 we should consider using. Some may be<br />
compiler/linker features that will help on other versions of<br />
windows, too.<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Miller2 "Exploit Mitigation Improvements in Win 8"]<br />
<br />
For the privacy geeks -- decloaking "private browsing" among other<br />
ways to track people.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Fleischer "Web Tracking for You"]<br />
<br />
A wildcard... Math.random() isn't crytographically secure, could we<br />
be vulnerable to anything like these PHP issues? If you go bring<br />
your open mind and wear your brainstorming hat.<br />
<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Argyros "PRNG: Pwning Random Number Generators (in PHP applications)"]<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Alonso Owning bad guys and mafia with javascript botnets] - who doesn't love a botnet that uses javascript?<br />
<br />
<br />
''July 26''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Shekyan Hacking with WebSockets] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Shah HTML5 Top 10 Threats – Stealth Attacks and Silent Exploits] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Oh Recent Java Exploitation Trends and Malware] - Java malware, sandboxes, etc.<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Purviance "Blended Threats and JavaScript: A Plan for Permanent Network Compromise"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Sabanal "Digging Deep Into The Flash Sandboxes"] -''Who is attending, if anyone? Name here''<br />
* [https://www.blackhat.com/html/bh-us-12/bh-us-12-briefings.html#Philput Hacking the Corporate Mind: Using Social Engineering Tactics to Improve Organizational Security Acceptance] - Makes sense for security folks<br />
<br />
=== DEFCON Sessions ===<br />
''July 27''<br />
<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Minozhenko How to Hack VMware vCenter Server in 60 Seconds]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Baldwin https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Baldwin]<br />
<br />
''July 28''<br />
<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Doctorow Beyond the War on General Purpose Computing: What's Inside the Box?] - Cory Doctorow Keynote<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Alonso Owning Bad Guys And Mafia With Javascript Botnets] - Repeat of BH talk if you're interested and missed it.<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Sood Botnets Die Hard - Owned and Operated]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Cannon Into the Droid: Gaining Access to Android User Data]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Floren Hellaphone: Replacing the Java in Android]<br />
<br />
''July 29''<br />
<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Zulla Improving Web Vulnerability Scanning]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Egypt Post Metasploitation: Improving Accuracy and Efficiency in Post Exploitation Using the Metasploit Framework]<br />
* [https://www.defcon.org/html/defcon-20/dc-20-speakers.html#Toussain Subterfuge: The Automated Man-in-the-Middle Attack Framework]<br />
<br />
=== dinners/meetups ===<br />
<br />
=== Tuesday Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Eric Parker<br />
* Guillaume Destuynder<br />
* Gary Kwong<br />
* Adam Muntner<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Kevin Brosnan<br />
* John Morrison<br />
* Al Billings<br />
* Raymond Forbes<br />
<br />
=== Wed Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Michael Herny :tinfoil<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Kevin Brosnan<br />
* Marshall Moutenot<br />
* John Morrison<br />
* Al Billings<br />
* Raymond Forbes<br />
<br />
=== Thurs Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Marshall Moutenot<br />
<br />
=== Friday Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Marshall Moutenot<br />
* Raymond Forbes<br />
<br />
=== Sat Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
* Joe Stevensen<br />
* Gary Kwong<br />
* Ben Kero<br />
* Brian Hourigan<br />
* Anthony Hughes<br />
* Jorge Villalobos<br />
* Raymond Forbes<br />
<br />
== Attendees ==<br />
Enter your name below if you plan on attending one or both conferences.<br />
<br />
{| class="wikitable"<br />
! | Name<br />
! Black Hat?<br />
! DEFCON?<br />
! Arrival Date<br />
! Departure Date<br />
|-<br />
|Al Billings<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Raymond Forbes<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Joe Stevensen<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Gary Kwong<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Guillaume Destuynder<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Jorge Villalobos<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Adam Muntner<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Michael Henry :tinfoil<br />
|No (going to BSidesLV)<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Jesse Ruderman<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Anthony Hughes<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|John Morrison :jrgm<br />
|Yes<br />
|No<br />
|2012-07-24<br />
|2012-07-27<br />
|-<br />
|Kevin Brosnan :kbrosnan<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Ben Kero :bkero<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Brian Hourigan :digi<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Marshall Moutenot :mmoutenot<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|}<br />
<br />
== Conference registration numbers for attendees ==<br />
<br />
<br />
== hotel reservation confirmations ==<br />
<br />
<br />
<h2> Flight planning </h2><br />
<table class="fullwidth-table"><br />
<tr><br />
<th> Name<br />
</th><br />
<th> Outbound Flight<br />
</th><br />
<th> Return Flight<br />
</th><br />
<th> Notes<br />
</th></tr><br />
<tr><br />
<td>Joe Stevensen<br />
</td><br />
<td>VX906 Arrives 7/24 14:55<br />
</td><br />
<td>VX905 Departs 7/29 11:00<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Guillaume Destuynder<br />
</td><br />
<td>VX906 Arrives 7/24 14:55<br />
</td><br />
<td>VX905 Departs 7/29 11:00<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Kevin Brosnan<br />
</td><br />
<td>VX906 Arrives 7/24 14:55<br />
</td><br />
<td>VX901 Departs 7/29 09:20<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Al Billings<br />
</td><br />
<td>VX260 Arrives 7/24 13:35<br />
</td><br />
<td>VX915 Departs 7/29 17:30<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Jorge Villalobos<br />
</td><br />
<td>UA1608 Arrives 7/24 22:01<br />
</td><br />
<td>UA1254 Departs 07/29 01:16<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Ben Kero<br />
</td><br />
<td>AS620 Arrives 7/24 20:06<br />
</td><br />
<td>AS621 Departs 7/29 20:50<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Anthony Hughes<br />
</td><br />
<td>WJ1788 Arrives 7/24 12:53<br />
</td><br />
<td>WJ1789 Departs 7/30 13:45<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td>Marshall Moutenot<br />
</td><br />
<td>SW1797 Arrives 7/24 21:25<br />
</td><br />
<td>SW2352 Departs 7/29 16:05<br />
</td><br />
<td><br />
</td></tr><br />
<tr><br />
<td><br />
</td><br />
<td><br />
</td><br />
<td><br />
</td></tr></table></div>Jessehttps://wiki.mozilla.org/index.php?title=Grow/MoBB&diff=441378Grow/MoBB2012-06-14T16:59:40Z<p>Jesse: </p>
<hr />
<div>Page for the Mozilla Brain Builders program<br />
<br />
* [https://intranet.mozilla.org/MoBB Additional resources for Mozilla employees]</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/BlackHat_2012&diff=438834Security/BlackHat 20122012-06-06T23:48:17Z<p>Jesse: /* Attendees */</p>
<hr />
<div>= Black Hat & DEFCON 2012 =<br />
This is to track organization and attendees for Black Hat and DEFCON 2012 security conferences this coming Summer.<br />
Black Hat is at Caesars Palace and DEFCON is at the Rio.<br />
<br />
= Dates =<br />
[http://blackhat.com/html/bh-us-12/ Black Hat] is from July 21 through 26, 2012. [http://defcon.org/html/defcon-20/dc-20-index.html DEFCON 20] is from July 26 through 29.<br />
<br />
== Sessions to be covered ==<br />
<br />
<br />
=== Interesting-sounding Blackhat and DEFCON sessions ===<br />
<br />
<br />
=== dinners/meetups ==<br />
<br />
=== Tuesday Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
<br />
=== Wed Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
<br />
<strike>=== Wed Night Milk and Cookies ===<br />
<br />
Join us for our annual Milk + Cookies party. We all need to take a turn at playing host/hostess. We have a suite reservation. Note: Room service is providing food and non-alcoholic beverages. Chofmann will pick up key and liquor. </strike><br />
<br />
We do not know if there is an event this year as previous years.<br />
<br />
=== Thurs Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
<br />
=== Friday Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
<br />
=== Sat Night Dinner Sign Up ===<br />
<br />
8:30 PM ??<br />
<br />
== Attendees ==<br />
Enter your name below if you plan on attending one or both conferences.<br />
<br />
{| class="wikitable"<br />
! | Name<br />
! Black Hat?<br />
! DEFCON?<br />
! Arrival Date<br />
! Departure Date<br />
|-<br />
|Al Billings<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Raymond Forbes<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Joe Stevensen<br />
|Yes<br />
|Yes<br />
|2012-07-24<br />
|2012-07-29<br />
|-<br />
|Gary Kwong<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Guillaume Destuynder<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Jorge Villalobos<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Adam Muntner<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|Michael Henry :tinfoil<br />
|No<br />
|Yes<br />
|2012-07-24<br />
|2012-07-30<br />
|-<br />
|Jesse Ruderman<br />
|Yes<br />
|Yes<br />
|?<br />
|?<br />
|-<br />
|}<br />
<br />
== Conference registration numbers for attendees ==<br />
<br />
<br />
== hotel reservation confirmations ==<br />
<br />
<br />
== Flight planning ==<br />
{| class="fullwidth-table"<br />
! Name<br />
! Outbound Flight<br />
! Return Flight<br />
! Notes<br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
| <br />
|- <br />
| <br />
| <br />
| <br />
|}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security&diff=433478Security2012-05-22T20:41:18Z<p>Jesse: /* Twitter Accounts of Security Mozillians */</p>
<hr />
<div>Welcome to the Mozilla Security wiki. <br />
<br />
=== Security-related bugs ===<br />
* [[Security Severity Ratings]] <br />
* [http://www.mozilla.org/security/#For_Developers How to report a security issue] <br />
* [[Security/FixMe|Want to fix a security bug? Here is a list of old thorny bugs you can take on.]]<br />
<br />
===Engaging with Security===<br />
====How To Find Us====<br />
Lot's of options, we're here to help:<br />
* [mailto:Security@mozilla.org Security@mozilla.org] - email us any questions, concerns, etc<br />
* Bugzilla Keyword - '''sec-review-needed''' - We triage based on this keyword and will jump in to provide assistance<br />
* '''#security''' on [https://wiki.mozilla.org/IRC IRC]<br />
* File a security/privacy review request via this [https://wiki.mozilla.org/Security/Reviews/Review_Request_Form link]<br />
<br />
====Security reviews for new features/products/applications====<br />
''Main Article: [[Security/Reviews]]''<br />
* Find past reviews by [https://wiki.mozilla.org/Category:SecReview Category:SecReview]<br />
====The Mozilla Secure Development Lifecycle ====<br />
* Understand the [[Security/Reviews/Secure Development Lifecycle | Secure Development Lifecycle]] used to secure our new features/products/applications <br />
* Information on Bugzilla and the [[Security/Reviews/Bugzilla Components| Security Assurance Component]]<br />
====Request a Security or Privacy Review ====<br />
* Complete the questions at the following page to provide the basic info to kickstart a security or privacy review<br />
* We'll create and link the corresponding wiki page within the [[Security/Radar|Security Radar]]<br />
* [[Security/Reviews/Review Request Form | Security & Privacy Review Request Form]]<br />
====[[Security/Radar|Security Radar]]====<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Unlinked Reviews<br />
|-<br />
|<br />
* [[Security/Reviews/Mobile/AndroidSystemStorage| Android System Storage]]<br />
* [[Security/Firefox/WebAPI/WebBattery| WebBattery]]<br />
* [[Security/Reviews/BrowserIDCAPI| BrowserID C API]]<br />
* [[Security/Reviews/crossoriginAttribute|Add crossorigin attribute]]<br />
* [[Security/Reviews/Firefox10/SyncDialogue|Sync Dialogue]]<br />
* [[Security/Reviews/JetPack2011-20/12 | JetPack 2011-10-12]]<br />
* [[Security/Reviews/XHRnonpost| XHR non-post rewrite]]<br />
* [[Security/Reviews/StubInstaller|Stub Installer]]<br />
* [[Labs/Weave/Sync Client Security Review|Sync Client]]<br />
* [[Firefox Sync/Weave 1.3b5 Client Security Review|Weave 1.3b5 Client]]<br />
* [[Security/Reviews/DNSSEC-TLS|DNSSEC-TLS]]<br />
* [[Security/Reviews/OWA-F1|Web Activities & F1]]<br />
* [[Security/Reviews/ReviewNotes/MouseLock|MouseLock]]<br />
* [[Security/Reviews/ReviewNotes/Joystick|Joystick]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Unlinked Discussions<br />
|-<br />
|<br />
* [[Security/Discussions/WebRTC|WebRTC]]<br />
|}<br />
<br />
===Security Feature Development===<br />
<br />
''Main article: [[Security/Roadmap]]''<br />
<br />
''Main article: [[Privacy/Roadmap]]''<br />
<br />
=== Security Initiatives ===<br />
<br />
*[[Security/TeamEmbedding]]<br />
*Prioritizing and driving non-feature work: [[Security/Driving]]<br />
<br />
=== Security Resources and Blogs ===<br />
<br />
==== Mozilla Official Sites ====<br />
* [http://www.mozilla.org/security Mozilla Security Center]<br />
* [http://developer.mozilla.org/en/Security Mozilla security developer docs]<br />
* [[CA|Mozilla CA Root Program]]<br />
* [http://blog.mozilla.com/security Mozilla Security blog]<br />
* [http://blog.mozilla.com/webappsec Mozilla WebApp Sec Blog]<br />
* [https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines Secure Coding Guidelines for Webapps]<br />
<br />
==== Personal Security Related Blogs of Mozillians ====<br />
* [http://blog.mozilla.com/ladamski Lucas Adamski's blog]<br />
* [http://blog.sidstamm.com Sid Stamm's blog]<br />
* [https://spartiates.wordpress.com/ Curtis Koenig's blog]<br />
* [http://www.squarefree.com/ Jesse Ruderman's blog] ([http://www.squarefree.com/categories/fuzzing/ fuzzing entries], [http://www.squarefree.com/categories/security/ security entries])<br />
* [http://michael-coates.blogspot.com/ Michael Coates]<br />
* [http://blog.mozilla.com/imelven Ian Melven's Mozilla/Security blog]<br />
* [http://blog.mozilla.com/decoder Christian Holler's blog (decoder)]<br />
<br />
==== Twitter Accounts of Security Mozillians ====<br />
* [https://twitter.com/mozsec Mozilla Security]<br />
* [https://twitter.com/mozwebsec Mozilla Web Security]<br />
* [https://twitter.com/jruderman Jesse Ruderman]<br />
* [https://twitter.com/curtisko Curtis Koenig] (all kinds of random stuff)<br />
* [https://twitter.com/_mwc Michael Coates]<br />
* [https://twitter.com/flamsmark Tom Lowenthal] (privacy)<br />
* [https://twitter.com/securitae Lucas Adamski]<br />
* [https://twitter.com/alexanderfowler Alex Fowler]<br />
* [https://twitter.com/ygjb Yvan Boily]<br />
* [https://twitter.com/dveditz Daniel Veditz]<br />
* [https://twitter.com/gh_rooster Raymond Forbes]<br />
* [https://twitter.com/openbuddha Al Billings] (but mostly Buddhist and Hackerspace tweets)<br />
* [https://twitter.com/imelven Ian Melven]<br />
* [https://twitter.com/kangsterizer Guillaume Destuynder]<br />
* [https://twitter.com/nth10sd Gary Kwong] (all sorts of stuff)<br />
* [https://twitter.com/mozdeco Christian Holler (decoder)]<br />
* [https://twitter.com/neoCrimeLabs Michael Henry (tinfoil)]<br />
* [https://twitter.com/tanvihacks Tanvi Vyas]<br />
<br />
==== Non-Mozilla Resources (blogs, news sites, twitter, tools) ====<br />
* [[Security/OtherSecurityResources| Other Security Resources]]<br />
<br />
<h3>Stuff that needs to be merged into this page properly</h3><br />
<br />
=== Meeting Notes ===<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Meetings<br />
|-<br />
|<br />
* [[Security/Meetings/SecurityAssurance|Security Assurance]]<br />
* [[Security/AppSecBiweekly|AppSec Bi Weelky]]<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! SecTeam Meetings 2012 <br />
|-<br />
|<br />
* [[Security/Meetings/2012-02-01|2012-02-01]]<br />
* [[Security/Meetings/2012-01-25|2012-01-25]]<br />
* [[Security/Meetings/2012-01-18|2012-01-18]]<br />
* [[Security/Meetings/2012-01-11|2012-01-11]]<br />
* [[Security/Meetings/2012-01-04|2012-01-04]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! SecTeam Meetings 2011 <br />
|-<br />
|<br />
* [[Security/Meetings/2011-12-28|2011-12-28]]<br />
* [[Security/Meetings/2011-12-21|2011-12-21]]<br />
* [[Security/Meetings/2011-12-07|2011-12-14]]<br />
* [[Security/Meetings/2011-12-07|2011-12-07]]<br />
* [[Security/Meetings/2011-11-30|2011-11-30]]<br />
* [[Security/Meetings/2011-11-23|2011-11-23]]<br />
* [[Security/Meetings/2011-11-16|2011-11-16]]<br />
* [[Security/Meetings/2011-11-09|2011-11-09]]<br />
* [[Security/Meetings/2011-11-02|2011-11-02]]<br />
* [[Security/Meetings/2011-10-26|2011-10-26]]<br />
* [[Security/Meetings/2011-10-19|2011-10-19]]<br />
* [[Security/Meetings/2011-10-12|2011-10-12]]<br />
* [[Security/Meetings/2011-10-05|2011-10-05]]<br />
* [[Security/Meetings/2011-09-28|2011-09-28]]<br />
* No meeting on 9/14 (All Hands) or 9/21 (Fuzzing Work Week)<br />
* [[Security/Meetings/2011-09-07|2011-09-07]]<br />
* [[Security/Meetings/2011-08-31|2011-08-31]]<br />
* [[Security/Meetings/2011-08-24|2011-08-24]]<br />
* [[Security/Meetings/lifecycledisc|Life Cycle discussion]]<br />
* [[Security/Meetings/2011-08-17|2011-08-17]]<br />
* [[Security/Meetings/2011-08-10|2011-08-10]]<br />
* [[Security/Meetings/2011-07-27|2011-07-27]]<br />
* [[Security/Meetings/2011-07-20|2011-07-20]]<br />
* [[Security/Meetings/2011-07-13|2011-07-13]]<br />
* [[Security/Meetings/2011-07-06|2011-07-06]]<br />
* [[Security/Meetings/2011-06-29|2011-06-29]]<br />
* [[Security/Meetings/2011-06-22|2011-06-22]]<br />
* [[Security/Meetings/2011-06-15|2011-06-15]]<br />
* [[Security/Meetings/2011-06-08|2011-06-08]]<br />
* [[Security/Meetings/2011-06-01|2011-06-01]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Joint Secteam-Infrasec Meetings 2012 <br />
|-<br />
|<br />
* [[Security/Meetings/2012-01-12|2012-01-12]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Joint Secteam-Infrasec Meetings 2011<br />
|-<br />
|<br />
<br />
* [[Security/Meetings/2011-12-15|2011-12-15]]<br />
* [[Security/Meetings/2011-11-17|2011-11-17]]<br />
* [[Security/Meetings/2011-10-06|2011-10-06]]<br />
* [[Security/Meetings/2011-09-08|2011-09-08]]<br />
* [[Security/Meetings/2011-08-25|2011-08-25]]<br />
* [[Security/Meetings/2011-08-11|2011-08-11]]<br />
* [[Security/Meetings/2011-07-28|2011-07-28]]<br />
* [[Security/Meetings/2011-06-16|2011-06-16]]<br />
|}<br />
|}</div>Jessehttps://wiki.mozilla.org/index.php?title=Privacy/Features/Improve_site_identity_button&diff=425725Privacy/Features/Improve site identity button2012-04-30T19:41:35Z<p>Jesse: </p>
<hr />
<div>{{FeatureStatus<br />
|Feature name=Improve Site identity button to show more about how you've interacted with a site in the past<br />
|Feature stage=Draft<br />
|Feature health=OK<br />
}}<br />
{{FeatureTeam<br />
|Feature product manager=Sid Stamm<br />
}}<br />
{{FeaturePageBody<br />
|Feature overview=Improve Site identity button to show <br />
* How you've interacted with a site in the past (relationship gauge).<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=711816 Indicators of how well the site is using TLS], maybe<br />
}}<br />
{{FeatureInfo<br />
|Feature priority=P2<br />
|Feature theme=Contextual Identity<br />
|Feature roadmap=Privacy<br />
|Feature list=Desktop<br />
}}<br />
{{FeatureTeamStatus}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Privacy/Roadmap/Tracking&diff=425723Privacy/Roadmap/Tracking2012-04-30T19:40:23Z<p>Jesse: /* Step 3: Establishing Trust */</p>
<hr />
<div>= Do-Not-Track Evolving =<br />
This document is a high-level plan for Mozilla's Do-Not-Track and related features (including non-feature efforts) that help users control how they are tracked across the web.<br />
<br />
== Vision ==<br />
<br />
The underlying goals of this effort are to instill users with control over their data, provide greater transparency in data sharing practices, and in general bring consumers in touch with how their data is shared, brokered and used throughout the web. We will accomplish this through a variety of directions including incentives for disclosure of behavior, technology to remove ambiguities with respect to intent of consumers and sites, as well as technological levers to facilitate fair and honest use of consumers' private data.<br />
<br />
In working towards a better web, we are focused on the following consumer-focused outcomes from this work. A user should be able to assert the following claims:<br />
# I know what tracking is<br />
# I know who is tracking me<br />
# I can tell them to stop tracking me<br />
# I can discern if they listened to my request to stop<br />
# I can stop sites from tracking me if they don't listen<br />
<br />
All of the features or efforts on this roadmap should aim for at least one of these outcomes.<br />
<br />
= Execution Plan =<br />
<br />
==Step 1: Do-Not-Track HTTP Header==<br />
<br />
Consumers need a way to tell web sites what they think of tracking. In its<br />
first incarnation, this voice is a DNT header broadcast as consumers' choice to<br />
"tell sites I do not want to be tracked." This feature may evolve into something slightly more complex, but the<br />
technology begins as a broadcast of what the user wants.<br />
<br />
{|class=wikitable<br />
! Priority<br />
! Item<br />
! Status<br />
! ETA<br />
! Owner<br />
! Outcomes<br />
|-<br />
| P1 || Implement DNT header <br />
| {{StatusHealthy|status={{bug|628197|Done}}}} || Firefox 4 || Sid Stamm<br />
| 1,3<br />
|-<br />
| P1 || Implement DNT header for Mobile <br />
| {{StatusHealthy|status={{bug|648654|Done}}}} || Firefox 5 || Sid Stamm<br />
| 3<br />
|-<br />
| P2 || Make DNT signal accessible from the navigator global object<br />
| {{StatusBlocked|status={{bug|629535|Shipped - pending change}}}} || ? || Sid Stamm<br />
| 3<br />
|-<br />
| P2 || Make DNT documentation and pref accessible from first-run page <br />
| Not Started || ? || Sid Stamm<br />
| 1,3<br />
|}<br />
<br />
==Step 2: Visualizing Tracking==<br />
<br />
The next class of work that needs to be done to aid transparency and control in<br />
tracking is to show consumers exactly what's going on with their browsing<br />
history. We must make accessible to Firefox users the tracking beacon and<br />
first-third party relationships that show up as they browse the web.<br />
<br />
{|class=wikitable<br />
! Priority<br />
! Item<br />
! Status<br />
! ETA<br />
! Owner<br />
! Outcomes<br />
|-<br />
| P1 || [[Privacy/Features/Tracking_Map|Tracking Map]] <br />
| {{StatusHealthy|status=investigating places DB, creating script to mine it}}<br />
| Q3 2011 || Sid Stamm<br />
| 2<br />
|-<br />
| P2 || [[Privacy/Features/Privacy reports|Based on hit-relationship graph, create visual representation so users<br />
can identify which sites are tracking them (and from where)]]<br />
| Not Started (depends on graph creation) || ? || Sid Stamm<br />
| 1, 2<br />
|}<br />
<br />
==Step 3: Establishing Trust==<br />
<br />
Once tracking can be identified, it's important for users to be able to discern<br />
"acceptable" tracking from "unacceptable" tracking and adjust how they interact<br />
with sites they trust.<br />
<br />
{|class=wikitable<br />
! Priority<br />
! Item<br />
! Status<br />
! ETA<br />
! Owner<br />
! Outcomes<br />
|-<br />
| P2 || [[Privacy/Features/Improve_site_identity_button|Improve Site identity button to show more about how you've interacted with a site in the past (relationship gauge)]]<br />
| Not Started || ? || ?<br />
| 3<br />
|-<br />
| P2 || Opt-back-in-from-DNT capability (so sites can ask you to turn off DNT for their site<br />
| Not Started || ? || Sid Stamm<br />
| 2,4<br />
|-<br />
| P2 <br />
| [[Privacy/Features/Third-party cookie API|API for allowing sites to request use of third-party cookies]]<br />
| Not Started || ? || ?<br />
| 2<br />
|-<br />
| P3<br />
| [[Privacy/Features/Unified privacy API|API for allowing sites to request various other capabilities like geolocation, a:ping, localstorage, etc]]<br />
| Not Started || ? || ?<br />
| 2<br />
|}<br />
<br />
==Step 4: Reducing Tracking from Untrusted Parties==<br />
<br />
Not all sites will honor simple requests, so it is necessary to build in<br />
features to enhance user control of tracking.<br />
<br />
{|class=wikitable<br />
! Priority<br />
! Item<br />
! Status<br />
! ETA<br />
! Owner<br />
! Outcomes<br />
|-<br />
| P2 || [[Privacy/Features/Tracking alert|Alert mechanism or auto-disabling of third party cookies when excessive tracking is encountered.]]<br />
| Not Started || ? || Sid Stamm<br />
| 2, 4, 5<br />
|}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security&diff=424010Security2012-04-25T01:38:12Z<p>Jesse: Add tanvi's twitter</p>
<hr />
<div>Welcome to the Mozilla Security wiki. <br />
<br />
=== Security-related bugs ===<br />
* [[Security Severity Ratings]] <br />
* [http://www.mozilla.org/security/#For_Developers How to report a security issue] <br />
* [[Security/FixMe|Want to fix a security bug? Here is a list of old thorny bugs you can take on.]]<br />
<br />
===Engaging with Security===<br />
====How To Find Us====<br />
Lot's of options, we're here to help:<br />
* [mailto:Security@mozilla.org Security@mozilla.org] - email us any questions, concerns, etc<br />
* Bugzilla Keyword - '''sec-review-needed''' - We triage based on this keyword and will jump in to provide assistance<br />
* '''#security''' on [https://wiki.mozilla.org/IRC IRC]<br />
* File a security/privacy review request via this [https://wiki.mozilla.org/Security/Reviews/Review_Request_Form link]<br />
<br />
====Security reviews for new features/products/applications====<br />
''Main Article: [[Security/Reviews]]''<br />
* Find past reviews by [https://wiki.mozilla.org/Category:SecReview Category:SecReview]<br />
====The Mozilla Secure Development Lifecycle ====<br />
* Understand the [[Security/Reviews/Secure Development Lifecycle | Secure Development Lifecycle]] used to secure our new features/products/applications <br />
* Information on Bugzilla and the [[Security/Reviews/Bugzilla Components| Security Assurance Component]]<br />
====Request a Security or Privacy Review ====<br />
* Complete the questions at the following page to provide the basic info to kickstart a security or privacy review<br />
* We'll create and link the corresponding wiki page within the [[Security/Radar|Security Radar]]<br />
* [[Security/Reviews/Review Request Form | Security & Privacy Review Request Form]]<br />
====[[Security/Radar|Security Radar]]====<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Unlinked Reviews<br />
|-<br />
|<br />
* [[Security/Reviews/Mobile/AndroidSystemStorage| Android System Storage]]<br />
* [[Security/Firefox/WebAPI/WebBattery| WebBattery]]<br />
* [[Security/Reviews/BrowserIDCAPI| BrowserID C API]]<br />
* [[Security/Reviews/crossoriginAttribute|Add crossorigin attribute]]<br />
* [[Security/Reviews/Firefox10/SyncDialogue|Sync Dialogue]]<br />
* [[Security/Reviews/JetPack2011-20/12 | JetPack 2011-10-12]]<br />
* [[Security/Reviews/XHRnonpost| XHR non-post rewrite]]<br />
* [[Security/Reviews/StubInstaller|Stub Installer]]<br />
* [[Labs/Weave/Sync Client Security Review|Sync Client]]<br />
* [[Firefox Sync/Weave 1.3b5 Client Security Review|Weave 1.3b5 Client]]<br />
* [[Security/Reviews/DNSSEC-TLS|DNSSEC-TLS]]<br />
* [[Security/Reviews/OWA-F1|Web Activities & F1]]<br />
* [[Security/Reviews/ReviewNotes/MouseLock|MouseLock]]<br />
* [[Security/Reviews/ReviewNotes/Joystick|Joystick]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Unlinked Discussions<br />
|-<br />
|<br />
* [[Security/Discussions/WebRTC|WebRTC]]<br />
|}<br />
<br />
===Security Feature Development===<br />
<br />
''Main article: [[Security/Roadmap]]''<br />
<br />
''Main article: [[Privacy/Roadmap]]''<br />
<br />
=== Security Initiatives ===<br />
<br />
*[[Security/TeamEmbedding]]<br />
*Prioritizing and driving non-feature work: [[Security/Driving]]<br />
<br />
=== Security Resources and Blogs ===<br />
<br />
==== Mozilla Official Sites ====<br />
* [http://www.mozilla.org/security Mozilla Security Center]<br />
* [http://developer.mozilla.org/en/Security Mozilla security developer docs]<br />
* [[CA|Mozilla CA Root Program]]<br />
* [http://blog.mozilla.com/security Mozilla Security blog]<br />
* [http://blog.mozilla.com/webappsec Mozilla WebApp Sec Blog]<br />
* [https://wiki.mozilla.org/WebAppSec/Secure_Coding_Guidelines Secure Coding Guidelines for Webapps]<br />
<br />
==== Personal Security Related Blogs of Mozillians ====<br />
* [http://blog.mozilla.com/ladamski Lucas Adamski's blog]<br />
* [http://blog.sidstamm.com Sid Stamm's blog]<br />
* [https://spartiates.wordpress.com/ Curtis Koenig's blog]<br />
* [http://www.squarefree.com/ Jesse Ruderman's blog] ([http://www.squarefree.com/categories/fuzzing/ fuzzing entries], [http://www.squarefree.com/categories/security/ security entries])<br />
* [http://michael-coates.blogspot.com/ Michael Coates]<br />
* [http://blog.mozilla.com/imelven Ian Melven's Mozilla/Security blog]<br />
* [http://blog.mozilla.com/decoder Christian Holler's blog (decoder)]<br />
<br />
==== Twitter Accounts of Security Mozillians ====<br />
* [https://twitter.com/mozsec Mozilla Security]<br />
* [https://twitter.com/mozwebsec Mozilla Security]<br />
* [https://twitter.com/jruderman Jesse Ruderman]<br />
* [https://twitter.com/curtisko Curtis Koenig] (all kinds of random stuff)<br />
* [https://twitter.com/_mwc Michael Coates]<br />
* [https://twitter.com/flamsmark Tom Lowenthal] (privacy)<br />
* [https://twitter.com/securitae Lucas Adamski]<br />
* [https://twitter.com/alexanderfowler Alex Fowler]<br />
* [https://twitter.com/ygjb Yvan Boily]<br />
* [https://twitter.com/dveditz Daniel Veditz]<br />
* [https://twitter.com/gh_rooster Raymond Forbes]<br />
* [https://twitter.com/openbuddha Al Billings] (but mostly Buddhist and Hackerspace tweets)<br />
* [https://twitter.com/imelven Ian Melven]<br />
* [https://twitter.com/kangsterizer Guillaume Destuynder]<br />
* [https://twitter.com/nth10sd Gary Kwong] (all sorts of stuff)<br />
* [https://twitter.com/mozdeco Christian Holler (decoder)]<br />
* [https://twitter.com/neoCrimeLabs Michael Henry (tinfoil)]<br />
* [https://twitter.com/tanvihacks Tanvi Vyas]<br />
<br />
==== Non-Mozilla Resources (blogs, news sites, twitter, tools) ====<br />
* [[Security/OtherSecurityResources| Other Security Resources]]<br />
<br />
<h3>Stuff that needs to be merged into this page properly</h3><br />
<br />
=== Meeting Notes ===<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Meetings<br />
|-<br />
|<br />
* [[Security/Meetings/SecurityAssurance|Security Assurance]]<br />
* [[Security/AppSecBiweekly|AppSec Bi Weelky]]<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! SecTeam Meetings 2012 <br />
|-<br />
|<br />
* [[Security/Meetings/2012-02-01|2012-02-01]]<br />
* [[Security/Meetings/2012-01-25|2012-01-25]]<br />
* [[Security/Meetings/2012-01-18|2012-01-18]]<br />
* [[Security/Meetings/2012-01-11|2012-01-11]]<br />
* [[Security/Meetings/2012-01-04|2012-01-04]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! SecTeam Meetings 2011 <br />
|-<br />
|<br />
* [[Security/Meetings/2011-12-28|2011-12-28]]<br />
* [[Security/Meetings/2011-12-21|2011-12-21]]<br />
* [[Security/Meetings/2011-12-07|2011-12-14]]<br />
* [[Security/Meetings/2011-12-07|2011-12-07]]<br />
* [[Security/Meetings/2011-11-30|2011-11-30]]<br />
* [[Security/Meetings/2011-11-23|2011-11-23]]<br />
* [[Security/Meetings/2011-11-16|2011-11-16]]<br />
* [[Security/Meetings/2011-11-09|2011-11-09]]<br />
* [[Security/Meetings/2011-11-02|2011-11-02]]<br />
* [[Security/Meetings/2011-10-26|2011-10-26]]<br />
* [[Security/Meetings/2011-10-19|2011-10-19]]<br />
* [[Security/Meetings/2011-10-12|2011-10-12]]<br />
* [[Security/Meetings/2011-10-05|2011-10-05]]<br />
* [[Security/Meetings/2011-09-28|2011-09-28]]<br />
* No meeting on 9/14 (All Hands) or 9/21 (Fuzzing Work Week)<br />
* [[Security/Meetings/2011-09-07|2011-09-07]]<br />
* [[Security/Meetings/2011-08-31|2011-08-31]]<br />
* [[Security/Meetings/2011-08-24|2011-08-24]]<br />
* [[Security/Meetings/lifecycledisc|Life Cycle discussion]]<br />
* [[Security/Meetings/2011-08-17|2011-08-17]]<br />
* [[Security/Meetings/2011-08-10|2011-08-10]]<br />
* [[Security/Meetings/2011-07-27|2011-07-27]]<br />
* [[Security/Meetings/2011-07-20|2011-07-20]]<br />
* [[Security/Meetings/2011-07-13|2011-07-13]]<br />
* [[Security/Meetings/2011-07-06|2011-07-06]]<br />
* [[Security/Meetings/2011-06-29|2011-06-29]]<br />
* [[Security/Meetings/2011-06-22|2011-06-22]]<br />
* [[Security/Meetings/2011-06-15|2011-06-15]]<br />
* [[Security/Meetings/2011-06-08|2011-06-08]]<br />
* [[Security/Meetings/2011-06-01|2011-06-01]]<br />
|}<br />
<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Joint Secteam-Infrasec Meetings 2012 <br />
|-<br />
|<br />
* [[Security/Meetings/2012-01-12|2012-01-12]]<br />
|}<br />
{| class="wikitable collapsible collapsed" style="width: 100%"<br />
! Joint Secteam-Infrasec Meetings 2011<br />
|-<br />
|<br />
<br />
* [[Security/Meetings/2011-12-15|2011-12-15]]<br />
* [[Security/Meetings/2011-11-17|2011-11-17]]<br />
* [[Security/Meetings/2011-10-06|2011-10-06]]<br />
* [[Security/Meetings/2011-09-08|2011-09-08]]<br />
* [[Security/Meetings/2011-08-25|2011-08-25]]<br />
* [[Security/Meetings/2011-08-11|2011-08-11]]<br />
* [[Security/Meetings/2011-07-28|2011-07-28]]<br />
* [[Security/Meetings/2011-06-16|2011-06-16]]<br />
|}<br />
|}</div>Jessehttps://wiki.mozilla.org/index.php?title=Firefox/Channels/Meetings/2012-03-29&diff=414097Firefox/Channels/Meetings/2012-03-292012-03-29T21:03:38Z<p>Jesse: /* Schedule Update */</p>
<hr />
<div><!-- YOU WILL WANT TO BUMP THESE VALUES <br />
See the 'Templates Used' sections below and edit the number in each template as needed, then use {{AURORA_VERSION}} and {{BETA_VERSION}} below in queries<br />
--><br />
<!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!<br />
--><br />
<center>[[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Firefox/Channels/Meetings |index]] | [[Firefox/Channels/Meetings/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</center><br />
<br />
'''Channel Meeting Details'''<br />
* Tuesdays and Thursday - 2:00pm PDT, 21:00 UTC<br />
* Mountain View Offices: Warp Core Conference Room<br />
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel<br />
<br />
'''Video/Teleconference Details - NEW'''<br />
* 650-903-0800 or 650-215-1282 x92 Conf# '''95312''' (US/INTL)<br />
* 1-800-707-2533 (pin 369) Conf# '''95312''' (US)<br />
* Vidyo Room: Warp Core<br />
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Guest URL]<br />
<br />
{{Notes}}<br />
<br />
__FORCETOC__<br />
<br />
== Previous Actions ==<br />
* QA/Jorge: {{bug|722538}} – block AMD Radeon HD 6290/6300/6310/6320 for DIRECT2D<br />
* <strike>RelEng: scoping of custom WN page for 3.6->12/13</strike><br />
** {{bug|739793}} – allow passing previous version to post-upgrade homepage override URL<br />
* <strike>Alex: to set up a meeting about 12/13 boundary with OS versions (esp. w/r/t 3.6.28->13) - {{bug|723158}} needs to happen before Beta 13</strike><br />
** Thursday at 10AM PT in PB&J<br />
* <strike>Asa: finalize automated 3.6->12 auto update decision</strike><br />
** email sent to dev-planning<br />
* Asa: determine if {{bug|718088}} should go out in 13<br />
<br />
== Schedule Update ==<br />
* [https://wiki.mozilla.org/Releases/Post-mortems/Firefox_11.0 Firefox 11 post-mortem] held yesterday<br />
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/H7jdpvT3Nbc Proposed 3.6 update plan announced this morning on dev-planning]<br />
* Win2k/XP SP1 desupport meeting held earlier today, have status update<br />
<br />
* Beta 3 out the door tomorrow<br />
** QA is on track for mid-morning sign-off as per normal<br />
<br />
* Maple uplift (and mobile Beta off of Aurora) plans to be solidified Friday - our expectation is a Monday uplift<br />
<br />
==Add-ons==<br />
<br><br />
== Stability ==<br />
===Aurora===<br />
<br><br />
===Beta===<br />
<br><br />
===Release===<br />
<br><br />
== QA ==<br />
===Aurora===<br />
Nothing unique to Aurora being tracked<br />
<br />
===Beta===<br />
<bugzilla><br />
{<br />
"id":"714320,720987,738392"<br />
}<br />
</bugzilla><br />
<br />
== RelEng ==<br />
<br><br />
== Marketing/Communications ==<br />
<br><br />
== Roundtable ==<br />
<br><br />
== Actions ==<br />
<br><br />
== Triage ==<br />
=== Aurora Queries ===<br />
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+flag%3Aapproval-mozilla-aurora%3F&order=Bug+Number '''Approval requests''']<br />
* [https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=cf_tracking_firefox{{AURORA_VERSION}}&resolution=---&resolution=DUPLICATE&query_format=advanced&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number&list_id=1793640 '''Tracking noms''']<br />
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{AURORA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{AURORA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{AURORA_VERSION}}''']<br />
<br />
=== Beta Queries ===<br />
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=approval-mozilla-beta%3F&order=Bug%20Number '''Approval requests''']<br />
* [https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_firefox{{BETA_VERSION}}&type0-0-0=equals&value0-0-0=%3F&order=Bug%20Number '''Tracking noms''']<br />
* [https://bugzilla.mozilla.org/buglist.cgi?field1-0-0=cf_status_firefox{{BETA_VERSION}};type0-0-0=equals;value0-0-0=%2B;field0-0-0=cf_tracking_firefox{{BETA_VERSION}};type1-0-0=notregexp;value1-0-0=%28fixed|wontfix|unaffected|verified%29;order=Bug%20Number '''Unresolved Tracking Bugs for FF{{BETA_VERSION}}''']</div>Jessehttps://wiki.mozilla.org/index.php?title=Silent_Update_not_now_prompt&diff=408613Silent Update not now prompt2012-03-16T19:43:58Z<p>Jesse: </p>
<hr />
<div>{{FeatureStatus<br />
|Feature name=Silent Update: Updated workflow for users with incompatible add-ons<br />
|Feature stage=Development<br />
|Feature status=In progress<br />
|Feature version=Firefox 14<br />
|Feature health=OK<br />
|Feature status note=Team met with UX to review use cases and the specs have been updated to reflect the latest plan. Feature page is ready for development. Other work has been prioritized ahead of this. Targeting Fx14 but may be Fx15.<br />
}}<br />
{{FeatureTeam<br />
|Feature product manager=Chris Lee<br />
|Feature feature manager=Lawrence Mandel<br />
|Feature lead engineer=Robert Strong<br />
|Feature qa lead=Ioana Budnar<br />
|Feature ux lead=Alex Limi<br />
}}<br />
{{FeaturePageBody<br />
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation. We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario.<br />
<br />
*{{bug|715607}}<br />
|Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version. However, as Firefox runs through the installation process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with the new version of Firefox. <br />
<br />
Given there are incompatible add-ons, Firefox will not update Sandra to the latest version of Firefox and enter a 10 day grace period that will continue to check in the background if her incompatible add-ons become compatible. <br />
<br />
There are a few things to note here:<br />
<br />
*If both add-ons become supported within the 10 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened. <br />
*Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks. She has the option to "remind me later".<br />
*If she selects "remind me later", Firefox will defer for 10 additional days and on day 20, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible. Firefox informs her via the notification bar that certain add-ons were disabled due to a Firefox security update. <br />
<br />
<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:<br />
<br />
*Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox. <br />
*To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward. All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated. <br />
*Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience. Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.<br />
|Feature requirements=*All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date<br />
** ITYM "eligible to update, modulo checking frequency and [https://wiki.mozilla.org/Firefox/Features/Lessen_App_Update_Displayed_UI prompts for long sessions]" -Jesse<br />
*For users with 1 or more incompatible Add-ons, we will offer a 10-day grace period with no prompt to update Firefox (assuming this passes security review)<br />
*As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 10-day grace period when all of their incompatible Add-ons become compatible<br />
*On the 10th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:<br />
**"Update now" -- We ask users to update now and inform them that their browser is insecure and they are more vulnerable to attacks. We will disable all incompatible add-ons (we will not remove them) at the time of updating.<br />
**"Remind me later" -- We will defer the update for 10 additional days and on day 20, we will update users automatically. However, we will notify users via the notification bar with the following message:<br />
***"For security reasons, Firefox has been upgraded, but certain add-ons have been disabled. Please contact the add-on authors for more info. [Link to add-ons manager]"<br />
*Some additional requirements we discussed:<br />
**In the preferences dialog under Advanced > Update, remove the "never check for updates" radio button option. <br />
**In the preferences dialog under Advanced > Update, remove the "Warn me if this will disable any of my add ons" check box. Now that we've moved to add-ons default to compatible, the only add-ons that will be incompatible are ones with binary components. This logic should be included in the 'recommended' update selection.<br />
**Create an add-on that allows users who want to have the option to disable the ability for Firefox check for updates.<br />
}}<br />
{{FeatureInfo<br />
|Feature priority=P1<br />
|Feature rank=1.1<br />
|Feature theme=Experience<br />
|Feature roadmap=Firefox Desktop<br />
|Feature list=Desktop<br />
|Feature project=Silent Update<br />
|Feature engineering team=Desktop front-end<br />
}}<br />
{{FeatureTeamStatus<br />
|Feature security status=sec-review-needed<br />
|Feature security health=Assigned<br />
|Feature security notes=imelven is embedded here and should look at this first<br />
|Feature qa status=In progress<br />
|Feature qa notes=[https://wiki.mozilla.org/Silent_Update_not_now_prompt/TestPlan Test Plan]<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Meetings/SecurityAssurance/2012-03-13&diff=407307Security/Meetings/SecurityAssurance/2012-03-132012-03-13T22:12:39Z<p>Jesse: </p>
<hr />
<div><!-- Maybe don't screw with these links unless you've read this blog post:<br />
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/<br />
Just copy them to new pages and it should Just Work!--><br />
<br />
<center>[[Security/Meetings/SecurityAssurance/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&laquo; previous week]] | [[Security/Meetings/SecurityAssurance|index]] | [[Security/Meetings/SecurityAssurance/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &raquo;]]</center><br />
<br />
{{SecAssuranceMeetingInfo}}<br />
<br />
{{TOC right}}<br />
<br />
=Agenda=<br />
* Goals - 2 weeks left<br />
* Q2 Goals<br />
* Team<br />
* Bugzilla Security Mail - https://wiki.mozilla.org/Security/Security_Bugs/EncryptedBugmail<br />
* Pwn2Own Update<br />
* Status updates (cutisk)<br />
** https://wiki.mozilla.org/Security/Radar#Action_Items_from_Security_Review_Meetings (database error? it's a feature)<br />
** https://wiki.mozilla.org/Security/Radar#Individually_Assigned_Reviews_.2F_tasks<br />
* Static Analysis<br />
** https://security.etherpad.mozilla.org/Static-Analyzers (add stuff to it)<br />
* Tag Merger update (curtisk)<br />
* SecReview form update<br />
= Second half =<br />
* [decoder] ASan as a nightly and/or for hardened environments <br />
* B2G permissions model (dchan, want to chat?)<br />
=Project Updates Below=<br />
==B2G==<br />
** Discussions on the Permissions Model ongoing<br />
** Developer Phone release 4/1/12 [https://wiki.mozilla.org/B2G/Schedule_Roadmap]<br />
** Q1 Goals - complete review for developer phone<br />
*** Dependant on B2G hitting this milestone (currently 5/40 features are "done".)<br />
*** https://wiki.mozilla.org/B2G/Schedule_Roadmap<br />
** Q2 Goals - product phone aiming for release by end of Q2 so:<br />
*** Complete all necessary security reviews<br />
*** Complete documentation of B2G security architecture (is this something we are responsible for? I guess not, but I think we want to be involved)<br />
*** Develop B2G fuzzing platform?<br />
==Automation Tools==<br />
** Debate on whether Marionette should land on Gecko between devs and code reviewers in {{bug|712643}}.<br />
==Fuzzing==<br />
** [gkw, decoder] m-c, IonMonkey fuzzing continuously underway<br />
*** decoder has a lot of asserts, gkw a lot of hard-to-reproduce-by-IM-devs GC bugs, Jesse a lot of general bugs<br />
** [decoder] Continue mobile fuzzing goal from Q1<br />
*** In Q2: Deploy fuzzers compatible with ADBFuzz developed in Q1 (e.g. jsfunfuzz, domfuzz)<br />
**** Involves getting necessary hardware and process in place<br />
** Move fuzzers to Releng hardware. jsfunfuzz harness migration underway.<br />
*** Non-mobile hardware already in-place.<br />
*** [gkw] Needed if we are to release funfuzz in April<br />
**** why?<br />
**** I wouldn't want to release old code from literally years ago only to overhaul them as they get released. Makes documentation easier (documenting the new code) as well.<br />
** I'd like if releng committed to fixing https://bugzilla.mozilla.org/show_bug.cgi?id=628573 ;)<br />
*** They rank it P3.<br />
** [gkw] Several Valgrind blockers for Mac OS X Snow Leopard & Lion fixed by sewardj<br />
** [jesse] tweaking jsfunfuzz to find bugs like our pwn2own bug https://bugzilla.mozilla.org/show_bug.cgi?id=720079<br />
==ASan==<br />
* http://blog.mozilla.com/decoder/2012/01/27/trying-new-code-analysis-techniques/<br />
* http://blog.mozilla.com/decoder/2012/03/09/update-on-address-sanitizer/<br />
* Q2 goal: get builds from RelEng<br />
** Get regular testing of Firefox setup<br />
** Integrate with our crash reporting so we can receive ASan crash reports once we decide to have more people testing ASan builds (e.g. a special nightly).<br />
*** This could be great for troubleshooting. "Hitting an intermittent crash? Try an ASan build and see if it becomes a reliable crash."<br />
* ASan builds as a "hardened Firefox" for paranoid users?<br />
** For what kinds of does ASan really prevent exploitation, as opposed to just requiring attackers to change offsets or do more allocations?<br />
*** Use-after-free as well as stack+heap buffer overruns should be covered<br />
** How many people are willing to take a 3x slowdown for it?<br />
** How would this compare to using debug builds with (at least some) assertions fatal?<br />
*** Maybe we should enable the nsTArray and nsPresArena and compartment assertions for these builds, but not all assertions.<br />
** Target audience size not as big, asan builds likely Linux/Mac-only</div>Jessehttps://wiki.mozilla.org/index.php?title=Fennec/Features/readability&diff=407230Fennec/Features/readability2012-03-13T21:02:31Z<p>Jesse: </p>
<hr />
<div>{{FeatureStatus<br />
|Feature name=Text Readability<br />
|Feature stage=Development<br />
|Feature status=In progress<br />
|Feature version=Firefox 11<br />
|Feature health=At risk<br />
|Feature status note=Core code has landed in time for Firefox 11; uncertain whether the heuristics for dealing with Web pages are going to be able to be in shape in time (or how much change will need to happen to get them in shape).<br />
}}<br />
{{FeatureTeam<br />
|Feature product manager=Jay Sullivan<br />
|Feature feature manager=Sheila Mooney<br />
|Feature lead engineer=David Baron<br />
|Feature qa lead=Ioana Chiorean [[irc://irc.mozilla.org ioanachiorean irc]] [[mailto:ioana.chiorean@softvision.ro e-mail]]<br />
}}<br />
{{FeaturePageBody<br />
|Feature open issues and risks=We need to choose a high-level approach. The table below lists a few that we have considered; there may be other options, or some combination.<br />
<br />
This feature has many potential issues with website compatibility. Whichever approach we choose will probably require iteration and tuning, so we should plan to have it enabled in Nightly for close to a full release cycle before enabling it on Aurora. (This means that if we start development work in the middle the Firefox 6 cycle, then we should probably plan on shipping the feature enabled no sooner than Firefox 7.)<br />
<br />
<table class="fullwidth-table"><br />
<tr><br />
<td>Approach</td><br />
<td>Pros</td><br />
<td>Cons</td><br />
</tr><br />
<tr><br />
<td> '''Fennec 4.0 style''' - On double tap, change minimum font size based on width of tapped element ({{Bug|611555}}).</td><br />
<td><br />
* Was possible to implement mostly in the front-end, late in the 4.0 cycle<br />
* Does not affect layout of pages until they are zoomed.<br />
</td><br />
<td> <br />
* Does not work well with pinch zoom.<br />
* Mangles layout of some pages.<br />
* Does not work well with elements like input fields.<br />
* Requires re-layout after zoom (can be slow).<br />
</td><br />
</tr><br />
<tr><br />
<td> '''Android style''' - On zoom, re-wrap text based on the zoom level ({{Bug|578179}}).<br />
</td><br />
<td><br />
* Works well with pinch zoom - the user can zoom text to any size and it will still fit on screen.<br />
* Android users expect it and like it.<br />
* Does not affect layout of pages until they are zoomed.<br />
* Does not mangle layout on most pages.<br />
* Works well with elements like input fields.<br />
</td><br />
<td> <br />
* Requires re-layout after zoom (can be slow).<br />
* Will still mangle layout on a few pages.<br />
</td><br />
</tr><br />
<tr><br />
<td> '''iPhone style''' - Set a minimum font size per element based on its text width ({{Bug|627842}}).<br />
</td><br />
<td> <br />
* Does not require re-layout after zoom.<br />
* With proper tuning, does not mangle layout on most pages.<br />
* Can probably work well with elements like input fields.<br />
</td><br />
<td> <br />
* Does not work well with pinch zoom.<br />
* Will still mangle layout on a few pages.<br />
* Alters layout on pages even before they are zoomed.<br />
* For Safari, web developers often work around layout mangling by adding -webkit-text-size-adjust CSS styles. Will they bother doing similar work for Fennec?<br />
* May not meet Android user expectations.<br />
* Some implementation issues need to be worked out to avoid feedback loops in the layout engine.<br />
</td><br />
</tr><br />
</table><br />
|Feature overview=Optimize zoom, reflow, and font sizes for best text readability.<br />
|Feature dependencies=* {{Bug|578179}} - Option to wrap text to screen width rather than container width<br />
* {{Bug|611555}} - should reflow on zoom [see dependencies for related bugs]<br />
* {{Bug|627842}} - Allow minimum font size based on size of frame<br />
* {{Bug|598736}} - Use higher-quality image scaling. (Affects readability of text in IMG elements.)<br />
|Feature ux design==== Design of record ===<br />
<br />
The design is to create a hybrid approach that has the benefits of iOS-style font inflation on page load, but that also covers the cases where Android-style reflow zoom is preferable. The approach described here should achieve readable font sizes, even when some reflow is required, without creating blocks of empty whitespace as in the native Android method.<br />
<br />
* The advantage to the initial font-inflation is that it's quick and results in:<br />
** and initial page where text should be a little to much more readable even without zooming in; often this won't be enough to really read an article on a news page, but might be enough to let a user see if he/she is interested in zooming in<br />
** a font size for the "body" article text on a page that, when zoomed into by either pinch or double-tap, is close to an optimal reading size without any reflow required (that body font, on page load, was inflated to a size that would be readable when zoomed into such that the column fits the screen). When this is good enough, it is a seamless experience from the user's experience<br />
* The shortcoming is that sometimes the body text cannot be inflated enough to be readable when zoomed without that font, at full zoom out, looking comically big; on iOS, then make a compromise by picking some in between font size, which means that, even on zoom in, the font is still not big enough to be readable.<br />
** To do something about this last case is where the Android-style mechanism comes in, though in our case, we're going to try accomplishing it with more font inflation, on double-tap.<br />
<br />
So, the approach is to:<br />
# On page load, inflate the font size of the "body" part of the page. As on iOS, this requires some heuristics so that areas of the page where font inflation would break the page layout (anything in a table, sidebar areas, etc.) do not get inflated. The inflation that does take place should increase the body font size such that, when that area is zoomed to fit by pinch-zooming, the font is at a good baseline readable size. This size may not be quite as large as our optimal size.<br />
# If step 1 does not get us to where we want to be, we will pursue step 2 which will apply a more aggressive metric on double tap<br />
## On double-tap of a particular area, the browser should further inflate the font size of that particular area if necessary to get to our optimal reading size. I think (someone correct me) that this involves some reflow. This would not happen on pinch zoom -- just on doubletap, because then we know exactly what block a user is trying to read.<br />
## Zooming back out, either by double-tap or pinch, would return the page to its initial font-inflated state (i.e. what the page looked like on load)<br />
## Double-tap zooming to a further-in nested area would further apply the aggressive inflation to that area to ensure its readability<br />
<br />
<br />
=== Older Discussion ===<br />
Some rough specs for two of the options above. (See also [https://groups.google.com/forum/#!topic/mozilla.dev.platforms.mobile/FDlBO8f1dCM this newsgroup discussion].)<br />
<br />
The following sections describe two approaches to making designed-for-desktop web pages readable on phones. Of the two, the '''UX team's preference is for the first one: Android-style reformat on zoom.''' It is what android users are used to, and it solves a broader range of readability cases.<br />
<br />
==== Android/Opera-style re-wrapping ({{bug|578179}}) ====<br />
<br />
When the user zooms the page, all text on the page reflows so that lines of text are no longer than the screen width, even if the containing box is wider than the screen. Only line wrapping is affected; the widths of block-level CSS elements are unchanged. We might choose to do this only when the user double-taps on a piece of text, or for both double-tap and pinch zoom actions.<br />
<br />
If the user double-taps to zoom, then the browser will align the left edge of the tapped block to the left side of the screen (so the re-wrapped lines of text will fit entirely on the screen).<br />
<br />
If the user pinches to zoom (and if we enable this feature for pinch zoom), then after zooming the browser should re-wrap text and then pan the page if necessary to move lines of re-wrapped text onto the screen. (This panning would occur only in cases where the rewrapped text ends up partly on-screen and partly off-screen. In cases where there is text partly off-screen in more than one direction, we would a rule to pan to the closest piece of text, or the largest, or whatever.)<br />
<br />
This feature be enabled/disabled by a preference, and this preference should probably be exposed to the user. (Experience with Firefox and other mobile browsers shows that users are divided over this feature.) For the implementation, the platform could expose a setter to specify a maximum text width, and the mobile front-end could set the value based on the current zoom level. The panning behavior above might also require platform support.<br />
<br />
==== Safari-style font zoom ({{bug|627842}}) ====<br />
<br />
The font sizes of some text on the page is increased based on heuristics. The heuristics include the width of the text (wide text needs to be scaled up more so that it can be readable while still fitting on the screen). There may be additional heuristics to avoid resizing text in ways that is likely to interfere with the normal layout of the page. (Needs more research or testing of approaches.)<br />
<br />
WebKit provides a "-webkit-text-size-adjust: none" CSS property that authors can use to prevent this resizing in places where it breaks the intended layout of the page. We might need to to do the same for Gecko, and evangelize its use.<br />
<br />
This feature should be enabled/disabled by a preference, so that (for example) it can enabled by default for mobile but not for desktop, or possibly exposed to the user through settings or add-ons.<br />
|Feature implementation notes=* https://bugzilla.mozilla.org/show_bug.cgi?id=627842<br />
* https://wiki.mozilla.org/User:Dbaron/Readability<br />
}}<br />
{{FeatureInfo<br />
|Feature priority=P1<br />
|Feature roadmap=Firefox Mobile<br />
|Feature list=Mobile<br />
|Feature engineering team=Layout<br />
}}<br />
{{FeatureTeamStatus<br />
|Feature security status=sec-review-complete<br />
|Feature security health=At risk<br />
|Feature security notes=Jesse added the relevant prefs to the DOM fuzzer.<br />
}}</div>Jessehttps://wiki.mozilla.org/index.php?title=Platform/Roadmap&diff=397829Platform/Roadmap2012-02-15T20:26:17Z<p>Jesse: Fix some typos</p>
<hr />
<div><section begin="summary" />{{RoadmapSummary<br />
|icon=Tempicon.png<br />
|pagelocation=Platform/Roadmap<br />
|pagetitle=Firefox Platform 2012 Roadmap<br />
|owner=Chris Blizzard<br />
|updated=January 2012<br />
|status=Awesome<br />
|description=This roadmap outlines the current strategy and direction for Firefox Platform development through 2012. It mostly covers new developer-facing APIs. Work on [https://wiki.mozilla.org/Performance/Snappy performance] and reliability is done elsewhere.<br />
}}<section end="summary" /> <br />
<br />
==Vision==<br />
This roadmap covers the surface area that we will expose to web developers in order to let them build the next generation of web applications. Overall our vision for Firefox's role in the web ecosystem is:<br />
<br />
'''We want the platform in Firefox to enable app-quality experiences and developer productivity that rivals native platforms.'''<br />
<br />
This roadmap covers the high-priority items that we should accomplish during 2012 in order to achieve this goal. We've broken the list of items roughly down by domain area, with small amounts of context around each one.<br />
<br />
==Networking==<br />
Networking covers several areas that are important to improving experiences in web browsers. In particular, there's a decent amount of work that can be done to improve performance. During 2012, we would like to be able to deploy SPDY, which offers significant performance improvements to end users on sites with many resources, as well as better resource management for servers.<br />
<br />
While SPDY's benefits are useful for sites that have SPDY-capable servers, most of the rest of the web still will run off HTTP for the foreseeable future. We've got some innovative ideas around how to deploy HTTP Pipelining, which would give many of the benefits that we can get with SPDY, but that will actually work with most of the web as its deployed today. Users will definitely be able to feel improvements from HTTP pipelining, especially for anyone using a high-latency mobile connection or over a trans-oceanic link.<br />
<br />
In addition, in order to support a richer and more seamless media experience there's work that needs to be done to support the emerging DASH-for-WebM standard. This will let the browser and server adapt to changing network conditions, start a video faster and adapt quickly to changes in resolution. (Like, when you change from in-a-page to full screen.)<br />
<br />
{| class="fullwidth-table"<br />
!Name<br />
!Description<br />
!Status<br />
!When<br />
!Who<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=695635 Compete WebSockets to Match RFC]<br />
| This brings WebSockets to the point where it matches the IETF RFC. It includes the protocol and API bits from the W3C.<br />
| Done<br />
| Done<br />
| Networking & Blizzard<br />
|-<br />
| [https://wiki.mozilla.org/Platform/Features/SPDY Support for SPDY]<br />
| SPDY is a new protocol built on the request app model of the web that allows for multiplexing, connection sharing and is SSL-only. It saves costs for server vendors who will have to deal with fewer connections per page load. And for end users it makes pages generally feel faster to load.<br />
| Checked in for testing, not enabled by default.<br />
| Testing in Q1, deployment depending on feedback.<br />
| Networking & Blizzard<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=702122 DASH WebM Support]<br />
| This adds support for adaptive streaming for video with the WebM codec. It's based on the [http://sourceforge.net/apps/trac/matroska/wiki/DASH_Profile WebM + DASH spec]. (This is largely a Media project that Networking has graciously taken on on behalf of both teams.)<br />
| Work underway<br />
| Work underway in Q1. Delivery based on spec stability and feedback, but hopefully in Q2.<br />
| Networking & Maire <br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=264354 HTTP Pipelining]<br />
| This adds support for HTTP pipelining to desktop browsers by default. HTTP pipelining offers a [http://bitsup.blogspot.com/2010/11/performance-of-pipelining-in-http.html significant page load performance win] especially over higher-latency connections (like mobile or any trans-oceanic connection.) The risk here is medium, as the patches have excellent back-off characteristics but pipelining has historically been considered to be difficult to implement. Pipelining is actually used on most mobile devices, but hasn't been turned on in desktop browsers to date.<br />
| Has patches<br />
| After SPDY is done.<br />
| Networking & Blizzard<br />
|-<br />
| HTTP Pre-connections<br />
| Adding support for pre-connections would open HTTP connections ahead of page loads or after search results under the assumption that users will always go to the same sites.<br />
| Not started<br />
| After pipelining.<br />
| Networking & Blizzard<br />
|}<br />
<br />
==Apps==<br />
There are a lot of tasks around Apps that need doing. These fall into a few major categories:<br />
<br />
1. '''Enabling a developer ecosystem.''' The first part of this is to allow users to take control of their identity in a way that fits with the decentralized model of the Internet. (This is useful to web sites as well, not just in the context of apps!) This identity can then be used to prove that they have paid for various items, software or services.<br />
<br />
2. '''Enabling a great experience for users with applications.''' While apps will be based on an HTML5-based platform and should run in any browser, there are several items where the experience should be better with Firefox (or any other browser that implements the same functionality.)<br />
<br />
3. '''Application communication and intergration.''' With Intents (and previously Mozilla Activities) it should be possible for the web to grow with each application that is added. That is, each application doesn't have to be something that stands alone, but instead can be used by other applications to enable new and interesting functionality.<br />
<br />
4. '''New capabilities.''' Items like raw socket access, HTTP without cookies, background tasks and a notifications system are all things that are available to native applications. Installed applications (not necessarily web pages) should have these privileges as well. <br />
<br />
{| class="fullwidth-table"<br />
!Name<br />
!Description<br />
!Status<br />
!When<br />
!Who<br />
|-<br />
| Identity (Verified Email)<br />
| This gives us the ability to assert that an email address has been verified, which is a proxy for identity. This has its own roadmap, but is worth mentioning because it's an important part of the overall roadmap for the rest of the apps platform.<br />
| First stage already deployed, with more UI coming in later quarters.<br />
| Q1<br />
| Dan Mills<br />
|-<br />
| Receipts<br />
| Receipts allows you to assert that a particular identity has paid for a service or item.<br />
| Underway (Jennifer)<br />
| Q1?<br />
| Dan Mills<br />
|-<br />
| Install process for Apps<br />
| An install process allows you to install an app into your browser or into your operating system.<br />
| Underway<br />
| Q1?<br />
| Jennifer<br />
|-<br />
| Make App Cache opportunistic for Firefox Desktop<br />
| This makes the app cache act much like our current cache, in that it has a bounded size and will expire old data. It also means we don't have to ask the user for permission to install something without context. This is useful in the browser context.<br />
| Waiting<br />
| Q2<br />
| DOM & Media & Blizzard<br />
|-<br />
| Updates to the App Cache<br />
| We need to update the App Cache to make it work better in many situations that have been identified since the original specs were written. This includes support in the face of CDNs, extra APIs, etc.<br />
| Scoping<br />
| Q2 to finish scoping and start work<br />
| DOM & Networking & Blizzard<br />
|-<br />
| Improve Register Protocol Handler<br />
| We need to improve our register protocol handler for Apps.<br />
| Unknown (Ben)<br />
| ?<br />
| DOM & Ben<br />
|-<br />
| Replacement for Web Intents<br />
| Web Intents allows applications to register themselves to handle actions and content. The current spec is apparently quite large and complicated and never got off the ground. So it needs re-visiting.<br />
| Unknown (tantek & hanson)<br />
| Maybe start in Q1?<br />
| Tantek & Hanson<br />
|-<br />
| Install trigger - Scope in Q1<br />
| In order to support installations we need the ability for a web site to trigger an install. This is essentially part of our store functionality.<br />
| Scoping<br />
| Q1<br />
| Hanson<br />
|-<br />
| [https://wiki.mozilla.org/Services/Notifications/Push/API Push Notifications]<br />
| Push notifications allow us to push data to installed apps on people's computers and browsers. This would be a pretty major change to the architecture of the web, is closely and would need background tasks and and activation system to support it. These would only be available to "installed" apps.<br />
| Unscoped<br />
| Later in 2012<br />
| Blizzard<br />
|-<br />
| Background tasks<br />
| Background tasks are things that apps can do in the background. These things could be the result of a push notification, network event or a timer that's running. They would only be available to "installed" applications, but could prove very useful.<br />
| Unscoped<br />
| Later in 2012<br />
| Blizzard<br />
|-<br />
| Low-level Socket API<br />
| One thing that's oft requested (especially for games) is a low-level read/write socket API that's available for installed apps. Native platforms can do this easily. This would not be available to untrusted applications/web pages.<br />
| Unscoped<br />
| Later in 2012<br />
| DOM & Networking & Blizzard<br />
|-<br />
| Open HTTP without cookies<br />
| One thing that's often requested by app developers is the ability to make arbitrary HTTP requests that don't share the cookie state with the browser. This is similar to the low-level socket API but is HTTP-specific. Another way to describe this: getting rid of the cross-domain restrictions for installed applications. This would not be available to untrusted applications/web pages.<br />
| Unscoped<br />
| Later in 2012<br />
| DOM & Networking & Blizzard<br />
|}<br />
<br />
==Devices==<br />
While it's important to build a developer ecosystem to enable payments and a great install experience it's also important that we enable a set of web APIs for access to devices connected to a computer, tablet or phone. This includes everything from access to an NFC device, to offline storage to raw touch events from your tablet.<br />
<br />
See also: [https://wiki.mozilla.org/WebAPI the WebAPI page.]<br />
<br />
{| class="fullwidth-table"<br />
!Name<br />
!Description<br />
!Status<br />
!When<br />
!Who<br />
|-<br />
| [https://wiki.mozilla.org/Platform/Features/Camera_API Taking a picture]<br />
| This lets a web page take a picture using the built-in camera for the device or PC.<br />
| Works on Mobile. Does not work on Desktop.<br />
| Q2 (maybe)<br />
| Media & DOM & Firefox & Maire<br />
|-<br />
| [https://wiki.mozilla.org/Features/Platform/OfflineApps Finish IndexedDB]<br />
| This completes the changes that happened to the IndexedDB spec and working on performance problems.<br />
| Done<br />
| 2011Q4<br />
| Blizzard & DOM<br />
|-<br />
| Upload a Directory<br />
| This lets you pick a directory and make it available to both File APIs or upload directly. It should maintain the subtree structure in the original filesystem.<br />
| Not started<br />
| Q2<br />
| Hanson, DOM & Blizzard<br />
|-<br />
| Access to Local Media Storage (including USB)<br />
| This gives access to local media for permitted applications and web pages to upload, sync, or otherwise access. This should be similar to the way that we upload files now, and eventually directories. It just flattens access across devices, PCs, phones, etc. Includes music, pictures and video.<br />
| Not started<br />
| Q2<br />
| Hanson, DOM & Blizzard<br />
|-<br />
| Drag files with download_url<br />
| Chrome includes the ability to mark an a href with a download_url. You can then drag that link to your desktop and the file is downloaded from the URL.<br />
| Not started<br />
| Later in 2012<br />
| DOM & Blizzard<br />
|-<br />
| Finish touch and multi-touch<br />
| We've done some first-pass touch APIs for Windows 7 and mobile. The multi-touch support and gesture support aren't done yet, so we need to finish them. This will be true for Windows 7 and Android.<br />
| Unknown<br />
| Later in 2012<br />
| DOM & Mobile & Firefox & Blizzard & Sicking<br />
|}<br />
<br />
[https://wiki.mozilla.org/WebAPI B2G APIs] (Not managed here.)<br />
Dialer (B2G) - Underway<br />
Network Status (B2G) - Underway<br />
Vibration (B2G) - Underway<br />
Battery (B2G) - Underway<br />
Contacts (sicking & B2G) - Underway<br />
Ambient Light (B2G) - Q2<br />
Proximity to Your Face (B2G) - Q2<br />
<br />
==Layout==<br />
In the area of layout we need to enable a bunch of new ways to express layouts that designers have used through other tools for years. These include flexbox, which is very similar what what we've been using to layout the Firefox UI for years, Grid and Regions & Exclusions. All of these enable new kinds of experiences.<br />
<br />
We also need to enable Gecko to run on Mobile devices. This means that we need to lay out pages with fonts in a sane way and enable spring scrolling for touch devices.<br />
<br />
Please also see the [https://wiki.mozilla.org/Platform/Layout#Feature_Planning Layout Feature Planning Page].<br />
{| class="fullwidth-table"<br />
!Name<br />
!Description<br />
!Status<br />
!When<br />
!Who<br />
|-<br />
| Readability / Font Size inflation<br />
| This is the ability to resize text for mobile devices based on the size of the screen and the reasonable minimum size for text.<br />
| The main layout parts of this were done in Q4 of 2011. There's still some additional work being done in Q1 based on the feedback we've seen.<br />
| Q1<br />
| David Baron & Mobile & Blizzard<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=702508 CSS Flexbox]<br />
| This adds support for something like the XUL box model to the web. It's being implemented in other browsers. It's very important for app layouts and will be a huge upgrade for the web.<br />
| Work underway<br />
| Q1 for single-line flexbox, Q2 for multi-line. Spec is still in a bit of flux.<br />
| Layout & Blizzard<br />
|-<br />
| CSS Grid<br />
| This adds grid layout support to our layout engine. Something well-known in the design community.<br />
| Not started<br />
| Start after Flexbox<br />
| Layout & Blizzard<br />
|-<br />
| CSS Regions & Exclusions<br />
| Magazine-style layouts. Render text around images and other complex interactions with entities in web pages. They are separate specs, but should probably be done together.<br />
| Not started<br />
| Later in 2012<br />
| Layout & Blizzard<br />
|-<br />
| @page support<br />
| Add support for @page<br />
| Not started<br />
| Later in 2012<br />
| Layout & Blizzard<br />
|-<br />
| ruby support<br />
| Add support for HTML5 ruby<br />
| Not started<br />
| Later in 2012<br />
| Layout & Blizzard<br />
|-<br />
| Spring Scrolling Support<br />
| Add support for spring scrolling<br />
| Not started<br />
| Later in 2012<br />
| Jonas & Blizzard<br />
|-<br />
| Scrolling APIs<br />
| Add support for decent scrolling APIs<br />
| Not started<br />
| Later in 2012<br />
| Jonas & Blizzard<br />
|}<br />
<br />
==Media==<br />
Media presents one of the most interesting areas where there's opportunity to build something amazing. These fall into a few areas of note:<br />
<br />
1. '''Enabling games.''' Mozilla's Full Screen API, which is also being implemented in other browsers, is useful for everything from watching videos to playing games. When you combine video, WebGL, fast JavaScript and the Mouse Lock API you end up with something that can create everything from small social games to first person shooters.<br />
<br />
2. '''Combining media.''' The media stream APIs make it possible to combine HTML5 video, real time communications, audio generation, audio manipulation and all kinds of interesting media experiences. This is useful for games, but will also be useful for presentation software, video editing applications and new kinds of media experiences.<br />
<br />
3. '''Real Time Communications.''' The emerging set of standards around WebRTC is the first time we'll see browsers being able to communicate with each other without all communication being routed through some kind of 3rd party server. While most of WebRTC will be audio & video, we're also building a data channel to go along with audio and video. This means that you will be able to build applications and games that save bandwidth and have low latency by avoiding the extra round trip required by a 3rd party server.<br />
<br />
{| class="fullwidth-table"<br />
!Name<br />
!Description<br />
!Status<br />
!When<br />
!Who<br />
|-<br />
| Full Screen Support<br />
| This lets any element on the page go into full screen mode. It's useful for watching HTML5 videos, full screen games, simulations, or anything else that you want to immerse yourself into.<br />
| Done<br />
| Q4, 2011<br />
| Blizzard & Media<br />
|-<br />
| Better Support for Capturing Keys in Full Screen Mode<br />
| We need to find a better way to allow key input in DOM full-screen mode. We need to allow enough key input to be useful for HTML5 games while minimizing the security risk. https://bugzilla.mozilla.org/show_bug.cgi?id=716107<br />
| Underway (need to verify this status with cpearce)<br />
| TBD in 2012<br />
| Maire & Media<br />
|-<br />
| WebRTC<br />
| This is support for real time, audio, video & data communications between two browsers. The connections are point to point, with only the initial rendezvous between clients via a server.<br />
| Underway<br />
| Demo in Q1<br />
| Maire & Media<br />
|-<br />
| Media Stream Processing APIs<br />
| This adds support for media processing, chaining and processing that unifies the Audio Data / Audio Web APIs, video, RTC and other related items into a single useful API.<br />
| Underway<br />
| Demo in Q1<br />
| Blizzard & Media<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=633602 Mouse Lock]<br />
| This compliments the full screen APIs and lets you use the mouse as a controller instead of as a pointing device. Good for first person shooters, simulators, etc.<br />
| Underway<br />
| Later in 2012<br />
| Humphd & Blizzard & Media<br />
|-<br />
| Video Capture & Upload<br />
| This is the ability to record a video locally and upload it to a server once it's recorded.<br />
| Not started.<br />
| Later in 2012<br />
| Blizzard & Media<br />
|}<br />
<br />
==Tests==<br />
We started to ship parts of HTML5 in Firefox 3.5 The spec has moved since then, and there are still some small parts we need to finish. These are often tested on sites as a kind of proxy for standards support and we should invest in finishing where it's appropriate.<br />
<br />
<br />
{| class="fullwidth-table"<br />
!Name<br />
!Description<br />
!Status<br />
!When<br />
!Who<br />
|-<br />
| Finish tests on [http://html5test.com/ html5test.com]<br />
| It's used as a proxy for HTML5 support in order to rate browsers.<br />
| Ongoing<br />
| All through 2012<br />
| Everyone<br />
|-<br />
| Finish test on [http://areweplayingyet.org/ areweplayingyet.org] ({{bug|700208}})<br />
| It's used as a proxy for HTML5 audio support.<br />
| Ongoing<br />
| All through 2012<br />
| Everyone<br />
|}<br />
<br />
<br />
[[Category:Roadmaps]]</div>Jessehttps://wiki.mozilla.org/index.php?title=Firefox/Roadmap&diff=397465Firefox/Roadmap2012-02-15T02:09:03Z<p>Jesse: /* Q2 */ Fix typo</p>
<hr />
<div><section begin=summary />{{RoadmapSummary<br />
|icon=Firefox-512-noshadow.png<br />
|pagelocation=Firefox/Roadmap<br />
|pagetitle=Firefox 2012 Strategy & Roadmap<br />
|owner=Asa Dotzler<br />
|updated=Feb 12, 2012<br />
|description=Firefox is Mozilla's expression of our manifesto and mission; it represents our vision of a people-centric Web experience, as well as a platform that makes it possible to do amazing things with the Web.<br />
}}<section end=summary /><br />
<br />
{{DoNotEdit}}<br />
<br />
<br />
== Firefox Desktop Strategy ==<br />
<br />
In 2012, Firefox will deliver incredible user and developer experiences in four areas.<br />
<br />
First, Firefox will continue shipping innovative new features that ensure users stay in control of their online lives. As a non-profit organization, Mozilla is uniquely positioned for putting users first, and in 2012 Firefox will do just that with features to help users manage how they're tracked on the Web, make sharing across multiple social networks quick and easy, bring privacy and control to the site sign-in process, and much more.<br />
<br />
Second, Firefox will deliver the highest quality browsing experience with top notch performance, memory usage, and stability. In 2012, all browsers do more, stay open longer, and display more and richer content; but as the capabilities of the browsers increase so do the opportunities for the experience to become heavy or unstable. Mozilla understands the value of a responsive user experience and a highly stable and performant platform for Web developers. In 2012 strengthened and dedicated teams will wipe out any and all Firefox responsiveness issues users face and guarantee the rock solid stability at low memory costs that developers demand for their apps.<br />
<br />
Third, while our mission compels us to deliver innovative new features and the highest quality experiences, the Web is more than just the desktop browser and so in 2012 Mozilla will be broadening its product offerings to include a web-wide people-centric identity system, a complete web apps ecosystem, and a no-compromises mobile browser. Integrating these products into the Firefox experience will give users a much richer Firefox and will help launch these new products to a broad user and developer audience.<br />
<br />
Finally, Firefox in 2012 will bring major advances in HTML, CSS, and JavaScript as well as a powerful and beautiful set of Web developer tools. These capabilities will enable app-quality experiences and developer productivity that rivals native platforms.<br />
<br />
<br />
== What is this document!? ==<br />
<br />
This strategy and roadmap is being developed with the direct inputs of key Firefox stakeholders, including engineering teams and technical leads; user experience, user research, and user support teams; marketing, market insights, and engagement teams; product management; and the entire Mozilla community.<br />
<br />
The features covered here are primarily Firefox front-end work. For the specific strategy and feature lists covering [https://wiki.mozilla.org/Platform/Roadmap Platform], [https://wiki.mozilla.org/DevTools/RoadmapDec2011 Developer Tools], [https://wiki.mozilla.org/Apps/Roadmap Apps], [https://wiki.mozilla.org/Fennec/NativeUI Mobile], and [https://wiki.mozilla.org/Identity Identity], [https://wiki.mozilla.org/Performance/Snappy Performance/Responsiveness], and [https://wiki.mozilla.org/CrashKill Stability], visit their respective roadmaps and other documentation.<br />
<br />
== Firefox Desktop Feature Roadmap ==<br />
<br />
=== Q1 ===<br />
* [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible Add-on Compatibility]: Our experience has given us confidence that the overwhelming majority of add-ons are not broken by new Firefox releases, so we are changing Firefox behavior from assuming add-ons are broken with each new release and managing exceptions with an allow list to assuming add-ons are compatible with each new release and managing exceptions with a disallow list.<br />
* [https://wiki.mozilla.org/Firefox/Features/Chrome_migration Chrome Migration]: Firefox already supports migrating from other popular browsers. Users moving from Chrome to Firefox should be able to bring their data with them. We are building this capability into Firefox.<br />
* [https://wiki.mozilla.org/Firefox/Features/Media_Controls_Refresh Refreshed Media Controls]: HTML5 media is increasing on the Web. The default media controls are being refined for usability and to include controls for new HTML5 features like full-screen viewing.<br />
* [https://wiki.mozilla.org/Services/Sync/Features/Addon_Sync Add-ons Sync]: Firefox Sync makes it easy to move between computers and devices. In addition to syncing passwords, bookmarks, and history between Firefox installs, users are going to be able to sync add-ons.<br />
* [https://wiki.mozilla.org/Features/Desktop/Add-on_hotfix Firefox Hotfix]: There are small issues that can occasionally affect Firefox users after a release. Correcting those small issues should not require a full Firefox update. With a new hotfix system, Mozilla can patch minor issues in Firefox without requiring a browser restart.<br />
* Developer Tools advancements: See the [https://wiki.mozilla.org/DevTools/RoadmapDec2011 Developer Tools roadmap].<br />
* Web Platform advancements: See the [https://wiki.mozilla.org/Platform/Roadmap Web Platform roadmap].<br />
<br />
=== Q2 ===<br />
* [https://wiki.mozilla.org/Windows8 Proof of concept for Firefox in Windows 8 Metro]: In order to deliver a compelling Firefox for Windows 8 Metro experience, we need to understand what's possible. A technology proof of concept is the first step. This is not a Alpha or a Beta, but should demonstrate the feasibility of Firefox in Windows 8 Metro. (Timing here is dependent on when Microsoft releases their Windows 8 consumer preview and developer documentation.)<br />
* [https://wiki.mozilla.org/Features/Desktop/Firefox_Home_Tab Firefox Home Tab additions]: Firefox's start page, AKA Firefox Home Tab, is where users start their browsing session and where they land when they've closed their last tab. In addition to easy search, Firefox Home will become a launch point for managing all of your Firefox data.<br />
* [https://wiki.mozilla.org/Firefox/Features/New_Tab_Page A New Tab page powered by the Awesomebar]: For keyboard users, opening a new tab and visiting a top site is super-easy thanks to the Awesomebar. For mouse users, Firefox's new tab page will include a "speed dial" like feature that provides Awesomebar-powered shortcut tiles for super-fast navigation.<br />
* [https://wiki.mozilla.org/Silent_Update Silent Update]: The Firefox update process will be moved to the background and Windows admin passwords and/or UAC prompts will be removed. Also, users with the rare incompatible extension will have a gentler upgrade process.<br />
* [https://wiki.mozilla.org/Web_Apps_integration Web Apps Marketplace integration]: Firefox Home will offer a launcher for the Web Apps Marketplace and promotion for personalized app recommendations.<br />
* [https://wiki.mozilla.org/Support/Firefox_Features/Clean_up_user_profile Restore Firefox]: For various reasons, a Firefox profile can become damaged causing performance and stability problems. Users will be able to quickly and easily restore Firefox without losing their passwords, history, and bookmarks.<br />
* [https://wiki.mozilla.org/Firefox/Features/URL_Autocomplete Awesomebar In-Line URL auto-complete]: In addition to the amazing Awesomebar pop-up list, users will have easy in-line address completion for even faster navigation.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=710372 Smooth scrolling]: Scrolling pages is one of the most common user interactions on the web. With a new scrolling implementation, users will find web page scrolling to be consistently silky smooth.<br />
* [https://wiki.mozilla.org/User:P.A./Panel-based_Download_Manager Panel-based Download Manager]: Firefox was one of the first browsers with an integrated download manger. With the new panel-based manager, users will be able to easily monitor and managing Web downloads without leaving the main browser window.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=692255 Start-up Performance Improvements]: Using the Firefox Windows maintenance service to work around Microsoft's pre-fetch "de-optimization", Firefox start-up speed will be improved dramatically.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=698919 New Cycle Collector] + [https://wiki.mozilla.org/Platform/Features/Incremental_GC Garbage Collector]: With the proliferation of games and other real-time content on the Web, even brief browser pauses are no longer acceptable. Thanks to major improvements to Firefox's cycle and garbage collectors, Firefox pauses and hangs will be a thing of the past.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=669034 Speedy Session Restore]: Session restore makes restarting the browser a frictionless experience. Firefox's session restore is being re-architected for major performance improvements.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=711193 Automatic Session Restore with Tabs on Demand]: Most users prefer starting the browser right where they left off. Firefox is moving to a model that restores all tabs when a user starts up the browser but delays the loading of background tabs until they are needed. This will improve the performance and usability of Firefox just after launch.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=712109 Hang Detector and Reporter]: Similar to how Mozilla collects crash data, this new capability will allow Mozilla to collect, analyze, and fix browser hangs.<br />
<br />
=== 2H ===<br />
* Seamless Plug-in [[Improved_missing_plugin_experience|install]] and update experience: Plug-ins like Flash are still a common experience on the Web. Firefox will make acquiring and updating the most popular plug-ins a simple and easy process.<br />
* Tracking Map and 3rd party cookie management: People are increasingly concerned about how they're tracked on the web. With Firefox's tracking map feature, people will be able to visualize how they are tracked as they move around the web and be empowered to easily block that tracking.<br />
* [https://wiki.mozilla.org/Labs/F1/Feature_Blocks/F1 Firefox Share]: The web is a social experience. But few of us live exclusively inside of any one social network. With Firefox Share, Firefox users will be able to easily share links and status updates across a variety of social networks.<br />
* [https://wiki.mozilla.org/Identity/Features/Sign_into_the_browser Log in to Firefox]: Many users carry around dozens of account logins and passwords but that's way too difficult. Based on the Verified Email standard, Firefox users will be able to log in to Firefox to enable Sync and user-centric site logins. Users will finally be able to say goodbye to remembering countless passwords.<br />
* [https://wiki.mozilla.org/Firefox/Features/Theme_Refinement_and_Evolution Firefox theme refresh]: Firefox is a modern browser that feels like you. With the new [http://people.mozilla.com/~shorlander/firefox-ui-design/firefox-visual-design-across-platforms.html Australis] look and feel, Firefox will be a more inviting and confident experience for users.<br />
* [https://wiki.mozilla.org/Windows8 Alpha and Beta of Firefox for Windows 8 Metro]: The Alpha will prove the installation path and basic browsing features. The Beta will be feature complete for a 1.0-capability product.<br />
* [https://wiki.mozilla.org/Features/Firefox/Network_Installer Network Installer]: Firefox's installer is the first experience of Firefox for most users. A new lightweight installer will strengthen security and help improve download performance.<br />
* [https://wiki.mozilla.org/Browser_translation Integrated translation service]: Firefox users, especially outside of the the U.S., encounter a lot of content that's not written in their native tongue. Firefox will offer an easy to use translating feature that makes reading foreign language content a piece of cake.<br />
* [https://wiki.mozilla.org/Firefox/Features/Expose_Add-on_Performance Add-on performance indicators]: Some add-ons cause Firefox users to experience performance and memory problems. Firefox will give users the information they need to decide whether or not a problematic add-on is worth the performance cost.<br />
* Site-based permissions manager: Currently users manage their permissions on a per-feature basis: cookies, passwords, history, etc. This is confusing. A site-based permission manager will empower people to edit all of the permissions associated with any particular site.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=712731 Multiple] [https://bugzilla.mozilla.org/show_bug.cgi?id=715376 Tab] [https://bugzilla.mozilla.org/show_bug.cgi?id=715378 Performance] Improvements: Most Firefox users have several tabs open in a session and background tabs can consume computer resources in ways that slow down the focused tab. There are several upcoming changes to Firefox that will better balance resources to improve performance for the focused tab.<br />
* [https://wiki.mozilla.org/Program_Management/Projects/SearchHijacking Search hijack prevention]: Because search is such a lucrative Web feature, some add-ons and plug-ins are switching user search settings without user consent. We can alert the user when a third party tries to change their search service settings.<br />
* [http://msujaws.wordpress.com/2012/01/09/in-content-preferences-for-firefox-may-be-here-in-16-weeks/ In-line Preferences Manager]: People appreciate Firefox's customizability, but some changes are too difficult for most users. Firefox Preferences will be moved from a pop-up window into the content area of the browser in order to improve ease of customization.<br />
* [https://bugzilla.mozilla.org/show_bug.cgi?id=711552 Plug-in Click to Start]: In order to protect our users from drive-by plug-in exploits and to provide users with more control over plug-ins in the browser, Firefox will have a new "click to play" feature.<br />
* [https://wiki.mozilla.org/Focus_mode Firefox Focus/Reader Mode]: Despite the rise of multi-media on the Web, reading is still the most common web activity. We will make reading long-form content a wonderful experience with a user-activated re-formatting and re-styling of the page that puts focus on the content rather than ads and navigation.<br />
* [https://wiki.mozilla.org/Platform/Features/IonMonkey IonMonkey]: The next generation of the Firefox JavaScript engine, code-named IonMonkey, will bring dramatic improvements to JavaScript performance making Web applications even faster.<br />
* [https://groups.google.com/forum/#!topic/mozilla.dev.tech.network/cUqRe8ZZjbA/discussion New Cache]: Firefox's network cache will be overhauled to improve page loading performance.<br />
* New DOM bindings: DOM manipulations are one of the performance bottlenecks in browsers today. To dramatically improve DOM performance for rich web applications, Mozilla will deliver a revamped for performance set of DOM bindings.<br />
* [https://wiki.mozilla.org/JavaScript:GenerationalGC Generational GC]: Moving to a generational collector will increase cache locality and make collections less expensive, increasing performance for apps and benchmarks that create a lot of short-lived objects.<br />
* [https://wiki.mozilla.org/Show_PDF_inline Inline PDF View]: Most users encountering PDFs on the Web do not need the full capabilities of a dedicated PDF editor application. A built-in PDF viewer will make viewing and previewing PDFs faster and safer for all users.</div>Jessehttps://wiki.mozilla.org/index.php?title=Security/Features/Application_Reputation&diff=395337Security/Features/Application Reputation2012-02-08T18:40:13Z<p>Jesse: Created page with "{{FeatureStatus |Feature name=Application Reputation |Feature stage=Feature Inbox }} {{FeatureTeam |Feature lead engineer=Needed |Feature privacy lead=Needed |Feature ux lead=Nee..."</p>
<hr />
<div>{{FeatureStatus<br />
|Feature name=Application Reputation<br />
|Feature stage=Feature Inbox<br />
}}<br />
{{FeatureTeam<br />
|Feature lead engineer=Needed<br />
|Feature privacy lead=Needed<br />
|Feature ux lead=Needed<br />
|Feature additional members=Bizdev needed<br />
}}<br />
{{FeaturePageBody<br />
|Feature overview=Bug 662819.<br />
<br />
We warn on every application download, which causes warning fatigue and doesn't help users make good decisions. We should track the reputation of download URLs and hashes.<br />
|Feature users and use cases=Downloading popular, legitimate applications: warnings should become less severe and less redundant.<br />
<br />
Downloading known malware or unknown applications: warnings should become more severe and clearer about the origin of the download. Perhaps more similar to the UI for installing Firefox addons (since the result is equivalent).<br />
|Feature requirements=* Preserve privacy as much as possible. This should only apply to downloaded applications, not documents. The URL should not be sent to Mozilla if the download is declined. Users should have the option to use this feature without contributing data to it.<br />
|Feature non-goals=* Virus scanning.<br />
* Offering to sandbox untrusted native applications.<br />
* Preventing downgrade attacks.<br />
* Forcing application download sites to use https.<br />
* Foist AMO-style user reviews upon application download sites.<br />
}}<br />
{{FeatureInfo<br />
|Feature priority=Unprioritized<br />
|Feature roadmap=Security<br />
}}<br />
{{FeatureTeamStatus}}</div>Jessehttps://wiki.mozilla.org/index.php?title=SecurityEngineering/Roadmap&diff=395268SecurityEngineering/Roadmap2012-02-08T17:43:50Z<p>Jesse: /* Related Info */</p>
<hr />
<div><small>[[Roadmaps|&lt; Product Roadmaps]] </small> <br />
<br />
<section begin="summary" />{{RoadmapSummary<br />
|icon=larry.png<br />
|pagelocation=Security/Roadmap<br />
|pagetitle=Product Security Feature Roadmap<br />
|owner=[[User:Ladamski|Lucas Adamski]]<br />
|updated=Weekly<br />
|status=Draft<br />
|description=Security at Mozilla can be thought of a set of principles that are reflected in the products we ship, but also in the impact Mozilla has on the entire web. As such our security roadmap should reflect the real security improvements we need to make to our products to reflect the evolving security landscape, but also the ambitious impact we'd like to have on all web users.}}<section end="summary" /> <br />
<br />
{{Draft}} <br />
<br />
<br> <br />
<br />
= Vision =<br />
<br />
Security at Mozilla can be thought of a set of principles that are reflected in the products we ship, but also in the impact Mozilla has on the entire web. <br />
<br />
= Themes and Goals =<br />
<br />
Web users are under constant attack from a wide variety of opponents, many of whom are merely opportunistic, but also by a minority of very clever and determined attackers.&nbsp; To protect users, we need to improve our current products to keep pace with these evolving threats, but we are ultimately limited in what we can do unilaterally within our products.&nbsp; We must also drive innovative solutions that require the participation of other vital players in the web ecosystem, including standards bodies, internet technology vendors, web developers, web admins and web frameworks. <br />
<br />
As such, security engineering at Mozilla has two primary themes:<br />
<br />
*Product Hardening: Protect our users directly from an ever-increasing volume &amp; sophistication of online attacks, by directly improving the products and services we deliver<br />
*Security Leadership: Drive innovative security solutions to enable the wider web ecosystem of web developers, web admins and users to adapt to evolving web technologies and their corresponding security threats.<br />
<br />
Here the concrete goals are segmented into themes. Some goals may potentially fit into multiple themes, but are only identified here under the most relevant one. <br />
<br />
Survey taken in early 2011 to identify and prioritize potential features for our security roadmap. The results of this survey are [https://spreadsheets.google.com/spreadsheet/pub?hl=en&hl=en&key=0AtpjIJJ66IkGdEQwOThzdHVFS0V4aUZUOWoxZXc3alE&output=html available as a Google doc] or as PDF: [[Image:Security roadmap survey.pdf]]. <br />
<br />
'''NOTE:''' these goals are tentative and more may be added or some may be dropped.<br />
<br />
= Roadmap =<br />
'''Items with Feature Pages'''<br />
<table class="querytable sortable"><br />
<tr><br />
<td class="header" style="width: 5%;">Pr</td><br />
<td class="header" style="width: 30%;">Feature</td><br />
<td class="header" style="width: 15%;">Team</td><br />
<td class="header" style="width: 15%;">Stage</td><br />
<td class="header" style="width: 20%;">Product Manager</td><br />
<td class="header" style="width: 15%;">Theme</td><br />
</tr><br />
{{#ask: [[Category:Feature Page]] [[Feature roadmap::Security]] OR [[Feature secondary roadmap::Security]] <br />
| ?#<br />
| ?Feature name#<br />
| ?Feature priority#<br />
| ?Feature engineering team#<br />
| ?Feature stage#<br />
| ?Feature product manager#<br />
| ?Feature theme#<br />
| mainlabel=-<br />
| sort=Feature priority,Feature stage<br />
| format=template<br />
| limit=500<br />
| template=FeatureListTable<br />
}}<br />
</table><br />
<br />
=Ideas Not Yet Awesome Enough=<br />
Apparently these ideas are not yet great enough to merit feature pages. If you disagree, you can [[Features/Create new | create a new feature page]] for it! Just make sure to put "Security" in the primary or secondary roadmap field.<br />
<br />
{|class=wikitable<br />
|-<br />
! Item <br />
! Owner<br />
|-<br />
| [https://wiki.mozilla.org/NPAPI:Pepper2 Plugin sandboxing]<br> <br />
| <br><br />
|-<br />
| [https://groups.google.com/group/mozilla.dev.security/browse_thread/thread/f8afac1eef7cb4cd/b570280627c3dca8 Effective certificate revocation and management]<br> <br />
| <br><br />
|-<br />
| javascript: and data: handling in URL bar and chrome <br />
| <br><br />
|-<br />
| DLL&nbsp;whitelisting by name or signature<br> <br />
| <br><br />
|-<br />
| Track "Application Reputation"<br> <br />
| <br><br />
|-<br />
| Prune dead and dying code<br> <br />
| <br><br />
|-<br />
| Malloc should be infallible<br> <br />
| <br><br />
|-<br />
| TLS&nbsp;1.2 support<br> <br />
| <br><br />
|-<br />
| Eviltraps meta-bug (prevents users from leaving a page)<br> <br />
| <br><br />
|-<br />
| Notify user of malware in their crash signatures<br> <br />
| <br><br />
|-<br />
| Expose HSTS&nbsp;and other security browser state to plugins (NPAPI)<br> <br />
| <br><br />
|-<br />
| Ignore autocomplete="off" for password fields<br />
| <br><br />
|-<br />
| UX security experiment <br />
| <br><br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=663566 Content Security Policy revisions]<br />
| Brandon Sterne<br />
|-<br />
| CSRF&nbsp;mitigations <br />
| <br><br />
|-<br />
| Clickjacking mitigations <br />
| <br />
|-<br />
| X-Content-Type-Options <br />
| <br />
|-<br />
| toStaticHTML <br />
| <br />
|-<br />
| Block DLLs without ASLR <br />
| <br />
|-<br />
| Force ASLR or similar mitigations (EMET) <br />
| <br />
|}<br />
<br />
<br><br />
<br />
=Related Info=<br />
<br />
Links to implementation plan and progress: <br />
<br />
*[[Firefox/Flight Tracking]] <br />
*[[Firefox/Features]]<br />
<br />
Inputs into the security roadmap:<br />
<br />
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=sw%3A%22sg%3Awant%22 sg:want bugs] that are both important and complex<br />
<br />
[[Category:Roadmaps]]</div>Jesse