18:30:46 #startmeeting docs 18:30:46 Meeting started Wed Jul 19 18:30:46 2023 UTC. 18:30:46 This meeting is logged and archived in a public location. 18:30:46 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:30:46 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:30:46 The meeting name has been set to 'docs' 18:30:55 #topic Roll call 18:31:10 Welcome everyone 18:31:23 Let's wait some minutes for everyone to show up. 18:34:57 .hello hankuoffroad 18:34:58 hankuoffroad[m]: hankuoffroad 'Hank Lee' 18:35:48 Hi hankuoffroad[m] today I wasn't too impatient. :-) 18:36:03 firtunaely 18:36:08 fortunately 18:36:17 me and the typos 18:37:00 pboy: no problem. I came back home early today. 18:37:25 Luckely. 18:37:32 I think we start now. 18:37:38 sure 18:37:43 #topic Agenda 18:37:54 #info Action item followup & Announcements 18:38:09 #info Tickets review: there is no ticket flagged for the meeting on GitLab. 18:38:26 #info There are two tickets flagged for “next meeting” on Quick Docs. 18:38:40 #info Quick Docs Improvement: Nominate Quick Docs articles for urgent review 18:38:50 #info Role-based call to action: banner on Quick Docs home page 18:38:58 #info Open floor 18:39:09 #topic 1. Action item followup & Announcements 18:39:27 #action still to remove outdated installation guide 18:39:41 Nothing to announce from me at the moment 18:40:30 Anything to add here? 18:40:40 no, let's carry on 18:40:57 #topic 2. Tickets review gitlab 18:41:07 there is no ticket flagged for the meeting on GitLab. 18:41:17 Not direkt a ticket, but there is a first cut for automated release notes. 18:41:28 which maybe a future issue on gitlab 18:41:45 Unfortunately, I didn't manage to have a look at it until now. Anyone did? 18:42:28 pboy: No, 18:42:30 Obviously not. 18:42:41 topic 3. Tickets review on Quick Docs 18:42:51 First one: 18:43:00 #link https://pagure.io/fedora-docs/quick-docs/issue/528 18:43:11 let us read some minutes 18:47:45 Well, first about partials. Is the article composed of partials? If yes, we should re-integrate the partials. They make editing so much harder. 18:48:39 there are partials in the middle. 18:49:44 Well, we should reintegrate them. What do you think? 18:50:36 Unless they are really reused. A grep could reveal that information 18:50:55 pboy: Could you explain what reintegration means? You mean inserting paragraphs, instead of partials? 18:51:38 I mean to copy the content of the partial into the intended place and then delete the partial. 18:52:04 The original intention of the partials didn't make into reality. 18:52:40 pboy: Understand. 18:52:53 (The intention was to cooperate between Fedora, RHEL, and CentOS. But, as Ben told us, it never worked out.) 18:53:13 perhaps not never, but in the end it didn't. 18:54:36 Well, i think we agree about it? 18:54:41 well, I'm not sure what I could do. The last thing I want is to copy and paste...after all, I lose context on what content needs to be rewritten. 18:55:43 Well, I alöready 18:56:11 I already did that, ever when I edit a QD file. 18:56:39 But I can't do anything until after Flock. 18:57:14 ok then, back to the main point - my suggestions to procedure/steps rewritten and a question on why we need other OSes on the guide? 18:57:49 I you review and update an article, loosing the context seems not such a problem, in my experiences. 18:58:26 if possible, we can revisit individual tickets and share opnions on DIscussion. Weekly meeting is not rnough to review all tickets and other topics. 18:58:31 Well, I think we want to guide a Windows user to check Fedora, even on a SBC 18:59:56 hankuoffroad[m]> yes, but I think, now we should speak about it. And the decision to re-integrate the partials is not just about this article, I think. 19:00:53 The Windows part is practically an attempt at "seduction" :-) 19:01:30 could we share an update on Pagure ticket? I feel overwhelmed if everything is discussed on meeting. 19:01:40 And I think, this is a general question: Will we enable Windows users to use Fedora as well. 19:02:09 Yes we can. I'll start with a comment about the three topics. 19:02:51 we lose focus on the quality and accuracy of Fedora linux installation process, while we try to be friends of other OSes. 19:03:00 agreed 19:03:35 OK, I can comment about the installer issue as well and we can discuss that off-meeting. 19:03:49 next one is too big to read todaay 19:03:56 OK. 19:04:05 can you share your feedback on the ticket? 19:04:19 Yes, I will 19:04:56 #topic 5. Role-based call to action: banner on Quick Docs home page 19:05:26 ah 'Nominate Quick Docs articles for urgent review' is for Flock? 19:06:04 I wish we spare more time offline to go through Quick Docs tickets..some of them are unattended for months. 19:06:32 Yes. I hoped, we would have a summary of the events in advance. So everyone, who plans to attend, could nominate an aricle. 19:07:04 It's part of my event description. But there is no publication of the propsals. 19:07:05 to be perfectly honest with you, if feedback is not received for PR/reasoned comments, I'm getting skeptical for more adventurous tasks. 19:07:12 At least not until recently 19:07:54 You are right, it is an attempt. 19:08:25 If someone is planning to attend the session, they have the option. 19:08:37 ok let's move on 19:09:08 We are now at topic 5, CTA 19:10:02 My question is the 2 lines don't stand out enough. 19:10:19 I think, we need 'more design'. :-) 19:10:20 banner wasn't possible, so the text is placed. 19:11:21 I don't know about mechanics of CSS/Antora. I saw your comment on it. Maybe we can wait for a reply 19:11:27 A box or banner below the table of contents is feasible. 19:11:43 pboy: that was a compromise 19:12:38 An understanding among different positions. 19:12:58 A little bit from everything, so to speak 19:13:52 well if banner is technically not possible (hold the thoughts), that's it. 19:14:57 I think, it is technically possible, but is maybe too much work for the current contributors. 19:16:11 It's no problem to write a bit of CSS just for the Docs pages with picks up your 2 lines and turns them in a banner, dynamically placed beyond the table of contents. 19:16:32 And do leave them off, if the table is longer as the text. 19:16:35 pboy: we could be patient in this case. it is summer and slow season. Time to take a break :) 19:18:25 Yeah, of course. When i worked on the new homepage, i produced some CSS that was only applied to the Docs pages. But in he end we didn't use it, because I could polish it before release date. 19:18:41 Just to demonstrate, it is possible. 19:19:14 Well, I think we are at the end? 19:19:30 And we continue on discussion an in the tickets? 19:19:50 yes, all the rest is actively discussed offline. 19:20:01 pboy: which one? 19:20:18 What do you mean with which? 19:20:53 ah got it now. agreed. 19:21:13 OK. So I close now? 19:21:48 no problem. 19:21:52 OK 19:21:57 #endmeeting