Voting foo as PQM policy? [was: attn folk doing reviews.]

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
| At martins request I'm setting up PQM for bzr.dev, so the committer term
| will imply 'can commit straight to bzr.dev' - and I think its
| appropriate to have the physical access, and the trust to not commit
| silly things linked.

I gave a presentation on bzr at the local Python User Group tonight, and
there were a couple of interesting suggestions.  Here's the first:

Review interface as pqm policy
==============================
It might be nice if the PQM policy for bzr allowed anyone to submit
merges.  The merges would be logged.  They could generate emails to
committers.  They could also update a tracking page.

However, they would only be processed if the required votes were submitted.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD1v020F+nu1YWqI0RAsR7AJ9/ynJStiP1ilvq4THgNkoV3nDsNACfckqZ
7xc0paq7Xg8n1GnctF8y9bM=
=aF74
-----END PGP SIGNATURE-----