<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I hesitate to wade into this but here are a few more things to
consider.<br>
<br>
1. As the primary instigator of the recent statement on API
stability, obviously what is documented and/or implemented in the
current API should<br>
continue to work. Whether XML support should be in the core of
future versions is a different story (see below).<br>
<br>
2. I don't know why George insists that "developer laziness" or
"boredom" is responsible for the current situation. If these
developers' employers said XML<br>
was important they would give it more priority. We can only
conclude that there are not many employers saying that to their
employees. Is there any<br>
company invested in OpenStack putting resources on this?<br>
<br>
3. We are talking about nova here. None of the other OpenStack APIs
use XML but I did see some middleware in keystone to translate back
and forth.<br>
<br>
4. Most users of the APIs never want to see unparsed JSON *or* XML.
To them it is<br>
really more a wire protocol and they will either use some
language binding, or write their own, or use the cli.<br>
<br>
This war goes on. Amazon uses XML. The new Google Compute API uses
JSON. These companies have VPs of product management and engineering
and make choices. No matter what the nova team ends up doing
with XML, there are not going to be in-core, spec'd XML bindings for
the other APIs. New projects are not going to implement both. It is
an intriguing possibility that there could be some shared middleware
for translation that could be used by all projects to handle this
issue. OpenStack needs to make choices too. I think the PPB really
needs to consider this issue.<br>
<br>
-David<br>
<br>
<br>
On 8/10/2012 8:21 AM, George Reese wrote:
<blockquote
cite="mid:F67B53F3-F644-4E6C-B850-1ABD9E5A7B8B@imaginary.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Just to be clear on what I mean by the truth…
<div><br>
</div>
<div>You do realize it is 100% unacceptable in any non-clown
development shop to…</div>
<div><br>
</div>
<div>* Not write XML support for an API that is documented as JSON
and XML…?</div>
<div>* Not write test cases for both the JSON and XML…?</div>
<div>* To consider altering the spec of a product in the wild in a
way that breaks compatibility because developers are bored with
the feature…?</div>
<div><br>
</div>
<div>Any one of the above items is clownish. Taken together, they
are representative of a pattern of software engineering defended
largely by the employees of Nebula that is much more offensive
to this project than anything I have ever said.</div>
<div><br>
</div>
<div>But you keep on focusing on what I am saying.</div>
<div><br>
</div>
<div>-George</div>
<div><br>
<div>
<div>On Aug 10, 2012, at 12:28 AM, Mark McLoughlin <<a
moz-do-not-send="true" href="mailto:markmc@redhat.com">markmc@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">On Thu, 2012-08-09 at 18:20 -0500,
George Reese wrote:<br>
<blockquote type="cite">It goes to the complete clown show
that Nebula team is running with<br>
respect to OpenStack development.<br>
</blockquote>
<br>
Tone it down on this list or we'll have to start actively
enforcing our<br>
code of conduct[1]. Do you want to be the first person
censured under<br>
it? We could name the "be respectful" clause after you if
you like?<br>
<br>
These kind of attacks are completely out of line on a
mailing list where<br>
people are trying to work together and get stuff done.<br>
<br>
Mark.<br>
<br>
[1] - <a moz-do-not-send="true"
href="http://wiki.openstack.org/Governance/Foundation/CommunityCodeOfConduct">http://wiki.openstack.org/Governance/Foundation/CommunityCodeOfConduct</a><br>
<br>
</blockquote>
</div>
<br>
<div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse:
separate; color: rgb(0, 0, 0); font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; "><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0);
font-family: Helvetica; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-align: -webkit-auto;
text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px;
-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space; ">
<div>--</div>
<div>George Reese (<a moz-do-not-send="true"
href="mailto:george.reese@imaginary.com">george.reese@imaginary.com</a>)<br>
t: @GeorgeReese m: +1(207)956-0217
Skype: nspollution<br>
cal: <a moz-do-not-send="true"
href="http://tungle.me/GeorgeReese">http://tungle.me/GeorgeReese</a> </div>
<div><br>
</div>
</div>
</span><br class="Apple-interchange-newline">
</span><br class="Apple-interchange-newline">
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>