I'd like to ake a suggestion regarding making behavior changes, and how the new beta/future branches might be used. Feedback welcome.
Developers and decision makers are often reluctant to change aspects in behavior, whether it's the web interface, remote interface, controller, library scanning, etc. The first reaction from users and developers alike is often "make it an option". That's fine - it's perfectly understandable given some of the past adverse user reactions to server changes. But this immediately runs into the other understandable questions and developer resistance. "Do we really need more options?" "Aren't the settings complicated enough already?". End result? Even simple, seemingly desirable changes, languish. My suggestion: Use the future beta branches to test the waters with some of the suggested changes. See what kind of feedback you get from beta testers. Isn't that half the point of beta testing? If there's something that maybe could have an option, but nobody wants to create another option, just try changing it and seeing what the beta testers think. If they hate it, or someone insists that it must be made an optional behavior, put it back on the shelf. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=46725 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
