Hello Pgnd,

I honestly do appreciate your point of view. Especially from a business owner standpoint. I do manage small business servers, and I feel you in that regard.

I do have to also applaud your nerves of steel though, using Fedora as a server in a business environment, to me anyway, always felt ill-advised as things tend to take rough 90 degree turns in Fedora which can often cause breakages in some server scenarios and stuff (The F40 mysql change comes to mind). That'S why most people I know that use Linux for server hosting tend to use a more 'stagnant' distro (i.e. Rocky, Alma, Debian, ...).

But I feel like I'm going off subject. I also think you are right, the KDE COPR-solution would work as long as it is documented somewhere. We could simply put it in the Fedora docs page, but also clearly note that those packages are not supported, but will be updated until the underlying frameworks (e.g. Xorg, or when the KDE foundation no longer supports Xorg, whichever comes first) are no longer available.

Le jeu. 1 févr. 2024, à 09 h 05, pgnd <pgnd@dev-mail.net> a écrit :
my non-technical, business-focused $0.02.

there's a great deal of reasonable discussion here.
there are technical & resource reasons for & against each change.

this very discussion sows confusion, particularly with F40 "just around the next corner".
nonetheless, it needs to be had.

the fact remains, Wayland functionality and X11 functionality are not at functional parity/equivalence.
and may never be.

to my cursory count, there are currently four constituencies in this discussion:

        Fesco/FedoraProject
        Fedora community
        Fedora KDE SIG
        KDE upstream

, each with varying degrees of pro- & con- X11-continued-support.

resources are limited.
at EACH of those constituencies. including end users' ...
and EACH has different priorities, with different weights.

'expectations of' any given constituency simply will not fly in community-driven work.

personally, i'm not at all in support of Fedora's wayland-only stance -- particularly as it's out-of-timeline-sync with KDE upstream's policy.

that said, Fedora already feels like it's fraying at the seams from lack of resource.
and for project health, if the project decision's been made to be wayland-only, then that should be a clean break.
any additional/continuing work should be allowed -- it's community -- but kept as separate as possible from official release.

i.e., rip the bandaid off, KISS, and don't dilute.

for me?
there's in-X11/not-yet-in-Wayland functionality that we've come to depend on.
loss of that functionality is a business cost, here.  planning, support, end-user sat, etc.
we've done our own math & risk assessment ... valid only for us, of course.

for many users, fedora/KDE COPR-based solutions will work. for awhile.
but for a fair number of others, we're pulling the plug and switching platforms.

that's not a criticism.  or a technical argument.
that's simply our ack of our current & forseeable business needs.
here.
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue