20:00:04 <nitzmahone> #startmeeting Ansible Windows Working Group
20:00:04 <zodbot> Meeting started Tue Feb 25 20:00:04 2020 UTC.
20:00:04 <zodbot> This meeting is logged and archived in a public location.
20:00:04 <zodbot> The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:04 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:04 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:12 * jborean93 too quick
20:00:16 <jborean93> o/
20:00:22 <nitzmahone> Nothing new on the agenda
20:00:33 <nitzmahone> #chair jborean93
20:00:33 <zodbot> Current chairs: jborean93 nitzmahone
20:00:55 <jborean93> Just an FYI for whoever might be reading this log later on
20:00:59 <nitzmahone> #topic open floor
20:01:09 <jborean93> But here is a test setup for the `ansible.windows` collection https://github.com/ansible-collections/ansible.windows
20:01:28 <jborean93> CI is green and with the redirection being added in base things should just be working as it does in 2.9
20:01:44 <jborean93> once migration is underway that collection will be based on the latest devel changes
20:02:08 <nitzmahone> Sup dag?
20:04:17 <nitzmahone> jborean93: I haven't looked, is there an option to preserve the tests now, or are we going to have to copy over from an old copy of devel manually to preserve comments and stuff?
20:04:47 <jborean93> only tests taht needed to be modified will be modified
20:04:52 <jborean93> the rest will remain untouched
20:05:08 <jborean93> and AFAIK only a very small subset of tests needed to be modified
20:05:29 <jborean93> I haven't actually found one yet but there will probably be 1 or 2 sprinkled in there
20:06:35 <briantist> 👋first WWG meeting, just want to say I'm excited for the collection breakout
20:06:56 <jborean93> welcome briantist
20:12:14 <nitzmahone> briantist: anything you want to discuss? We're at open floor, and other than the pending freeze/migration in the next couple weeks, nothing burning to discuss from my end.
20:12:30 <briantist> as a general question, what's the etiquette on requesting PR review? I know it's easy for things to slip by and that everyone's busy (especially with the collection migration), but also don't want to be too annoying pinging people/channels about it
20:12:34 <nitzmahone> (if not, we'll close in 2min)
20:12:59 <jborean93> usually a quick ping here or asking in the meeting is fine
20:13:19 <jborean93> Once I'm done with my current work I was planning on doing another round of reviews on the current PRs
20:13:55 <nitzmahone> The process may change a bit with the plugins being split out as well, especially for the community collection.
20:14:58 <nitzmahone> Basically the intent is to let the community drive the process more, and each working group can put whatever process they want in place.
20:16:24 <briantist> sure makes sense, I'm looking forward to that. The Windows group already seems to have a pretty good loop going, hope it improves things in some of the other areas too (I have a hashi_vault lookup PR that I can't seem to get anyone to look at)
20:17:48 <jborean93> the bar for community PRs should be lower than core so hopefully post migration it will be easier to get your hashi_vault lookup PR in
20:22:35 <briantist> cool, thanks folks, I don't have much else at the moment
20:25:06 <nitzmahone> Ok, well hope you keep seeing you around! We'll close out for this week. I'll be traveling next week, so Jordan will probably have to run this.
20:25:14 <nitzmahone> *to
20:25:25 <nitzmahone> #endmeeting