On 06/03/2015 12:32 PM, Boris Pavlovic wrote:
Guys,
One more time it's NOT about reputation and it's NOT about believing
somebody.
It's about human nature. We are all making mistakes.
And if we do, we can always revert a patch.
System that checks can code review merge patch is just extra check
to avoid unintentional mistakes of core reviewers and make things
self organized.
I suggest you start with trusting these leutnants and go forward with a
social contract - and if that really does not work at all, let's discuss
other options.
For the security guide, we have a social contract: It needs two +2s as
usual - but one +2 from a security team member, one from a Documentation
team member. This social contract works for our small group just fine
and I encourage you to try it out,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
