Dean, thank you for the feedback. The current text (which we edited live at the call this week) says: "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. In the event that 3 people from one organization are elected to the TSC in one election, the person with the lowest vote count among the 3 is skipped and the next candidate is elected. Any other case of more than 2 people per company on the TSC shall be addressed at the latest at the next scheduled election." I think this addresses your concerns. brucej -----Original Message----- From: Thierry Carrez [mailto:thierry@openstack.org] Sent: Thursday, September 20, 2018 2:41 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: Updated governance doc on the wiki Jones, Bruce E wrote:
Dean, thank you for this feedback. I have made all of the changes you suggested to the Governance wiki page.
Additional feedback on https://wiki.openstack.org/wiki/Starlingx/Initial_Governance is welcome!
Great work there (especially on the Project Lead rewritten paragraph)! My only comment would be around the "no single organization may be represented by more than two seats at any given time" rule for TSC and how that would work in practice. At election time it's pretty simple -- if the elected person would break the rule, just skip them and take the next ranked person. It's a bit more tricky in case of job changes triggering the rule. Like some TSC member X moving to a company that already has 2 members. It would be a good idea to describe how to handle that (likely) situation so that you already know how to handle it. Options would be for that person to immediately lose their TSC seat (to be replaced by next in line in the election results ?), or to keep it until the next election round, or to keep it but not have a formal vote until the next election... The mention that "Individuals are expected to continue to support the project in the event of career changes unless they notify the project that they are resigning their position" tend to point to one of the latter options, but it's a bit unclear. In my experience, we tend to overthink those rules -- I think it would be safe to just wait until the next election to "fix" the situation. Those happen often enough anyway, and someone changing companies and continuing to work on the project is a lot more likely to wear their "project hat" rather than their "new company hat" anyway. So my suggestion would be to replace "no single organization may be represented by more than two seats at any given time" by "no single organization may be represented by more than two seats after any election round". -- Thierry Carrez (ttx) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss