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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 highlighted the need for a mission statement/elevator pitch/mantra
that we can repeat to
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
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
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
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
--
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
20 matches
Mail list logo
