<@hricky:fedora.im>
13:09:44
!startmeeting Fedora Docs Team Meeting - 2026-05-19
<@meetbot:fedora.im>
13:09:44
Meeting started at 2026-05-19 13:09:44 UTC
<@meetbot:fedora.im>
13:09:44
The Meeting name is 'Fedora Docs Team Meeting - 2026-05-19'
<@hricky:fedora.im>
13:10:03
!meetingname docs
<@meetbot:fedora.im>
13:10:04
The Meeting Name is now docs
<@theprogram:fedora.im>
13:10:05
I like your future thinking ways re docs tags. That could work will into Michael WInters Fedora Data Working Group
<@theprogram:fedora.im>
13:10:12
!hi
<@zodbot:fedora.im>
13:10:13
MatH: Mat H (theprogram)
<@hricky:fedora.im>
13:10:27
!topic Intros, welcomes, hellos
<@korora:fedora.im>
13:10:27
!hi
<@zodbot:fedora.im>
13:10:28
Jocelyn Gould (UTC-4): Jocelyn Gould (korora) - she / her / hers
<@egret:fedora.im>
13:10:36
!hi
<@theprogram:fedora.im>
13:10:36
!hi
<@jonashub:fedora.im>
13:10:37
!hi
<@zodbot:fedora.im>
13:10:37
Eli Ridge: Eli Ridge (egret)
<@zodbot:fedora.im>
13:10:38
MatH: Mat H (theprogram)
<@zodbot:fedora.im>
13:10:39
Jonas Hubeny: Jonáš Hubený (jonashub) - he / him / his
<@hricky:fedora.im>
13:10:48
!info Welcome to another Fedora Docs Team meeting! If you are present and intend to follow along with today's meeting, please identify yourself by typing `!hi` in the chat.
<@a-moor:fedora.im>
13:10:59
!hi
<@zodbot:fedora.im>
13:11:04
Andreas Moor: Andreas Moor (a-moor)
<@hricky:fedora.im>
13:11:40
!hi
<@zodbot:fedora.im>
13:11:53
Hristo Marinov: Hristo Marinov (hricky) - he / him / his
<@a-moor:fedora.im>
13:12:39
I thought it might fit in the concept of a Docs Team Strategy, the team talked the last time.
<@theprogram:fedora.im>
13:13:34
lets see if this on todays agenda, and if not, chat in channel about it after
<@hricky:fedora.im>
13:14:33
Do we have an agenda for today?
<@jflory7:fedora.im>
13:14:52
!hi
<@zodbot:fedora.im>
13:14:53
Justin Wheeler (away until 2026-05-19): Justin Wheeler (jflory7) - he / him / his
<@jflory7:fedora.im>
13:15:04
I'm half here, still working on Flock stuff
<@jflory7:fedora.im>
13:15:27
[@pbokoc:fedora.im](https://matrix.to/#/@pbokoc:fedora.im) usually has an agenda prepped but not sure if it was ready for today
<@jflory7:fedora.im>
13:16:00
Petr and I met last week, didn't get to catch up with [@pboy:fedora.im](https://matrix.to/#/@pboy:fedora.im), but I know some of the focus right now is on the Flock workshop and talk. I know that's not everyone though.
<@jflory7:fedora.im>
13:16:23
The project board might be a good place to follow
<@jflory7:fedora.im>
13:16:42
https://forge.fedoraproject.org/docs/-/projects/448
<@jflory7:fedora.im>
13:16:47
!link https://forge.fedoraproject.org/docs/-/projects/448
<@theprogram:fedora.im>
13:17:02
I think it could work in a broader strategy, it's certianly not wrong, but does it complicate things or give extra work we don't need?
<@jflory7:fedora.im>
13:17:16
https://forge.fedoraproject.org/docs/tickets/issues/19
<@jflory7:fedora.im>
13:17:25
https://forge.fedoraproject.org/docs/tickets/issues/22
<@jflory7:fedora.im>
13:17:34
These seem like the only two triaged tickets
<@theprogram:fedora.im>
13:17:58
And how about https://forge.fedoraproject.org/docs/tickets/issues/40
<@egret:fedora.im>
13:18:01
https://forge.fedoraproject.org/docs/tickets/projects/333
<@egret:fedora.im>
13:18:01
Also this:
<@egret:fedora.im>
13:20:11
Who can do the Stg branches?
<@hricky:fedora.im>
13:20:18
! topic [Repo alignment] Fix labels
<@egret:fedora.im>
13:20:21
I would volunteer but i dont know what i am doing
<@hricky:fedora.im>
13:20:25
!topic \[Repo alignment\] Fix labels
<@jflory7:fedora.im>
13:20:31
Ah, I wish issues could be assigned to multiple Projects at once!
<@hricky:fedora.im>
13:21:09
! link https://forge.fedoraproject.org/docs/tickets/issues/40
<@hricky:fedora.im>
13:21:20
!link https://forge.fedoraproject.org/docs/tickets/issues/40
<@a-moor:fedora.im>
13:22:50
I think this is a good question which could be labeled as "/status/needs decussion". Since I'm new to contributing, I don't have any experience in the Docs Team workflows and see my proposal more as an invitation.
<@jflory7:fedora.im>
13:23:13
I glanced at the proposed labels and I really liked what I saw
<@a-moor:fedora.im>
13:23:43
I think this is a good question which could be labeled as "/status/needs descussion". Since I'm new to contributing, I don't have any experience in the Docs Team workflows and see my proposal more as an invitation.
<@jflory7:fedora.im>
13:23:54
My only feedback was that there are too many statuses, either some could be removed or grouped with another exclusive label set. But I think if there are too many labels, there is the risk that people do not use them
<@theprogram:fedora.im>
13:24:35
Peter came back and trimmed it a little,
<@theprogram:fedora.im>
13:24:35
Andreas has made a great and well structured list.
<@theprogram:fedora.im>
13:24:35
And now Adreas has clarified that a certain structure would allow ffor better issue tracking and data extraction over time.
<@jflory7:fedora.im>
13:24:51
Oh, oops, I missed the very latest comments
<@a-moor:fedora.im>
13:25:40
Hey Justin Wheeler (away until 2026-05-19) , yeah the last comment came 1 hour ago. Sorry for that.
<@jflory7:fedora.im>
13:25:45
[@a-moor:fedora.im](https://matrix.to/#/@a-moor:fedora.im) BTW, great work on this, I know it is mostly discussion but I think your proposal of labels is helping drive things forward with a concrete proposal. The hardest part is always a first draft 😛
<@jflory7:fedora.im>
13:25:57
Heheh all good. As my display name indicates, I'm still catching up!!
<@jflory7:fedora.im>
13:27:02
I think we should be cautious about overcomplicating things. Structure is good, data extraction is good, but in order for the value to be made from those, we have to have a system that is uniformly followed
<@korora:fedora.im>
13:27:08
I mena, you can't edit a blank page
<@korora:fedora.im>
13:27:19
I mean, you can't edit a blank page
<@jflory7:fedora.im>
13:27:22
Starting with something more simple, getting the team buy-in, and then iterating is always a solid approach
<@theprogram:fedora.im>
13:27:43
This is my feeling. We need to keep streamlined and headed in a solid direction rather than making extra work.
<@theprogram:fedora.im>
13:28:09
Data extraction is good, but we are a small team.
<@jflory7:fedora.im>
13:28:35
I'd be in favor of dropping "size" for "effort"
<@jflory7:fedora.im>
13:29:12
Speaking from experience, I had the same ideas of data extraction with my label set, but I realized that the data only works if everyone is aligned on the labels, their meaning, and intended use!
<@jflory7:fedora.im>
13:30:09
"good first issue" is a standard team for open source, so worth keeping one way or another. We used to have scripts that collected all of the GFIs from various repos across Fedora and display them uniformly in one place
<@jflory7:fedora.im>
13:30:17
"good first issue" is a standard term for open source, so worth keeping one way or another. We used to have scripts that collected all of the GFIs from various repos across Fedora and display them uniformly in one place
<@a-moor:fedora.im>
13:30:19
I think keeping the possibility of using timestamps and labels in mind for the usage of evaluating the issue pipeline was the whole point I was trying to make. 👍️
<@jflory7:fedora.im>
13:31:02
For sure! It's the right idea. I think we can try to figure out some of the efficiency of the pipeline as we go too. Getting more organized will help us get better at this
<@korora:fedora.im>
13:31:24
My thought is we have to have something to start with and we can adapt it as we go
<@theprogram:fedora.im>
13:32:28
It is worth gett the issue list up this week, and not overthinking it. One or two isseues here or there are not confusing.
<@a-moor:fedora.im>
13:32:36
I guess this is what the discussion in the team is for. Make clear what is worth the extra work and whether the value is worth it to push things further.
<@jflory7:fedora.im>
13:32:36
[@a-moor:fedora.im](https://matrix.to/#/@a-moor:fedora.im) Also, I think we could use other tools to accomplish the goals you have for indicating state, i.e. a project board with columns that indicate progress or review
<@jflory7:fedora.im>
13:33:11
Not necessarily all of these things have to be tracked as labels, but we may be able to use other tools like projects and milestones for similar effects, and avoid too many labels
<@a-moor:fedora.im>
13:34:09
Totally agree! Adapting on the go if specific insights are needed.
<@korora:fedora.im>
13:34:53
are the labels more for 'interal' use once it's decided that an issue is something we need to foucs attention on?
<@theprogram:fedora.im>
13:35:04
So I think then the proposal is to go with Petr's trimmed list, and add to it if necessary?
<@jflory7:fedora.im>
13:35:07
Looking at the list in Petr's comment, I would be happy dropping "size" labels and adding a code label back to the types
<@jflory7:fedora.im>
13:35:38
Good question. More for internal use by the core Docs Team, since only repos under the Docs org on Forge will pick up these labels
<@theprogram:fedora.im>
13:35:54
All the labels are for internal use only as far as I can tell
<@jflory7:fedora.im>
13:35:56
For instance, other teams, SIGs, and WGs with docs won't have these labels
<@korora:fedora.im>
13:36:24
+1
<@jflory7:fedora.im>
13:36:33
+1 with dropping "size" and adding the code label back as Andreas suggested
<@theprogram:fedora.im>
13:36:54
+1 lets get it done
<@jflory7:fedora.im>
13:37:05
Ah I'm off hold on the phone, BRB
<@jflory7:fedora.im>
13:37:15
Would be great to make notes in meeting minutes
<@jflory7:fedora.im>
13:37:18
BRB
<@theprogram:fedora.im>
13:37:24
Shall we move to the next topic in 1 min then?
<@theprogram:fedora.im>
13:37:44
Whats the bot command to record that decision?
<@korora:fedora.im>
13:38:03
I think it's ! agreed
<@hricky:fedora.im>
13:38:21
!agreed Dropping "size" and adding the code label back
<@egret:fedora.im>
13:39:24
is the the stg item next?
<@cstrauf:fedora.im>
13:39:27
!hi
<@zodbot:fedora.im>
13:39:33
Christian Strauf: Christian Strauf (cstrauf)
<@cstrauf:fedora.im>
13:39:35
Sorry, very late to the party.
<@theprogram:fedora.im>
13:39:46
https://forge.fedoraproject.org/docs/tickets/projects/333 ?
<@egret:fedora.im>
13:39:47
is it the stg item next?
<@korora:fedora.im>
13:40:15
It's ok, we're fumbling our way through it and stilll getting stuff done.
<@egret:fedora.im>
13:40:32
This one is a bit of a slow cook this one but getting there
<@pbokoc:fedora.im>
13:40:44
Ahhhh, sorry everyone
<@theprogram:fedora.im>
13:40:44
Eli you wanna say what you need to get published?
<@egret:fedora.im>
13:41:13
PR just opened on the local workflow
<@egret:fedora.im>
13:41:44
That can just get review in due course
<@egret:fedora.im>
13:41:56
but hopefully it is basically ready
<@egret:fedora.im>
13:42:12
Thanks to Jocelyn for the help on that one
<@theprogram:fedora.im>
13:42:16
I read it the other day and looks good to go
<@egret:fedora.im>
13:42:40
Next will be the intro page and then the git Writers Fedora one
<@theprogram:fedora.im>
13:43:28
Is a git for writers any different than the local workflow you did? Are we making to many copies of the same thing?
<@egret:fedora.im>
13:43:46
Yeah it will be quiet different
<@egret:fedora.im>
13:43:58
Yeah it will be quite different
<@korora:fedora.im>
13:44:26
it's possible that there will be some overlap, but I think the git for writers is going to be a little more indepth on what git is/how it works/ why we should use it
<@egret:fedora.im>
13:44:28
the local workflow only covers the most basic of git scenarios
<@cstrauf:fedora.im>
13:45:28
Would it make sense to consolidate local workflow git and the git for writers doc into one? Create a "basics" part and an "in-depth" part in the same doc?
<@theprogram:fedora.im>
13:45:53
Nah, I say just do that in the menu structure
<@cstrauf:fedora.im>
13:45:57
And basically link to it from local workflow doc so that only one git guide needs to be maintained?
<@cstrauf:fedora.im>
13:46:14
Or that.
<@a-moor:fedora.im>
13:46:28
Would be "Git + Forgejo Intro" be a good combo too?
<@a-moor:fedora.im>
13:46:43
Wouldn't be "Git + Forgejo Intro" be a good combo too?
<@korora:fedora.im>
13:46:58
I think combinging it in one doc could be overwehelming for those who have never used the.... wonder that is git
<@theprogram:fedora.im>
13:47:08
Similarly, I would recommend to keep each page as short as possible and address the conenctions to each other through a menu structure
<@korora:fedora.im>
13:47:23
i've used git for a while and there are things I still learn about it on the regular
<@korora:fedora.im>
13:47:52
We could set it up as a sries of interconnected docs depending on what the users goals ar3e
<@korora:fedora.im>
13:47:55
We could set it up as a sries of interconnected docs depending on what the users goals are
<@cstrauf:fedora.im>
13:48:23
KISS principle is always good.
<@korora:fedora.im>
13:48:57
For a lot of people the basics are going to be the most that they are going to need
<@egret:fedora.im>
13:49:14
Another idea is the git for writers could lean into a reference style, with the design choice of "what i want to achieve" > "the command"
<@egret:fedora.im>
13:49:26
and list them all out
<@cstrauf:fedora.im>
13:49:29
In the beginner's guide we simply moved all advanced stuff to a separate section.
<@cstrauf:fedora.im>
13:49:40
Linked from the left-hand index.
<@cstrauf:fedora.im>
13:49:54
That way we could keep sections mostly short and sweet.
<@theprogram:fedora.im>
13:50:13
No, it complicated things again. Simple pages, people will figure out what they need from the titles.
<@korora:fedora.im>
13:50:30
I think we should treat the 'getting started with docs" thing similarly
<@theprogram:fedora.im>
13:52:14
agreed review Local Workflow Article, keep related pages simple, and connected by a clear menu structure
<@theprogram:fedora.im>
13:52:15
?
<@korora:fedora.im>
13:52:33
<@korora:fedora.im>
13:52:33
In the past when I've been the user of the docs, I prefer that each section deal with a specific topic.
<@korora:fedora.im>
13:52:33
We can aleays link to other pages as needed
<@korora:fedora.im>
13:52:41
+1
<@theprogram:fedora.im>
13:52:51
!agreed review Local Workflow Article, keep related pages simple, and connected by a clear menu structure
<@theprogram:fedora.im>
13:53:00
Next topic?
<@hricky:fedora.im>
13:53:42
There is only few minutes left, so we can do a quick open floor.
<@korora:fedora.im>
13:54:05
I literaly just thought this...
<@hricky:fedora.im>
13:54:33
!topic open floor
<@hricky:fedora.im>
13:55:45
There are only few minutes left, so we can do a quick open floor.
<@jonashub:fedora.im>
13:55:51
Just wanted to add - for the Git for contributors guide, "Learn Git Branching": https://learngitbranching.js.org/ could be a great resource to include. It visualizes commits as a tree structure, so contributors can clearly see how branches split off and how merges work, rather than just reading about it. Could be a handy reference especially for those new to Git.
<@theprogram:fedora.im>
13:56:27
Lets publish first, and put that in as a PR at a later date
<@hricky:fedora.im>
13:56:28
There are only a few minutes left, so we can do a quick open floor.
<@theprogram:fedora.im>
13:57:01
Or even as a seperate menu item
<@korora:fedora.im>
13:57:03
Jonas, can you throw that in the tracking ticket for https://forge.fedoraproject.org/docs/tickets/issues/15
<@korora:fedora.im>
13:57:11
Just so we don't lose it?
<@jflory7:fedora.im>
13:57:21
Thanks [@hricky:fedora.im](https://matrix.to/#/@hricky:fedora.im) for helping man the Meetbot, and thanks to all of you for helping drive the discussion today!
<@jflory7:fedora.im>
13:57:35
Sorry it was a little chaotic on my side 😕
<@jflory7:fedora.im>
13:57:56
+1
<@jonashub:fedora.im>
13:58:42
Sure, I'll add it!👍️
<@hricky:fedora.im>
13:58:44
(Just a note that this meeting needs to conclude in a minute or so)
<@korora:fedora.im>
13:58:56
Thank you!
<@theprogram:fedora.im>
13:59:07
Lets keep chatting in channel later if anybody wants
<@jflory7:fedora.im>
13:59:09
June 2nd is our next scheduled meeting, I think
<@theprogram:fedora.im>
13:59:17
Thanks for a productive meeting all
<@jflory7:fedora.im>
13:59:21
We might want to figure out the meeting cadence with Flock around the corner
<@jflory7:fedora.im>
13:59:25
But we can do that in channel
<@jflory7:fedora.im>
13:59:34
Thanks folks for being engaged and driving the discussion!
<@jflory7:fedora.im>
13:59:42
See ya next time 👋🏻
<@jflory7:fedora.im>
13:59:49
[@hricky:fedora.im](https://matrix.to/#/@hricky:fedora.im)++ for chairing
<@zodbot:fedora.im>
13:59:50
jflory7 gave a cookie to hricky. They now have 19 cookies, 1 of which were obtained in the Fedora 44 release cycle
<@hricky:fedora.im>
14:00:32
!endmeeting