<snip> I'm definitely looking for ideas - especially ones of finding enough thoroughly researched test scripts so that we could more easily validate changes. </snip>
Surely the existing code was released after passing a set of "thoroughly researched test scripts." Aren't these test scripts are still available in CVS or Subversion. I assume what you want is for submitters to provide not just code patches, but also updated, documented tests showing that the new code performs correctly, conforming to specifications. Right? Thanks, Donald Holliday -----Original Message----- From: Shane Curcuru [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2008 8:12 AM To: commons-dev@xml.apache.org Cc: Earl Hood; Norman Walsh Subject: Re: Future of xml-commons-resolver development and maintenance Indeed, the ASF is a meritocracy, and welcomes input from everyone, both in the form of patches from everyone, as well as code checkins, once someone becomes a committer on any project. The issue here is validating that the patches submitted properly follow the various XML-ish specs available. Sadly, I've forgotten much of my real XML knowledge. We also would need to clearly document any changes from past behavior that we added to the tool, to avoid surprise by anyone who uses the resolver in an existing production environment. The trick to building up community again is to work with interested new volunteers. Trust me, I feel *really* bad that I don't have more time myself. If it were just a case of eyeballing the code and running simple programming tests, I'd be doing it already; I could make time for that. But when it comes to properly processing documents and catalogs in strict XML land, and testing that we're not breaking some standard or behaving completely differently than what people expect - then I get worried. I'm definitely looking for ideas - especially ones of finding enough thoroughly researched test scripts so that we could more easily validate changes. As always, the last resort is to fork the code, which of course the ASF license generally allows you to do. But I'd love to find a way to draw in new volunteers while maintaining our strict standards support. - Shane Michael Glavassevich <[EMAIL PROTECTED]> wrote: > Hi Earl, > > In case it wasn't obvious, anyone can start contributing to the > project if they're interested and potentially become one of its > committers. The caveat being that there needs to be an existing > committer around who has the time and ability to review patches and > also PMC oversight for releases and other project issues. I can > certainly provide the latter but neither have the time or knowledge > (don't know the code at all or the catalog spec that well) to do the former. > > I'm sure this isn't the first time that an attempt has been made to > revive a component/sub-project with no active committers. I wonder > how other ASF projects have dealt with this in the past. > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > > [EMAIL PROTECTED] wrote on 06/15/2008 03:06:28 PM: > > > Norman, > > > > Recently, I have made a few changes to my local version of the resolver > > to address bugs with it. I have posted my patches to ASF bugzilla. > > > > However, it appears that the development of the resolver is stagnant, > > with 15 open bugs, with some quite old. > > > > If you no longer have the time and resources to work on the > > resolver, are you open to transitioning maintenance to others > > whom have cycles to spare? > > > > Thanks, > > > > --ewh > > -- > > Earl Hood, <[EMAIL PROTECTED]> > > Web: <http://www.earlhood.com/> > > PGP Public Key: <http://www.earlhood.com/gpgpubkey.txt>
