Electrolysis/Short-Term Goals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(clear the page of old information)
 
(40 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Get Firefox Starting Up ==
= Current Goals =


Get Firefox to start up and browse, so that the accessibility, devtools, and perhaps Jetpack SDK teams can work on dependencies.
The work on content processes has been suspended so that we can focus on more immediate responsiveness efforts. See [http://lawrencemandel.com/2011/11/15/update-on-multi-process-firefox-electrolysis-development/ lmandels' blog post] for details.
 
Owner: Felipe Gomes
Goal date: 23-June (Wednesday)
Status: patches posted, see [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe his status report]
 
== Dynamic Instrumentation for Chrome/Content Interaction ==
 
We want to identify:
 
* non message-manager scripts
* which touch a "content object"
* or implement nsIWebProgressListener
 
Definitions:
 
Non message-manager script is any chrome script that isn't run through nsIChromeFrameMessageManager.loadFrameScript.
 
Content objects are at least the following:
 
* Any DOM object (window, document, or node)
* Docshell or docshell derivative
* nsIWebProgress
* nsIDOMWindowUtils
 
Owner: Drew Willcoxon
Goal date: 30-June
 
== Static Analysis of Chrome/Content Interaction ==
 
Parallel to the dynamic analysis, we need to be able to statically identify code patterns which may require rewriting (mainly in long-tail extensions). This will be an ongoing project, but we need to set intermediate goals (obvious patterns that we should start flagging). Refinement will depend on analysis gathered in the dynamic phase
 
Owner: Dave Herman
 
=== Subgoal 1: Write Testcase code ===
 
Write some testcase extensions which the tool must analyze.
 
Goal date: 23-June
 
=== Subgoal 2: Analyze and produce reports on one bad pattern ===
 
Goal date: 7-July
 
== Identify Work Items for Multiple Content Processes ==
 
We have identified multiple content processes as a requirement for desktop Firefox. Identify and find owners for the work required for multiple content processes.
 
Owner: Benjamin Smedberg
Goal Date: 23-June
 
== Extension Usage Metrics ==
 
Identify which extensions must be compatible with content processes in order to reach 80% of Firefox users.
 
Owner: blizzard?/jorge?
Goal Date: 7-July
 
== Accessibility Engineering Plan ==
 
Identify whether the accessibility tree will need to be mirrored, or whether accessibility tools can work directly with trees in content processes.
 
Owner: David Bolter
Goal Date: 7-July
 
== Developer Tools Engineering Plan ==
 
Identify how existing in-product developer tools will be made compatible with content processes and what additional platform support is required. DOM Inspector will almost certainly require some additional platform support.
 
Owner: Rob Campbell
Goal Date: 7-July
 
== Deploy a Responsiveness Metric ==
 
Deploy a responsiveness metric which measures the average and maximum time away from the event loop.
 
Owner: Ted Mielczarek
Goal Date: TBD

Latest revision as of 21:28, 30 November 2011

Current Goals

The work on content processes has been suspended so that we can focus on more immediate responsiveness efforts. See lmandels' blog post for details.

Retrieved from "https://wiki.mozilla.org/index.php?title=Electrolysis/Short-Term_Goals&oldid=374722"