lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: Poll: solr-dev/java-dev overlap
Date Sun, 14 Mar 2010 19:44:34 GMT
Hi,

Hey Grant, I'm not picking on you, I swear!  :)

----- Original Message ----
> From: Grant Ingersoll <gsingers@apache.org>
> To: general@lucene.apache.org
> Sent: Wed, March 10, 2010 6:56:57 AM
> Subject: Re: Poll: solr-dev/java-dev overlap
> 
> 
On Mar 4, 2010, at 3:52 PM, Otis Gospodnetic wrote:

> Out of 
> curiosity.  Please reply ONLY if your are a Solr committer and the answer 
> to any of the questions is Yes.
> 
> 1) Are you on solr-dev, but NOT 
> on java-dev?
> 
> 2) Are you active on solr-dev, but do NOT 
> ACTIVELY FOLLOW java-dev?
> 

> I actively follow.  
> Lately, it seems java-dev requires following IRC too, but that is a separate 
> issue.  For the record, I follow that too.

> 
> 3) Are you 
> active on solr-dev, but do NOT ACTIVELY PARTICIPATE on java-dev?
> 

> I'm less active on java-dev than solr-dev, but I still do contribute, 
> just not at the level I used to and the primary reason is b/c of the disjunction 
> between the two.  My time is more effectively spent in Solr for the reasons 
> mentioned before.

And this is what confuses me.  How will merging -dev mailing lists help?  You are already
on both.  This is not meant as some kind of a provocative or rhetoric question.  I really
don't follow.


I do understand how for a Solr user/developer/contributor it makes sense (and is easier) to
just contribute X functionality to Solr and get it in the next Solr release vs. taking the
time to commit to Lucene core/module.  By committing directly to Solr one doesn't have to:
* learn Lucene internals/code
* be a member of Lucene dev community
* be on java-dev
* wait for the Lucene release and its inclusion in Solr

And indeed, I don't know how to prevent *contributors* from wanting to contribute patches
directly against Solr.
But I don't understand why Solr *committers* could not write/commit patches against Lucene
directly, not Solr, if we can get Solr to always have the fresh Lucene builds, so we can get
rid of the Lucene trunk jars->Solr  trunk delay.

Please help me and others understand.  Thanks,
Otis


Mime
View raw message