16:00:15 #startmeeting api wg 16:00:20 Meeting started Thu Oct 20 16:00:15 2016 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:25 The meeting name has been set to 'api_wg' 16:00:25 #chair cdent elmiko etoews 16:00:26 Current chairs: cdent elmiko etoews 16:00:35 #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda 16:00:45 hey 16:00:55 hey 16:01:20 #topic previous meeting action items 16:01:26 let's see what we had last time 16:02:02 #link http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-10-13-16.00.txt 16:02:09 looks like they both got done 16:02:40 #topic open mic 16:03:05 not sure if cdent is available, but here is a pad with ideas for barcelona bof meetup 16:03:12 #link https://etherpad.openstack.org/p/api-wg-ocata-bof 16:03:14 o/ 16:03:15 * cdent waves from behind other meeting headphones 16:03:26 * elmiko waves back 16:03:32 looking for input (pro and con) on that 16:03:38 cool 16:03:43 * elmiko reads over the list 16:04:56 cdent: is that a 40min session? 16:05:24 elmiko: i think so, I suspect it will end up like tokyo, not vancouver 16:05:30 in which case it will go much more free form 16:05:34 right 16:05:46 i think that's a fine list of topics 16:06:10 cdent: do you know if the usability study comes before or after the bof? 16:06:26 usability is monday morning, I won't be there 16:06:32 don't get in until monday afternoon 16:06:39 * edleafe wanders in late 16:07:01 i think piet_ has some ideas on maybe doing some other interviews later in the year 16:07:01 s/year/week/ 16:09:19 cdent: okay. either way it might be worth mentioning the study in the bof. just to let people know it happened and something? might come of it. 16:09:34 can you stick that on the etherpad please? 16:09:47 (as a memory aid) 16:09:53 yep 16:11:40 and speaking of the study 16:11:42 #link https://etherpad.openstack.org/p/osux-api-oct2016 16:12:43 i'm not sure if there is more to discuss about the study, but folks should take a look and add questions they might have 16:13:49 ok, so there is another topic in the open mic section 16:13:54 i'm not sure who added this 16:14:05 "should we put API porcelain in our domain?" 16:14:22 #help 16:14:33 hmm, i thought there was a way to do sub-topics 16:14:50 #info should we put API porcelain in our domain? 16:15:21 any comments on this? 16:16:22 Not sure what exactly that would entail 16:16:32 i have no idea what that is really. something cdent put there. i think we can skip it for now. 16:16:43 k 16:16:52 #topic guidelines 16:17:00 #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z 16:17:08 do we have anything new? 16:17:34 etoews: mind taking a look at https://review.openstack.org/#/c/388576/ 16:17:42 that's a simple change 16:18:28 workflow+1 16:18:29 probably need a few more eyes on edleafe's change 16:18:32 #link https://review.openstack.org/#/c/386614/ 16:21:16 +1'd 16:22:07 same 16:22:32 i agree with cdent's comments on that review, should we go around one more time then freeze or just bring it as-is to the wider community? 16:22:52 i'd say as-is 16:22:57 k 16:23:09 i can add the +2 freeze notice on it 16:23:10 elmiko: it felt more like application design than API 16:23:23 (cdent's remark) 16:23:26 yeah, that makes sense 16:25:02 this one looks like it's getting good traction as well 16:25:05 #link https://review.openstack.org/#/c/383862/ 16:25:35 elmiko: yeah, was just reading that one now 16:26:06 what's the standard for wrapping URLs in specs? 16:26:30 Specifically, lines 137-9 bother me as written 16:26:40 will they generate a usable URL when rendered? 16:26:52 i think that should be a single line 16:27:10 i'm not sure if the linter will reject that though 16:27:18 same issue on L160 as well 16:27:28 yep 16:27:46 I know that commit messages permit long lines for URLs 16:27:50 content-wise, i'm ok with that 16:28:04 Not sure about the .rst, though 16:28:26 imo, add a comment about it, and we can always move to freeze next week 16:28:35 (or week after, since it's summit) 16:31:38 ok, i added a -1 with some questions on that 16:31:41 Hmmm... looking at api-docs.rst, line 27 has a long URL and it merged 16:32:03 ack, thanks for doing the legwork 16:33:18 Should I comment on the patch, or just unwrap it myself? 16:34:04 good question 16:34:28 i don't mind giving Milan some time to fix it, but i don't think it's a big deal if you unwind it 16:34:45 (i haven't met Milan) 16:34:56 Yeah, I typically do that for Nova when it's a trivial fix like that 16:35:05 that's fair 16:35:37 Heh, line 23 of that file is already a long URL 16:35:42 lol 16:37:17 Done. Also included an explanation 16:37:29 yeah, thanks. added my +1 16:37:42 i think we could probably propose that for freeze as well 16:37:48 agreed 16:37:58 cdent, etoews, could you take a quick look https://review.openstack.org/#/c/383862 16:39:45 ok, assuming that it passes the checks i'll move to freeze it at the end of the meeting 16:39:53 #topic bug review 16:39:59 #link https://bugs.launchpad.net/openstack-api-wg 16:40:07 looks like we are still at 18 bugs 16:41:00 * etoews looks 16:41:14 i think cdent added a bug to fill the one i fixed 16:41:19 XD 16:41:19 that's the same number, but not the same bugs 16:41:24 right 16:43:27 anything to say about the bugs? 16:44:54 #topic APIImpact 16:45:01 #link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z 16:45:14 anyone around who wants to highlight an APIImpact review? 16:47:41 ok then 16:47:45 #topic weekly newsletter 16:48:16 cdent, etoews, either of you have bandwidth for the newsletter? 16:48:46 not really, sorry 16:48:47 ugh. not at all. 16:48:51 lol 16:48:55 k, i'll take care of it 16:48:56 * etoews apologies profusely 16:49:01 no worries 16:49:12 just figured i'd make the offer ;) 16:49:15 sorry i've barely been present at this meeting 16:49:17 etoews: so canadian of you :) 16:49:39 cdent: elmiko: do we cancel next week due to summitry? 16:49:50 makes sense 16:49:56 yeah, i think so 16:49:59 kk 16:50:16 elmiko: maybe mention that in the newsletter 16:50:19 speaking of which, will everyone here be in Barcelona? 16:50:23 nope 16:50:27 not me =( 16:50:38 i'll be in seville about 3 weeks later lol 16:51:15 elmiko: that doesn't count, but it's pretty cool nonetheless 16:51:27 hehe =) 16:51:34 apachecon eu 16:51:35 Sorry that you all won't be there 16:51:41 yeah, would have been fun 16:52:39 have a good time! 16:52:44 thanks, you too! 16:52:54 I plan on it! :) 16:53:02 ok, i'm gonna close out the meeting and spend the last few minutes doing the newsletter 16:53:05 any last words? 16:53:33 (sounds so ominous) 16:53:41 thanks everybody! 16:53:43 #endmeeting