On May 20, 2:28 am, [email protected] wrote: > On 19 May 2010, at 23:36, Christopher Forsythe wrote: > > > > > OK, if you add a white list feature, it should not be able to be > > > > overridden by end user in any case. > > > > This overrides one of our main goals, giving users the control. I'm ok > > > with a white list, but the end user must have control. > > > What do you mean by control here? > > > I mean that in the end, the end user can decide what they get notified for. > > > If the admin decides to notify for something which is quite not in the > > interest of the end user, and the end user knows enough about Growl to get > > around the admins control, then they should be allowed to do that. > > Exactly. > For a regular user of growl, the admin’s set of notifications I expect would > be quite limited (as they are aiming for “don’t upset or confuse unaware > users”). So for me as a regular user, I would almost certainly want to be > able to at least enable any others I like. I can see a reasonable argument > for not being able to disable those notifications whitelisted (especially if > they’re being used eg. to push notifications by the admin as previously > mentioned), although I’d rather expect that the admin could rely on aware > users to behave themselves in this respect, rather than force things.
Admins just want the flexibility to manage things. > > From my point of view, this comes down to what we want to achieve: > Do we want to allow admins to blanket apply a default set of notifications > and configurations thereof, to stop support cases from unaware users (and > other benefits)? Admins already have this. It's call "Growl isn't going on my systems" > or > Do we want to give admins absolute power over everything? (because they like > the taste? i don’t really know what a good reason is, but then i’m not > exactly sitting on the fence…) It's not up to you or any of the Growl Developers to make this call. Admins already do have full control of everything (see my response to Christopher) including whether or not to allow Growl on the system. Here's what the admins have control over: 1) Decision to include Growl or not (there's nothing the Dev Team can do except *encourage* other software to install Growl like Adobe did and that's not a good strategy). So admins win here. 2) Application registrations. While making the standard image that goes on all managed machines, the admin can decide which Growl apps are registered and set alerts styles. If the access to the Growl System Preference pane is block via Workgroup Manager, the end users cannot change update the settings. So admins win here. So, admin control seems pretty absolute to me with the current situation. Now if a whitelist were implemented then - 3) Admins could managed the allowed applications alerts centrally, without re-imaging their machines or touching them with a script or patching them. If the white list were extended to include alert styles and stickiness, then effectively Growl would get centralized manageability for *free* and win a lot of warm fuzzies from the control freak admin community, as well as be able to stop alerts from rogue installs (cough cough Adobe). What I guess I'm saying is that the argument of whether admins should get absolute control is pointless. They already have it. I am advocating a layer of manageability that would make choice 3) more amenable than choices 1) which is easy and choice 2) which is a "set it once and forget it or go back and patch it" scenario. For everyone involved in this discussion, I am grateful that you are considering the white list idea. I think it would be a fairly straightforward change, and would be well-received. Dean > > Josh > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/growldiscuss?hl=en. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
