Hi Otis, The action item request is to create a scratchpad area in Lucene's CVS.
The scratchpad code would be part of the Lucene distribution nor part of the build process. I should have made that more clear in my proposal. If people are willing to create this an contribute there wares here, I think this is a much better idea than in the commons area. I think that all the Lucene related code should be part of the Lucene project. I don't even think that there would be a link to it from the Lucene web page. Which way are you going to vote? --Peter On 3/26/02 8:00 AM, "Otis Gospodnetic" <[EMAIL PROTECTED]> wrote: > Before we can really vote I think we need to have a common approach to > this. One idea proposed by Andrew was Jakarta Common 'luceneappext' > (long word, how about just LuceneApps?) subproject. This would mean > org.apache.commons.luceneappext. > On the other had Andrew said that he thinks of scratchpad as only > another build target, so that implies keeping this under Lucene's > Jakarta project. > What you are suggesting is keeping it all within Lucene repository, > etc. > So which one is it? :) > > I think it may be easier to go with Jakarta Commons Sandbox, but I > think the purpose of that Sandbox is that when code matures it migrates > to Commons proper, and not elsewhere (not to Lucene). I could be > wrong, maybe there are examples/subprojects that can easily show that > I'm wrong :). In that case I'd vote for Jakarta Commons Sandbox > approach, as I feel that it will be more clear that this is > experimental/work-in-progress code. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
