blueprints do not permit full preparation / presentation of specifications - relies on external wiki

[Harald Sitter]

While outside specification writing (in wikis) clearly has advantages in terms of group editability, it also has a large disadvantage in that it makes the data virtually unusable and unfindable and eventually rot because of the former two. Especially the latter is a shame when we are talking about technical specifications such as the Ubuntu upgrade hooks. It also prevents from doing enhanced queries on the specification data.

Take the following page for an example:
https://wiki.kubuntu.org/KubuntuLucidSpecs

It largely replicates informations form launchpad blueprints, so do the individual spec pages. Also, the page does not provide any in-depth information on what the specs might be about.

So say you want to know about all Kubuntu specs targeted for Kubuntu's Lucid release. You might go to google, and possibly, but very unlikely, find above page. You go there and have to at least take a glimps at each spec to know what they are about. Each of these things are considerable easy to do if all data was kept in launchpad rather than outsourced to some random wiki, which might not even be openid enabled, eventually forcing someone who already got an launchpad account to get yet another account just so she can contribute in the blueprinting process.

Please enable full specifications inside LP blueprints. Maybe split into introductional description (which could be the regular blueprint description already), the actual spec and tags (as seen with bugs, just in a more moderated manner). Using these 3 information you can already build large amounts of more useful data representations than what is currently available.
For example one might do a query on all blueprints in Ubuntu, having "Kubuntu" in their title and were discussed at the sprint "uds-l", this would be exactly what above mentioned wiki page does right now. Upon that query you'd just need to stack some nice visual presentation that shows the first 150 words from the introduction and the Kubuntu team would not have to make such ugly unorganized, unfindable... wiki pages :)

Thanks for considering.