Since the discussion is pretty quiet, I'll toss out a few more questions. (I don't have any good answers, since I'm pretty new here :)
1) Not huge uptake due to plethora of options--can't reduce the number of options, but can make S2 more appealing. Agreed. Options are good :) I'm not intimately familiar with the docs yet. Are the options organized into beginner, intermediate, expert categories to avoid overwhelming people? 2) Some plugins are pretty rusty. Which ones? The ones nobody uses or the ones everybody would like to use if they weren't so rusty? If the former, perhaps they should be retired instead of polished? 5) I think if the internals were leaner/cleaner it'd be easier to take stock of where we're at and tighten things up. Anything in particular that you can think of? "Internals" covers a lot of ground :) I agree. This is a discussion needed to determine short-, medium and long term goals. If we agree priorities can be more effective at the time we spend. Right now my colleague Albert and I are still working on improving and expanding the capabilities of the REST plugin to easy the creation of hypermedia driven applications. Honestly, I think this is a crucial point if we want struts 2 to stay relevant . But that is our point of view. Improving documentation is a must as well. How can we cooridinate efforts effectively? The simple answer would seem to be that this dev list is the best place to coordinate efforts. It sounds like you want to know if anybody else is working on REST? (I'm working primarily on security-related issues.) John
