On Mon, Sep 17, 2018 at 3:54 PM, Jones, Bruce E <bruce.e.jones@intel.com> wrote:
I have updated our draft Governance document based on feedback from the PTG. Please review and send me any feedback you have.
I made a minor formatting change to reduce the emphasis on company affiliation in the initial TSC membership and decided I wanted to do more for clarity without changing the intent. I will propose the changes here to include some rationale initially before further editing the wiki:
We are actively recruiting for additional Technical Steering Committee members
Strike this, it does not feel appropriate for a governance doucment
In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote.
s/will be/is/.. Should use 'is' in both places in that sentence.
In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. In that election, the other initial TSC members from Wind River and Intel will be opened for election.
Strike the last sentence above, it is redundant, suggest replace with: At that time all initially appointed TSC terms will have been replaced by elected terms.
TSC elections will continue on this staggered cycle (3 seats and 4 seats) every six months in order to allow new leaders to rise up and ensure some consistency across the terms. TSC members will serve at least one year terms after the initial bootstrapping phase. There are no term limits, but in order to encourage diversity, no more than 2 of the 7 seats can be filled by any one organization.
Suggest alternative: TSC Elections will continue on a staggered six month cycle (3 seats and 4 seats) in order to ensure consistency across terms while allowing new leaders to begin to serve. There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time. For clarity, here is the rewritten paragraph: In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. At that time all initially appointed TSC terms will have been replaced by elected terms. TSC Elections will continue on a staggered six month cycle (3 seats and 4 seats) in order to ensure consistency across terms while allowing new leaders to begin to serve. There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time.
The Technical Steering Committee will meet regularly in an open forum with times and locations published in community channels. The Technical Steering Committee can elect a Chair at its discretion. Meetings with be hosted and facilitated by the OpenStack Foundation.
The meeting facillitation and hosting doesn't seem like something to be codified in governance?
Voting within the TSC requires a quorum of 5 members present. In the initial phase when the TSC does not have 5 members, a quorum will be 4 members. TSC members should seek consensus on most technical issues but if needed they can be resolved through a simple majority vote. Voting to create a new or archive an inactive StarlingX sub-project or to change the project's formal Governance document requires a 2/3rds super-majority.
How about this: A quorum for the TSC requires more than half of the members. (When the TSC membership is an even number, this means half + 1.) The TSC should seek consensus on issues and decisions however a simple majority vote shall be sufficient for most resolutions. Certain resolutions, specifically changing the project formal governance (including this document) and changes to project structure (adding or removing a sub-project) require a two-thirds majority vote. ((If there are more super-majority things we need to list them here)) dt -- Dean Troyer dtroyer@gmail.com