16:00:28 #startmeeting api wg 16:00:29 Meeting started Thu May 19 16:00:28 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:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:32 The meeting name has been set to 'api_wg' 16:00:34 o/ 16:00:42 hi 16:00:57 do we have any other participants? 16:01:14 excellent question =) 16:02:08 #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda 16:02:26 #topic previous meeting action items 16:02:34 since we didn't meet last week, these are still good 16:02:41 #link http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-05-05-16.00.html 16:02:59 i did mine, and i/think/ etoews covered his as well 16:03:08 yes, I believe he did 16:03:14 cool 16:03:50 hmm, need to groom this agenda slightly 16:05:05 #topic guidelines 16:05:12 #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z 16:05:24 is there anything we need to freeze? 16:05:37 oh hey, there are new things there I hadn't seen yet 16:05:53 we should just merge this https://review.openstack.org/#/c/312970/1 16:06:59 done 16:07:30 thanks 16:07:41 https://review.openstack.org/#/c/312971 16:07:57 that seems easy too, but i like the suggestion 16:08:55 should we put this up for freeze? https://review.openstack.org/#/c/281511 16:09:09 I've fixed 312971 in place 16:09:23 ah, excellent! 16:10:05 so we can probably merge that one too, if you liked to do those honors? 16:10:06 this is probably ready for freeze as well https://review.openstack.org/#/c/301846 16:10:15 sure 16:10:58 ok then 16:11:27 i think we should propose these for freeze, https://review.openstack.org/#/c/301846 , https://review.openstack.org/#/c/281511 16:11:31 on metadata changes, there are still some unresolved comments on etag stuff, but maybe not worth fussing 16:11:43 yea, we might as well put them up 16:11:58 yeah more eyes would be good 16:12:10 do you want to take the action or shall i? 16:13:43 ok, i'll take it ;P 16:13:57 sorry, I'm being a bad multitasker :( 16:14:15 but yes, if you could do the honors that would be great 16:14:15 #action elmiko propose 301846 and 281511 for freeze 16:14:23 no worries, these are pretty low bandwidth actions for me 16:15:38 the other guidelines look like they need some work 16:16:34 #topic weekly email 16:16:49 not sure if we want to dive into this, but i wanted to mention it 16:17:05 agree that other guidelines need work 16:17:24 yeah, weekly email a) great idea b) hard to do 16:17:36 right 16:17:52 i wonder if we could start by coming up with a template or something? 16:18:18 maybe annegentle would share some secrets learned from the "What's up doc" emails =) 16:18:27 heya 16:18:30 =D 16:18:51 we're talking about the possibility of doing a weekly email from the api-wg. any advice you might have to share? 16:18:52 I do think that ML post regularly does help, since people know they can look it up later for a point-in-time. 16:19:50 I think you could have a simple 3-header template. Stuff in progress, stuff to think about and join in the discussion (needs input), status/done. 16:19:56 that's a terrible outline :) 16:20:00 but you hopefully get the gist 16:20:30 do you use a template with the doc emails? 16:20:33 it's a good structure: simple, meaningful 16:20:42 yeah it was simply a text file with headers 16:20:47 super low tech 16:20:48 ok, cool 16:21:15 should we make a wiki page to iterate on the template? 16:21:53 one thing lana moved to was a weekly etherpad update for everyone to add to by a certain day 16:21:58 then she can include that info in the weekly email 16:22:07 ah, nice. that's a good idea 16:22:12 so for docs, it's a specialty team etherpad 16:24:20 ok, so now the tough question. do you want to take this or shall i? (cdent) 16:24:38 probably makes sense for me to drive it for now 16:24:49 unless you want it 16:25:22 elmiko: given your extraction I figured it would have to be me, but given my complete awash in resource providers it being you is nice 16:25:35 * cdent is frusrated 16:25:48 ok, i'll get the ball rolling then we can figure out who does the weekly mails later 16:25:48 so frustrated I'm spelling even worse than usual 16:25:52 haha 16:25:54 +1 16:26:05 #action elmiko setup wiki page with some details about weekly email from api-wg 16:26:08 that sound good? 16:26:24 i'll incorprate an etherpad for suggestions and a template for the email 16:29:04 ossum 16:29:43 ok 16:29:48 #topic APIImpact 16:29:55 #link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z 16:30:22 not sure if we want to address anything, but i want to give for any reviews that lurkers may want to bring up ;) 16:30:23 I'm way behind on these 16:30:27 same 16:30:44 and this is one of the points we have about clarifying how APIImpact is sued 16:30:48 er, used 16:32:00 ok, then 16:32:04 #topic open discussion 16:32:11 anything else we should discuss? 16:32:59 maybe annegentle can give us a crash course in "how to remain engaged in a cross project thing and keep sane and get stuff done" 16:33:07 haha, +1 16:33:27 cdent: no such thing exists :) 16:33:44 edleafe: did you just rise from the ashes? 16:34:05 nah, I've been popping in here while doing 6 other things 16:34:07 music plays, coffin opens, edleafe intones "sorry, mate, no can do" 16:34:23 lol! 16:36:51 shall we reclaim part of the day? 16:37:55 yessir 16:38:38 I promise to become a good api-wg-member asap 16:38:42 cool, take care, see ya next week o/ 16:38:47 hehe, no worries =) 16:38:52 #endmeeting