19:30:50 #startmeeting docs 19:30:50 Meeting started Wed Feb 22 19:30:50 2023 UTC. 19:30:50 This meeting is logged and archived in a public location. 19:30:50 The chair is darknao. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:30:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:30:50 The meeting name has been set to 'docs' 19:30:58 #topic Roll call 19:31:01 #chair pboy darknao pbokoc py0xc3[m] 19:31:01 Current chairs: darknao pbokoc pboy py0xc3[m] 19:31:24 .hallo2 19:31:48 ,hi 19:31:51 .hi 19:31:52 pboy: pboy 'Peter Boy' 19:32:19 Sorry for the typos 19:32:20 .hi 19:32:21 darknao: darknao 'Francois Andrieu' 19:34:41 it's only the two of us today as it seems 19:34:52 alright let's start then 19:34:59 #topic Agenda 19:35:06 #link https://discussion.fedoraproject.org/t/docs-meeting-agenda-2023-02-22/47061 19:35:08 #info Announcements 19:35:11 #info Quick docs update 19:35:14 #info Open Floor 19:35:17 #topic Announcements 19:35:19 #info The category system for Quick Docs has been deployed on PROD 19:35:21 #link https://docs.fedoraproject.org/en-US/quick-docs/categories/administration/ 19:35:24 #info Next milestone is F38 (2023-04-18) 19:35:26 #info F38 Beta Freeze is in effect until beta release next month (target: 2023-03-14) 19:35:28 #info We use GitLab to track work: https://gitlab.com/groups/fedora/docs/-/boards 19:35:30 #info First draft of Quick Docs contributors guide is available! Thanks pboy :) 19:35:32 #link https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/contrib-quickdocs/ 19:35:55 do you have any announcements on your side? 19:36:08 no, not yet 19:36:30 hopefully next week regarding a draft for blog 19:36:46 note: F38 beta is next week, so it's pretty much the good time to start working on the release notes and do the branching on the docs that need it 19:36:54 next month* 19:37:28 #topic Quick docs update 19:37:43 anything to report regarding QD? 19:38:13 We should have a short look on the merge requests and the issues 19:38:28 And I have a question regarding the categories. 19:39:36 I don't see any PR or issue flagged for the meeting on QD repo. Is there any you want to talk about? 19:39:53 yes, e.g. 19:40:03 #link https://pagure.io/fedora-docs/quick-docs/pull-request/564 19:40:36 Could you have a short look. Can we merge it? 19:41:38 glb did the review, and it looks good to me too 19:41:45 so yes, I think we can merge it 19:41:56 OK. I'll do it afterwards. 19:42:17 What about 19:42:31 #link https://pagure.io/fedora-docs/quick-docs/pull-request/565 19:43:00 I think, it is a real improvement. 19:43:20 But I don't use Workstation 19:44:17 yep, I agree, +1 to merge 19:44:36 And the page is not specifically about workstation, but generell about all edtions. 19:45:27 Or we tag is as Workstation specific. 19:45:45 OK. I'll merge afterwards. 19:46:35 .hello hankuoffroad 19:46:36 hankuoffroad[m]: hankuoffroad 'None' 19:46:52 sorry for being late 19:47:06 Welcome hankuoffroad 19:47:19 reading the page, it does indicate it's specific to Workstation 19:48:18 so I guess it's ok to add the workstation tag/category 19:48:31 hi hankuoffroad 19:48:43 OK, I'll do the merge afterwards 19:48:55 I see I mentally confused this with the general Getting started page. 19:49:06 Another issue: 19:49:16 #link https://pagure.io/fedora-docs/quick-docs/issue/567 19:49:49 What can we do with that? 19:51:29 i have no idea, I didn't know this was a official fedora repository 19:51:39 (I don't think this is actually) 19:52:44 Who of us reviewed the article last time? There is a category added, so someone should have worked on it 19:52:51 but the repository is in a user namespace, belonging to https://accounts.fedoraproject.org/user/jwboyer/ 19:53:05 so maybe we can ask him in the ticket? 19:54:21 https://pagure.io/fedora-docs/quick-docs/c/83bfbba379913425efe48bf32b66bcfa07ecb953 19:54:30 this part is 4 years old 19:55:01 darknao Good idea to ask jwboyer. Sorry for the question, but can you do it? 19:55:32 I have no idea what an exploded git tree is 19:55:58 I neither. My last kernel experience is more a decade ago. 19:56:25 my recommendation would be to just remove that piece if it's not working anymore 19:57:04 I just see, if was me who is the last person working on it. :-) 19:57:25 OK. Let's just remove it. 19:57:40 I mean that part not working 19:58:27 ok, anything else? You had a question about categories? 19:58:35 darknao, can you do it? It's rather complicated for me at the moment to work on QD 19:58:55 I mean the removal 19:59:07 ok, give me 2 sec 19:59:23 I do gratefully. :-) 19:59:56 In the meantime I write my category question. 20:00:40 done 20:01:28 Is it possible, to include in the projected new QD start page listing the articles belonging to a category instead if the navigation tree also articles of the editions repository if they are taged accordingly? 20:02:03 So we would extend the QD listing to include other documentation as well. 20:03:05 And is such a extension usefull? 20:04:06 yes, it's possible to add such listing to the start page 20:04:21 and for now, only QD is included in the category systems 20:04:54 I'm not sure how difficult it would be to add others editions 20:05:25 that will definitely require to rewrite parts of the antora extension 20:06:35 Hm, that sounds quite laborious 20:06:43 yes it does :) 20:07:51 Then we should drop the idea. We have plenty to do as it is. 20:08:28 hankuoffroad[m] anything from your side? 20:09:45 At the moment, converting QD category could be a priority gradually. 20:10:27 I mean when writers take on editing any QD articles they need to be reminded of updating category tag and template 20:10:49 Yes, indeed! 20:11:46 Maybe we should also do a quick pass through all the articles and just add categories, without an elaborate review. The latter would then be a second step. 20:12:28 yes 20:14:13 Maybe I should make a try next week. That would be a good opportunity to complete the QD Guide category system. 20:16:16 If we are finished with QD, I would like to discuss about some issues in gitlab repo. 20:16:31 ok let's move to open floor then 20:16:39 #topic Open Floor 20:17:23 Well, I don't know what to do with: 20:17:34 #link https://gitlab.com/fedora/docs/docs-website/pages/-/merge_requests/5 20:17:59 let me see 20:18:24 so I don't know this specific user, and I don't see any commit belonging to him 20:18:32 It is or was a kind of confidential request. 20:18:37 no comment, no description 20:18:52 i'd say, close it 20:20:11 Well, in includes some useful type corrections. And some items I don't know about. 20:20:19 if I look closely, it's just a PR to merge the main branch on staging. We don't do that 20:20:32 if there is a need, I'll rebase the stg branch manually 20:21:09 Well, I will pick those which are usfull and understandable, and ignore the other. 20:21:18 And comment, that stg is no longer used. 20:21:41 true. it is hard to review 20:22:08 I have a suggestion - 20:22:21 if we can move to next topic 20:22:25 those commits are all in the main branch already 20:23:05 darknao, can you close the merge with a kind comment? 20:23:08 yes hankuoffroad[m] go ahead 20:23:21 what is priority for contributor guide? I was bit sidetracked to casual contributor guide and test the Web IDE features. 20:24:18 I think it is very good if you optimize the WEB ide related guides. 20:24:39 And I would try to add categories and tags to the QD guide. 20:25:41 Or did I missunderstand something? 20:26:11 no that's clear for me. 20:26:34 ok. after a few mistakes made with MR conflict in Pagure and GitLab, I've managed to resolve MR conflict in GitLab, so I can continue editing it in batch 20:26:55 +1 20:27:11 Cool 20:27:50 Mostly I focus on style and brevity of setence for users to follow through one by one 20:28:16 setence = sentence = paragraph, typo 20:29:04 Yes, I think such optimization would be very valuable and helpful. 20:29:40 no problem. will do 20:29:46 Web Ide could become the main tool, especially for occasional contributors. 20:29:57 And we need those urgently! 20:30:21 yep 20:30:26 ok folks, time's up, thanks for joining today! 20:30:36 thanks 20:30:40 #endmeeting