Let's create it as a top-level directory solely because it might give people a small head-start in SOLR evaluation and getting things off the ground (less navigation around the tree to get started). If there are any problems, we can always revert back to /contrib/clients.
B -----Original Message----- From: Mike Klaas [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 3:26 PM To: solr-user@lucene.apache.org Subject: Re: acts_as_solr On 8/29/06, Chris Hostetter <[EMAIL PROTECTED]> wrote: > Maybe ... "contrib" in the "Java Lucene" project sense however is all java > code, i would imagine that if someone wrote a perl utility to deal with > index files it would not make sense to but in the Lucene "contrib" > directory for that reason ... thre may be Java code submitted down the > road that we think is useful enough to make available in releases, but > niche enough that we on't want to put it in the main solr.war, which might > be more along the lines of the "contrib" notion -- hence my suggestion of > "clients" ... > > ...but i'm just thinking outloud at this point, i don't have a strong > opinion either way. Your point definately resonates. clients are also a rather important type of third-party contribution for a webapp thus a top-level directory makes sense. -Mike
