19:30:29 #startmeeting docs 19:30:29 Meeting started Wed Nov 30 19:30:29 2022 UTC. 19:30:29 This meeting is logged and archived in a public location. 19:30:29 The chair is darknao. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:30:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:30:29 The meeting name has been set to 'docs' 19:30:39 #topic Roll call 19:30:41 #chair pboy darknao pbokoc py0xc3[m] 19:30:41 Current chairs: darknao pbokoc pboy py0xc3[m] 19:30:57 hi everyone! 19:31:09 Hello... 19:31:11 .hi 19:31:12 pboy: pboy 'Peter Boy' 19:31:14 .hello hankuoffroad 19:31:15 hankuoffroad[m]: hankuoffroad 'None' 19:31:37 hi all 19:34:06 ok let's start 19:34:12 #topic Agenda 19:34:14 #link https://discussion.fedoraproject.org/t/docs-meeting-agenda-2022-11-30/44493 19:34:16 #info Announcements 19:34:18 #info Action item followup 19:34:20 #info Follow up on plan for missing install guide 19:34:22 #info Open Floor 19:34:27 #topic Announcements 19:34:36 #info New variant-oriented homepage is live 19:34:38 #info New Workstation docs has been shipped 19:34:40 #link https://docs.fedoraproject.org/en-US/workstation-docs/ 19:34:42 #info Next milestone is F38 (2023-04-18) 19:34:44 #info We use GitLab to track work: https://gitlab.com/groups/fedora/docs/-/boards 19:35:18 Any other announcements? 19:36:03 ok, proceeding to the next topic then 19:36:11 #topic Previous action items 19:36:22 #info pboy was to test run the new builder script on Mac 19:36:38 Hmmm, same procedure as every year. :-) 19:36:56 still on todo 19:37:11 I created a ticket for that so I don't think we need to action you for that anymore 19:37:17 #link https://gitlab.com/fedora/docs/templates/fedora-docs-template/-/issues/7 19:37:21 I tested the script on a Mac and put my results in a comment there. 19:37:33 thanks AlanBowman[m] 19:37:42 TL;DR, it doesn't work. 19:37:44 AlanBowman[m]. +1 ! 19:38:07 I guess that need some extra documentation to make it works, or make changes to the script 19:38:29 #info darknao was to set up Vale linting on contributors-guide and Fedora Linux homepage repositories 19:38:40 I don't think it will work on a Mac, it's looking for a utility that isn't available on macOS. 19:40:16 AlanBowman[m]: I think we can still modify the script to look for another tool for mac, or just drop this feature (only for mac) 19:40:21 darknao: I saw one set up for a repo. How does it work? Does it show the results for writers before git push or is i for reviewers? Great to hear 19:41:10 back to Vale: so I've set that up for the contributors-guide. It'll run the tool automatically for each merge request & commit 19:41:37 I don't have any MR on this repo to show you, but for individual commit, that looks like this: 19:41:43 https://gitlab.com/fedora/docs/community-tools/documentation-contributors-guide/-/pipelines/708679375/codequality_report 19:41:47 darknao: I understand. 19:42:06 There is a lot of errors right now that need to be fixed 19:42:51 nice 19:42:52 I'll see if I can write a quick documentation about how to use the tools and fix errors 19:43:23 I'll most likely just give a few links to the upstream documentation 19:43:51 like this one: https://redhat-documentation.github.io/vale-at-red-hat/docs/main/user-guide/introduction/ 19:44:29 it's not upstream, but it's still good documentation 19:45:26 darknao: Cool, I'll run it for next commits 19:45:41 Does it have any automatic correction functions ? 19:46:05 copperi[m]: I don't think there is 19:46:12 it's only reporting 19:46:51 Can we make it part of the local preview? 19:46:59 ok 19:47:36 maybe, but that require to install the tool first, which is not available in fedora repositories 19:48:02 there is a docker image, so I think we could use that instead in the script 19:48:10 OK, so we can't, actually 19:48:27 that's something to look into 19:49:40 #action darknao to document the use of Vale for doc writers 19:50:20 so we have 2 more actions to mention, but I'll keep those for the next topic 19:50:26 which is.... 19:50:43 #topic Follow up on plan for missing install guide 19:51:20 we had a few complains about the missing install guide & administration guide lately 19:51:55 and I think it's most likely caused by the broken links we have scattered everywhere 19:52:08 #info pboy was to create a redirect for old install-guide links 19:52:10 #info darknao was to list broken docs links in websites 19:52:18 Yeah, regarding the admin guide there is a wrong link in the tools box. I have to fix it. 19:52:36 I gathered the list of broken links on the websites 19:52:41 #link https://gitlab.com/fedora/docs/fedora-linux-documentation/release-docs-home/-/issues/4#note_1185856253 19:52:51 And yeah, I'll edit the getting started page with the proper aliases 19:54:08 so yeah, we need to either fix those links and replace them with the correct document link or redirect everything to the getting started page 19:54:28 For most of the links we have proper replacements, I think 19:55:13 also: $ grep DOC /etc/os-release 19:55:25 DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f37/system-administrators-guide/" 19:55:33 that need to be fixed too 19:56:22 Where can we find the admin guide ? 19:57:07 De we have to use the 36 revision? 19:57:20 well, that's the problem, we don't have an admin guide for f37 19:58:17 Yes, the admin guide is unchanged since at least 6 revisions. We don't have a "revision-less" address? 19:58:49 no, it was always linked to a fedora version 19:58:57 just like the install guide 19:59:22 latest available is https://docs.fedoraproject.org/en-US/fedora/f36/system-administrators-guide/ 19:59:32 The problem now is, the f36 revision works, but links to 37, which we would link back to 36 .... 19:59:47 in the "View latest" 20:00:03 Can we remove the "View latest " part? 20:00:23 I suppose, it is automatically added? 20:00:36 no we can't, since it's not the latest ^^ 20:00:58 but if you want to get the same admin guide in f37, then we just need to add it back to the f37 branch 20:01:29 Hm, would not be nice. 20:01:54 Can we create a new address like https://docs.fedoraproject.org/en-US/fedora/system-administrators-guide/ 20:02:25 In the long term we want to get rid of ot 20:03:07 I was under the impression that we initially removed it because it was mostly obsolete content 20:03:52 Yes, you are right! Is is only for the time, the replacement like the anaconda guide is not in place. 20:04:00 bringing it back, even with another url seems like a step back 20:04:30 in that case, I would recommend to just add it back to the f37 branch, and once we have a replacement, remove it for good 20:04:34 agreed. It is kind of a gapstop solution 20:04:43 and that way, we don't even need to update any links 20:04:50 at least regarding the admin guide 20:05:23 Currently, the old admin guide is also mentioned in the tools box. 20:05:58 https://docs.fedoraproject.org/en-US/tools/ 20:06:25 that is the main complaint we have currently, we removed docs without anything to replace them 20:07:37 Yeah, for the installation guide we have replacements. We just have to fix the links. The issue is the admin guide. 20:07:55 alright, so +1/-1 to bring back the admin-guide in F37 space? 20:08:03 +1 for me 20:08:48 sorry, I have to step out early. Thanks for today. 20:09:00 +1 20:09:02 +1 20:09:07 no problem hankuoffroad[m], see you next time 20:09:22 I'll leave a note in discussion on my suggestion to merge some pages. 20:09:25 Hm, not a nice solution. But OK for the time being. 20:10:06 But we shouldn'Ät make it public anywhere else as in the tools box! 20:10:20 #agreed to bring back the admin-guide for F37 20:13:03 anything else on this topic? 20:13:44 not from me 20:14:17 last topic then: 20:14:19 #topic Open Floor 20:15:21 I can look into a replacement for inotify-tools on macOS. I saw some old discussions on StackOverflow about the same issue, but with no real fixes 20:15:51 That would be very helpfull! 20:16:14 I've a question about the tickets for the Quick Docs stuff. Where should I create 20:16:14 them? In GitLab? 20:16:21 I'm currently working on some improvements on the documentation website: https://discussion.fedoraproject.org/t/discussing-fedora-docs-website-improvement/36600/34 20:16:48 feel free to leave any feedbacks 20:17:10 I can also look at the merging topics ticket that hankuoffroad has open. 20:17:22 AnthonyMcGlone[m: the repository for quick docs is https://pagure.io/fedora-docs/quick-docs/issues 20:17:26 I think, we have a repository for quickdocs, haven't we? 20:17:45 (note that we should maybe consider moving that to gitlab at some point) 20:17:46 Okay, I'll add them there. 20:18:57 I see, is it really still pagure? 20:19:19 yep it's still in pagure 20:19:34 OK, nice 20:20:20 Who gets notified about new issues and new comments? 20:22:13 can't say, except that I'm not 20:22:51 We have a lot of open PRs und open issues. Who is in charge? 20:23:41 you can find the list of project members in the front page of the repository 20:24:32 basically, everyone in https://pagure.io/group/quick-docs-committers 20:26:21 Is a Pagure account separate from the Fedora account? 20:26:39 it's the same account 20:26:40 Would I need to sign up there as a separate thing? 20:26:59 AlanBowman[m] No, but you need additionl permissions to commit. 20:27:01 OK, thanks. 20:27:16 With your Fedora Account you can open issues 20:27:45 Does it use the standard fork, clone, push to origin, open a merge request workflow? 20:28:13 Yes. 20:28:43 And we need someone to takes care it all these issues and PRs. 20:29:04 From the list of committers I don't see, who would be that. 20:29:32 Probably ankursinha? 20:30:24 no idea :( I've never done anything related to quick docs 20:31:11 How could we proceed? 2 years old issues are quite bad. 20:31:52 time is up. Maybe you can ask on discussion? 20:32:09 The repo is owned by pbokoc and mainteined by flory7. 20:32:18 Yes, we should discuss it there. 20:32:42 Thanks everyone for today! See you all next week. 20:32:45 #endmeeting