Making it *fun* to contribute to bzr core

[Ian Clatworthy]

In case anyone missed Martin's email about "patch pilots", we've had a 
long discussion today at the Bazaar sprint about improving the patch 
submission experience. The short summary is this: we all agree fixing 
this problem is *hugely* important and we're changing our process 
accordingly.

The two big problems we want to solve are:

1. Patches are taking too long to land (or never land), making
    the process a disheartening one.

2. We're been putting the burden for "perfection" back on
    the contributor, e.g. they have needed to learn all about
    our test suite and how to write tests to get (otherwise good)
    patches through the process.

 From now on, community submissions will be adopted by a core member who 
will "pilot" the patch. In practical terms, the pilot will either reject 
it and explain why or agree it's a good thing and get it landed. We 
still want community members to write tests if they can. If they can't, 
we'll do it for them, teaching them if they are interested. See Martin's 
email for further details (until we get the process documentation updated).

Like any process change, we'll undoubtedly learn as we go about how to 
make things better. Please let us know how we're going. If you want 
fixes made to the core and you've been reluctant because of past 
experience, please fire up your engines, crank out those merge proposals 
and put our new process to the test!

Ian C.