16:00:15 #startmeeting api sig 16:00:16 Meeting started Thu Aug 2 16:00:15 2018 UTC and is due to finish in 60 minutes. The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:19 The meeting name has been set to 'api_sig' 16:00:22 #chair cdent elmiko edleafe dtantsur 16:00:23 Current chairs: cdent dtantsur edleafe elmiko 16:00:29 o/ 16:00:31 #link https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda 16:00:34 hey folks =) 16:00:38 geez, just one second before I hit return to start the meeting! 16:00:48 hahaha 16:00:53 * edleafe needs to type faster 16:01:10 it is a sort of free-for-all at the start there 16:01:15 o/ 16:01:26 and here i thought i was waiting before hitting return 16:01:53 #topic previous meeting action items 16:01:54 oh sure, rub it in. We all get it, you can type fast 16:02:00 #link http://eavesdrop.openstack.org/meetings/api_sig/2018/ 16:02:10 in fairness, i just cut and pasted 16:02:17 heh 16:02:27 there, now the secret is out 16:02:51 so, how far did everyone make it through the draft? 16:03:00 I did 16:03:08 * edleafe gives himself a cookie 16:03:13 I read the whole thing 16:03:16 * elmiko gives edleafe another cookie 16:03:25 * edleafe gives cdent a cookie too 16:03:27 i made it about 80% through 16:03:27 I even gossiped about the parts I didn't agree with with someone 16:03:33 * elmiko gives cdent another cookie 16:03:41 ooh, bonus points for cdent ! 16:03:46 ikr 16:03:54 Which parts were those? 16:04:00 The part I didn't agree with was about not using specific 4xx responses 16:04:18 I disagree with a few things, this being one of them 16:04:24 * dtantsur tries to remember 16:05:06 overall the thing did not read like something breaking 16:05:09 I read it nearly a week ago, so the specifics are a bit fuzzy 16:05:22 for the most part, i found it to be quite sane, my concern for us is going through it more closely to ensure that we haven't make guidance that contradicts (assuming we adopt it as a starting point for something) 16:05:27 a lot of "do not", but not much "instead do" 16:05:30 yeah, it wasn't particularly revolutionary, sort of gentle intro to REST with some pragmatism added in 16:05:42 ++ 16:06:17 I think we had something contradicting, but I cannot remember 16:06:23 * dtantsur needs to re-read it 16:06:41 I felt that a large part of our HTTP guidelines could have been replaced with "hey, read this" 16:07:10 I wasn't really expecting it to provide much in the way of guidance for us, more sort of a lemon zesty refresher from the outside world, squeezed upon our staid interiors 16:07:19 that would really help spread the load of our guidance edleafe , i'm ++ 16:07:30 it _would_ be good to link to it 16:07:56 Somehow reading an IETF draft proposal doesn't conjure up "lemon zesty" in my mind 16:07:57 perhaps where we say "in the absence of direct guidance look at the rfcs" we could also say "and this good overview" 16:08:04 i'm kinda curious about our next steps here, like should we review it at a more detailed level? publish a link? wait for it to finalize? 16:08:05 because in the end what we want is to be globally consistent 16:08:19 agreed cdent 16:08:27 I can take that action 16:08:37 sweet, thanks! 16:08:38 #action cdent add links to mnot http protocol thing 16:08:50 I think our guidelines need to be more succinct than this draft 16:09:00 yes 16:09:01 But yeah, linking to it would be excellent 16:09:17 there's much refactoring and refining it would be good to do 16:09:27 that draft is almost as wordy as a mordred patch! 16:09:32 haha 16:09:39 lol 16:09:40 * elmiko notes "almost" 16:09:49 unpossible 16:09:55 nothing is that wordy 16:10:03 =D 16:10:13 any other comments on this topic? 16:10:40 The showrunners for the api-sig have mordred pop up over the backstage wall for a few million $$ every few episodes 16:10:45 and then he fades away 16:10:53 LOL 16:10:56 :D 16:10:57 so good 16:11:00 #topic open mic and ongoing or new biz 16:11:20 i guess we didn't clean up the kruft here, but anything to discuss that is not the draft thingie? 16:11:45 anything we need/want to think about PTG-wise? 16:12:12 I was thinking that the PTG would be a good place to discuss the draft thingy in more detail 16:12:16 who is going to be there? 16:12:25 I'm hoping to go 16:12:41 But IBM is still dragging their collective feet on travel approval 16:12:43 * mordred would like to actually meet with y'all this ptg instead of not doing that like I have done at the last few 16:12:57 edleafe: I do not want to visualize IBM's collective feet 16:12:59 edleafe: you could almost drive up and camp in the halls 16:13:06 * elmiko chuckles 16:13:07 heh 16:13:15 i'll be there 16:13:25 mordred: actually, just my grand-boss 16:13:32 it's very unlikely that i will be there 16:13:39 which makes me sad =( 16:13:41 You say that every time 16:13:45 haha, i know 16:13:47 and then you show up 16:13:53 but this time i feel the winds have changed 16:14:05 road trip? 16:14:36 elmiko: I'd suggest that your employer is crazy if they think they should not send you to the PTG 16:14:47 but, you know, that may just be me 16:14:59 * cdent will fly to detroit, pick up elmiko, go visit cdent's niece in Louisville, then drive to denver? 16:15:01 ROAD TRIP 16:15:06 ROAD TRIP 16:15:15 sadly my flights are already booked :( 16:15:21 otherwise that's a great idea 16:15:26 mordred: yeah, i just know some things are changing for our travel budget and i am loathe to push too hard 16:15:32 * dtantsur is not going 16:15:37 Sounds like National Lampoon's Vacation 16:16:13 So it might be just me and mordred coming up with ways to enshrine and work around microversion simultaneously 16:16:23 sounds like it 16:16:26 cdent: we can make so many decisios 16:16:29 decisions 16:16:31 \o/ 16:16:38 and hopefully some sort of update on the graphql situation (assuming one of them is there) 16:16:39 or more probably decisios 16:16:58 Yeah, still no reply from Gilles 16:17:15 ack 16:17:23 I'll be looking forward to maybe see some of you in Berlin 16:17:52 I'll be there too. 16:17:58 After that things will start getting vague 16:18:09 It's funny - IBM tends to spend more on travel later in the year 16:18:20 Probably be easier to get to Berlin than to Denver :) 16:18:40 i thought about submitting a talk for berlin, but it was really stretching it 16:19:14 * dtantsur submitted two talks 16:19:22 nice! good luck =) 16:19:33 At some point I'll start an etherpad for the PTG 16:19:40 thanks cdent 16:19:41 #action cdent start etherpad for api-sig at ptg 16:20:03 cdent is action man this week 16:20:09 yea seriously 16:20:10 dtantsur, mordred : did you make your microversion proposal? 16:20:13 someone get that man a cookie 16:20:18 cdent: we did 16:20:41 and now I suspect *SOMEONE* did not vote for it ;) 16:20:52 we're gonna tell everyone about microversions 16:20:55 * cdent does not vote 16:21:05 what?? Everyone LOVES microversions!! 16:21:11 "microversion, it's way of life maaaan" 16:21:18 it's too tedious going through all the proposals 16:21:23 espeically since I never go to presentations... 16:21:25 doesn't seem right 16:21:37 well, I watch the most interesting ones in recording 16:21:37 cdent: but BUZZWORD BUZZWORD is awesome because BUZZWORD BUZZWORD! 16:21:45 so I still feel the right to vote for good stuff 16:21:45 hahaha 16:22:33 * cdent saves all his voting karma for destroying brexit 16:22:42 nice 16:22:54 anything else for open biz? 16:23:15 * edleafe thinks cdent doesn't understand voting karma 16:23:19 #topic guidelines 16:23:27 #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z 16:23:33 #link https://review.openstack.org/#/q/status:open+project:openstack/api-sig,n,z 16:23:44 no news is good news? 16:23:54 i think there is nothing go on here this week for guidelines 16:23:56 yea 16:24:07 #topic bug review 16:24:12 #link https://storyboard.openstack.org/#!/project/1039 16:24:24 looks like the same story here as well 16:24:26 same again 16:24:36 #topic weekly newsletter 16:24:41 #link https://etherpad.openstack.org/p/api-sig-newsletter 16:24:45 Before you do that... 16:24:47 any volunteers? 16:24:48 I just remembered 16:24:58 should i switch back the topic? 16:25:13 Infra will be doing the rename for the sig on Friday 16:25:19 ooh, cool 16:25:25 \o/ 16:25:47 do we need to update anything more than the agenda wiki? 16:25:48 So we can toss all our API-WG business cards 16:25:52 hahaha 16:26:07 I don't think so, but we'll see 16:26:15 cool, thanks for the update edleafe 16:26:29 Making sure that the github links still work and stuff like that 16:26:35 I had some really cool business cards 16:26:52 https://www.youtube.com/watch?v=cISYzA36-ZY 16:27:14 lol, knew it 16:27:25 (this is clearly the most fun hour all week, for me) 16:27:31 =) 16:27:43 i'm happy to have been part of it 16:28:02 now, who's gonna write the newsletter? 16:28:04 same here 16:28:13 I wrote it last week 16:28:22 ok, edleafe is off the hook 16:28:37 I can do it 16:28:38 i think it's only fair that i do it since cdent was kind enough to take all the actions this week 16:28:46 either way 16:28:46 oh yeah, yeah, that 16:28:50 go for it 16:28:57 k, i'll ping in a bit 16:29:01 thanks everybody! 16:29:13 now's your chance for a last word =D 16:29:20 word 16:29:25 #endmeeting