Mallard Plan: what's needed

[Kyle Nitzsche]

I think:
* Lucid LTS is the wrong time for Mallard.
* We need an ubuntu-docs system guide high-level requirements doc/wiki
* We need a document/blueprint that shows how mallard relates to the 
requirements and that provides a plan for implementation that includes: 
rationale, mallard transition project structure, building, packaging, 
localization, source transition to mallard, testing, release integration 
with ubuntu release cycles, and possibly community training (for writers)
* There should be a period of review > comments > modifications > final 
version > decision (go/no go)

Regarding project structure, I propose:
 * a new LP project "Ubuntu-docs to Mallard"
 * used to develop, test, finalize the build system and ultimately to 
include the source
 * code in bzr
 * dedicate bug system
 * a ppa for ubuntu-docs pkg (I think it will be pkgS, because we should 
consider modularizing the docs packages to facilitate customizability)

Having a dedicated project for the transition enables people to 
participate and track what's happening. code in a known place. bugs 
logged. milestones, ppa for testing dev versions, etc.

I think this ground work should be done in preparation for the next UDS. 
Such important changes are appropriate for UDS. Following these (usual) 
steps will only increase docs credibility and profile in the ubuntu 
community.

cheers,
Kyle