14:59:27 #startmeeting ansible core irc public meeting 14:59:27 Meeting started Thu Aug 30 14:59:27 2018 UTC. 14:59:27 This meeting is logged and archived in a public location. 14:59:27 The chair is bcoca. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:27 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:59:27 The meeting name has been set to 'ansible_core_irc_public_meeting' 14:59:39 #topic ansible/ansible#42163 15:00:01 * gundalow waves 15:00:50 .hello2 15:02:09 seems author is looking at runner as altnerative, any one else have something related to this? 15:02:48 k, closing then 15:02:58 #topic ansible/proposals#57 15:03:21 hrmmm... the bot isn't awake 15:03:43 .hello2 15:03:51 alikins: i believe you are now partial to having meta/requirements.yml ? 15:03:53 can't remember, do we need to be `#chair`? 15:04:08 we can, im still unclear what it actually does 15:04:12 maxamillion: maxamillion 'Adam Miller' 15:04:15 I had to rejoin all my channels so maybe they changed something due to spam and the bot needs to rejoin. 15:04:25 I think people with `#chair` can set topics and stuff 15:04:26 probably 15:04:30 gundalow: gundalow 'John Barker' 15:04:36 There is goes. 15:04:48 .hello2 15:04:51 sivel: sivel 'Matt Martz' 15:06:54 bcoca: I like the idea, but cant speak for galaxy in general 15:07:32 i just saw 15:08:03 ok, going to shelve till we can discuss more with rest of galaxy team, i'll give kustodian a ping that we are discussing it as it might impact other plans 15:08:23 * bcoca hates wasting willing 'free' developer time 15:08:32 #topic open floor 15:10:41 #topic Fixing GitHub labels (BOTMETA.yml) #44903 15:10:45 :( 15:11:02 bcoca: Can I have a #chair ? 15:11:14 #b ench gundalow 15:11:20 #chair gundalow 15:11:20 Current chairs: bcoca gundalow 15:11:30 #topic Fixing GitHub labels (BOTMETA.yml) #44903 15:11:36 * ryansb waves 15:11:39 #info https://github.com/ansible/ansible/pull/44903 15:12:08 Currently https://github.com/ansible/ansible/labels?q=support isn't accurate, lots of things are marked incorrectly 15:12:28 ^ my only comment, defaulting to community for many of those dirs makes future maintenance easier imo, otherwise core will support any new plugins/module_utils by default 15:12:55 yeah, I think defaulting to community is a good idea 15:13:03 Sure, I can do that and explicitly add support: core 15:13:24 I think that makes sense for `module_utils` 15:13:36 Not sure about the other `plugin/` directories 15:14:50 modules/module_utils have the most traffic, but users do add to other plugins also, lots less, but it does happen 15:15:26 `lib/ansible/modules/` is generally driven by `ANSIBLE_METADATA`, so that should allbe community 15:15:28 many lookups are community 15:15:32 +1 to default to community 15:15:49 callbacks also 15:15:53 yeah, pretty much the sensible way to go 15:15:55 +1 15:16:10 vars_plugins has 1 , but once i create a couple more i also expect community to start contributing more 15:16:40 I'm not bothered about this being 100% right, just want to improve it a lot for high traffic areas of the codebase 15:16:49 a) I'll change module_utils to be community by default 15:17:04 agreed, im just saying it might save us work in future to default to community 15:17:08 b) looks to be community by default - which looks are supported by core? 15:17:22 callbacks also, most are community 15:17:25 s/looks/lookups/g 15:17:28 we probalby have to go through list 15:18:13 we don't have much of those documented as to what are core, but most of us can point them out as needed 15:18:51 callbacks default/minimal/tree would be only ones core , top of my head 15:18:53 OK, I might just fix the support:network stuff in that PR and do a follow up PR. Need to get those labels fixed before Network can do backlog review 15:19:02 I'll do googlesheet for others 15:19:03 Thanks 15:19:22 maybe profile_X 15:19:32 and junit, cause ansible-test uses is 15:19:32 ? 15:19:39 profile_roles/profile_task callbacks 15:19:44 ah 15:19:53 an, oneline, used by -o in ansible 15:20:15 bcoca: ack, will do this in Google docs at somepoint in $future 15:20:19 as I'm out a bit next week 15:20:34 k, was thinking of just doing it in PR 15:23:33 TIL we have a 'null' callback 15:23:44 fair point, I'll see where I get to 15:23:45 anything else? 15:23:49 #topic Open Floor 15:25:15 gundalow: not sure that BOTMETA "support" key is propagated to subpaths 15:25:19 * ryansb nothing going on 15:25:39 closing in 1 min if no other items 15:25:52 I'd welcome feedback on my Developer Guide WIP PR 15:26:05 link? 15:26:21 https://github.com/ansible/ansible/pull/44098 15:26:25 #topic developer guide revamp https://github.com/ansible/ansible/pull/44098 15:26:46 the HTML version is published at http://docs.testing.ansible.com/ansible/latest/dev_guide/index.html 15:29:12 it's a big changeset, so it may take a while to read - if you see stuff that could be improved, post it on github or ping me with comments/ideas 15:33:50 If there's no immediate feedback, we can move on. 15:34:11 #topic open floor 15:34:18 acozine: probably need a longer read from most 15:34:30 yep, absolutely 15:34:41 just wanted to get it out there 15:36:08 acozine: When do you need feedback by? 15:36:40 gundalow: I'd like to merge by Monday if possible - the PR has had a long run already 15:36:49 nod 16:04:10 #endmeeting