Specification
|
Size: 2427
Comment:
|
Size: 2028
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 19: | Line 19: |
| This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) It is mandatory. |
This section should include a paragraph describing the end-user impact of this change. |
| Line 25: | Line 23: |
| This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. | https://wiki.ubuntu.com/Learning/Rationale |
| Line 33: | Line 31: |
| You can have subsections that better describe specific parts of the issue. |
|
| Line 36: | Line 32: |
This section should describe a plan of action (the "how") to implement the changes discussed. |
|
| Line 46: | Line 39: |
| Managing the server, council for project/project board, who moderates, and how is the moderation structured. |
Web: learn.ubuntu.com (coming soon)
- Launchpad: ~ubuntu-learning IRC: #ubuntu-learning @ irc.freenode.net IRC-based courses in Classroom
Draft
Summary
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.
Release Note
This section should include a paragraph describing the end-user impact of this change.
Rationale
https://wiki.ubuntu.com/Learning/Rationale
User stories
Assumptions
Design
Implementation
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Management and Moderation
Managing the server, council for project/project board, who moderates, and how is the moderation structured.
Release Marketing Plan
How will the project be marketed when it is ready?
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
Individual Notes
Individual contributors can please enter what their rationale for the project is.
Who |
Rationale |
Discussion
Please add comments here as we build the rationale of the project.
Learning/Specification (last edited 2009-05-19 04:13:46 by pc012856)