19:01:38 #startmeeting community-working-group 19:01:38 Meeting started Wed Jul 6 19:01:38 2016 UTC. The chair is gregdek. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:38 The meeting name has been set to 'community-working-group' 19:01:44 * rbergeron applauds 19:01:49 #chair rbergeron gundalow 19:01:49 Current chairs: gregdek gundalow rbergeron 19:01:53 * gregdek bows. 19:02:02 * gundalow waves 19:02:08 * rbergeron waves to gundalow 19:02:27 Agenda, as always: https://waffle.io/ansible/community 19:02:40 #topic Planning for Contributor Conference SF 19:02:52 https://github.com/ansible/community/issues/93 19:02:53 heyyyyo! 19:03:09 So. Any word back from Carrie re: "session is full"? 19:03:44 looking 19:04:02 not yet! 19:04:12 i wonder if we have a link to the spreadsheet where things go, though 19:04:19 ok. that's weird. kinda need to know what's up there. 19:04:31 Assuming we get that sorted, we should probably announce to the world in the next day or two. 19:04:39 And finalize an agenda. 19:04:53 Got time to work out the final agenda tomorrow or Fri? 19:05:08 i don't seem to have that link. 19:05:27 yeah, we do. I kind of wonder if the link got forwarded to the core team and they filled it up, since i think there was a loose cap on it. 19:05:34 which we can revise, but. 19:05:52 and: yes, probably earlier tomorrow morning would be better, if that works for you? 19:06:01 Yep! 19:06:04 and maybe we'll have more data from carrie by then, also. 19:06:09 Pick a time and put it on the calendar. 19:06:21 because i'd love to know who is actually going to be present while making the agenda, to some extent. 19:07:19 (your entire calendar says "busy" all day tomorrow till 4pm your time. is 10am your time okay?) 19:07:31 Yep. 19:07:54 OK, anything more on that front for now? 19:08:39 Imma guess "no" and we'll move on! 19:08:40 Nope! Just a bit concerned about the link situation. 19:08:52 Especially if we're going to advertise things or whatever. 19:09:06 #topic Module Maintainer Guidelines 19:09:08 https://github.com/ansible/community/issues/81 19:09:20 Now it's post-Summit so we can think about these things again! 19:09:25 I have no idea where we left this. 19:09:55 oh, right, alikins proposed some good changes. 19:10:06 Hey! Well, i was supposed to be working on it, and uh, I guess now i can work on it more with more time and stuff. 19:10:09 Maybe just pull all this together for a review session next week? 19:10:19 yeah. 19:10:28 right, I'm back 19:10:29 deadlines plz so i don't slack. 19:10:35 heh 19:10:55 or get distracted by shiny objects 19:11:13 By next Wednesday so we can make it the focus of this mtg. 19:11:50 pressure! okay 19:12:10 #action rbergero to pull together the module maintainer guidelines for review in this mtg next week 19:12:59 Next! 19:13:37 * gregdek finds the right tab grrr 19:13:50 #topic Public Metrics 19:13:51 https://github.com/ansible/community/issues/81 19:13:59 Doh 19:14:00 https://github.com/ansible/community/issues/38 19:14:44 Well, i have nothing here but stuff in my head, I guess. 19:14:47 Should we hand this over to newtMcKerr or work with him on it? 19:14:53 Because he's got Teh Big Googlz 19:14:57 probably work with him on it, to some extent. 19:14:58 exactly 19:15:26 I’m actually already running some of those. definitely assign to me 19:15:36 Great! Done! 19:16:18 Maybe we can catch up in the next week or two to figure out what we can expose, and how? 19:17:25 yes, lol. 19:17:34 i'll just volunteer him for yes on that. 19:17:35 :) 19:17:49 we can help a bit probably with figuring out where to put the info. 19:17:52 Go git 'im. 19:18:05 cool 19:18:17 newtMcKerr: i will be beeping at you about such things :) 19:18:17 GOT 'EEM 19:18:25 sounds good 19:19:32 next! 19:19:47 * gregdek looks 19:19:50 * rbergeron hopes it's something for greg to be working on and not something i'm failing to get done 19:19:55 :D 19:20:07 #topic Add labels for issuebot and prbot to ansible/ansibullbot 19:20:26 But this is really on mine and/or alikins plate at this point. 19:20:31 I guess we have issuebot now. 19:20:38 Oh wait, no it's not. 19:20:41 Well, we KINDA do. 19:20:48 well, it was mostly so we could separate issues from one and the other. 19:20:59 Yeah. But issuebot still doesn't exist. DAMMIT. 19:21:01 so people working on different things could easily see which bot the problems listed were for. 19:21:12 Sigh. Lots of false starts, nothing running. 19:21:14 well, make a label and and issue saying "issuebot needs to exist" and label it issuebot 19:21:25 and then we can close this one :) lol 19:21:41 Done! 19:22:12 * rbergeron brings the solutions 19:22:45 We now have an issuebot label. 19:22:56 ISSUE #1 GET ISSUEBOT DONE (sigh( 19:23:13 z;0 19:23:15 :) 19:23:25 NEXT! 19:23:31 #topic Testing Working Group 19:23:42 https://github.com/ansible/community/issues/47 19:23:48 * gundalow waves 19:23:50 :) 19:24:00 this is a thing we plan to chat about at the contributor summit a bit. 19:24:00 also, gundalow has things and magic 19:24:00 So I'm now part of the team \o/ 19:24:01 Well, you're in for it now, sir. 19:24:08 you were part of the team anyway :) 19:24:14 CONGRATULATIONS! 19:24:18 THANKS! 19:24:27 (And rbergeron is right, of course.) 19:24:40 But now you can spend all your time on this stuff, instead of just most of it! 19:24:41 So. 19:25:13 It's probably time to figure out what the remit of this Working Group is. Maybe a proposal to discuss at AnsibleFest for what the scope is? 19:25:59 So, I was chatting with newtMcKerr about this earlier. We need to agree what we want to get out of it. I've just had 90minute chat with Matt Clay about where he's upto. I think the next thing is a very short video call between a few of us to work out the remit 19:26:11 maybe.. though i would argue that could / should be a fairly light proposal / scope. 19:26:15 My priority is Network for privateip 19:26:22 I mean, it can be pretty loose to start... "people who care about testing and want to do things" at first. Just a place to plant the flag even. 19:26:31 since... having a group would be nice, and hopefully those who might want to be part of the group might have ideas. :) 19:26:44 Both of those points are good points 19:27:06 a wise man once told me 19:27:08 "just start doing stuff" 19:27:11 And yes, $DAYJOB for privateip clearly takes precedence, no argument there. 19:27:16 (and make it visible) 19:27:34 I'm here till Tuesday 12th July, then I'm traveling and I'll see you in SanFran. I plan on getting there on the Monday 19:28:49 I'd like to get some thoughts together *before* the Community Summit, so we make best use of that time. Also to avoid the "erm, yes, stuff, we should, erm do stuff" 19:29:42 aye. 19:30:01 :) 19:30:09 ugh, lag 19:30:15 The community has lots of energy, we can do good things together 19:30:16 Oh excellent! 19:30:29 Yes. I think that's right. 19:30:47 Throw stuff at the wall, see if it sticks. 19:30:50 yarp 19:31:34 progress++ 19:31:58 gregdek: Could you poke me tomorrow/Friday when you have a bit of time and we can put together the lightest weight proposal 19:32:01 gundalow: want a deadline or anything? 19:32:05 Ah, lol, timing 19:32:10 :D 19:32:14 Can we do Friday AM eastern US time? 19:32:33 If that works for you, I can send out a calendar invite 19:32:47 rbergeron: want to be along for that or nah? 19:32:49 that works jobarker@redhat.com 19:32:55 okeydoke 19:34:13 augh, the lag 19:34:16 sorry 19:34:18 rbergeron: I included you on the invite, if you can make it good, if not no worries 19:34:27 gregdek: merci 19:35:04 Next: 19:35:16 #topic schedule some #&$(# meetups 19:35:32 rbergeron: you and me need to get these done to get them off the plate. 19:36:26 yeah, yes. the folks here who were working to host that stuff basically deferred until after summit, so if they're still not ready to do things, then i'll just .. do things without them, i guess. 19:36:34 they were offering me the lazy way though :) lol 19:37:19 and we can set other things up. 19:37:52 Anyway. Nothing to talk about there except just doin' stuff. 19:37:53 maybe we should make a meeting, so we actually, like, figure out what needs doing on this front, without figuring it out right this second. unless it's literally "phoenix and rdu" in which case, we should go do 19:38:06 and it sounds like that's the case. 19:38:10 the latter 19:38:10 It's literally Phoenix and RDU, since they're in our backyards. 19:38:16 Yup. 19:38:18 JUST DO 19:38:22 THINGY 19:38:23 okay. "some" just sounded like it could be "a whole bunch" 19:39:04 what else are we (me) dreadfully behind on? :D 19:40:03 Nothing that can't wait. We've got backlog, but we should just knock this stuff out first. 19:40:09 okay! 19:40:30 #topic Open Floor 19:40:33 Anything else? 19:40:35 Anyone? 19:40:38 Bueller? 19:40:42 Anyone? 19:40:51 nope. ;) 19:40:55 How do we tell people when meetings are canceled 19:41:15 :D 19:41:55 Also Privateip and I are both away Wed 13th, so no Networking meeting then 19:42:51 Yes. Good point. 19:43:01 The question is, "who's looking for this stuff and where?" 19:43:13 An email to ansible-project is one possibility, but there's a lot of noise. 19:43:25 Wherever it is, we need to tell people to look there. 19:43:35 I've changed the Networking meeting to a standing agenda like the New Modules. So I guess I could just put it on there 19:43:56 and as we have just one agenda people should hopefullysubscribt 19:44:10 *nod* 19:45:04 Yes, that actually makes a lot of sense. 19:46:53 Proposal: Move the AnsibleFest one month so I can come ;-) 19:47:05 #agreed canceling a meeting? Add a comment to the github meeting agenda issue 19:47:08 dag-: :( 19:47:15 dag-: Come to the London one? 19:47:15 It's now right in the middle of the holiday season :-/ 19:47:16 dag-: we will be having another one in October in NYC... 19:47:26 gregdek: aye 19:47:31 aha 19:48:03 Lets start the negotiations with my significant other... 19:48:03 gregdek: rbergeron I did https://github.com/ansible/community/issues/110 You might want to do the same on the others? 19:48:07 And they're all well wired for remote participation, so you can't weasel out. ;) 19:48:15 Bring your SO to NYC! 19:48:26 (and the significant little ones ;-)) 19:48:53 That's trickier. :) 19:49:20 gundalow: yes, I will. 19:49:37 OK! Any other items? 19:50:19 not here. 19:50:31 nah 19:51:04 beer time I think 19:51:18 ;) 19:52:49 gregdek: you are welcome to end the meeting now unless you'd like me to :) 19:52:59 #endmeeting