On Fri, Nov 30, 2001 at 08:52:47PM -0000, Darrell May <[EMAIL PROTECTED]> wrote: > [...] > Gordon, I do not know why you take this stance.
Because we must make a choice as to which features should be presented to the majority of users. And, as I said, there are impacts on other areas, for example documentation and support. > We are in beta1 mode are > we not. We have not even had time to test your latest samba rpm. We > have not seen or tested any php or mysql upgrades yet. You are implying > we are at a closed feature set, done deal for 5.1. These are not user-visible changes. They do not have a documentation impact. > I have taken the time today out of my busy work schedule to look into > this for you. I have completed the necessary Workgroup panel changes > which I have offered to you already. I'm happy to contribute this to you > to assist you in finishing this project. And we appreciate your help. Your panel text strongly advises against enabling roaming profiles. We have followed your advice (and that of many others on devinfo) and disabled them by default. Just because we can add a toggle to the server-manager, it doesn't mean that we should. One of our overriding design goals is, and always has been, reducing the number of parameters seen by the typical user. > Step back, relax, and let's complete this. The reason it is done this way is that I _have_ stepped back and taken the advice of the devinfo community that roaming profiles should be disabled and only enabled by those who really know what they are doing. Adding the server-manager toggle makes it easy for people who do not know the ramifications to enable roaming profiles. If they are as problematic as the people on this list say, it is better for it to be a conscious decision at the command line, covered by a HOWTO. Adding the server-manager toggle means that support people will need to know how to support roaming profiles and know about the problems and resolutions. People will toggle it, and they must be fully supported when they do so. The current status is that they are disabled, as advised, and can be enabled with two commands from the command line. This seems like a very reasonable compromise: - Standard users get the safe, advised default - "Power users" can easily enable them, but must do so consciously If you advise your customers against roaming profiles, why would you want an easy toggle for them to cause you support load? If you know your customer's environment would work well with roaming profiles, you have a simple method to do so on their behalf. This seems to be the best of both worlds. Gordon -- Gordon Rowell [EMAIL PROTECTED] VP Engineering Network Server Solutions Group http://www.e-smith.com Mitel Networks Corporation http://www.mitel.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
