1. Concentrate for a while not on new fancy features, but on enhancing quality & usability of the current version.
2. Provide examples _with throughout_ tutorials showing how to create components, configurations, apps etc. _from scratch_ to actual (simple) applications. Including hints on "why this way" (eg why use or don't use LW-components) and "where to collect the needed information" (eg. which archetyppe to use). => users understand the process and can easily build their own apps. 3. Giving more information on where & what for SM is used with 2-3 main pros & cons. Yes, this has to be user contributed :) but developers might regulary ask directly for that tiny contribution when answering questions on the mailing list => for possible users it's easier to see what SM is usable for (evaluation whether use an ESB and which ESB to use) and devls can see where to focus on (stengthen the relevant strengths, cure the main weaknesses) 4. Show the big picture / architecture of SM so people understand better what they do and what is possible at all. Sorry, no idea how to do that :-/ 5. keep on the great support on the lists :-) All the best, Georg -- View this message in context: http://www.nabble.com/User-Feedback-Request-tf2356023.html#a6563288 Sent from the ServiceMix - User mailing list archive at Nabble.com.
