I would like to see this happen. I agree that inter-operability between platforms/languages would be a wonderful feature. It would blow the socks off of other logging mechanisms. However, I do have a concern.
<my-opinion> As it stands right now, log4j does not have enough active committers. We have a number of committers listed, but not very many of them are actively working to address issues, add features, fix bugs, etc. I don't know the reasons, and I am not going to judge. But I strongly feel that we need more active individuals to lead/take log4j into the future as a healthy (healthier) open source project. There are all sorts of things that could be worked on to make it a better tool/library/framework. Heck, if we just had one committer that was dedicated to evaluating and applying submitted patches from the user base, either in the core library or a sandbox, that would be a step in the right direction. Maybe bringing everyone together at "logging.apache.org" will help bring new faces and energy to the project. But it might also drain resources from log4j as well. If we start spending our time trying to figure out how to inter-operate between the various languages/frameworks, what happens to other important items we need to be doing for log4j? One important issue right now is increasing performance. We've had some ideas and proposals on several fronts. People only have so much time to devote to any subject, open source projects included, and an issue like performance strikes at the core of the log4j framework. It is going to take a fair amount of effort to understand the issues, figure out the changes, and then implement them without completely changing the current api. Are we going to be able to focus on this issue, as a team, and make it happen for v1.3? v1.4? I don't know. I want to make it happen, and I very much want to be part of the team figuring it out. I don't mean to sound dire or bleak. I just think that we should seriously look at the health of the project and what this new logging group will mean and how it will affect log4j. </my-opinion> So, what does "logging.apache.org" really mean? What would it really be/do? Is the goal logging interoperability or is the goal to bring the like frameworks together, under one umbrella? Or something else? What do we envision the structure of this project to be? > 1) Is inter operability a realistic goal? Is it possible at all? We may not know until we sit down to seriously discuss it. Assuming that one can control both ends of the serialization, yes, it should be theoretically possible. > 2) Is everyone comfortable with assigning copyright to the Apache > Software foundation? I assume that log4j is...:-). Are the other projects comfortable with the Apache 1.1 license or do they prefer GNU? That would be a show stopper. -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
