Just to start this conversation up again, is there already a link to the current accepted blocking list somewhere?

https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#Default_application_functionality
https://fedoraproject.org/wiki/Basic_Release_Criteria#Required_applications

Here is my guess based on the above links:

• web browser: firefox
• file manager: dolphin
• package manager: discover, dnf (?)
• image viewer: gwenview
• document viewer: okular, libreoffice
• text editor: kate
• archive manager: ark
• terminal emulator: konsole
• problem reporter: abrt (?)
• help viewer: khelpcenter
• system settings: systemsettings

The issue that was brought up during the blocker review had to do with system monitoring:
- system monitor: plasma-systemmonitor

It seems like media playing is missing from this list?
- media player: dragon (dragon player though there has been discussion of replacing this with haruna)

The other item to keep in mind is that all of these defaults would need to be functioning on arm now that it is also release blocking

There are other applications that are default applications that the average user would consider deal-breaking that should likely be added to the list or separately added to the test matrix for F41

email clients (kmail), chat application (neochat, konversation), rdp (krdp), calendar (?), paint application (kolourpaint)

@kparal pointed me in the direction of the release blocking test criteria that QA uses here:
https://fedoraproject.org/wiki/Test_Results:Fedora_41_Rawhide_20240723.n.0_Desktop#Release-blocking_desktops:_x86_/_x86_64

The current link for the release criterion is this:
https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria#Default_application_functionality

Note all the expandable footnotes below it, expand them, read them all.

This is a general criterion that has to apply for all release blocking desktops. Note the exception saying that on Fedora Workstation on x86_64 (and just there), all applications are blocking, and not just the listed set of apps. If you want to extend the set, it can either be extended as a general rule for all desktops, or we can consider having a section specific for KDE (just on x86_64, perhaps) - but honestly I'm not really sure how others would feel about it, because too many if-then sections are then quite hard to remember and process. We can certainly discuss it.

Also, I want to mention that this criterion is one of the most problematic ones and a frequent cause of arguments. The "basic functionality" is really hard to define and it means something else to different people. The list of covered apps is intentionally short, because it's a universal set that must be working everywhere, and especially on arm there are frequent issues, and also it's a pain to test it all. The fact that we cover everything on x86_64 for Workstation is very often a source of debate and question whether we shouldn't trim it down. Should really the whole Fedora, all editions, be stopped, just because you can't delete a contact in gnome-contacts? Or because gnome-maps renders the routing directions incorrectly? Even though the release criteria were approved as they are, when there's a release blocker like this, suddenly people start to change opinions. That is the reason why the universal selection is intentionally covering just the most important apps. Which means no email clients, no chats, no drawing apps, no music/video player. If we block on all this on all desktops on all arches, we just know we'd probably never release.

When we discussed a broken system monitor on KDE last cycle, I was of the same opinion, that it's not important enough to warrant a whole-Fedora delay. But other people have different opinions, so you're certainly welcome to raise this topic and suggest changes, and let's see if we can reach some agreement across all stakeholders.

The following is an implementation of the criterion mentioned above, as well as other desktop-related criteria:
https://fedoraproject.org/wiki/Template:Desktop_test_matrix

It lists the test cases which verify whether the criteria are satisfied. A failure in a test case doesn't necessarily mean a criterion is broken, that is decided in a blocker review meeting. Also, the test cases are not supposed to be a completely exhaustive coverage, they are just means to make sure we have a chance to detect serious problems and don't forget about any important area.

There are other applications that are default applications that the average user would consider deal-breaking that should likely be added to the list or separately added to the test matrix for F41

If this is just about adding test cases and not mandating them to be release blocking, that's an easy task, write a test case (or we can even just use "QA:Testcase desktop app basic" with a particular label) and we can add it to the matrix. Note that those apps are already supposed to be covered by "QA:Testcase_desktop_app_basic_others" (meaning test basic functionality in all other apps which are not listed explicitly), but realistically we mostly care about that test case on Workstation x86_64, where it's release blocking, and do it in some extent on other desktops/arches when we have enough time. Having an explicit test case for say an email client is fine, if you see value in it and plan to test it regularly. We can slot it in there with an Optional label.

Hope this clarifies things a bit :-)

I don't think we could make KRDP a deal-breaker unless we figured out a way to automate setting up and testing an RDP connection, which requires enough manual steps that I don't know if it's feasible to do.

We no longer test Konversation once Fedora 39 falls off. The calendar application is Merkuro, we should probably have some tests for it.

Understood. It sounds like we would be mostly adding test cases and separately adding just plasma-systemmonitor as a blocker based on the comments above.

The test cases would probably be a good opportunity to invite participation from the end users so we should come up with a list of the new applications that should have test cases added (e.g. merkuro, dragon)

Based on the general exclusive focus on the Workstation x86_64, KDE Sig will probably need to recruit end users for QA:Testcase_desktop_app_basic_others and QA:Testcase desktop app basic

I'll post something in the channel once we have a sensible list of applications for them to test.