19:31:00 #startmeeting docs 19:31:00 Meeting started Wed Dec 28 19:31:00 2022 UTC. 19:31:00 This meeting is logged and archived in a public location. 19:31:00 The chair is darknao. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:31:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:31:00 The meeting name has been set to 'docs' 19:31:07 #topic Roll call 19:31:13 #chair pboy darknao pbokoc py0xc3[m] 19:31:13 Current chairs: darknao pbokoc pboy py0xc3[m] 19:31:20 .hi 19:31:22 pboy: Something blew up, please try again 19:31:25 pboy: An error has occurred and has been logged. Please contact this bot's administrator for more information. 19:31:28 hi o/ 19:31:44 .hello pboy 19:31:45 pboy: Something blew up, please try again 19:31:48 pboy: An error has occurred and has been logged. Please contact this bot's administrator for more information. 19:31:58 hm, no luck today 19:32:17 zodbot is on holiday :p 19:32:26 nice 19:33:45 so I'm not sure there will be many people today 19:33:46 .hello hankuoffroad 19:33:47 hankuoffroad[m]: Something blew up, please try again 19:33:50 hankuoffroad[m]: An error has occurred and has been logged. Please contact this bot's administrator for more information. 19:33:57 hi 19:34:05 hey hankuoffroad[m] 19:34:58 ok let's get started 19:35:08 #topic Agenda 19:35:10 #link https://discussion.fedoraproject.org/t/docs-meeting-agenda-2022-12-28/45240 19:35:12 #info Announcements 19:35:14 #info Quick docs update 19:35:16 #info Open Floor 19:35:18 #topic Announcements 19:35:24 #info Old Fedora docs (anything older than F26) have been retired. 19:35:26 #info Beta version of the category system for Quick Docs has been deployed on stg 19:35:28 #link https://docs.stg.fedoraproject.org/en-US/quick-docs/categories/administration/ 19:35:30 #info Next milestone is F38 (2023-04-18) 19:35:32 #info We use GitLab to track work: https://gitlab.com/groups/fedora/docs/-/boards 19:35:48 anything else to announce? 19:37:06 nope 19:37:08 alright, next topic then 19:37:10 #topic Quick docs update 19:37:21 Well, that's me 19:37:27 floor is yours 19:37:41 Unfortunately, discussion is down just now. 19:37:51 I wanted to discuss 2 threads . 19:38:03 But we can discuss some issues, first. 19:38:13 Write a better "installing software from source" quick-doc 19:38:24 https://pagure.io/fedora-docs/quick-docs/issue/120 19:38:32 What about my proposal (last comment) 19:38:57 SORRY 19:39:02 https://pagure.io/fedora-docs/quick-docs/issue/111 19:40:38 is there a PR waiting for this? 19:40:55 No, just the issue. 19:41:06 I would do the editing. 19:42:03 you are going to reuse ramin's work right? 19:42:31 yes, as it is with just some formal adjustmends. 19:42:46 ok, seems fine to me 19:42:53 And I would take him as the author. 19:43:28 hankuoffroad[m] What about you? 19:44:08 I presume those who need to install sotware from source are advanced users. It's beyond my toolbelt 19:45:16 I'll take a look at it and comment 19:45:25 Yeah, what do you think about the proposal, to take and publish it as is (with just formal adjustments) 19:45:57 And to add a editor's note. 19:47:37 pboy: I haven't looked at the commits by @ramin 19:48:05 Ok, so what to do? 19:48:23 Postpone to next meeting? 19:49:16 pboy: I think i'm not ready to comment on the docs for advanced users. Don't hold it for me. 19:50:14 Ok, but you don't object to pick up the work and publish it? 19:50:31 note that I didn't read it completly either, but the content seems to be a good base if someone advanced enough want to work on it in the future 19:50:55 +1 19:51:11 pboy: I have no objection to it as the content was reviewed by several authors. 19:51:23 Ok, so 19:51:31 at least, it has way more chance to be improved if published as is, as if we leave it in ramin's fork and forget about it 19:51:53 so +1 for me 19:51:55 #agreed We publish the work or ramin issue #111 19:52:11 Next issue: 19:52:21 133: Adding (Debugging) info to Navigation tool 19:52:28 https://pagure.io/fedora-docs/quick-docs/issue/133 19:52:35 Proposal: Close a stale. 19:52:43 as stale 19:53:57 I guess the idea was to move wiki articles to Docs? 19:54:18 I think so, yes. 19:54:43 Many wiki articles had been transferred. These ones are obviously left. 19:55:29 Alternativly, we can transferr them and add the proviso, some other articles still have. 19:55:37 maybe we can keep it open if someone want to work on moving those pages? 19:57:05 most of them are quite old so no sure how accurate they are right now 19:57:07 May be, then is would be better to transfer them and add a disclaimer as in 19:57:15 #link https://docs.fedoraproject.org/en-US/quick-docs/kernel/build-custom-kernel/ 19:57:36 Yes, the problem is, they are old, indeed. 19:58:37 I'm afraid just leaving the ticket open won't bring any change for the next 2 years either. 20:01:36 troubleshooting guides require quite extensive knowledge on the topic, so moving the wiki articles to docs is easy, but reviewing or fixing them, not so much 20:02:41 Yes, it we transfer them, someone may read and do a review, hopefully. 20:03:38 if we just leave the ticket open, nobody will find them and we better close it, I think. 20:03:43 the stacktraces one has been modified in 2021, so it's not that old, and the content still seems relevant 20:04:15 Good, I think then we should transfer it (I'm willing to do itI. 20:04:43 +1 20:05:18 Question with the others is, are we making fools of ourselves? 20:05:23 +1 20:06:12 I think it'll get more visibility than on the wiki and maybe someone will get interested in reviewing it 20:06:47 I also think we should only move the ones that are still relevant and not too old 20:06:59 for instance, I would drop the xorg one 20:07:14 same for Alsa 20:07:22 pboy: I don't think so. It is content reuse. All we need is subject matter expert for cusom kernel. 20:09:16 all the others seem like valuable information to me 20:09:46 darknao: Sure 20:10:06 OK, new proposal, we start to transfer, but w/o xorg, Alsa 20:11:13 +1 20:11:29 #agreed issue #133: We start to transfer with wiki disclaimer w/o xorg and alsa 20:11:44 Next one. 20:11:53 #153 Request: using a Yubikey on Fedora 20:12:01 https://pagure.io/fedora-docs/quick-docs/issue/153 20:12:10 For 2 yeas noone worked on it. Not one line of text sofar. 20:12:20 Proposal: close stale 20:15:06 I think we should keep that one open 20:15:09 +1. until someone revives the topic. 20:15:47 a page on how-to use yubikey with Fedora is very valuable, even if no one want to work on it at this time 20:16:28 My concern is, just leaving it open will not lead to anything. 20:16:39 closing it either :) 20:17:03 Indeed, yes. :-) But OK, let's check it in 6 months again. 20:17:45 also there is a wiki page here 20:17:46 Well, I wanted to discuss 2 threads indiscussion. But it is not back again. 20:17:55 that has been modified very recently 20:18:10 Can you post a URL? 20:18:15 so maybe we can just move it to Docs and see if that helps? 20:18:20 https://fedoraproject.org/wiki/Using_Yubikeys_with_Fedora 20:18:28 (it's in the issue) 20:19:11 Oh, I overlooked that. Yes, I think we should transfer it. 20:20:17 #agreed Regarding issue 153 we will transfer the wiki page at https://fedoraproject.org/wiki/Using_Yubikeys_with_Fedora 20:21:19 That's it from me. My other topics need discussion which is still offline. 20:21:54 ok, open floor then 20:22:02 #topic Open Floor 20:22:52 I have a question on meeting time 20:23:28 hankuoffroad[m]: sure, go ahead 20:24:14 We have new contributors working on different time zone. 20:24:46 Can we take a vote for alternative meeting time? 20:24:54 I'm fine with that 20:25:17 me too 20:25:22 The Fedora chat has been motivating me for more collaboration. 20:25:44 can you create a topic on Discourse with multiple time slot to choose? or a WhenIsGood (even better)? 20:25:58 Sure, I'll do that 20:26:16 thanks 20:26:17 I think WhenIsGood is better. :-) 20:26:27 more systematic 20:26:50 Should I copy the link to Discussion? 20:27:06 yes! 20:27:07 yep so everyone interrested can vote 20:27:21 You should open a thread about it nevertheless. 20:27:46 That works for me. Will check in later and open the thread 20:28:47 You should wait until next year, when everyone is back, I think. 20:29:04 it means: end of next week. 20:29:18 Yeah fair enough, forgot 20:30:00 we can keep it open for 2-3 weeks to make sure everyone has time to vote 20:30:34 alright, time is up 20:30:47 Yes, but the thread should not be done now, when it is forgotten, when everyone is back. 20:31:08 thanks everyone, and see you all next year! 20:31:14 +1 pboy 20:31:27 +1 20:31:44 #endmeeting