Sorry I wrote something, that could be missunderstood. It would like to say:
Because this is an indicator that our documentation is not structured and conditioned in a way, that an adopter understand which features our software has. That means the querstions "what can I do with a Matterhorn?" not "How-to configure and use a Matterhorn?". It's pointed to the feature list or something similar, not to the documentation of this feature. Regards Nils > 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] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
