16:00:20 <etoews> #startmeeting api wg
16:00:20 <openstack> Meeting started Thu Nov 17 16:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is etoews. 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:24 <openstack> The meeting name has been set to 'api_wg'
16:00:33 <etoews> #chair cdent elmiko etoews
16:00:34 <openstack> Warning: Nick not in channel: elmiko
16:00:36 <openstack> Current chairs: cdent elmiko etoews
16:00:41 <edleafe> \o
16:00:54 <cdent> hola
16:00:54 <etoews> hey edleafe
16:00:58 <etoews> #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
16:01:00 <edleafe> hey
16:01:36 <cdent> managed to get off the call
16:01:46 * edleafe too
16:01:48 <etoews> #topic previous meeting action items
16:01:57 <etoews> #link http://eavesdrop.openstack.org/meetings/api_wg/2016/
16:02:37 <etoews> nada
16:02:49 <etoews> #topic open mic
16:03:15 <etoews> #topic negation
16:03:19 <cdent> #link http://markmail.org/message/yr3ex6u6kcv4itty is about negation
16:03:28 <etoews> a markmail link!
16:03:29 <cdent> I have to say that I'm quite pleased with the process happening there
16:03:36 <edleafe> me too
16:03:37 <etoews> haven't seen one of those in a while :)
16:03:39 <cdent> better navigation
16:04:15 <edleafe> it boils down to: clarity vs consistency
16:04:32 <edleafe> not_in => clearer
16:04:45 <edleafe> nin => consistent with neq
16:06:05 * etoews opinion rapidly flip flops between the two
16:06:12 <cdent> rather
16:06:35 <cdent> neq feels like it has global precendent
16:06:41 <cdent> whereas nin, not so sure
16:06:43 <etoews> is there a nout?
16:06:59 * edleafe thinks the Nine Inch Nails reference tilts it towards 'nin'
16:07:48 <cdent> I'm not sure it matters that much, and we can just let the (nice) democratic process prevail, and someone will create the review, potentially further winnowing it
16:08:08 <cdent> I stuck the thread on the agenda when the thread started, to make sure it went somewhere, and it has done a remarkable job of doing so
16:08:15 <etoews> cool
16:08:27 <etoews> i suppose i lean ever so slightly towards to nin
16:08:53 * edleafe flips a coin
16:09:45 <etoews> any action to come out of this? seems like it's covered well enough on the ML and eventual patch
16:10:07 <etoews> maybe one last email to the list to precipitate a patch?
16:10:17 <cdent> yeah ,that sounds right
16:10:34 <etoews> edleafe: care to take that since you're already invested in the thread?
16:10:40 <edleafe> sure
16:10:46 <etoews> thx
16:10:52 <edleafe> I was hoping someone else from the thread would show up
16:11:19 <etoews> #action edleafe to precipitate patch for http://markmail.org/message/yr3ex6u6kcv4itty thread
16:12:12 <cdent> edleafe is silver iodide
16:12:20 <etoews> #topic glance thang
16:12:30 <etoews> glance wants api-wg input on #link https://review.openstack.org/#/c/396919
16:12:40 <etoews> sounds like you jumped on this one cdent
16:13:00 <cdent> yeah, it's in hand, same "in case it didn't get addressed by the time of meeting" as above
16:13:14 <etoews> anything left to do?
16:13:45 <cdent> they've had a few more related topics, mostly to do with language: shared v shareable
16:14:07 <cdent> stuff that is good for beer+api-talk but probably not something we need to concern outselves with at this time
16:14:14 <etoews> kk
16:14:42 <etoews> anything anyone else wants to bring to the open mic?
16:15:11 <edleafe> not from me
16:15:18 * cdent plays some folk guitar
16:15:32 <cdent> this is a little protest song
16:15:35 <etoews> #topic guidelines
16:15:35 <cdent> ec
16:15:44 <etoews> #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
16:15:59 <cdent> pagination is a bit stuck I think
16:16:15 <cdent> capabilities still remains pretty wip but has a lot of eyes on it
16:17:25 <edleafe> the capabilities one sounds like it could open a huge rabbit hole
16:17:47 <cdent> a) yes, b) its supposed to close others c) \o/
16:17:50 <edleafe> iow, if it's there, then every group will feel required to implement it
16:18:12 <edleafe> so +1 for consistent rabbit holes
16:18:17 <edleafe> :)
16:18:41 <cdent> I'm going to go back to it after it settles a bit and restate my original concern: what's the real problem this is solving
16:18:57 <cdent> because at the moment it sounds like a bit solution first oriented
16:19:29 <cdent> but since it has been talked about in various context as a necessary for a long time, I'm probably missing some important details
16:20:51 <edleafe> it's useful when try/fail/react takes too long or is too intensive
16:20:58 <edleafe> but otherwise...
16:22:32 <cdent> neither are ready for wider review, neither are ready for freeze
16:24:02 <etoews> #topic APIImpact
16:24:11 <etoews> #link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z
16:25:41 <etoews> erm...apiimpact is a thing.
16:26:00 <etoews> #topic bug review
16:26:07 <etoews> #link https://bugs.launchpad.net/openstack-api-wg
16:26:18 <etoews> i need to duck out in 4 min
16:26:21 <cdent> nothing new
16:26:23 <cdent> on the bugs
16:26:29 <etoews> cdent: can you finish up the meeting?
16:26:33 <cdent> yessir
16:26:50 * etoews bows
16:27:19 <cdent> I think if there's nothing more to discuss we can probably call it, and I'll do the newsletter (highlighting that we liked the nin/not_in process) sometime before EOD
16:28:06 <cdent> anyone?
16:28:28 <cdent> okay then
16:28:31 <cdent> #endmeeting