Closed (won't fix)
Project:
Hostmaster (Aegir)
Version:
6.x-0.4-alpha3
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
27 Apr 2011 at 18:14 UTC
Updated:
27 May 2011 at 20:14 UTC
Obviously anyone can enable it if they want it- but my worry is that you are denying yourselves and Aegir contrib module developers valuable usage information. Without Update Status enabled, there's no way to get even a rough idea of how many people are using Aegir, or contrib modules for it...
Comments
Comment #1
ergonlogicIt's in the plan, but until there are recommended releases, it won't show anything. Hostmaster releases on d.o are blocked by #1128596: version numbers in hostmaster project are wrong and #751242: Install profiles cannot create releases with a non drupal-org makefile.
Comment #2
danepowell commentedFair enough- I guess my interest is primarily as a maintainer of a new Aegir contrib module... it's a little dissatisfying to not have any way of knowing if people are actually using it.
Comment #3
anarcat commentedThis seems like a dupe of #1128596: version numbers in hostmaster project are wrong.
Comment #4
danepowell commentedHrm, not so much dupe as postponed waiting on that issue I think. But whatever.
Comment #5
anarcat commentedOh! I see what you mean - you think aegir, when installed should automatically enable update-status?
Comment #6
danepowell commentedBingo :)
Comment #7
anarcat commentedOkay, then my take on this is the following: there is a good reason why update_status is not enabled by default in Aegir (or Drupal, for that matter). I consider it is a privacy intrusion to have software *automatically* phone home when it is installed. Aegir, as any Drupal site, doesn't automatically do that because it would invade your privacy. You can enable it if you want, but as long as Drupal.org doesn't do it, I don't believe we should either.