15:00:24 #startmeeting Documentation Working Group aka DaWGs 15:00:24 Meeting started Tue Oct 11 15:00:24 2022 UTC. 15:00:24 This meeting is logged and archived in a public location. 15:00:24 The chair is DonNaro[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:00:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:24 The meeting name has been set to 'documentation_working_group_aka_dawgs' 15:00:47 who's around to talk docs? 15:01:02 o/ 15:01:03 hi acozine 15:01:03 #chair acozine 15:01:03 Current chairs: DonNaro[m] acozine 15:01:33 hi Don Naro 15:01:56 https://github.com/ansible/community/issues/643#issuecomment-1267321151 15:02:02 * #info https://github.com/ansible/community/issues/643#issuecomment-1267321151 15:02:29 let's see what Sandra left in the agenda. I hope she's having fun right now. 15:03:05 autumn in New England, that's built-in fun 15:03:15 how is Hacktoberfest going? 15:03:41 Hacktoberfest has been great! 15:04:26 #info we got a lot of really great commits and work done during Hacktoberfest. in fact we closed all the issues we had open super quickly and are all out. 15:04:26 wow, and it's only the 11th of the month! 15:04:38 thanks to everyone who got involved 🎉 15:05:24 the PR queue was really busy for a few days but that event had a pretty solid result. all those true/false booleans. 15:06:03 also small things like replacing Latin terms and common spelling mistakes 15:06:29 that was fabulous timing, needing widespread but tightly focused work just in time for Hacktoberfest 15:06:55 indeed. it was great. 15:06:55 ooh, if folks were replacing latin terms, maybe they were reading the style guide!!! 15:07:25 it's always heartening to find out someone is using the docs 15:09:13 agreed. it was my first Ansible Hacktoberfest and I really enjoyed it 15:09:33 that was the liveliest one I've participated in for sure 15:09:53 have we stopped doing @ room pings for the start of meetings? I got one for the 1 hour reminder, but I think last time too I missed the start of the meeting 15:10:04 seems I've really grown to rely on the pings :-/ 15:10:11 o/ 15:10:15 #topic release preparation for core 2.14 15:11:01 briantist: hi there. no, that's my bad. apologies 15:11:14 #chair briantist 15:11:14 Current chairs: DonNaro[m] acozine briantist 15:11:47 @room ping 15:13:04 argh. that ping didn't seem to work. I think being double booked for so long meant I was really more of a casual lurker on most DaWGs sessions. 15:13:50 tremble felixfontein hi, friendly reminder for the DaWGs if you're around to talk docs 15:13:56 I'm on IRC on the @ room is just some text for me that I've set my client to alert on 15:14:05 thank you :) 15:14:54 maybe it's `@here`? 15:14:54 I'm double booked (as usual), so will be lurking but probably either slow to respond or quiet 15:15:20 briantist: oh, sneaky! 15:15:49 I reply on my work calendar to alert me, which is mostly does 15:15:50 s/is/it 15:16:08 jeez, also s/reply/rely 15:16:14 well, when folks started using that instead of pinging individuals, I also got left out since I wasn't on matrix, not sure who recommended it the IRC text matching thing but it was a good idea 15:16:36 don't let me write any docs today, apparently it's Typo Tuesday at my house 15:16:36 lol 15:17:21 yeah, it's a great solution 15:17:28 Tpyo Twosday 15:17:34 briantist: did my `@room` ping actually work for you then? 15:17:45 yes 15:19:10 sweet. I'll make a note to do that. I'd actually like to get some docs for running these meetings more effectively when Sandra is on PTO. 15:19:35 so we can keep the party going while she's enjoying life 15:20:18 right. trying to steer back to the 2.14 topic. I know I've got some todo items for the release. 15:20:39 has anyone got anything they need to discuss on that topic? 15:21:32 * acozine shakes her head 15:22:28 sorry. kids came barging in after school and I had to change rooms in the house. 15:22:58 ah, the joys of WFH 15:23:19 hopefully that head shake means nothing to discuss. and not shaking your head in disgust. lol 15:23:29 heh, nothing to discuss 15:24:33 of course. although I might ask as this is my first rodeo but Sandra said there will be a porting guide that we need to backport along with a docs update for 2.14 15:25:27 if anyone here is familiar with that porting guide and knows the routine, I wouldn't mind you double checking my work. 15:26:28 there used to be a checklist of "Docs Release Tasks" or something like that, and I think it had descriptions of the porting guide tasks 15:27:19 cool. I'm pretty sure I can dig it up in a doc that Sandra shared with me last week. I just need to go through all that again. 15:28:17 here's the checklist from 2.13, not sure how helpful it will be for your specific question though https://github.com/ansible/ansible/issues/77574 15:29:13 nothing to disgust 15:29:53 I have to run for a meeting that requires my full attention, sorry to whine about pings and then duck out shortly after lol 15:30:01 #unchair briantist 15:30:01 Current chairs: DonNaro[m] acozine 15:30:18 later! 15:30:27 ciao briantist 15:30:51 for the record, "nothing to disgust" kinda sounds like an album from the 90s 15:30:57 heh 15:31:05 I appreciate the commitment there to Typo Tuesday 15:31:20 that was a great shout btw acozine lead me to https://github.com/ansible/ansible/issues/78880 15:31:42 still need help navigating all the repos and issues so cheers 15:32:27 yw, glad it helped 15:33:14 it did. it also lead me to a bunch of other questions but I'll get on to them later and might ping you if I hit any snags. 15:35:31 any time 15:35:47 let's keep the DaWGs party moving anyway 15:35:58 so many rabbitholes to go down 15:36:47 #topic userguide split 15:37:08 one of the recurring items from the DaWGs agenda 15:37:36 #info remaining work for the userguide restructure is to set up and test redirects 15:38:13 I guess this is just a reminder to myself to make sure that gets done this week 15:38:54 it's only just Thaipo Tuezday though 15:38:56 heh 15:39:35 Last time I looked at the user guide changes, there were a lot of orphan pages (pages at the old URLs with no redirects) 15:39:48 but it's been a while 15:40:11 yeah, that's still the case unfortunately and I need to get it fixed. 15:40:18 ah, so they all still need to be done? 15:40:28 shakes head yes 15:40:30 I don't envy you the task 15:41:32 I've taken a look under the hood already and am gearing myself up for it 15:41:43 I can always ping you on the PR and you can laugh at me lol 15:42:11 once again samccann was very helpful and gave me a few pointers so I think it'll be alright 15:42:11 I think those PRs are on the private repo, so I wont' be able to review 15:42:16 ah, nuts 15:42:23 but there are lots of examples 15:43:04 I was cautious when I set up the orphan pages and the anchors so I'm hoping the redirects won't be too bad and will make sense for others who might need to go in there 15:43:06 definitely deploy them to the testing docsite, though, we saw some unexpected multi-redirect interactions in the past 15:43:24 will do 15:43:46 * acozine sings the Talking Heads ("you may ask yourself, how did I get here?") 15:43:57 and now that song is in my head 15:44:02 water flowing underground . . . 15:44:08 sorry? 15:44:12 same as it ever was 15:44:30 into the blue again... 15:44:55 we should rick roll Sandra next week 15:45:01 #topic never gonna give you up 15:45:24 heh 15:45:59 #topic proposal to archive docs for EOL releases 15:46:16 #info reminder on https://github.com/ansible-community/community-topics/issues/78 15:46:58 not sure if there's anything to discuss here today but didn't want to totally skip it 15:47:38 that will be a monumental achievement 15:48:06 though it may involve a certain amount of grumbling and bring folks out of the woodwork who are still using, say, Ansible 2.4 15:48:44 with luck it will also highlight any places where people are still reading the old docs because they cover some specific topic better than the current ones 15:50:15 true. I didn't consider that. it will solve a lot of problems and help folks connect with the best / right content though. 15:50:32 yes, absolutely 15:50:35 so, yeah, monumental achievement and fair dues to samccann 15:50:44 10 mins left 15:51:00 let's take a look at some doc PRs maybe 15:51:12 #topic recently opened doc PRs 15:51:57 I see there's a new one for managed node requirements that I haven't looked at 15:52:02 I'll check that out 15:52:29 if I can be a little selfish I have my own PR in the queue: https://github.com/ansible/ansible/issues/79022 15:53:18 that looks like the issue 15:53:18 I picked this one up from a chat with ssbarnea 15:53:47 you're right. it's the issue. here's the PR: https://github.com/ansible/ansible/pull/79077 15:53:50 bah 15:54:51 sorry, was busy elsewhere :( 15:56:00 #chair felixfontein 15:56:00 Current chairs: DonNaro[m] acozine felixfontein 15:56:11 hi felixfontein better late than never 15:56:27 whoops. maybe I shouldn't have chaired you if you didn't `o/` 15:56:27 Don Naro: that's a useful change, I agree with sivel about keeping the note about keywords somewhere in the docs 15:57:15 a link over to the "include or import" docs page might also be helpful on those pages 15:57:26 thanks acozine I'll take another stab at it so. it's good to hear that it makes sense to someone else. 15:57:47 really appreciate you taking a look 15:57:57 #topic open-floor 15:58:27 I guess we're just about out of time but has anyone got anything they'd like to mention? 15:58:47 https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse.html << page I was referring to above 15:59:25 I'm excited for AnsibleFest next week 15:59:31 woot 15:59:48 are you going to attend in person? 15:59:49 I am, yes 15:59:55 wow, awesome 16:00:02 are you flying over to attend? 16:00:02 I'm jealous 16:00:21 no I won't be able to attend this year but hopefully next 16:00:21 ah, bummer 16:00:47 I will be doing some stuff online like moderating breakout sessions for the contributor summit next week 16:01:40 I hope you have a great time and safe trip anyway 16:01:40 thanks! 16:01:40 sure it'll be a blast 16:01:56 * acozine has to run to $NEXT_MEETING 16:02:06 bye acozine see you later 16:02:08 thanks Don Naro for running the meeting! 16:02:08 thanks for hanging out 16:02:15 #endmeeting