16:55:02 #startmeeting Docs Working Group meeting extension 16:55:02 Meeting started Tue Jan 19 16:55:02 2021 UTC. 16:55:02 This meeting is logged and archived in a public location. 16:55:02 The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:55:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:55:02 The meeting name has been set to 'docs_working_group_meeting_extension' 16:55:27 #topic adding breadcrumbs to the plugin pages 16:55:30 #info https://github.com/ansible-community/antsibull/pull/240 16:55:44 #info acozine ended the main meeting too early, mea culpa 16:56:58 #info the PR would add index pages at the namespace level 16:56:58 Heh :-) 16:57:50 abadger1999: what do you think of the PR? you probably have to review the code changes ;) 16:58:31 #info example of the breadcrumbs in action: https://ansible.fontein.de/collections/community/crypto/x509_certificate_module.html 16:59:57 alongchamps lmodemal samccann all +1'd the PR outside of the official meeting 17:01:17 #chair abadger1999 felixfontein alongchamps 17:01:17 Current chairs: abadger1999 acozine alongchamps felixfontein 17:01:44 not sure if I need to do that or not, hope the info entries will all work correctly 17:02:34 * felixfontein switches room 17:03:27 physical room? or chat-room? 17:03:54 tadeboro: you were offline earlier, want to join the discussion about breadcrumbs? 17:04:38 physical room. I'm back now :) 17:05:52 acozine: Sorry, I will skip today's debate. I need to start acting on GitHub notifications from today. Reviewing collections turned out to be quite labor intensive. 17:05:56 felixfontein: Yeah, I'll have to look at the code. The concept and output are nice, though :-) 17:06:49 tadeboro: yes, collection reviews are challenging 17:06:54 thanks for doing them! 17:07:34 yw! 17:08:36 I also have another PR: https://github.com/ansible-community/antsibull/pull/238 which processes routing metadata and adds stub pages for moved / renamed / tombstoned modules/plugins 17:09:37 hmmmm 17:10:42 adding >1 page per module for all modules in 2.9 seems like a lot of overhead; would those pages really show up for users given the server-side redirects we put in place? 17:12:15 I thought about just hardcoding something that removes them all. the problem is when ansible-core 2.x suddenly starts moving out more content to other collections, then we'll either have to whitelist these modules/plugins explicitly, or add new redirects 17:13:24 last I heard, moving the remaining plugins out of ansible/ansible is an extremely low priority 17:13:34 and unlikely to happen in the next few years 17:14:22 on the ohter hand, the fewer hard-coded exceptions we have to maintain, the better 17:14:24 so I'm torn 17:17:07 they really dont need to be hardcoded, they are all in same place 17:19:20 bcoca: the routing file of ansible-core is still huge :) 17:20:32 felixfontein: can we carry the stub-pages PR over to next week? 17:20:53 I'll be sure to make it a proper topic 17:21:16 felixfontein: we keep moving everything 17:21:26 but I think getting more folks thinking about it would be good 17:23:47 sounds good! 17:25:43 thanks! 17:25:49 #endmeeting