<div dir="ltr">Two items:<div><br></div><div>When I listened to the Elephant.6 meeting I was very encouraged to hear people say they wanted to publish a list of guidelines for selecting designated sections. It sounded like these guidelines were already well understood by one side of the table. Are these guidelines now published somewhere? If not, why are we trying to create a strawman proposal before they are published? I for one don't question the wisdom of using designated sections--I just want to know more clearly or elaborately what we're trying to achieve so that I can make an intelligent recommendation for my project.</div>
<div><br></div><div>The governance wiki page uses a specific definition for a plugin that is not universally applicable or universally good in a technical sense. What is the pedigree of this definition? Can it be dropped, or was it baked into the Board motion? The use of designated sections seems to me to be a very adroit way of addressing the need that was originally being met with the plugin definition, so this definition doesn't really feel necessary to me.</div>
<div><div><br></div><div>Thanks!</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 21, 2014 at 6:41 AM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Fri, Mar 21, 2014 at 4:10 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-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>Michael Still wrote:<br>
> So, the defcore committee just had a meeting and I have to say it was<br>
> a lot more productive than the previous one. I'm sure the recording<br>
> will appear on YouTube at some point, but I am not sure when that will<br>
> be.<br>
><br>
> There is a desire to have a voice chat to interactively produce an<br>
> etherpad that contains straw man designated sections for the various<br>
> integrated projects. I personally think this is a good idea, because I<br>
> think it will be more productive than yet another email thread.<br>
><br>
> So... Who is available for either of these time slots next week?<br>
><br>
> * Wednesday 26 March at 8pm UTC<br>
> * Friday 28 March at 8pm UTC<br>
<br>
</div></div>Shouldn't this call also be directed to the integrated projects PTLs,<br>
rather than just the TC members ? IMHO the PTLs are the final authority<br>
for producing this information, with the TC providing guidance and<br>
encouraging some homogeneity.<br>
<br>
Here is a list of people that need to be looped in (Icehouse release):<br>
David Lyle (Horizon)<br>
Dolph Mathews (Keystone)<br>
John Dickinson (Swift)<br>
Julien Danjou (Ceilometer)<br>
Mark Washenberger (Glance)<br>
Michael Basnight (Trove)<br>
Steve Baker (Heat)<br>
<br>
The other integrated projects PTLs (Nova, Cinder, Oslo, Neutron) also<br>
seat on the TC.<br>
<span><font color="#888888"><br></font></span></blockquote><div><br></div></div></div><div>Thanks for the list, Thierry. Adding them to this thread. (There's no all-PTL mailing list I should use, right?)</div><div><br>
</div><div>The request: we're looking for designated sections of your program's code to help define criteria for "core definition" where core definition is part of our governance docs at <span style="font-size:13px"><a href="https://wiki.openstack.org/wiki/Governance/CoreDefinition" target="_blank">https://wiki.openstack.org/wiki/Governance/CoreDefinition</a>. </span></div>
<div class="gmail_quote"><br></div>Who wants it: The board members working on core definition<br><br></div><div class="gmail_quote">What does it get them: Forward movement on defining the OpenStack mark use policies<br>How will they know if they have it: The etherpad at <a href="https://etherpad.openstack.org/p/openstack-designated-sections" target="_blank">https://etherpad.openstack.org/p/openstack-designated-sections</a> will have your project's name in it with simple definitions of what parts of your code base should be run. (Do not overthink this: simple outlines will suffice.)<br>
<br></div><div class="gmail_quote">When do they need it by: 3/31 (I know this is a busy time for everyone with the release. Please raise your hand if you need help, we will find it for you.)<br><br></div><div class="gmail_quote">
Who might be exempt: We do not need all projects to designate sections, only the ones that are likely to have capabilities flagged by required tests. If you think yours lands in this exempt category, just ask. </div><div class="gmail_quote">
<br></div><div class="gmail_quote">What happens if this doesn't get done: We continue to struggle with the definition of an OpenStack cloud. Probably someone else will define for you (which is also likely just fine).</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">Let me know if this request outline is useful and feel free to ask any questions as you go.</div><div class="gmail_quote"><span class="HOEnZb"><font color="#888888"><br>
<div>Anne</div></font></span><div class=""><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">
<span><font color="#888888">
--<br>
Thierry Carrez (ttx)<br>
<br>
_______________________________________________<br>
OpenStack-TC mailing list<br>
<a href="mailto:OpenStack-TC@lists.openstack.org" target="_blank">OpenStack-TC@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc</a><br>
</font></span></blockquote></div></div><br></div></div>
</blockquote></div><br></div>