I was looking at KDE Products => KDE's Applications.

The majority of the Applications can be installed and unstalled without breaking the Plasma desktop. They stand-alone and require a Framework and libraries. However KUserFeedback is not one of them. It was installed as a dependency for kate and plasma-workspace.

I think when an "Application" has this sort of dependency/requirement, it ceases being an "Application", as the majority are on this page, and becomes another component of the base, Plasma. An "Application" is a optional tool used by the end-user and is incorporated into the user's workflow as the user deems necessary to improve their experience in play, education, or work.

At a minimum, KUserFeedback should not appear on the Application web page. It isn't an optional tool used by the end-user to improve their experience in play, education, or work.

Packaging dependencies like this are dependent on the distro, so this sort of issue should be discussed with them.

Packaging dependencies like this are dependent on the distro, so this sort of issue should be discussed with them.

Okay. Do you know of a distro using Plasma desktop that doesn't require kuserfeedback telemetry installed?

Funny that they chose that "Application" to make system dependent. I'll talk with the distribution maintainers and see what they need.
My initial impression that since it is a "Application" and there are hooks throughout plasma, it's not easy to undo

That's the KUserFeedback Console. I agree it shouldn't appear as an application in the website, it's an internal development tool.

The fact that KUserFeedback console appears is due to a regression during the gitlab transition. I created a TODO for myself: https://invent.kde.org/websites/kde-org ... -/issues/4

stormrainbow wrote:
Okay. Do you know of a distro using Plasma desktop that doesn't require kuserfeedback telemetry installed?

I don't see it even packaged for Kubuntu.