<br><font size=2 face="sans-serif">Situations like this are always interesting
to watch. :-)</font>
<br>
<br><font size=2 face="sans-serif">On the one hand its open-source, so
if you care about something then put up the resources to make it happen.</font>
<br><font size=2 face="sans-serif">On the other hand, that doesn't mean
that as a developer you get to ignore the bigger picture and only do 1/2
of the work because you don't care about the other 1/2.</font>
<br>
<br><font size=2 face="sans-serif">Overall, I tend to agree with the attitude
that as long as XML is officially supported then all code changes need
to make sure they run through both the JSON and XML codepaths. And if this
means twice the testcases then so be it. People committing code shouldn't
have a choice in this - its either you do the full job or your code is
rejected.</font>
<br>
<br><font size=2 face="sans-serif">Having said that, it is a valid question
to ask whether we want to continue to support both JSON and XML going forward.
But, until that decision is formally made letting 1/2 of the APIs
atrophy makes the entire community look bad and therefore should not be
allowed to happen. </font>
<br>
<br><font size=2 face="sans-serif">My vote: from now on don't let any code
change in unless if works for both. I suspect we'll either see the
XML side come up to speed really quickly or it'll force an ugly vote. But
either way, this needs to be resolved before the next release.</font>
<br><font size=2 face="sans-serif"><br>
thanks<br>
-Doug<br>
________________________________________________________<br>
STSM | Standards Architect | IBM Software Group<br>
(919) 254-6905 | IBM 444-6905 | dug@us.ibm.com<br>
The more I'm around some people, the more I like my dog.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>George Reese <george.reese@imaginary.com></b>
</font>
<p><font size=1 face="sans-serif">08/09/2012 07:02 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
OpenStack Development Mailing List <openstack-dev@lists.openstack.org></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">OpenStack Development Mailing List <openstack-dev@lists.openstack.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">"openstack@lists.launchpad.net
\(openstack@lists.launchpad.net\)" <openstack@lists.launchpad.net></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [openstack-dev] [nova] Call for
Help -- OpenStack API XML Support</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>And this is why I go off on the developer-oriented mentality
of the OpenStack community.</font>
<br>
<br><font size=3>The fact that there is no one in the OpenStack developer
community writing XML stuff is not a reflection of the fact that there's
no huge desire for XML.</font>
<br>
<br><font size=3>It's in the spec for a reason: BECAUSE ENTERPRISES USE
XML HEAVILY</font>
<br>
<br><font size=3>OpenStack developers aren't that audience. They use JSON.</font>
<br>
<br><font size=3>That the project can get to this point and not have tests
for these things shows a flaw in the development processes, not some grand
illustration of supply and demand.</font>
<br>
<br><font size=3>Do I really have to point out that if the spec calls for
JSON and XML, you should bloody well write integration tests to check for
JSON and XML?</font>
<br>
<br><font size=3>You don't write whatever happens to please you.</font>
<br>
<br><font size=3>You know how I know all of this? I have an API that supports
both XML and JSON. I personally prefer JSON. Most of my friends and colleagues
prefer and use JSON.</font>
<br>
<br><font size=3>Most of my customers use XML.</font>
<br>
<br><font size=3>Thank $deity I actually write unit tests for each format.</font>
<br>
<br><font size=3>-George</font>
<br>
<br><font size=3>File under:</font>
<br><font size=3>-> statistics 101</font>
<br><font size=3>-> software development 101</font>
<br>
<br><font size=3>On Aug 9, 2012, at 5:52 PM, Vishvananda Ishaya <</font><a href=mailto:vishvananda@gmail.com><font size=3 color=blue><u>vishvananda@gmail.com</u></font></a><font size=3>>
wrote:</font>
<br>
<br>
<br><font size=3>On Aug 9, 2012, at 3:32 PM, George Reese <</font><a href=mailto:george.reese@imaginary.com><font size=3 color=blue><u>george.reese@imaginary.com</u></font></a><font size=3>>
wrote:</font>
<br>
<br><font size=3>Why aren't the integration tests both XML and JSON?</font>
<br>
<br><font size=3>The simple answer is that no one has taken the time to
write them. Our devstack exercises use the python client bindings. Tempest
has json clients but no xml clients[1]. I think this demonstrates that
there just isn't a huge desire for xml. Users that I have chatted with
just seem to care that the api works and that they they have good bindings.</font>
<br>
<br><font size=3>I am definitely willing to be proven wrong on this point,
but I'm secretly hoping everyone agrees with me. It is a lot of work to
maintain three APIs (we are still maintaining EC2 as well) and keep them
all functioning well, so if people are happy without OpenStack XML I would
be perfectly content to deprecate it.</font>
<br>
<br><font size=3>Vish</font>
<br>
<br><font size=3>[1] </font><a href=https://github.com/openstack/tempest/tree/master/tempest/services/nova/xml><font size=3 color=blue><u>https://github.com/openstack/tempest/tree/master/tempest/services/nova/xml</u></font></a>
<br>
<br><font size=3>_______________________________________________<br>
OpenStack-dev mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org"><font size=3 color=blue><u>OpenStack-dev@lists.openstack.org</u></font></a><font size=3><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font>
<br>
<br><font size=3>--</font>
<br><font size=3>George Reese (</font><a href=mailto:george.reese@imaginary.com><font size=3 color=blue><u>george.reese@imaginary.com</u></font></a><font size=3>)<br>
t: @GeorgeReese m: +1(207)956-0217
Skype: nspollution<br>
cal: </font><a href=http://tungle.me/GeorgeReese><font size=3 color=blue><u>http://tungle.me/GeorgeReese</u></font></a><font size=3>
</font>
<br>
<br><font size=3><br>
</font>
<br><tt><font size=2>_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</font></tt>
<br>