All 3 API guidelines have merged. Thanks everyone!
Everett
On Apr 22, 2015, at 2:08 PM, Everett Toews wrote:
> Hi All,
>
> We have 3 API Guidelines that are ready for a final review.
>
> 1. Metadata guidelines document
> https://review.openstack.org/#/c/141229/
>
&g
On Apr 30, 2015, at 9:54 AM, Jay Pipes wrote:
> Hi Stackers,
>
> OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova team's
> liaisons to the API working group. Big thank you to Matthew and Alex for
> volunteering for this important role.
>
> I've created a wiki page [1] that
On May 6, 2015, at 1:58 PM, David Kranz
mailto:dkr...@redhat.com>> wrote:
+1
The basic problem is we are trying to fit a square (generic api) peg in a round
(HTTP request/response) hole.
But if we do say we are recognizing "sub-error-codes", it might be good to
actually give them numbers somewh
On May 11, 2015, at 1:05 PM, Dean Troyer
mailto:dtro...@gmail.com>> wrote:
On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services)
mailto:andrea.r...@hp.com>> wrote:
> Agreed. Violating the HTTP spec is something that should be avoided.
Actually it is not violating the HTTP spec, fro
I would like to propose Michael McCune (elmiko) as an API Working Group core.
Among Michael’s many fine qualities:
* Active from the start
* Highly available
* Very knowledgable about APIs
* Committed the guideline template
* Working on moving the API Guidelines wiki page
* Lots of s
Top posting to make it official...Michael McCune (elmiko) is an API Working
Group core!
Cheers,
Everett
On May 11, 2015, at 8:57 PM, Ryan Brown wrote:
> On 05/11/2015 04:18 PM, Everett Toews wrote:
>> I would like to propose Michael McCune (elmiko) as an API Working Group core.
>
> On Mar 9, 2017, at 11:52 AM, Ed Leafe wrote:
>
> Greetings OpenStack community,
>
> Today's meeting started on a heavyhearted note, as we hoisted our virtual
> beers and gave a toast to Everett Toews, who recently had to step down from
> his API-WG duties due to
On Aug 3, 2016, at 12:59 AM, Ramakrishna, Deepti
mailto:deepti.ramakris...@intel.com>> wrote:
Hi,
I would like to bring your attention to my spec [1] (already approved) on
capability APIs and would like to get feedback from API WG.
To summarize, I propose defining a capability API for every r
Greetings OpenStack community,
Our main new topic for today was making sure that we take a more active role in
curating the bugs that are now being kept in launchpad [4] by including review
of those bugs in the workshopping that we do in each meeting. If you find
issues in the existing guidelin
Top posting with general comment...
It sounds like there's some consensus in Nova-land around these traits (née
"capabilities"). The API Working Group [4] is also aware of similar efforts in
Cinder [1][2] and Glance [3].
If these are truly the same concepts being discussed across projects, it w
Subject: [all][api] POST /api-wg/news
Greetings OpenStack community,
Today we were joined by Scott DAngelo (scottda) who has graciously taken over
the liaison role for Cinder as Alex Meade steps down. Thanks for stepping up
Scott and welcome to the API WG!
We also cleaned house today and merge
On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi
mailto:ken1ohmi...@gmail.com>> wrote:
2017-02-06 6:45 GMT-08:00 Brian Rosmaita
mailto:rosmaita.foss...@gmail.com>>:
On 2/6/17 5:51 AM, Jordan Pittier wrote:
[super-enormous snip -- Chris, Ken, and Jordan make good points, I
encourage you to read the
> On Oct 6, 2016, at 10:43 AM, Jeremy Stanley wrote:
>
> On 2016-10-06 10:30:30 -0500 (-0500), Kevin L. Mitchell wrote:
> [...]
>> Problem with that is that ':' is a valid character within an ISO date,
>> though I do like the 'between' prefix. Now, '/' can be used if it's URL
>> encoded, but I
On Oct 13, 2016, at 10:00 AM, Devananda van der Veen
wrote:
>
> So I have finalized five proposals of substantial changes we can make, that
> folks agreed were important to work on, and which I believe we can do within
> the
> microversion framework starting immediately. Four of them will, I th
101 - 114 of 114 matches
Mail list logo
