16:58:28 #startmeeting cwg 16:58:28 Meeting started Wed Sep 13 16:58:28 2017 UTC. The chair is gregdek. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:58:28 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:58:28 The meeting name has been set to 'cwg' 16:58:34 We'll get started in a few. 16:58:54 #topic agenda: https://github.com/ansible/community/issues 17:00:53 here 17:08:07 OK! 17:08:22 rbergeron is at a conference and will be joining shortly. 17:08:36 So imma just jump in: 17:09:21 And I'm actually going to sort by oldest, because I'd like to close some of these if we can. 17:09:36 https://github.com/ansible/community/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-asc 17:09:53 #topic https://github.com/ansible/community/issues/193 17:10:33 I basically sent out the update for London as part of the SF invite, so I'm closing this one. 17:11:50 (Hm, wish zodbot could pull issue title there) 17:11:52 Next: 17:12:29 Extend yaml2ical to add one-off events and merged calendars #196 17:12:33 Oops 17:12:35 #topic Extend yaml2ical to add one-off events and merged calendars #196 17:12:52 dag: you assigned this one to yourself, but I see a related commit. 17:12:55 Around to comment? 17:13:02 https://github.com/ansible/community/issues/196 17:14:12 Or maybe that commit was just to tee that up. 17:14:24 Anyway, I'll move on, dag I'll leave it open for you. 17:14:56 Next: 17:15:04 #topic https://github.com/ansible/community/issues/98 17:16:16 This has been open for a year, and feels suspiciously like a WONTFIX at this point, since no one on the core team cares to comment, and it's been a year -- so I'm closing to that effect. I mean, it certainly isn't pretty, but it's functional, and people know how it works. 17:16:40 Well... 17:17:08 ...ok, so I'm going to ping thaumos to see if he has any thoughts, since this really is kinda "product manager-y". 17:18:51 OK, moving on: 17:20:36 #topic Many duplicate new module submissions #60 17:20:43 https://github.com/ansible/community/issues/60 17:22:15 That's a docs issue, really, and now that we've cleaned up the docs a bit, it should be easier to tackle. Taking that one on myself. 17:22:24 Next: 17:23:35 HI 17:23:42 Hi! 17:23:53 Hi! 17:24:04 * rbergeron finally escaped and escaped the humans who wanted to say hi and found some internet and a chair 17:24:12 #topic Need a good way to advertise CFPs to the wider community #89 17:24:21 Just in time! 17:24:28 https://github.com/ansible/community/issues/89 17:24:45 Though I'm pretty sure this is just "flag this with ambassadors and/or news tags". 17:25:12 Really, this is the endless "how do I know about CFPs" question. 17:25:26 yeah. 17:25:31 I kinda wonder if we should leverage other work that the broader Red Hat community teams do here. 17:25:48 there is a cfp list internally. and a bunch externally. 17:25:49 I don't know how good their processes are, and I know There Be Dragons to some extent there. 17:25:56 there are lots of places to suck things from. 17:26:17 * dag appears 17:26:17 Should we suck things from those places, or could we just tag and link somehow? 17:26:18 i think part of this is also the "when people very specifically want to find an ansible thing for their event" 17:26:25 Hey dag! 17:26:27 ansible talk 17:26:38 rather 17:26:57 dag, I pinged thaumos about arranging the releases directory, and he favors your approach, he will discuss with team. 17:27:05 not sure. i mean -- i think there's a balance of "more resources about places to talk, but here's the highlights of some cool things you could give a talk at" 17:27:24 What is a cfp 17:27:30 So I could see this being a bunch of work for no effect, and I would like to change it into a little bit of work for a large effect, LOL 17:27:30 call for presentations. 17:27:35 K 17:28:22 gregdek: cool, thanks ! 17:28:25 I guess my question is, "what do we want here?" Do we just want to advertise a single place to say "hey, know a conference where you want an Ansible talk? Send it to us using this handy dandy widget/whatever"? 17:28:27 well -- i think if nothing else it can fit into either a static page that we update as we see fit 17:28:39 Smells like a WIKI PAGE! 17:28:41 or as lines in a newsletter 17:28:45 or who knows. but. yeah. 17:28:52 and yeah, wiki page. 17:29:02 Classified ads 17:29:25 I think I can get a few thousand dollars to advertise in print media. 17:29:36 Seriously, though, maybe it's as simple as: 17:30:13 Well, no. 17:30:14 Hm. 17:30:34 lol 17:30:42 OK, I'm probably thinking about this too much. 17:30:47 But there's two things here: 17:30:52 LOL 17:31:05 1. Finding out about events that people should submit talks to; 17:31:18 2. Telling people about events that people will be speaking at. 17:31:22 Is this 1, or 2, or both? 17:31:46 the CFP thing is 1. 17:32:01 yeah, #1 would be really helpful 17:32:05 The second thing is also a potential thing but not related to this ticket :) 17:32:09 imo 17:33:22 OK. 17:33:33 Then we can do something simple. 17:33:42 yup. 17:34:05 Like a weekly tweet: "got any conferences upcoming that you'd like to see an @Ansible talk at? Let us know by doing x!" 17:34:22 And then have some very simple thing for x: send an email, edit a wiki page, whatever. 17:34:27 yup. 17:34:32 Which should it be? 17:34:50 i am full of yup. 17:34:53 If we can figure out the value for x, we can have this done pretty much asap. 17:35:20 umm... "replying" 17:35:21 ummmm -- i think edit a wiki page is a good start. if that's too high a bar or whateer for folks -- then i dunno. 17:35:29 You know what? We need the "ansible-community" catch all email address at red hat. 17:35:46 i would just tweet back 17:35:46 Oh, chouseknecht, you have all the good obvious answers. 17:35:51 then email. i just worry that that kind of thing turns into mega spam from every conference organizer on earth 17:36:14 like, conferences totally unrelated :) 17:36:21 Yeah, it may well. 17:36:36 OK, so: 17:36:57 * sub-wiki page under the ambassadors namespace that is "conferences with cfps". 17:37:15 * weekly tweet pointing people to it. 17:37:42 * maybe we send out something to news based on that list. 17:37:47 Simplest possible solution? 17:37:53 That might actually be useful? 17:38:18 yes 17:38:24 yes yes. 17:38:45 does wiki let you create a form for people to complete? 17:39:17 I don't think so. 17:39:32 We could ask people to file a ticket... lol ugh 17:39:52 i was thinking like a Google docs form. But, that might be too much. 17:40:07 Maybe that's ok, actually. 17:40:15 I mean, we do want a dead simple form. 17:40:30 "What's the event? What's the URL? When's the deadline? Any other notes?" 17:40:47 yup. 17:40:52 yup! 17:40:58 ok. 17:41:11 yup 17:41:20 so still a wiki page, but for the masses we just send them to the form, and we add the stuff, and we tweet it every week. 17:41:23 and if we have that form go into a database / spreadsheet / whatever we can reconvert that data into whatever format we want elsewhere. 17:41:34 Yup! 17:41:42 w00t! 17:42:35 I'll take it for now, since I'm gluing a bunch of these bits together anyway in standing up the ambassadors wg. 17:42:41 * gregdek goes to edit ticket 17:44:00 OK, moving on: 17:44:26 #topic documentation working group #30 17:44:33 https://github.com/ansible/community/issues/30 17:44:39 I think this one is just a no. 17:45:08 then close it up, yo! :) 17:45:17 yup 17:45:20 I think docs need to be part of the various working groups, and neither docschick nor dharmabumstead show any interest. 17:45:30 And since there are no objections, closing. 17:45:37 * chouseknecht just likes saying yup 17:45:52 okay, i'm relocating because my spot is suddenly invaded by 10 billion humans 17:45:55 brb 17:46:58 #topic Public Metrics #38 17:47:15 This one's been around for quite a while. 17:47:23 Waiting for rbergeron to return and comment. 17:47:28 Public Metrics #38 17:47:30 GAH 17:47:35 https://github.com/ansible/community/issues/38 17:48:18 I may now believe this is a monthly news column by jtanner :) 17:48:27 +1 17:48:35 It would be interesting to actually talk about what things we measure and why. 17:48:48 Raw numbers are meaningless. Metrics exist solely for analysis. 17:51:10 you could even break the metrics down by topic, i.e. cloud modules, aws, docker, etc. 17:51:33 other number: number of "automerged" PR. number of shipit by roles (module maintainers, namespace maintainers, others) 17:52:34 Yeah. 17:52:58 And all of these metrics are really asking the question: how are we doing at managing all of the requests to improve Ansible? That's kind of the overarching question. 17:53:44 jtanner are these the kinds of questions that we have the metrics to answer? 17:55:30 OK, updating the ticket with some ideas. 17:55:34 We will revisit. 17:55:44 Getting close to the end of the hour. 17:55:48 #topic Open Floor 17:55:57 Any particular topics anyone wanna cover while we're here? 17:57:05 Is meetup part of ambassador working group? 17:57:33 Yep, I think that's the plan. 17:57:40 Cool 17:57:50 That's what the majority of meetup folks seemed to favor, so. 17:58:53 Ah zone have been in contact, cool 17:59:22 Ah some have been in contact, cool 17:59:32 Nothing else from me 17:59:37 OK, gonna wrap then. Thanks all 17:59:40 #endmeeting