<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.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><br>
On Aug 13, 2014, at 3:05 PM, Eoghan Glynn <<a href="mailto:eglynn@redhat.com" target="_blank">eglynn@redhat.com</a>> wrote:<br>
<br>
><br>
>>> At the end of the day, that's probably going to mean saying No to more<br>
>>> things. Everytime I turn around everyone wants the TC to say No to<br>
>>> things, just not to their particular thing. :) Which is human nature.<br>
>>> But I think if we don't start saying No to more things we're going to<br>
>>> end up with a pile of mud that no one is happy with.<br>
>><br>
>> That we're being so abstract about all of this is frustrating. I get<br>
>> that no-one wants to start a flamewar, but can someone be concrete about<br>
>> what they feel we should say 'no' to but are likely to say 'yes' to?<br>
>><br>
>><br>
>> I'll bite, but please note this is a strawman.<br>
>><br>
>> No:<br>
>> * Accepting any more projects into incubation until we are comfortable with<br>
>> the state of things again<br>
>> * Marconi<br>
>> * Ceilometer<br>
><br>
> Well -1 to that, obviously, from me.<br>
><br>
> Ceilometer is on track to fully execute on the gap analysis coverage<br>
> plan agreed with the TC at the outset of this cycle, and has an active<br>
> plan in progress to address architectural debt.<br>
<br>
</div>Yes, there seems to be an attitude among several people in the community that the Ceilometer team denies that there are issues and refuses to work on them. Neither of those things is the case from our perspective.<br>
</blockquote><div><br></div><div>Totally agree.</div><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">
<br>
Can you be more specific about the shortcomings you see in the project that aren’t being addressed?<br></blockquote><div><br></div><div><br></div><div>Once again, this is just a strawman.</div><div><br></div><div>I'm just not sure OpenStack has 'blessed' the best solution out there.</div>
<div><br></div><div><a href="https://wiki.openstack.org/wiki/Ceilometer/Graduation#Why_we_think_we.27re_ready" target="_blank">https://wiki.openstack.org/wiki/Ceilometer/Graduation#Why_we_think_we.27re_ready</a></div><div>
<br></div><div>
<font color="#333333" face="Arial Unicode MS, Arial, sans-serif"><span style="font-size:14px;line-height:20px">"</span></font></div><ul style="padding:0px;margin:0.3em 0px 0px 1.6em;color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">
<li>Successfully passed the challenge of being adopted by 3 related projects which have agreed to join or use ceilometer:</li><ul style="padding:0px;margin:0.3em 0px 0px 1.6em"><li>Synaps</li><li>Healthnmon</li><li><a href="https://wiki.openstack.org/w/index.php?title=StackTach&action=edit&redlink=1" title="StackTach (page does not exist)" style="color:rgb(186,0,0);text-decoration:none" target="_blank">StackTach</a>"</li>
</ul></ul><div><br></div><div>Stacktach seems to still be under active development (<a href="http://git.openstack.org/cgit/stackforge/stacktach/log/" target="_blank">http://git.openstack.org/cgit/stackforge/stacktach/log/</a>), is used by rackspace in production and from everything I hear is more mature then ceilometer.</div>
<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><br>
><br>
>> Divert all cross project efforts from the following projects so we can focus<br>
>> our cross project resources. Once we are in a bitter place we can expand our<br>
>> cross project resources to cover these again. This doesn't mean removing<br>
>> anything.<br>
>> * Sahara<br>
>> * Trove<br>
>> * Tripleo<br>
><br>
> You write as if cross-project efforts are both of fixed size and<br>
> amenable to centralized command & control.<br>
><br>
> Neither of which is actually the case, IMO.<br>
><br>
> Additional cross-project resources can be ponied up by the large<br>
> contributor companies, and existing cross-project resources are not<br>
> necessarily divertable on command.<br></div></blockquote><div><br></div><div>Sure additional cross-project resources can and need to be ponied up, but I am doubtful that will be enough.</div><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>
<br>
</div>What “cross-project efforts” are we talking about? The liaison program in Oslo has been a qualified success so far. Would it make sense to extend that to other programs and say that each project needs at least one designated QA, Infra, Doc, etc. contact?<br>
<span><font color="#888888"><br>
Doug<br>
</font></span><div><div><br>
><br>
>> Yes:<br>
>> * All integrated projects that are not listed above<br>
><br>
> And what of the other pending graduation request?<br>
><br>
> Cheers,<br>
> Eoghan<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>
<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>
</div></div></blockquote></div><br></div></div>