-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 04/02/2015 03:22 AM, Sylvain Bauza wrote:
> I was originally pro giving a limited set of merge powers to > subteams for a specific codepath, but my personal experience made > me think that it can't work that way in Nova at the moment - just > because everything is intersected. > > So, yeah, before kicking-off new features, we need at least people > enough aware of the global state to give their voice on if it's > doable or not. I don't want to say it would be a clique or a gang > blessing good people or bad people, just architects that have > enough knowledge to know if it will work - or not. > > Good ideas can turn into bad implementations just because of the > existing tech debt. And there is nothing that we can avoid that, > unless we have mentors that can help us finding the right path. > > Don't get me wrong : again, it's not giving more powers to people, > it's basically stating that cores are by definition people who have > the global knowledge. It *can* work, as long as the cores hold the all-important +W. I'm sure that having your +1 on a scheduler-related patch now makes cores feel more confident that the change is correct for the scheduler, so making your vote a +2 would streamline the process. But as you correctly point out, they have a deeper knowledge of the entire project, and need to validate that the change won't adversely affect other parts, so holding the +W for cores would minimize the chance of adding to tech debt. - -- - -- Ed Leafe -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJVHVuCAAoJEKMgtcocwZqLjcwQAIOzkKTLCjWLV84bqoCJX6Ai D/zzqMCoOOYyj341lrfVM2SxkJX6+awQfe75WNo46u4nEC1CZp5EscZpbrIUIxG2 Bic5l2cjKQmvKEIyvNrAb1g3mmC50mEUscZwfvrUr4QUamwL0wNm7jkZBMVlAGMd uD2My/HRqnls/FhCMGprzTI+zeowa4KdUWuZUC5CfGZg/GFVty2/k4u0Jej5nla9 efoQ49VG3M2g+Ipxhg1sgVWvru+7E2pfCNd3lFVt+C/gwJUrQ7x36nQkOIR8OtyN j9BH5NqJ+8qDIqEvQIaI1ToaBwwNn4JK1XsKfj41wt+YFym4qS0o8/wKuup+5Syj q1m29yWZwFfFXqYoLqfqHQJ34bY3CTFS7OllXGX1KkMh7MfMffbwbPZn67ICYnoY 4Q4ed/QQOzDnzvH3MAOwVfaeNq8vL8u/x5C2rotXQmcihJrrgi5MWfATayiuNGpj Sfi++C1MDgW61I1ehFrgHcW2sQ6vvuyErA9e8mm0xPBO/o+64gL4dmqnU2U6rfTx KBR6Q9vXJXoFBvCmrFMv+F7vk+XDEUUP5uoXj8069/lXblQxZwowH4ijJql2RwlI COUsWahnKAp05F8CiMKxaIF/R7UeHslTLer7yE+dwmNTqIVF1ylj0ToOxnSXV/WK f7sPIo9aHtfZbPO+d8uV =Euob -----END PGP SIGNATURE----- __________________________________________________________________________ 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