Juju GUI

Registered by Kapil Thangavelu

Rationale:
Response has been very positive since the announcement of the GUI at ODS (Oct'12). User feedback has also been collected. Thus, there is a need to analyze, and define improvements needed by the GUI in the r-cycle.

Goal:
Analyze user feedback and feature requests. Based of analysis implement needed improvements.

Blueprint information

Status:
Not started
Approver:
Antonio Rosales
Priority:
High
Drafter:
Ubuntu Server
Direction:
Approved
Assignee:
Kapil Thangavelu
Definition:
Discussion
Series goal:
Accepted for raring
Implementation:
Unknown
Milestone target:
milestone icon ubuntu-13.04

Sprints

Whiteboard

## Feedback:
Kapil, can you add some WI please? Thanks.

Notes from UDS-R Pad:

Feature requests
[] Layout shared within environment
[] Manual Layout (with automatic components)
[] Nicer staging site url
[] Deploy story (charm - has prereqs, etc.)
[] Charm upgrade
[] Custom charms/local charms (also, new services from existing local charms)
[] Indicate on service config when value is different then default
[] Webapplication desktop integration
[] Discoverable ux? (re: longclick)
[] Read-only view
[] Staging mode with commit?
[] Concurrent editing (with command line, auto-scaling, etc)?
[] import/export
[] Logging

WI
[] Staging on a more consumable url
[] Public mailing list (weekly retrospectives, dev notes)
[] Hangouts on air?

Notes
- Meetings of devops should center around looking at the gui - not just for sales - use it as a noc view
- uistage updates every 15 from trunk
- Feedback via bugs launchpad.net/juju-gui

--- User Stories ---

--- Risks ---

--- Test Plans ---

--- Release Note ---

--- Blog Post ---

(Needs spec and WI definition) -[a.rosales; 12-DEC-2012]

(?)

Work Items

Work items:
[arosales] Public mailing list (weekly retrospectives, dev notes): DONE
[gary] Nicer staging site url: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.