At 08:15 PM 12/15/2003 +0100, you wrote:
Hi,
I'm the developer and maintainer of a log4j sister project: Log4PHP. After reading the initial draft and ml comments I give my "+1" to the LS project. Since log4php is a pure port of log4j it's not a problem for me to change the license.
Very good.
However, I have some questions:
1. The draft talks about the "migration and rationalization of the log4j sister
projects".
Can the PMC explain in detail the roadmap of the migration and what is the exact
meaning of rationalization (finding a common api, a common design, a common
...)?
I changed the word 'rationalization' to 'integration'. I think the term 'integration' would mean at least inter-operability but I can't give you an exact meaning. We have to come up with a meaning together. There is no desire to impose an API on a sub-project. Sub-projects will retain much if not all of their existing freedom.
2. Will the Log4* sister projects be structured as LS subprjs (LS/log4*) or as log4j subprjs (LS/Log4j/Log4*) ?
Log4j will be a sub-project of LS. So here is a possible hierarchy:
LS/Log4j LS/log4php LS/log4cxx
Does this answer your question?
- Marco Log4php project maintainer
-- Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
