> I wouldn't take silence as a lack of interest, just a lack of time to dig > into it.
That's what I hoped it was ;) > I didn't look at any of the code, but playing arround with the UI it > seemed really slick. Assuming there aren't any licence incompatibilities > with the libraries the app depends on, i think it would probably make a > great contrib. (hmm... actually i would probably categorize this as a > "client" not a contrib, but that's a semantic question) I've checked the licenses, all of the libraries are either BSD or Apache licensed, the icons are creative commons share alike. > I would start be emailing solr-user and seeing what the whole Solr > community thinks of it -- while it may serve as a good starting point for > Spring folks wanting to wire up their own UIs, I also think non-Java folks > looking for a glossier UI then the simple admin screens Solr has would > really get into it. Ok, I wasn't sure about emailing solr-user, as this in its current stage is really just related to development. > the next step from there is just submitting a patch. Well, it'd be a really huge patch. I think a better approach would be to "merge" the stuff in my repository into the Solr repository, especially as things such as build scripts need to be adjusted. For example the integration tests need a solr war, so it might be good to integrate that with the overall build process. If everybody is ok with that, I think the easiest way would be to give me commit access -- not only to merge it into the existing repository, but also for maintaining it (which I'd be happy to do). Lars
