16:01:11 #startmeeting api wg 16:01:12 Meeting started Thu Oct 22 16:01:11 2015 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:15 The meeting name has been set to 'api_wg' 16:01:33 o/ 16:01:38 o/ 16:02:19 #topic agenda 16:02:26 #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda 16:02:34 seems like we might have a light meeting today 16:02:59 #topic previous meeting action items 16:03:09 #link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-10-08-16.00.html 16:03:21 there was a meeting on the 15th, but no one showed >.< 16:03:52 so, as for action items. i think mine and miguelgrinberg's have been started 16:03:57 * elmiko digs for links 16:04:13 #link https://review.openstack.org/#/c/233729/ 16:04:25 that's for the review on adding more APIImpact info to the docs 16:04:45 #link https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Links 16:04:53 and that is my progress so far on the link analysis 16:05:24 as for #link https://review.openstack.org/#/c/187112 16:05:36 we are still waiting for a response from alex xu 16:06:03 etoews wasn't able to make it today, not sure about his items 16:06:21 and i don't see annegentle 16:06:29 any comments on the action items? 16:07:50 moving on... 16:07:52 #topic summit meetup 16:08:00 nngh 16:08:00 #link https://etherpad.openstack.org/p/mitaka-api-wg-session-plans 16:08:15 cdent has been kinda enough to add a bunch of content to this page 16:09:17 mostly random 16:09:30 yea, but i kinda agree with some of the major overtones 16:09:49 and i hope we can discuss the working group's impact on the community at summit 16:10:04 it would be nice to get some ideas about how we can be more effective in the larger openstack community 16:10:59 yes 16:11:13 I reckon that will be need to be the main topic 16:11:41 probably, and i think we've captured that to some extent in the future plans agenda 16:12:32 #topic guidelines dashboard 16:13:00 i don't think we have any new guidelines that need attention, or are ready for freeze 16:13:20 are there any guidelines that should be highlighted? 16:13:44 miguelgrinberg’s actions one is interesting and probably worthy of some more attention from people other than the three of us 16:13:50 +1 16:14:03 i really like what he's done, but i'm an easy sell ;) 16:15:08 i'm not sure the best path forward, like if we start announcing this guideline to get more attention is that part of a freeze or outside of that 16:15:22 kinda confusing, maybe we should just ensure that it is clean then start the freeze process? 16:15:54 i reckon during the summit season its not going to get much light 16:16:06 right, this will have to be stuff for after summit 16:17:03 ok, moving along then 16:17:10 #topic APIImpact 16:17:30 any reviews we should look at? 16:18:47 #topic open discussion 16:19:03 anything else, or should we take back 40minutes =) 16:19:12 is it just you me and stevelle here today? 16:19:17 i think so 16:19:28 and stevelle has been suspiciously quiet.. ;) 16:19:29 you going to tokyo stevelle ? 16:19:32 I am 16:19:39 cool 16:20:01 this meeting is always double booked with another community meeting 16:20:18 no worries, i'm just goofin around =) 16:20:19 that one is being a bit feisty 16:20:49 i think things have slowed down a bunch for the wg recently anyways, probably good fodder for discussion at summit 16:21:23 ok, well if neither of you has any issues to raise, i say let's end early =) 16:21:30 +1 16:21:50 we could mention the tags thread on the dev list 16:21:59 oh yea! good point 16:22:04 just for those who might read later 16:22:32 * elmiko digs for link 16:22:45 #link http://lists.openstack.org/pipermail/openstack-dev/2015-October/077701.html 16:23:11 i just started looking at this earlier, and without much research i don't see they couldn't use PATCH for a partial update 16:23:37 although, i thought there was a section in the guideline for doing a partial update 16:23:58 there’s been some fussiness about the bodies of PATCH that we’ll need to resolve at some point 16:24:17 yea, that's true 16:24:51 i think the best guidance we had we to either use json-patch *or* just an update json object, but never both! 16:25:22 s/had we/had was/ 16:26:25 maybe we should put “how about those partial updates” on the etherpad 16:26:34 yea, was just thinking something similar 16:26:42 and then that will give us at least one technical thing to bikeshed over 16:26:48 amongst the political things 16:26:50 hmm, good topic 16:27:12 I need to go through the schedule again and make sure I have the WG sessions marked too 16:27:27 k, added to the pad 16:27:50 #link https://mitakadesignsummit.sched.org/event/36e6c27e324044e4b91dd7137b4ef57f 16:30:01 anything else? 16:30:45 ok then, see you in tokyo =) 16:31:07 #endmeeting