Preparation for Postponing 2.0 features but providing a converged HUD service
This blueprint outlines the work items to land a converged HUD service (the backend) and pausing the HUD 2.0 APIs or any further HUD feature development for time being. Reason for this is that it's not fully clear yet whether HUD will be part of first phone release or not.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Antti Kaijanmäki
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Ted Gould
Related branches
Related bugs
Sprints
Whiteboard
This blueprint is a PROPOSAL outlining the work items for cracefully postponing the HUD 2.0 features in case the HUD might be left out from the first phablet release.
phablet hud-service would be merged to HUD trunk to get a single unified code base.
Note:
This blueprint assumes that the HUD will be removed from the phablet image completely and reintroduced when the postponed features are implemented.
https:/
Acceptance Criteria:
- nux HUD UI does not regress on the desktop
- possible bit-rot on the postponed components does not affect other parts of the system like the Shell
Work Items
Work items:
[ted] Provide support for Unity-Compiz (2d): DONE
[ted] Architecture documentation (2d): INPROGRESS
[ted] Merge phablet HUD to trunk (3d): TODO
[pete-woods] merge cmake branch (1d): INPROGRESS
[pete-woods] merge test-coverage branches (1d): INPROGRESS
[kaijanmaki] Remove HUD integration from the phablet applications (2d): TODO
[kaijanmaki] disable HUD in the shell (3d): TODO
[kaijanmaki] mark libhud-qt branches experimental, communicate with the stakeholders (SDK, phablet team) about libhud-qt being postponed (1d): TODO
