On Mon, Feb 24, 2020 at 11:11 AM Kamil Páral <kparal@fedoraproject.org> wrote:
> I am opposed to this, as it is means Fedora is more likely to ship with
> broken KDE applications.

Hello, I have been doing the KDE "all applications must work" test for more than two years already and I can
tell you, that some of the KDE pre-installed applications are of low quality, if not broken already. Last time I checked, there were over 60 applications listed in Menu where there are like 30 in Gnome. Some applications (browsers) are tripled, some are doubled. Others are connected with a certain use case, e.g. converting one data format into another, therefore useless for people without that use case.

If "all applications" must work, than I need to start every application and test the "basic functionality". Nowhere is written exactly, what basic functionality is, so I must test what I think needs to be tested "in bona fide." Many KDE applications generally work, but they have flaws in some parts that can or do not need to be basic functionality, depending on opinions.

In case of a reported bug, the readiness of KDE developers to fix it usually is lower when compared to Gnome, so sometimes there are bugs that will never be fixed, because they are not as severe as to block the release completely, so they get ship over and over again.

The proposal could actually improve the situation, because important apps would be tested thoroughly and not just for the basic functionality. We do not want to order which applications that should be, I think the SIGs should create a list of such applications. What the proposal says is just a generic example of applications that "make sense" on a desktop system.

We lack help on testing desktops and we probably would not want to solve this, if there were plenty of community members doing the applications tests and reporting to the matrices. In the past, there were moments when we had to retest a new compose like
12 hours prior to the releas readiness meeting and we had to assign one person to work on KDE applications only for half the time.

Have a nice day, Kevin.

Even the core ones if the KDE Spin keeps also
> shipping, e.g., Firefox (something I think should just stop, but that is not
> my decision to make), since your proposal only requires ANY browser on the
> Spin to work. I do not think it is acceptable to ship a Fedora KDE release
> with a broken Falkon.

The responsiveness to KDE related bugs is much lower (when compared to Gnome), so even if a bug is reported, it will not get fixed so easily, or possibly ever. 


Out of curiosity, would you be willing to contribute in release validation testing and cover the apps which are not part of the proposal, in order to keep the "all apps must work" criterion for the KDE spin? I'm not sure it is the right solution, but I'm interested in hearing your thoughts.
kde mailing list -- kde@lists.fedoraproject.org
To unsubscribe send an email to kde-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/kde@lists.fedoraproject.org


Lukáš Růžička


Red Hat

Purkyňova 115

612 45 Brno - Královo Pole