16:00:45 #startmeeting api-wg 16:00:46 Meeting started Thu Jul 20 16:00:45 2017 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:50 The meeting name has been set to 'api_wg' 16:00:56 #chair edleafe 16:00:58 Current chairs: edleafe elmiko 16:01:16 o/ 16:01:17 \o 16:01:20 hi 16:01:28 #chair cdent 16:01:28 Current chairs: cdent edleafe elmiko 16:01:29 #chair cdent 16:01:30 Current chairs: cdent edleafe elmiko 16:01:33 jinx! 16:01:36 hehe =) 16:01:41 my communism was getting tested over in openstack-tc 16:01:43 i owe you some beverage i suppose 16:01:52 wow, sounds interesting 16:02:19 I don't want to know 16:02:21 just a head's up before we start, i have a hard stop at quarter till the hour 16:02:54 my efforts to model openstack problems as a conflict between labor and rentiers doesn’t quite work 16:03:03 haha 16:03:07 sounds hilarious though 16:03:12 #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda 16:03:20 #topic previous meeting action items 16:03:29 #link http://eavesdrop.openstack.org/meetings/api_wg/2017/ 16:03:56 ok, so we were all supposed to chew on the idea of the ptg review stuff 16:04:13 and due to a stray ":" cdent's action item for me never got committed XD 16:04:21 but, i created a thing anyways 16:04:39 #link https://wiki.openstack.org/wiki/API_Working_Group/Guided_Review_Process 16:04:51 my hope was to get the ball rolling and just throw out a few ideas 16:05:11 * cdent reads 16:05:32 * edleafe reads too 16:06:27 So it sounds like a wider-ranged approach than what I had in mind 16:06:29 "Pick a general area of your API to focus on" 16:06:42 well, that was just my first stab 16:06:49 mmm, interesting. I suspect Ironic could use a review or two 16:06:59 I was thinking more like "pick an API that is causing controversy among team members" 16:07:21 my hope is that interested parties will look at their api, figure out some questions they have about api-wg guidelines, and then start a review 16:07:25 The general approach would be excellent for new APIs, though 16:07:39 edleafe: i agree with the "pick an API..." approach 16:08:21 it is certainly _far_ easier to do a review when there is a known conflict or question 16:08:27 yeah, i tried to hint that teams should pick something a little more specific, but maybe that wasn't clear enough 16:08:36 having people rock up and say “do you like our api” is hard to get any leverage 16:08:42 totally 16:09:20 so, maybe #1 should say "pick a specific part of your API" instead? 16:09:20 "No, your API sucks. Next!" 16:09:23 LOL 16:09:24 lol 16:09:40 edleafe: come on, cdent would be way more tactful than that! 16:09:41 reserve a slot or two for us, we have a few long-standing problems 16:10:08 dtantsur: you're first in line apparently =) 16:10:16 good :) 16:10:36 bear in mind, this is just a proposal at this point 16:10:45 sure, sure :) 16:10:55 Could we say “priority will be given to those applicants who are trying to make a choice between two or more options…” 16:11:52 or “if you come to us with some choices, it will be like so much easier…” 16:11:55 i will certinaly go back and make it more clear that teams with specific requests will be given priority over general "is it gud?" questions 16:12:08 Oooh... I like it! Makes it sound like there will be a line down the hallway waiting to get in 16:12:14 right 16:12:40 makes no sense to spend an entire session look at one entire api when we could answer several smaller questions in the same time 16:12:43 r i gud? u r gud. 16:12:50 exactly 16:13:17 they’re good apis lmeeeko 16:13:24 would it be easier to review and collaborate on this document if i try to make it a review in gerrit to the specs repo or something? 16:13:25 LOL 16:13:49 yeah, elmiko, we can make it a sort of guideline itself 16:13:49 ++ for a review for anything 16:13:54 indeed, they are... /me pats on head gently 16:14:05 ok 16:14:08 no, not a guideline - those get permanently published 16:14:19 just a note of some sort 16:14:23 yeah 16:14:34 like one of the extra docs we have on the specs repo 16:15:02 hmm 16:15:17 i thought about this while writing it, that wiki is terrible for collaborating with review 16:15:26 but i wanted to get something started 16:15:44 I was thinking that permanently published is a good thing: as in “this is a thing we do at ptgs” 16:15:58 when ptgs stop or we stop going to ptgs, then the guideline can be marked dead 16:16:28 so, how about this: 16:16:48 #action elmiko investigate moving the wiki guided review document into gerrit, somehow 16:16:56 yes 16:17:06 ack 16:18:03 kewl 16:18:11 ok, then, any more on this topic? 16:18:36 #topic open mic and new biz 16:18:49 nothing on the agenda, any new biz to bring up? 16:19:02 not from me 16:19:15 nor me, this phase of the cycle is very project oriented 16:19:32 cool 16:19:33 #topic guidelines 16:19:40 #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z 16:19:50 was there any movement since last meeting? 16:20:09 looks like we're still waiting 16:20:14 I admit to not having spent much time on any of those 16:20:27 likewise, i used up my time last week writing the doc =( 16:21:00 I looked a couple days ago, and the main thing is mordred’s stuff and he’s actively implementing some of it in ksa at the moment, so productively distracted 16:21:26 got it 16:21:47 ok, so for now we're kinda in a holding pattern unless we get some new work 16:22:13 yes 16:22:23 #topic bug review 16:22:36 i'm guessing same story here, albeit with different main characters ;) 16:23:05 #link https://bugs.launchpad.net/openstack-api-wg 16:23:50 at some point, maybe we should do a bug triage or something just to make sure all these are still relevant 16:24:18 possibly plan a meeting to be a bug triage meeting and just spend the hour going through the list? 16:24:21 that’s a good idea, but I don’t reckon there’s that much of a rush. the last time we did a bug run was to create most of them based on the todo’s in the existing guidelines 16:24:37 ok, i'm good with that too 16:24:56 Yeah, I keep thinking I should grab a TODO every now and then 16:24:57 part of the current malaise is that edleafe and I are too wrapped up in placement related stuff 16:25:02 Then other work gets in the way 16:25:13 i feel ya, work... feh. 16:25:44 i'm more or less completely enmeshed in kubernetes and spark stuff 16:26:19 ok, moving along 16:26:20 #topic weekly newsletter 16:26:26 there will be some surfacing in a week or two? (Im unsure when feature freeze is) 16:26:30 #link https://etherpad.openstack.org/p/api-wg-newsletter 16:26:34 cool 16:26:36 I guess it is probably my turn? 16:26:46 that would be grand, thank you sir 16:26:52 yes, thank you 16:27:02 will ping for a proof 16:27:29 i will try to read it, but i'm doing another meeting after this for like 2 hours 16:27:47 anything else to bring up? 16:27:55 everyone having a good thursday so far? 16:28:01 nothing else to bring 16:28:06 relatively good thursday 16:28:08 many bugs found 16:28:10 nice =) 16:28:14 * edleafe pulls out empty pockets 16:28:17 haha 16:28:36 * elmiko gives edleafe a quarter for a cup of coffee 16:28:46 ok, thanks everybody! 16:28:50 #endmeeting