20:00:00 #startmeeting Ansible Windows Working Group 20:00:00 Meeting started Tue Aug 3 20:00:00 2021 UTC. 20:00:00 This meeting is logged and archived in a public location. 20:00:00 The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:00 The meeting name has been set to 'ansible_windows_working_group' 20:00:21 hello all 20:00:34 hello 20:00:44 how's it going 20:01:19 pretty good, yourself? 20:01:35 not too bad, just had my 2nd vaccine shot yesterday and my arm is quite sore 20:01:52 but could be worse! 20:01:59 very nice! I hope the effects are limited to just soreness 20:02:21 mine was that way, soreness late first day/second day, then all good 20:02:23 the first one was just the sore arm, hopefully that's the same here 20:02:43 #topic open floor 20:02:55 nitz is having some lunch so it's just us today 20:03:12 sounds good, I got nothing Windows related 20:03:37 I'm still trying to fill in the missing pieces for the pypsrp refactor. Seems like every thing I want to fix is some deep rabbit hole which is very time consuming :( 20:03:56 ahh that's the worst, huge motivation killer 20:05:04 yea, on the plus side I do learn more useless things :) 20:05:34 on the opposite end of the spectrum, I managed to actually see an idea through with a minimum of pain (getting Ansible collection docs built on each PR) 20:05:49 you might have seen this already since I've been spamming it around IRC just because I'm so happy with it: https://github.com/ansible-collections/community.hashi_vault/pull/121 20:08:08 nice so it creates a build of the docs specifically for the changes in the PR? 20:08:29 yeah, and also a version for `main` on every push to `main` (which includes PR merges) 20:09:07 sweet, how did you pull that off? 20:09:12 RST is tricky (at least for me) so being able to see it rendered it huge, and I hope it encourages more people who want to make docs changes 20:09:41 well, Felix Fontein got a command going that inits sphinx for a collection and generates a build script, so that's the hard part 20:10:05 with that done, the GitHub actions to generate docs and comment on the PR weren't really hard 20:10:20 the hosting was going to be the thorny bit, and I stumbled on surge.sh 20:10:58 they host any number of static sites, including free subdomains or custom domains, with SSL, for free, with a CLI... it fit the bill perfectly 20:11:20 seems pretty cool 20:11:23 so I really just put together a bunch of pieces 20:11:40 still that can be difficult in itself 20:12:02 even if I'm the only one who uses it (my collection is pretty low traffic) it'll remove a lot of barriers from me writing better docs, so that's great 20:12:44 rst is a pain, I remember hating writing docs because to generate them properly took a lot of time and effort 20:12:56 which I then forgot the steps and had to re-learn all the time :) 20:13:36 right, exactly, I expect a lot of shared documentation in this collection once I put out more plugins and modules, and I just started the beginnings of those docs recently 20:14:01 I got a nice workaround from the docs team of copyign my docs to core's, and then running that doc build 20:14:13 it was enough to get me rendered RSTs, but not ideal long term 20:14:41 so anyway, this is at least a success of the community coming together to solve a problem :) 20:16:23 yea that's great to see 20:16:37 I'm just about to tackle https://github.com/ansible-collections/ansible.windows/issues/258 so hopefully it's a simple problem 20:16:47 once done the plan is to publish the first release to AH 20:17:20 oh ok! if you haven't started that yet, I was going to use it as an issue to help a coworker get acquainted with the process of opening a PR 20:17:39 we meant to get that started last week but had to put it off 20:18:11 if you fix it first that's fine too, there's always other issues, not asking you to hold off by any means 20:18:30 I'll have a quite look, if it turns out to be too difficult I might hold off 20:18:55 I think we already know the fix and it's quite simple (I think it's shifting one staement to be inside the `if`, IIRC) 20:19:18 so it should be easy if you wanna get it out with the next release 20:19:54 I'll leave it for you, always good to help people work on a real issue 20:20:10 I'll just create a patch release that does nothing for the publish :) 20:20:46 wait what is AH? 20:20:52 automation hub 20:21:09 ahhh ok, I have almost no familiarity with AH but have heard of it 20:21:39 it was meant to have been done for the new 2.0 platform release but slipped through the cracks 20:22:12 anyway, I'll keep you updated in case we end up not being able to get around to fixing it in a timely manner, no reason to keep it broken for an extended period 20:22:26 thanks for the reminder too I'll look at setting some calendar time with him 20:22:31 sounds good 20:22:41 anything else you would like to talk about? 20:22:47 nope all good here 20:23:06 sweet, have a good one 20:23:15 #endmeeting