<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;">
<br>
<div>
<div>On Mar 24, 2014, at 2:23 PM, Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-size: 12px; 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;">
On 03/24/2014 02:05 PM, James E. Blair wrote:<br>
<blockquote type="cite">Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>> writes:<br>
<br>
<blockquote type="cite">On 03/24/2014 12:34 PM, James E. Blair wrote:<br>
<blockquote type="cite">Hi,<br>
<br>
So recently we started this experiment with the compute and qa programs<br>
to try using Gerrit to review blueprints. Launchpad is deficient in<br>
this area, and while we hope Storyboard will deal with it much better,<br>
but it's not ready yet.<br>
</blockquote>
<br>
This seems to be a point of confusion. My view is that Storyboard isn't<br>
intended to implement what gerrit provides. Given that, it seems like<br>
we'd still be using this whether the tracker is launchpad or storyboard.<br>
</blockquote>
<br>
I don't think it's intended to implement what Gerrit provides, however,<br>
I'm not sure what Gerrit provides is _exactly_ what's needed here. I do<br>
agree that Gerrit is a much better tool than launchpad for collaborating<br>
on some kinds of blueprints.<br>
<br>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<div>Agreed, but the current blueprint system is broken in a way that a half step with an imperfect tool is better than keeping the status quo.</div>
<br>
<blockquote type="cite">
<div style="font-size: 12px; 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;">
<blockquote type="cite">However, one of the reasons we're creating StoryBoard is so that we have<br>
a tool that is compatible with our workflow and meets our requirements.<br>
It's not just about tracking work items, it should be a tool for<br>
creating, evaluating, and progressing changes to projects (stories),<br>
across all stages.<br>
<br>
I don't envision the end-state for storyboard to be that we end up<br>
copying data back and forth between it and Gerrit. Since we're<br>
designing a system from scratch, we might as well design it to do what<br>
we want.<br>
<br>
One of our early decisions was to say that UX and code stories have<br>
equally important use cases in StoryBoard. Collaboration around UX<br>
style blueprints (especially those with graphical mock-ups) sets a<br>
fairly high bar for the kind of interaction we will support.<br>
<br>
Gerrit is a great tool for reviewing code and other text media. But<br>
somehow it is even worse than launchpad for collaborating when visual<br>
media are involved. Quite a number of blueprints could benefit from<br>
better support for that (not just UI mockups but network diagrams, etc).<br>
We can learn a lot from the experiment of using Gerrit for blueprint<br>
review, and I think it's going to help make StoryBoard a lot better for<br>
all of our use cases.<br>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<div>Diagram handling was one of the first questions I asked Russell when I saw the repo creation proposal. Diagrams are very helpful and while gerrit is not ideal for handling diagrams, Sphinx should allow us to incorporate them in basic way for now. I view
this as an improvement over the 5 different formats blueprints are submitted in now. </div>
<div><br>
</div>
<blockquote type="cite">
<div style="font-size: 12px; 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;">
<br>
I think that's fine if long term this whole thing is optimized. I just<br>
do very much worry that StoryBoard keeps going under progressive scope<br>
creep before we've managed to ship the base case. That's a dangerous<br>
situation to be in, as it means it's evolving without a feedback loop.<br>
<br>
I'd much rather see Storyboard get us off launchpad ASAP across all the<br>
projects, and then work on solving the things launchpad doesn't do.<br>
<br>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>+1000 I don’t want to see Storyboard changing scope to the point where it doesn’t adequately deliver because it is trying to solve too many problems in the first iteration.</div>
<div><br>
</div>
<div>mark</div>
</body>
</html>