[openstack-tc] Stepping down

Doug Hellmann doug at doughellmann.com
Thu Aug 4 17:24:31 UTC 2016


> On Aug 4, 2016, at 1:15 PM, Doug Hellmann <doug at doughellmann.com> wrote:
> 
>> 
>> On Aug 4, 2016, at 1:10 PM, Sean Dague <sean at dague.net <mailto:sean at dague.net>> wrote:
>> 
>> On 08/04/2016 10:07 AM, Flavio Percoco wrote:
>>> On 04/08/16 09:56 -0400, Doug Hellmann wrote:
>>>> 
>>>>> On Aug 4, 2016, at 9:52 AM, Monty Taylor <mordred at inaugust.com <mailto:mordred at inaugust.com>> wrote:
>>>>> 
>>>>> On 08/04/2016 08:05 AM, Doug Hellmann wrote:
>>>>>> 
>>>>>>> On Aug 4, 2016, at 6:14 AM, Flavio Percoco <flavio at redhat.com <mailto:flavio at redhat.com>
>>>>>>> <mailto:flavio at redhat.com <mailto:flavio at redhat.com>>
>>>>>>> <mailto:flavio at redhat.com <mailto:flavio at redhat.com> <mailto:flavio at redhat.com <mailto:flavio at redhat.com>>>> wrote:
>>>>>>> 
>>>>>>> On 04/08/16 09:46 +0200, Thierry Carrez wrote:
>>>>>>>> Morgan Fainberg wrote:
>>>>>>>>> NOTE: Cross-posted to this list as well as the -dev list.
>>>>>>>>> 
>>>>>>>>> Based upon my personal time demands among a number of other
>>>>>>>>> reasons I
>>>>>>>>> will be stepping down from the Technical Committee. This is
>>>>>>>>> planned to
>>>>>>>>> take effect with the next TC election so that my seat will be up
>>>>>>>>> to be
>>>>>>>>> filled at that time.
>>>>>>>>> 
>>>>>>>>> For those who elected me in, thank you.
>>>>>>>> 
>>>>>>>> Hijacking this branch of the thread to discuss how to replace
>>>>>>>> Morgan at
>>>>>>>> next election, since our charter is a bit unclear on that.
>>>>>>>> 
>>>>>>>> We have two options:
>>>>>>>> 
>>>>>>>> 1/ just renew 7 seats at the fall election (and 6 seats next spring)
>>>>>>> 
>>>>>>> I'd prefer #1, tbh. I'd rather have someone elected for the entire
>>>>>>> period than
>>>>>>> having a temporary member that might not be re-elected on the Northern
>>>>>>> Spring. 6
>>>>>>> months won't likely be enough for the 7th elected member to shine and
>>>>>>> be amazing
>>>>>>> and it sounds unfair to me.
>>>>>> 
>>>>>> While I agree that it’s less than ideal, there are a lot of situations
>>>>>> in which a partial term might come up, and we don’t want to rewrite the
>>>>>> charter every time we get into a new situation. If Morgan needed to
>>>>>> step
>>>>>> down right now, or a month or two ago, we would likely have wanted an
>>>>>> interim replacement earlier. We should fix up the charter to allow
>>>>>> that.
>>>>> 
>>>>> I agree that fixing up the charter to allow for a generalized mechanism
>>>>> for member replacement is a good idea.
>>>>> 
>>>>>> I believe the board has an informal replacement policy of looking back
>>>>>> at the last election and taking the next person down the list, don’t
>>>>>> they? That seems reasonable for us, too. In this case, since Morgan is
>>>>>> going to serve until the election, we should select the 7th from those
>>>>>> results to serve a half term. I think this is Thierry’s option 2,
>>>>>> isn’t it?
>>>>> 
>>>>> The board bylaws state that in the case a replacement individual
>>>>> director is needed, the remaining individual directors will select one,
>>>>> or may choose to not select a replacement. So far in the cases it has
>>>>> come up, the individual directors have chosen to look at the prior
>>>>> election because it seemed like a good way to go about it.
>>>> 
>>>> Thanks for clarifying that. I’d like to use the same system. I’m not
>>>> sure if we want to hard-code that, or use the same flexible language
>>>> and just agree on the process informally. I don’t have a strong reason
>>>> for avoiding hard-coding it, other than maintaining flexibility.
>>> 
>>> The process sounds flexible enough, I don't think hard-coding it would
>>> take some
>>> flexibility away.
>> 
>> I think my preference is to use the board process here. Have it formally
>> be a TC level decision so we're not springing a special election on
>> people during vacation season. And putting the election mechanism into
>> play out of rhythm when people aren't expecting it.
>> 
>> And with that TC decision, my recommendation should just look at the
>> results from the most recent election -
>> http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fef5cc22eb3dc27a <http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fef5cc22eb3dc27a> and
>> ask folks from the top down if it's something they are still interested in.
> 
> Right, though Morgan has said he’ll serve through the next election, so we’d use that one this time.

Here’s some wording to work on: https://review.openstack.org/351295

Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20160804/b62da558/attachment.html>


More information about the OpenStack-TC mailing list