Electrolysis/Short-Term Goals: Difference between revisions
(goals) |
(e10s short-term goals, more!) |
||
| Line 1: | Line 1: | ||
= Get Firefox Starting Up = | == Get Firefox Starting Up == | ||
Get Firefox to start up and browse, so that the accessibility, devtools, and perhaps Jetpack SDK teams can work on dependencies. | Get Firefox to start up and browse, so that the accessibility, devtools, and perhaps Jetpack SDK teams can work on dependencies. | ||
| Line 7: | Line 7: | ||
Status: patches posted, see [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe his status report] | Status: patches posted, see [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe his status report] | ||
= Dynamic Instrumentation for Chrome/Content Interaction = | == Dynamic Instrumentation for Chrome/Content Interaction == | ||
We want to identify: | We want to identify: | ||
| Line 29: | Line 29: | ||
Goal date: 30-June | Goal date: 30-June | ||
= Static Analysis of Chrome/Content Interaction = | == 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 | 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 | ||
| Line 35: | Line 35: | ||
Owner: Dave Herman | Owner: Dave Herman | ||
== Subgoal 1: Write Testcase code == | === Subgoal 1: Write Testcase code === | ||
Write some testcase extensions which the tool must analyze. | Write some testcase extensions which the tool must analyze. | ||
| Line 41: | Line 41: | ||
Goal date: 23-June | Goal date: 23-June | ||
== Subgoal 2: Analyze and produce reports on one bad pattern == | === Subgoal 2: Analyze and produce reports on one bad pattern === | ||
Goal date: 7-July | Goal date: 7-July | ||
= Identify Work Items for Multiple Content Processes = | == 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. | We have identified multiple content processes as a requirement for desktop Firefox. Identify and find owners for the work required for multiple content processes. | ||
| Line 52: | Line 52: | ||
Goal Date: 23-June | Goal Date: 23-June | ||
= Extension | == Extension Usage Metrics == | ||
Identify which extensions must be compatible with content processes in order to reach 80% of Firefox users. | Identify which extensions must be compatible with content processes in order to reach 80% of Firefox users. | ||
Owner: ? | 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: Kevin Dangoor | |||
Goal Date: 7-July | Goal Date: 7-July | ||
Revision as of 21:24, 16 June 2011
Get Firefox Starting Up
Get Firefox to start up and browse, so that the accessibility, devtools, and perhaps Jetpack SDK teams can work on dependencies.
Owner: Felipe Gomes Goal date: 23-June (Wednesday) Status: patches posted, see 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 Willcoxen 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: Kevin Dangoor Goal Date: 7-July