KubuntuDocs

Differences between revisions 5 and 6
Revision 5 as of 2005-10-19 13:38:27
Size: 2437
Editor: mail
Comment: More thoughts on this
Revision 6 as of 2005-10-20 02:24:54
Size: 2439
Editor: 69-87-142-85
Comment: nominated myself for second on this
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * People: NeedsLead, NeedsSecond  * People: NeedsLead, JonathanJesse

Summary

What documents will we be focusing on for DapperDrake?

  • Let's finish the Kubuntu Starter Guide and incorporate it to the milestones
  • Also check on the content of KDE docs, maybe some of the stuff needed for a User Guide are already there and just needs a few edits and screenshots.
  • Not so much on server docs

Rationale

The documents for BreezyBadger where thrown together at the last minute. There was not a real plan and part of it was my fault. Some of us were working on docs that are now scheduled for Dapper, instead of things that were going to get released in Breezy. The About Kubuntu and Kubuntu Release Notes took a lot of last minute stuff to finish. We should not repeat this in Dapper as it is going to be supported for 5 years.

Use cases

Scope

Goal is three important documents to updated and finsihed. The Kubuntu FAQ Guide, Kuubuntu Release Notes, and the Userguide should be finished before release. Also any updates and changes to the docs during the 5 year support window should be packaged and updatable via Adept or apt-get.

Design

Implementation

As I worked w/ JonathanRiddell on the Kubuntu Release Notes for BreezyBadger, I would like to focus on the release notes for DapperDrake. We need to work with RobertStoffers to make any changes to the FAQGuide that are Kubuntu Specific whether thru profiling or creation of new doc. The Kubuntu UserGuide is currently a work in progress and needs to be finished. Current status can be found at DocteamProjects. Screenshots and information will need to be changed and updated to reflect Dapper.

If time allows an Adept manual should be worked on as well, unless there already is one upstream. The Kynaptic guide will be replaced by this document.

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion