<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 30, 2013 at 9:17 AM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug.hellmann@dreamhost.com" target="_blank">doug.hellmann@dreamhost.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div class="h5">On Tue, May 28, 2013 at 5:18 PM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div>On Tue, May 28, 2013 at 8:29 AM, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi everyone,<br>
<br>
Back in January we had a thread[1] about modifying how the Technical<br>
Committee members[2] are selected, in order to cope with future expected<br>
growth in the number of projects. Unfortunately there wasn't enough time<br>
to properly discuss it before we had to look into incubated projects<br>
graduation and setting up the Spring elections, so we decided to<br>
postpone this to the Havana cycle.<br>
<br>
[1]<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2013-January/004513.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2013-January/004513.html</a><br>
[2] <a href="https://wiki.openstack.org/wiki/Governance/TechnicalCommittee" target="_blank">https://wiki.openstack.org/wiki/Governance/TechnicalCommittee</a><br>
<br>
To kick off this second attempt, we had an interesting session at the<br>
Design Summit where various goals were discussed and various solutions<br>
proposed and compared. I summarized the current state of affairs on the<br>
wiki at:<br>
<br>
<a href="https://wiki.openstack.org/wiki/TC_Membership_Models" target="_blank">https://wiki.openstack.org/wiki/TC_Membership_Models</a><br>
<br>
I'd like everyone interested with this discussion to have a look at this<br>
page. If you see goals that we missed, please suggest them on the thread<br>
here, along with how well each currently-proposed solution would score<br>
against it. Same if you think some model was not scored fairly against<br>
existing stated goals. Finally, if you have an alternate model which<br>
you'd like to suggest, feel free to do so. I'll keep the wiki page<br>
updated based on the ML discussion.<br></blockquote><div><br></div></div><div>Thanks for the draft write up. I have some thoughts for discussion.<br><br></div><div>You point to an idea number of 11 for the group size, and I would like some citation for where that number comes from. I know of the two-pizza rule in tech, and there's group research around "ten-groups" (saying eight to fourteen people in a group is about right for overcoming human nature and collaborating effectively, citing book <em>Corporation Man</em> by Antony Jay (Pelican 1975)). What causes you to land on 11? Could we say 10 or a range of 8-14 instead? <br>
<br></div><div>Defining the ideal group size will help with scoring. For example, I don't think the difference between 11 members and 13 members merits a +2 vs. a +1 score.<br><br>I also think the ideal number of members will help determine whether categories are useful, and further defining categories to discover how many there may be will help score that one better.<br>
</div></div></div></div></blockquote><div><br></div></div></div><div>The category model seems interesting, but I would like to be able to consider a more concrete proposal. Should we work out a list of specific categories?</div>
</div></div></div></blockquote><div><br></div><div><br></div><div style>Yes! I was waiting for a range of values to see where my list from the old thread [1] might work inside a range. </div><div style><br>Storage<br>Computing<br>
Networking<br>Monitoring<br>Operating<br>Packaging<br>Continuous Integration and Builds<br>Doc<br>QA<br>Integration Testing<br>API<br>UI/CLI (Dashboard/clients)<br><br>That's twelve, and I may not be including all the categories. Some do not<br>
have projects yet. There may be another category of "services on top of<br>Computing" that I'm under-representing, thinking of Databases or Load<br>Balancers or DNS that would rely on Compute to provide their service. How<br>
would we expand to include them? <br></div><div style><br></div><div style>Anne</div><div style><br></div><div>1. <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-January/004539.html">http://lists.openstack.org/pipermail/openstack-dev/2013-January/004539.html</a></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<span class=""><font color="#888888">
<div><br></div><div>Doug</div></font></span><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>
</div><div><br></div><div>Thanks,<br>Anne<br></div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Hopefully we can all come up with a generally-consensual model able to<br>
handle future growth of the project.<br>
<br>
Regards,<br>
<span><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
Chair, OpenStack Technical Committee<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</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>
</font></span></blockquote></div></div><span><font color="#888888"><br><br clear="all"><br>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</font></span></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</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></blockquote></div></div><br></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>