Re: [openstack-dev] [kolla] our 3 voting processes in detail
Thanks for the suggestion. I think it merits further work to write our policies down in git. I wanted to get this out a little more quickly since these are our foundational policies and there is some confusion among the cores about them - even though we have been using them for the better part of 2+ years :) I'll see what I can do to get our policies put into our documentation. Regards, -steve On 6/17/16, 7:36 PM, "Gerard Braad" wrote: >On Sat, Jun 18, 2016 at 9:49 AM, Assaf Muller wrote: >> I would recommend in-tree policies .rsts instead of Wiki entries. >> There is a higher cost to make changes, but they have to go through >> the review process, and the content will survive as long as the .git >> repo does. > >Good point. The higher cost is probably even desirable. +1 > >__ >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
Re: [openstack-dev] [kolla] our 3 voting processes in detail
On Sat, Jun 18, 2016 at 9:49 AM, Assaf Muller wrote: > I would recommend in-tree policies .rsts instead of Wiki entries. > There is a higher cost to make changes, but they have to go through > the review process, and the content will survive as long as the .git > repo does. Good point. The higher cost is probably even desirable. +1 __ 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
Re: [openstack-dev] [kolla] our 3 voting processes in detail
On Fri, Jun 17, 2016 at 9:41 PM, Gerard Braad wrote: > Thanks Steve, > > > Very useful. Would be great if for future reference we would only need > to pint people to an URL on the Wiki for instance... what do you > think? I would recommend in-tree policies .rsts instead of Wiki entries. We do that in Neutron-land and the resulting HTML is published here: http://docs.openstack.org/developer/neutron/policies/index.html There is a higher cost to make changes, but they have to go through the review process, and the content will survive as long as the .git repo does. > > regards, > > > Gerard > > __ > 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
Re: [openstack-dev] [kolla] our 3 voting processes in detail
Thanks Steve, Very useful. Would be great if for future reference we would only need to pint people to an URL on the Wiki for instance... what do you think? regards, Gerard __ 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-dev] [kolla] our 3 voting processes in detail
Hey core reviewers, I was speaking with one of the core reviewers of Kolla today who said "only you can nominate people for core reviewer". By you, he meant me :) This is absolutely not true and I'd like to set the record straight on our three voting processes we have developed over the last 3 years of the project's existence: For core reviewer nominations: If you have someone in mind you would like to propose, please contact the PTL via email or irc or cellphone or carrier pigeon. Feel free to make a short writeup about the individual's accomplishments or if you don't the PTL will. I will send it on or craft a message for the mailing list. The core reviewer nominations while originating from my email address represent a nomination from the community, not me personally. Requires majority of core reviewers to vote +1 with no veto vote within 1 week window. Voting closes early on unanimous vote or veto. For policy matters: If you want to trigger a policy change, please either send an email to the mailing list with the [kolla][vote] tag with your proposal or contact the PTL to execute the vote. Requires majority of core reviewers to vote +1 within 1 week window. No veto is permitted. Voting closes early when majority is reached. For technical specifications of a contentious nature or that are highly complex changes: Kolla uses specifications as a last resort mechanism when other forms of communication have failed. Another use of specifications is to discuss highly complex topics that touch a whole lot of Kolla. Many times after the specification is created and discussed in gerrit, it is abandoned as the review process itself sets a direction that breaks the logjam. Anyone may submit a specification for review. Requires majority of core reviewers to vote +2. There is no time window. The final majority vote may workflow the specification. No veto (A vote of -2) is permitted. NB: The reason no veto is permitted on specs or policy matters is to break logjams. Democracies operate best when there are no veto abilities. This prevents dictatorships. NB: The reason veto is permitted on core review nominations is related to how OpenStack operates and has a whole lot to do with trust. NB: If the PTL is unresponsive (Ill, on vacation for 3 months in the bahamas, whatever) please feel free to take it upon yourself to execute the actions declared above that the PTL would typically do. Regards -steve __ 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
