<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>+1 to this. It would be great to read the compiled spec and have it be searchable/filtered.</div>
<div>-Anthony</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>Thank you for the update, Kyle.</div>
<div><br>
</div>
<div>I was sceptical about this move at first but hopefully I was wrong. The specs repository indeed eases a lot of the work from a submitter and reviewer point of view.</div>
<div><br>
</div>
Is there any web page where all approved blueprints are being published to? Jenkins builds such pages I’m looking for but they are linked to each patchset individually (e.g., <a href="http://docs-draft.openstack.org/77/92477/6/check/gate-neutron-specs-docs/f05cc1d/doc/build/html/">http://docs-draft.openstack.org/77/92477/6/check/gate-neutron-specs-docs/f05cc1d/doc/build/html/</a>).
In addition, listing BPs currently under reviewing and linking to its review.o.o page could potentially draw more attention/awareness to what’s being proposed to Neutron (and other OpenStack projects).
<div>
<div>
<div>
<div>
<div><br>
</div>
<div>Thanks,</div>
<div>Carlos Goncalves</div>
<div><br>
<div>
<div>On 11 Jun 2014, at 18:25, Kyle Mestery <<a href="mailto:mestery@noironetworks.com">mestery@noironetworks.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">tl;dr: The specs repository has been great to work with. As a<br>
reviewer, it makes reviews easier. As PTL, it makes tracking easier as<br>
well.<br>
<br>
Since Juno-1 is about to close, I wanted to give everyone an update on<br>
Neutron's usage of the specs repository. These are observations from<br>
using this since a few weeks before the Summit. I thought it would be<br>
good to share with the broader community to see if other projects<br>
using spec repositories had similar thoughts, and I also wanted to<br>
share this info for BP submitters and reviewers.<br>
<br>
Overall, the spec repository has been great as a tool to consolidate<br>
where new ideas are documented and made into something we can merge<br>
and move forward with. Using gerrit for this has been great. We've<br>
merged a good amount of specs [1], and the process of hooking these to<br>
Launchpad for milestone tracking has been straightforward. As the PTL<br>
of Neutron, I've found the specs repository helps me out immensely,<br>
the workflow is great.<br>
<br>
One of the things I've noticed is that sometimes it's hard to get<br>
submitters to respond to feedback on the specs repository. If you look<br>
at our current queue of open BPs [2], we have a lot which are waiting<br>
for feedback from submitters. I don't know how to address this issue,<br>
any feedback appreciated here.<br>
<br>
Secondly, with so many open BPs, it's unlikely that all of these will<br>
make Juno. With what we already have approved and being worked, a lot<br>
of these will likely slide to the "K" release. At some point in the<br>
next few weeks, I may start going through some and marking them as<br>
such.<br>
<br>
So, to summarize, I'm very happy with the workflow from the specs repository.<br>
<br>
Thanks for reading!<br>
Kyle<br>
<br>
[1] <a href="https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z">
https://review.openstack.org/#/q/status:merged+project:openstack/neutron-specs,n,z</a><br>
[2] <a href="https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z">
https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z</a><br>
<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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>