19:31:24 #startmeeting docs 19:31:24 Meeting started Wed Feb 1 19:31:24 2023 UTC. 19:31:24 This meeting is logged and archived in a public location. 19:31:24 The chair is darknao. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:31:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:31:24 The meeting name has been set to 'docs' 19:31:32 #topic Roll call 19:31:34 #chair pboy darknao pbokoc py0xc3[m] 19:31:34 Current chairs: darknao pbokoc pboy py0xc3[m] 19:31:38 .hi 19:31:39 pboy: pboy 'Peter Boy' 19:31:40 .hi 19:31:42 darknao: darknao 'Francois Andrieu' 19:31:53 Hi 19:34:22 Hi there 19:34:29 hi pbokoc o/ 19:34:42 ok let's start :) 19:34:44 #topic Agenda 19:34:49 #link https://discussion.fedoraproject.org/t/docs-meeting-agenda-2023-02-01/46383 19:34:51 #info Announcements 19:34:53 #info Quick docs update 19:34:55 #info Open Floor 19:34:57 #topic Announcements 19:35:02 #info The category system for Quick Docs has been deployed on PROD 19:35:04 #link https://docs.stg.fedoraproject.org/en-US/quick-docs/categories/administration/ 19:35:06 #info Next milestone is F38 (2023-04-18) 19:35:08 #info We use GitLab to track work: https://gitlab.com/groups/fedora/docs/-/boards 19:35:35 nothing more to announce? 19:36:13 ok then, moving on 19:36:16 #topic Quick docs update 19:36:40 Anything to discuss regarding Quick docs today? 19:37:13 I'm on the road to regeneration from copious amounts of stress over the past few weeks, especially with our tax bureaucracy. 19:37:26 Yesterday was deadline. And now I am in the process of reading all the missed messages and joining the discussion and solutions. 19:37:34 So nothing new at the moment. 19:37:56 I'm still working on #522, reviewing the GRUB stuff. 19:38:17 From me, maybe a side note 19:38:38 We have a quandry of sorts. 19:38:49 We have lots of aricles in the works, but to complete that we would actually need a guide for quickdocs. 19:39:34 Well, and the work on QD guide is kind of blocks because all the articles in the work. 19:40:29 To get out of that, I would like to concentrate on the QD guide until next week. 19:40:34 pboy, what kind of a guide do you mean? How to write QuickDocs? 19:40:44 I mean, for contributors? 19:41:11 pbokoc yes. It includes categories to assign, tags, style guide for howtos, etc 19:41:48 Right. 19:42:11 #link https://pagure.io/fedora-docs/quick-docs/issue/518 19:43:45 ah so kind of a template to follow to write QD article, got it 19:44:29 Well, one of these will have to come first, if you want to focus on the guide first, I don't see why not 19:45:52 And additionally, we should have in mind the quality criteria compiled by our intern by Anushka Jain. 19:47:18 pboy: do you have a link to Anushka's post by any chance? 19:47:40 pbokoc yes, but the consequence is, I can not deal with any content questions for another week. i could the last 2 weeks because the reasons I mentioned above. And that was bad and causes already some frustration, unfortunately 19:48:24 darknao not at hand. It was April / Mai last year. I'll put in into the issue (I'm seeking for it myself. :-) ) 19:49:23 .hello hankuoffroad 19:49:24 hankuoffroad[m]: hankuoffroad 'None' 19:49:39 Hey hankuoffroad[m] :) 19:49:40 sorry im late, Hi all 19:49:57 Hi hankuoffroad[m] 19:50:21 pboy, QDs aren't tied to any specific release, so it's not like there's a deadline. I'm sure all the other stuff can wait another week. And if anyone complains, tell them it's an open project, they're welcome to contribute themselves :) 19:50:43 pbokoc: +1 19:51:10 +1 19:51:46 pbokoc Fortunately they do, especially hankuoffroad[m] and AnthonyMcGlone[m. But sometimes the need information from me. 19:53:02 And I'm very sorry if I can't do it because of the circumstances. 19:54:32 I wouldn't worry too much about it. This is a volunteer, community project, everyone should expect everyone else to have other things to attend to. 19:54:39 pboy: Not really for you to be sorry. All quality requirements make sense. I began to unserstand them slowly. 19:55:25 Thanks for all the understanding. 19:56:22 Just gut reaction about scope creep. I would need to break the tasks down and need some support. 19:58:16 moving on. let's continue the discussion 19:58:21 The mention of F38 brings to mind. 19:58:30 We have open tickets for this. What is the status there? Who is working on it? 19:58:45 Oh sorry, it's another topic. 20:00:54 I think we still have some time before F38 20:01:47 Yeah, 3 and a half months. I'll handle the usual branching and release notes (contributions welcome as always :) 20:02:04 but it's usually just creating f38 branches and start working on release notes.... I don't think there is anything to be done right now 20:02:13 Yeah, pretty much. 20:02:26 Okay, does anyone have anything else have anything on Quick Docs? If not we can move on to open floor I think :) 20:03:06 #topic Open Floor 20:03:43 So, I have two things. One's really tiny: Does anyone have merge permissions on this repo? https://pagure.io/fedora-docs/flatpak/pull-request/16 20:03:59 not me 20:04:12 nope 20:04:51 Ah well. (kalev, are you here by any chance? :) 20:05:06 I haven't tried. 20:05:59 Anyway, the other thing: repo migration. Now would be the perfect time to migrate repos to gitlab. Especially those that contain versioned docs (the Release Notes, Install Guide, the old Sysadmin Guide). 20:06:41 I think only the release notes one remain on pagure 20:06:52 the other two are already on gitlab 20:07:14 Ah, you're right 20:07:24 Okay, all the better then :) 20:08:05 Okay, so... anyone want to do it? It's going to be really painful because there's >100 open issues that'll need migrating too. 20:08:34 I really want to see the release notes repo on Gitlab but that would require some sync with bcotton as I believe he is the main user of that repo 20:08:57 Yeah, that too, but I think that's going to be the easiest part :) 20:09:05 and also there is a lot of issues that would require to be moved to gitlab, and I don't think we have a tool for that yet 20:09:38 Actually I can cut down the number of open issues a bit because some of them are outdated (i.e. for F35). But it's still going to be a lot. 20:09:39 and I'm not going to do that by hand :p 20:10:33 * nirik[m] notes someone had a proof of concept of one. 20:10:41 or we could just create the repo right now, and start logging issue on gitlab starting from F39 20:11:06 then discard old issue when F38 is out 20:11:40 nirik[m], Oh? Do you know who it was or where I could find more? 20:11:58 I can look, but in the middle of 3 things 20:12:07 nirik[m], no problem, I'll ping you later 20:12:51 darknao, Hmmm... I think that would end up being really complicated. A lot of the time, changes are originally approved for a release and then postponed to a later one. 20:13:17 It was an infra arc investigation... and it was akash... https://pagure.io/fedora-infra/arc/blob/20f97d44e2a092a1981cd15356be738121964a79/f/docs/pagure2gitlab/index.rst 20:13:20 So we'd end up with changes originally filed for F38 on Pagure suddenly needing to be moved to gitlab and tagged F39, while currently it's just a matter of changing the release tag. 20:13:35 nirik[m], thanks! 20:15:42 Anyway, it would be easier for everyone including Ben to just keep using pagure until we migrate everything. I think doing it sort of "partially" would just confuse everyone. 20:16:40 I can talk to Ben and ask him if it's something he'd be willing to deal with, but it would be extra work for him. 20:16:54 yeah ok make sense 20:17:56 Alright. That's all from me. 20:18:59 I have one to share if I may. 20:19:06 Go ahead! 20:19:17 I have a question about docs build script in local environment. 20:19:17 For MAC OS users, did the test with the docs build/preview script finish? Is it not done, and still necessary, 20:19:45 To my findings it doesn't work 20:19:48 I recall there are some writers who use mac for workflow and other reasons (dev) 20:19:56 I believe it still need testing/rewrite as pboy has some trouble with it 20:20:01 Even the old way 20:20:20 yeah, the -b / -p options don't work either 20:20:28 does it mean the script is not compatible? 20:20:59 Yeah, it's not compatible wir macOS 20:21:25 The issue with the -p option is the handling of Docker 20:21:41 did you install the dependencies? 20:21:53 It worked with the old ./preview.sh script, but not with the new -p option. 20:22:10 I installed Docker, yes 20:22:28 and the old script of our Server docu still works 20:23:00 if the previous script is working, then it should be just a copy/paste of code in the new script to make it work again 20:23:25 i see. I was going to try it in podman-docker with docker image (catalina) because I don't have mac. 20:23:42 may be there is a change how Fedora handles Docker resp. podman 20:23:55 pboy: alright then you can still work with old script and review PR, right? 20:24:00 I believe there is a special section just for mac (linux user don't use docker or podman for the preview) 20:25:03 hankuoffroad[m] I can work with our Server docu. Regarding QD, every pull provides the new version. 20:25:43 no prob. 20:25:54 Therefore I'm in the process to transfer everything to one of my Fedora servers and work remotely 20:29:34 that's all from me. 20:30:14 ok, we've reached the end of our time. Thank you everyone for today! 20:30:27 thanks 20:30:30 #endmeeting