Well, Drupal has always had an opt in feature for reporting, though we haven't done much with it except run the occasional SQL query to get the data. There is work done on a presentation of that data via project module.... However .....
This is important. We should probably write up what is sent and how it will be used in the future. And note that it is an Opt-In setting.
I agree. I tend to think the action plan should be: * get the patch to drupal.module in. * note that both drupal.module and update.module are opt-in. * note the exact data that both send, and why. And this should be included in both the README.txt (so that it is included with every distribution download) and in every future release announcement (in a smaller form that admonishes to see the README for more information). I can help work on this (though, perhaps not today as I'm about to leave). I don't have a running 6.x install anywhere, so would need sniffs on update.module. Based on looking at update.fetch.inc, it looks like we're sending only project name/version (and the IP, a side effect of the HTTP request). -- Morbus Iff ( drowning in data, bereft of knowledge. ) Technical: http://www.oreillynet.com/pub/au/779 Enjoy my: http://www.disobey.com/ and http://www.60bwc.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus