17:59:46 #startmeeting new modules meeting 17:59:46 Meeting started Wed May 25 17:59:46 2016 UTC. The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:46 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:59:46 The meeting name has been set to 'new_modules_meeting' 17:59:58 * rbergeron will go and find the things -- beep if you're here :) 18:00:28 * gundalow waves 18:00:38 * MichaelBaydoun lurking 18:00:45 rbergeron: https://github.com/ansible/community/issues/92 18:00:57 gundalow: merci 18:01:03 no problem :) 18:01:04 * gregdek lurks 18:01:21 beep boop [filter sweep] blop 18:02:49 wheee 18:02:52 gregdek, the lurker 18:02:56 okay! 18:03:07 #topic agenda -- https://github.com/ansible/community/issues/92 18:03:28 welcome to the new modules meeting, we'll be modulating the modules in a modular fashion today. 18:03:32 looks like... first up we have... 18:04:02 * rbergeron isn't quite sure, but we'll just do this one anyway. 18:04:18 #topic https://github.com/ansible/ansible-modules-extras/pull/1690 - mssql_db 18:05:13 so -- looks like this has already had shipits, 18:05:26 and just got bumped down in the queue because it needed to have the version updated 18:05:32 thoughts? anyone? :) 18:05:40 This is the one we were arguing about iirc. 18:05:50 That it provides users with too big a gun to shoot off all their toes. 18:05:56 And we agreed to defer. 18:06:22 i thought maybe so, but ... i don't see any of the arguing in this PR? 18:06:36 was there another recent mysql PR? 18:06:38 But now we're committing to split out extras in 2.2, and one of the reasons is to allow us to push more "risky" content so we're not directly associated. 18:06:48 I don't think I've looked at 1690 before 18:06:53 No, I think this was the one, and I think all the arguing happened in IRC because we didn't want to say "no". 18:06:57 But maybe I am thinking of another one. :) 18:07:23 so ready to merge? 18:07:24 I vote we shipit and see what happens ;) 18:07:24 there was also, https://github.com/ansible/ansible-modules-extras/pull/189 18:07:44 Right, which was closed in favor of 1690 18:07:49 shipit, I sez 18:07:54 * gregdek afk a bir 18:08:09 but they were competing a bit, so that one got closed in favor of this one. 18:08:24 mysql_query I think was the one we argued about. 18:08:34 gundalow: i think it's ready, if you want to give a thumbs up then i'll label it for shipping 18:08:43 * rbergeron should change her nick to ups_lady or something 18:08:55 abadger1999: yeah, that may be it 18:09:15 rbergeron: on 1690, will do 18:09:31 gundalow: i meant in irc though :) 18:09:34 oh 18:09:38 SHIPIT 18:09:38 +1 18:09:40 i think it's had the requisite shipits and all that in the PR 18:09:50 #agreed 1690 -- ready to be shipped, yo 18:09:51 given it another one for good measure 18:11:42 okay! 18:12:08 the previous arguments over mysql were for a mysql_query module 18:12:21 #topic https://github.com/ansible/ansible-modules-extras/pull/1942 -- HONEYBADGER YES 18:12:27 #link https://github.com/ansible/ansible-modules-extras/pull/1942 18:12:31 I know nothing about honeybadger. 18:12:35 except it has an awesome name. 18:13:18 and that it's failing travis 18:13:42 because version #. 18:13:52 but aside from that: anyone, thoughts? 18:14:10 * gundalow looks 18:14:30 it seems a bit trivial 18:14:42 he seems to be one of the main honeybadger project folks, so I have to assume that he has checked this pretty thoroughly 18:14:59 he == the author 18:15:11 this really doesn't seem to add more value than just using get_url 18:15:33 We have other notify type things 18:16:04 such as https://github.com/ansible/ansible-modules-extras/tree/devel/notification 18:16:15 lot of which are just get_url 18:16:22 (I believe) 18:16:26 i suppose that's true 18:16:33 ...and it's probably more obvious to honeybadger users than knowing to use get_url, but ... i have no clue, as we know :) 18:16:55 rbergeron: You make a good point 18:17:05 (the first part) 18:17:16 I can give it a quick review then get it merged 18:17:16 so: other thoughts? 18:17:39 +1 gundalow 18:17:41 version added would be 2.2 18:17:49 make the kind human happy after 2 years? 18:17:50 jtanner|t420: ah, good spot 18:17:54 jtanner|t420: yeah, that needs fixing 18:17:56 but i think we aren't holding things up for trivial stuff like that 18:17:58 in core 18:18:03 that's why travis is yelling 18:18:11 Nah, if version is the only thing breaking, shipit 18:18:12 What are we doing about version added, the person doing the merge fixes that/ 18:18:25 rather than bouncing it back to creator 18:18:39 Person merging is usually fixing if that's the only problem. 18:18:54 i think that's the case here. 18:19:03 (Can travis warn instead of fail? Probably not) 18:19:14 nop 18:19:24 OK. I'll review it after this meeting 18:19:30 next? 18:19:33 afk again 18:19:44 gundalow: review it and leave a note saying it's ready to ship, or? 18:20:15 rbergeron: will do 18:20:26 can you chair me? 18:20:38 #chair gundalow 18:20:38 Current chairs: gundalow rbergeron 18:20:40 sorry 18:20:56 action yo self on it :) 18:20:58 #action gundalow to review 1942 18:21:05 :) 18:21:07 next! 18:21:09 :) 18:22:36 #topic https://github.com/ansible/ansible-modules-extras/pull/1434 -- aws vpc peering 18:23:21 has plenty of shipits 18:23:36 is bot working correctly? 18:23:59 yeah. 18:24:12 the bot just starts recounting the shipits after it gets an update. 18:24:27 which, mostly good, because who knows, but sucks in cases like this. 18:24:58 anyway: i think this seems to have enough shipits and is meeting the various requirements of multiple people and the author seems to be fairly responsive. I think it's ready to ship -- anyone else feel otherwise? 18:25:06 shipit 18:25:16 seriouslyshipit? 18:25:19 new keyword 18:25:27 #agreed shipit on 1434 -- has enough shipits and meets all the things 18:25:45 gundalow: homeybadger also needs python3 syntax update -- If you decide it's otherwise a shipit, let me know and I'll fix that when I merge, though (since the guy has been working on the module for 2 years) 18:26:05 i've never peer'ed vpcs, so this one is outside my realm of expertise 18:27:33 gundalow: do you know offhand (or anyone else) if these other modules in the agenda list are ... ones we missed getting to in past weeks, or if they're just ... drama-filled? 18:28:11 rbergeron: some were carried over from the previous meeting ("rolled over"), I'm not sure where gregdek got the others from 18:28:25 ahhh, yea they were all resolved except the F5 one. 18:28:32 which looks like you'er waiting for some eyeballs on, it seems 18:28:49 #topic open floor or taking suggestions on modules we could knock out 18:28:56 rbergeron: aye 18:28:58 gundalow: https://github.com/ansible/ansible-modules-extras/pull/1765 <-- that one 18:29:08 Anyone reviewed any other modules recently 18:29:21 We should probably put the standing "sort descending by number of comments" into 92 18:29:35 That's as good a starting place as any 18:29:52 + newest? 18:29:53 ? 18:30:06 Newest is bad because most of them don't have comments. 18:30:22 I don't know if there's a search that can be "minimum comments plus minimum age" or something 18:30:30 sorry, I meant newest PR 18:30:33 at least one shipit? 18:30:39 MichaelBaydoun: YES 18:30:43 stop starting and start finishing 18:30:50 +100000000000000000000000 18:32:55 okay, so: 18:32:57 oyyyyy 18:33:05 trying to find shipit is so terrible 18:33:09 aye 18:33:16 shipit but exclude if greg said shipit in a comment 18:33:17 lol 18:33:43 I think it requires the meets_guidelines & works_for_me labels 18:33:54 so not gona be doable today 18:34:08 how does the bot currently distinquish the "needs two shipits" message from a real shipit? 18:34:24 but yes, topic for another time 18:34:27 MichaelBaydoun: I believe it looks at who added the comment 18:34:39 similarly for ready_for_review 18:36:07 aye. 18:36:42 well, filtering through this just hunting for things is unfun :) anyone have any modules they'd like to suggest? otherwise... i may just call an end to meeting in a few here 18:38:18 gundalow: still peeking at the rhev one as well? https://github.com/ansible/ansible-modules-extras/pull/2202 18:39:52 rbergeron: Would be good if someone else could take a look at that 18:40:12 I'll try and make time for it 18:40:18 I'm away abit over the next week 18:41:43 gundalow: ack -- gotcha 18:42:07 okay, if nobody else has anything -- i'm closing this in like a minute fo reals 18:42:46 nod 18:43:01 closeit <--- new keyword 18:43:43 * gregdek is good with that. 18:45:48 #endmeeting