> Is adding Xindice add-ons to the Apache tree an option. What is the > disadvantage to keeping everything together on the Apache tree?
Everything is always an option and having some code on SF doesn't mean that it won't be included into the Apache tree. On the contratry: SF is often used to mature projects before they join Apache. Apache emphasis on "Community" and it's not IMO (only) a code repository. If you want to bring code into Apache, you must prove that you have a community of developers AND users. > Would it make sense to keep all of the development work on the Apache tree > but at the same time keep a copy of all of the production-level source and > binaries on SF? That way Xindice developers would have a forum at Apache > and potential users would have an easy access point at SF. Too much hassle. The current problem is that we should make a release but we first learn how to do it in the Apache infrastructure. Other projects do it successfully so there's no reason that Xindice can't do it too. > Does someone run the show here and make executive decisions about this kind > of thing? Or is this a sort of democratic process? democratic process > If there isn't a place to do > this on the Apache tree, then, barring any reasonable objections, I will > put it on SourceForge. Good decision. But it doesn't mean that the Delphi code can't ever be @ Apache. Before you start committing into SF, drop me a mail since I have some experience with the SF infrastructure. I would also like to see the HTTP and WebDAV servlets for the latest CVS code but haven't had the time to start working on it. -Vladimir -- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
