<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;">
On Feb 9, 2015, at 9:28 PM, Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
<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 02/02/2015 02:51 PM, Stefano Maffulli wrote:<br>
<blockquote type="cite">On Fri, 2015-01-30 at 23:05 +0000, Everett Toews wrote:<br>
<blockquote type="cite">To converge the OpenStack APIs to a consistent and pragmatic RESTful<br>
design by creating guidelines that the projects should follow. The<br>
intent is not to create backwards incompatible changes in existing<br>
APIs, but to have new APIs and future versions of existing APIs<br>
converge.<br>
</blockquote>
<br>
It's looking good already. I think it would be good also to mention the<br>
end-recipients of the consistent and pragmatic RESTful design so that<br>
whoever reads the mission is reminded why that's important. Something<br>
like:<br>
<br>
To improve developer experience converging the OpenStack API to<br>
a consistent and pragmatic RESTful design. The working group<br>
creates guidelines that all OpenStack projects should follow,<br>
avoids introducing backwards incompatible changes in existing<br>
APIs and promotes convergence of new APIs and future versions of<br>
existing APIs.<br>
</blockquote>
<br>
After reading all the mails in this thread, I've decided that Stef's suggested mission statement above is the one I think best represents what we're trying to do.<br>
<br>
That said, I think it should begin "To improve developer experience *by* converging" ... :)<br>
</div>
</blockquote>
<div><br>
</div>
<div>+1 </div>
<div><br>
</div>
<div>I think we could be even more explicit about the audience. </div>
<div><br>
</div>
<div>To improve developer experience *of API consumers by* converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow, avoids introducing backwards incompatible changes
in existing APIs, and promotes convergence of new APIs and future versions of existing APIs.</div>
<div><br>
</div>
<div>I’m not crazy about the term "API consumer" and could bike shed a bit on it. The problem being that alternative terms for "API consumer" have been taken in OpenStack land. “developer” is used for contributor developers building OpenStack itself, “user”
is used for operators deploying OpenStack, and “end user” has too many meanings. “API consumer” makes it clear what side of the API the working group audience falls on.</div>
<div><br>
</div>
<div>I also like dtroyer’s idea of a Tweetable mantra but I think we need to distill that mantra _from_ a longer mission statement. If we constrained the mission statement to <= 140 chars at the outset, we’d be losing valuable information that’s vital in communicating
our intent. And if we can’t fully communicate our intent in a mission statement then it doesn’t have as much value.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Everett</div>
<div><br>
</div>
</div>
</body>
</html>