Re: Branding Solr+Lucene

2010-03-22 Thread Mattmann, Chris A (388J)
What are the implications of this this new branding effort with the brands
for the existing Lucene and Solr? Will the names Lucene and Solr cease
in the mainstream in favor of a merged name?

Cheers,
Chris


On 3/22/10 11:02 AM, Steven A Rowe sar...@syr.edu wrote:

 Now that Solr and Lucene live in the same space, there has been an on-going
 debate about what to call the merged entity.
 
 The names being mulled at this point include (variously sized) snippets of
 both Lucene's and Solr's names, and include LuSolr, Solcene, etc. (my current
 personal favorites along these lines: Sorlusr :) ).
 
 My guess is that Lucene partisans would like to see Solr just become a product
 (along with the Lucene java library) of the Lucene project.  Judging from
 suggestions coming from Solr partisans, though, I don't think this will fly.
 
 So I think an entirely new name is needed for the merged project.  Lucene and
 Solr would remain the product names of this newly named merged project.
 
 Along these lines, search.apache.org has been brought up a couple of times
 recently on the #lucene IRC channel.  However (with all due respect to
 what-happens-on-#lucene-stays-on-#lucene (TM) ), Grant wrote in response to
 one of these suggestions this morning:
 
prob. is Search is not a brand
ASF likes names
 
 So in the spirit of a real name (i.e., an abstract symbol), I propose Srrrch
 (riffing off of Riot Grrrls and Solr's penchant for vowel droppings)
 Okay, not really.
 
 I do have one idea, though: thinking about the icons for Lucene (looks to me
 like the font used on 50's automobile brand logos) and Solr (a sun): car+sun
 = convertible = Ragtop.  Fun, short, abstract, apolitical.  Solr's and
 Lucene's icons could be easily embedded in a Ragtop logo.
 
 Steve
 
 


++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++




Re: Branding Solr+Lucene

2010-03-22 Thread Ryan McKinley
I'm confused... what is the need for a new name?  The only place where
there is a conflict is in the top level svn tree...

What about something general like:
https://svn.apache.org/repos/asf/lucene/dev
or
https://svn.apache.org/repos/asf/lucene/project

ryan


On Mon, Mar 22, 2010 at 2:02 PM, Steven A Rowe sar...@syr.edu wrote:
 Now that Solr and Lucene live in the same space, there has been an on-going 
 debate about what to call the merged entity.

 The names being mulled at this point include (variously sized) snippets of 
 both Lucene's and Solr's names, and include LuSolr, Solcene, etc. (my current 
 personal favorites along these lines: Sorlusr :) ).

 My guess is that Lucene partisans would like to see Solr just become a 
 product (along with the Lucene java library) of the Lucene project.  Judging 
 from suggestions coming from Solr partisans, though, I don't think this will 
 fly.

 So I think an entirely new name is needed for the merged project.  Lucene and 
 Solr would remain the product names of this newly named merged project.

 Along these lines, search.apache.org has been brought up a couple of times 
 recently on the #lucene IRC channel.  However (with all due respect to 
 what-happens-on-#lucene-stays-on-#lucene (TM) ), Grant wrote in response to 
 one of these suggestions this morning:

   prob. is Search is not a brand
   ASF likes names

 So in the spirit of a real name (i.e., an abstract symbol), I propose 
 Srrrch (riffing off of Riot Grrrls and Solr's penchant for vowel 
 droppings)  Okay, not really.

 I do have one idea, though: thinking about the icons for Lucene (looks to me 
 like the font used on 50's automobile brand logos) and Solr (a sun): car+sun 
 = convertible = Ragtop.  Fun, short, abstract, apolitical.  Solr's and 
 Lucene's icons could be easily embedded in a Ragtop logo.

 Steve


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




Re: Branding Solr+Lucene

2010-03-22 Thread Yonik Seeley
On Mon, Mar 22, 2010 at 2:20 PM, Ryan McKinley ryan...@gmail.com wrote:
 I'm confused... what is the need for a new name?  The only place where
 there is a conflict is in the top level svn tree...

Agree, no need to re-brand.

 What about something general like:
 https://svn.apache.org/repos/asf/lucene/dev
 or
 https://svn.apache.org/repos/asf/lucene/project

Hmmm, that one isn't bad.

-Yonik


Re: Branding Solr+Lucene

2010-03-22 Thread Ted Dunning
On Mon, Mar 22, 2010 at 11:30 AM, Yonik Seeley ysee...@gmail.com wrote:

 On Mon, Mar 22, 2010 at 2:20 PM, Ryan McKinley ryan...@gmail.com wrote:
  I'm confused... what is the need for a new name?  The only place where
  there is a conflict is in the top level svn tree...

 Agree, no need to re-brand.


I don't see any need to rebrand.  The artifacts will still be called Lucene
and Solr, regardless.  In SVN, the natural thing to do is go with the
momentum that puts solr under lucene.  Insofar as the TLP, I would think
that it would still be Lucene with two delivered artifacts.


RE: Branding Solr+Lucene

2010-03-22 Thread Steven A Rowe
On 03/22/2010 at 2:30 PM, Yonik Seeley wrote:
 On Mon, Mar 22, 2010 at 2:20 PM, Ryan McKinley ryan...@gmail.com
 wrote:
  I'm confused... what is the need for a new name?  The only place where
  there is a conflict is in the top level svn tree...
 
 Agree, no need to re-brand.

Hmm, I've apparently misunderestimated the name-mooting that's been echoing 
around lately.

Since name can refer to a bunch of partially overlapping things (Apache TLP 
name; svn directory name; development project name; product name; etc.):

- Lucene will remain the name of the Apache TLP hosting both the Lucene-Java 
product and the Solr product.

- Solr, while ceasing to refer to a stand-alone development sub-project, will 
continue to be a product, with no change in its user-facing *product* 
communications; Solr's downloadable artifacts, the wiki, the website, and the 
solr-user mailing list will remain as-is.  (The website javadocs will need 
re-jiggering, though, I'd guess.)

Any disagreement?

Steve