From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Thread: 103376,deac256a05c84a59 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!news.agarik.com!usenet-fr.net!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: DOM and SAX parsing in Ada Date: 28 Jan 2005 04:57:12 -0500 Organization: Cuivre, Argent, Or Message-ID: References: <41900010.D28DD400@boeing.com> <9CWjd.17305$5K2.1356@attbi_s03> <1106223415.857525.176640@c13g2000cwb.googlegroups.com> <41F4DB6F.4090909@mailinator.com> <35nh12F4oe4caU1@individual.net> <35pmqtF4iqgimU1@individual.net> <1106820016.e20ede44b96063b70b5f6f5503a7b1a9@teranews> NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: melchior.cuivre.fr.eu.org 1106906255 86234 212.85.156.195 (28 Jan 2005 09:57:35 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Fri, 28 Jan 2005 09:57:35 +0000 (UTC) To: comp.lang.ada@ada-france.org Return-Path: In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: g2news1.google.com comp.lang.ada:8043 Date: 2005-01-28T04:57:12-05:00 Pascal Obry writes: > Martin Krischik writes: > > > So I would be in for a XML/Ada extension pack hostet at i.E. SourceForge. > > That's a very bad idea to me. Some of us agree, but you have not addressed the issue that, for XML/Ada at least, contributions are not available in a timely way. > Better to have one strong Ada tools that zillions of > not-well-supported forked ones. It is fine to have another project > to build an XML parser in Ada but for me a fork is really bad and > should happen only if there is *big* maintenance problem. Waiting a year for a contribution to be generally available counts as a "big" problem for me. > One good point on the Ada side is the strong standard. We really > want to build on this. Not a lot of libraries but some good, well > documented, safe ones that does the job. We all agree with that. > Personally I would not like to find an AWS fork. I've tried (and > will continue to) to work with the contributors to have patches > integrated. But it is true that patches are not always very easy to > integrate and requires some changes. We all agree with that as well. > Note that I know well the main XML/Ada maintainer and can tell you > that if a patch is not integrated yet there is certainly good > reasons. The issue is, after a patch is integrated, how long is it before it is available to others? > Another note. In this thread one guy (can't remember who sorry) talked about > CVS write access. That was me; it appeared to be an issue for Nick Roberts. > This is not serious. I'm not clear what you mean here; I was certainly "serious". > To have a write access to a project you really want to become part > of the project team, take responsibilities for part of it... and of > course you can't keep the copyright, this would be a problem for the > product in the long term. Ok, so you mean "it is not reasonable to grant write access to everyone who makes a contribution". That's fine. However, it is necessary for _everyone_ to have read access to a CVS repository, if you want to encourage comtributions to that repository. -- -- Stephe