Merge lp://qastaging/~mars/tarmac/contributor-instructions into lp://qastaging/tarmac

Actually, item #6 is probably ok to remove from here. As rockstar is the only one who can actually mark the proposals as Approved, since he is the branch owner.

Hi Maris. Thanks for taking the time to note this in the HACKING document. Sometimes I forget that those processes need documentation too.

I think a better solution for this would be to link to Launchpad's help documentation on merge proposals. Mentioning "bzr send" at all is a huge mistake, because it's a pretty advanced method, and one that I don't even use (especially with lp-propose now anyway). Leveraging Launchpad's documentation means that it only gets out of date in one place, instead of two. :)

Here are some updated instructions - I left in the first three about committing and pushing code, linked to the Launchpad help docs for creating the merge proposal and reviewing the code, and changed the last step to be a bit more descriptive and hopefully helpful.

To get your patch into the Tarmac mainline, do the following:

1. Check your changes into a bzr branch of lp:tarmac

2. Push your changes: ``bzr push lp:~myuser/tarmac/my-descriptive-patch``

3. Follow the Launchpad help instructions to create a new merge proposal
   containing your changes: https://help.launchpad.net/Code/Review

4. The Tarmac core developers will review your code and provide feedback.
   When your code is approved they will commit it for you.