ant elder wrote:
On Tue, Nov 11, 2008 at 10:11 AM, Simon Laws <[EMAIL PROTECTED]> wrote:
OASIS is clearly on the list. Ant's survey should help. But what else?
IMO this is not really about a detailed shopping list of code changes but
more about themes (as per the thread title), i.e. more the what than the
how.
Here's some things i think it could be good to look at:
More coherent documentation.
Improved JEE/Webapp support.
Policy and QoS
Distribution
I agree with the these technical suggestions. I think the OSGI
enablement will be a big draw (even if it comes before 2.0). We are
going to need some good samples and demos that show this off.
I'd also like to see the documentation improved. I spend a lot of time
searching the samples for specific techniques and patterns. I think the
samples have many golden nuggets hidden in there. The documentation
would be a nice way to expose the riches and put them to use.
In a similar vein, I think consumability would be a good theme. We could
spend a few more cycles honing the user experience. I'd like to see
more top notch demos and presentations of the Tuscany capabilities.
Perhaps this is not our development realm, but promoting graphical tools
and syntax assist tools to work with Tuscany. Personally I get
frustrated when I read or make Tuscany demos or presentations and the
simple composites must be created with PaintShop or some non-tech tool.
--
Thanks, Dan Becker
