Project Configuration Presentation
Registering a project in Launchpad should be as lightweight as possible, requiring the user to provide the minimal amount of information to get the project up and running enough to perform the initial task at hand. After that first effort there are many aspects of the project that still need to be specified for it to be a completely specified project. The maintainer of the project must be shown which parts are not yet specified and provide links to various configuration pages. The maintainer should be able to tell at a glance from the project index page how far along the project configuration is and the tasks remaining.
As a $PERSON
I want $FEATURE
so that $BENEFIT
As a $PERSON
I want $FEATURE
so that $BENEFIT
As a $PERSON
I want $FEATURE
so that $BENEFIT
Consider clarifying the feature by describing what it is not?
Link this from LEP
Rationale
Why are we doing this now?
What value does this give our users? Which users?
Stakeholders
Who really cares about this feature? When did you last talk to them?
Constraints
What MUST the new behaviour provide?
What MUST it not do?
Subfeatures
Other LaunchpadEnhancementProposals that form a part of this one.
Workflows
What are the workflows for this feature? Provide mockups for each workflow.
You do not have to get the mockups and workflows right at this point. In fact, it is better to have several alternatives, delaying deciding on the final set of workflows until the last responsible moment.
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
Put everything else here. Better out than in.