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.
System that checks can code review merge patch is just extra check
to avoid unintentional mistakes of core reviewers and make things
self organized.
Best regards,
Boris Pavlovic
On Wed, Jun 3, 2015 at 12:55 PM, Alexis Lee <alex...@hp.com> wrote:
> Robert Collins said on Wed, Jun 03, 2015 at 11:12:35AM +1200:
> > So I'd like us to really get our heads around the idea that folk are
> > able to make promises ('I will only commit changes relevant to the DB
> > abstraction/transaction management') and honour them. And if they
> > don't - well, remove their access. *even with* CD in the picture,
> > thats a wholly acceptable risk IMO.
>
> +1, optimism about promises is the solution. The reputational cost of
> violating such a promise is high, given what a small world open source
> can turn out to be.
>
>
> Alexis
> --
> Nova Engineer, HP Cloud. AKA lealexis, lxsli.
>
> __________________________________________________________________________
> 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
>
__________________________________________________________________________
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
