> > > > Did anyone object the last time you suggested this (a few months ago)? > > I proposed to moved a bunch of code (e.g. the eclipse-ui) from > the Apache tree > into a SF tree. Others found that it was splitting the community > and since we > don't have a large community... >
Is adding Xindice add-ons to the Apache tree an option. What is the disadvantage to keeping everything together on the Apache tree? 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. Does someone run the show here and make executive decisions about this kind of thing? Or is this a sort of democratic process? Frankly, I am not particularly invested in where code is kept or collaboration takes place. I simply want a place to put my Xindice Delphi API when it is ready so that others can use it, thus opening Xindice to a large new population of potential adopters. If there isn't a place to do this on the Apache tree, then, barring any reasonable objections, I will put it on SourceForge. Thanks, Pietro > But I'm still convinced that this is the way to go. > > > If not, since you have experience, please go ahead and set up a > new project > > for Xindice add-ons. > > It's better if other developers have that experience too. So I > won't volunteer > for setting up the project but I can have a look at your code and > give my 2 > cents if you want (but wait 1-2 weeks because I'm quite busy and > don't have > broadband right now) > > -Vladimir > > -- > Vladimir R. Bossicard > Apache Xindice - http://xml.apache.org/xindice >
