#meeting:fedoraproject.org log

<@jflory7:fedora.im>

13:11:04

!startmeeting Fedora Docs Team Meeting - 2026-02-24

<@meetbot:fedora.im>

13:11:05

Meeting started at 2026-02-24 13:11:04 UTC

<@meetbot:fedora.im>

13:11:05

The Meeting name is 'Fedora Docs Team Meeting - 2026-02-24'

<@jflory7:fedora.im>

13:11:08

!meetingname docs

<@meetbot:fedora.im>

13:11:09

The Meeting Name is now docs

<@hricky:fedora.im>

13:11:16

!hi

<@zodbot:fedora.im>

13:11:17

Hristo Marinov (hricky) - he / him / his

<@jflory7:fedora.im>

13:11:18

!topic Roll Call & Welcome's

<@jflory7:fedora.im>

13:11:19

!hi

<@zodbot:fedora.im>

13:11:20

Justin Wheeler (jflory7) - he / him / his

<@korora:fedora.im>

13:11:22

!hi

<@cstrauf:fedora.im>

13:11:22

!hi

<@zodbot:fedora.im>

13:11:23

Jocelyn Gould (korora) - she / her / hers

<@zodbot:fedora.im>

13:11:24

Christian Strauf (cstrauf)

<@theprogram:fedora.im>

13:11:24

!hi

<@nielsenb:fedora.im>

13:11:25

!hi

<@zodbot:fedora.im>

13:11:26

Mat H (theprogram)

<@zodbot:fedora.im>

13:11:27

Brandon Nielsen (nielsenb)

<@pg-tips:fedora.im>

13:11:28

!hi

<@jflory7:fedora.im>

13:11:28

Better late than never, I suppose 🙂

<@zodbot:fedora.im>

13:11:30

None (pg-tips)

<@smoliicek:fedora.im>

13:11:32

!hi

<@zodbot:fedora.im>

13:11:33

Vít Smolík (smoliicek) - he / him / his

<@jflory7:fedora.im>

13:11:41

Thanks folks for waiting out. We will get started quickly to make up for lost time!

<@jflory7:fedora.im>

13:12:23

!info Present: @jflory7, @korora, @cstrauf, @theprogram, @nielsenb, @pg-tips, @smoliicek, @pboy

<@jflory7:fedora.im>

13:12:34

Still quite a quorum today! 🙂

<@jflory7:fedora.im>

13:12:43

!topic Announcements & community news

<@jflory7:fedora.im>

13:12:48

Anyone have anything specific to share?

<@jflory7:fedora.im>

13:13:11

!info === "Save the Date: Fedora Council Video Meeting on 2026 Strategy Summit" ===

<@jflory7:fedora.im>

13:13:17

!link https://fedoramagazine.org/fedora-council-meeting-2026-strategy-summit/

<@jflory7:fedora.im>

13:13:33

!info Join the Fedora Council video meeting on Feb 25, 2026 for 2026 Strategy Summit outcomes and strategic direction with Fedora leadership.

<@pg-tips:fedora.im>

13:13:37

Justin Wheeler: 1400 UTC or 1500?

<@jflory7:fedora.im>

13:13:41

D'oh.

<@jflory7:fedora.im>

13:13:53

15:00 UTC.

<@jflory7:fedora.im>

13:14:58

Magazine post edited 🙂

<@jflory7:fedora.im>

13:15:06

Any other announcements that folks have?

<@jflory7:fedora.im>

13:15:11

Anything cool or interesting out there?

<@jflory7:fedora.im>

13:15:22

Peter Boy (ServerWG, Docs), Petr Bokoc: Should we say anything about Forgejo?

<@jflory7:fedora.im>

13:16:07

Brandon Nielsen: Do you have any quick updates on your quick-docs progress, or do you want to save it for the ticket discussion?

<@jflory7:fedora.im>

13:16:34

Jocelyn (she/her) (Server WG: Docs): Oh, and I should say welcome, since I think this is your first Fedora Docs Team meeting! 👋

<@pboy:fedora.im>

13:16:40

Regarding forge: There is a problem, but I don't know any details.

<@jflory7:fedora.im>

13:17:31

!info Some migrations are underway for Forgejo, but some of the more complex repos (e.g. Antora theme, docs website) have some bigger challenges. Not enough details known to report on right now.

<@jflory7:fedora.im>

13:18:03

OK, if nothing else, we can get to the agenda for today.

<@jflory7:fedora.im>

13:18:08

!topic Ad-hoc agenda triaging

<@jflory7:fedora.im>

13:18:24

So, Peter Boy (ServerWG, Docs) and I briefly caught up before this meeting, and wanted to focus most of the meeting on Quick Docs.

<@jflory7:fedora.im>

13:18:43

I also want to peek at our issue tracker, now that is getting operational, and use tickets to drive more of our meeting discussions.

<@jflory7:fedora.im>

13:18:59

!link https://forge.fedoraproject.org/docs/tickets

<@pboy:fedora.im>

13:19:48

Probably, specifically for today: https://forge.fedoraproject.org/docs/tickets/issues/1#issuecomment-544444

<@jflory7:fedora.im>

13:20:00

I was just seeing that.

<@jflory7:fedora.im>

13:20:16

Here is what I propose, optimistically. Unlikely we can cover them all, but we can try to cover as much as we can:

<@jflory7:fedora.im>

13:22:10

<@jflory7:fedora.im>

13:22:10

!proposed Agenda:

<@jflory7:fedora.im>

13:22:10

4. [Ticket #9](https://forge.fedoraproject.org/docs/tickets/issues/9): Consider using Vale as part of Docs workflow

<@jflory7:fedora.im>

13:22:10

3. [Ticket #6](https://forge.fedoraproject.org/docs/tickets/issues/6): Planning the expansion of the Docs homepage content

<@jflory7:fedora.im>

13:22:10

2. [Ticket #8](https://forge.fedoraproject.org/docs/tickets/issues/8): Creating a Beginner's Guide to Fedora

<@jflory7:fedora.im>

13:22:10

1. [Ticket #1](https://forge.fedoraproject.org/docs/tickets/issues/1): Improvement of the instructions for the Fedora Local Authoring System.

<@jflory7:fedora.im>

13:22:14

How does this sound?

<@jflory7:fedora.im>

13:22:56

I am seeing some thumbs 🙂

<@jflory7:fedora.im>

13:23:03

!agreed Tickets to cover for today, as time allows: Ticket #1, Ticket #8, Ticket #6, Ticket #9

<@jflory7:fedora.im>

13:23:15

!topic Ticket #1: Improvement of the instructions for the Fedora Local Authoring System

<@jflory7:fedora.im>

13:23:21

!link https://forge.fedoraproject.org/docs/tickets/issues/1

<@jflory7:fedora.im>

13:25:29

!info Peter proposed the following packages of work to group the content.

<@korora:fedora.im>

13:25:33

So as someone that is newish to docs work, I will say that the instruction in https://forge.fedoraproject.org/docs/tickets/issues/1 are sufficient. I did this when I started with the Server WG and started editing docs. The instructions work, but there is always room for improvement.

<@jflory7:fedora.im>

13:25:34

!info **Introductory page**: Update the tools section to focus on local authoring, leaving the other in the text, but marking as „not current“. Update explaining how to get a page from the icons on the documentation.

<@jflory7:fedora.im>

13:25:40

!info **Article, "Create a new documentation module"**: Update focusing on Local authoring, leaving the other parts in place with a warning "outdated"

<@jflory7:fedora.im>

13:25:46

!info **Contributing to Quick Docs**: Update with focus on Local authoring, Special Focus on Correct Meta Data

<@jflory7:fedora.im>

13:25:52

!info **Article: How to Create and Use a Local Fedora Documentation Workflow**: Update to describe in a compact way the basic workflow, Integrate Article (How to run a local preview)

<@nielsenb:fedora.im>

13:25:53

I didn't realize we signed commits.

<@jflory7:fedora.im>

13:25:57

!info **New: Article „Git for Writers“**: Starting with adjusting and improve „A Git cheat sheet For Server Documentation Authors“

<@jflory7:fedora.im>

13:26:04

GPG sign?

<@jflory7:fedora.im>

13:26:32

Jocelyn (she/her) (Server WG: Docs): You are referring to this page? https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-local-authoring-env/

<@nielsenb:fedora.im>

13:26:36

Yeah

<@jflory7:fedora.im>

13:26:36

!link https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-local-authoring-env/

<@jflory7:fedora.im>

13:26:55

I don't think we ever really mandate it as a standard. I don't think it hurts, but it is not required.

<@korora:fedora.im>

13:27:25

Uhh.... It's been a bit, but probably. (I have the setup of the local stuff scripted at this point)

<@cstrauf:fedora.im>

13:27:38

If the goal is to attract more people who'd like to contribute docs, the technical threshold is quite high.

<@jflory7:fedora.im>

13:27:46

OK. Just trying to figure out what the scope for this task might be.

<@nielsenb:fedora.im>

13:27:49

The documentation doesn't ever seem to cover actually using that signature

<@jflory7:fedora.im>

13:27:53

I am seeing some sub-issues, perhaps

<@jflory7:fedora.im>

13:28:09

Brandon Nielsen: I am not sure whether GPG signing docs commits are something worth explaining since it is so niche.

<@pboy:fedora.im>

13:28:34

And currently we don't sign.

<@jflory7:fedora.im>

13:28:35

Sub-issues, meaning some smaller tasks to execute this issue

<@pboy:fedora.im>

13:28:52

We have no infrastructure at docs for that.

<@jflory7:fedora.im>

13:29:39

Peter Boy (ServerWG, Docs): I am seeing each of those five work packages being its own issue, and someone could take up one of the individual tasks.

<@pboy:fedora.im>

13:29:47

Regarding the possible work packages: the idea is to make a rework plan first, before starting to write away.

<@jflory7:fedora.im>

13:29:49

We could also consider how we are using project boards and milestones for these things too…

<@jflory7:fedora.im>

13:30:33

!halp We need some help from the Docs Team to carry forward the local authoring content. Per the last discussion, we do not want to reinvent the wheel, but we can help guide new writers through our tools and help them understand our processes. Help wanted! 🙏

<@pboy:fedora.im>

13:30:36

Yes, in my view it describes 5 work pakcages, each worth a own (sub) issue.

<@jflory7:fedora.im>

13:30:57

Anyone here have an interest on taking any of these tasks on right now? Or have questions about what is in the issue?

<@jflory7:fedora.im>

13:31:01

!group member docs

<@zodbot:fedora.im>

13:31:01

● members <groupname> - Return a list of members of the specified group

<@zodbot:fedora.im>

13:31:01

● sponsors <groupname> - Return a list of owners of the specified group

<@zodbot:fedora.im>

13:31:01

● info <groupname> - Return a list of owners of the specified group

<@zodbot:fedora.im>

13:31:01

<@zodbot:fedora.im>

13:31:01

**Usage:** !group <subcommand> [...]

<@jflory7:fedora.im>

13:32:12

!group members docs

<@zodbot:fedora.im>

13:32:14

Members of docs: augenauf, copperi, Francois Andrieu, hank L, Stephen Snow, jflory7 (@jflory7:fedora.im, @fca:fedoraproject.org), Jean-Baptiste Holcroft, Kevin Fenzi, laubersm, Anushka Jain, Cornelius Emase, Mateus Rodrigues Costa, Matthew Miller, mjahoda, mpduty, Petr Bokoč, Peter Boy, P G, pmkovar, Christopher Klooz, sarkajana, sclark, Shaun McCance, Sumantro Mukherjee, x3mboy, Zach Oglesby

<@jflory7:fedora.im>

13:32:19

Grammar gets me once again 😛

<@theprogram:fedora.im>

13:32:30

Can we put the ask for help in the ticket, and then we can refer people to the ticket to pick up the assignments?

<@jflory7:fedora.im>

13:33:03

MatH: If nobody wants to jump in right now, sure. I was actually thinking of copying some of the issue labels that the CommOps team uses for Fedora Docs. I needed to start a bigger discussion first though, probably in a ticket 😛

<@jflory7:fedora.im>

13:33:19

In either case, it might be that this task needs to be divided up a bit more. Which is fine!

<@theprogram:fedora.im>

13:33:27

I think you can add the labels with minimal discussion.

<@jflory7:fedora.im>

13:33:34

Also, thinking of this… we should also think of a default issue template.

<@jflory7:fedora.im>

13:33:43

!halp We need a default issue template for our Forgejo tickets repo

<@jflory7:fedora.im>

13:34:45

!action @jflory7 Post an update in Ticket #1, explaining the meeting discussion and the context of where the discussion has gone so far

<@niknikovsky:fedora.im>

13:34:46

- Misc

<@niknikovsky:fedora.im>

13:34:46

Split it into:

<@niknikovsky:fedora.im>

13:34:46

- Issues and typos

<@niknikovsky:fedora.im>

13:34:46

- Suggestions

<@jflory7:fedora.im>

13:35:05

!action @jflory7 Create five sub-issues from Ticket #1, following @pboy's five work packages defined in #1

<@korora:fedora.im>

13:35:17

I can look for places where ticket 1 could be improved as someone who is just coming into the docs team

<@jflory7:fedora.im>

13:35:25

Once the five sub-issues are opened, would anyone be interested in volunteering to write a promo post on Fedora Discussion about the contribution?

<@jflory7:fedora.im>

13:35:37

Some extra visibility would be helpful to maybe wrangle in some new writers

<@jflory7:fedora.im>

13:35:50

I see my plate getting fuller 😅

<@jflory7:fedora.im>

13:36:09

This would be a nice thing for someone to help out with and make sure we are keeping Fedora Discussion peeps updated

<@theprogram:fedora.im>

13:36:47

Write it for the Magazine and cross post to discussion.

<@jflory7:fedora.im>

13:36:52

!halp Once the five sub-issues about the new author documentation for Fedora Docs are opened, share a callout post on Fedora Discussion to invite people to contribute and request mentoring on these tasks from experienced Fedora Docs Team members.

<@jflory7:fedora.im>

13:37:03

!halp Or a Magazine post, cross-posted to Fedora Discussion.

<@pg-tips:fedora.im>

13:37:51

and perhaps content input as well as mentoring? i.e. the writer needs to understand the core Docs team's decision on what the workflows should be

<@jflory7:fedora.im>

13:37:54

I have put a few "help wanted" tasks that we need to be successful on carrying out Ticket #1. I have taken on my share for what I can right now. Unless anyone has questions or wants to take up one of the `halp` tasks, we can move on!

<@theprogram:fedora.im>

13:38:00

I haven't had luck on discussion recruiting doc writers, they like the immediacy of the social elemnt of discussion.

<@theprogram:fedora.im>

13:38:00

But I do get a lot of people on Matrix and Join who would contribute.

<@cstrauf:fedora.im>

13:38:47

As a docs newbie the threshold that needs to be crossed to be able to contribute feels high. Even for people who are familiar with RCS etc.

<@jflory7:fedora.im>

13:38:57

MatH: I am a little curious what we could accomplish with carefully-marketed "good first issue" opportunities to contribute. I think offering some bite-sized tasks with the potential of receiving mentored guidance on contributing could be appealing to people who are looking for more technical docs opportunities. Traditionally, we are not very good at promoting ourselves.

<@jflory7:fedora.im>

13:39:21

Linking up with #marketing:fedoraproject.org is something I hope to do, like after a Fedora Magazine article is written

<@jflory7:fedora.im>

13:39:40

And technically, I am one of the people behind the Fedora LinkedIn page, so that could be an audience we have not yet tried to reach

<@cstrauf:fedora.im>

13:40:03

I don't think finding fields to contribute to are the problem. The onboarding into the "contribution machine" is.

<@theprogram:fedora.im>

13:40:09

I can write for promotional purposes, but social media is a real time sink and I do a lot each day already.

<@jflory7:fedora.im>

13:40:39

Christian Strauf: Totally hear you there. I think this is one of the biggest challenges in the Fedora community contributor ecosystem today. We have lots of arcane workflows for doing what we do in Fedora. They partially resemble the world Fedora came up in 23 years ago. Some parts of the contributor experience have modernized, but many have not.

<@pboy:fedora.im>

13:40:40

Christian Strauf: Maybe you can contribute to the local authoring article. If you are new to docs, your are perfect to make sure all relevant info gets included 😀

<@jflory7:fedora.im>

13:41:44

Christian Strauf: I am not sure if we can make the threshold much lower, but all ideas to improve the ease of access into the community is key. Many others have struggled with this same feeling and gotten stuck here. There is definitely room for improvement, and for those of us with a few years of experience, these papercuts can sometimes be harder and harder to see.

<@cstrauf:fedora.im>

13:41:49

Justin Wheeler There need to be mechanisms in place for issue tracking, revision management etc. But it feels a little overwhelming. Mentoring might be a good way.

<@theprogram:fedora.im>

13:42:08

I would like to see one social media channel done properly, rather than try three or four.

<@cstrauf:fedora.im>

13:42:26

Peter Boy (ServerWG, Docs) I still need to understand myself what I'm getting myself into but if I do, I'd be happy to contribute to an onboarding guide.

<@nielsenb:fedora.im>

13:42:30

"contribution machine" is such an excellent turn of phrase

<@jflory7:fedora.im>

13:42:37

!idea Better systems of organization and structure for issue tracking, revision management, etc. could be helpful

<@jflory7:fedora.im>

13:42:46

!idea Structured mentoring as a better way of inviting new contributors

<@theprogram:fedora.im>

13:42:57

Have a look first, and commit to it on the ticket

<@korora:fedora.im>

13:43:32

Is there still a web IDE for editing docs on the web? Meaning that one doesn't have to set up a local environment for contributing

<@jflory7:fedora.im>

13:44:19

!action @cstrauf Follow-up on Ticket #1 to follow along with the sub-issue split into five new issues for this project

<@jflory7:fedora.im>

13:44:33

Jocelyn (she/her) (Server WG: Docs): I actually haven't gone looking yet 😅

<@jflory7:fedora.im>

13:44:45

## 15 minute time check

<@korora:fedora.im>

13:44:46

i'll take a peek at that

<@jflory7:fedora.im>

13:44:56

In the interest of covering other topics, let's proceed to the next agenda topic.

<@jflory7:fedora.im>

13:45:15

!topic Ticket #8: Creating a Beginner's Guide to Fedora

<@jflory7:fedora.im>

13:45:17

!link https://forge.fedoraproject.org/docs/tickets/issues/8

<@jflory7:fedora.im>

13:45:29

Christian Strauf, MatH: I think this one is all y'all 🙂

<@cstrauf:fedora.im>

13:45:42

Please find the first draft here: https://cryptpad.fr/code/#/2/code/view/te8J4lq0fdMQKDs10Fh6E8BsbtGoWeMMt1hiAPh4nOA/present/

<@nielsenb:fedora.im>

13:45:52

Interest in *using* Fedora, or *contributing*?

<@cstrauf:fedora.im>

13:45:58

Using

<@theprogram:fedora.im>

13:46:21

Its a bit long to read in 2 mins, it details to someone that can use WIn or Mac how to install and get comfortable with Fedora KDE

<@theprogram:fedora.im>

13:46:37

We chose KDE because Christian uses it, not becasue it is better or right

<@theprogram:fedora.im>

13:46:56

We have focussed on 'open' solutions, including Mozilla dn libre office.

<@cstrauf:fedora.im>

13:47:12

Additionally, I've had many Linux newbies recently who felt more at home ad hoc on Fedora KDE when coming from other systems.

<@theprogram:fedora.im>

13:47:37

we include how to get going, and link out to other authoritative sources (such as mozilla or libre office)

<@theprogram:fedora.im>

13:47:51

There is a section for installing widel used software,

<@theprogram:fedora.im>

13:48:04

and the Doc ends with some 'advanced' topics like using the command line

<@cstrauf:fedora.im>

13:48:07

In terms of writing style the focus is to be very personal, encouraging, not to use difficult or "in crowd" terminology.

<@pboy:fedora.im>

13:48:22

MatH: I proposed to write such a guide to the KDE working group. Unfortunately, nobody jumped in. We need to cooordinate such a guide with the working group, who is responsible for the "product"

<@jflory7:fedora.im>

13:48:39

I am having a feeling of deja vu

<@cstrauf:fedora.im>

13:48:50

Additionally, one of the main paradigms was not to produce dupe docs.

<@jflory7:fedora.im>

13:48:50

Remember when we used to do more user support on the users@lists.fp.o mailing list?

<@theprogram:fedora.im>

13:48:53

Peter Boy (ServerWG, Docs) it does not really do a deep dive into KDE

<@jflory7:fedora.im>

13:49:01

And the old Ask Fedora, before it was on Fedora Discussion?

<@theprogram:fedora.im>

13:49:26

I see the 'product' as a beginners guide, not a KDE document

<@jflory7:fedora.im>

13:49:29

I am not sure if we have something like… a "Fedora Users SIG"

<@jflory7:fedora.im>

13:50:06

Because when we get into covering specific desktops, the support matrix for Fedora end-user experiences is hard. (This is one reason why having two default desktop Editions is hard, but I digress for this meeting.)

<@cstrauf:fedora.im>

13:50:07

The main point is: how do you get absolute beginners kickstarted with a self-help document which is a root document that links to further odcs.

<@cstrauf:fedora.im>

13:50:18

The main point is: how do you get absolute beginners kickstarted with a self-help document which is a root document that links to further docs.

<@cstrauf:fedora.im>

13:50:39

Very important: the document is **not** very KDE specific.

<@jflory7:fedora.im>

13:50:42

When I see content covering a specific desktop, I want to encourage collaboration with the subject-matter experts in Fedora, which would be the packagers and community behind delivering that Edition into Fedora

<@jflory7:fedora.im>

13:51:01

But we never really had a Fedora Users support knowledge-base

<@jflory7:fedora.im>

13:51:30

I think this could be a really excellent way of finding a home for this sort of content, and also be a potential rally in our various support channels online around the world, in various different apps and services

<@pboy:fedora.im>

13:51:30

MatH: I suppose you know the "Beginners Guide" which I proposed?

<@pg-tips:fedora.im>

13:51:35

I'd be very interested in a SIG focusing on supporting users (including but not limited to newcomers)

<@cstrauf:fedora.im>

13:51:47

I saw it as well.

<@jflory7:fedora.im>

13:51:56

For example, I used to run a Fedora Telegram user support group, and having some general stuff like this would have been great to lean on for end-user support, like a Users best practices guide

<@theprogram:fedora.im>

13:52:04

Yes, I have read the 2018 guide cover to cover, and we could replace that with this (if you thought it was suitable)

<@jflory7:fedora.im>

13:52:36

I wonder if the Docs Team could help spin up a new "sub-team" focused on Fedora user experience and support.

<@pboy:fedora.im>

13:52:45

MatH: yes, I think so.

<@theprogram:fedora.im>

13:52:50

Our 2026 guide is more specific on steps to take, but covers some more specific ground such as more command to get beginners outputs

<@theprogram:fedora.im>

13:53:15

We can make it printable, I used to make a lot of 'zines' so I can co-ordinate that

<@cstrauf:fedora.im>

13:53:21

I also have a few beginners in my surroundings which I would test the guide on. :)

<@theprogram:fedora.im>

13:53:51

no, we have too much work already - leave this guide to Christian and myself for the next two years

<@jflory7:fedora.im>

13:54:21

Two years? 😅

<@theprogram:fedora.im>

13:54:33

You want me to commit into my 70!

<@theprogram:fedora.im>

13:54:40

You want me to commit into my 70s!

<@jflory7:fedora.im>

13:54:58

Hahah, I meant I would hope we could find some sort of MVP and open up contribution opportunities as we go

<@theprogram:fedora.im>

13:54:59

/ j

<@theprogram:fedora.im>

13:55:20

Later - docs has too much work now and we support people in fedora discussion already

<@theprogram:fedora.im>

13:55:23

I do a lot of that

<@jflory7:fedora.im>

13:55:24

The truth is, we do not have a clear home for user-focused content

<@theprogram:fedora.im>

13:55:45

We can make a page / area, but lets not start a new group

<@cstrauf:fedora.im>

13:55:46

A guide is a doc per definition.

<@jflory7:fedora.im>

13:55:54

In this use case MatH, I would want the Ask Fedora folks to feel empowered to contribute to these user experience docs, to help save time with repeated support cases.

<@theprogram:fedora.im>

13:55:57

as does PG

<@pboy:fedora.im>

13:56:00

User docs?

<@pboy:fedora.im>

13:56:00

> The truth is, we do not have a clear home for user-focused content

<@pboy:fedora.im>

13:56:00

<@pg-tips:fedora.im>

13:56:03

yeah, I think there's a docs aspect to this area, but not *only* a docs aspect

<@theprogram:fedora.im>

13:56:03

And Hristo

<@jflory7:fedora.im>

13:57:10

In Antora speak, I think we would call this a new Antora component, with its own module(s). The component would be docs.fp.o/ `users` and we could create different modules to organize the content.

<@jflory7:fedora.im>

13:57:26

Modules can be `ROOT` but they can also be more specific and diverse

<@jflory7:fedora.im>

13:57:32

And we don't need to make a new sub-team to do that

<@jflory7:fedora.im>

13:57:47

But we do need someone to help own it and be accountable to watching the issue tracker for the site

<@theprogram:fedora.im>

13:57:51

Sounds reasonable, should be put this into the ticket is everyone is roughly okay with the tone and direction of the content we produced?

<@jflory7:fedora.im>

13:57:54

I imagine it might overlap a lot with Quick Docs

<@cstrauf:fedora.im>

13:58:07

My main question would be these: (a) would the docs SIG members say that the beginner's guide is something that we should develop further and (b) if yes: is the style, scope and content ok so that we can refine it.

<@jflory7:fedora.im>

13:58:12

MatH: Are you good with taking an action item to summarize this discussion in the ticket?

<@pg-tips:fedora.im>

13:58:21

yes! got some lower-level suggestions, but we can chat about that separately

<@cstrauf:fedora.im>

13:58:22

Ah! MatH was quicker. :)

<@theprogram:fedora.im>

13:58:40

I disagree, quickdocs is really technical, and personally I would propose merging 'quickdocs' with 'docs' at some point but I don't want to waste cycles on that today

<@jflory7:fedora.im>

13:58:45

Christian Strauf: The beginner's guide is probably an easier bite to chew on. The user docs thing is actually quite a huge topic.

<@theprogram:fedora.im>

13:58:52

Yes

<@cstrauf:fedora.im>

13:59:09

I don't think so either.

<@cstrauf:fedora.im>

13:59:21

If at all it references Quick Docs.

<@jflory7:fedora.im>

13:59:34

!action @theprogram Share a summary of meeting discussion in today's Docs Team meeting into Ticket #8 to help rally a path forward on publishing the beginner's guide

<@jflory7:fedora.im>

13:59:40

!topic Open floor

<@pboy:fedora.im>

13:59:45

And it may overlap with " AskFedora"

<@jflory7:fedora.im>

14:00:08

!info We ran out of time to discuss Ticket #6 and Ticket #9. Docs Team members are encouraged to review these tickets asynchronously.

<@theprogram:fedora.im>

14:00:20

I think that awesome team can be a big part of the solution.

<@jflory7:fedora.im>

14:00:35

OK folks, we are out of time for today!

<@jflory7:fedora.im>

14:00:42

Another packed meeting, and some big ideas covered too

<@jflory7:fedora.im>

14:00:47

Let's keep the conversation going!

<@jflory7:fedora.im>

14:00:53

I will share a summary on Fedora Discussion per the norm

<@jflory7:fedora.im>

14:01:11

!action @jflory7 Publish a post-meeting summary on the #docs tag on Fedora Discussion after the meeting

<@jflory7:fedora.im>

14:01:15

THanks folks for being here!

<@jflory7:fedora.im>

14:01:18

See ya next time 👋

<@jflory7:fedora.im>

14:01:21

🌊

<@jflory7:fedora.im>

14:01:23

!endmeeting