Specific documentation improvements for the 'Precise' development cycle

Registered by Scott Lavender on 2011-11-10

Ubuntu Studio needs to develop and maintain a basic infrastructure of documentation to help reduce the work load on the contributors and developers. This would include developing and maintaining a QA ISO testing wiki page and a 'Contribute to Ubuntu Studio Development' wiki page.

Blueprint information

Status:
Complete
Approver:
Scott Lavender
Priority:
Medium
Drafter:
Scott Lavender
Direction:
Approved
Assignee:
Ubuntu Studio Development
Definition:
Approved
Series goal:
Accepted for precise
Implementation:
Implemented
Milestone target:
None
Started by
Scott Lavender on 2011-11-10
Completed by
Scott Lavender on 2011-11-24

Related branches

Sprints

Whiteboard

Work items:
[slavender] qa - determine which information should be on the qa iso testing page: DONE
[slavender] qa - develop the page: DONE
[slavender] qa - review it for usability: DONE
[slavender] qa - email users: DONE
[slavender] contribute - create a wiki page: DONE
[slavender] contribute - email users: DONE

notes:
The QA ISO testing wiki page should do the following:
 * explain and provide rationale of QA ISO testing
 * contrast QA ISO (i.e. milestone) testing against 'dailies' testing
 * provide link to current schedule
 * provide link to QA ISO test report page
 * explain available methodologies to test images (i.e. VM versus bare metal)
 * provide link to bug reporting explanation

The 'contribute to ubuntu studio development' wiki page should do the following:
 * provide a list of tasks that non-developers can accomplish
 * provide enough explanation that the contributor can at least understand the goal and can research further
 * provide contact information
 * provide any required resource links

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.