Stefan Bodewig wrote:
Conceptually, Gump has a higher goal than just be part of Jakarta, and it's possibly also cross-language. Remember I'm also a Forrest committer, so I see the synergy between the projects of higher value to Apache, and keep pursuing that vision.On Mon, 11 Nov 2002, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:I second Jon, he is right.+0. I'm not that Gump qualifies from the community aspect for a top-level project.
I understand that community-wise it's not (yet) a top-level project, but I don't like it to move under Jakarta Commons...
Probably ATM simply moving the codebase to its own gump CVS repo and make its own mailing list would solve this handily, since we remain ATM under Jakarta but move out of the Alexandria skin.
One step at a time.
I'm in favor of moving it out of the Alexandria module, BTW.
+1
The descriptors were initially all in the Gump repo for better control and cross-project check.A solution would be to make two repos: gump and gump-repos, and have gump-repos open to all *Apache* committers.Why? You can already host descriptors outside of Gump's control.
Making a common repo would continue this tentative, while not relinquishing control of the whole Gump codebase to people that could start bashing (am I being too defensive here?)
As a start though I'd probably keep things as is, and suggest all committers that ask the descriptor to be patched to move it to their codebase and have it administered. Probably.
--
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>
