Nicola Ken Barozzi wrote: > I don't like it to move under Jakarta Commons...
Can you give any reasons for that ? > 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. The problem is growing its commmunity and improving a bit the code and usability. The reason I proposed jakarta-commons is that it's the best place where this can happen. If Sam is not afraid of losing control over gump ( which may happen in j-c ), than I can't see any reason to not have it in j-c. >>>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. > > The descriptors were initially all in the Gump repo for better control > and cross-project check. > > 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?) Is 'relinquishing' control a problem ? If the 'bashing' results in finding problems and improving gump - or even increasing awarness - then it's should be welcomed. > 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. I think the real issue is where to host gump's code - i.e. the xslt and java code. Costin -- To unsubscribe, e-mail: <mailto:alexandria-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:alexandria-dev-help@;jakarta.apache.org>
