<div dir="ltr">Hi Anne; this was more or less directed in Monty's direction and/or those in agreement with his position. Sorry for the confusion, I probably should have been a bit more clear. ; )<div><br></div><div>Mahalo,</div><div>Adam</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><font><div style="font-family:arial;font-size:small"><b><i><br>Adam Lawson</i></b></div><div><font><font color="#666666" size="1"><div style="font-family:arial"><br></div><div style="font-family:arial;font-size:small">AQORN, Inc.</div><div style="font-family:arial;font-size:small">427 North Tatnall Street</div><div style="font-family:arial;font-size:small">Ste. 58461</div><div style="font-family:arial;font-size:small">Wilmington, Delaware 19801-2230</div><div style="font-family:arial;font-size:small">Toll-free: (844) 4-AQORN-NOW ext. 101</div><div style="font-family:arial;font-size:small">International: +1 302-387-4660</div></font><font color="#666666" size="1"><div style="font-family:arial;font-size:small">Direct: +1 916-246-2072</div></font></font></div></font></div><div style="font-family:arial;font-size:small"><img src="http://www.aqorn.com/images/logo.png" width="96" height="39"><br></div></div></div></div>
<br><div class="gmail_quote">On Thu, Jan 29, 2015 at 9:05 AM, Anita Kuno <span dir="ltr"><<a href="mailto:anteaya@anteaya.info" target="_blank">anteaya@anteaya.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/28/2015 07:24 PM, Adam Lawson wrote:<br>
> I'm short on time so I apologize for my candor since I need to get straight<br>
> to the point.<br>
><br>
> I love reading the various opinions and my team is immensely excited with<br>
> OpenStack is maturing. But this is lunacy.<br>
><br>
> I looked at the patch being worked [1] to change how things are done and<br>
> have more questions than I can count.<br>
><br>
> So I'll start with the obvious ones:<br>
><br>
</span>> - Are you proposing this change as a Foundation Individual Board<br>
<span class="">> Director tasked with representing the interests of all Individual Members<br>
> of the OpenStack community or as a member of the TC? Context matters<br>
> because your two hats are presenting a conflict of interest in my opinion.<br>
> One cannot propose a change that gives them greater influence while<br>
> suggesting they're doing it for everyone's benefit.<br>
</span>How can Jim be proposing a change as a Foundation Individual Board<br>
Director? He isn't a member of the Board.<br>
<br>
<a href="http://www.openstack.org/foundation/board-of-directors/" target="_blank">http://www.openstack.org/foundation/board-of-directors/</a><br>
<br>
He is a member of the Technical Committee.<br>
<br>
<a href="http://www.openstack.org/foundation/tech-committee/" target="_blank">http://www.openstack.org/foundation/tech-committee/</a><br>
<br>
Keep in mind that the repository that he offered the change to, the<br>
openstack/governance repository, welcomes patches from anyone who takes<br>
the time to learn our developer workflow and offers a patch to the<br>
repository using Gerrit.<br>
<br>
<a href="http://docs.openstack.org/infra/manual/developers.html" target="_blank">http://docs.openstack.org/infra/manual/developers.html</a><br>
<br>
Thanks,<br>
Anita.<br>
> - How is "fun" remotely relevant when discussing process improvement?<br>
<span class="">> I'm really hoping we aren't developing processes based on how fun a process<br>
> is or isn't.<br>
</span>> - Why is this discussion being limited to the development community<br>
<span class="">> only? Where's the openness in that?<br>
</span>> - What exactly is the problem we're attempting to fix?<br>
> - Does the current process not work?<br>
> - Is there group of individuals being disenfranchised with our current<br>
<span class="">> process somehow that suggests the process should limit participation<br>
> differently?<br>
><br>
> And some questions around the participation proposals:<br>
><br>
</span>> - Why is the election process change proposing to limit participation to<br>
<span class="">> ATC members only?<br>
> There are numerous enthusiasts within our community that don't fall<br>
> within the ATC category such as marketing (as some have brought up),<br>
> corporate sponsors (where I live) and I'm sure there are many more.<br>
</span>> - Is taking back the process a hint that the current process is being<br>
<span class="">> mishandled or restores a sense of process control?<br>
</span>> - Is the presumption that the election process belongs to someone or<br>
<span class="">> some group?<br>
> That strikes me as an incredibly subjective assertion to make.<br>
><br>
> <opinion>This is one reason I feel so strongly folks should not be allowed<br>
> to hold more than one position of leadership within the OpenStack project.<br>
> Obfuscated context coupled with increased influence rarely produces<br>
> excellence on either front. But that's me.</opinion><br>
><br>
> Mahalo,<br>
> Adam<br>
><br>
> [1] <a href="https://review.openstack.org/#/c/150604/" target="_blank">https://review.openstack.org/#/c/150604/</a><br>
><br>
><br>
</span>> *Adam Lawson*<br>
<span class="im HOEnZb">><br>
> AQORN, Inc.<br>
> 427 North Tatnall Street<br>
> Ste. 58461<br>
> Wilmington, Delaware 19801-2230<br>
> Toll-free: (844) 4-AQORN-NOW ext. 101<br>
> International: <a href="tel:%2B1%20302-387-4660" value="+13023874660">+1 302-387-4660</a><br>
> Direct: <a href="tel:%2B1%20916-246-2072" value="+19162462072">+1 916-246-2072</a><br>
><br>
><br>
</span><div class="HOEnZb"><div class="h5">> On Wed, Jan 28, 2015 at 10:23 AM, Anita Kuno <<a href="mailto:anteaya@anteaya.info">anteaya@anteaya.info</a>> wrote:<br>
><br>
>> On 01/28/2015 11:36 AM, Thierry Carrez wrote:<br>
>>> Monty Taylor wrote:<br>
>>>> What if, to reduce stress on you, we make this 100% mechanical:<br>
>>>><br>
>>>> - Anyone can propose a name<br>
>>>> - Election officials verify that the name matches the criteria<br>
>>>> - * note: how do we approve additive exceptions without tons of effort<br>
>>><br>
>>> Devil is in the details, as reading some of my hatemail would tell you.<br>
>>> For example in the past I rejected "Foo" which was proposed because<br>
>>> there was a "Foo Bar" landmark in the vicinity. The rules would have to<br>
>>> be pretty detailed to be entirely objective.<br>
>> Naming isn't objective. That is both the value and the hardship.<br>
>>><br>
>>>> - Marketing team provides feedback to the election officials on names<br>
>>>> they find image-wise problematic<br>
>>>> - The poll is created with the roster of all foundation members<br>
>>>> containing all of the choices, but with the marketing issues clearly<br>
>>>> labeled, like this:<br>
>>>><br>
>>>> * Love<br>
>>>> * Lumber<br>
>> Ohh, it gives me a thrill to see a name that means something even<br>
>> remotely Canadian. (not advocating it be added to this round)<br>
>>>> * Lettuce<br>
>>>> * Lemming - marketing issues identified<br>
>>>><br>
>>>> - post poll - foundation staff run trademarks checks on the winners in<br>
>>>> order until a legally acceptable winner is found<br>
>>>><br>
>>>> This way nobody is excluded, it's not a burden on you, it's about as<br>
>>>> transparent as it could be - and there are no special privileges needed<br>
>>>> for anyone to volunteer to be an election official.<br>
>>>><br>
>>>> I'm going to continue to advocate that we use condorcet instead of a<br>
>>>> launchpad poll because we need the ability to rank things for post-vote<br>
>>>> trademark checks to not get weird. (also, we're working on getting off<br>
>>>> of launchpad, so let's not re-add another connection)<br>
>>><br>
>>> It's been some time since we last used a Launchpad poll. I recently used<br>
>>> an open surveymonkey poll, which allowed crude ranking. Agree that<br>
>>> Condorcet is better, as long as you can determine a clear list of voters.<br>
>>><br>
>><br>
>> Glad we are talking about this,<br>
>> Anita.<br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>