SmartPhone Code Transition

Program Description

A team led by Gregor Wagner and Fabrice Desré conducted the analysis necessary to determine what changes should be made and the level of effort those changes would take to move us closer to being able to run on generic gecko to reduce its maintenance cost. The results of the analysis has led to the final version of the Firefox OS Code Transition Plan, and the plan has been approved to proceed with the following as its primary goal:

To transition the Firefox OS for smartphone code to reduce its maintenance cost and get it into a state where the volunteer contributor community can successfully take the lead and ownership for the future direction of the b2g for smartphone code Description

Requirements:

There were four areas analyzed for inclusion in the code transition plan (shown below with their owners):

• Packaged apps (b2g features), perhaps the most important piece (Fabrice)
• Removal of security model and wait for platform team to give us new security layer. (Paul)
• Process model - abandon ours and move to the one desktop has (Kan-Ru)
• Graphics/media (Kan-Ru)

It was decided that the focus of the transition would be on the first two of these areas. In addition, an effort has begun to reduce code duplication by merging the 2 separate system apps.

User Stories and Acceptance Criteria

Title	BUG ID	User story	Acceptance Criteria
Title Goes Here	Bug ID	User Story 1	Acceptance Criteria 1
	Bug ID	User Story 2	Acceptance Criteria 2
Help/Onboarding	Bug ID	User Story 3	Acceptance Criteria 3

Program Status

Milestone	Date	Status
Milestone 1		ON TARGET
Milestone 2		CHALLENGED
Milestone 3		AT RISK

Status Key

Color	Status	Key
	On Target	The project or deliverable is expected to meet its due date.
	Challenged	The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track.
	At Risk or Late	The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late.
	Done	The project or deliverable has been completed.
	On Hold	The project or deliverable has been placed on hold.

---

Program Timeline

---

MVP Scope

Querying by 2.6+ features

(please add correct bug tracking number)

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

---

Dependency Tracking

---

Detailed Program Plan

Action Item	Engineering Owner	QA Owner	UX Owner	Bugzilla ID	Planned Done	Actual Done

---

Program Stakeholders

Role	Name	IRC
EPM
EM
PM
TL
UX
QA

• EPM = Engineering Program Manager
• EM = Engineering Manager
• PM = Product Manager
• TL = Tech Lead
• UX = User Experience
• QA = Quality Assurance

---

---