Framework for collecting feedback from application users
https://www.kde.org
KUserFeedback is a framework which allows applications to collect user
telemetry and feedback surveys. It is designed to be compliant with the
KDE Telemetry Policy, which forbids the usage of unique identification.
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / kuserfeedback
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout KDE:Extra/kuserfeedback && cd $_ - Create Badge
Refresh
Refresh
Source Files (show unmerged sources)
| Filename | Size | Changed |
|---|---|---|
| kuserfeedback-1.2.0.tar.xz | 0000206364 202 KB | |
| kuserfeedback-1.2.0.tar.xz.sig | 0000000833 833 Bytes | |
| kuserfeedback.changes | 0000002342 2.29 KB | |
| kuserfeedback.keyring | 0000003139 3.07 KB | |
| kuserfeedback.spec | 0000007455 7.28 KB |
Latest Revision
Christophe Giboudeaux (cgiboudeaux)
accepted
request 952946
from
Wolfgang Bauer (wolfi323)
(revision 5)
- Update to 1.2.0 * bump version for new release * opengl source: Do not crash if we could not make our context current * Add Linux Qt6 CI * Make UserFeedbackConsole build with Qt6 * Fix linking libKUserFeedbackCommon.a * Build with C++17 * Build docs on Qt6 too * Adapt CMake code to make it build with Qt6 * Add auto generated files to .gitignore * Add FreeBSD CI * Add Android CI * Enable Linux CI * Fix typos found by codespell * Qt 6: Replace calls to removed QDateTime(QDate) constructor * Qt 6: Fix issues caused by size() returning a qsizetype * Qt 6: Remove QNetworkRequest::FollowRedirectsAttribute * Replace declarations of QVector, QStringList * CMake: Allow building with Qt 6 * Qt 6: Replace QMap>QVariant ... * Qt 6: Fix signature of methods for QQmlListProperty * Fix cmake warning * Port away from ECMSetupVersion's deprecated *_VERSION_STRING CMake variable * Make the survey expression variant comparison work with Qt6 as well * Use non-deprecated QStandardPaths enum values * Make QString to QUuid conversion explicit * fix Windows compile, no unistd.h needed * Update historical links to cgit.kde.org. * Check for invalid JSON first, then for empty objects * Don't record telemetry-less survey queries, that just produces empty rows * Fix php unit tests * Also record the device pixel ratio * [server] Convert JSON fetch to stream data * Provider: add API to restore default user-visible settings * Always show the "View previously submitted data..." link * Add appdata file for UserFeedbackConsole * KUserFeedback: Convert license headers to SPDX expressions * Fix area charts with Qt 5.14 * Use KDE_INSTALL_LOGGINGCATEGORIESDIR with ECM >= 5.58 * Make it compile without deprecated method - Update kuserfeedback.keyring
Comments 9
1.2 has been released, does this fixed the issue to warrant to re-enable it? if yes..remember to enable for git build also (as currently it's "Disabled until upstream complies with the KDE policies") https://jriddell.org/2022/02/07/kuserfeedback-1-2-0/
The compliance is an issue of the individual users of kuserfeedback, not kuserfeedback itself.
dont really get the issue...but okay
KDE policy requires projects using kuserfeedback to have a discussion / review of what's collected (see https://community.kde.org/Telemetry_Use). Plasma has not done so, in violation of KDE's own policies. Therefore kuserfeedback support is disabled for Plasma and related software.
Ohh...well that sucks...and does sound weird (why it exist then if plasma hasn't done that), as apparently KDE team does use the data they collect for their development (for example "cover task switch wasn't ported originally, because according to the data there wasn't many who used it...but after some backlash they ported it :D)
about this being disable on openSUSE, so KDE closed the bug report https://bugs.kde.org/show_bug.cgi?id=418981 with "Not a bug; saving local data that isn't sent anywhere isn't telemetry, it's how your system remembers state and settings." -statement
I don't see how that statement is related to why kuserfeedback is disabled by default here
so this will be disabled on openSUSE forever? and I still have no understanding why ....KDE says there is no issue and other Distros have on issue have it enabled...so why openSUSE has it disabled?
Maybe. Personally I don't really like how this was handled.
No, they acknowledged that there was an issue.
Those other distros also didn't notice that the KDE policies were violated.