Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 10248 invoked by uid 500); 4 May 2001 19:18:08 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 10213 invoked from network); 4 May 2001 19:18:06 -0000 Subject: Re: PMC Meeting minutes for 5/1/2001 To: general@xml.apache.org X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: From: Shane_Curcuru@lotus.com Date: Fri, 4 May 2001 15:17:15 -0400 X-MIMETrack: Serialize by Router on CAMMAIL01/CAM/M/Lotus(Build V508_04052001 |April 5, 2001) at 05/04/2001 03:22:37 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N -- Yes, there should be both an xml-commons and an xml-commons-cvs mailing list. Our firewall is down right now so I can't check; will look into it over the weekend. -- Yes, we need guidelines on what gets checked in. Obviously the SAX2, DOM2, and JAXP 1.1 stuff goes in along with docs on suggested guidelines for their use in xml.apache.org projects, since that was in the proposal. One of my proposed guidelines is that nothing gets checked into the 'main' area of xml-commons until two separate xml.apache.org subprojects ask for it. There's no sense in having a common area for files if only one group is using them... (Of course, this means that some nifty ideas will need to 'sell' themselves to the obvious other groups before checking in, which I think is generally a good thing). -- As for a scratch area where we don't have strict guidelines, why don't we have a (damn, I've forgotten the name - sandbox?) directory that is open for any new proposals, just like jakarta-commons has. Over in jakarta, they have a limited commiter list to the main area of jakarta-commons, but the sandbox is open to all jakarta committers. Then there's a voting process for code to 'graduate' to the main area from the sandbox. There's plenty of neat ideas to think about stealing from jakarta here, but I don't want to just copy everything: the xml community needs to decide for itself how we want to manage shared/common files, and I bet there will be differences from how jakarta does it. - Shane ---- you Scott_Boag@lotus.com wrote ---- I suspect that we may want something like a xml-commons/java/proposed or xml-commons/proposed/ to hold stuff that is proposed for xml-commons, but hasn't been voted on. Before anything beyond SAX2, DOM2, and JAXP gets committed to xml-commons, we need to come up with a firm set of criteria, that sits in some official looking document. As I have said before, the biggest danger of xml-commons is the danger of turning xml.apache.org into a bowl of spaghetti. Shouldn't there be an xml-commons mailing list? -scott --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org