It seems uselessly annoying to have drupal.module require site name, mission and slogan if the goal is to register module/theme usage stats: some stats don't have any of these set, because they would adversely affect their default look under the chosen theme.

This requirement should be removed from the module.

Comments

add1sun’s picture

Version: x.y.z » 6.x-dev

I agree. This is still annoying. :p There are many sites which don't want these nor do they want to muck about removing them from the theme layer when they never wanted it to begin with.

Heine’s picture

Priority: Minor » Critical

I'd say this entire page a complete rewrite. Which function is sending what information? Why would it need to send the email address at all? Compare Send system information: and Send statistics. Does the former submit private information?

sepeck’s picture

I think the site name is important.
Mission and slogan and contact email address not so much as the purpose has changed from when there was a Drupal servers registry on drupal.org.

whether that gets changed or not, we need to clarify what is sent. If someone can list it out I can verbiage it up nice.

seanr’s picture

Should be a warning if it's not included, though, not a requirement. If it isn't included, then it should only send anonymous module usage stats, and not put you in the list. The help/warning text should be written to reflect that.

Gábor Hojtsy’s picture

You should consider what drupal module was developed for and what it is used now.

The idea was to have distributed authentication and to have drupal.org maintain a list of ALL Drupal sites, which have this module enabled, so it can list basic data about the sites. It was also possible to use a custom server to "phone home" to, so users were able to maintain a "directory server" for their own Drupal site network.

Later, drupal.org stopped collecting the list of sites, so this data is not collected on drupal.org anymore (to my best knowledge), and consequently it is not listed there. It is still possible to use this module for a custom "directory server" setup, which honestly I don't think too many people used this functionality for. The distributed authentication portion is also depreciated in favor of OpenID in Drupal 6, which is more secure and much more widely supported.

That said, as far as I have hear, drupal.module is slated to be removed altogether from Drupal 7, and is left in Drupal 6 for some short term for backwards compatibility reasons I guess.

Therefore instead of massaging smaller details in the module, I think we should discuss the following:
- either remove the phone home and directory listing feature from the module completely and keep it as a distributed auth server for D6
- or remove the module altogether, moving it in its entirety to contib (but rename it on the way)

I think it might be possible to entirely remove it even in D6 (we removed modules late in the cycle in D5), and it would help us get rid of this inappropriately named, and in both of its functions pretty much outdated module.

Dries’s picture

I think it would be OK to move the drupal.module to the contributions repository.

Vacilando’s picture

Gábor, you say "this data is not collected on drupal.org anymore" -- does it mean that all the good work on usage statistics ( e.g. here http://drupal.org/node/165380 ) becomes useless? I hope not...

Gábor Hojtsy’s picture

http://drupal.org/node/178768 is focued on the move of the contributed module, so we can leave this issue open for now, and then recategorize for the new module, once it is in contrib.

Gábor Hojtsy’s picture

Usage stats data is collected form the "update" (Drupal 6 core) and "update status" (Drupal 5 contrib) modules, and is in no way connected to drupal.module. drupal.module was only used to present a listing of Drupal powered sites on drupal.org and is not required for usage stats data collection.

AjK’s picture

Project: Drupal core » Site Network
Version: 6.x-dev »
Component: drupal.module » Code
NancyDru’s picture

Gábor said (#5):

distributed authentication portion is also depreciated in favor of OpenID in Drupal 6

Perhaps the better tack to take then is to 1) provide an upgrade path to OpenID, and 2) document, document, document it. (Yes, I'd be willing to help if someone can help me understand it.)

Gábor Hojtsy’s picture

Title: drupal.module should not require mission and slogan » Module should not require mission and slogan

nancyw: http://groups.drupal.org/node/7806 is food for thought on upgrade paths.

Retitled. Not drupal.module anymore.

brmassa’s picture

Version: » 6.x-1.x-dev
Assigned: Unassigned » brmassa
Status: Active » Closed (won't fix)

Guys,

Site Network now only focus on distributed authentication. The site registry feature are deprecated.

regards,

massa