ansible_windows_working_group
LOGS
20:00:00 <jborean93> #startmeeting Ansible Windows Working Group
20:00:00 <zodbot> Meeting started Tue Aug  3 20:00:00 2021 UTC.
20:00:00 <zodbot> This meeting is logged and archived in a public location.
20:00:00 <zodbot> The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:00 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:21 <jborean93> hello all
20:00:34 <briantist> hello
20:00:44 <jborean93> how's it going
20:01:19 <briantist> pretty good, yourself?
20:01:35 <jborean93> not too bad, just had my 2nd vaccine shot yesterday and my arm is quite sore
20:01:52 <jborean93> but could be worse!
20:01:59 <briantist> very nice! I hope the effects are limited to just soreness
20:02:21 <briantist> mine was that way, soreness late first day/second day, then all good
20:02:23 <jborean93> the first one was just the sore arm, hopefully that's the same here
20:02:43 <jborean93> #topic open floor
20:02:55 <jborean93> nitz is having some lunch so it's just us today
20:03:12 <briantist> sounds good, I got nothing Windows related
20:03:37 <jborean93> 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 <briantist> ahh that's the worst, huge motivation killer
20:05:04 <jborean93> yea, on the plus side I do learn more useless things :)
20:05:34 <briantist> 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 <briantist> 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 <jborean93> nice so it creates a build of the docs specifically for the changes in the PR?
20:08:29 <briantist> yeah, and also a version for `main` on every push to `main` (which includes PR merges)
20:09:07 <jborean93> sweet, how did you pull that off?
20:09:12 <briantist> 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 <briantist> 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 <briantist> with that done, the GitHub actions to generate docs and comment on the PR weren't really hard
20:10:20 <briantist> the hosting was going to be the thorny bit, and I stumbled on surge.sh
20:10:58 <briantist> 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 <jborean93> seems pretty cool
20:11:23 <briantist> so I really just put together a bunch of pieces
20:11:40 <jborean93> still that can be difficult in itself
20:12:02 <briantist> 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 <jborean93> rst is a pain, I remember hating writing docs because to generate them properly took a lot of time and effort
20:12:56 <jborean93> which I then forgot the steps and had to re-learn all the time :)
20:13:36 <briantist> 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 <briantist> 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 <briantist> it was enough to get me rendered RSTs, but not ideal long term
20:14:41 <briantist> so anyway, this is at least a success of the community coming together to solve a problem :)
20:16:23 <jborean93> yea that's great to see
20:16:37 <jborean93> 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 <jborean93> once done the plan is to publish the first release to AH
20:17:20 <briantist> 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 <briantist> we meant to get that started last week but had to put it off
20:18:11 <briantist> 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 <jborean93> I'll have a quite look, if it turns out to be too difficult I might hold off
20:18:55 <briantist> 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 <briantist> so it should be easy if you wanna get it out with the next release
20:19:54 <jborean93> I'll leave it for you, always good to help people work on a real issue
20:20:10 <jborean93> I'll just create a patch release that does nothing for the publish :)
20:20:46 <briantist> wait what is AH?
20:20:52 <jborean93> automation hub
20:21:09 <briantist> ahhh ok, I have almost no familiarity with AH but have heard of it
20:21:39 <jborean93> it was meant to have been done for the new 2.0 platform release but slipped through the cracks
20:22:12 <briantist> 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 <briantist> thanks for the reminder too I'll look at setting some calendar time with him
20:22:31 <jborean93> sounds good
20:22:41 <jborean93> anything else you would like to talk about?
20:22:47 <briantist> nope all good here
20:23:06 <jborean93> sweet, have a good one
20:23:15 <jborean93> #endmeeting