commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <skitch...@apache.org>
Subject RE: [Digester] Question about ports
Date Sat, 10 Sep 2005 01:11:23 GMT
[Aargh - I hate top-posting!]

If someone wants to move Digester to Apache XML, I wouldn't object.
However I don't feel particularly motivated to do it myself.

I think the easiest way to deal with this particular case (python/ruby
versions of Digester) is for the ports to be separate projects at
sourceforge/rubyforge/etc. I'm happy to have links to those projects
from the Digester homepage and the Wiki. 

Running these projects as real Apache projects means that committers
must be Apache committers, which means project members (like Silas) need
to go through a fairly lengthy "trial" phase with an existing Apache
committer (or several) willing to evaluate patches etc. before being
proposed as official Apache committers. I don't know if any existing
Digester committers are python people - I'm certainly not. So it just
looks easier to run this stuff as an external project. Anyway, it's not
really the same project; it's just a project in a different language
that happens to share the same basic architectural concepts.

As I mentioned earlier, there is already an attempt to port this to ruby
at:
  http://rubyforge.org/projects/xmldigester/

Regards,

Simon

On Fri, 2005-09-09 at 15:23 -0400, James Carman wrote:
> I don't know what other folks think about moving Digester to Apache XML.
> But, if there are going to be any ports of it, that's where they belong.
> Any of the committers care to chime in?
> 
> -----Original Message-----
> From: Silas Snider [mailto:swsnider@gmail.com] 
> Sent: Friday, September 09, 2005 11:49 AM
> To: Jakarta Commons Developers List
> Subject: Re: [Digester] Question about ports
> 
> As I am also planning on porting it to Ruby, should I bother? Or should
> I just open my own (say) sourceforge project? Only reason I'm asking is
> that I have never participated in apache devlopment before, so I don't
> know what the accepted community norms are, etc.
> 
> Sincerely,
> Silas Snider
> 
> James Carman wrote:
> > It could possibly be argued that Digester belongs in Apache XML.  There
> > could probably be different "flavors" of it (a la Xerces) like DigesterJ,
> > Digesterl (digester/perl), or Digesterthon (digester/python).  Of course,
> > those are horrible names (except for maybe DigesterJ), but you get the
> > point.
> > 
> > -----Original Message-----
> > From: Silas Snider [mailto:swsnider@gmail.com] 
> > Sent: Friday, September 09, 2005 2:59 AM
> > To: commons-dev@jakarta.apache.org
> > Subject: [Digester] Question about ports
> > 
> > Dear List:
> > 	I was getting fed up with the lack of digester in python, so I
> > ported
> > it over. It's in testing right now, but I wanted to know if you knew of
> > a place for this kind of project (does apache do this, or a different
> > organization?)
> > 
> > Sincerely,
> > Silas Snider



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message