19:07:34 #startmeeting community-working-group 19:07:34 Meeting started Wed Aug 17 19:07:34 2016 UTC. The chair is gregdek. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:07:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:07:34 The meeting name has been set to 'community-working-group' 19:07:37 LOL 19:07:43 If you all can think of better ways to do it, feel free to let me know :-) 19:07:46 #topic WE GOT NEXT 19:07:50 #topic Roll Call 19:07:59 blippy 19:08:17 i'm more into croissants than rolls, personally 19:09:25 Agenda, comme toujours: https://waffle.io/ansible/community 19:09:38 OK, let's blow thru this thang. 19:09:44 OUI 19:09:47 #topic Planning for Contributor Conference Brooklyn 19:09:55 https://github.com/ansible/community/issues/115 19:10:19 whee! 19:10:21 Updated! 19:10:26 Any questions? 19:10:30 So I'm on the hook for putting that in hubspot. 19:10:34 Yeppers. 19:10:41 and i expect you to harass me about it in the morning. 19:10:46 LIKE A BOSS 19:10:48 literally 19:11:01 Will do! 19:11:05 thanks! 19:11:07 next? 19:11:34 #topic Ansiblefest SF recap 19:11:45 https://github.com/ansible/community/issues/93 19:11:54 Blog post done, waiting on Anna to post 19:11:56 I think we're waiting on annaucbo's draft :) 19:12:03 Er, draft, yes 19:12:03 or to post 19:12:06 or draft! yes 19:12:15 * rbergeron gets a giant cup of tea 19:12:27 And once that's done, we're done with that item. 19:12:30 Next: 19:12:42 #topic Module Maintainer Guidelines 19:13:07 https://github.com/ansible/community/issues/81 19:13:25 We've got a new draft in, just need to clean up some other stuff... 19:13:50 yeah, cleaning up. 19:14:15 Should we ask alikins to submit his changes as a PR to this file? 19:14:51 ummm 19:15:02 so - i think maybe a lot of that could still just go in ... 19:15:04 * rbergeron looks 19:15:16 If you want to Just Do It, that's fine too. 19:15:29 well, i'll finish saying why -- because the same guidelines apply even if you're just submiting a PR to someone else's module. 19:15:47 and if you'er not a maintainer, you might wind up missing some of that context. 19:15:56 iirc. was my line of thinking 19:16:11 but -- open to just having him do a PR to that file as well :) 19:16:46 You tell me the right answer. :) 19:17:06 I think it might be best in the ... 19:17:15 ... 19:17:19 ... 19:17:22 !!! 19:17:28 ??? 19:17:35 ¯\_(ツ)_/¯ 19:17:46 ughhhhhhh 19:18:13 i don't know. i want to say "OMG so much redundancy" but it seems like a lot to untangle and fix, before we then ... have to sort out the core / extras stuff. 19:18:23 Is this doc sprint material? 19:18:40 I'll do a pr, though maybe not soon 19:19:28 gregdek: actually, probably, yeah. (i mean, the whole of the core / extras stuff probably is.) 19:19:47 actually, i think this stuff from alikins is probably fine in guidelines.md 19:20:09 Then let's do that. If you can pull it in so alikins doesn't have to mess with the PR, so much the better. 19:20:26 yeah 19:20:32 um, also: i do'nt think my PR has been merged? 19:20:44 It hasn't? 19:20:52 What's the PR id? 19:21:08 https://github.com/ansible/ansible-modules-extras/pull/2710 19:22:05 abadger1999 bcoca any reason we can't just merge this new GUIDELINES.md file into extras? 19:22:37 It's just a new top level text file, so I would just merge, but I vaguely remember some reason for being careful with top-level files like that...? 19:22:52 * abadger1999 checks 19:23:43 gregdek: I think it will be okay if it's not a directory and doesn't end in .py or .ps1.... I say merge it to devel only -- we'll find out pretty quickly if there's a problem. 19:24:02 ok will do, thx! 19:24:41 Done. 19:24:59 WOOO 19:25:20 okay, then i'll make a PR to that. Unless things go awry. 19:25:21 ok, next? 19:25:23 Yep. 19:25:37 #topic Public Metrics 19:25:46 https://github.com/ansible/community/issues/38 19:25:54 newtMcKerr: any update on ^^^? 19:27:13 I'll say that's a "no" for now. 19:27:18 :) 19:27:20 JCTanner is working on a bunch of this stuff and has it coming along. Data and graphs. 19:27:33 okeydoke! 19:27:37 not sure if I’m allowed to post those yet :) 19:27:37 Should I reassign to him? 19:27:40 yes please. 19:27:44 will do, thx! 19:28:00 jtanner|t420: you're now on the hook for that one :) 19:28:16 * jtanner|t420 reads up 19:28:37 https://jctanner.github.io/ 19:28:46 yay, that ^ 19:28:54 ooooOoooo! 19:28:57 updated ~hourly 19:29:22 I'm so glad there's an actual engineer working on this stuff now. 19:29:23 i broke the galaxy one, but i'll fix it soon 19:29:30 (thanks tanner, didn’t think those were for public consumption yet) 19:29:39 er…thanks :) 19:29:40 fun! 19:29:40 it's public data, so i don't mind 19:31:00 w00t 19:31:03 ok. 19:31:05 i'm not able to assign issues to myself in the community repo 19:31:12 abadger1999: or bcoca have you guys made a decision on the retry/backoff PR https://github.com/ansible/ansible/pull/17039? Just following up. 19:31:32 oops wrong channel, should have asked in devel 19:31:34 sorry 19:31:40 no worries :) 19:31:47 #topic Testing Working Group 19:31:54 (jtanner|t420 I will add you after the mtg) 19:32:09 k, thnx 19:32:27 https://github.com/ansible/community/issues/47 19:32:32 IT LIVES 19:32:37 so closing. Thx gundalow! 19:33:13 :) 19:33:14 yay 19:34:12 Closed. 19:34:23 And jtanner|t420 I've added you to the community team and assigned you that issue. 19:34:27 Next: 19:34:29 thanks 19:34:33 Meetups. I've done nothing on mine, sigh. 19:34:56 Bummer. 19:34:58 Mine is next week! 19:35:01 wish me luck! 19:35:03 :D 19:35:06 GOOD LUCK! 19:35:10 THANKS! 19:35:21 When i'm done, i'm gonna take myself to see a movie, maybe. 19:35:30 You do that. 19:35:34 probably not though 19:35:37 I'll get mine scheduled tomorrow. 19:35:42 :) 19:36:12 OK, that's it. 19:36:15 #topic open floor 19:36:20 Anyone have anything else? 19:36:28 Ansiblefest! coming up yo 19:36:31 that's it. 19:36:45 We covered that first! 19:36:57 no, we talked about the contributor thing 19:37:04 which is the day before ansiblefest 19:37:06 :) 19:37:19 i'll just shut up now, because brain is terrible 19:37:41 Ah right, ok. 19:37:46 Technically correct. 19:37:50 *Technically*. 19:37:55 Anything else? 19:38:00 Not technically. 19:38:01 Anyone? Anyone? 19:38:04 :p 19:38:06 YES TECHNICALLY 19:38:13 I meant not technically anything else. 19:38:22 Ohhhhh lol 19:38:30 #endmeeting 19:38:33 oh great 19:38:36 #chair rbergeron 19:38:37 Current chairs: gregdek rbergeron 19:38:40 #endmeeting