You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Silas Snider <sw...@gmail.com> on 2005/09/09 08:59:22 UTC
[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
RE: [Digester] Question about ports
Posted by James Carman <ja...@carmanconsulting.com>.
I wasn't aware that (again, I'm somewhat of a newbie) there had to be a
board member for each TLP within Apache. Of course, I didn't realize that
all projects within Apache XML are TLPs. If XML itself were a TLP with each
project within it merely being a subproject (a la Jakarta), then I would say
that Digester (or DigesterJ) should be a subproject of it. But, if it's
structured as you say it is, then maybe you're right. The way I would see
the hierarchy would be:
Apache -> XML -> Digester -> different flavors (perl, ruby, Java, python,
etc.).
So, Digester (as a concept; like logging) would be a subproject within XML
(not a TLP), since it's XML-specific.
-----Original Message-----
From: robert burrell donkin [mailto:robertburrelldonkin@blueyonder.co.uk]
Sent: Sunday, September 11, 2005 5:51 PM
To: Jakarta Commons Developers List
Subject: RE: [Digester] Question about ports
On Sun, 2005-09-11 at 17:11 -0400, James Carman wrote:
> Just make sure you use the apache license!
+1
use version 2 :)
> I think the idea/concept of
> Digester is big enough to merit a TLP (or group of them). And, since it's
> an XML-specific technology, I think it belongs within the XML group. Then
> again, I'm no expert here, but it seems an obvious fit to me.
IMHO too many small TLPs would bring difficulties. for example, i'm not
sure whether it would make sense to have an ASF board member for
digester.
what has been in the air (and in my mind) for a little while is the idea
of a TLP bring together various code-centric mapping and binding
technologies from both inside and outside apache but IMHO the time isn't
right (as yet).
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Digester] Question about ports
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sun, 2005-09-11 at 17:11 -0400, James Carman wrote:
> Just make sure you use the apache license!
+1
use version 2 :)
> I think the idea/concept of
> Digester is big enough to merit a TLP (or group of them). And, since it's
> an XML-specific technology, I think it belongs within the XML group. Then
> again, I'm no expert here, but it seems an obvious fit to me.
IMHO too many small TLPs would bring difficulties. for example, i'm not
sure whether it would make sense to have an ASF board member for
digester.
what has been in the air (and in my mind) for a little while is the idea
of a TLP bring together various code-centric mapping and binding
technologies from both inside and outside apache but IMHO the time isn't
right (as yet).
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Digester] Question about ports
Posted by James Carman <ja...@carmanconsulting.com>.
Just make sure you use the apache license! I think the idea/concept of
Digester is big enough to merit a TLP (or group of them). And, since it's
an XML-specific technology, I think it belongs within the XML group. Then
again, I'm no expert here, but it seems an obvious fit to me.
-----Original Message-----
From: robert burrell donkin [mailto:robertburrelldonkin@blueyonder.co.uk]
Sent: Sunday, September 11, 2005 4:46 PM
To: Jakarta Commons Developers List
Subject: RE: [Digester] Question about ports
On Sat, 2005-09-10 at 13:11 +1200, Simon Kitching wrote:
> [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.
xml is now a federation of top level projects. IMHO digester isn't big
enough to be a TLP.
> 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.
+1
feel free to post stuff to this list (announcements and so on or
questions) if you want...
> 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.
+1
apache is changing quite a lot at the moment and a lot of process stuff
is still being developed and documented. there's quite a danger of
losing momentum if you become entangled with the process ATM. IMHO
better to start coding now: there's always the possibility of moving to
apache later.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Digester] Question about ports
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sat, 2005-09-10 at 13:11 +1200, Simon Kitching wrote:
> [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.
xml is now a federation of top level projects. IMHO digester isn't big
enough to be a TLP.
> 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.
+1
feel free to post stuff to this list (announcements and so on or
questions) if you want...
> 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.
+1
apache is changing quite a lot at the moment and a lot of process stuff
is still being developed and documented. there's quite a danger of
losing momentum if you become entangled with the process ATM. IMHO
better to start coding now: there's always the possibility of moving to
apache later.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Digester] Question about ports
Posted by Simon Kitching <sk...@apache.org>.
[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
RE: [Digester] Question about ports
Posted by James Carman <ja...@carmanconsulting.com>.
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
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Digester] Question about ports
Posted by Silas Snider <sw...@gmail.com>.
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
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Digester] Question about ports
Posted by James Carman <ja...@carmanconsulting.com>.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org