calamares/src/modules/tracking/CMakeLists.txt

calamares_add_plugin( tracking
    TYPE viewmodule
    EXPORT_MACRO PLUGINDLLEXPORT_PRO
    SOURCES
        Config.cpp
        TrackingJobs.cpp
        TrackingPage.cpp
        TrackingViewStep.cpp
    UI
        page_trackingstep.ui
    RESOURCES
        page_trackingstep.qrc
    LINK_PRIVATE_LIBRARIES
        calamaresui
    SHARED_LIB
)

calamares_add_test(
    trackingtest
    SOURCES
        Tests.cpp
        Config.cpp
)
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it possible for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module. 2017-08-29 14:00:37 +02:00			`calamares_add_plugin( tracking`
			`TYPE viewmodule`
			`EXPORT_MACRO PLUGINDLLEXPORT_PRO`
			`SOURCES`
[tracking] Add a Config object 2020-05-12 14:24:33 +02:00			`Config.cpp`
[tracking] hook the install-tracking job into the build. (it doesn't work yet, though .. multi-threading issues). 2017-11-09 11:45:25 +01:00			`TrackingJobs.cpp`
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it possible for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module. 2017-08-29 14:00:37 +02:00			`TrackingPage.cpp`
[tracking] hook the install-tracking job into the build. (it doesn't work yet, though .. multi-threading issues). 2017-11-09 11:45:25 +01:00			`TrackingViewStep.cpp`
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it possible for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module. 2017-08-29 14:00:37 +02:00			`UI`
			`page_trackingstep.ui`
[tracking] Polish UI a bit - add icons for graphical display of actions - extend description of tracking options - add debug logging - enable next button - show/hide tracking options based on configuration 2017-11-06 16:12:41 +01:00			`RESOURCES`
			`page_trackingstep.qrc`
Telemetry stub. This is experimental, off-by-default, code for developing a telemetry / tracking configuration module. It is preliminary work for issue #628, but also for KDE Neon configuration. Any telemetry should conform to the KDE Telemetry Policy [1] or similar Free Software telemetry policy (e.g. the Mozilla one). [1] https://community.kde.org/Policies/Telemetry_Policy Initial idea is to distinguish three kinds of tracking: - installs. This tracks that OS <foo> has been installed somewhere. It might send some machine information to a remote server. - machines. This enables some kind of machine tracking in the installed system, for instance it could enable popcon on Debian, or periodic phone-home-pings. - users. This enables some kind of telemetry / tracking on the installed user in the system. A simple and transparent setting is to enable install-tracking and set it to opt-in, and disable machine and user tracking. Explain to the user that <foo> would like to know when <foo> is installed, and that the following information <d1>, <d2> will be sent to <url> in accordance to the <foo> telemetry policy at <url2>. Work in this branch is subject to VDG review for the visuals, and privacy oversight by whatever group is responsible for <foo> privacy. Note that this module makes it possible for telemetry configuration to be visible inside the installer; what distro's do with telemetry already is entirely outside the scope of this configuration module. 2017-08-29 14:00:37 +02:00			`LINK_PRIVATE_LIBRARIES`
			`calamaresui`
			`SHARED_LIB`
			`)`

[tracking] Add a test executable - just a stub, hardly tests useful functionality 2020-06-23 14:43:26 +02:00			`calamares_add_test(`
			`trackingtest`
			`SOURCES`
			`Tests.cpp`
			`Config.cpp`
			`)`