Not sure some of my clients would be keen to know that some monitoring was going on in the background, how do you explain the need to abate their fears of data protection.
It would probably be a good module though and that is how I would prefer to install it. Where necessary or allowed even.
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
Interesting, don't they ask to collect install data already?
Not sure some of my clients would be keen to know that some monitoring was going on in the background, how do you explain the need to abate their fears of data protection.
It would probably be a good module though and that is how I would prefer to install it. Where necessary or allowed even.
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
I'm not sure if more accurate browser stats would greatly influence the discussion about SilverStripe 4 browser support
I'm a bit more tinfoil hat than some of my colleagues, but I'm very uneasy about have a default-on phone home system in the CMS. I think it will significantly affect SilverStripe's acceptability to larger enterprises (as well as others I'm sure, myself included) because of the security and privacy implications.So I don't mind having something like this, but I think it needs to be opt-in. If it's opt-out, it needs to be in SilverStripe 4 only. We want people to be able to upgrade within a major release fairly fearlessly, and adding something like this silently would impact that.
So I don't mind having something like this, but I think it needs to be opt-in.
We cannot have and allow any uncontrolled requests to third-party sites in our environment. So *please make it optional*.
For the statistics purpose, we use latest FF and Chrome browsers and never IE to access CMS.
As far as "user or developer enable-able", it probably needs to be developer enable-able, since most larger organisations wouldn't give authority to random CMS users to opt-in to this sort of collection. The first user won't always happen to be someone that has authority for the entire system or all users.
I like the idea of coupling this to some sort of tool for checking whether an install's modules are out of date. That way, it's opt-in with a clear benefit.