Moving project telemetry reporting from the update module into core

Created on 21 May 2024, about 1 month ago
Updated 28 May 2024, about 1 month ago

Problem/Motivation

The update module (packaged with core) provides a lot of functionality:

  • Reports interface to view a list of modules and themes that are out of date
  • Email notifications when there are updates available
  • Update individual modules and themes by uploading a file via the UI
  • Report usage metrics (telemetry) of installed modules and themes back to Drupal.org

For people that run a large number of sites, especially those that share a common codebase (very common in Higher Ed and Government), it's very common to NOT enable this module, because none of the functionality is needed. As a result, Drupal.org misses out on receiving a lot of telemetry data because it's bundled in this with this module.

Proposed resolution

Separate out the telemetry reporting from the update module and instead bring it into core. I briefly scanned thru the code and didn't see an obvious area where this is being reported, so I think what's happening is that when the module gets its list of extensions and asks Drupal.org for the latest versions of those extensions, Drupal.org registers the usage. So there may need to be some work on Drupal.org's end to faciliate this.

Remaining tasks

Decide if it should be opt-in or opt-out. There's some discussion about this in 🌱 Telemetry initiative Needs review .

User interface changes

API changes

Data model changes

Release notes snippet

✨ Feature request
Status

Active

Version

11.0 πŸ”₯

Component
UpdateΒ  β†’

Last updated about 1 hour ago

  • Maintained by
  • πŸ‡ΊπŸ‡ΈUnited States @tedbow
  • πŸ‡ΊπŸ‡ΈUnited States @dww
Created by

πŸ‡ΊπŸ‡ΈUnited States bkosborne New Jersey, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @bkosborne
  • πŸ‡¬πŸ‡§United Kingdom AaronMcHale Edinburgh, Scotland

    This sounds like a good idea. More accurate usage data is a good thing.

    Decide if it should be opt-in or opt-out.

    My default position is opt-in, but we should definitely encourage sites to opt-in, highlighting the benefits of doing so, linking to a privacy statement, etc.

    Having said that, I personally wouldn't object to an opt-out strategy, as long as it was very clear to users that they can opt-out and the implications of staying "in" are clearly communicated.

    At the end of the day I think it comes down to how we communicate it and where we choose to place the option.

Production build 0.69.0 2024