00:00:09 #startmeeting api wg 00:00:10 Meeting started Thu Aug 6 00:00:09 2015 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 00:00:13 The meeting name has been set to 'api_wg' 00:00:32 hi 00:02:13 anyone around....? 00:02:50 \o 00:02:55 hey ryansb 00:03:02 just you and me so far 00:03:06 I see 00:03:38 although, since you're here 00:03:43 was going to get an opinion on https://review.openstack.org/#/c/186526/, since we have -1s on it should I update the patch? 00:03:44 this one #link https://review.openstack.org/#/c/186526/ 00:03:47 haha 00:03:52 lolol 00:04:13 yea, i think so. there was some good feedback from the cross project meeting 00:04:23 so anyways, is there an "unfreeze" process, or should I just go for it 00:04:33 yea, i'd say update away 00:04:40 then we will run it up the flag pole again 00:04:59 kk 00:05:17 some of the suggestions/questions were about maybe creating an example based on keystone, any advice about registering the headers, and also advice on migrating currently used headers 00:05:34 i think folks were really hung up on the idea that we are telling folks not to use X- 00:05:41 which i don't think we are, per se 00:05:57 but like, X-Auth-Token was a big case in point 00:06:08 due to the collisions? 00:06:49 well, just the thought about should projects now attempt to migrate away from their X-My-Header stuff 00:06:57 yeah, we're saying "it lacks the prior semantic meaning" 00:07:03 not "never use it" 00:07:10 yea, exactly 00:07:17 i think that point may have been too subtle 00:07:26 so yeah, I'll spin a new patch that's a bit clearer on that front 00:07:41 also, guidance on what to do if your project already uses something like X-foo-bar 00:08:01 like, should you consider moving to OpenStack-foo-bar 00:08:15 and if so, how is that accomplished 00:08:34 i'm not sure we need all that in this version of the guidance, but it's food for thought for future versions 00:11:43 hmm, looking at our merge process. we are a little light on details about fixing up something in freeze 00:12:02 but, i think just fix it up and we'll announce it at cross project once it's ready again 00:12:14 and if no -1's then cool 00:13:18 yeahh, so moving is not something that I'd look forward to, just for backward compat 00:13:45 yeah, also next mtg we can see if folks want to flesh that out 00:13:56 ok, it might be worth mentioning something about advising against moving unless there is an api version bump or something? 00:14:01 yeah 00:14:11 ok, i'll leave this on the agenda for next time too 00:14:24 well, i'll change it to reflect the new discussion 00:14:30 works for me 00:14:34 cool 00:15:23 anything else we should discuss? 00:15:32 not that comes to mind 00:15:38 did you have a nice vacation? ;) 00:15:38 #reviewMoreGuidelines 00:15:48 yea, agreed about that 00:16:49 i'm not sure how we can increase the review throughput, maybe i can ping the liaisons again 00:16:59 also, need to talk with etoews once he is back 00:17:01 yeah, I'd go with that 00:17:59 ok, well, thanks for showing up =) 00:18:05 :) 00:18:16 see ya around the campus, as it were 00:18:22 heh, IRC campus 00:18:25 #endmeeting