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