Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Varun Thacker]

+1 (binding)

On Tue, May 12, 2020 at 9:18 PM Koji Sekiguchi 
wrote:

> +1
>
> Koji
>
> On 2020/05/12 16:36, Dawid Weiss wrote:
> > Dear Lucene and Solr developers!
> >
> > According to an earlier [DISCUSS] thread on the dev list [2], I am
> > calling for a vote on the proposal to make Solr a top-level Apache
> > project (TLP) and separate Lucene and Solr development into two
> > independent entities.
> >
> > To quickly recap the reasons and consequences of such a move: it seems
> > like the reasons for the initial merge of Lucene and Solr, around 10
> > years ago, have been achieved. Both projects are in good shape and
> > exhibit signs of independence already (mailing lists, committers,
> > patch flow). There are many technical considerations that would make
> > development much easier if we move Solr out into its own TLP.
> >
> > We discussed this issue [2] and both PMC members and committers had a
> > chance to review all the pros and cons and express their views. The
> > discussion showed that there are clearly different opinions on the
> > matter - some people are in favor, some are neutral, others are
> > against or not seeing the point of additional labor. Realistically, I
> > don't think reaching 100% level consensus is going to be possible --
> > we are a diverse bunch with different opinions and personalities. I
> > firmly believe this is the right direction hence the decision to put
> > it under the voting process. Should something take a wrong turn in the
> > future (as some folks worry it may), all blame is on me.
> >
> > Therefore, the proposal is to separate Solr from under Lucene TLP, and
> > make it a TLP on its own. The initial structure of the new PMC,
> > committer base, git repositories and other managerial aspects can be
> > worked out during the process if the decision passes.
> >
> > Please indicate one of the following (see [1] for guidelines):
> >
> > [ ] +1 - yes, I vote for the proposal
> > [ ] -1 - no, I vote against the proposal
> >
> > Please note that anyone in the Lucene+Solr community is invited to
> > express their opinion, though only Lucene+Solr committers cast binding
> > votes (indicate non-binding votes in your reply, please).
> >
> > The vote will be active for a week to give everyone a chance to read
> > and cast a vote.
> >
> > Dawid
> >
> > [1] https://www.apache.org/foundation/voting.html
> > [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Koji Sekiguchi]

+1

Koji

On 2020/05/12 16:36, Dawid Weiss wrote:

Dear Lucene and Solr developers!

According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent entities.

To quickly recap the reasons and consequences of such a move: it seems
like the reasons for the initial merge of Lucene and Solr, around 10
years ago, have been achieved. Both projects are in good shape and
exhibit signs of independence already (mailing lists, committers,
patch flow). There are many technical considerations that would make
development much easier if we move Solr out into its own TLP.

We discussed this issue [2] and both PMC members and committers had a
chance to review all the pros and cons and express their views. The
discussion showed that there are clearly different opinions on the
matter - some people are in favor, some are neutral, others are
against or not seeing the point of additional labor. Realistically, I
don't think reaching 100% level consensus is going to be possible --
we are a diverse bunch with different opinions and personalities. I
firmly believe this is the right direction hence the decision to put
it under the voting process. Should something take a wrong turn in the
future (as some folks worry it may), all blame is on me.

Therefore, the proposal is to separate Solr from under Lucene TLP, and
make it a TLP on its own. The initial structure of the new PMC,
committer base, git repositories and other managerial aspects can be
worked out during the process if the decision passes.

Please indicate one of the following (see [1] for guidelines):

[ ] +1 - yes, I vote for the proposal
[ ] -1 - no, I vote against the proposal

Please note that anyone in the Lucene+Solr community is invited to
express their opinion, though only Lucene+Solr committers cast binding
votes (indicate non-binding votes in your reply, please).

The vote will be active for a week to give everyone a chance to read
and cast a vote.

Dawid

[1] https://www.apache.org/foundation/voting.html
[2] 
https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Shai Erera]

I agree this is a procedural vote. Here's my +1 for the proposal.

Shai

On Tue, May 12, 2020, 23:07 Simon Willnauer 
wrote:

> I agree this is not a code change category vote. It’s a majority vote. -1s
> are not vetos.
>
> Simon
>
> On 12. May 2020, at 21:17, Atri Sharma  wrote:
>
> 
> I would argue against that — this is more of a project level decision with
> no changes to the core code base per se — more of restructuring of it. Sort
> of how a sub project becomes a TLP.
>
> On Wed, 13 May 2020 at 00:38, Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
>
>> This is in the code modification category, since code will be modified as
>> result of this proposal.
>>
>> On Wed, 13 May, 2020, 12:27 am Shawn Heisey,  wrote:
>>
>>> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
>>> > According to an earlier [DISCUSS] thread on the dev list [2], I am
>>> > calling for a vote on the proposal to make Solr a top-level Apache
>>> > project (TLP) and separate Lucene and Solr development into two
>>> > independent entities.
>>>
>>> +1 (pmc)
>>>
>>> We should clarify exactly what kind of vote this is.  If it is in the
>>> "code modification" category, then a single -1 vote would be enough to
>>> defeat the proposal.  There are already some -1 votes.
>>>
>>> Thanks,
>>> Shawn
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>> --
> Regards,
>
> Atri
> Apache Concerted
>
>

Re: [DISCUSS] 8.5.2 Release?

[Mike Drob]

Alan and I worked out how to do this on the PR, and the change was made
without affecting the API signatures.

I am now working on cutting the bugfix release, it doesn't look like there
are any more pending issues to backport. Please follow the usual
conventions if you need to backport to this branch including giving a
notification here.

On Sat, May 9, 2020 at 7:07 AM Adrien Grand  wrote:

> I'd rather not change signatures on a patch release. Are there ways we
> could have the bug fix on 8.5 without backporting this API change?
>
> On Fri, May 8, 2020 at 5:18 PM Mike Drob  wrote:
>
>> While back porting LUCENE-9350, I ran into needing LUCENE-9349[1] which
>> introduces a small API change to QueryVisitor. Do we think this is
>> acceptable in a bug fix release, or do I need to figure out how to back
>> port the changes without it?
>>
>> [1]: https://issues.apache.org/jira/browse/LUCENE-9349
>>
>> On 2020/05/07 18:30:53, Alan Woodward  wrote:
>> > +1, thanks for volunteering Mike
>> >
>> > > On 7 May 2020, at 19:03, Anshum Gupta > > wrote:
>> > >
>> > > Thanks for doing this, Mike.
>> > > +1 to the 8.5.2 release.
>> > >
>> > > On Thu, May 7, 2020 at 10:13 AM Mike Drob > md...@apache.org>> wrote:
>> > > Devs,
>> > >
>> > > I know that we had 8.5.1 only a few weeks ago, but with the fix for
>> LUCENE-9350 I think we should consider another bug-fix. I know that without
>> it I will be explicitly recommending several users to stay off of 8.5.x on
>> their upgrade plans. There are some pretty scary looking charts on
>> SOLR-14428 that describe the impact of the bug in more detail.
>> > >
>> > > I'd be happy to volunteer as RM for this, would probably be looking
>> at trying to get it a vote started sometime next week.
>> > >
>> > > Thanks,
>> > > Mike
>> > >
>> > >
>> > > https://issues.apache.org/jira/browse/SOLR-14428 <
>> https://issues.apache.org/jira/browse/SOLR-14428>
>> > > https://issues.apache.org/jira/browse/LUCENE-9350 <
>> https://issues.apache.org/jira/browse/LUCENE-9350>
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > dev-unsubscr...@lucene.apache.org>
>> > > For additional commands, e-mail: dev-h...@lucene.apache.org > dev-h...@lucene.apache.org>
>> > >
>> > >
>> > >
>> > > --
>> > > Anshum Gupta
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>
>
> --
> Adrien
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Simon Willnauer]

I agree this is not a code change category vote. It’s a majority vote. -1s are 
not vetos.

Simon

> On 12. May 2020, at 21:17, Atri Sharma  wrote:
> 
> 
> I would argue against that — this is more of a project level decision with no 
> changes to the core code base per se — more of restructuring of it. Sort of 
> how a sub project becomes a TLP.
> 
>> On Wed, 13 May 2020 at 00:38, Ishan Chattopadhyaya 
>>  wrote:
>> This is in the code modification category, since code will be modified as 
>> result of this proposal.
>> 
>>> On Wed, 13 May, 2020, 12:27 am Shawn Heisey,  wrote:
>>> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
>>> > According to an earlier [DISCUSS] thread on the dev list [2], I am
>>> > calling for a vote on the proposal to make Solr a top-level Apache
>>> > project (TLP) and separate Lucene and Solr development into two
>>> > independent entities.
>>> 
>>> +1 (pmc)
>>> 
>>> We should clarify exactly what kind of vote this is.  If it is in the 
>>> "code modification" category, then a single -1 vote would be enough to 
>>> defeat the proposal.  There are already some -1 votes.
>>> 
>>> Thanks,
>>> Shawn
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>> 
> -- 
> Regards,
> 
> Atri
> Apache Concerted

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Anshum Gupta]

Dawid,

Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).


I wanted to clarify that only PMC members cast binding votes and not
committers.

 Also, community votes are as important as it would help a lot of people
also decide what is the right direction to move forward w.r.t. the
community.

On Tue, May 12, 2020 at 12:37 AM Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Anshum Gupta

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Anshum Gupta]

I am about to re-read the rules here but I think this is a procedural vote.

Also, considering almost all procedural changes would impact the code in
some way, I don't think anything would pass if we were to put stuff in the
"code modification" category as getting a single veto would stop all
progress.

-Anshum

On Tue, May 12, 2020 at 12:17 PM Atri Sharma  wrote:

> I would argue against that — this is more of a project level decision with
> no changes to the core code base per se — more of restructuring of it. Sort
> of how a sub project becomes a TLP.
>
> On Wed, 13 May 2020 at 00:38, Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
>
>> This is in the code modification category, since code will be modified as
>> result of this proposal.
>>
>> On Wed, 13 May, 2020, 12:27 am Shawn Heisey,  wrote:
>>
>>> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
>>> > According to an earlier [DISCUSS] thread on the dev list [2], I am
>>> > calling for a vote on the proposal to make Solr a top-level Apache
>>> > project (TLP) and separate Lucene and Solr development into two
>>> > independent entities.
>>>
>>> +1 (pmc)
>>>
>>> We should clarify exactly what kind of vote this is.  If it is in the
>>> "code modification" category, then a single -1 vote would be enough to
>>> defeat the proposal.  There are already some -1 votes.
>>>
>>> Thanks,
>>> Shawn
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>> --
> Regards,
>
> Atri
> Apache Concerted
>


-- 
Anshum Gupta

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

[Namgyu Kim]

It's hard to make a decision because it seems to have pros and cons.
Basically, I agree to separate but there are some questions.
So I don't not vote right now.

1) Release version
Currently, versions of Lucene and Solr are aligned, how will they be
managed in the future?
Other people took Elasticsearch as an example... But it was an independent
project from the beginning.
So there is no problem with the Lucene version. (Elasticsearch 7.7 and
Lucene 8.5.1)
I'm sure if we make solr as an independent project, it will make cracks
about the version structure. (like Lucene 8.6.2 and Solr 8.9.1)
But it's also strange to suddenly start a new version of the Solr. (Solr
1.0)
Of course it's a matter of adaption, but it's likely to cause some
confusion for existing users.

2) Complementary relationship
When Lucene and Solr are built together, Solr can always maintain the
latest Lucene.
In my personal opinion, it's a great advantage of Solr.
Because Solr doesn't have to suffer from Lucene API changes and has latest
library.
But it will be difficult if Solr becomes independent.
If Solr tracks the master branch of Lucene on separate repository(project),
can it always check and reflect Lucene's API changes?

On Tue, May 12, 2020 at 10:12 PM Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:

> I'll give a perspective that comes more from the user's / "market" point
> of view as at OSC we onboard lots of new organizations into Solr.
>
> - Most new users incorrectly think of Solr as an independent Apache
> project, and many will have little knowledge or awareness of Lucene itself
> until given the full history of Lucene, Solr, Elasticsearch... or they have
> to dive into the code/write a plugin
>
> - Most orgs / managers think in terms of "Solr" (as in "Solr" vs
> "Elasticsearch" vs "Vespa, etc). So the starting point for new devs / folks
> is from the Solr angle
>
> - Lucene, when discussed, is understood more colloquially as a Solr
> dependency
>
> - If someone brings down the code to do some kind of work or
> investigation, there's typically surprise that Lucene and Solr are bundled
> together.
>
> - There's further surprise as the projects are indeed so different: Lucene
> and Solr tests, for example look little alike. They seem to have different
> coding syles / practices. One has more server-like and distributed system
> concerns; the other is clearly a low-level library for doing search work...
>
> I personally have a hard time explaining to new users the rationale for
> keeping these together, and it only increases the barrier to entry (to both
> projects) to have this added complexity of two very different code bases
> munged together.
>
> Just my 2 cents...
> -Doug
>
> On Tue, May 12, 2020 at 7:30 AM Alan Woodward 
> wrote:
>
>> One advantage I find with the way Elasticsearch and Lucene interact is
>> that ES doesn’t depend on the master branch.  We upgrade our master branch
>> frequently to keep up to date with the latest release branch, and that lets
>> us find regressions or API problems pretty quickly, but it also insulates
>> us from having to make big changes immediately.  I find this really useful
>> for things like deprecations.  Let’s say we deprecate a particular API in
>> the release branch, and remove it entirely in master.  Currently, that
>> means Solr needs to immediately switch over to the new API in its master
>> branch.  But the whole point of doing deprecations first is that it gives
>> users time to find issues with the replacements - if we find that the
>> replacement API doesn’t quite fit in ES, we have time to work out either
>> how to change our code, or to improve the new API, but because the
>> deprecated version is still there we’re not blocked from upgrading and
>> getting other improvements.  Solr, meanwhile, may end up with a hacky
>> workaround because that’s what got tests passing for the Lucene developer;
>> or worse, we end up just copying the deprecated API wholesale into Solr and
>> abandoning it there - witness TrieField or UninvertingReader.
>>
>> > On 11 May 2020, at 19:05, Atri Sharma  wrote:
>> >
>> > My two cents:
>> >
>> > As a Lucene heavy developer, I have several found maintaining Solr
>> > dependencies while making large changes a bit cumbersome. I believe
>> > Lucene and Solr should exist in a symbiotic relationship but not
>> > tightly coupled with each other.
>> >
>> >
>> > On Mon, May 11, 2020 at 7:22 PM Erik Hatcher 
>> wrote:
>> >>
>> >> Without reading much or replying to any specific points made on this
>> thread, here's my raw thoughts on this age-old topic (finally  coming
>> out of my cocoon after taking things in for a bit)
>> >>
>> >> Solr is a search -server- with distributed capabilities, that
>> leverages the magic of Lucene underneath.  Solr depends on Lucene, is a
>> consumer of it.  Lucene is a tight search -library- with little to no
>> external dependencies.  Their purposes and end-users are different.
>> >>
>> >> I was never really 

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Dawid Weiss]

This is a procedural vote. Code is not affected. The future of each
project diverges from the same git commit.

Dawid

On Tue, May 12, 2020 at 9:08 PM Ishan Chattopadhyaya
 wrote:
>
> This is in the code modification category, since code will be modified as 
> result of this proposal.
>
> On Wed, 13 May, 2020, 12:27 am Shawn Heisey,  wrote:
>>
>> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
>> > According to an earlier [DISCUSS] thread on the dev list [2], I am
>> > calling for a vote on the proposal to make Solr a top-level Apache
>> > project (TLP) and separate Lucene and Solr development into two
>> > independent entities.
>>
>> +1 (pmc)
>>
>> We should clarify exactly what kind of vote this is.  If it is in the
>> "code modification" category, then a single -1 vote would be enough to
>> defeat the proposal.  There are already some -1 votes.
>>
>> Thanks,
>> Shawn
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Atri Sharma]

I would argue against that — this is more of a project level decision with
no changes to the core code base per se — more of restructuring of it. Sort
of how a sub project becomes a TLP.

On Wed, 13 May 2020 at 00:38, Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:

> This is in the code modification category, since code will be modified as
> result of this proposal.
>
> On Wed, 13 May, 2020, 12:27 am Shawn Heisey,  wrote:
>
>> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
>> > According to an earlier [DISCUSS] thread on the dev list [2], I am
>> > calling for a vote on the proposal to make Solr a top-level Apache
>> > project (TLP) and separate Lucene and Solr development into two
>> > independent entities.
>>
>> +1 (pmc)
>>
>> We should clarify exactly what kind of vote this is.  If it is in the
>> "code modification" category, then a single -1 vote would be enough to
>> defeat the proposal.  There are already some -1 votes.
>>
>> Thanks,
>> Shawn
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>> --
Regards,

Atri
Apache Concerted

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Ishan Chattopadhyaya]

This is in the code modification category, since code will be modified as
result of this proposal.

On Wed, 13 May, 2020, 12:27 am Shawn Heisey,  wrote:

> On 5/12/2020 1:36 AM, Dawid Weiss wrote:
> > According to an earlier [DISCUSS] thread on the dev list [2], I am
> > calling for a vote on the proposal to make Solr a top-level Apache
> > project (TLP) and separate Lucene and Solr development into two
> > independent entities.
>
> +1 (pmc)
>
> We should clarify exactly what kind of vote this is.  If it is in the
> "code modification" category, then a single -1 vote would be enough to
> defeat the proposal.  There are already some -1 votes.
>
> Thanks,
> Shawn
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Shawn Heisey]

On 5/12/2020 1:36 AM, Dawid Weiss wrote:

According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent entities.


+1 (pmc)

We should clarify exactly what kind of vote this is.  If it is in the 
"code modification" category, then a single -1 vote would be enough to 
defeat the proposal.  There are already some -1 votes.


Thanks,
Shawn

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Mike Drob]

-1 (committer)

On Tue, May 12, 2020 at 1:14 PM Chris Hostetter 
wrote:

>
> : Therefore, the proposal is to separate Solr from under Lucene TLP, and
> : make it a TLP on its own. The initial structure of the new PMC,
> : committer base, git repositories and other managerial aspects can be
> : worked out during the process if the decision passes.
> :
> : Please indicate one of the following (see [1] for guidelines):
> :
> : [ ] +1 - yes, I vote for the proposal
> : [ ] -1 - no, I vote against the proposal
>
> -1
>
> (non-binding)
>
>
> -Hoss
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Chris Hostetter]

: Therefore, the proposal is to separate Solr from under Lucene TLP, and
: make it a TLP on its own. The initial structure of the new PMC,
: committer base, git repositories and other managerial aspects can be
: worked out during the process if the decision passes.
: 
: Please indicate one of the following (see [1] for guidelines):
: 
: [ ] +1 - yes, I vote for the proposal
: [ ] -1 - no, I vote against the proposal

-1 

(non-binding)


-Hoss


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Anshum Gupta]

-1 (binding)

On Tue, May 12, 2020 at 12:37 AM Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Anshum Gupta

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Michael Sokolov]

+1

On Tue, May 12, 2020 at 11:20 AM Ryan Ernst  wrote:
>
> +1 (binding)
>
> On Tue, May 12, 2020 at 12:37 AM Dawid Weiss  wrote:
>>
>> Dear Lucene and Solr developers!
>>
>> According to an earlier [DISCUSS] thread on the dev list [2], I am
>> calling for a vote on the proposal to make Solr a top-level Apache
>> project (TLP) and separate Lucene and Solr development into two
>> independent entities.
>>
>> To quickly recap the reasons and consequences of such a move: it seems
>> like the reasons for the initial merge of Lucene and Solr, around 10
>> years ago, have been achieved. Both projects are in good shape and
>> exhibit signs of independence already (mailing lists, committers,
>> patch flow). There are many technical considerations that would make
>> development much easier if we move Solr out into its own TLP.
>>
>> We discussed this issue [2] and both PMC members and committers had a
>> chance to review all the pros and cons and express their views. The
>> discussion showed that there are clearly different opinions on the
>> matter - some people are in favor, some are neutral, others are
>> against or not seeing the point of additional labor. Realistically, I
>> don't think reaching 100% level consensus is going to be possible --
>> we are a diverse bunch with different opinions and personalities. I
>> firmly believe this is the right direction hence the decision to put
>> it under the voting process. Should something take a wrong turn in the
>> future (as some folks worry it may), all blame is on me.
>>
>> Therefore, the proposal is to separate Solr from under Lucene TLP, and
>> make it a TLP on its own. The initial structure of the new PMC,
>> committer base, git repositories and other managerial aspects can be
>> worked out during the process if the decision passes.
>>
>> Please indicate one of the following (see [1] for guidelines):
>>
>> [ ] +1 - yes, I vote for the proposal
>> [ ] -1 - no, I vote against the proposal
>>
>> Please note that anyone in the Lucene+Solr community is invited to
>> express their opinion, though only Lucene+Solr committers cast binding
>> votes (indicate non-binding votes in your reply, please).
>>
>> The vote will be active for a week to give everyone a chance to read
>> and cast a vote.
>>
>> Dawid
>>
>> [1] https://www.apache.org/foundation/voting.html
>> [2] 
>> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [jira] [Commented] (SOLR-12823) remove clusterstate.json in Lucene/Solr 8.0

[Jan Høydahl]

Would appreciate any contribution, Ilan.

Please look at https://issues.apache.org/jira/browse/SOLR-12823 and contribute 
there (create a JIRA user if necessary).

Jan

> 12. mai 2020 kl. 17:06 skrev Ilan Ginzburg :
> 
> I could work on a PR to remove it in Solr 9, unless you think it's
> super tricky work.
> 
> Ilan
> 
> On Tue, May 12, 2020 at 3:32 PM Erick Erickson  
> wrote:
>> 
>> Definitely +1, but I won’t have the bandwidth to help.
>> 
>>> On May 12, 2020, at 9:03 AM, Jan Høydahl (Jira)  wrote:
>>> 
>>> 
>>>   [ 
>>> https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105402#comment-17105402
>>>  ]
>>> 
>>> Jan Høydahl commented on SOLR-12823:
>>> 
>>> 
>>> Any plan to remove clusterstate.json for Solr 9? And perhaps let Overseer 
>>> fail if it is non-empty, i.e. if not all collections are migrated to format 
>>> 2?
>>> 
 remove clusterstate.json in Lucene/Solr 8.0
 ---
 
   Key: SOLR-12823
   URL: https://issues.apache.org/jira/browse/SOLR-12823
   Project: Solr
Issue Type: Task
  Reporter: Varun Thacker
  Priority: Major
 
 clusterstate.json is an artifact of a pre 5.0 Solr release. We should 
 remove that in 8.0
 It stays empty unless you explicitly ask to create the collection with the 
 old "stateFormat" and there is no reason for one to create a collection 
 with the old stateFormat.
 We should also remove the "stateFormat" argument in create collection
 We should also remove MIGRATESTATEVERSION as well
 
 
>>> 
>>> 
>>> 
>>> --
>>> This message was sent by Atlassian Jira
>>> (v8.3.4#803005)
>>> 
>>> -
>>> To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: issues-h...@lucene.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Ryan Ernst]

+1 (binding)

On Tue, May 12, 2020 at 12:37 AM Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Erik Hatcher]

+1

> On May 12, 2020, at 3:36 AM, Dawid Weiss  wrote:
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
> 
> Please indicate one of the following (see [1] for guidelines):
> 
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
> 
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
> 
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
> 
> Dawid
> 
> [1] https://www.apache.org/foundation/voting.html
> [2] 
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [jira] [Commented] (SOLR-12823) remove clusterstate.json in Lucene/Solr 8.0

[Ilan Ginzburg]

I could work on a PR to remove it in Solr 9, unless you think it's
super tricky work.

Ilan

On Tue, May 12, 2020 at 3:32 PM Erick Erickson  wrote:
>
> Definitely +1, but I won’t have the bandwidth to help.
>
> > On May 12, 2020, at 9:03 AM, Jan Høydahl (Jira)  wrote:
> >
> >
> >[ 
> > https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105402#comment-17105402
> >  ]
> >
> > Jan Høydahl commented on SOLR-12823:
> > 
> >
> > Any plan to remove clusterstate.json for Solr 9? And perhaps let Overseer 
> > fail if it is non-empty, i.e. if not all collections are migrated to format 
> > 2?
> >
> >> remove clusterstate.json in Lucene/Solr 8.0
> >> ---
> >>
> >>Key: SOLR-12823
> >>URL: https://issues.apache.org/jira/browse/SOLR-12823
> >>Project: Solr
> >> Issue Type: Task
> >>   Reporter: Varun Thacker
> >>   Priority: Major
> >>
> >> clusterstate.json is an artifact of a pre 5.0 Solr release. We should 
> >> remove that in 8.0
> >> It stays empty unless you explicitly ask to create the collection with the 
> >> old "stateFormat" and there is no reason for one to create a collection 
> >> with the old stateFormat.
> >> We should also remove the "stateFormat" argument in create collection
> >> We should also remove MIGRATESTATEVERSION as well
> >>
> >>
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
> >
> > -
> > To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: issues-h...@lucene.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Andi Vajda]

+1 (binding)

Andi..

> On May 12, 2020, at 00:37, Dawid Weiss  wrote:
> 
> Dear Lucene and Solr developers!
> 
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
> 
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
> 
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
> 
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
> 
> Please indicate one of the following (see [1] for guidelines):
> 
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
> 
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
> 
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
> 
> Dawid
> 
> [1] https://www.apache.org/foundation/voting.html
> [2] 
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Ishan Chattopadhyaya]

+1 (binding)

On Tue, May 12, 2020 at 7:21 PM Ignacio Vera  wrote:

> +1 (binding)
>
> On Tue, May 12, 2020 at 3:38 PM Tomás Fernández Löbbe <
> tomasflo...@gmail.com> wrote:
>
>> -1 (binding)
>>
>>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Ignacio Vera]

+1 (binding)

On Tue, May 12, 2020 at 3:38 PM Tomás Fernández Löbbe 
wrote:

> -1 (binding)
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Tomás Fernández Löbbe]

-1 (binding)

Re: [jira] [Commented] (SOLR-12823) remove clusterstate.json in Lucene/Solr 8.0

[Erick Erickson]

Definitely +1, but I won’t have the bandwidth to help.

> On May 12, 2020, at 9:03 AM, Jan Høydahl (Jira)  wrote:
> 
> 
>[ 
> https://issues.apache.org/jira/browse/SOLR-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105402#comment-17105402
>  ] 
> 
> Jan Høydahl commented on SOLR-12823:
> 
> 
> Any plan to remove clusterstate.json for Solr 9? And perhaps let Overseer 
> fail if it is non-empty, i.e. if not all collections are migrated to format 2?
> 
>> remove clusterstate.json in Lucene/Solr 8.0
>> ---
>> 
>>Key: SOLR-12823
>>URL: https://issues.apache.org/jira/browse/SOLR-12823
>>Project: Solr
>> Issue Type: Task
>>   Reporter: Varun Thacker
>>   Priority: Major
>> 
>> clusterstate.json is an artifact of a pre 5.0 Solr release. We should remove 
>> that in 8.0
>> It stays empty unless you explicitly ask to create the collection with the 
>> old "stateFormat" and there is no reason for one to create a collection with 
>> the old stateFormat.
>> We should also remove the "stateFormat" argument in create collection
>> We should also remove MIGRATESTATEVERSION as well
>>  
>>  
> 
> 
> 
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
> 
> -
> To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
> For additional commands, e-mail: issues-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

[Doug Turnbull]

I'll give a perspective that comes more from the user's / "market" point
of view as at OSC we onboard lots of new organizations into Solr.

- Most new users incorrectly think of Solr as an independent Apache
project, and many will have little knowledge or awareness of Lucene itself
until given the full history of Lucene, Solr, Elasticsearch... or they have
to dive into the code/write a plugin

- Most orgs / managers think in terms of "Solr" (as in "Solr" vs
"Elasticsearch" vs "Vespa, etc). So the starting point for new devs / folks
is from the Solr angle

- Lucene, when discussed, is understood more colloquially as a Solr
dependency

- If someone brings down the code to do some kind of work or investigation,
there's typically surprise that Lucene and Solr are bundled together.

- There's further surprise as the projects are indeed so different: Lucene
and Solr tests, for example look little alike. They seem to have different
coding syles / practices. One has more server-like and distributed system
concerns; the other is clearly a low-level library for doing search work...

I personally have a hard time explaining to new users the rationale for
keeping these together, and it only increases the barrier to entry (to both
projects) to have this added complexity of two very different code bases
munged together.

Just my 2 cents...
-Doug

On Tue, May 12, 2020 at 7:30 AM Alan Woodward  wrote:

> One advantage I find with the way Elasticsearch and Lucene interact is
> that ES doesn’t depend on the master branch.  We upgrade our master branch
> frequently to keep up to date with the latest release branch, and that lets
> us find regressions or API problems pretty quickly, but it also insulates
> us from having to make big changes immediately.  I find this really useful
> for things like deprecations.  Let’s say we deprecate a particular API in
> the release branch, and remove it entirely in master.  Currently, that
> means Solr needs to immediately switch over to the new API in its master
> branch.  But the whole point of doing deprecations first is that it gives
> users time to find issues with the replacements - if we find that the
> replacement API doesn’t quite fit in ES, we have time to work out either
> how to change our code, or to improve the new API, but because the
> deprecated version is still there we’re not blocked from upgrading and
> getting other improvements.  Solr, meanwhile, may end up with a hacky
> workaround because that’s what got tests passing for the Lucene developer;
> or worse, we end up just copying the deprecated API wholesale into Solr and
> abandoning it there - witness TrieField or UninvertingReader.
>
> > On 11 May 2020, at 19:05, Atri Sharma  wrote:
> >
> > My two cents:
> >
> > As a Lucene heavy developer, I have several found maintaining Solr
> > dependencies while making large changes a bit cumbersome. I believe
> > Lucene and Solr should exist in a symbiotic relationship but not
> > tightly coupled with each other.
> >
> >
> > On Mon, May 11, 2020 at 7:22 PM Erik Hatcher 
> wrote:
> >>
> >> Without reading much or replying to any specific points made on this
> thread, here's my raw thoughts on this age-old topic (finally  coming
> out of my cocoon after taking things in for a bit)
> >>
> >> Solr is a search -server- with distributed capabilities, that leverages
> the magic of Lucene underneath.  Solr depends on Lucene, is a consumer of
> it.  Lucene is a tight search -library- with little to no external
> dependencies.  Their purposes and end-users are different.
> >>
> >> I was never really for the grand unification of Lucene and Solr back in
> the day because:
> >>
> >> - Solr's developer experience would be greatly streamlined, faster,
> cleaner, leaner, and focused
> >> - Having Lucene change when Solr doesni't (yet) adapt to those changes
> leads to confusion and inconsistency, loose wires hanging out of the wall
> unconnected or duct taped together
> >> - It simply makes sense to keep Lucene versioned and tightly controlled
> for upgrades, various testing configurations varying Lucene versions,
> within Solr
> >> - Solr could have a very concerted upgrade effort for Lucene capability
> jumps, with a focused upgrade effort at the changed/improved/added touch
> points just like other dependencies within Solr (like Tika and Jetty)
> >>
> >> Those points all kinda say the same thing Solr depends on
> "lucene.jar" and I'm in the camp that thinks Solr and Lucene development,
> communities, and end-users/consumers would all greatly benefit from a fancy
> new TLP and focused community for solr.apache.org and a tight(er)
> relationship with the Lucene community as an involved and vested consumer.
> >>
> >> Erik
> >>
> >
> >
> > --
> > Regards,
> >
> > Atri
> > Apache Concerted
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: 

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[David Smiley]

+1 (binding)
~ David

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Nhat Nguyen]

+1 (binding)

On Tue, May 12, 2020 at 8:41 AM Steve Rowe  wrote:

> +1
>
> --
> Steve
>
> > On May 12, 2020, at 3:36 AM, Dawid Weiss  wrote:
> >
> > Dear Lucene and Solr developers!
> >
> > According to an earlier [DISCUSS] thread on the dev list [2], I am
> > calling for a vote on the proposal to make Solr a top-level Apache
> > project (TLP) and separate Lucene and Solr development into two
> > independent entities.
> >
> > To quickly recap the reasons and consequences of such a move: it seems
> > like the reasons for the initial merge of Lucene and Solr, around 10
> > years ago, have been achieved. Both projects are in good shape and
> > exhibit signs of independence already (mailing lists, committers,
> > patch flow). There are many technical considerations that would make
> > development much easier if we move Solr out into its own TLP.
> >
> > We discussed this issue [2] and both PMC members and committers had a
> > chance to review all the pros and cons and express their views. The
> > discussion showed that there are clearly different opinions on the
> > matter - some people are in favor, some are neutral, others are
> > against or not seeing the point of additional labor. Realistically, I
> > don't think reaching 100% level consensus is going to be possible --
> > we are a diverse bunch with different opinions and personalities. I
> > firmly believe this is the right direction hence the decision to put
> > it under the voting process. Should something take a wrong turn in the
> > future (as some folks worry it may), all blame is on me.
> >
> > Therefore, the proposal is to separate Solr from under Lucene TLP, and
> > make it a TLP on its own. The initial structure of the new PMC,
> > committer base, git repositories and other managerial aspects can be
> > worked out during the process if the decision passes.
> >
> > Please indicate one of the following (see [1] for guidelines):
> >
> > [ ] +1 - yes, I vote for the proposal
> > [ ] -1 - no, I vote against the proposal
> >
> > Please note that anyone in the Lucene+Solr community is invited to
> > express their opinion, though only Lucene+Solr committers cast binding
> > votes (indicate non-binding votes in your reply, please).
> >
> > The vote will be active for a week to give everyone a chance to read
> > and cast a vote.
> >
> > Dawid
> >
> > [1] https://www.apache.org/foundation/voting.html
> > [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Steve Rowe]

+1

--
Steve

> On May 12, 2020, at 3:36 AM, Dawid Weiss  wrote:
> 
> Dear Lucene and Solr developers!
> 
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
> 
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
> 
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
> 
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
> 
> Please indicate one of the following (see [1] for guidelines):
> 
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
> 
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
> 
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
> 
> Dawid
> 
> [1] https://www.apache.org/foundation/voting.html
> [2] 
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Michael McCandless]

+1, this is long overdue.

It will indeed be quite a bit of work to separate everything, but I think
the long term benefits to both projects will be massive, making that
one-time cost very much worth it.

Thanks for raising this Dawid!

Mike McCandless

http://blog.mikemccandless.com


On Tue, May 12, 2020 at 3:37 AM Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Robert Muir]

+1

On Tue, May 12, 2020 at 3:37 AM Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[jim ferenczi]

+1 (binding)

Le mar. 12 mai 2020 à 14:00, Simon Willnauer  a
écrit :

> +1 binding
>
> Sent from a mobile device
>
> > On 12. May 2020, at 13:33, Jason Gerlowski 
> wrote:
> >
> > -1 (binding)
> >
> >> On Tue, May 12, 2020 at 7:31 AM Alan Woodward 
> wrote:
> >>
> >> +1 (binding)
> >>
> >> Alan Woodward
> >>
>  On 12 May 2020, at 12:06, Jan Høydahl  wrote:
> >>>
> >>> +1 (binding)
> >>>
> >>> Jan Høydahl
> >>>
>  12. mai 2020 kl. 09:36 skrev Dawid Weiss :
> 
>  Dear Lucene and Solr developers!
> 
>  According to an earlier [DISCUSS] thread on the dev list [2], I am
>  calling for a vote on the proposal to make Solr a top-level Apache
>  project (TLP) and separate Lucene and Solr development into two
>  independent entities.
> 
>  To quickly recap the reasons and consequences of such a move: it seems
>  like the reasons for the initial merge of Lucene and Solr, around 10
>  years ago, have been achieved. Both projects are in good shape and
>  exhibit signs of independence already (mailing lists, committers,
>  patch flow). There are many technical considerations that would make
>  development much easier if we move Solr out into its own TLP.
> 
>  We discussed this issue [2] and both PMC members and committers had a
>  chance to review all the pros and cons and express their views. The
>  discussion showed that there are clearly different opinions on the
>  matter - some people are in favor, some are neutral, others are
>  against or not seeing the point of additional labor. Realistically, I
>  don't think reaching 100% level consensus is going to be possible --
>  we are a diverse bunch with different opinions and personalities. I
>  firmly believe this is the right direction hence the decision to put
>  it under the voting process. Should something take a wrong turn in the
>  future (as some folks worry it may), all blame is on me.
> 
>  Therefore, the proposal is to separate Solr from under Lucene TLP, and
>  make it a TLP on its own. The initial structure of the new PMC,
>  committer base, git repositories and other managerial aspects can be
>  worked out during the process if the decision passes.
> 
>  Please indicate one of the following (see [1] for guidelines):
> 
>  [ ] +1 - yes, I vote for the proposal
>  [ ] -1 - no, I vote against the proposal
> 
>  Please note that anyone in the Lucene+Solr community is invited to
>  express their opinion, though only Lucene+Solr committers cast binding
>  votes (indicate non-binding votes in your reply, please).
> 
>  The vote will be active for a week to give everyone a chance to read
>  and cast a vote.
> 
>  Dawid
> 
>  [1] https://www.apache.org/foundation/voting.html
>  [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>  For additional commands, e-mail: dev-h...@lucene.apache.org
> 
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >>> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Simon Willnauer]

+1 binding 

Sent from a mobile device

> On 12. May 2020, at 13:33, Jason Gerlowski  wrote:
> 
> -1 (binding)
> 
>> On Tue, May 12, 2020 at 7:31 AM Alan Woodward  wrote:
>> 
>> +1 (binding)
>> 
>> Alan Woodward
>> 
 On 12 May 2020, at 12:06, Jan Høydahl  wrote:
>>> 
>>> +1 (binding)
>>> 
>>> Jan Høydahl
>>> 
 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
 
 Dear Lucene and Solr developers!
 
 According to an earlier [DISCUSS] thread on the dev list [2], I am
 calling for a vote on the proposal to make Solr a top-level Apache
 project (TLP) and separate Lucene and Solr development into two
 independent entities.
 
 To quickly recap the reasons and consequences of such a move: it seems
 like the reasons for the initial merge of Lucene and Solr, around 10
 years ago, have been achieved. Both projects are in good shape and
 exhibit signs of independence already (mailing lists, committers,
 patch flow). There are many technical considerations that would make
 development much easier if we move Solr out into its own TLP.
 
 We discussed this issue [2] and both PMC members and committers had a
 chance to review all the pros and cons and express their views. The
 discussion showed that there are clearly different opinions on the
 matter - some people are in favor, some are neutral, others are
 against or not seeing the point of additional labor. Realistically, I
 don't think reaching 100% level consensus is going to be possible --
 we are a diverse bunch with different opinions and personalities. I
 firmly believe this is the right direction hence the decision to put
 it under the voting process. Should something take a wrong turn in the
 future (as some folks worry it may), all blame is on me.
 
 Therefore, the proposal is to separate Solr from under Lucene TLP, and
 make it a TLP on its own. The initial structure of the new PMC,
 committer base, git repositories and other managerial aspects can be
 worked out during the process if the decision passes.
 
 Please indicate one of the following (see [1] for guidelines):
 
 [ ] +1 - yes, I vote for the proposal
 [ ] -1 - no, I vote against the proposal
 
 Please note that anyone in the Lucene+Solr community is invited to
 express their opinion, though only Lucene+Solr committers cast binding
 votes (indicate non-binding votes in your reply, please).
 
 The vote will be active for a week to give everyone a chance to read
 and cast a vote.
 
 Dawid
 
 [1] https://www.apache.org/foundation/voting.html
 [2] 
 https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
 For additional commands, e-mail: dev-h...@lucene.apache.org
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Jason Gerlowski]

-1 (binding)

On Tue, May 12, 2020 at 7:31 AM Alan Woodward  wrote:
>
> +1 (binding)
>
> Alan Woodward
>
> > On 12 May 2020, at 12:06, Jan Høydahl  wrote:
> >
> > +1 (binding)
> >
> > Jan Høydahl
> >
> >> 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
> >>
> >> Dear Lucene and Solr developers!
> >>
> >> According to an earlier [DISCUSS] thread on the dev list [2], I am
> >> calling for a vote on the proposal to make Solr a top-level Apache
> >> project (TLP) and separate Lucene and Solr development into two
> >> independent entities.
> >>
> >> To quickly recap the reasons and consequences of such a move: it seems
> >> like the reasons for the initial merge of Lucene and Solr, around 10
> >> years ago, have been achieved. Both projects are in good shape and
> >> exhibit signs of independence already (mailing lists, committers,
> >> patch flow). There are many technical considerations that would make
> >> development much easier if we move Solr out into its own TLP.
> >>
> >> We discussed this issue [2] and both PMC members and committers had a
> >> chance to review all the pros and cons and express their views. The
> >> discussion showed that there are clearly different opinions on the
> >> matter - some people are in favor, some are neutral, others are
> >> against or not seeing the point of additional labor. Realistically, I
> >> don't think reaching 100% level consensus is going to be possible --
> >> we are a diverse bunch with different opinions and personalities. I
> >> firmly believe this is the right direction hence the decision to put
> >> it under the voting process. Should something take a wrong turn in the
> >> future (as some folks worry it may), all blame is on me.
> >>
> >> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> >> make it a TLP on its own. The initial structure of the new PMC,
> >> committer base, git repositories and other managerial aspects can be
> >> worked out during the process if the decision passes.
> >>
> >> Please indicate one of the following (see [1] for guidelines):
> >>
> >> [ ] +1 - yes, I vote for the proposal
> >> [ ] -1 - no, I vote against the proposal
> >>
> >> Please note that anyone in the Lucene+Solr community is invited to
> >> express their opinion, though only Lucene+Solr committers cast binding
> >> votes (indicate non-binding votes in your reply, please).
> >>
> >> The vote will be active for a week to give everyone a chance to read
> >> and cast a vote.
> >>
> >> Dawid
> >>
> >> [1] https://www.apache.org/foundation/voting.html
> >> [2] 
> >> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Alan Woodward]

+1 (binding)

Alan Woodward

> On 12 May 2020, at 12:06, Jan Høydahl  wrote:
> 
> +1 (binding)
> 
> Jan Høydahl
> 
>> 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
>> 
>> Dear Lucene and Solr developers!
>> 
>> According to an earlier [DISCUSS] thread on the dev list [2], I am
>> calling for a vote on the proposal to make Solr a top-level Apache
>> project (TLP) and separate Lucene and Solr development into two
>> independent entities.
>> 
>> To quickly recap the reasons and consequences of such a move: it seems
>> like the reasons for the initial merge of Lucene and Solr, around 10
>> years ago, have been achieved. Both projects are in good shape and
>> exhibit signs of independence already (mailing lists, committers,
>> patch flow). There are many technical considerations that would make
>> development much easier if we move Solr out into its own TLP.
>> 
>> We discussed this issue [2] and both PMC members and committers had a
>> chance to review all the pros and cons and express their views. The
>> discussion showed that there are clearly different opinions on the
>> matter - some people are in favor, some are neutral, others are
>> against or not seeing the point of additional labor. Realistically, I
>> don't think reaching 100% level consensus is going to be possible --
>> we are a diverse bunch with different opinions and personalities. I
>> firmly believe this is the right direction hence the decision to put
>> it under the voting process. Should something take a wrong turn in the
>> future (as some folks worry it may), all blame is on me.
>> 
>> Therefore, the proposal is to separate Solr from under Lucene TLP, and
>> make it a TLP on its own. The initial structure of the new PMC,
>> committer base, git repositories and other managerial aspects can be
>> worked out during the process if the decision passes.
>> 
>> Please indicate one of the following (see [1] for guidelines):
>> 
>> [ ] +1 - yes, I vote for the proposal
>> [ ] -1 - no, I vote against the proposal
>> 
>> Please note that anyone in the Lucene+Solr community is invited to
>> express their opinion, though only Lucene+Solr committers cast binding
>> votes (indicate non-binding votes in your reply, please).
>> 
>> The vote will be active for a week to give everyone a chance to read
>> and cast a vote.
>> 
>> Dawid
>> 
>> [1] https://www.apache.org/foundation/voting.html
>> [2] 
>> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

[Alan Woodward]

One advantage I find with the way Elasticsearch and Lucene interact is that ES 
doesn’t depend on the master branch.  We upgrade our master branch frequently 
to keep up to date with the latest release branch, and that lets us find 
regressions or API problems pretty quickly, but it also insulates us from 
having to make big changes immediately.  I find this really useful for things 
like deprecations.  Let’s say we deprecate a particular API in the release 
branch, and remove it entirely in master.  Currently, that means Solr needs to 
immediately switch over to the new API in its master branch.  But the whole 
point of doing deprecations first is that it gives users time to find issues 
with the replacements - if we find that the replacement API doesn’t quite fit 
in ES, we have time to work out either how to change our code, or to improve 
the new API, but because the deprecated version is still there we’re not 
blocked from upgrading and getting other improvements.  Solr, meanwhile, may 
end up with a hacky workaround because that’s what got tests passing for the 
Lucene developer; or worse, we end up just copying the deprecated API wholesale 
into Solr and abandoning it there - witness TrieField or UninvertingReader.

> On 11 May 2020, at 19:05, Atri Sharma  wrote:
> 
> My two cents:
> 
> As a Lucene heavy developer, I have several found maintaining Solr
> dependencies while making large changes a bit cumbersome. I believe
> Lucene and Solr should exist in a symbiotic relationship but not
> tightly coupled with each other.
> 
> 
> On Mon, May 11, 2020 at 7:22 PM Erik Hatcher  wrote:
>> 
>> Without reading much or replying to any specific points made on this thread, 
>> here's my raw thoughts on this age-old topic (finally  coming out of my 
>> cocoon after taking things in for a bit)
>> 
>> Solr is a search -server- with distributed capabilities, that leverages the 
>> magic of Lucene underneath.  Solr depends on Lucene, is a consumer of it.  
>> Lucene is a tight search -library- with little to no external dependencies.  
>> Their purposes and end-users are different.
>> 
>> I was never really for the grand unification of Lucene and Solr back in the 
>> day because:
>> 
>> - Solr's developer experience would be greatly streamlined, faster, cleaner, 
>> leaner, and focused
>> - Having Lucene change when Solr doesni't (yet) adapt to those changes leads 
>> to confusion and inconsistency, loose wires hanging out of the wall 
>> unconnected or duct taped together
>> - It simply makes sense to keep Lucene versioned and tightly controlled for 
>> upgrades, various testing configurations varying Lucene versions, within Solr
>> - Solr could have a very concerted upgrade effort for Lucene capability 
>> jumps, with a focused upgrade effort at the changed/improved/added touch 
>> points just like other dependencies within Solr (like Tika and Jetty)
>> 
>> Those points all kinda say the same thing Solr depends on "lucene.jar" 
>> and I'm in the camp that thinks Solr and Lucene development, communities, 
>> and end-users/consumers would all greatly benefit from a fancy new TLP and 
>> focused community for solr.apache.org and a tight(er) relationship with the 
>> Lucene community as an involved and vested consumer.
>> 
>> Erik
>> 
> 
> 
> -- 
> Regards,
> 
> Atri
> Apache Concerted
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Jan Høydahl]

+1 (binding)

Jan Høydahl

> 12. mai 2020 kl. 09:36 skrev Dawid Weiss :
> 
> Dear Lucene and Solr developers!
> 
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
> 
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
> 
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
> 
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
> 
> Please indicate one of the following (see [1] for guidelines):
> 
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
> 
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
> 
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
> 
> Dawid
> 
> [1] https://www.apache.org/foundation/voting.html
> [2] 
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: [VOTE] Solr to become a top-level Apache project (TLP)

[Uwe Schindler]

Hi,

here is also my +1
I have a few objections about the process, but in general it's a good idea.

Uwe

-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: Dawid Weiss 
> Sent: Tuesday, May 12, 2020 9:37 AM
> To: Lucene Dev 
> Subject: [VOTE] Solr to become a top-level Apache project (TLP)
> 
> Dear Lucene and Solr developers!
> 
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
> 
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
> 
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
> 
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
> 
> Please indicate one of the following (see [1] for guidelines):
> 
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
> 
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
> 
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
> 
> Dawid
> 
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7
> e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Dawid Weiss]

Oh, here is my +1 (binding).

Dawid

On Tue, May 12, 2020 at 9:36 AM Dawid Weiss  wrote:
>
> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2] 
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Christian Moen]

Thanks for suggesting this and bringing this forward to a vote, Dawid.

I'm in favor of the proposal; +1 (binding)

Best,
Christian


On Tue, May 12, 2020 at 4:37 PM Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Karl Wright]

+1 from me (binding)
Karl

On Tue, May 12, 2020 at 3:54 AM Atri Sharma  wrote:

> +1 (binding).
>
> Regards,
>
> Atri
>
> On Tue, 12 May 2020 at 13:07, Dawid Weiss  wrote:
>
>> Dear Lucene and Solr developers!
>>
>> According to an earlier [DISCUSS] thread on the dev list [2], I am
>> calling for a vote on the proposal to make Solr a top-level Apache
>> project (TLP) and separate Lucene and Solr development into two
>> independent entities.
>>
>> To quickly recap the reasons and consequences of such a move: it seems
>> like the reasons for the initial merge of Lucene and Solr, around 10
>> years ago, have been achieved. Both projects are in good shape and
>> exhibit signs of independence already (mailing lists, committers,
>> patch flow). There are many technical considerations that would make
>> development much easier if we move Solr out into its own TLP.
>>
>> We discussed this issue [2] and both PMC members and committers had a
>> chance to review all the pros and cons and express their views. The
>> discussion showed that there are clearly different opinions on the
>> matter - some people are in favor, some are neutral, others are
>> against or not seeing the point of additional labor. Realistically, I
>> don't think reaching 100% level consensus is going to be possible --
>> we are a diverse bunch with different opinions and personalities. I
>> firmly believe this is the right direction hence the decision to put
>> it under the voting process. Should something take a wrong turn in the
>> future (as some folks worry it may), all blame is on me.
>>
>> Therefore, the proposal is to separate Solr from under Lucene TLP, and
>> make it a TLP on its own. The initial structure of the new PMC,
>> committer base, git repositories and other managerial aspects can be
>> worked out during the process if the decision passes.
>>
>> Please indicate one of the following (see [1] for guidelines):
>>
>> [ ] +1 - yes, I vote for the proposal
>> [ ] -1 - no, I vote against the proposal
>>
>> Please note that anyone in the Lucene+Solr community is invited to
>> express their opinion, though only Lucene+Solr committers cast binding
>> votes (indicate non-binding votes in your reply, please).
>>
>> The vote will be active for a week to give everyone a chance to read
>> and cast a vote.
>>
>> Dawid
>>
>> [1] https://www.apache.org/foundation/voting.html
>> [2]
>> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>> --
> Regards,
>
> Atri
> Apache Concerted
>

Re: [VOTE] Solr to become a top-level Apache project (TLP)

[Atri Sharma]

+1 (binding).

Regards,

Atri

On Tue, 12 May 2020 at 13:07, Dawid Weiss  wrote:

> Dear Lucene and Solr developers!
>
> According to an earlier [DISCUSS] thread on the dev list [2], I am
> calling for a vote on the proposal to make Solr a top-level Apache
> project (TLP) and separate Lucene and Solr development into two
> independent entities.
>
> To quickly recap the reasons and consequences of such a move: it seems
> like the reasons for the initial merge of Lucene and Solr, around 10
> years ago, have been achieved. Both projects are in good shape and
> exhibit signs of independence already (mailing lists, committers,
> patch flow). There are many technical considerations that would make
> development much easier if we move Solr out into its own TLP.
>
> We discussed this issue [2] and both PMC members and committers had a
> chance to review all the pros and cons and express their views. The
> discussion showed that there are clearly different opinions on the
> matter - some people are in favor, some are neutral, others are
> against or not seeing the point of additional labor. Realistically, I
> don't think reaching 100% level consensus is going to be possible --
> we are a diverse bunch with different opinions and personalities. I
> firmly believe this is the right direction hence the decision to put
> it under the voting process. Should something take a wrong turn in the
> future (as some folks worry it may), all blame is on me.
>
> Therefore, the proposal is to separate Solr from under Lucene TLP, and
> make it a TLP on its own. The initial structure of the new PMC,
> committer base, git repositories and other managerial aspects can be
> worked out during the process if the decision passes.
>
> Please indicate one of the following (see [1] for guidelines):
>
> [ ] +1 - yes, I vote for the proposal
> [ ] -1 - no, I vote against the proposal
>
> Please note that anyone in the Lucene+Solr community is invited to
> express their opinion, though only Lucene+Solr committers cast binding
> votes (indicate non-binding votes in your reply, please).
>
> The vote will be active for a week to give everyone a chance to read
> and cast a vote.
>
> Dawid
>
> [1] https://www.apache.org/foundation/voting.html
> [2]
> https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
> --
Regards,

Atri
Apache Concerted

[VOTE] Solr to become a top-level Apache project (TLP)

[Dawid Weiss]

Dear Lucene and Solr developers!

According to an earlier [DISCUSS] thread on the dev list [2], I am
calling for a vote on the proposal to make Solr a top-level Apache
project (TLP) and separate Lucene and Solr development into two
independent entities.

To quickly recap the reasons and consequences of such a move: it seems
like the reasons for the initial merge of Lucene and Solr, around 10
years ago, have been achieved. Both projects are in good shape and
exhibit signs of independence already (mailing lists, committers,
patch flow). There are many technical considerations that would make
development much easier if we move Solr out into its own TLP.

We discussed this issue [2] and both PMC members and committers had a
chance to review all the pros and cons and express their views. The
discussion showed that there are clearly different opinions on the
matter - some people are in favor, some are neutral, others are
against or not seeing the point of additional labor. Realistically, I
don't think reaching 100% level consensus is going to be possible --
we are a diverse bunch with different opinions and personalities. I
firmly believe this is the right direction hence the decision to put
it under the voting process. Should something take a wrong turn in the
future (as some folks worry it may), all blame is on me.

Therefore, the proposal is to separate Solr from under Lucene TLP, and
make it a TLP on its own. The initial structure of the new PMC,
committer base, git repositories and other managerial aspects can be
worked out during the process if the decision passes.

Please indicate one of the following (see [1] for guidelines):

[ ] +1 - yes, I vote for the proposal
[ ] -1 - no, I vote against the proposal

Please note that anyone in the Lucene+Solr community is invited to
express their opinion, though only Lucene+Solr committers cast binding
votes (indicate non-binding votes in your reply, please).

The vote will be active for a week to give everyone a chance to read
and cast a vote.

Dawid

[1] https://www.apache.org/foundation/voting.html
[2] 
https://lists.apache.org/thread.html/rfae2440264f6f874e91545b2030c98e7b7e3854ddf090f7747d338df%40%3Cdev.lucene.apache.org%3E

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org