On Sun, 12 Mar 2006, Stephen Colebourne wrote:
DbUtils and DBCP to db.apache.org sounds like a win to me; DBCP would
point back to Jakarta for a dependency on [pool], but that helps to
foster intra-project involvement.
Betwixt, Digester and JXPath strike me as a bit more to swallow and XML
might not want to taking such bites. You want to go ahead and ask them?
Martin Cooper wrote:
I think this whole thing is putting the cart before the horse. You're in
the
process of destroying Commons, not just dismantling it, and for no good
reason that I can see. The people involved with Digester should be the ones
to initiate a discussion about whether or not they want to take Digester
elsewhere. As it is, this is coming across more like "why don't you guys go
away, somewhere far away, 'cos we think that's a good idea".
+1. I believe there is the potential to group Jakarta around perhaps 4 or 5
mailing lists groupings instead of 15+ now. But it cannot be forced.
Right. My first response was that we needed to be sure community would go
with them. My gut instinct is that the DB ones would go - there's somewhat
of an overlap between db.apache and commons, but I'm not convinced the XML
ones would.
Asking the question on commons-dev should initiate discussion with those
who care about Digester - ideally asking it here would too but they might
not be paying attention I guess. Waiting for every individual codebase to
individually decide to get active and discuss non-code issues is a
non-starter from the beginning.
Just because db-commons and xml-commons exist doesn't mean that we should
'outsource' to them. OSS isn't like that.
That's no reason to ignore the idea though. OSS is sometimes like that.
As I've said before, its in our nature as programmers to look for
abstractions and hierarchies - to look for order. Community isn't that
convenient.
This still comes down to the basic issue :) I believe that as Thomas is a
Jakarta committer it is not an idea being forced from the outside, but
something from the inside. As he's a DB PMC member, then at least half is
very much from the inside - and I think he was involved in the Commons SQL
-> DdlUtils move.
Even in the model where we only look to those with substantial commits to
a codebase - some of the inactive ones are going to be left behind and
will need someone to be suggesting a direction for them.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
