To get better statistics about Drupal Core usage (and module usage) to use in Drupal marketing I say we should remove the statistic submission of the Update module and get Drupal to send statistics all the time to drupal.org.

Why? Well, for one, accurate statistics (that most certainly show an increase) for Drupal usage is always good. Accurate statistics are good in markering.

Secondly, with services like DrupalStatus.org you don't need the Update module, they collect the data in some other way. When I don't need a module, I shut it off, and if a developer doesn't want the end-user/client to see the messages of updates or if the developer choose to use the DrupalStatus service (which I really like, and use every day) they shut the Update module off, and no statistics doesn't reach drupal.org. If DrupalStatus.org, and similar services, continue to grow and more and more website shuts off the Update module the stats will be very incorrect, and that is not at all good.

I've written more about it here: http://www.adamevertsson.se/en/articles/more-reliable-drupal-statistics, but the essence is what I've stated above - report all Drupal usage to drupal.org.

Yours fellow Drupalist,
Adam Evertsson

Comments

btopro’s picture

I don't think you'll ever move this mountain personally in the name of data security / reporting without people's knowledge / in-ability for non developers to turn it off.

after the disclaimer: I really like the idea, I think it should be abstracted from update module but still made a UI checkbox that can be disabled if users so choose. I leave it on everything I do because I also like my projects getting accurate numbers but I'm not sure everyone feels this way for security, performance and personal reasons.

AdamEvertsson’s picture

I think you are right, btopro, and a checkbox is a nice option when looking at the alternatives. Since I'm not a programmer and not able to push this change through myself, I'll just have to see what happens. Perhaps there are more of the same thought for the upcoming versions of Drupal.

Dom.’s picture

I woul be happy to make this change, but as said by btopro in #1, it will probably result in a long discussion before it is approved...

Althought could you please clarify "where" you would like to set this functionnality ? To the module manager somehow (I don't know it's name but there is probably a set of serivce to handle modules [discovery, install, etc...]) ?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

xjm’s picture

xjm’s picture

Title: Collect all module usage and send it to drupal.org » Require collection of all module usage for Drupal.org (rather than in an optional module)
Status: Closed (duplicate) » Active

Sorry, I read more closely and saw that this issue is requesting that it be non-optional.

I think that is probably wontfix, but retitling and reopening so that can be discussed if it is the request. Sorry for the noise!

dawehner’s picture

I think what the issue argues is to make the reporting still optional, but not bind it to the update module, as with composer/other services you won't have update module installed, but rather make it as part of system module for example.

xjm’s picture

Title: Require collection of all module usage for Drupal.org (rather than in an optional module) » Move module usage statistics out of Update module
Version: 8.1.x-dev » 8.2.x-dev

Ahh, thanks @dawehner for clarifying.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Active » Closed (works as designed)
Related issues: +#2940737: Telemetry initiative

@AdamEvertsson, thank you for making this proposal.

Three and a half years after this issue was created the Telemetry Initiative was proposed in the core ideas queue. Even though that discussion is still ongoing it does has support and more discussion. Therefor, I think this can be closed and further work be carried out in the other issue.

Cheers