<html><body>
<p><tt><font size="2">Clint Byrum <clint@fewbar.com> wrote on 04/11/2013 12:55:39 PM:<br>
> Excerpts from Doug Davis's message of 2013-04-10 05:27:54 -0700:<br>
> > <br>
> > +1<br>
> > <br>
> > I believe that the core of Heat should, for the most part, remain pretty<br>
> > agnostic<br>
> > to the format of the deployment descriptions.<br>
> > <br>
> > There will be a bit of pain for users of Heat for a while until the dust<br>
> > settles and<br>
> > the community gravitates towards the preferred format. But I'd prefer to<br>
> > let the users<br>
> > and the community decide the winner instead of just us doing it right now.<br>
> > <br>
> <br>
> Right, I am most concerned with deciding on our principles, not on<br>
> trying to crown a king. If a user shows up with an entirely new way to<br>
> drive Heat, but it does not compromise Heat, I think we should be quite<br>
> enthusiastic about accepting it into Heat.<br>
> <br>
> There is a side concern, which is that Heat's documentation will need to<br>
> focus on one standard for the sake of user education and for gathering<br>
> steam around the format we think will benefit the broadest base of users.<br>
> This isn't to the exclusion of others, but without that kind of focus,<br>
> users will get frustrated.<br>
</font></tt><br>
<tt><font size="2">Even if there is one 'main' format and docs, I think it would be incumbent</font></tt><br>
<tt><font size="2">upon anyone suggesting an alternative format to also include the docs that</font></tt><br>
<tt><font size="2">go along with it. New format w/o docs should be rejected... the same way</font></tt><br>
<tt><font size="2">it should be rejected if its lacking tests, etc... </font></tt><br>
<br>
<tt><font size="2">-Doug</font></tt><br>
<tt><font size="2"><br>
> Maybe TOSCA is a great way to bring large scale applications and<br>
> enterprise users into Heat, but that may be too heavy and narrow focus<br>
> for Heat to push as "the way to learn Heat".<br>
> <br>
> <br>
> Clint Byrum<br>
> HP Cloud Services</font></tt></body></html>