Besides Judy concerns regarding the UI, I would bring up another question:
If the problem is: >> in the developer meeting today the question came up why the Episode UI [1] >> is not activated by default. Several people have not noticed this feature >> yet because of this. is enabling it by default the solution? In my opinion NO. Because this is an indicator that our documentation is not structured and conditioned in a way that an adopter understand the feature of our software. If we follow this proposal, in the log run every new feature has to be activ by default an to get the adopters attention we have to add flashes and arrows in yellow and red and blinking to highlight these features. So instead of using this short-therm solution I would vote for a solution that will help us to deal with this and further problem for example with features that could not be distributed by default due to license- or legal restrictions. Regards Nils --- Nils Hendrik Birnbaum IT-Consultant Requirements Engineer
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
