There are some issues that have languished a while because consensus generally can't be reached between the issue creator and the Fedora KDE Sig.

Example Issues:

• #6 Opacity Shortcuts by Default Suggestion
• #7 Default Shortcut for KWin's "No Border" function
• #8 Improve Plasma's Default "Launch Feedback"
• #11 Replace Middle Click Paste on Desktop with Application Launcher
• #59 Consider installing the Plasma Browser Integration extension in Firefox by default
• #109 Consider installing kdenetwork-filesharing + deps by default
• #116 Add usbmuxd to the default install of KDE spin and Kinoite
• #146 include Skanpage by default
• #189 Add plasma-wallpapers-dynamic to KDE Spin & Kinoite default install
• #357 Include Haruna (mpv based media player) by default

Generally speaking, it appears that an end user will open an issue relevant to their workflow and the KDE Sig will consider each default on a case-by-case but because Fedora is an "upstream-first" distribution, it is frequently asked to send the request upstream first. In the case of defaults, the upstream appears to be looking for downstream to take the lead on default settings.

There is a risk here of default instability if the downstream is frequently changed based on the input of individual users, and often there is insufficient data provided in the issues to make an educated decision about the impact to other users.

I believe it would be beneficial to codify the data that the end user seeking the change should bring to the Sig before requesting the change. I think depending on the change impact, there can be different criteria that need to be met. Also some changes can simply be off the table (e.g. X11 change requests).

The members of the Fedora KDE Sig wouldn't need to follow these procedures but they would probably help their case. There are some times where upstream has requested downstream install default applications, which I think would be an exception (e.g. ngraham, tfella etc requesting a change).

Here is a proposal:

1. The user can create the issue that must be well-reasoned (e.g. there is critical functionality that it provides) and a Sig member can triage to determine if it's worth starting end user consensus procedures or if it's something the Sig should just do
2. The user that is requesting the default change should utilize the poll feature of the Fedora Discussion Forum to collect consensus data.
3. The poll would need a minimum of 30 responses.
4. There needs to be at least 3 options on the poll. Yes, No, N/A (e.g. doesn't care about the changing of the default)
5. For low impact changes, at least 60% must say "Yes" in the poll.
6. This doesn't obligate the KDE Sig to make the change (e.g. the KDE Sig can still block it for reasons)
7. Other criteria can be added during the triage stage depending on the impact.

If this all feels unnecessary, I can start going through some of the old issues and start closing them out instead of letting them languish just to do some cleanup.

If the Sig thinks this is something that would be beneficial, we can get the Fedora KDE Documentation Team to create a Wiki Page / Documentation Page that writes up the procedure and then send out the information on the mailing list or on the discussion forums to make end users aware.