Costin Manolache wrote:
First of all, thank you all for listening to my points and commenting.Sam Ruby wrote:I have been *trying* to relinquish control for about a year now.
It shows that you somewhat value my opinions and take time to convince me. I appreciate that, so I'd better think a second and give a pretty damn good reply ;-)
I've thought and rethought and came to a conclusion that I was touting the wrong solution to my concerns, so let me state the concerns first.
-oOo-
Some background: I started becoming interested in Gump while making Centipede http://www.krysalis.org/centipede/. I started using the Gump descriptor format in Centipede, and tried (slowly) to understand how to evlove it and use it to build day2day builds.
Costin knows a bit about this from the Ant side, that has turned into the "donation" of the XmlPropertyTask and to numerous patches to his embed proposal.
Anyway, at that time Maven was starting to steam up too, and we tried to convince them to come to a common descriptor format, to no avail.
I asked also to come to a common project, but even with my best intentions and with users asking for it, the result was that I was "kindly" requested to get out of the way and stop bugging.
Then I continued Centipede with the Gump descriptor, started using the enhanced version in many projects, committed an editor for it to the Gump codebase, tried to refactor it to make it a bit easier (no success unfortunately), and started using a modified version of it in Cocoon to build subprojects from Ant.
I have a lot in that descriptor. Maven uses a different version, that is incompatible with it, since there is no 1-1 relationship with them.
A Maven project can be written as a Gump project, but a Gump project can result in many Maven projects. In Centipede we have done many considerations on it, and have come to a design that uses it.
So, trying to get to the point, my concern is that the Gump descriptor can evlove with respect and cooperation with the Centipede and the Forrest communities.
Centipede is able now to use it to build projects with its info, and will soon be able to do it with respect to dependencies.
This would make it possible for projects to use Gump descriptor data daily and keep the descriptors uptodate.
This is my concern. Now the possible solution:
My ideal would be to have a reposititory in which every Apache committer has commit access. Those that wish to contribute are welcome to. All I would ask is that people who express an opinion are willing to do the work and provide support for the results.
This I agree with. It's not in disaccord with what I need, so +1
This is the only negative thing about moving to jakarta-commons: notI would be happy to make Centipede developers more involved in Gump, and take part in the decisions on it, since the descriptor is heavily used by us.
every apache committer has commit access there ( yet ).
However quite a few xml.apache people are committers to j-c, and I think
the community is quite open to any apache committer who is interested.
But some have said that they will not partecipate on Jakarta Commons, because of the massive quantity of posts on that list that they find overwhelming and because they feel uncomfortable in that environment.
We also have concerns about the drastic changes that could be taken on the descriptor format, and don't want it to happen and break our efforts to use Gump descriptors in day2day builds in Ant.
What about this then (please comment per point why it wouldn't work):
- a Gump mailing list
- a Gump CVS module open to *all* Apache committers, but with
us giving oversight on the process
- commit access given also to selected Centipede developers
Costin, Sam, are you willing to help me in not making this disruptive for Centipede?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:alexandria-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:alexandria-dev-help@;jakarta.apache.org>
