15:59:58 <cdent> #startmeeting api-wg
15:59:59 <openstack> Meeting started Thu May 18 15:59:58 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:02 <openstack> The meeting name has been set to 'api_wg'
16:00:13 <cdent> #link agenda https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
16:00:15 <dtantsur> o/
16:00:19 <elmiko> hi
16:00:21 <cdent> who is here for the api-wg meeting?
16:00:44 <cdent> mtreinish you said you wanted a ping, so here it is
16:00:56 <cdent> #topic previous meeting action items
16:01:02 <cdent> #link http://eavesdrop.openstack.org/meetings/api_wg/2017/
16:01:31 <cdent> #link minutes from last http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-05-04-16.00.html
16:02:13 <cdent> there were no action items, some of us went to a summit
16:02:24 <cdent> edleafe are you listening in from your airport?
16:02:39 <cdent> #topic open mic and new biz
16:02:48 <cdent> #link discovery https://review.openstack.org/#/c/459405/7
16:03:15 <cdent> mordred has a large collection of fairly complex documents describing how to use the service catalog, do version discovery and attend to the concept of aliases in the service types authority
16:03:49 <cdent> anyone who hasn't had a chance to look at that stuff yet should set aside some time and a beverage and give it a good read
16:03:53 <elmiko> yeah, looks cool, but i need to devote some time for a serious read
16:04:02 <dtantsur> it's so big I cannot force myself into reading it properly..
16:04:08 <dtantsur> yeah, this
16:04:19 <cdent> it sets out some good ideas and places a lot of stuff in context that might be missing people in the past
16:04:59 <cdent> it also represents a slight change of focus from the old standbys of api-wg guidelines, towards also specifying how clients ought to behave in certain circumstances
16:05:07 <cdent> at summit this was declared a GoodThing™
16:05:22 <cdent> which segues nicely to:
16:05:31 <cdent> #link BOF etherpad https://etherpad.openstack.org/p/BOS-API-WG-BOF
16:05:45 <cdent> that's the etherpad from the BOF, which records some of the feedback we got there
16:06:00 <cdent> I thought it was a good session, would you agree elmiko ?
16:06:05 <elmiko> definitely!
16:06:14 <elmiko> great number of people showed up and good participation
16:06:25 <elmiko> much different than the last api-wg bof we had
16:06:53 <cdent> indeed
16:07:13 <elmiko> i liked seeing some new faces too
16:07:28 <cdent> indeed to that too
16:07:52 <cdent> I haven't fully digested that etherpad to extract any actions, have you?
16:08:18 <elmiko> not really
16:08:20 <cdent> (other than the action asettle made
16:08:30 <cdent> which is to get more links to api-wg guidelines from docs
16:08:47 <cdent> and a need to enhance visibility
16:09:15 <cdent> I came away with a bit of "keep up the good work" kind of feeling, which was great
16:09:23 <elmiko> we get a lot of that though
16:09:37 <elmiko> i think one thing we should focus on is getting the link to the specs into more doc locations
16:09:42 <cdent> yes
16:10:01 <elmiko> i'm not sure what exactly we need to do, aside from open PRs on the doc repos, but well, yeah..
16:10:03 <asettle> cdent: heh what?
16:10:09 <asettle> Oh right
16:10:10 <asettle> Api
16:10:11 <asettle> Guidelines
16:10:12 <asettle> Yes
16:10:16 <asettle> Lemme write that down
16:10:16 * elmiko waves at asettle
16:10:19 <elmiko> hehe
16:10:20 <asettle> Hey elmiko !
16:10:31 <asettle> Awkward timing, docs meeting now too
16:10:35 <dtantsur> I wonder if there is something that project-specific api-ref's can add
16:10:37 <asettle> Do you guys have any informal stuff written down?
16:10:39 <elmiko> ouch, just our luck
16:10:44 <cdent> and I suspect we can do more to make the existing guidelines fresh and visible (probably by re-reviewing them periodically)
16:10:47 <dtantsur> like, links to API versioning..
16:10:51 <elmiko> asettle: not yet
16:11:00 <cdent> dtantsur: there was talk of that: getting api-ref to have links to guidelines
16:11:16 <elmiko> that seems much longer tail to me
16:11:30 <elmiko> in the short term, we could get more visibility into the developer.openstack.org stuff
16:12:53 <asettle> elmiko: might be good to have something ... just some notes?
16:13:22 <cdent> asettle: when you said "informal stuff written down" what kind of stuff did you mean?
16:13:35 <cdent> the only notes we've got from summit is the etherpad: https://etherpad.openstack.org/p/BOS-API-WG-BOF
16:14:04 <elmiko> yeah, i guess that's about as informal as it gets
16:14:20 <elmiko> aside from a beer soaked napkin with scrawl on it i suppose XD
16:15:19 <cdent> can we enumerate any actions or shall we take reading monty's novels as our next big step and wait and see otherwise?
16:15:34 <asettle> cdent: sorry, I'm half in and half out. Hhaha I mean any informal notes on the actual guidelines.
16:15:52 <asettle> Or official stuff, whatever you've got, really. A basis for us to begin forming the guidelines to link to the docs stuff
16:15:53 <elmiko> i'm +1 for reading monty's stuff as an action for next week
16:16:00 <elmiko> i really can't load much more than that, saly
16:16:03 <elmiko> sadly...
16:16:23 <cdent> asettle: so the guidelines live here: http://specs.openstack.org/openstack/api-wg/
16:16:47 <cdent> there's no continuity between then, which I kind of think is something that could be improved
16:17:14 <elmiko> that's a nice idea
16:17:16 <asettle> cdent: ah thats the link I was missing.
16:17:37 <asettle> cdent: let me take a look at this post-doc meeting :)
16:17:40 <asettle> Sorry to be a bit scattered
16:17:55 * edleafe forgot about the api-wg meeting
16:17:59 <cdent> asettle++
16:18:11 <edleafe> much more interesting than CNN on the airport TV
16:18:44 <elmiko> edleafe++
16:19:55 <cdent> any other new business?
16:20:49 <cdent> okay moving on
16:21:00 <cdent> #topic guidelines
16:21:08 <cdent> #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
16:21:45 <cdent> https://review.openstack.org/#/c/446138/ needs more votes from those us currently here
16:21:51 <cdent> before it is freezeworthy
16:22:06 <elmiko> yeah, was just thinking that
16:22:09 <elmiko> i'll have a read now
16:23:52 <cdent> while that's happening I'll bump us ahead to bug review to say:
16:23:55 <cdent> there are no new bugs
16:24:27 <elmiko> that guideline look sensible to me
16:24:55 <elmiko> the date thing raised an eyebrow for me, but given that it's useful and optional i don't see an issue
16:25:13 <cdent> dtantsur: you had a chance to think more about that one?
16:25:29 * edleafe has a chatty woman sitting near him. Heading off and may not rejoin
16:25:59 <cdent> stranger danger!
16:26:05 <elmiko> LOL
16:26:39 <dtantsur> cdent: nope, I'll check it again
16:26:47 <cdent> cool, thanks
16:27:40 <cdent> we seem to have breezed through this meeting rather quickly. elmiko are you feeling overwhelming urges to do the newsletter or shall I?
16:28:39 <elmiko> cdent: please, don't let me stop you D
16:28:41 <elmiko> XD
16:28:51 <cdent> mmmkay
16:28:57 <elmiko> can't believe that worked!
16:29:04 * cdent shrugs
16:29:07 <elmiko> hehe
16:29:09 <cdent> I'm a pushover or something
16:29:17 <elmiko> no way...
16:29:33 <cdent> Shall we end it then, and I'll ping for a proof?
16:29:38 <cdent> Any last words from anyone?
16:29:44 <elmiko> sounds good
16:29:54 <mordred> ugh. /me keeps missing the start of this meeting
16:30:11 <elmiko> we've got time mordred, if you want to raise an issue =)
16:30:11 <cdent> mordred: no worries you're already giving us enough work
16:30:22 <elmiko> oh wait
16:30:26 <mordred> looks like y'all talked about me already :)
16:30:31 <dtantsur> mordred: we liked your writing so much that we decided that you'll be writing all our specs from now on
16:30:36 <elmiko> #action everyone read mordred's specs before next meeting
16:30:44 <cdent> spec boy!
16:30:48 <elmiko> LOL
16:32:21 <elmiko> #link https://review.openstack.org/#/q/project:openstack/api-wg+owner:mordred+status:open
16:34:02 <cdent> if nothing else, I'm calling it
16:34:05 <cdent> one
16:34:08 <cdent> two
16:34:11 <cdent> three
16:34:14 <cdent> #endmeeting