<html><body><p>I have known Mr. Taylor for many years and I would like to come out as his first endorser for his big league thoughts and recommendations below. <br><br><br>Brad Topol, Ph.D.<br>IBM Distinguished Engineer<br>OpenStack<br>(919) 543-0646<br>Internet: btopol@us.ibm.com<br>Assistant: Kendra Witherspoon (919) 254-0680<br><br><img width="16" height="16" src="cid:1__=0ABB0AADDFEEDEC08f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Monty Taylor ---09/29/2016 07:29:54 PM---On 09/29/2016 06:14 PM, Clint Byrum wrote: > https://review."><font color="#424282">Monty Taylor ---09/29/2016 07:29:54 PM---On 09/29/2016 06:14 PM, Clint Byrum wrote: > <a href="https://review.openstack.org/379850">https://review.openstack.org/379850</a></font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Monty Taylor <mordred@inaugust.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">openstack-dev@lists.openstack.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">09/29/2016 07:29 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] TC candidacy</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>On 09/29/2016 06:14 PM, Clint Byrum wrote:<br>> </tt><tt><a href="https://review.openstack.org/379850">https://review.openstack.org/379850</a></tt><tt><br>> <br>> Let's make OpenStack great again.<br>> <br>> If you don't know me, I'm very good. The code and designs I make<br>> are tremendous, and I intend to contribute to the TC bigly. The other<br>> candidates are sad, and they want OpenStack to be a third world project,<br>> no good.<br>> <br>> OpenStack, could be the greatest cloud in the history of clouds, but to<br>> get there, you need me, to make sure our clouds are the greatest. We<br>> need to test the clouds, I'm talking about EXTREME cloud vetting,<br>> EXTREME cloud vetting. You know the other TC's are laughing at us,<br>> because we don't have such a great TC.<br>> <br>> The biggest problem we have is people rewriting parts of OpenStack in Go.<br>> They're bringing threads, they're compiled, with errors handled at the<br>> point of return, and some of them, I assume, are good programmers. So<br>> when I'm elected to the TC, I will build a wall, and make Go pay for it.<br>> <br>> ...<br>> <br>> Ok if you're still reading and you don't take things too seriously,<br>> then hello. I'm Clint Byrum, known as "SpamapS" on IRC, and I want to<br>> serve you on the OpenStack Technical Committee. You may recognize me<br>> from various scalability and deployment discussions.<br>> <br>> OpenStack has a number of challenges that face it in the immediate. There<br>> is a crisis of identity that we're only just now wrapping our arms<br>> around, and a question about whether or not this should be something<br>> decided at a centralized level by the TC or not. Are we a toobox? Are<br>> we a product? Can we be both? These are real things, and the TC should<br>> debate them. However, I don't think the TC should force the community to<br>> do anything it doesn't want to do as a whole. If the community really<br>> wants to end the big tent, we should listen, inform, and debate, and<br>> decide whether or not we think it is in the best interest to do so based<br>> on our own expertise, the experience thus far, and a plan to go forward.<br>> <br>> It is my personal belief that the big tent has largely been a success<br>> for OpenStack project teams, but created a problem of confusion that we<br>> should resolve. The recent efforts to more clearly define OpenStack have<br>> been positive, and I would like to help the TC continue down that road.<br>> <br>> In fact, I have recently started an Architecture Working Group to help<br>> define and shape what OpenStack is at a technical design level. Whether<br>> pieces have been evolved apart from one another, or specifically designed<br>> and built to spec, OpenStack hasn't done a good job of writing some<br>> of those things down. I believe the Architecture Working Group will<br>> be capable of improving that, and I want the TC to have some of that<br>> influence built in.<br>> <br>> So, if you want to see more design, consensus building, and an eye for<br>> scaling on the TC, then please consider casting a vote for me.<br><br>I nominate this email to be the best email ever sent to an OpenStack<br>list. In fact, I think we should replace the entire TC with this email.<br>This email shall be our leader and I, for one, welcome it gladly.<br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br><br></tt><br><br><BR>
</body></html>