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 [EMAIL PROTECTED] 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
