First though, should we sit back ever so slightly and document up some overarching goals/principles we wish to follow for log4j2 as well as a general overall high level design, and plan of attack? Sort of a 'vision' statement?
I'm starting to put together a 'compelling reasons to adopt log4j 2.0' bit of text. I am trying to think about why a fictional user who has used log4j 1.2 and is thinking about adopting log4j2.0 would choose to make the switch. If we are unable to define what the compelling advantages of log4j2.0 will be, I think we'll be starting off on the wrong foot.
I've got a tonne of family and other events on this weekend, and might not get to complete this list straight away, but I can post an initial cut of my thoughts on the wiki for comment soon, and people can discuss them but perhaps people can begin to think about this in the meantime.
cheers, Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
