18:30:12 #startmeeting docs 18:30:12 Meeting started Wed Jul 6 18:30:12 2022 UTC. 18:30:12 This meeting is logged and archived in a public location. 18:30:12 The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:30:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:30:12 The meeting name has been set to 'docs' 18:30:32 #topic Roll call 18:30:39 .hi 18:30:43 pboy: pboy 'Peter Boy' 18:30:45 #chair pboy darknao 18:30:45 Current chairs: bcotton darknao pboy 18:31:17 .hello hankuoffroad 18:31:18 hankuoffroad[m]: hankuoffroad 'None' 18:31:23 .hello py0xc3 18:31:23 py0xc3[m]: py0xc3 'Christopher Klooz' 18:31:50 .hello mateusrodcosta 18:31:51 mateusrc: mateusrodcosta 'Mateus Rodrigues Costa' 18:33:07 .hi 18:33:08 darknao: darknao 'Francois Andrieu' 18:33:35 I suggest to postpone the survey issues until Anushka has recovered? 18:33:51 No prob. 18:34:24 okay, let's get started 18:34:40 #topic Agenda 18:34:44 #info Announcements 18:34:49 #info Review action items 18:35:11 .... so i've been away for the better part of a few weeks, what else should be on today's agenda? 18:35:33 The old Docs are one 18:36:15 e had some discussion about front page design and have to made some decisions 18:36:18 On one hand, getting rid of the old. On the other hand, where to provide the PDFs 18:36:24 I believe there was going to be some discussion on whether to move the old docs and start from there or do from scratch 18:37:07 We have a suggestion: Keep it until I made an archive and then remove it from online site. 18:37:20 any other topics? 18:37:36 So we have docu where to find what and we have a repo for the pdfs 18:37:59 #topic Announcements 18:38:09 #help Some release notes still need written: https://discussion.fedoraproject.org/t/how-to-write-fedora-release-notes/38311 18:38:14 #info We're using the docs-fp-o repo to track meta-work 18:38:14 #link https://pagure.io/fedora-docs/docs-fp-o/issues 18:38:21 ^ should this be updated to GitLab now? 18:39:17 pboy: Sounds good! 18:39:26 (or is this a better Discussion thread?) 18:39:55 May be a good idea to start new issues on Gitlab and to work off the old ones in pagure. 18:40:09 So we have both for some time 18:40:46 pboy: +1 18:41:06 In general we should discuss first on discussion and then finally decide here. 18:41:15 I think 18:41:17 Although long term issues might be transferred from pagure to gitlab? In order to soon consolidate organization at one of them. 18:41:27 yeah, let's move this to discussion 18:41:31 #topic Previous action items 18:41:42 #info pbokoc to finally add a relnotes guide to the contributor docs 18:41:45 not done, afaik 18:41:57 #action pbokoc to finally add a relnotes guide to the contributor docs 18:42:02 #info bcotton to draft Docs Team Charter 18:42:30 definitely not done. I do have some time on an airplane (!!!) next week, which will be a good time to work on this 18:42:31 #action bcotton to draft Docs Team Charter 18:42:35 #info darknao to configure remaining repos in GitLib for CI 18:43:11 ^ not done yet 18:43:22 #action darknao to configure remaining repos in GitLib for CI 18:43:41 #topic Old docs 18:44:35 I made a suggestion of discussion about that. 18:45:14 I'll create an archiv page with documentaton where to find what. 18:45:32 And I check the completeness of the coresponding repos. 18:45:53 excellent. is there anything to discuss about it now, then? 18:45:56 pboy: Do you need support? 18:45:59 With all done, we remove old docs from site completely. 18:46:17 py0xc3 would be helpful! 18:46:44 May i ask you, when I'm working on that? 18:46:57 Yes. Let me know when/where to help! 18:48:02 thanks, unfortunately I got swamped with huge problems with our server farm. But I'm recovering. 18:48:24 #action pboy and py0xc3 to create an archive page for old docs 18:48:59 anything else on this topic? 18:50:28 i guess not! 18:50:35 #topic Docs front page design 18:52:12 There is a fundamental decision to be made here. 18:52:21 Do we want to have both areas, community and user doc, on the start width or split from 2 sides. 18:52:39 We had a thread on discussion about that. 18:52:54 https://discussion.fedoraproject.org/t/fedora-docs-design-work/40062/18 18:56:00 i like the idea of having them both on the same page, but clearly distinguished 18:56:27 Me too. 18:56:34 the main motivation being that a curious user might start looking at contributor docs and end up being a contributor 18:56:58 but i'm also fine if we go with separate pages, so long as we make a decision and act on it :-) 18:57:57 It is important to keep it comprehensible for less-experienced users. So that should be considered; many users are not aware of the difference to "community". Fedora is "only an OS" for several 18:58:40 I would prefer to have it on one page to make it clear, docsdoes not fall from the sky. We have to organize cooperative work. 18:58:52 And that is the community part. 18:59:19 py0xc3[m] Yes, therefor we need a good design! 18:59:39 And a better text for some topics. 19:00:21 We should wait with an intensive discussion until Anuschka is healthy again. And we should invite Allan Day. But maybe we have an opinion? 19:00:34 pboy: Absolutely. "user" and "community" needs to be comprehensible distinguished from each other; but if that is considered, I have no preference. 19:01:40 pboy: +1 & +1 19:01:51 Do you mean Community doc to be wiki? 19:02:08 No! Everything to docs 19:02:21 I mean to Antorra. 19:02:37 Wiki just for special cases, e.g. Change Proposal. 19:03:55 pboy: oki 19:05:19 so it sounds like there's a general consensus that we'd prefer a single page? 19:05:28 +1 19:07:10 #agreed We'd prefer a single front page for user and contributor docs 19:07:11 anything else on this topic? 19:08:50 One comment, might make sense to focus the term "contributor" Docs when distinguishing from user docs, that's more obvious to everybody 19:09:19 So avoiding the term "community" as separation to "user" docs 19:09:31 What about project doc? 19:10:08 Already needs the user to know that this refers to Fedora, which is a project and not just an OS :) 19:10:18 It's not about contributor alone. But also about procedures, organisation, ressources, .... 19:10:31 those are also docs for contibutors 19:10:35 pboy: Yeah, you are right about that 19:11:24 Ok, yeah, for users vs. for contributors. 19:12:24 Anyway, we need a smart design for that. 19:13:36 pboy: Maybe put into the discussion to collect ideas about it? 19:14:01 Yes, indeed. 19:15:37 anything else? 19:16:27 #topic Open floor 19:17:00 stop me if you've heard this before, but i probably won't be available for next week's meeting. i have a meeting in Raleigh 19:17:36 No problem, I think. 19:18:20 Who takes the initiative? Shaun? darknao? 19:18:20 Yeah, sorry but I didnĀ“t look into either the style guide or writing the DNF guide in the last two weeks, sorry 19:18:49 mateusrc: I was busy with personal stuff + work, but I should be able to do those this week 19:18:52 mateusrc welcome to the club. :-). me too. 19:19:47 But I have a proposal for the new team page and contrib pages nearly ready, now. 19:20:07 Can hopefully finish it tomorrow until evening. 19:20:26 And also, apprantly a lot of disscussion about Docs happens on... Discussion. 19:20:26 And I usually forget to look there, I will start keeping a close look there as well as putting a reminder to meeting on calendar 19:21:21 Btw, there is one person right now on another Fedora channels asking if there's an epub version of docs, is there? 19:21:47 It's a bit tricky, but you can config notification, so you get an email in case of new posts. 19:22:29 We don't have a ebook version of user docs. 19:22:35 mateusrc: I think not, only existing PDFs could be converted. Btw, do we also have automatic creation of PDFs of the current Docs? 19:22:56 we don't have automatic pdfs anymore 19:23:11 (and i think that doesn't make sense for a lot of our content compared to 5+ years ago) 19:23:25 Agreed :) 19:24:43 Pointed them to Dcos channel 19:24:50 s/Dcos/Docs/ 19:26:08 anything else for this week? 19:28:04 okay, thanks everyone! 19:28:08 #endmeeting