<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">On August 7, 2014 at 8:36:16 AM, Matt Wagner (<a href="mailto:matt.wagner@redhat.com">matt.wagner@redhat.com</a>) wrote:</div> <div><blockquote type="cite" class="clean_bq" style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><span><div><div></div><div>On 07/08/14 14:17 +0200, Dmitry Tantsur wrote:<span class="Apple-converted-space"> </span><br><snip><span class="Apple-converted-space"> </span><br>>2. We'll need to speed up spec reviews, because we're adding one more<span class="Apple-converted-space"> </span><br>>blocker on the way to the code being merged :) Maybe it's no longer a<span class="Apple-converted-space"> </span><br>>problem actually, we're doing it faster now.<span class="Apple-converted-space"> </span><br><br>I'm not sure if this will actually delay stuff getting merged.<span class="Apple-converted-space"> </span><br><br>It certainly has the potential to do so. If people submit a draft in<span class="Apple-converted-space"> </span><br>Launchpad and it takes us a week to review it, that's adding a lot of<span class="Apple-converted-space"> </span><br>latency.<span class="Apple-converted-space"> </span><br><br>OTOH, if we're on top of things, I think it could actually increase<span class="Apple-converted-space"> </span><br>overall throughput. We'd spent less time reviewing specs that are just<span class="Apple-converted-space"> </span><br>entirely out of scope, and we'd be able to help steer spec-writers<span class="Apple-converted-space"> </span><br>onto the right path sooner. They, in turn, would waste less time<span class="Apple-converted-space"> </span><br>writing specs that are then rejected wholesale, or deemed to need<span class="Apple-converted-space"> </span><br>significant reworking.<span class="Apple-converted-space"> </span><br><br>I'm not really disagreeing with you--we need to be vigilant and make<span class="Apple-converted-space"> </span><br>sure we don't introduce a bottleneck with this. But I also think that,<span class="Apple-converted-space"> </span><br>as long as we do that, we might actually speed things up overall.<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>I agree. I think we have been doing much better with specs, especially since growing that core team and explicitly defining our priorities for Juno.</p><p>I don’t think this will increase latency in reviews - the initial review is quick and easy to do, as it’s just deciding overall if we want the feature. I think this may actually *reduce* latency - specs that are not wanted will get -2’d quickly, and steps that are wanted will have at least one core that is excited about the feature (if no cores care about the feature, it likely won’t be “pre-approved” or whatever we’re calling it).</p><p>I +1’d this at the meetup, doing it here again for public consumption. :)</p><p>// jim</p><div><blockquote type="cite" class="clean_bq" style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><span><div><div><br><br>-- Matt<span class="Apple-converted-space"> </span><br>_______________________________________________<span class="Apple-converted-space"> </span><br>OpenStack-dev mailing list<span class="Apple-converted-space"> </span><br>OpenStack-dev@lists.openstack.org<span class="Apple-converted-space"> </span><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<span class="Apple-converted-space"> </span><br></div></div></span></blockquote></div></body></html>