18:30:09 #startmeeting docs 18:30:09 Meeting started Wed May 31 18:30:09 2023 UTC. 18:30:09 This meeting is logged and archived in a public location. 18:30:09 The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:30:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:30:09 The meeting name has been set to 'docs' 18:30:20 #topic Roll call 18:30:28 Welcome everyone 18:30:33 .hello hankuoffroad 18:30:34 hankuoffroad[m]: hankuoffroad 'Hank Lee' 18:30:41 Let's wait some minutes for everyone to show up. 18:31:43 Welcome Hank. Let's wait some minutes. Maybe, someone else joins. 18:32:13 yep 18:34:43 OK. Hope dies last. 18:34:43 Let’s proceed. 18:34:54 #topic Agenda 18:35:08 #info Action item followup & Announcements 18:35:20 #info Discussion and decision of Docs team work plan F39/F40 period 18:35:31 #info Open floor 18:35:54 #topic 1. Action item followup & Announcements 18:36:11 I think, no follow up at the moment, so far as I know. 18:36:26 Annything to add or to announce? 18:36:48 no, you can move to the topic 18:36:58 #info Currently, there is no open follow up or to announce. 18:37:11 topic 2. Discussion and decision of Docs team work plan F39/F40 period 18:37:23 #link https://discussion.fedoraproject.org/t/possible-docs-team-work-plan-for-the-f39-f40-period/81122/33 18:37:46 Until now, there seems to be no disagreement. 18:38:41 If anyone objects of if there are any doubts, let's discuss now. 18:39:36 Server, CoreOS, IoT, SilverBlue, and Quick Docs - what do we need for the rest of working group? 18:39:54 Quick Docs is clear to me. 18:40:42 I think, they use primarily local authoring environment. That works for all of them. 18:41:31 And we need Web UI for pagure. None of those is using GitLab repo, as far as I know. 18:42:09 correct, none of docs of working group (editions) use GitLab. 18:42:39 So, we can focus in those 2 and postpone GitLab WEB UI until there is a final version. 18:43:05 i understand the item 1. 18:44:10 can we move on to 2? 18:44:35 Yes, item 2 of the 5 items proposal. 18:45:12 My question is, will you take the lead? 18:45:22 yes 18:45:42 hankuoffroad[m] ++1 18:46:07 put me in. Regarding CTA location and practicalities, I added some comments. 18:46:50 Yes, I agree. My compilation were only keywords and examples. 18:47:33 Anybody else around here with concerns or comments? 18:48:14 Well, I see none, therefore: 18:48:47 #agreed hankuoffroad[m] takes the lead of item 2 of the 5 item proposal. 18:49:09 And as a postscript: 18:49:43 #agreed We agree to item 1 of the 5 item proposal 18:50:31 ok, next? 18:50:37 Well, lets proceed with item 3 of the 5 item proposal 18:50:49 Any concerns here? 18:51:31 3 Quick Docs - could you help me understand bit better about each task? 18:52:49 As a 1st step I would like to add to every article a category and some tags, and to get rid of the navigation bar. So, everything get's a new look&feel. 18:52:58 1) conversion of all contributions to the category system: is there automatic conversion by Antora? 2) elimination of the navigation column - is there agreement made? 3) introduction of the new header data - replacing navigation column?? 4) elimination of the partials - why? 18:53:07 In a 2nd step I w 18:53:25 pboy: navigation bar on the left? 18:53:25 In a 2nd step I qwould update the content. 18:53:41 yes, navigation var on the left. 18:54:11 I'm not aware of any automation. So it is a one go manual editing. 18:54:13 pboy: oh was there discussion that happened before I became a regular? 18:54:51 I think so. It was a discussion initiated by Allan Day. 18:54:58 The long term goal: 18:55:05 pboy: oh, did you check with Antora specialsts? 18:55:22 s/specialsts/specialists/ 18:55:32 Away from the traditional handbook like documentation to short, independent articles. 18:55:59 pboy: does it affect all other working groups like CoreOS docs and so on? 18:56:10 hankuoffroad[m] No, I didn't, besides a discussion with darknao. 18:56:24 An do, it's just about QUick Docs. 18:56:37 s/An no/And no/ 18:56:51 pboy: that'll do. no objection from me 18:57:07 Ok then: 18:57:38 partials - there are many...are you getting rid of all of them? 18:57:51 #agreed We agree about item 3 of the 5 item proposal. pboy will take the lead. 18:58:29 Now, coming to item 4 of the 5 item proposal (link at the beginning of this topic) 18:59:20 pboy: wait - about partials, I need your answer 18:59:38 Sorry, what was it about partials? 18:59:49 are you getting rid of all of them? 18:59:57 over 100 partials 19:00:42 Well, just Quick Docs, I'll reintegrate it into the main text, making it much easier for new contributors. I now, it's a lot. 19:01:09 May be it is a step 1a, after we have everything on categories. 19:01:12 ah that's fine now. Yes partials are a pain for me 19:01:24 i can't touch them at all. 19:01:40 pboy: +1 19:02:27 It's a boring effort, something for the late evening when you are too exhausted for anything else 19:03:04 OK, back to item 4 19:03:15 I think, we agree, too? 19:04:01 OK, no ob jections. 19:04:11 agreed We agree about item 4 of the 5 item proposal. pboy will take the lead. 19:04:16 pboy: yes 19:04:22 #agreed We agree about item 4 of the 5 item proposal. pboy will take the lead. 19:04:48 Well, last one: item 5 of the 5 item proposal 19:05:17 what is the change you are suggesting for release note? 19:05:32 I think, we have no other choice. But we should explicitely decide and inform the community 19:05:51 i vaguely remember you're looking to automate publishing of release note 19:06:25 hankuoffroad[m]. Yes, bat I was just the messenger. We discussed it that time and darknao wanted to do the technical side. 19:07:04 ok if my memory serves right, it is technically possible, but darknao needs to write script. correct? 19:07:09 and yes: the proposal is to automate the gneration of release note by extracting relevant text from the Change proposal 19:07:38 that's really a step forward. 19:08:01 Yes, we need some one with good skills in scripting and wiki technologies 19:08:10 it is worth waiting for, but you could influence dev resources at Flock to prioritize for F39/F40 or F100? 19:08:48 A good idea to bring it to flock! 19:09:09 Maybe we get ti for 41/42 19:09:14 i guess you're going to Ireland - holiday and Flock to represent Docs? 19:09:29 Yes, my wife an me will do so 19:09:50 Representing Docs and Server 19:10:07 wow that's family business. That's me only in my family with FOSS blood 19:10:24 pboy: i do admire both 19:10:49 Yeah, I'm a lucky guy. :-) 19:11:13 sure you are. 19:11:40 Well, I think we are agree, so for the protocol: 19:12:10 #agreed We agree about item 5 of the 5 item proposal. 19:12:12 Alles klar 19:12:22 +1. :-) 19:12:46 'I think we can proceed with next topic. 19:13:05 #topic 3. Open floor 19:13:26 a burning question 19:13:30 Regarding release party: I'm nearly done 19:13:45 done with the itemihzing and the template. 19:14:08 Sorry, we had some server breakdown here and I had to do crisis intervention. 19:14:28 cool, thanks. Because it is my first public appearance representing Docs group, so nervous. 19:14:37 pboy: at work? 19:15:09 I'll send you the form about one or two hour or so after closing out meeting 19:15:19 super 19:16:33 Yes, at work. I'm leader of the IT department of several fresearch institutes (as a side job besides doing research), and we are in the middle of a funding process. Everyone is very nerveous 19:17:05 pboy: that's huge commitment and tricky balance to make. 19:17:11 But is done now, everything works again since some hours. 19:18:12 Yes, it is. Scientist are a funny and impatient community. I know, I'm one myself. :-) 19:18:36 i know it from my son 19:19:34 pboy: actually impatience goes with passion, too 19:19:45 Yes, if you don't know it from the inside, it's hard to grab that athmosphere 19:20:10 Well everyone with everything else here? 19:21:22 None, so I'll close the meeting. 19:21:37 Thanks to every lurker. :-) 19:21:42 great. 19:21:53 #endmeeting