<@jflory7:fedora.im>
13:04:17
!startmeeting 2026-01-13 - Fedora Docs Team Meeting
<@meetbot:fedora.im>
13:04:18
Meeting started at 2026-01-13 13:04:17 UTC
<@meetbot:fedora.im>
13:04:18
The Meeting name is '2026-01-13 - Fedora Docs Team Meeting '
<@pboy:fedora.im>
13:04:20
https://discussion.fedoraproject.org/t/docs-team-2025-kick-off-meeting-part-two-agenda-proposal/179450
<@jflory7:fedora.im>
13:04:29
!meetingname docs
<@meetbot:fedora.im>
13:04:31
The Meeting Name is now docs
<@jflory7:fedora.im>
13:04:47
!topic Roll Call
<@yukih:fedora.im>
13:04:58
Hi yes I'm here
<@pboy:fedora.im>
13:04:59
!hi
<@zodbot:fedora.im>
13:05:02
Peter Boy (pboy)
<@nielsenb:fedora.im>
13:05:10
!hi
<@zodbot:fedora.im>
13:05:11
Brandon Nielsen (nielsenb)
<@pbokoc:fedora.im>
13:05:27
!hi
<@zodbot:fedora.im>
13:05:28
Petr BokoΔ (pbokoc)
<@yukih:fedora.im>
13:05:45
!hi
<@zodbot:fedora.im>
13:05:47
None (yukih)
<@jflory7:fedora.im>
13:07:16
Welcome, folks!
<@jflory7:fedora.im>
13:07:21
A good morning from here.
<@jflory7:fedora.im>
13:07:28
Our first meeting of the new year!
<@yukih:fedora.im>
13:07:35
good evening from here
<@jflory7:fedora.im>
13:07:40
I hope it is a good beginning of the year for you all.
<@pbokoc:fedora.im>
13:07:50
Welcome to 2026 :)
<@jflory7:fedora.im>
13:08:03
So, we have a few topics to discuss today, that Peter outlined on Fedora Discussion: https://discussion.fedoraproject.org/t/docs-team-2025-kick-off-meeting-part-two-agenda-proposal/179450
<@yukih:fedora.im>
13:08:04
Happy new year
<@jflory7:fedora.im>
13:08:19
We will go through this shortly!
<@jflory7:fedora.im>
13:10:08
I am also properly at my desk now instead of the phone π
<@jflory7:fedora.im>
13:10:45
!info Present: @jflory7, @pboy, @nielsenb, @pbokoc, @yukih
<@jflory7:fedora.im>
13:10:48
Let's get started.
<@jflory7:fedora.im>
13:10:52
!topic Agenda
<@jflory7:fedora.im>
13:10:57
!link https://discussion.fedoraproject.org/t/docs-team-2025-kick-off-meeting-part-two-agenda-proposal/179450
<@jflory7:fedora.im>
13:11:57
!info 1. Improving Contributor Guidance
<@jflory7:fedora.im>
13:12:11
!info 2. Improvement of the current local authoring tool
<@jflory7:fedora.im>
13:12:15
!info 3. Document analyses and improvement
<@jflory7:fedora.im>
13:12:27
!info 4. Way of collaboration
<@jflory7:fedora.im>
13:12:34
These are the four main topics we will discuss
<@jflory7:fedora.im>
13:12:40
Let's check in on action items from last time first
<@jflory7:fedora.im>
13:12:47
!topic Action items from previous meeting
<@jflory7:fedora.im>
13:13:06
!link https://discussion.fedoraproject.org/t/fedora-docs-team-meeting-2025-12-16-first-meeting-back-initiative-overview-and-next-steps/177331
<@jflory7:fedora.im>
13:13:50
OK, so, that was our first meeting.
<@jflory7:fedora.im>
13:13:56
And we didn't have so many action items yet π
<@jflory7:fedora.im>
13:14:02
But there was one "ongoing" call for everyone.
<@jflory7:fedora.im>
13:14:18
!info An ongoing call for help: Meeting attendees last time were encouraged to reflect on areas of passion to volunteer for in the new year.
<@jflory7:fedora.im>
13:14:30
So, I think this still applies! But no discussion needed here
<@jflory7:fedora.im>
13:14:36
Let's go the discussion topics
<@hricky:fedora.im>
13:14:43
!hi
<@zodbot:fedora.im>
13:14:44
Hristo Marinov (hricky) - he / him / his
<@jflory7:fedora.im>
13:15:03
!info +Present: @hricky
<@jflory7:fedora.im>
13:15:06
Hey Hristo!
<@jflory7:fedora.im>
13:15:18
!topic Improving Contributor Guidance
<@jflory7:fedora.im>
13:16:41
Wait a sec, soβ
<@jflory7:fedora.im>
13:16:56
I see the way that Peter Boy (ServerWG, Docs) planned the meeting was for us to discuss all of these topics.
<@yukih:fedora.im>
13:16:58
Ahhhh, ok. We can start with a detailed doc on the tools used for the docs, how to set up their forgejo, and different repo structures so new contributors don't get lost
<@jflory7:fedora.im>
13:17:10
And then try and see who could become the "task owner" for the various topics on the list.
<@jflory7:fedora.im>
13:17:22
so, maybe it is better to discuss them at once, instead of one by one.
<@jflory7:fedora.im>
13:18:01
!info We will not discuss topic-by-topic, but instead, review all of the topics together, and go over prioritization and allow all present meeting members ask questions about the tasks to help get involved.
<@jflory7:fedora.im>
13:18:20
!topic Reviewing the 2026 Docs Team priorities, identifying task/topic leads, and team Q&A
<@jflory7:fedora.im>
13:19:51
!info Meeting Goal: We are conducting our first round of work planning for the year. Our objective is to define our key work topics and, most importantly, assign a dedicated lead (someone to wear the "hat") for each initiative. We need individuals to commit to these specific areas to ensure progress.
<@pboy:fedora.im>
13:19:59
Yukih: Also I currently are writing a doc about setting up a local Forgejo, Docs contributor may not need a local repo.
<@yukih:fedora.im>
13:20:32
Ohhhh, ok. Thank you β€οΈ
<@pboy:fedora.im>
13:20:33
But we need some docs, who to use the Forgejo repo
<@pboy:fedora.im>
13:20:58
But we need some docs, how to use the Forgejo repo
<@yukih:fedora.im>
13:21:42
https://forge.fedoraproject.org/docs
<@yukih:fedora.im>
13:21:42
You mean fedora forge for the docs?
<@jflory7:fedora.im>
13:22:05
!info Contributor Guidance & Tooling: We are seeking a lead to document the Forgejo editing workflow and oversee improvements to the local authoring tool. This role includes managing technical tasks such as adding ARM support to the container and enabling on-demand document rebuilding to replace full site builds.
<@jflory7:fedora.im>
13:22:21
!info Document Analysis & Maintenance: A lead is required to conduct a comprehensive audit of Quick Docs and Administration Guides to categorize content by age and accuracy. This individual will identify priority areas for updates, determine which guides should be archived, and coordinate with maintainers to verify technical details.
<@jflory7:fedora.im>
13:22:42
!info Collaboration Workflow: We need a coordinator to finalize our collaboration standards, specifically regarding Git branching strategies and real-time editing platforms. This task involves evaluating the trade-offs between HackMD's discussion features and the requirement for native AsciiDoc support in alternative tools like Etherpad.
<@pboy:fedora.im>
13:22:58
Yeah, but currently we didn't manage to migrate at least one repo, I just notice. Petr Bokoc are you planing to migrate ReleaseNotes and QuickDocs?
<@jflory7:fedora.im>
13:23:17
So, I think those three items are the high-level things we are looking for leads on. There are plenty of smaller, sub-tasks that could fit into these things.
<@pbokoc:fedora.im>
13:23:22
Yes, soon
<@jflory7:fedora.im>
13:23:33
But those three areas are the main focuses that Peter outlined in the Discussion topic
<@jflory7:fedora.im>
13:23:54
Using it for writing and publishing docs?
<@jflory7:fedora.im>
13:24:05
Or for using the WYSIWYG editor feature?
<@jflory7:fedora.im>
13:24:16
I wonder if Forgejo would already have docs about the WYSIWYG editor
<@pboy:fedora.im>
13:24:24
Yes, as soon as we have migrated QuickDocs and Release Notes
<@jflory7:fedora.im>
13:24:28
It seems like something we may not need to document, if it already is documented upstream
<@pboy:fedora.im>
13:25:09
As far as I know, currently we have no ASCIIDOCS WYSISYG editor in Forgejo
<@nielsenb:fedora.im>
13:25:14
If they don't, they might appreciate it if we document it and contribute upstream
<@hricky:fedora.im>
13:25:16
Do we really need to document how to use Git, fork repos, etc.?
<@yukih:fedora.im>
13:25:49
I mean, kinda. Just to be safe i think
<@jflory7:fedora.im>
13:26:11
I think the question that will be more useful to document is how to get a docs repo published on docs.fp.o. Where to find the Fedora Docs source repo, understanding the `antora.yml` definition file, who can review the PR, etc.
<@jflory7:fedora.im>
13:26:25
These are the questions I see advanced contributors asking and they get stuck on today
<@jflory7:fedora.im>
13:26:45
And I think we might be putting the cart before the horse
<@pboy:fedora.im>
13:26:53
Hristo Marinov: For many writers the git workflow is unknown. And Git is quite a barrier. So we need a doc.
<@jflory7:fedora.im>
13:26:53
Yes, some docs on how to edit in Forgejo could be useful
<@jflory7:fedora.im>
13:26:58
But I think we need a strategy.
<@yukih:fedora.im>
13:27:08
ok
<@jflory7:fedora.im>
13:27:39
Peter Boy (ServerWG, Docs): It might be wise, since these basic items are very common things out there, that we avoid repeating the Internet ourselves. If we can lean on other communities who have already documented important things, it saves us a lot of time and effort to focus more on the Fedora-specific plumbing pieces
<@pboy:fedora.im>
13:27:54
We already have it (nearly) all. But it needs improvement and updates
<@jflory7:fedora.im>
13:28:08
For example, I'd prefer to have a "Resource Guide" for how to edit docs on Forgejo, and the resource guide links to other docs and pages online for where to learn the basics
<@jflory7:fedora.im>
13:28:32
Really? π I actually didn't even know this. Where do we publish the instructions today on how to add a new Fedora Docs site?
<@nielsenb:fedora.im>
13:28:42
Does the in place editor in Forgejo really support much git complexity?
<@jflory7:fedora.im>
13:28:44
I need to know, so I stop typing it out in details every time someone asks me π
<@nielsenb:fedora.im>
13:29:13
Like, if someone submits and update to the wrong branch or something, I feel like that is something we can walk them through changing.
<@jflory7:fedora.im>
13:29:29
So, bringing it back to the main topic at handβ
<@jflory7:fedora.im>
13:29:41
The goal for this topic is to identify some people who would want to take a leader role on some tasks.
<@jflory7:fedora.im>
13:29:51
We can discuss details all day here and in #docs:fedoraproject.org π
<@nielsenb:fedora.im>
13:30:10
Probably easier to guide after they've completed the first hurdle of "okay, I'm going to write this documentation and submit it" then add yet more needed learning on the front end.
<@jflory7:fedora.im>
13:30:12
But we need some bottom-liners to take accountability on thinking through the focus area, brainstorming some ideas and approaches, and sharing them back with the team.
<@pboy:fedora.im>
13:30:14
https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/
<@jflory7:fedora.im>
13:30:35
Peter Boy (ServerWG, Docs), Petr Bokoc, and I are looking at some high-level things, including a presentation to the Fedora Council in a little under a month.
<@jflory7:fedora.im>
13:30:48
So some of these content tasks will need some more hands while we are focused on these parts of the Community Initiative.
<@yukih:fedora.im>
13:31:01
4. Have a good defined structure and a systemic way to organize the docs to avoid later confusion and merges.
<@yukih:fedora.im>
13:31:01
2. Let contributors know the tools needed and add some sources for reference. For example: asciidoc, antora, docker.....etc
<@yukih:fedora.im>
13:31:01
<@yukih:fedora.im>
13:31:01
1. Start by letting contributors know where they can find the sorce code for the docs. That is https://forge.fedoraproject.org/docs
<@yukih:fedora.im>
13:31:01
I think I have a way to clear all the smoke.
<@yukih:fedora.im>
13:31:01
<@yukih:fedora.im>
13:31:01
3. How contributors can set up their development and help them understand the workflow. This makes new contriputors understand how to keep track with issues and open PRs
<@yukih:fedora.im>
13:31:01
<@hricky:fedora.im>
13:32:05
Can't we just provide links to guides that already describe the basic workflows instead of rewriting them?
<@jflory7:fedora.im>
13:32:28
<@jflory7:fedora.im>
13:32:28
I see this page now, but I actually thinking a bit that the content people are looking for might not be exposed in the best possible way. https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/contrib-new-documentation/
<@jflory7:fedora.im>
13:32:28
For example, I answer questions often for people on how to request a new docs site published on docs.fp.o. This page answers most but not all of it. Maybe someone looking at the Contributor Documentation as part of the content ownership topics would be good.
<@jflory7:fedora.im>
13:33:12
So, part of these tasks could be for someone taking the lead on Fedora Docs _contributor_ docs, which is largely in the section that Peter just linked.
<@pboy:fedora.im>
13:33:23
Maybe we should add some kind of FAQ
<@jflory7:fedora.im>
13:33:49
I don't know if discussing the content focus for a single article is the best use of our time, but if we can map out next steps for a group or groups of content, we will start cooking π³
<@yukih:fedora.im>
13:34:00
Hmmm, good question, we can improve them i think
<@jflory7:fedora.im>
13:34:41
I would think about it this way. The best way for _this group_ of Fedora Docs writers to use our time is to focus our talents, energy, and time on the things that are so uniquely Fedora, there won't be docs about them elsewhere on the Internet yet π
<@jflory7:fedora.im>
13:35:08
For the basic workflow things, let's follow DRY principles and think tactically on how the work of others in the FOSS community can be building blocks for us to do our own work
<@pboy:fedora.im>
13:36:12
We need to be aware that the GIT workflow was a major obstacle for many writers. They are not familiar with it. And the usual programmer Wirkflox, which is documented everywhere, is only approximately suitable for Docs.
<@jflory7:fedora.im>
13:36:48
So, to me, I am thinking we need a Content Owner for these topics: **Contributor Guidance & Tooling** (the meta workflows on tooling and how to interact with the Docs Team), **Document Analysis & Maintenance** (reviewing our most popular docs sites like Quick Docs for information architecture and triage), and **Collaboration Workflow** (meta processes on how the Docs Team works together, including exploring tools to help us do our work better).
<@nielsenb:fedora.im>
13:36:50
Yeah, I agree. I just poked at the Forgejo editor, it requires you to fork. Which is fine, but a big hurdle.
<@jflory7:fedora.im>
13:37:55
So, for our beginnings, I would like to consider perhaps the persona of _experienced Fedora contributors_ who write and maintain docs already. Onboarding newcomers is important of course, but we have a lot of people in Fedora who are familiar with git, maintain docs in Fedora either because they want to or they have to, and need to get more support from the Docs Team on things that are not the basic level stuff.
<@jflory7:fedora.im>
13:38:15
Consider all of the Fedora Docs sites we publish today. All 50+ of them in all of the different git repos, with all of the different teams working on them.
<@jflory7:fedora.im>
13:38:34
For a first focus, I'd almost like to cater to this persona first, instead of the total open source newcomer who has never used git before.
<@jflory7:fedora.im>
13:38:49
Then, once we address this persona, we can work backwards and improve the newcomer experience.
<@jflory7:fedora.im>
13:38:52
Does that make sense?
<@pboy:fedora.im>
13:39:00
Yes, Agreed.
<@nielsenb:fedora.im>
13:39:39
I agree in general. But I do worry about building an experience that is difficult to ever make newcomer friendly.
<@pboy:fedora.im>
13:40:05
Yeah, that's the challenge!
<@nielsenb:fedora.im>
13:40:09
I think a huge part of Arch wiki's success is anyone can figure out how to edit it without much additional knowledge.
<@jflory7:fedora.im>
13:40:37
I think "newcomer friendly" is relative. There is not one-size-fits-all and this is part of the challenge. But also, I think a big goal is on supporting our experienced folks already publishing docs, because they are the role models and many times, the first line of interaction with Fedora Docs.
<@jflory7:fedora.im>
13:40:52
This small group of people here is not responsible for all the content and all the teams writing content on docs.fp.o π
<@jflory7:fedora.im>
13:41:08
So, we should think about how we can be empowering other teams in Fedora to be good Fedora Docs stewards and leaders
<@jflory7:fedora.im>
13:41:26
This is a "people" part that needs to come one step before we get too deep on tooling and newcomer processes
<@jflory7:fedora.im>
13:41:31
Thinking about the rollercoaster rideβ
<@jflory7:fedora.im>
13:41:54
One of the "Fedora Docs rollercoaster dips" is when you get involved, you learn the basics, and now you are more ready to contribute. BUT, the community is not ready for you π
<@jflory7:fedora.im>
13:42:12
We should consider the needs of our existing docs authors and leaders, so they can be better landing points across the community
<@jflory7:fedora.im>
13:42:34
Very few Fedora Docs content improvements actually flow through _us_. Maybe Quick Docs, but the rest is managed independently by other Fedora teams out there. Not us.
<@nielsenb:fedora.im>
13:43:02
I think the current dip shows that a lot of current authors don't really take stewardship after the doc is contributed...?
<@jflory7:fedora.im>
13:43:12
That's why, I want us to focus on the "end" part of the rollercoaster. Maybe it is a big burden to learn some of our tools and workflows. It can be a challenge. For those who take the challenge and succeed, I want to be able to promise them a future as contributors in Fedora Docs π
<@nielsenb:fedora.im>
13:43:15
Probably not a popular opinion, but it's what I see.
<@pboy:fedora.im>
13:43:39
Yeah, indeed!
<@jflory7:fedora.im>
13:43:49
Brandon Nielsen: I think "taking stewardship" is a confusing thing in Fedora, and this could be the kind of guidance that we, the Fedora Docs Team, could provide.
<@jflory7:fedora.im>
13:44:06
## Time check: 16 minutes remaining
<@jflory7:fedora.im>
13:44:29
I do want to leave the last five minutes of the meeting for "open floor", for any other meta topics for next time or ongoing business
<@jflory7:fedora.im>
13:45:54
3. **Collaboration Workflow**: Meta processes on how the Docs Team works together, including exploring tools to help us do our work better.
<@jflory7:fedora.im>
13:45:54
1. **Contributor Guidance & Tooling**: Meta workflows on tooling and how to interact with the Docs Team.
<@jflory7:fedora.im>
13:45:54
2. **Document Analysis & Maintenance**: Reviewing our most popular docs sites like Quick Docs for information architecture and triage.
<@nielsenb:fedora.im>
13:45:55
I'll step aside for time with this last thought: making the process as easy as possible benefits everyone. Most people do documentation last, for better or for worse, so it gets rushed. If it's easy to contribute edits, at least we catch the people that use the documentation and go "huh, that's not right" and can fix it quickly. If that "quick fix" has much more than even the smallest hurdle to overcome, most people won't do it.
<@jflory7:fedora.im>
13:46:16
Do we have anyone who wants to raise their hand for being a lead on these topics, and working with me, Peter, and Petr and overseeing this?
<@jflory7:fedora.im>
13:47:34
You have a point here, but also, that step "fix it quickly" is rarely a quick thing in Fedora⦠I think we need to empower the maintainers more on the other end of the equation, so when the contribution does come in, it can be managed and responded to quickly. This works in some parts of the community but not in others. I think part of the ups-and-downs of the Fedora Docs rollercoaster is that the pathway to success is not clear.
<@jflory7:fedora.im>
13:48:11
We have a problem in Fedora in several teams, where the onboarding process is really tight and good, but then once the person is "onboarded", they are stuck without direction on what to do or how to keep contributing, and they get off the rollercoaster
<@nielsenb:fedora.im>
13:48:57
*looks nervously at my years old package sponsorship requests*
<@nielsenb:fedora.im>
13:49:28
But yeah, absolutely agree
<@nielsenb:fedora.im>
13:51:10
But I think a lot like quality, we'd benefit more by casting a wide net with almost no barrier to entry. Once people have contributed once or twice, they might be more inclined to stick around. And even if they, at least it's still easy for the next person that walks by.
<@jflory7:fedora.im>
13:51:16
Any takers? Or anyone interested in working on a part of it?
<@nielsenb:fedora.im>
13:51:27
But I think a lot like quality, we'd benefit more by casting a wide net with almost no barrier to entry. Once people have contributed once or twice, they might be more inclined to stick around. And even if they don't, at least it's still easy for the next person that walks by.
<@jflory7:fedora.im>
13:51:31
It is not fair just to discuss ideas and leave me, Peter, and Petr to do all of the work π
<@yukih:fedora.im>
13:51:50
I can help in documenting the tooling
<@jflory7:fedora.im>
13:51:52
If it is just us, then we will get our goals done in 2028 π€£
<@nielsenb:fedora.im>
13:51:55
I can probaly "do", one, the other, but not both
<@jflory7:fedora.im>
13:52:17
Awesome! That seems like where you are interested too.
<@jflory7:fedora.im>
13:52:26
Peter Boy (ServerWG, Docs): Have we moved the Fedora Docs Team docs to Forgejo yet?
<@nielsenb:fedora.im>
13:52:28
And I can't "do" hanging around in Matrix, it isn't compatible with my current on the go lifestyle. :D
<@jflory7:fedora.im>
13:52:42
Which ones?
<@jflory7:fedora.im>
13:52:53
You can with Element X now, zoooooooooooooooom π
<@pboy:fedora.im>
13:52:59
Hm, just notice, we haven't
<@nielsenb:fedora.im>
13:53:04
The two you just listed, which I guess now just means 2
<@nielsenb:fedora.im>
13:53:27
OH wait, I see that collapsed. I hate Matrix...
<@jflory7:fedora.im>
13:53:28
Peter Boy (ServerWG, Docs): Maybe this would be a good priority topic for you, me, and Petr to work on this month? WDYT? Is it worth writing an action for us to consider migrating this one?
<@nielsenb:fedora.im>
13:53:34
There was a 3 on the table. :D
<@jflory7:fedora.im>
13:54:11
Brandon Nielsen: You could possibly work with Yukih on the contributor guidance and tooling topics, or you could branch off on a different direction.
<@pboy:fedora.im>
13:54:18
Yeah, action is a good reminder
<@jflory7:fedora.im>
13:54:48
!action @jflory7 @pboy @pbokoc Migrate the Fedora Docs Team docs site from Pagure to Forgejo in January 2026 (ideally before FOSDEM)
<@nielsenb:fedora.im>
13:55:05
I guess either Justin Wheeler or Peter Boy (ServerWG, Docs) , where do you want docs states recorded?
<@yukih:fedora.im>
13:55:17
I can work with brandon on it
<@nielsenb:fedora.im>
13:55:17
Issues in the quick docs / main docs repository?
<@jflory7:fedora.im>
13:55:21
Docs states? What do you mean? Like review of content?
<@jflory7:fedora.im>
13:55:25
Aha
<@nielsenb:fedora.im>
13:55:37
That's what #2 was, no?
<@jflory7:fedora.im>
13:55:48
So, for me _personally_, I think writing an issue in the Quick Docs repo with a summary of the content, and where action is needed is a good first step.
<@jflory7:fedora.im>
13:55:58
Putting it there makes sure it will get moved to Forgejo when we import the repo over there later.
<@jflory7:fedora.im>
13:56:19
!info @yukih is interested in documenting the Fedora Docs tooling and working on the contributor guidance for authors.
<@jflory7:fedora.im>
13:56:28
Right.
<@jflory7:fedora.im>
13:58:15
Brandon Nielsen: Want me to write you an action item for a first analysis of Quick Docs? If yes, when is an appropriate deadline for you?
<@jflory7:fedora.im>
13:58:27
I notice we have two minutes remaining π
<@jflory7:fedora.im>
13:58:40
So much for open floor, heh! But I think this meeting has kind of been an "open floor" sort of meeting too
<@nielsenb:fedora.im>
13:59:00
I see an course of action is listed the agenda
<@nielsenb:fedora.im>
13:59:21
Just give me a "deadline", I'll hit it
<@jflory7:fedora.im>
13:59:25
Brandon Nielsen: Are you raising your hand? Should I make it official and give you homework? π
<@yukih:fedora.im>
13:59:31
Brandon Nielsen: Since you have experience in this, you can guide me on how i can write all these ok?
<@jflory7:fedora.im>
13:59:39
Brandon Nielsen: How about by the next Docs Team meeting in two weeks?
<@nielsenb:fedora.im>
13:59:59
Okay, it'll be the quickest of quick analysis.
<@jflory7:fedora.im>
14:00:13
And you two can also work together, Yukih and Brandon Nielsen, on the contributor tooling part. Best to chat in #docs:fedoraproject.org and others can follow along if they want.
<@nielsenb:fedora.im>
14:00:18
Is there some email reminder for those?
<@jflory7:fedora.im>
14:00:21
Brandon Nielsen: Quick is fine here!
<@jflory7:fedora.im>
14:00:30
Brandon Nielsen: There is not an email reminder but I will write a summary on Fedora Discussion.
<@jflory7:fedora.im>
14:00:40
OK, writing the action items, and then we need to yield our use of this channel!
<@jflory7:fedora.im>
14:00:48
I don't think someone is after us, but best to be prompt.
<@jflory7:fedora.im>
14:01:38
!action @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>
14:01:42
Alright, it is if official!
<@jflory7:fedora.im>
14:01:46
And I am yielding our channel!
<@jflory7:fedora.im>
14:01:53
Thanks so much everyone for your time and attention.
<@nielsenb:fedora.im>
14:01:54
I don't have much experience with writing guidance, but I'm happy to answer questions. I have some experience with the tooling. However, as mentioned, I don't linger on matrix, feel free to email nielsenb@jetfuse.net
<@jflory7:fedora.im>
14:02:04
We will see you around in the Fedora-verse! Until next time π
<@jflory7:fedora.im>
14:02:05
!endmeeting