19:00:27 #startmeeting community-working-group 19:00:27 Meeting started Wed Jul 13 19:00:27 2016 UTC. The chair is gregdek. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:27 The meeting name has been set to 'community-working-group' 19:00:27 not in three weeks, but you'll see everyone in 3 weeks? i guess? 19:00:34 #topic Roll Call 19:00:40 * rbergeron exists 19:01:44 :) 19:01:55 Agenda as always: https://waffle.io/ansible/community 19:02:48 So, to take it from the top: 19:02:52 aye. 19:03:02 #topic 93: Planning for Contributor Conference SF 19:03:50 okay, we seem to have a bunch more feedback last i looked earlier today 19:04:09 and we promised to send out an agenda -- and i suspect we'll be hosed next week, unless we put that together on monday. 19:04:11 Yes, but not a lot of actual votes. Just... more topics. :/ 19:04:30 well -- we could do a little poll o rsomething via google? 19:04:40 So I'd say, one more note to ansible-devel to urge +1s, and then if we don't have that by next Friday, we just pick 'em. 19:04:48 are you coming, are you coming remotely, put a yes or not next to what you want to do 19:04:49 Yes, we could do some kind of poll, I imagine. 19:04:57 but that is a pain and etherpad seems just as effective theoretically 19:05:03 Or not, LOL 19:05:21 I think the poll is actually a good idea. Just a quick Google form. 19:05:22 well - i am happy either way. i just hate being like, "add your plus 1! well, you can't follow directions, so here is a poll" 19:05:35 Ain't it true? :) 19:05:43 because some people won't see that, or will think their stuff got counted elsewhere, or whatever. 19:05:49 Yeah, good point. 19:06:04 But I can make a poll. Or we can. Or whatever. Or we can jsut use our best judgement. 19:06:06 Then just reiterate the etherpad, and if we don't have any better data by next Friday, we'll just pick 'em. 19:06:18 send the no hanging chads mail :) 19:06:32 ugh 19:06:34 "for your vote to count, you actually have to... :D" 19:06:35 lol 19:07:12 so uh 19:07:18 which of us is doing that urging 19:07:29 You! 19:07:48 Unless your time is right. 19:07:52 Er, tight. 19:08:00 did you send the last one? I think you did 19:08:05 Did I? 19:08:07 My rhymes are tight 19:08:10 i can mail all night 19:08:13 without a fight 19:08:15 there is no plight. 19:08:21 Riiiiight. 19:08:22 Email, i might! 19:08:29 (i actually will, tho) 19:08:38 That's enough rhyming now. I mean it! 19:08:52 #action rbergero to send rhyme-free pun-free mail reminder to plz vote with actual numbers on etherpad 19:09:01 should i just respond to the mail you sent out? 19:09:08 that seems logical 19:09:30 i guess the problem is more topics get added 19:09:38 and everyone assumes they already voted 19:09:39 Well, if that happens, fine. 19:09:50 so then we're like "geeeeeez, why isn't this getting more votes" 19:09:53 Worst case scenario is we do our best to pick 'em. 19:09:56 I dunno. I'll write something up 19:10:00 and we'll plow ahead 19:10:06 next item! 19:10:35 Well, still on this one... re: the room, we've got, what, 20ish? I think that's pretty good. We should probably wrap that up here in the next day or two. 19:10:56 Don't actually know that there's an action item there per se. I just think we're in good-ish shape. 19:10:56 aye. 19:11:13 did we want to blog post or anything for anyone who might be coming to ansiblefest who might be interested in coming / learning / whatever? 19:11:16 or not so much 19:11:47 Nah. I think it needs to be a working session, and the people who are participating now are the right people. It's not really the kind of thing for a drop-in. 19:11:58 It's almost like the "Ansible Midcycle" when you get right down to it. 19:12:51 ... maybe :) lol 19:12:54 but okay. 19:13:13 OK. 19:13:17 Next item! 19:13:33 #topic 81: Module Maintainer Guidelines 19:14:23 okay, per notes in the issue: i updated the version i have in my repo (rather than just mangle the real thing) -- i think it's okay, just have this outstanding question re: the things that alikins had in a fork of the contributors.md file 19:14:48 because i think those things really should be in contributors.md and not in maintainers.md 19:14:56 just pointed to from contributors.md 19:14:59 err 19:15:01 from maintainers.md 19:15:08 Hrm. 19:15:17 or a good chunk of them. 19:15:28 you're not a maintainer until you write a thing. 19:15:32 Yes. 19:15:44 and you need to know those guidelines regardless of being maintainer or just contributor to random module maintained elsewhere. 19:15:54 maintainer == more what my long-term responsibilities are. 19:15:59 Yeah. 19:16:11 ... yet "hrm" sounds skeptical. 19:16:13 :) 19:16:51 No, it's just easy to over-analyze. For now, I'm happy with (a) getting alikins to submit a PR with his CONTRIBUTORS.md changes, and (b) getting your changes into MAINTAINERS.md. 19:17:04 Because it will be better than what we have now. 19:17:15 We may later decide it's insufficient in some way, but it's better than what we have now. 19:17:23 That's my sense. 19:17:49 okay. well, let's poke at adrian to make that PR, and then merging my stuff should be piece of cake. 19:19:13 Sounds good. 19:19:18 how do you feel about the rest? missing anything? 19:19:29 overly sappy? 19:19:35 too mean? 19:19:37 :) 19:20:30 No, it's good. 19:20:32 also, does that PR from alikins (or to be PR from alikins) ... count as the work needed for #78? 19:20:59 or some of it at least? 19:21:04 ...not quite yet, I don't think. Some of it probably. 19:21:09 okay. 19:22:52 I'll ping alikins. 19:23:01 Shall we move on? 19:23:31 yesplz 19:25:02 * rbergeron looks at gregdek wondering if she's driving the bus now 19:25:40 or if there is lag 19:25:47 Sorry 19:26:05 #topic 38: Public Metrics 19:26:21 This one is on newtMcKerr, and he's waiting for some Google stuff to sort out, so we'll defer this one for now. 19:26:24 Any Qs? 19:26:45 um - one, i guess 19:26:57 once we have that stuff sorted out -- what's the reporting mechanism, really? 19:27:21 are we going to mail things out occasionally or do we want to just have a spreadsheet that front ends to .. one of those pretty boards i had previously, or what? 19:27:27 just thigns to ponder on - don't need to know today. 19:27:42 but should probably figure out at some point. if they're public, where is that public place :) 19:28:14 other than that: no questions 19:28:21 I would very much like some kind of dashboard, but it should really be as cheap as we can do it effort-wise :) 19:28:29 kudos to newtmckerr for awesomeness 19:28:32 aye. agreed 19:29:04 well -- i know of options since i've dug into all this before, so ... I think we find something that is good enough, smart enough, and easy enough 19:29:13 without being 47 billion dollars 19:29:16 :) 19:29:20 kk 19:29:24 Next: 19:29:37 #topic 47: Testing Working Group 19:29:44 Nice work by gundalow to move this one along... 19:29:54 And by mattclay as well 19:30:01 gundalow: any status update? 19:31:13 I know gundalow said he's be in and out, so I'll give him a min or two, and then we'll move on 19:31:36 * rbergeron nods 19:31:46 Hi 19:31:51 Me reads back 19:32:27 Ah 19:32:40 :) 19:32:44 Testing working group will formally start after AnsibleFest 19:33:11 Weekly meetings (not Wednesday). 19:34:02 Next step is add any questions we have to the Contributors summit Document. 19:34:17 Which is out for review internally at Ansible. 19:34:50 Then have we can have a productive section of the Contributors Summit as we have an aim 19:35:00 Sounds good to me :) 19:35:05 Think that's it 19:35:43 * rbergeron added some comments, may add a few more, as fyi 19:36:50 rbergeron: Sweet, thanks. I'm not going to add it to either pad till next week, so feel free time keep adding stuff 19:36:50 OK. 19:37:01 gundalow: ack, sounds good 19:37:04 Thanks for the update gundalow 19:37:06 :) 19:37:08 Moving on: 19:37:21 #topic 104: Ansible Durham meetup 19:37:39 Looking at the week of 8/8 with House. Probably Thu 8/11. 19:37:54 Will look at availability of venues and so forth and get that up in the coming days. 19:38:38 Any Q there? 19:38:39 * rbergeron nods 19:38:42 nope. 19:39:54 Next: 19:39:58 #topic Ansible phx meetup 19:40:02 oh 19:40:05 no chair for me 19:40:07 You got it 19:40:10 Grrr. 19:40:15 i don't got it 19:40:15 #topic 42: Ansible phx meetup 19:40:21 #char rbergeron 19:40:26 #chair rbergeron 19:40:26 Current chairs: gregdek rbergeron 19:40:27 do not char me. 19:40:30 please. 19:40:32 FOOOM 19:40:43 i am hot enough already 19:40:45 anyway. 19:41:14 I have pinged the red hat folks and there is juggling looking. i pinged other folks for independent spaces and .. waiting and seeing. I did think of another human that may be more flexible. 19:41:24 People kind of hate summer meetups here basically 19:41:31 FAIR ENOUGH 19:41:32 hosting, going, you name it 19:41:52 but ... poiking for a venue at this rate might get me something in september when it's slightly less awful 19:42:07 I think the nice citrix folks might hook me up though 19:42:12 so I will ping chris 19:43:08 ok! 19:43:11 I updated the issue. 19:43:17 thx :) 19:43:30 That's all the big stuff. 19:43:50 thank goodness 19:43:51 And then next week is all-hands, and then week after that is fest! 19:43:56 woot 19:43:56 #topic open floor 19:44:01 So really it's all about Fest at this point. 19:44:03 i'll just do that, 19:44:05 lol 19:44:06 Though no hands for me 19:44:17 :( 19:44:35 Had already booked holiday 19:44:39 I will be in many abstracts for talks ... land the next day or so 19:44:58 at least the rest of today (openstack summit) and then i have to actually come up with my thing for automacon and apparently containercon 19:45:51 And yes, fest is about it. :) wooo 19:46:43 anyone else have anything to chat about? 19:46:52 burning questions? 19:46:55 hot gossip? 19:47:01 free winning lottery tickets? 19:47:43 * gundalow will be in SF from Sun 24th so poke me for beer based meetings :) 19:47:58 lol. that will be no problem, i am sure 19:48:14 :) 19:48:40 gregdek: you have anything else? 19:48:44 I do not. 19:48:49 Oh... 19:48:54 you do. 19:49:00 ...except I'm gonna try to get the damned issue bot done this week. 19:49:08 Finally. 19:49:11 Wish me luck. 19:49:15 it's a blessed issue bot, actually 19:49:22 :) 19:49:23 Nothing else from me 19:49:29 let me know when i can be your guinea pig 19:49:35 rbergeron: will do. 19:50:01 or .. alternately, take the corner case not guinea pig things and just start whittling as you can get through and refine things 19:50:04 :) 19:50:09 (i will take the corner cases) 19:50:11 just lmk. 19:50:16 and: now that's it? 19:50:52 That's it! 19:50:55 #endmeeting