Would this mean if I had an idea I'd like to offer up, I'd implement it, create the sample app, then present everything to the dev list? What about those looking to contribute to the path the committers have chosen?
I don't think that the only way to contribute is a full-blown sample app; I think Don was speaking about a specific type of contribution.
I just sent an email with a few of the things I'm thinking about doing; otherwise, I'm not sure what to "break off" and delegate. Do you see anything I didn't mention? What is the part that interests you?
One thing which has been talked about in a few places, and which would be valuable, but which no one has done any work on is implementing "extends" in as many places in struts-config.xml as it would be useful, to eliminate repeated chunks of XML. For Validation, this would really be an enhancement to commons-validator, but perhaps the same general strategy could be applied. I haven't even looked at what would be involved in trying to implement it.
I also like the idea of auto-discovery of struts-config.xml and the other config files; we've taken to making many of them for our apps, and it's boring to have to add them all.
And, of course, many users have filed enhancement requests throughout Bugzilla, although working on those may or may not be close enough to the current discussions which have generated so much discussion.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]