15:01:46 #startmeeting Ansible Core public meeting 15:01:46 Meeting started Thu Feb 14 15:01:46 2019 UTC. 15:01:46 This meeting is logged and archived in a public location. 15:01:46 The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:46 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:46 The meeting name has been set to 'ansible_core_public_meeting' 15:02:35 * madonius waves 15:04:16 .hello2 15:04:17 maxamillion: maxamillion 'Adam Miller' 15:04:42 #chair alongchamps madonius maxamillion 15:04:42 Current chairs: alongchamps gundalow madonius maxamillion 15:05:40 #info Agenda https://github.com/ansible/community/labels/core 15:06:01 #topic Feature/alphanumeric password in passwordstore #38121 15:06:07 #info https://github.com/ansible/ansible/pull/38121 15:06:19 madonius: Hi, all yours 15:06:38 I am not quite sure what part I am to play 15:06:53 as I see it the only topic is my PR? 15:07:09 madonius: start with you :) 15:07:14 ok 15:07:45 I am a heavy user of ansible and there was a feature missing from the password store module 15:07:59 Thanks for adding it 15:08:05 this was added by me in PR 38121 15:08:20 and it's been there a while ^^' 15:08:49 so, I'd like you to merge it. Especially since somebody else expressed interest 15:09:12 looking 15:09:30 Looks sensible 15:09:56 yeah, I'm on board 15:09:57 +1 15:10:48 gundalow: you want to `rebuild_merge` or you want me to? 15:11:00 * gundalow will, thanks 15:11:07 +1 15:12:19 done 15:12:26 madonius: Thanks for raising it 15:13:04 thanks for the work :) 15:13:13 No DW today 15:13:16 #topic Open Floor 15:14:27 Anyone got anything else? 15:14:48 I had a failure on one of my tests that seems to be external (error was that docker couldn't find container id) 15:14:55 not sure where to bring it up 15:14:58 Got a link? 15:15:01 Is it still failing? 15:15:12 I didn't run it again yet, https://app.shippable.com/github/ansible/ansible/runs/107432/summary/console 15:15:25 or more directly: https://app.shippable.com/github/ansible/ansible/runs/107432/80/console 15:15:46 I wasn't sure if there was a command I could put on PR 52125 to run again, or if it needed another commit to trigger 15:16:25 there's also a link on this page that 404's: https://github.com/ansible/community/wiki/Testing, links to https://github.com/ansible/community/tree/master/group-testing 15:16:53 ah, all the `group-*` have been removed, I'll fix that 15:17:07 +1 15:17:41 yeah, that test seems like it might be a shippable problem ... or we goofed something 15:18:39 usually that test just gets skipped with no tests for my pulls 15:19:27 gundalow: new agenda item, I would like to revert this: https://github.com/ansible/ansible/pull/51657 15:21:24 alongchamps: wiki updated to remove broken link, thanks 15:21:31 :) 15:22:04 gundalow: originally the Wiki pages had a link back to the group-entries (as those were considered more official) 15:22:19 dag: nod, I need to check out the wiki repo and find and remove them all 15:22:24 #chair dag 15:22:24 Current chairs: alongchamps dag gundalow madonius maxamillion 15:22:41 I need to drop maxamillion you OK to continue, just one other item from dag ? 15:24:06 may not be core-related though :-) 15:24:20 gundalow: yeah, that's good 15:24:27 but since there was a meeting, and I think we need to revert it asap... 15:24:36 dag: or just fix the comments 15:24:45 #topic GitHub Issue templates 15:24:48 right, dropping now 15:25:11 dag: so what's up? ... I'm not familiar with the changes that occurred with the issue template ... what needs changing or do you just want to revert all together? 15:26:41 I honestly cannot see many if anyone actually filling out that portion of the template "Dependency Problems" 15:27:19 yeah, same 15:27:42 I'd wager some people don't even know exactly what 'dependency' means in that context 15:28:49 I'm +1 to revert 15:29:53 I am undecisive, therefore I would abstain from either down or upvoting it, if that is fine 15:31:10 sivel: ? 15:31:30 actually, do we even have quorum? (what is quorum numbers these days?) 15:31:32 +1 for me too 15:31:54 * maxamillion misses working on core stuff :/ 15:32:02 maxamillion: if has never been defined, although I have repeatidly tried to convince people that a vote requires 5 people 15:32:14 if people are changing templates, i need to be informed. 15:32:30 jtanner: someone added a new `DEPENDENCY PROBLEMS` section 15:32:37 I think we don't believe it is useful, or will be sued 15:32:38 jtanner: yo, we might change some ish 15:32:48 :) 15:32:49 we're talking about reverting that change 15:32:52 the bot died when 51657 was merged 15:33:05 if it's reverted, it will die again 15:33:16 Ok, so not just revert, but remove 15:33:33 i have to go fix a line of code, so i just need to know when it's happening 15:33:35 since the PR effectively moved the source of truth for the template 15:35:58 afk, brb 15:38:15 b 15:40:02 jtanner: how should we proceed? the general consensus is in agreement with dag in that we need to remove that change, either by revert or otherwise 15:41:10 either revert the PR and let me know that i need to fix the bot, or make a commit to remove that paragraph in the new template location 15:41:34 changing the file location is what creates pain for the bot 15:44:48 sivel: dag: any preference? 15:46:44 alright, I'll call it ... we'll just revert 15:46:55 jtanner: I'm going to revert the PR, do the needful on the bot 15:47:09 maxamillion: can we just remove that section via a new PR instead of reverting? 15:47:17 then we don't need any bot changes afaik 15:47:40 i may make a new section in BOTMETA so that i'm not having to deal with this anymore 15:47:42 that would be easiest 15:47:49 sivel: part of the initial complaint was that the old file was removed and that caused issues for certain users 15:51:54 i think the mistake is believing the templates are synonymous with troubleshooting guides. they need to remain simple and not arduous for issue reporters 15:52:26 so i see that as the reason why they're always in flux 15:56:51 alright 15:57:10 so what do we want to do here? 15:58:39 considered all things, I would side with jtanner and 'revert' 15:59:19 if actual reverting is an issue then a new PR would be a good way 16:00:20 I thought jtanner was suggesting we don't revert 16:00:48 just make a new commit to remove the new stanza 16:00:57 or have someone do it 16:02:48 maxamillion read the PR wrong 16:03:05 alright 16:03:07 i would be pro decluttering the templates 16:03:26 I'll file a new PR to remove the `DEPENDENCY PROBLEMS` section 16:05:44 thnx 16:07:32 alright, any other open floor business or can we light the fuse? 16:07:54 we're over time anyway 16:09:21 I would agree 16:09:29 let's call it a day 16:12:01 #endmeeting