18:59:42 #startmeeting Ansible Core Meeting 18:59:42 Meeting started Tue Apr 18 18:59:42 2017 UTC. The chair is abadger1999. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:59:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:59:42 The meeting name has been set to 'ansible_core_meeting' 19:00:30 #chair alikins bcoca jimi|ansible sivel funzo gundalow jtanner mattclay nitzmahone Qalthos ryansb shertel agaffney 19:00:30 Current chairs: Qalthos abadger1999 agaffney alikins bcoca funzo gundalow jimi|ansible jtanner mattclay nitzmahone ryansb shertel sivel 19:00:48 Good day everyone. 19:01:00 * nitzmahone lurks while eating 19:01:02 #info agenda: https://github.com/ansible/community/issues/159 19:01:15 hello 19:01:27 I am here-ish. This conflicts with my teams daily stand up for a few 19:01:54 #topic Extend module workflow to non-modules 19:01:56 https://github.com/ansible/community/issues/159#issuecomment-291567077 19:02:32 sivel: Cool. No worries. We'll ping you after the meeting if there's anything we think is blocking on you. 19:02:43 Looks like jtanner hada question. 19:02:45 :) 19:03:27 I assumed that "Nothing new to discuss while we wait on module metadata to be reworked." meant the final draft of metadata version1. 19:03:34 That's done and modules have that metadata. 19:03:51 abadger1999: its about other plugins having it also 19:04:04 I'll record that in the ticket. 19:04:05 19:04:29 But I don't see that as a blocker in the comment's history of past dicsussions? 19:04:31 you are looking at old discussion that was already put to bed 19:05:01 bcoca: If it's done, then we need to cross it off the list. 19:05:20 Metadata rework is done. <= not sure how to make clearer 19:08:43 okay, updated ticket. And left note for jtanner that it looks like everything is approved. When he's back he can tell us if he needs more decisions made 19:08:47 #topic Fix for wildcards inside of a path for fileglob lookup 19:08:52 https://github.com/ansible/community/issues/159#issuecomment-291567721 19:09:06 So I wrote up the pros and cons just before the meeting. 19:09:35 #info https://gist.github.com/abadger/7f9466272d84fad9ab7c4207a65a67fd <== pros and cons for wildcards in path portion of fileglob. 19:09:48 bcoca and I had a chance to discuss it a bit. 19:10:07 We're leaning towards an error if there's a wildcard in a relative path. 19:10:37 It's just ambiguous what the user intended to happen in that case. 19:11:07 Anyone else have ideas? 19:12:47 Okay. Moving on. 19:12:52 the other option i was toying with is ^ default to above and allow extra flag to determine behaviour (but also need to code it) 19:13:01 +1 to making it an error for now 19:13:05 19:13:10 other options can come in later 19:13:13 I'd be okay with a flag to change behaviour. 19:13:17 Cool. 19:13:20 #topic Define and document proposals process 19:13:32 https://github.com/ansible/community/issues/159#issuecomment-291567969 19:14:06 allanice001 doesn't seem to be here and the proposal hasn't been updated with the comments yet. 19:14:09 So moving on 19:14:28 #topic relative paths in ansible.cfg 19:14:29 https://github.com/ansible/community/issues/159#issuecomment-291568339 19:15:03 bcoca, alikins: So we are kinda in limbo of thinking we may have a solution but haven't thought it out enough. 19:15:42 Do we want to leave this on the agenda or say that making placeholders is the plan unless we come up with a problem when implementing it? 19:15:42 we have a couple of them, just seems we are busy with other stuff and this is lower priority, though i think it is something we shoud 'rule on' 19:15:49 time for a prototype/testcases? 19:16:19 not sure its worth it as ansible config would make it obsolete soon enough 19:17:17 we want to take it off the agenda and put it back on when we're ready to work on it? 19:17:37 * abadger1999 just looking for options to keep the agenda for thigns we're able to move forward on. 19:19:12 sounds reasonable 19:19:22 (removing from agenda for now) 19:19:58 Okay cool. I'll strike it as deferred. Feel free to put it back on once we're ready to code/decide 19:20:44 in that order! 19:21:21 #topic expand doc fileds 19:21:22 https://github.com/ansible/community/issues/159#issuecomment-291568454 19:21:26 #undo 19:21:26 Removing item from minutes: 19:21:31 #topic expand doc fields 19:21:48 So, bcoca, nitzmahone, and I all +1'd this. 19:22:05 it's been a week. anyone else want to vote/discuss? 19:22:21 Otherwise I'd say it's approved, feel free to implement. 19:25:10 #info Expand doc fields proposal approved 19:25:52 #topic Enforcing docs for all new plugins 19:25:53 https://github.com/ansible/community/issues/159#issuecomment-291569609 19:26:13 I think this one is basically "Approved once CI is able to test it" 19:27:21 Let's keep this on the agenda for next week to make sure mattclay is aware of it and then we can remove it from the meeting. 19:28:19 #topi Open Floor 19:28:24 #topic Open Floor 19:28:33 not all plugins .. 'all plugins that support docs' 19:28:37 Anyone else have something for today? 19:28:45 ^ sadly some don't yet 19:29:04 bcoca: Ah. Want to enumerate those in the comment? 19:29:27 bcoca: that way we have the list of what mattclay needs to add tests for in one place. 19:29:31 it might change, ansible-doc -h for 'current list' 19:29:48 k. I'll note to use ansible-doc -h to figure out what plugins need testing 19:30:37 Anything else today? 19:30:45 If not, I'll close in 60 seconds 19:31:48 #endmeeting