Comment 73 for bug 240067

We'd still need a bunch of work do do even plain html:
 - There are security implications with taking raw html and serving it inside the launchpad.net domain - javascript there could trivially access a users authentication cookie and hand that off to a malicious site :(. We've resisted having plain sites in the past due to concerns about being used to host porn or whatnot - but I think we could address that satisfactorily.
 - We'd need to handle renames and private projects gracefully

Doing something like github does with e.g. ReST and README from the trunk branch would be pretty awesome too.

I don't think a wiki is /all that/ much more work than a plain static site, or doing ReST on the fly from the bzr trunk. Tim Penhey's wikkid project is pretty awesome too, and he's had this bug in mind in his development of that.

I think what we need to do is wait for someone to step up and work on this - *at that point* do the design work to evaluation wikis vs static sites vs rest/markdown from source control.

Canonical itself will step up and work on this at some future date - the key consideration for us at the moment is our current in-progress work:
 - performance [our 99th percentile render time is 2.5 seconds - for LP to feel fast we need that to be consistently below 1 second]
 - agility - it takes us too long to change things in LP, and fixing that requires some considerable investment
 - message sharing for translations with upstream/downstream
 - better bug subscriptions - a *massive* source of user frustration
 - derivative distributions - we're making it easier for people to remix Ubuntu, and for Ubuntu to remix Debian.

When we've finished those 5 things we'll reevaluate all the feature requests we have and pick new things to work on.