19:00:49 #startmeeting Public Core Meeting 19:00:49 Meeting started Tue Sep 27 19:00:49 2016 UTC. The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:49 The meeting name has been set to 'public_core_meeting' 19:01:18 #chair abadger1999 bcoca jimi|ansible nitzmahone 19:01:18 Current chairs: abadger1999 bcoca gundalow jimi|ansible nitzmahone 19:02:40 #topic Open Floor 19:02:43 * jimi|ansible waves 19:03:21 Nothing in todays agenda (so far) 19:03:40 Did the discussion arount auauthorized_key.py get resolved from last week https://github.com/ansible/community/issues/124 19:07:04 gundalow: I think the consensus was agreement with resmo 19:07:22 but no one took the followup. 19:07:24 abadger1999: cool, I didn't spot anything on the ticket, so wasn't sure if it got covered 19:09:31 #action abadger1999 to close tickets and PRs as wontfix with explanation that we think the authorized_key module should fail rather than create a home dir. Creating a home dir should be done by another task. 19:09:38 #undo 19:09:38 Removing item from minutes: ACTION by abadger1999 at 19:09:31 : abadger1999 to close tickets and PRs as wontfix with explanation that we think the authorized_key module should fail rather than create a home dir. Creating a home dir should be done by another task. 19:09:51 #info https://github.com/ansible/community/issues/124 19:10:09 #action abadger1999 to close tickets and PRs for authorized_keys recursively creating directories as wontfix with explanation that we think the authorized_key module should fail rather than create a home dir. Creating a home dir should be done by another task. 19:17:39 gundalow, jimi|ansible: Do we want to review the dimensiondata module_util PR? 19:18:05 I'm guessing that's something that needs to wait until 2.2 branches? 19:18:29 abadger1999: aye, I was gona ask about that 19:18:48 abadger1999: i said last week we're not doing any new module reviews until we do rc1 for 2.2 19:19:02 * gundalow will add a comment 19:19:06 Cool. 19:19:22 i was pinged about this ticket today https://github.com/ansible/ansible-modules-core/issues/1124 19:20:56 Is current behaviour, umask dependent? 19:21:02 checking 19:22:26 mode not preserved 19:23:06 should i work on it for 2.2 ? 19:23:17 I'm not sure about backwards compat but I would have found preserving mode it more intuitive and useful when I first started out with ansible. 19:23:27 Could probably implement it in the action plugin. 19:23:41 most of the code is probably in the action plugin 19:23:42 If mode not in the params: set mode = to mode of the file. 19:24:34 so ... 2.2 ... 2.3 ? 19:24:45 jimi|ansible: ^ 19:26:05 I guess... if we consider it a bugfix (this is the way it should always have been) then 2.2. If we think it's a feature (too big a change; add a preserve_mode=(True|False) parameter to implement this) then 2.3. 19:26:27 i'll work on the PR and then let someone decide when to merge 19:26:27 the code should be pretty short and non-invasive 19:26:28 how about that 19:26:50 Works for me. 19:27:23 assigned to myself 19:28:11 i have nothing else to add to the agenda 19:28:35 If there's enough of us here we can discuss: https://github.com/ansible/ansible/pull/17768/files 19:30:01 ready for dharmabumstead to review/edit/merge imo 19:30:03 (I may have to go offline shortly) agenda for Thursday is https://github.com/ansible/community/issues/126 19:30:05 Quite a bit of "What branch can this change be applied to right now" has been done by feel. This would help to set expectations and guidance about that. 19:31:38 set for 2.2 milestone and assign to scott ? 19:32:10 if a bugfix requires a minor new feature, i'm ok with that being added at this point btw 19:32:17 a new param is very very minor 19:38:52 so ... we done here? 19:39:16 Agenda for Thursday is https://github.com/ansible/community/issues/126 19:39:18 #endmeeting