16:00:13 #startmeeting Docs Working Group aka DaWGs 16:00:13 Meeting started Tue Jan 19 16:00:13 2021 UTC. 16:00:13 This meeting is logged and archived in a public location. 16:00:13 The chair is acozine. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:13 The meeting name has been set to 'docs_working_group_aka_dawgs' 16:00:23 #topic opening chatter 16:00:30 https://docs.ansible.com/ansible/ < missing index 16:00:38 o/ 16:00:39 #chair lmodemal dmsimard 16:00:39 Current chairs: acozine dmsimard lmodemal 16:00:48 Hello ALL! 16:00:48 #chair bcoca samccann 16:00:48 Current chairs: acozine bcoca dmsimard lmodemal samccann 16:00:58 well that's unpleasant. 16:01:11 ahhh 16:01:27 I bet that's the fallout from the Problematic Too-Broad Redirect being removed 16:01:42 that should redirect to docs.ansible.com/ansible/latest/ 16:01:59 hi! 16:02:01 thanks bcoca 16:02:04 #chair felixfontein 16:02:04 Current chairs: acozine bcoca dmsimard felixfontein lmodemal samccann 16:02:21 i think it's a docsite problem yeah. the old docsite uses docs.ansible.com/ansible/index 16:02:22 acozine: sdoran noticed, but reported in slack, i realized your attentino was 'here' 16:02:32 heh, yep 16:03:25 so we'll make this a quick meeting and then go figure out what's gone wrong 16:03:38 who else is around? 16:04:43 * dericcrago waves 16:04:48 #chair dericcrago 16:04:48 Current chairs: acozine bcoca dericcrago dmsimard felixfontein lmodemal samccann 16:04:49 o/ 16:04:53 #chair gwmngilfen 16:04:53 Current chairs: acozine bcoca dericcrago dmsimard felixfontein gwmngilfen lmodemal samccann 16:05:17 "consistent furniture achievement" 16:05:59 alongchamps: andersson007_ baptistemm briantist cyberpear madonius join us if you're around 16:06:26 heh, we'll vote on upholstery for you next week gwmngilfen 16:06:43 so think about whether you prefer floral or stripes 16:06:48 * alongchamps waves 16:06:54 #chair alongchamps 16:06:54 Current chairs: acozine alongchamps bcoca dericcrago dmsimard felixfontein gwmngilfen lmodemal samccann 16:07:03 good morning/afternoon/evening everyone 16:07:05 I'm in multiple work meetings so only kinda here 16:07:27 briantist: that describes 2/3rds of people chaired 16:07:28 though I asked this yesterday and it maybe got lost, just curious: "I just noticed the Japanese (2.9_ja) docs, I'm curious where that content/translation comes from? I didn't really see it in the docsite. Especially interested in the stuff that gets auto-generated from changelog fragments and such." 16:07:29 briantist: cool, I won't make you furniture then, though I think today will be a short meeting 16:07:51 #topic open floor 16:08:25 briantist: the japanese docs are generated by Red Hat's translation team 16:09:06 the first translation, the one you see for 2.9, was done very much ad hoc, and lives in a branch outside of the main repo 16:09:53 #info no more Thursday supplemental DaWGs meeting. We are implementing the docsite split now and will cover details in Tuesday meetings 16:10:06 ah I see, are there any plans for open translation or anything like that? 16:10:08 when you say you don't see the translation on the docsite, what do you mean? 16:10:24 I meant in the docsite repo 16:10:28 the source 16:10:39 oh, in `docs/docsite/rst` 16:10:55 yeah, right now it's not there, because it would be a whale of a PR to devel 16:11:22 we're looking to formalize the process this year 16:11:33 cool, thanks for the info 16:12:39 but RH doesn't do open translations, because we have no way to verify that folks aren't making the translated docs incorrect or full of profanities 16:13:20 it's unfortunate, but understandable 16:13:29 yeah, makes sense 16:14:10 definitely 16:14:16 * bcoca is pretty sure everyone with a forgein language tatoo has been lied to about the meaning of such tatoo 16:14:27 heh 16:14:55 Following up on last week, I did not summarize our discussion of the possible uses of the `/docs/` folder in collections and create an issue for tracking ideas. I will get to that this week. 16:15:57 heh, yep, anything that's supposed to be "spiritual" is especially suspect 16:16:23 #info docsite work is progressing. We will post here when we have test site updates available for review. 16:17:07 mmm, we did manage to get the new URL for `/ansible-core/` working, but the content there is no different from the current content at `/ansible/` 16:17:17 so there's nothing to review 16:17:22 but it's on the test site if anyone is curious 16:18:21 have a link ? 16:18:44 dmsimard: http://docs.testing.ansible.com/ansible-core/2.11/ 16:18:49 it's quite boring, I'm afriad 16:19:02 but it exists, and that's a step in the right direction 16:19:17 thanks :) 16:19:35 remember, SSL is not enabled on the testing site 16:20:19 so you can move from the testing site to the production site by deleting `testing` in the URLs, but if you want to move the other direction, you must edit `https` to say `http` 16:20:41 someday we will enable SSL on the testing site too 16:20:45 but today's not looking good 16:22:52 o/ 16:23:13 ok if we don't have urgent business we should end this meeting so we can fix the docsite 16:23:25 hi abadger1999! 16:23:42 bom dia! 16:23:46 anybody have stuff they want to bring up? 16:24:02 PRs to review, issues to ponder, progress to report, questions to ask? 16:24:51 Last weekened I mentioned the FQCN abbreviation being used without prior explanation -- should I create an issue so we can improve that in the future ? 16:25:07 dmsimard: sounds good 16:25:16 you could open a PR to add `FQCN` to the glossary 16:25:26 or at least suggest that in the issue 16:25:52 oh it's not even in the glossary -- I can take that 16:26:02 also point to where it is used w/o explanation cuz I know we put in hovers over some of them 16:26:21 works for me 16:26:28 since we don't control which page users see first, we can't do the classic "define it the first time, use the abbreviation thereafter", but if we link to the glossary we can help folks figure it out 16:26:54 well, I guess we could define it once on every page . . . 16:26:55 erg 16:27:30 yeah it is supposed to be defined on every page on first use. 16:27:30 yeah that wouldn't be very DRY :) 16:27:43 hello 16:28:20 hi baptistemm! 16:28:21 I was suggesting perhaps an automated tooltip or link through sphinx but I don't know whether it'd be a good idea or if it's even possible :) 16:28:32 hi acozine and everybody ! 16:28:46 we're doing a short meeting today, pretty much just open floor 16:28:46 yeah we have it as a tooltip in sphinx on some places 16:28:57 i'll dig it up and post how here later... after we get the docsite fixed 16:29:03 * samccann fixated on broken docsite 16:29:10 that's a good thing 16:29:18 hello baptistemm 16:29:22 fixing the broken docsite is important 16:30:24 oh actually samccann already added FQCN to glossary https://github.com/ansible/ansible/commit/4aedd1b987150baae4b11200de916c87c53e6d30 but it hasn't made it's way to /latest/ yet: https://docs.ansible.com/ansible/latest/reference_appendices/glossary.html 16:30:30 thanks dmsimard for keeping on top of that 16:30:38 ah, so we need a backport 16:30:55 to stable-2.10 ? 16:30:56 or it will fix itself when 3.0.0 comes out 16:31:07 yeah, if we want it in current latest, backport it to stable-2.10 16:31:17 ok I'll take care of the backport 16:31:24 thanks 16:31:33 what else is on people's minds? 16:33:01 thanks dmsimard 16:33:17 #action dmsimard to backport PR that adds FQCN to glossary 16:33:31 hearing no other topics, I think we'll end the official meeting early 16:33:42 and turn our attention to regex and redirects 16:33:47 * acozine shudders 16:34:07 chat welcome in the channel any time 16:34:58 thanks abadger1999 alongchamps baptistemm bcoca dericcrago dmsimard felixfontein gwmngilfen lmodemal samccann 16:35:08 #endmeeting