Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 3761 invoked from network); 21 Dec 2003 21:59:22 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 21 Dec 2003 21:59:22 -0000 Received: (qmail 73252 invoked by uid 500); 21 Dec 2003 02:29:20 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 73234 invoked by uid 500); 21 Dec 2003 02:29:19 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 73221 invoked from network); 21 Dec 2003 02:29:19 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 21 Dec 2003 02:29:19 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AXtLT-0002hc-00 for ; Sun, 21 Dec 2003 03:29:27 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: commons-dev@jakarta.apache.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AXtLS-0002hU-00 for ; Sun, 21 Dec 2003 03:29:26 +0100 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AXtLS-0006CG-00 for ; Sun, 21 Dec 2003 03:29:26 +0100 From: "Bill Barker" Subject: Re: What is Jakarta Commons? Date: Sat, 20 Dec 2003 18:41:22 -0800 Lines: 51 Message-ID: References: <004101c3c6ed$1365e6e0$cd5c8051@oemcomputer> X-Complaints-To: usenet@sea.gmane.org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N "Stephen Colebourne" wrote in message news:004101c3c6ed$1365e6e0$cd5c8051@oemcomputer... > Jakarta is having trouble redefining what is truly stands for. I had hoped > that in Jakarta-Commons we knew. However, since its specifically different > to what is in the charter, I guess we should decide. And then update the > charter. http://jakarta.apache.org/commons/charter.html > > From the websites: > 'small scale, reusable, code components that are useful in multiple Jakarta > subprojects' > > 'focused on all aspects of reusable Java components' > > 'creating and maintaining reusable Java components' > > 'collaboration and sharing, where developers from throughout the Jakarta > community can work together on projects to be shared by the Jakarta projects > and Jakarta users' > > > There are other practical ways to define it. Each J-C component has > insufficient community on its own to survive at Apache, either as an > independent TLP or within another TLP. Yet within J-C the component is > supported and watched over. For example, one way to view this is by mailing > lists. If each commons component had its own mailing list, then most would > be very quiet. Not enough to stand alone. > > My preferred short definition of J-C is: > 'creating and maintaining small-scale, reusable, utility components written > in Java' > > Is this definition OK? Any comments? This pretty much boots Daemon out of J-C, which would be IMHO would be a shame. Almost of the (supported) code in Daemon is written in C (basically, JNI wrappers to solve OS level restrictions on Java code), so it wouldn't fit the definition. However, it is most definitely Java-centric, so I'd be happiest if it stayed in Jakarta. I'm only a developer for Daemon, so I don't get to vote on its future. And if it is booted out to A-C, then I'll follow it there. But I think that it's best fit is with Jakarta. > Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org