Mailing-List: contact general-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Logging General" <general@logging.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Mon, 21 Nov 2005 10:29:36 +0100 (MET)
From: "Stephan Strittmatter" <stephan@st-strittmatter.name>
To: "Logging General" <general@logging.apache.org>
MIME-Version: 1.0
References: <C5EFCC0B-E79B-40B6-8D3E-2F11919889D6@apache.org>
Subject: Re: [ANN] log4js - logging for JavaScript
Message-ID: <3857.1132565376@www53.gmx.net>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Hello Arnold,

you are speaking out of my soul. It is not required to have "my" version of
logging at Apache. I and Seth already contacted some of the authors (or
tried) you are refered as links.
My intention is first to have a API for logging, which is as most as
possible the same than log4j.
Having a Sandbox would be really great. I would then invite all the guys to
have a look there.
The idea is to focus all these ideas and energy to one project where you
have not to think about which API should I use now.

When do you think, we could get such a sandbox? Currently it is very
difficult to exchange the sources via mail.

Kind regards,

Stephan

> --- Urspr�ngliche Nachricht ---
> Von: Curt Arnold <carnold@apache.org>
> An: Logging General <general@logging.apache.org>
> Betreff: Re: [ANN] log4js - logging for JavaScript
> Datum: Sun, 20 Nov 2005 18:49:10 -0600
> 
> There are a couple of distinct issues here and it would be good to  
> keep them separate.  Would it be desirable for the Logging Services  
> project to start development on a JavaScript logging framework?  If  
> so, would it be better to start from an existing code base?  If so,  
> which code base would be the best to start from?
> 
> Doing a quick search on JavaScript and Logging, I found the following  
> links which seem to be on topic and many of them provide some some  
> implementation code:
> 
> http://kb.mozillazine.org/JavaScript_Console
> http://www.alistapart.com/articles/jslogging
> http://jroller.com/page/stritti?entry=logging_in_javascript_log4js
> http://log4js.sourceforge.net/
> http://gleepglop.com/javascripts/logger/
> http://www.decafbad.com/blog/2005/07/18/ajax_testing_and_logging
> http://ajaxpatterns.org/Logging
> 
> There does seem to be a lot of interest and likely a good community  
> could develop around LS hosted project.  I'd be hesitant to pick a  
> particular implementation to start with at this time before trying to  
> put together a community and developing some shared vision.  It may  
> be that none of the existing frameworks aligns with the collective  
> vision and it ends up being simpler to start from scratch than to  
> deal with adopting an existing code base.  Based on a very  
> superficial review, it appears that all of the logging frameworks in  
> the previous links were solo developer efforts.
> 
> I'd suggest:
> 
> Creating a sandbox-dev@logging.apache.org for Sandbox related  
> discussion and SVN commits.
> Rearranging the sandbox as previous discussed in http:// 
> marc.theaimsgroup.com/?l=apache-logging-general&m=112649550919155&w=2
> Create a directory sandbox to collect artifacts related to a logging  
> framework for Javascript
> Invite the authors of javascript frameworks listed above and others  
> to join the discussion
> 
> Once a community is established:
> Decide how to collect requirements (JIRA, Wiki, SVN, etc)
> Pick a name
> Pick a development strategy
>