Could someone post a quick intro (or link) to how launchpad.net should be used? Particularly for WorldForge blueprints.
I took a quick look, but I wasn't sure how to use it. Is it mostly helpful as a registry of design/specification documents? In that case, it sounds like we could continue to put most documentation in wiki, but use launchpad as a convenient index with metadata relevant to design/specification documents, with support for design and implementation workflow.
Or are there additional features/requirements to using launchpad.net?
Yep, I think a mix between the wiki and the launchpad is best. Look at how ubuntu is using it: https://blueprints.launchpad.net/ubuntu/ The blueprints have an option for providing a link to the full spec. While the wiki is better suited for providing the info, the launchpad helps with communication and progress reporting. It also has support for dependencies.
I envisage launchpad as a more structured way of handling our information than the wiki. The wiki is great for getting things down quickly, but it becomes increasingly difficult to find stuff as no structure has been imposed. Using a blueprint entry as a reference point, linking to the wiki seems fine. Launchpad provides the structure, the wiki provides a nice easy trackable way to edit the content without having to worry too much about access and permissions.