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. -- Should have a document for external contributors to know what they need to do to get a branch landed https://bugs.launchpad.net/bugs/535150 You received this bug notification because you are a member of Launchpad Documentation Team, which is subscribed to Launchpad Documentation. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-doc Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-doc More help : https://help.launchpad.net/ListHelp
