Sensible Project Structure
Registered by
Dylan McCall
Ubiquity-Slideshow needs a sensible project structure that encourages efficiency and separation of the different slideshow efforts.
We need a system that keeps the core project - developing and documenting Open Projector, integrating it with Ubiquity - to its own devices. Slideshows themselves should be entirely unique efforts with no concern about this project's own timeline.
This requires enhancement of the existing design to encourage easier integration.
Blueprint information
- Status:
- Not started
- Approver:
- Dylan McCall
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
On the bright side, Ubiquity works as a part of the name for this project, so when the reason for it being called ubiquity-slideshow comes into question, I can quite easily claim it was all part of a grander plan...
-Dylan
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
