[Cryptography-dev] Code review policy

[Hynek Schlawack]

> Basically, crypto is scary, openssl is a footgun, and humans are fallible. Therefore I think we want have a pretty strict policy that everything needs to go through a PR *and be merged by someone else*. Anyone have a problem with that?
> 
> I don't even need any of those arguments to think code review is great.

Aye.  We’re trying nothing less than giving canonical crypto tools to the Python community.  Strict is good.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20130802/99569c3c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20130802/99569c3c/attachment.pgp>