18:32:43 <darknao> #startmeeting docs
18:32:43 <zodbot> Meeting started Wed Sep 14 18:32:43 2022 UTC.
18:32:43 <zodbot> This meeting is logged and archived in a public location.
18:32:43 <zodbot> The chair is darknao. Information about MeetBot at
18:32:43 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:32:43 <zodbot> The meeting name has been set to 'docs'
18:32:53 <darknao> #topic Roll call
18:33:04 <pboy> .hi
18:33:05 <zodbot> pboy: pboy 'Peter Boy' <>
18:33:12 <darknao> #chair pboy darknao pbokoc
18:33:12 <zodbot> Current chairs: darknao pbokoc pboy
18:33:53 <py0xc3[m]> .hello py0xc3
18:33:54 <zodbot> py0xc3[m]: py0xc3 'Christopher Klooz' <>
18:34:08 <pbokoc> Hello
18:34:19 <darknao> #chair pboy darknao pbokoc py0xc3[m]
18:34:19 <zodbot> Current chairs: darknao pbokoc pboy py0xc3[m]
18:34:26 <darknao> hey pbokoc :)
18:36:19 <darknao> ok let's go
18:36:22 <darknao> #topic Announcements
18:36:28 <darknao> #info Some F36 release notes still need to be written
18:36:30 <darknao> #info F37 Beta has been released!
18:36:32 <darknao> #info We use GitLab to track work:
18:36:42 <darknao> Anything else to add?
18:37:53 <darknao> ok moving on
18:37:56 <darknao> #topic Previous action items
18:38:01 <darknao> #info pboy (and perhaps likeanushka) was to develop a step-by-step plan for the re-formed product-oriented docs
18:38:05 <darknao> #info pboy was to submit the release note proposal to FESCO
18:38:25 <darknao> #link
18:39:32 <pboy> And we have a step-by-step plan as well
18:39:49 <pboy> #link
18:40:17 <darknao> nice, thanks pboy
18:40:37 <pboy> Sorry for the short notice
18:40:51 <py0xc3[m]> sounds good
18:41:26 <darknao> that's ok, do you want to talk about it now? or we can go back to it after the other topics
18:41:48 <pboy> I think after the other topics, but hopefuly today. :-)
18:42:02 <darknao> ok, we will do that
18:42:06 <darknao> so next topic is
18:42:39 <darknao> #topic tickets triage
18:42:49 <darknao> #link
18:43:01 <py0xc3[m]> On is open:
18:43:11 <py0xc3[m]> +One -on
18:43:48 <py0xc3[m]> The first question is if that is to be implemented.
18:43:59 <darknao> I think we discussed this one very briefly last time
18:44:12 <py0xc3[m]> We started this one, but had to stop due to the time
18:44:57 <py0xc3[m]> For the other one we decided to make it "good first issue" if someone is interested (I already labelled it).
18:45:22 <darknao> I think the documentation about the Account System should fall into the Infrastructure team
18:46:02 <darknao> but in the mean time, yes we can tag it as "good first issue", sounds good
18:46:09 <py0xc3[m]> +1. We have already sufficient To Do given the team size. Should it be forwared?
18:46:54 <pboy> I would prefer to forward it to the appropriate team for the affected docs.
18:47:05 <py0xc3[m]> darknao: I meant the other one ;) but yes, if we keep it in our triage, we can do so, maybe someone is interested
18:47:50 <darknao> ah ok sorry :)
18:48:29 <py0xc3[m]> All good ^^. So forward it to infra and close ?
18:48:52 <darknao> we can keep it there, i mean the repo is the good one, so I see no reason to close it
18:49:15 <pbokoc> Heh, well, if we forward it to infra they'll probably just ask me to do it anyway, so keep it open in case someone wants it, and if not I'll get to it sometime soon
18:49:42 <pboy> pbokoc 1++
18:49:51 <py0xc3[m]> Ok. So I just add good first one in case there is someone who wants to do it.
18:49:58 <pbokoc> Yeah.
18:50:29 <py0xc3[m]> The other old ticket is already discussed. So done.
18:50:37 <darknao> good :)
18:51:24 <darknao> #topic Discuss about the current Installation Guide
18:51:49 <darknao> #link
18:52:42 <py0xc3[m]> I started to do an index page for a "workstaiton + spin/kde" box in case we use that way:
18:53:30 <py0xc3[m]> pbokoc: I think you wrote the "beginner guide" we also distribute as printed version?
18:54:55 <pboy> py0xc3[m]. I'm fine with that.
18:55:16 <pbokoc> py0xc3[m], I didn't. I believe Jiri Eischmann (username eischmann) did
18:56:21 <py0xc3[m]> Ah ok.
18:57:01 <py0xc3[m]> However, the approach for the guide is currently that one:
18:58:10 <py0xc3[m]> pboy: what do you mean?
18:59:14 <pboy> py0xc3[m] I mean your "Workstation & spins User Guide" is a good plan. So let's do it.
18:59:30 <py0xc3[m]> Ah, ok.
18:59:54 <pboy> I'm not sure about Anaconda. Anaconda is only a small part in the Workstation installation, as far as I noticed.
19:00:07 <pboy> So you may not get so far with it.
19:00:24 <py0xc3[m]> Yes. They create the installer. So for the install guide, I mostly need them.
19:00:43 <py0xc3[m]> But in my experience it works comparably with other teams.
19:00:53 <pboy> Yes, but at first the live media needs explanation.
19:01:00 <py0xc3[m]> I have not yet collaborated for Docs but related issues.
19:01:19 <pboy> And when Anaconda finishes, there is some "post installation" work to do - and to describe.
19:01:27 <py0xc3[m]> pboy: the image they will provide will be something that contains everything until Fedora is installed
19:02:08 <py0xc3[m]> And if others are involved for a Doc, I tend to go to them.
19:02:40 <pboy> That's a good approach, I think.
19:02:48 <pboy> My very pragmatic intention is to have a name for the box and a text that the box can link to.
19:03:01 <py0xc3[m]> As I wrote, in Fedora's social dynamics, we have the role of Workstation WG when it comes to Docs... So if we don't accept  that, it will be something for the Council to clarify what to do. If we do, we take the role and then, I don't see the need for another iteration in between.
19:03:50 <py0xc3[m]> I already forked a template in that we can put the Docs
19:04:05 <py0xc3[m]> I can add it to /Fedora/Docs so that it is already there if you prefer that?
19:04:28 <py0xc3[m]> But it is not yet ready. I just wrote the index file
19:04:47 <pboy> You should do it as it is good for you and your work.
19:05:06 <py0xc3[m]> Or do you already have something? In which I should put the index.adoc?
19:05:21 <pboy> No, I haven't.
19:05:38 <py0xc3[m]> As long as I have a repo to push to, I'm fine ;) I can fork to my account anyway.
19:06:04 <py0xc3[m]> So if it is easier for you to already prepare your files, I can put it to our fedora docs gitlab
19:06:53 <pboy> I think, darknao it's your domain how to organize the repo, I think!
19:07:23 <pboy> You know best of us
19:09:13 <darknao> well, i've nothing against creating a new repo in the Fedora Linux Documentatino namespace if that is what you need
19:10:07 <pboy> What do you think is best of us?
19:10:22 <pboy> What do you advise to do?
19:10:27 <py0xc3[m]> I have no preference. I can also add it to an existing repo. My guess was that or structure "traditionally" has separated repos for separated boxes.
19:10:35 <py0xc3[m]> -or +our
19:11:30 <darknao> I think you should start working directly in the Fedora Docs groups instead of your own space, if for some reason someone else need to take over, that'll be easier
19:12:10 <py0xc3[m]> So keep it in separated repo?
19:12:10 <darknao> and everyone can see your work in the meantime, and I think that is a good thing to show that we are actually working on something :)
19:12:46 <pboy> darknao agreed! (specifically with the last post)
19:13:38 <py0xc3[m]> Ok. I'll move the repo as it is to /Fedora/Docs.
19:14:10 <py0xc3[m]> /fedora/docs/fedora-linux-documentation
19:14:19 <darknao> we traditionnally use one repo per doc component, but antora is quite flexible on that matter, so if you think your docs can live within an existing repo, that's fine to me too
19:15:08 <pboy> I've a slight preference for separate repo. it's easier to finde it. :-)
19:15:25 <py0xc3[m]> I think for future organization, separation makes sense. So that different boxes don't depend on each other
19:15:50 <pboy> No, the box a separate and contain mainly a link.
19:16:55 <py0xc3[m]> I know, I meant everything that belongs to it ;) If we make major changes to a box, it is likely to also affect any content contained. Knowing one box represents one repo is easier and nothing can go wrong with that ;)
19:17:56 <py0xc3[m]> However, I will put the repo to Fedora Linux Docs in Gitlab, I think there is a slight consensus about that :)
19:18:22 <darknao> agreed
19:18:25 <pboy> py0xc3[m] most boxes have the own short text anda link to a repo elsewhere. in case of Server e.g. to pagure.
19:18:32 <py0xc3[m]> I will merge the install guide and workstation & spin repo already
19:18:43 <py0xc3[m]> I know ;)
19:18:58 <pboy> I think, we should leave the current install guide repo as it is.
19:19:45 <py0xc3[m]> no no, I mean my new install guide ;) currently, I started it as a dedicated repo. Then I created the "Workstation & spin" repo when you asked me for an index page.
19:20:08 <py0xc3[m]> I will not touch the old one... (for now :P )
19:20:19 <darknao> if it's ok for you, i would like to use the last 10 minutes for pboy's topic
19:20:35 <pboy> It's OK for me. :-)
19:20:36 <darknao> just to make sure we have enough time for it :)
19:20:47 <py0xc3[m]> Well, I think we are done with the other :)
19:21:08 <darknao> alright
19:21:12 <darknao> #topic step-by-step plan for the re-formed product-oriented docs
19:21:14 <darknao> #link
19:21:53 <pboy> My first question is, do we agree about the target date? F37 / Oct. 25?
19:22:06 <pboy> It's tight, but doable, I think
19:22:57 <darknao> it's indeed a bit tight considering our current work force :)
19:23:38 <darknao> i don't want anyone to feel any kind of pressure about this
19:24:04 <pboy> Well, we have 2 documents to write. One is the intro text "Fedora Documentation" and the other is "Workstation & spin"
19:24:05 <darknao> but we can at least try
19:24:28 <pboy> OK, let's try
19:24:43 <py0xc3[m]> Do you mean much more than an index page for Workstation?
19:25:13 <pboy> py0xc3[m] An index page with an overview would be fine, I think.
19:25:25 <pboy> It's a first step.
19:25:35 <py0xc3[m]> Ok. That should be fine for that date.
19:25:44 <pboy> And it is a huge improvement, given the current situation.
19:26:09 <py0xc3[m]> However, we should be clear that the guide will take time, especially as it is created along with Web UI
19:26:51 <pboy> py0xc3[m] Agreed! It's the same with other parts, e.g. administrators guide
19:27:10 <py0xc3[m]> I will create a topic in ask.fp and discussion about other categories and contents taht should be added. Let's see what people mean and suggest, and what I can maintain over time.
19:27:16 <py0xc3[m]> So we can already gather information.
19:27:22 <py0xc3[m]> Ok.
19:28:00 <pboy> My other concern is the proper infra to work with. And to have an easy preview.
19:28:15 <pboy> darknao we need you for that. :-)
19:28:28 <darknao> so I see the first step is to configure the staging environment
19:28:54 <darknao> I can create a stg branch on that repo where you can make all your changes
19:29:20 <darknao> this repo I mean
19:29:52 <pboy> OK. for the docs homepage it is "Fedora Linux Documentation" and there Fed Lin Doc Home, isn't it?
19:30:34 <pboy> darknao. yes, I meant that.
19:31:10 <darknao> ok, can do that
19:31:18 <pboy> Thanks!
19:32:08 <pboy> So, I think we implicit decided to start the run.
19:32:17 <pboy> and make the move
19:33:19 <py0xc3[m]> Sounds good ;)
19:34:40 <darknao> #agreed We start implementing the variant-oriented docs plan
19:34:51 <darknao> ok, we are overtime
19:35:06 <darknao> thanks everyone, see you around!
19:35:19 <darknao> #endmeeting