Should have a document for external contributors to know what they need to do to get a branch landed

Would be nice for new internal contributors too; I've been piecing together the steps on my own (pages in wiki have been helpful, but a surprising amount of the wisdom is only available via word-of-mouth.)

For external contributors, I would further suggest maybe breaking the entirety of the process up into more discrete chunks, so they could suggest changes without having to commit to following a change through for the entire process. What I'm thinking is an analogy of how it works in Ubuntu, where there are widespread contributors who supply patches on bugs, and the MOTU group of contributors who shepherd other people's patches through the remainder of the process to get into Ubuntu. I could see an analogous division of labor being worth considering for launchpad's external contributor community.

The wiki field on the project is intended to be the location of project process, specifications, and documentation. That is https://dev.launchpad.net/. We could use Launchpad like we suggest other projects to use Launchpad.

Moving this bug to launchpad-foundations. Although that'd not a perfect fit for this bug, the launchpad-documentation project is no longer active and documentation bugs should be filed against the "launchpad" project for later moving to the relevant project.

This sounds like a good idea, but from a Foundations perspective is a low priority.

Hello Fellow Developers,
Launchpad Doc team is active I will create this document and put it on the help.launchpad dev.launchpad it proper places. I will put links on here to show what I mean. There is some that will have to go on dev and the help sides.
Regards,
Leo Jackson