<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 16-08-04 09:05 AM, Doug Hellmann wrote:<br>
<blockquote
cite="mid:92B28F90-0987-407A-874C-E9D54DD16C68@doughellmann.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">On Aug 4, 2016, at 6:14 AM, Flavio Percoco <a class="moz-txt-link-rfc2396E" href="mailto:flavio@redhat.com"><flavio@redhat.com></a> wrote:
On 04/08/16 09:46 +0200, Thierry Carrez wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Morgan Fainberg wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
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)
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<pre wrap="">
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 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?</pre>
</blockquote>
<br>
First of all Morgan, sad to see you go. Glad you are making a
decision that is responsible regarding the way you want to use your
time.<br>
<br>
I would consider Morgan's seat to be up for by-election, which can
take place any time, including congruent with the election of the
other 6 seats. But like any other time a term is not finished, I
consider the situation to be a by-election.<br>
<br>
I think the 6 seats that are up for re-election are renewed as usual
and that Morgan's seat is a by-election, which means that person
filling the role does so for the remainder of the term Morgan was to
serve.<br>
<br>
They by-election could be held any time and separately. If it is
held at the same time as the election to renew 6 seats as scheduled
then selecting the candidate that ranks 7th overall certainly is an
option.<br>
<br>
Thanks,<br>
Anita.<br>
<br>
<blockquote
cite="mid:92B28F90-0987-407A-874C-E9D54DD16C68@doughellmann.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">2/ hold a normal 6-seat election in fall and give Morgan's seat for 6
months to whoever ranks 7th
I'm fine with both, but if we do (1) we'll have to update the charter
(which explicitly says "6 seats are renewed every (Northern hemisphere)
Fall, and 7 seats are renewed every Spring"). So it may be simpler to do
(2).
Thoughts ? I added this to the agenda for next meeting (which I'll miss).
</pre>
</blockquote>
<pre wrap="">
Put this up for the sake of voting/discussing this argument: <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/351104/">https://review.openstack.org/#/c/351104/</a> <a class="moz-txt-link-rfc2396E" href="https://review.openstack.org/#/c/351104/"><https://review.openstack.org/#/c/351104/></a>
Happy to help with this change,
Flavio
--
@flaper87
Flavio Percoco
_______________________________________________
OpenStack-TC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:OpenStack-TC@lists.openstack.org"><mailto:OpenStack-TC@lists.openstack.org></a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a> <a class="moz-txt-link-rfc2396E" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc"><http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc></a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-TC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-TC@lists.openstack.org">OpenStack-TC@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a>
</pre>
</blockquote>
<br>
</body>
</html>