[tc] Gradually reduce TC to 11 members over 2020
Ghanshyam Mann
gmann at ghanshyammann.com
Wed Aug 28 04:09:46 UTC 2019
--- On Wed, 28 Aug 2019 01:50:40 +0900 Jim Rollenhagen<jim at jimrollenhagen.com> wrote ----On Tue, Aug 27, 2019 at 12:34 PM Dean Troyer <dtroyer at gmail.com> wrote:On Tue, Aug 27, 2019 at 11:02 AM Jeremy Stanley <fungi at yuggoth.org> wrote:
> With my (soon to be former, at least for a cycle) TC member hat on,
> I suggest that we hold this election as planned but circulate the
> suggestion of electing fewer seats in coming cycles. Then once the
> new TC has been confirmed let them decide whether that should be the
> plan as soon into the new term as possible, and announce that
> decision so the community will be prepared for it in the next
> election.
I completely agree with this, it is usually around election time
(often just after) that we think about these things but making a
change for the impending election is too quick. I like Thierry's
suggested schedule and I like the target of 9. I do not have a strong
preference for getting to 9 in 2 vs 4 cycles (2 at a time vs 1 at a
time). As has been mentioned elsewhere (IRC?) having an even number
should not be an issue, looking back I can recall only one vote where
it might have been a problem and in that case since it was clear we
did not have consensus the plan was dropped anyway. FWIW, StarlingX
had an even number of members on its Technical Steering Committee (TC
equivalent) for two cycles and it has not been a problem for basically
the same reason, when driving for even close consensus you generally
do not get ties.I agree even numbers are not a problem. I don't think (hope?)the existing TC would merge anything that went 7-6 anyway.I agree with the idea here to reduce the TC number. I think even number make more sense to have balance between both elections. We can reduce it gradually with target of 11 or 10 as of now and depends on future situations we can decide for more lower number.-gmann// jim
dt
--
Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190828/3518ad8c/attachment.html>
More information about the openstack-discuss
mailing list