-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable telemetry module on new installs #5253
Comments
First PR effort is up. |
The PR looks good. The only big issue is that the link for our policy should go to backdropcms.org/privacy, rather than the philosophy page. I wasn't sure about adding a Dashboard block (or the wording in it), but if we want to add one I think the block in the PR looks fine: I was thinking we could explain more about what "Telemetry is enabled" meant, but with previous concerns in #285 about scaring people into turning it off, perhaps that simple statement is sufficient. |
We agreed at todays sprint to remove the block. There is already an entry in the status report that provides the same info. Agreed also to add the links to the policy and the collected data to the status report. PR updated. |
PR looks good to me. I like this more than cluttering the dashboard with a block that doesn't actually report any dynamic data and admins do not need to visit on a regular basis. |
I have merged backdrop/backdrop#3872 into 1.x for 1.21.0! Yay, very simple but a big decision here. Thanks @docwilmot and @klonos for helping move this along! |
This is part of the #5231 meta.
I think that we should tackle the following items here:
Add Admin Dashboard block to telemetry module(removed as a requirement after discussion)Translation update
New strings introduced:
View the Backdrop CMS data collection policy
,View public Backdrop CMS data
,Anonymous information about how your site is configured is being sent to @domain to help improve the project. See the <a href="!telemetry_report">Telemetry report page</a> for more information.
The text was updated successfully, but these errors were encountered: