Has this been done yet (Governance doc in stx-governance repo)? The way I understand the timeline from the last call I attended, and from talking to various people is the following: August 2018-PTG Initial 4 people appointed Q4 2018 (around launch and Berlin) 3 open seats appointed 1H 2019 (time undetermined) 2 more open seats appointed August 2019 4 initial seats up for voting TBD- not clear.... Other seats up for voting I think it is necessary for this to be very clear with a timeline similar to, and as simple as, the above so that when we are doing our outreach to prospective new contributers we can be crystal clear about when they might expect to be appointed a chair, or voted into a chair. Regards, -glenn -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, September 27, 2018 9:15 AM To: Claire Massey; Thierry Carrez; Ildiko Vancsa Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX Initial Governance Thank you for the feedback. We appreciate it. The way I'd like to suggest that we handle this is to get the governance document into source control. At the Documentation team meeting this week we agreed to create a stx-governance repo and place the document there. Then I will post changes to gerrit to address this feedback that can be reviewed and approved. Makes sense? @Ildiko, please let me know when the repo goes live. I'll be working on converting the current draft from wiki to .rst this week. brucej -----Original Message----- From: Claire Massey [mailto:claire@openstack.org] Sent: Thursday, September 27, 2018 8:21 AM To: Thierry Carrez <thierry@openstack.org> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX Initial Governance Hi all, I agree with Thierry and think that in order to encourage growth for the project, the first election period should to be adjusted. The next several months will be a critical time for StarlingX to welcome diverse engagement. From what we’ve experienced while launching other projects, like Kata Containers for example, new companies that are interested in engaging with the project for the first time are also very interested in having the opportunity to be elected to the technical leadership body within a reasonable amount of time. The opportunity to contribute to the project and possibly earn an elected seat early on in the life of the project can be very motivating for new companies that want to get involved. Based on the current StarlingX election timeline shown in the governance documentation[1], September 2019 is the soonest date when a new person would be able to be elected to the TSC. I personally think that waiting an entire year is just too long and may discourage new contributors from getting involved in the short-term. I recommend that instead of waiting a full year to hold the first election, that it's held sooner, in *May 2019*, which is eight months from now. The planned StarlingX release cadence and schedule[2] shows that the next two releases are timed to happen in March and July 2019, so hosting the first election between those two releases, in May 2019, could work well. [1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance#Technical_Steer... [2] https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Cadence_and_S... Thanks, Claire
On Sep 27, 2018, at 10:13 AM, Thierry Carrez <thierry@openstack.org> wrote:
Hi everyone,
I reread the Governance document[1] and found an inconsistency we'll likely want to address before the initial TSC formally blesses it:
In "Technical Steering Committee":
It will be comprised of 7 members who will be appointed at Launch but fully elected by the Contributors within the first year
then:
In April 2020, the remaining 4 seats are up for election
"appointed at Launch" is a bit vague, I would use "initially appointed" (which would start the clock to when the TSC is fully formed). But more importantly, "fully elected by the Contributors within the first year" is at odds with still having appointed members around in March, 2020. The date or the period needs to be adjusted to match.
We'll also likely want to clarify initial terms for the non-WR and non-Intel initial TSC members. One option is to appoint one of them with a short term, and the other two with long terms. Another option would be to randomly select the short one (like for the WR and Intel initially-appointed seats)
Finally, I would suggest saying that if somone steps down from their TSC seat, their seat should automatically be up for election at the next round. So imagine someone that is initially appointed for a year, stepping down after 4 months: their seat would be up for reelection, which would make the first election determine 4 seats instead of just 3. That will facilitate keeping an active TSC with a limited number of stale members.
That level of subtlety could be conveyed through a separate document that details the corner cases of the election process, if you find it too distracting for the Governance document.
[1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance
-- Thierry Carrez (ttx)
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss