Skip to content

Telemetry Initiative

Tim Erickson edited this page Oct 18, 2020 · 15 revisions

GOAL: To collect useful data so that we can make better-informed decisions about what should go into (or be removed from) backdrop core.

FAQ:

What data do we want to collect

MVP

  • PHP Version
  • MySQL Version
  • Webserver and Version

Other options

  • which core modules are enabled
  • are clean URLs enabled?
  • which core layouts are in use?
  • which core module field types are in use?
  • which contrib (sub)modules (not projects) are in use?
  • which color module color palettes in use?
  • how many roles are in use (and their names?)
  • how many sites are using revisions?
  • which permissions are added to editor role
  • (problematic - need to think about implications of it)
  • PHP version (needed for #3490 and #719)
  • Server OS - needed for these
  • Multisite or not (needed for #3206)
  • Name of Install profile in use (needed for #3205)
  • Number of block displays vs page displays for views (needed for #2978)
  • Sticky admin bar setting (needed for #788)
  • User role names (needed for #1285)
  • Number of active themes (needed for #131)
  • Site size metrics (number of user accounts, number of nodes, number of managed files etc.)
  • Whether the site was a previous D6/7 upgrade
  • enabled modules & sub-modules (not just packages) d.o issue 1 | d.o issue2 | d.o issue 3 Needed for the following:
  • Contextual links module: #1409
  • Contact module: #3023

Where do we want to collect the data.

Options include:

  • BackdropCMS.org database
  • Separate MySQL database
  • Solr database
  • Elasticsearch

The current thinking is that we would just start storing this data in our existing BackdropCMS.org database. Mostly, because of simplicity and to reduce the need to have someone with special skills available to manage this. We are open to other options, but based upon currently available skills and resources, the current BackdropCMS.org database seems to make sense.

How do we manage data responsibly and with consent?

  1. Being totally transparent about exactly what we are collecting and how it is being used.
  2. With opt in language similar to this: Would you like to send anonymous data to backdropcms.org to help inform future product development?

Are we collecting data all the time?

We expect to update the data on a weekly basis.

Can this be used for contrib as well

No, we do not expect to make it possible for contrib projects to collect data using this process. At least, not initially. This is something that can be considered in the future.

How does Wordpress do this?

https://wordpress.org/about/stats/

Other examples