Re: [openstack-dev] The API WG mission statement

2015-02-13 Thread Everett Toews
On Feb 12, 2015, at 9:29 AM, Ryan Brown rybr...@redhat.commailto:rybr...@redhat.com wrote: On 02/10/2015 08:01 AM, Everett Toews wrote: On Feb 9, 2015, at 9:28 PM, Jay Pipes jaypi...@gmail.commailto:jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 02/02/2015 02:51 PM, Stefano Maffulli

Re: [openstack-dev] The API WG mission statement

2015-02-12 Thread Ryan Brown
On 02/10/2015 08:01 AM, Everett Toews wrote: On Feb 9, 2015, at 9:28 PM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 02/02/2015 02:51 PM, Stefano Maffulli wrote: On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote: To converge the OpenStack APIs to a consistent and

Re: [openstack-dev] The API WG mission statement

2015-02-10 Thread Everett Toews
On Feb 9, 2015, at 9:28 PM, Jay Pipes jaypi...@gmail.commailto:jaypi...@gmail.com wrote: On 02/02/2015 02:51 PM, Stefano Maffulli wrote: On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote: To converge the OpenStack APIs to a consistent and pragmatic RESTful design by creating guidelines that

Re: [openstack-dev] The API WG mission statement

2015-02-09 Thread Jay Pipes
On 02/02/2015 02:51 PM, Stefano Maffulli wrote: On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote: To converge the OpenStack APIs to a consistent and pragmatic RESTful design by creating guidelines that the projects should follow. The intent is not to create backwards incompatible changes

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread michael mccune
On 02/02/2015 08:58 AM, Chris Dent wrote: This is pretty good but I think it leaves unresolved the biggest question I've had about this process: What's so great about converging the APIs? If we can narrow or clarify that aspect, good to go. +1, really good point The implication with your

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread michael mccune
On 02/02/2015 02:51 PM, Stefano Maffulli wrote: To improve developer experience converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow, avoids introducing

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread Everett Toews
On Feb 3, 2015, at 10:07 AM, michael mccune m...@redhat.com wrote: On 02/02/2015 08:58 AM, Chris Dent wrote: This is pretty good but I think it leaves unresolved the biggest question I've had about this process: What's so great about converging the APIs? If we can narrow or clarify that

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread michael mccune
On 02/03/2015 01:49 PM, Everett Toews wrote: I think where we want to focus our attention is: * strict adherence to correct HTTP * proper use of response status codes * effective (and correct) use of a media types * some guidance on how to deal with change/versioning * and _maybe_ a standard

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread Kevin L. Mitchell
On Tue, 2015-02-03 at 18:49 +, Everett Toews wrote: I’ll echo Mike’s sentiment that we should be very mindful of the idea that these are guidelines not hard standards. H…even that might be a bit restrictive. In the Openstack HTTP error codes [1] discussion I’m getting the impression

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread Chris Dent
On Tue, 3 Feb 2015, Everett Toews wrote: On Feb 3, 2015, at 10:07 AM, michael mccune m...@redhat.com wrote: On 02/02/2015 08:58 AM, Chris Dent wrote: I think where we want to focus our attention is: * strict adherence to correct HTTP * proper use of response status codes * effective (and

Re: [openstack-dev] The API WG mission statement

2015-02-03 Thread Dean Troyer
On Tue, Feb 3, 2015 at 1:19 PM, michael mccune m...@redhat.com wrote: that's something i hadn't thought about, the process behind a list of this sort. i don't mind having this list as a starting point, but i also agree with Everett for the need to establish an open and transparent working

Re: [openstack-dev] The API WG mission statement

2015-02-02 Thread Stefano Maffulli
On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote: To converge the OpenStack APIs to a consistent and pragmatic RESTful design by creating guidelines that the projects should follow. The intent is not to create backwards incompatible changes in existing APIs, but to have new APIs and

Re: [openstack-dev] The API WG mission statement

2015-02-02 Thread Ryan Brown
On 01/30/2015 06:18 PM, Dean Troyer wrote: On Fri, Jan 30, 2015 at 4:57 PM, Everett Toews everett.to...@rackspace.com mailto:everett.to...@rackspace.com wrote: What is the API WG mission statement? It's more of a mantra than a Mission Statement(TM): Identify existing and future

Re: [openstack-dev] The API WG mission statement

2015-02-02 Thread Chris Dent
On Fri, 30 Jan 2015, Everett Toews wrote: To converge the OpenStack APIs to a consistent and pragmatic RESTful design by creating guidelines that the projects should follow. The intent is not to create backwards incompatible changes in existing APIs, but to have new APIs and future versions of

Re: [openstack-dev] The API WG mission statement

2015-01-30 Thread Everett Toews
On Jan 30, 2015, at 4:57 PM, Everett Toews everett.to...@rackspace.com wrote: Hi All, Something we in the API WG keep bumping into are misconceptions around what our mission really is. There’s general agreement in the WG about our mission but we haven’t formalized it. It’s really

Re: [openstack-dev] The API WG mission statement

2015-01-30 Thread Dean Troyer
On Fri, Jan 30, 2015 at 4:57 PM, Everett Toews everett.to...@rackspace.com wrote: What is the API WG mission statement? It's more of a mantra than a Mission Statement(TM): Identify existing and future best practices in OpenStack REST APIs to enable new and existing projects to evolve and

Re: [openstack-dev] The API WG mission statement

2015-01-30 Thread Jeremy Stanley
On 2015-01-30 17:18:00 -0600 (-0600), Dean Troyer wrote: [...] Identify existing and future best practices in OpenStack REST APIs to enable new and existing projects to evolve and converge. [...] I'm shuddering at the anti-term best practices there. How about ideals instead? More shorter means

Re: [openstack-dev] The API WG mission statement

2015-01-30 Thread Dean Troyer
On Friday, January 30, 2015, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-01-30 17:18:00 -0600 (-0600), I'm shuddering at the anti-term best practices there. How about ideals instead? More shorter means more twittable too, right? I'd buy that even if it costs a buzzword point. dt --

Re: [openstack-dev] The API WG mission statement

2015-01-30 Thread Jeremy Stanley
On 2015-01-30 18:25:43 -0600 (-0600), Dean Troyer wrote: I'd buy that even if it costs a buzzword point. The Vancouver summit needs buzzword bingo as a social event. -- Jeremy Stanley __ OpenStack Development Mailing List