> Perhaps the log4j community needs to formalise some sort of "feature > requirements" for Chainsaw through discussion, and prioritise those on a > release schedule basis. Once the requirements are ok-ed by the dev (and > even the users themselves! :) ) community, then portions of everyone's > respective sandbox code could be integrated. I'd really like to see > Chainsaw develop into something totally powerful and flexible, but it'll > probably need to be done through small iterations, formed from a > base plan. > > If this sounds agreeable to the dev community, are there any guidelines to > follow for this sort of thing? I'm happy to help co-ordinate anything if > need be. Scott, interested in this too?
I don't think there are any formal guidelines. I'd like to see Scott's code added to the log4j-sandbox. It was created for just such an occasion. (I'd also like to see Richard Bair's configuration tool and maybe an experimental JDBCAppender added as well. BIG hint here, guys!) As far as co-ordinating a feature/wish list for Chainsaw, there have been a number of email threads on the topic. It would be nice to have something to refer to. I would suggest the wiki area as a good place (http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages). As far as priority, it will probably be obvious which tasks/features are dependent on others, but anywhere folks want to jump in and get their hands dirty would be good. I agree that smaller, concise changes are easier to patch, discuss, and digest. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
