<@jflory7:fedora.im>
13:06:11
!startmeeting Fedora Docs Team Meeting - 2026-01-27
<@meetbot:fedora.im>
13:06:12
Meeting started at 2026-01-27 13:06:11 UTC
<@meetbot:fedora.im>
13:06:12
The Meeting name is 'Fedora Docs Team Meeting - 2026-01-27'
<@jflory7:fedora.im>
13:06:19
!meetingname docs
<@meetbot:fedora.im>
13:06:20
The Meeting Name is now docs
<@jflory7:fedora.im>
13:06:26
!topic Hello & Welcome's
<@jflory7:fedora.im>
13:06:28
!hi
<@zodbot:fedora.im>
13:06:30
Justin Wheeler (jflory7) - he / him / his
<@hricky:fedora.im>
13:06:38
!hi
<@pbokoc:fedora.im>
13:06:38
!hi
<@zodbot:fedora.im>
13:06:39
Hristo Marinov (hricky) - he / him / his
<@zodbot:fedora.im>
13:06:39
Petr Bokoฤ (pbokoc)
<@nielsenb:fedora.im>
13:06:47
!hi
<@zodbot:fedora.im>
13:06:48
Brandon Nielsen (nielsenb)
<@jflory7:fedora.im>
13:07:09
Good morning, good afternoon, good evening, folks.
<@jflory7:fedora.im>
13:07:12
How is everyone doing today?
<@pboy:fedora.im>
13:07:58
Fine. Just back from shoveling snow :_)
<@jflory7:fedora.im>
13:08:11
So much here in Germany from yesterday!!
<@jflory7:fedora.im>
13:08:25
Mecklenberg-Vorpommen was slammed too with snow
<@jflory7:fedora.im>
13:08:47
I am just getting settled in myself
<@hricky:fedora.im>
13:08:58
I'm fine. It's just raining here.
<@jflory7:fedora.im>
13:08:59
I saw your brief agenda in the Docs Team chat, Peter. We will stick with that for today.
<@jflory7:fedora.im>
13:09:14
Whereabouts? What time zone are you in? Also CET?
<@hricky:fedora.im>
13:10:42
Sofia, Bulgaria, UTC +2
<@jflory7:fedora.im>
13:11:06
!info Proposed agenda topics for today's meeting: Review of ongoing actions from last meeting; What to do next: Improve Docs Homepage contentwise; Forgejo?
<@jflory7:fedora.im>
13:11:50
Hristo Marinov: So not too far southeast from me and Peter today ๐
<@jflory7:fedora.im>
13:11:57
Let's get to some team announcements and news
<@jflory7:fedora.im>
13:12:07
!topic Team announcements, community updates, and general open source news
<@jflory7:fedora.im>
13:12:12
Anyone have something to share?
<@jflory7:fedora.im>
13:12:26
Peter Boy (ServerWG, Docs), Petr Bokoc: Want to plug your CentOS Connect session? And Docs Hour at FOSDEM?
<@jflory7:fedora.im>
13:13:25
!info This week is "open source week" in Brussels, Belgium. Several events like CentOS Connect, FOSDEM, CHAOSScon EU, and others are taking place in Brussels. There are several Fedora contributors who will be present, including members of the Fedora Docs Team. If you will be there, be sure to let us know and add your name to the FOSDEM 2026 Wiki page.
<@jflory7:fedora.im>
13:13:30
!link https://fedoraproject.org/wiki/FOSDEM_2026
<@jflory7:fedora.im>
13:13:47
Anyone else going to be there, other than me, Peter, and Petr?
<@jflory7:fedora.im>
13:14:17
I know we are hoping to do some Docs "office hours" at our Fedora stand at FOSDEM this weekend.
<@pboy:fedora.im>
13:14:24
Well, for those who join Cent'OS Connect, we have a workshop on Thursday.
<@pbokoc:fedora.im>
13:14:50
!Info we'll have a 2 hour session at CentOS Connect on Jan 29 at 11 AM local time. Schedule is here: https://www.centos.org/events/connect/ - note that this is a separate venue from FOSDEM, more info on the page.
<@pboy:fedora.im>
13:14:53
And we have planned an "office 2 hours" on Saturday
<@jflory7:fedora.im>
13:15:03
!link https://cfp.fedoraproject.org/centos-connect-2026/talk/HTTAMR/
<@jflory7:fedora.im>
13:15:11
Petr Bokoc: TY!
<@jflory7:fedora.im>
13:15:27
We need to follow up with ffmancera and Daniel to make sure this gets scheduled ๐
<@jflory7:fedora.im>
13:15:41
I have one more announcement to share
<@jflory7:fedora.im>
13:16:49
!info Flock, the annual Fedora contributor conference, is taking place from 14-16 June 2026 in Prague, CZ. Registration is now open. The CFP closes on Monday! Now is the time to get content into the CFP before it closes.
<@jflory7:fedora.im>
13:16:50
!link https://cfp.fedoraproject.org/flock-to-fedora-2026/cfp
<@jflory7:fedora.im>
13:17:18
(Something I am not going to put in the meeting minutes is that we are secretly going to extend the CFP by one week, with a public announcement coming on Thursday or Friday)
<@jflory7:fedora.im>
13:17:28
Just so you folks going to Brussels need not to panic ๐
<@pbokoc:fedora.im>
13:17:33
Haha, nice
<@jflory7:fedora.im>
13:17:57
Any other news, announcements, cool FOSS news?
<@pboy:fedora.im>
13:18:01
Yes, I've to CfP proposals in work.
<@pboy:fedora.im>
13:18:10
Yes, I've two CfP proposals in work.
<@jflory7:fedora.im>
13:18:25
Superb!
<@jflory7:fedora.im>
13:18:34
### News & announcements, going onceโฆ
<@jflory7:fedora.im>
13:18:55
### News & announcements, going twiceโฆ
<@jflory7:fedora.im>
13:19:05
### News & announcements, going thriceโฆ
<@jflory7:fedora.im>
13:19:17
๐จ
<@jflory7:fedora.im>
13:19:25
!topic Today's Agenda
<@jflory7:fedora.im>
13:19:36
!info Topic 1: Action items from last time
<@jflory7:fedora.im>
13:19:53
!info Topic 2: Next steps, Fedora Docs homepage content.
<@jflory7:fedora.im>
13:19:58
!info Topic 3: Forgejo
<@jflory7:fedora.im>
13:20:02
!info Topic 4: Open Floor
<@jflory7:fedora.im>
13:20:08
!topic Action items from last time
<@jflory7:fedora.im>
13:20:28
!link https://discussion.fedoraproject.org/t/fedora-docs-meeting-2026-01-13-tooling-triage-and-task-leads/179473
<@jflory7:fedora.im>
13:20:39
> @jflory7, @pboy, @pbokoc: Migrate the Fedora Docs Team docs site from Pagure to Forgejo in January 2026 (ideally before FOSDEM).
<@jflory7:fedora.im>
13:20:48
> @nielsenb: Open a new ticket on Quick Docs repo with an initial analysis of content needs, challenges, and state of affairs so we can prioritize content updates and request help from authors later in 2026. Due: 2026-01-27 (next Fedora Docs Team meeting).
<@jflory7:fedora.im>
13:20:57
Peter Boy (ServerWG, Docs), Petr Bokoc: Any Forgejo progress to report?
<@jflory7:fedora.im>
13:21:04
Brandon Nielsen: I believe you did the Quick Docs analysis, right?
<@pboy:fedora.im>
13:21:28
The Docs Docs has been merged.
<@pboy:fedora.im>
13:21:42
And I started to add projects and tracking issues.
<@jflory7:fedora.im>
13:21:43
You mean, like our team's docs? The Docs Team's docs?
<@pboy:fedora.im>
13:21:51
Yes.
<@jflory7:fedora.im>
13:21:55
Fantastic.
<@jflory7:fedora.im>
13:22:14
I see some progress here, indeed:
<@jflory7:fedora.im>
13:22:17
!link https://forge.fedoraproject.org/docs/
<@jflory7:fedora.im>
13:22:30
Peter Boy (ServerWG, Docs): Is this also updated in Antora too?
<@jflory7:fedora.im>
13:22:38
I mean, the git repo source
<@pboy:fedora.im>
13:23:03
Petr Bokoc: Did you update the file?
<@pboy:fedora.im>
13:23:10
I think so.
<@pbokoc:fedora.im>
13:23:42
I got the contributor docs moved, and I might be able to switch Quick Docs over before I leave for Brussels tomorrow, but I'm not 100% sure.
<@nielsenb:fedora.im>
13:23:57
https://pagure.io/fedora-docs/quick-docs/issue/923
<@jflory7:fedora.im>
13:23:58
!link https://gitlab.com/fedora/docs/docs-website/docs-fp-o/-/blob/prod/site.yml?ref_type=heads#L124
<@jflory7:fedora.im>
13:24:21
!link https://forge.fedoraproject.org/docs/team-docs
<@pbokoc:fedora.im>
13:24:33
And yes, it's switched, it's building from Forgejo now
<@jflory7:fedora.im>
13:24:59
!agreed [COMPLETED] @jflory7, @pboy, @pbokoc: Migrate the Fedora Docs Team docs site from Pagure to Forgejo in January 2026 (ideally before FOSDEM).
<@zodbot:fedora.im>
13:25:34
jflory7 gave a cookie to nielsenb. They now have 1 cookie, 1 of which was obtained in the Fedora 43 release cycle
<@jflory7:fedora.im>
13:25:40
Wow! This is super useful. Just seeing it for the first time.
<@jflory7:fedora.im>
13:25:53
So, who exactly is "in charge" of Quick Docs? Officially, is it us?
<@jflory7:fedora.im>
13:26:09
Oh nice. First-ever cookie ๐
<@nielsenb:fedora.im>
13:26:46
Given the amount of time I put in, makes me question the whole cookie system... :D
<@jflory7:fedora.im>
13:27:14
OK, let me clarify, who is actually merging PRs over there?
<@jflory7:fedora.im>
13:27:26
Is it Petr Bokoc?
<@pboy:fedora.im>
13:27:38
Brandon Nielsen: It's really greatโand scary. There's a lot to do.
<@jflory7:fedora.im>
13:27:51
Oh: https://pagure.io/group/quick-docs-committers
<@jflory7:fedora.im>
13:27:56
Another group that I created, lol
<@pboy:fedora.im>
13:27:57
Merge is done by various authors directly.
<@pboy:fedora.im>
13:28:15
We have a quickdocs contributor group
<@jflory7:fedora.im>
13:28:39
We probably need to have a dedicated "Quick Docs" topic. I think this is more important than the dedicated Forgejo topic for today.
<@pboy:fedora.im>
13:28:46
We have to oversee the process
<@jflory7:fedora.im>
13:28:47
!link https://pagure.io/fedora-docs/quick-docs/issue/923
<@pbokoc:fedora.im>
13:28:55
Usually me, yes
<@jflory7:fedora.im>
13:29:01
!agreed [COMPLETED] @nielsenb: Open a new ticket on Quick Docs repo with an initial analysis of content needs, challenges, and state of affairs so we can prioritize content updates and request help from authors later in 2026. Due: 2026-01-27 (next Fedora Docs Team meeting).
<@jflory7:fedora.im>
13:29:32
I propose we substitute the Forgejo topic for a Quick Docs topic in today's meeting, to follow up on Brandon Nielsen's work and figure out next steps for that.
<@jflory7:fedora.im>
13:29:39
For now, we just have 30 minutes
<@jflory7:fedora.im>
13:29:42
so let's keep the agenda rolling
<@jflory7:fedora.im>
13:29:45
And move to the next topic
<@jflory7:fedora.im>
13:30:01
Petr Bokoc, Peter Boy (ServerWG, Docs), Brandon Nielsen: Thanks all for following through on your action items! ๐ช
<@jflory7:fedora.im>
13:30:12
!info All pending action items from last time were completed, woohoo! ๐
<@jflory7:fedora.im>
13:30:26
!topic Next steps, Fedora Docs homepage content
<@jflory7:fedora.im>
13:30:50
Peter Boy (ServerWG, Docs), Petr Bokoc: I will hand over this topic to both of you, as I am not sure the goals we want to accomplish in today's discussion.
<@pboy:fedora.im>
13:31:32
Wait, i searching ....
<@pboy:fedora.im>
13:32:03
The proposal is at https://pboy.fedorapeople.org/draft/.
<@pboy:fedora.im>
13:32:24
Es should discuss / decide what to add there.
<@pboy:fedora.im>
13:32:57
E.g. the join group. And then have someone to contact them.
<@jflory7:fedora.im>
13:34:23
Screenshots for reference. Current page:
<@jflory7:fedora.im>
13:34:51
Peter's proposal:
<@pboy:fedora.im>
13:34:55
See also: https://forge.fedoraproject.org/docs/team-tasks/issues/6
<@jflory7:fedora.im>
13:35:07
!link https://pboy.fedorapeople.org/draft/
<@jflory7:fedora.im>
13:35:14
!link https://forge.fedoraproject.org/docs/team-tasks/issues/6
<@jflory7:fedora.im>
13:35:44
Peter Boy (ServerWG, Docs): If the structure is already approved from past discussions, what are the details that need to be finalized?
<@jflory7:fedora.im>
13:36:08
Does "structure" here mean "How to use Fedora Linux", "How to contribute and make Fedora Linux better", and "How Fedora Project & Community work"?
<@jflory7:fedora.im>
13:36:24
And the content details are which sites/things we publish? Or the content that describes each project/team/edition there?
<@pboy:fedora.im>
13:36:45
Well, we agreed about the structure. Nevertheless, if there are objections now, we should disuss nevertheless.
<@pboy:fedora.im>
13:37:16
The structure refers to the 3 sections: User doc, contrib doc, project doc
<@pboy:fedora.im>
13:37:47
Content deteils refers to the boxes beyond the section title.
<@nielsenb:fedora.im>
13:38:05
The only thought I have is, is "How to use Fedora Linux" really going to be unique to Fedora?
<@pboy:fedora.im>
13:38:59
We can't list all contrib docs. We must select which 6-10 we want to include here.
<@jflory7:fedora.im>
13:40:16
Got it. A small nitpick, but for the second section, I would just say "make Fedora better" instead of "make Fedora Linux better", just so we can really push the actual _Linux_-focused content into the top section.
<@pboy:fedora.im>
13:40:18
Brandon Nielsen: We have this section, currently. It should be specific to Fedora: Which edition to choose, how to prepare boot media for installation, etc.
<@jflory7:fedora.im>
13:40:23
How do you mean?
<@nielsenb:fedora.im>
13:40:34
Surfacing more docs on that page is probably a good thing, so from that standpoint I like the proposal.
<@jflory7:fedora.im>
13:40:58
So, the ๐ถ๏ธ spicy decision of deciding what projects/teams show up on the homepage, and what needs deeper exploration into the site to discover organically
<@nielsenb:fedora.im>
13:41:12
I mean, using Fedora (with the exception of say, Silverblue) isn't really that unique, and more non-unique documentation is just more maintenance burden.
<@jflory7:fedora.im>
13:41:29
Petr Bokoc: Do you know where the actual AsciiDoc source for this homepage lives? Is it AsciiDoc? Or is it actual HTML and CSS/JS?
<@pbokoc:fedora.im>
13:41:50
Yeah, just a sec, it's in gitlab
<@jflory7:fedora.im>
13:41:54
True. I think our main focus for what we elevate on the home page _should_ be things highly specific to Fedora only.
<@jflory7:fedora.im>
13:42:07
Because generally, our goal should not be to rewrite the world
<@jflory7:fedora.im>
13:42:17
A lot of people are going to go to Arch Wiki first, and we just need to accept that ๐
<@pboy:fedora.im>
13:42:23
The current source is kind of embedded html und lives on GitLab
<@jflory7:fedora.im>
13:42:28
But Arch Wiki doesn't ever get super specific into Fedora on stuff, it is usually more general
<@pbokoc:fedora.im>
13:42:55
https://gitlab.com/fedora/docs/docs-website/pages
<@jflory7:fedora.im>
13:43:01
Awesome
<@pbokoc:fedora.im>
13:43:09
The layout is in plain HTML.
<@jflory7:fedora.im>
13:43:25
So, OK. A logistics question. Should we undertake the effort of redoing this page on GitLab? Or should we make the leap to Forgejo, and then do a rally call for contributions?
<@jflory7:fedora.im>
13:43:35
And maybe, I am even putting the cart before the horse
<@jflory7:fedora.im>
13:43:40
We probably need to make a timeline for this effort
<@pboy:fedora.im>
13:43:40
to Forgejo !!!
<@jflory7:fedora.im>
13:43:45
Since we have been discussing/talking about it for some time
<@jflory7:fedora.im>
13:43:52
This is my feeling too TBH ๐
<@jflory7:fedora.im>
13:44:23
If I were to sketch out a possible timeline for thisโฆ
<@pboy:fedora.im>
13:45:40
I suppose, to migrate that repo to forgejo ist not that much work. A big thing is the repo with all the antorra config.
<@pboy:fedora.im>
13:46:15
https://gitlab.com/fedora/docs/docs-website/docs-fp-o
<@jflory7:fedora.im>
13:46:37
<@jflory7:fedora.im>
13:46:37
## Docs Homepage, Phase 1: Initialization
<@jflory7:fedora.im>
13:46:37
<@jflory7:fedora.im>
13:46:37
Tooling-focused, workflow-focused. Migrating from GitLab to Forgejo. Setting up the repo. Opening/moving issues that describe the work that needs to be done on the Fedora Docs homepage.
<@jflory7:fedora.im>
13:46:37
<@jflory7:fedora.im>
13:46:37
## Docs Homepage, Phase 2: Content
<@jflory7:fedora.im>
13:46:37
Could happen in parallel to Phase 1. Focusing on vetting the content, and which Antora modules/git repos we are loading onto the Fedora Docs homepage. Making sure we are aligned on what should be appearing here and that we are linking out to docs sites that are being maintained.
<@jflory7:fedora.im>
13:46:37
<@jflory7:fedora.im>
13:46:37
## Docs Homepage, Phase 3: Hack Time! ๐ฅ๏ธ
<@jflory7:fedora.im>
13:46:37
<@jflory7:fedora.im>
13:46:37
Implementation. Actually updating the HTML to map out to Peter's prototype and the agreed team decision on content.
<@jflory7:fedora.im>
13:46:40
How does this sound?
<@jflory7:fedora.im>
13:47:19
I think migrating this specific repo to Forgejo might be one of our last ones, and something we will want to do in close synchronization with darknao
<@pboy:fedora.im>
13:47:20
Sounds great!
<@pboy:fedora.im>
13:47:53
I already pinged Darknao for help.
<@jflory7:fedora.im>
13:47:57
OK, super. Ideally, each phase has a timebox on it, but I want to make sure we have time for a Quick Docs discussion.
<@jflory7:fedora.im>
13:48:08
That's great.
<@jflory7:fedora.im>
13:48:32
So, I can codify some of this in the meeting minutes with Meet Bot, but is anyone actually interested in leading on some of this?
<@jflory7:fedora.im>
13:48:42
I would say it is a high-visibility contribution opportunity.
<@jflory7:fedora.im>
13:48:49
After all, this is the homepage of the Fedora Docs universe ๐
<@jflory7:fedora.im>
13:49:10
Petr Bokoc, Brandon Nielsen, Hristo Marinov: Any thoughts?
<@pboy:fedora.im>
13:49:25
Well, I did this in the past.
<@nielsenb:fedora.im>
13:49:26
Seems reasonable to me.
<@pbokoc:fedora.im>
13:49:35
I
<@nielsenb:fedora.im>
13:49:55
I agree with the "straight to Forgejo" for anything new / refreshed.
<@pbokoc:fedora.im>
13:50:00
I can do the migration. I'm not sure I can do it before the next meeting, though, the next 2 weeks are going to be busy.
<@pbokoc:fedora.im>
13:50:39
Well, okay, the Monday after next maybe :)
<@jflory7:fedora.im>
13:50:45
I think getting from GitLab to Forgejo is something best done by an experienced contributor first, so we can "set up" the foundation for success. But for Phases 2 and 3, I think we should promote these more widely and protect them from core maintainers ๐
<@jflory7:fedora.im>
13:51:16
They are great contribution opportunities, and if we can all be aligned on the process and general workflow for how we want to do it, then we can guide someone along in making these changes, and maybe onboard some new folks along the way too
<@jflory7:fedora.im>
13:51:35
Petr Bokoc: The Monday after, meaning 2 February or 9 February?
<@pboy:fedora.im>
13:51:50
Yes, we should have all the migrations in one hand!
<@pboy:fedora.im>
13:52:27
Until now it is Petr and me (me as discussion partner).
<@jflory7:fedora.im>
13:53:43
OK. We are running out of time. Let me document this for the minutes and give some action items.
<@jflory7:fedora.im>
13:54:20
!info The general timeline for the Fedora Docs homepage modernization process can be divided into three, sequential phases: Initialization, Content Review, Implementation.
<@lochipi:matrix.org>
13:54:27
Hi, and thanks. I'll check that. Joining late :)
<@jflory7:fedora.im>
13:55:07
!info Phase 1, Initialization: Tooling-focused, workflow-focused. Migrating from GitLab to Forgejo. Setting up the repo. Opening/moving issues that describe the work that needs to be done on the Fedora Docs homepage.
<@jflory7:fedora.im>
13:55:10
!info Phase 2, Content Review: Could happen in parallel to Phase 1. Focusing on vetting the content, and which Antora modules/git repos we are loading onto the Fedora Docs homepage. Making sure we are aligned on what should be appearing here and that we are linking out to docs sites that are being maintained.
<@jflory7:fedora.im>
13:55:15
!info Phase 3, Implementation: Actually updating the HTML to map out to Peter's prototype and the agreed team decision on content.
<@jflory7:fedora.im>
13:55:50
!info Suggested to let an experienced team member handle the migration, and then make a more open call for help on this project in our existing outreach channels (e.g. Fedora Discussion, Matrix, mailing lists, etc.)
<@jflory7:fedora.im>
13:56:15
!action @pbokoc Migrate the Fedora Docs "pages" repository from GitLab to Forgejo by the next team meeting on 10 February 2026
<@jflory7:fedora.im>
13:56:38
!action @pboy Edit the Forgejo issue for the Docs homepage task to describe the "three phases" approach to this ticket.
<@jflory7:fedora.im>
13:56:55
!action @jflory7 Prepare a next meeting topic for opening up the contribution call for the Fedora Docs homepage project
<@jflory7:fedora.im>
13:56:59
OK, I think that is enough.
<@jflory7:fedora.im>
13:57:10
!topic Quick Docs content structure & organization
<@jflory7:fedora.im>
13:57:25
OK, so I have a _little_ bit of flex to go over the meeting time.
<@jflory7:fedora.im>
13:57:32
But not more than 3-4 minutes ๐
<@jflory7:fedora.im>
13:57:41
So, Brandon Nielsen did all of that awesome work:
<@pboy:fedora.im>
13:57:58
Yes, many thanks!
<@jflory7:fedora.im>
13:58:26
!link https://pagure.io/fedora-docs/quick-docs/issue/923
<@jflory7:fedora.im>
13:58:32
I think we need to figure out how to action this ๐ค
<@jflory7:fedora.im>
13:58:54
There are lots of jumping-off points from here, but I almost feel like we need to choose 2-3 pages and make "good first issues" to guide newcomer contributors to these tasks
<@pboy:fedora.im>
13:58:57
I would like to have evolved this into a batch file running every 3 months and to compress this into a table.
<@jflory7:fedora.im>
13:59:14
Peter Boy (ServerWG, Docs): I think Brandon Nielsen did this review manually, though?
<@nielsenb:fedora.im>
13:59:22
I did.
<@pboy:fedora.im>
13:59:48
Yes, question is, would it be possible to automate? See:
<@pboy:fedora.im>
14:00:07
https://forge.fedoraproject.org/docs/team-tasks/issues/3
<@nielsenb:fedora.im>
14:00:40
In general it would. But I'm not actually sure how strongly "reviewed last" correlates to "doc quality".
<@jflory7:fedora.im>
14:00:50
The automation question is, indeed, interesting. But I don't think that should be our main focus first, though.
<@nielsenb:fedora.im>
14:01:13
At the same time, it could be said that documentation that hasn't changed in a decade, but is still "good", might not actually be that Fedora specific?
<@pboy:fedora.im>
14:01:14
Brandon Nielsen: yeah, but at the moment we don't have a better indicator.
<@jflory7:fedora.im>
14:01:14
Since the focus of the Initiative is to "flatten the rollercoaster" and ultimately make it easier to participate in Docs, I think we have a great recruiting opportunity in front of us
<@jflory7:fedora.im>
14:01:33
And maybe if we recruit some writers to help with this content, we can move to bigger and better automation projects in the future
<@pboy:fedora.im>
14:01:46
T
<@jflory7:fedora.im>
14:02:09
I'm not sure there is a statistical correlation there.
<@pboy:fedora.im>
14:02:31
The focus regarding QD should currently be content. But at the ende we need some metrics.
<@nielsenb:fedora.im>
14:02:58
I'm mostly just passing along my general, overall, feelings from actually scrolling through each doc page.
<@nielsenb:fedora.im>
14:03:15
I agree that at this moment any metric would be appreciated.
<@jflory7:fedora.im>
14:03:16
So, it sounds like we also need to do some "timeline mapping" for this Quick Docs effort. And actually, maybe prioritizing Quick Docs tasks/projects in a way where we can prioritize them and map them on a timeline.
<@nielsenb:fedora.im>
14:03:23
Especially if it can be eventually automated.
<@pboy:fedora.im>
14:03:26
Part of quality is timeliness. And Fedora is developing rapidly.
<@jflory7:fedora.im>
14:03:34
Time and energy are finite, so we need to make sure we are choosing our focuses wisely. And a key focus for me is growing our numbers.
<@jflory7:fedora.im>
14:03:45
With that though, I do think we need to yield back ๐
<@jflory7:fedora.im>
14:03:54
I am late for my next meeting, and I think this topic will need more discussion.
<@jflory7:fedora.im>
14:04:03
Let's defer to some async chat in #docs:fedoraproject.org
<@jflory7:fedora.im>
14:04:35
Brandon Nielsen: I saw someone in the Docs channel working on the sysadmin guide. Not sure if any of the quick docs pages you identified might be relevant for this person to work on, but I think if someone is rearing to go and get started, your issue gives an idea of where to start.
<@jflory7:fedora.im>
14:05:10
!info Ran out of time to discuss this topic sufficiently. There was discussion about the goal of automating the report that Brandon compiled, creating some metrics for docs quality, and using the new issue to map out "good first issue" contributions for new contributors.
<@jflory7:fedora.im>
14:05:20
!halp Please help carry on this discussion in the Fedora Docs team chat!
<@pboy:fedora.im>
14:05:44
Brandon Nielsen: Hi checked QD for relation to SysAdmin guide.
<@jflory7:fedora.im>
14:05:44
!action @pboy Update Docs Team ticket about Quick Docs with today's discussion and next steps for the 10 February 2026 meeting
<@jflory7:fedora.im>
14:05:55
With that folks, I am going to do an abrupt end ๐
<@jflory7:fedora.im>
14:05:59
No time for open floor, this time.
<@jflory7:fedora.im>
14:06:10
Brandon Nielsen: Let's talk membership for the Docs Team over in #docs:fedoraproject.org too!
<@jflory7:fedora.im>
14:06:16
See ya next time folks. Thanks so much for being here!
<@jflory7:fedora.im>
14:06:18
!endmeeting