-1 of course
We can not just randomly merge/unmerge Lucene/Solr whenever a problem
comes up. It will still be the same community and therefore we need to
fix the way we interact with each other.
Could we all please try to be less stubborn and accusing and figure this
out? Obviously things like vetoing refactorings to move code into Lucene
is very counterproductive. But also Solr progress shouldn't suffer.
Hanging out with you guys at Apachecons always felt to me like we were
all good friends. Reading these discussions makes me think we can't
stand each other. Let's stop this passive-aggressive silliness and find
a good solution.
On 4/26/11 11:50 AM, Yonik Seeley wrote:
A single merged project works only when people are relatively on the same page,
and when people feel it's mutually beneficial. Recent events make it
clear that that
is no longer the case.
Improvements to Solr have been recently blocked and reverted on the
grounds that the new functionality was not immediately available to
non-Solr users.
This was obviously never part of the original idea (well actually - it was
considered but rejected as too onerous). But the past doesn't matter as
much as the present - about how people chose to act and interpret
things today.
https://issues.apache.org/jira/browse/SOLR-2272
http://markmail.org/message/unrvjfudcbgqatsy
Some people warned us against merging at the start, and I guess it
turns out they were right.
I no longer feel it's in Solr's best interests to remain under the same
PMC as Lucene-Java, and I know some other committers who have said
they feel like Lucene got the short end of the stick. But rather than
arguing about who's right (maybe both?) since enough of us feel it's no longer
mutually beneficial, we should stop fighting and just go our separate
ways.
Please VOTE to create a new Apache Solr TLP.
Here's my +1
-Yonik