ChoiceOfBrowser
|
⇤ ← Revision 1 as of 2007-10-29 21:41:50
Size: 2819
Comment: Creating spec page for UDS Boston BOF
|
Size: 2307
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = PLACEHOLDER FOR UDS-BOSTON SPEC = * '''This page is currently a placeholder !''' * '''Action:''' Spec information to be populated by Richard : Tue Oct 30 = PLACEHOLDER FOR UDS-BOSTON SPEC = |
|
| Line 14: | Line 6: |
| * '''Packages affected''': | * '''Packages affected''': classmate-desktop, epiphany, firefox-3.0 |
| Line 18: | Line 10: |
| This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. | The Firefox 2.0 version behaves very non-performant on the ClassmatePC architecture, it takes up to 1.5min to start and uses lots of ram. Results from tests with the current Firefox 3.0 package showed that it starts pretty much instantly and that its memory usage is a lot lower than the memory usage of Firefox 2.0 on the ClassmatePC. Sice it is not clear if Firefox 3.0 will be ready in time for the hardy release, other xulrunner or webkit based browsers should be reviewed on the ClassmatePC with focus on their performance and memory usage. |
| Line 22: | Line 14: |
| This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) | The ClassmatePC image includes $BROWSER |
| Line 24: | Line 16: |
| It is mandatory. | (where $BROWSER has to be replaced with the actual choosen one) |
| Line 28: | Line 20: |
| This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. | Starting firefox 2.0 on a ClassmatePC takes way to long, memory usage is way to high. |
| Line 32: | Line 24: |
| == Assumptions == | Fred wants to browse some webpages on his ClassmatePC, he clicks the webbrowser icon on the panel, his mouse pointer indicates the app is starting and it actually starts before the pointer turns back to normal state. Fred is able to have multiple webpages open and his system doesnt run out of ram. |
| Line 36: | Line 28: |
| You can have subsections that better describe specific parts of the issue. | Test all the available browser options and front/backend combinations we have in ubuntu to determine the most performant option. ship the seleced browser of choice. This spec gets obsolete if Firefox 3.0 is ready in time for the hardy release, else another stable browser without the performance limitations of Firefox 2.0 has to be chosen. |
| Line 40: | Line 33: |
| This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === UI Changes === Should cover changes required to the UI, or specific UI that is required to implement this === Code Changes === Code changes should include an overview of what needs to change, and in some cases even the specific details. === Migration === Include: * data migration, if any * redirects from old URLs to new ones, if any * how users will be pointed to the new way of doing things, if necessary. |
Add the chosen browser to the classmate-desktop seed. |
| Line 59: | Line 37: |
| It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release. This need not be added or completed until the specification is nearing beta. |
Open a browser on a hardy ClassmatePC desktop, check that it starts before the pointers startup notification ends, open up to 4 tabs with websites and make sure the system is still responsive in that scenario. |
| Line 65: | Line 41: |
| This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. == BoF agenda and discussion == Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. |
Test available browser and backend combinations on the ClassmatePC |
Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad Entry: classmatepc-choice-of-browser
Packages affected: classmate-desktop, epiphany, firefox-3.0
Summary
The Firefox 2.0 version behaves very non-performant on the ClassmatePC architecture, it takes up to 1.5min to start and uses lots of ram. Results from tests with the current Firefox 3.0 package showed that it starts pretty much instantly and that its memory usage is a lot lower than the memory usage of Firefox 2.0 on the ClassmatePC. Sice it is not clear if Firefox 3.0 will be ready in time for the hardy release, other xulrunner or webkit based browsers should be reviewed on the ClassmatePC with focus on their performance and memory usage.
Release Note
The ClassmatePC image includes $BROWSER
(where $BROWSER has to be replaced with the actual choosen one)
Rationale
Starting firefox 2.0 on a ClassmatePC takes way to long, memory usage is way to high.
Use Cases
Fred wants to browse some webpages on his ClassmatePC, he clicks the webbrowser icon on the panel, his mouse pointer indicates the app is starting and it actually starts before the pointer turns back to normal state. Fred is able to have multiple webpages open and his system doesnt run out of ram.
Design
Test all the available browser options and front/backend combinations we have in ubuntu to determine the most performant option. ship the seleced browser of choice. This spec gets obsolete if Firefox 3.0 is ready in time for the hardy release, else another stable browser without the performance limitations of Firefox 2.0 has to be chosen.
Implementation
Add the chosen browser to the classmate-desktop seed.
Test/Demo Plan
Open a browser on a hardy ClassmatePC desktop, check that it starts before the pointers startup notification ends, open up to 4 tabs with websites and make sure the system is still responsive in that scenario.
Outstanding Issues
Test available browser and backend combinations on the ClassmatePC
Education/UDS-Boston/ClassmatePC/ChoiceOfBrowser (last edited 2008-08-06 16:29:21 by localhost)