On Wed, 2024-05-29 at 15:36 -0500, John Himpel wrote:

The Release Management folks have assigned (volunteered) Patrik Polakovic to serve as our guide for the process of renaming our various distribution media.

I am virtually unavailable the next two weeks.  If anyone has time to contact Patrik and begin the learning process, please feel free to go ahead.

John

Sent from my iPhone

---

server mailing list -- server@lists.fedoraproject.org To unsubscribe send an email to server-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

I am forwarding an email from Kevin Fenzi of the Release Management team. It is his response to the issue found at: https://pagure.io/releng/issue/12098

On Fri, May 10, 2024 at 10:16:55AM GMT, John W. Himpel wrote:

The Fedora Server WG is seriously contemplating changing the naming convention for its distribution media.

yeah.

We have developed a naming convention that we would like to follow. It can be found at: https://pagure.io/fedora-server/issue/126

ok. I have tried to sort of follow it, but haven't dug in deep yet.

As we began our research in preparation of s system-wide change proposal, we discovered two things:

1. The current naming convention has it's tentacles far and wide

thought the distribution generation processes, distribution processes and documentation.

yes, renaming things is _HARD_. It requires changes to compose configurations, and in some cases changes to compose tooling if they don't support the name you want to use. It needs changes not only there, but in compose scripts, then in QA stuff, then in tools that look for images, then in websites to point to the right names and finally... users will have to adjust any tooling they have to download/test/consume things.

It's gonna be a long road. ;)

2. The Fedora Server WG recognizes quite clearly that "we don't know

what we don't know".

Thats true for everyone. ;)

We are hopeful the Release Engineering team will assist in the early stages of acquiring the necessary knowledge to develop a cogent and complete system-wide change. Firstly, we need help in identifying

all

the areas within Fedora Project that would require change. Secondly, we need help in developing a detailed statement of work for each of

the

areas requiring change.

We can try, but releng is pretty overloaded/doesn't have too many spare resources.

Off the top of my head, places needing changes:

* pungi config/tool * kiwi config/tool * possibly lorax/pylorax * Releng compose sync scripting * fedfind (QE) * openqa / fedora-ci changes * websites * documentation/release notes

We would greatly appreciate if the Release Engineering team would assign someone from the team to work with us and serve a "guide" for

us

as we attempt to complete the two above objectives.

I have been appointed as the point of contact for this effort.

We look forward to engaging with the Release Engineering team for

this

effort.

We can discuss it in our next weekly meeting and see if we can see someone who can help.

kevin

This should give some idea of the scope of this change. I think at best we are looking at F42.

John