I think Oliver wants something more concrete: jakarta-lucene-sandbox/projects/[project]/src/... jakarta-lucene-sandbox/projects/[project]/docs/... jakarta-lucene-sandbox/projects/[project]/xdocs/... jakarta-lucene-sandbox/projects/[project]/build.xml jakarta-lucene-sandbox/projects/[project]/README.txt jakarta-lucene-sandbox/projects/[project]/CHANGES.txt jakarta-lucene-sandbox/projects/[project]/LICENSE.txt
Replace '[package]' with 'crawler' or something appropriate. Otis --- Peter Carlson <[EMAIL PROTECTED]> wrote: > What is your example? > > If it is a Lucene application extension, then I would suggest the > contributions area if the source is available. For example, if there > was a > Russian Analyzer then I would suggest adding that to the > contributions area. > > If you are talking about a separate jar that is being used by the > contribution, AND it fell under the APL license (or a compatible > license to > distribute), then I could see the contribution having a lib > directory. > > I'm sure I'm missing something. > > --Peter > > > On 4/7/02 6:55 AM, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > > > Okay...so where do I put the app extensions? > > > > On Sat, 2002-04-06 at 22:38, Peter Carlson wrote: > >> > >> > >> I was thinking that the contributions in the sandbox area would be > source > >> contributions under the APL license. Other contributions that are > basically > >> references can still be added through the contributions page. > >> > >> I guess want I am not thinking the contributions area is just a > hodge podge > >> of unorganized stuff. It is structured repackaged > (org.apache.lucene) > >> contributions from contributors who are taking ownership. There > may be some > >> exceptions to the organization if the contributions are not > related to > >> lucene functionality directly (i.e. Erik Hatcher's indexing ant > task). Again > >> this does not stop us from adding other's contributions (binaries, > >> non-repackaged) to the contributions area. > >> > >> Thoughts? > >> > >> > >> I agree with your naming convention changes. > >> > >> Thanks > >> > >> --Peter > >> > >> > >> On 4/4/02 8:22 AM, "Otis Gospodnetic" <[EMAIL PROTECTED]> > wrote: > >> > >>> Peter, > >>> > >>>> Does everyone agree on that we should following this structure > and > >>>> naming convention? > >>>> > >>>> > >>>> jakarta-lucene-sandbox/README.txt > >>>> jakarta-lucene-sandbox/LICENSE.txt > >>>> jakarta-lucene-sandbox/index.html > >>>> jakarta-lucene-sandbox/CHANGES.txt > >>>> jakarta-lucene-sandbox/contributions/CHANGES.txt > >>>> jakarta-lucene-sandbox/contributions/build/build.xml > >>>> jakarta-lucene-sandbox/contributions/docs/... > >>>> jakarta-lucene-sandbox/contributions/[contribution]/src/... > >>> > >>> Not all contributions may include source. > >>> I imagine some contributions will come as an archive of .class > files, > >>> too. > >>> > >>> > jakarta-lucene-sandbox/contributions/[contribution]/xdocs/about[contribution > >>>> ].xml > >>> > >>> How about: about-[contribution].xml, it's a little easier to > read. > >>> > >>>> jakarta-lucene-sandbox/contributions/[contribution]/build.xml > >>> > >>> Not all contributions will have sources, so some may not need > this. > >>> > >>>> jakarta-lucene-sandbox/contributions/[contribution]/readme.txt > >>> > >>> How about README.txt, it's more common. > >>> > >>>> jakarta-lucene-sandbox/projects/[project]/src/... > >>>> jakarta-lucene-sandbox/projects/[project]/docs/... > >>>> jakarta-lucene-sandbox/projects/[project]/xdocs/... > >>>> jakarta-lucene-sandbox/projects/[project]/build.xml > >>>> jakarta-lucene-sandbox/projects/[project]/README.txt > >>>> jakarta-lucene-sandbox/projects/[project]/CHANGES.txt > >>>> jakarta-lucene-sandbox/projects/[project]/LICENSE.txt > >>>> > >>>> Where [contribution] is the name of the contribution > >>>> [project] is the name of the subproject in the sandbox area. > >>>> The contribution/build directory contains a build.xml which run > all > >>>> contributions build scripts. > >>>> jakarta-lucene-sandbox/contributions/docs/... Would contain all > >>>> created html > >>>> files from the each contributions xdocs/about[contribution].xml > >>>> > >>>> I'll create the base files when we get buy off. > >>>> > >>>> The distinction between a contribution and a project is a little > >>>> fuzzy, but > >>>> projects would be for functionality outside the scope of > Lucene's > >>>> current > >>>> API, where contributions would be able to be integrated into the > >>>> current API > >>>> (i.e. Analyzers, queryParsers, ...). > >>> > >>> I may be misunderstanding this. > >>> I'd imagine contributions to be code (source or binaries or...) > that > >>> various people provide, which we then either provide as is, or > use bits > >>> and pieces of to refactor in specific projects. > >>> These projects then eventually become a part of Lucene (not core, > but > >>> applications/extensions). > >>> The crawler+indexer may be one such project, and it may get its > pieces > >>> from various people's contributions. > >>> > >>>> Please provide feedback so we can finalize this. > >>>> > >>>> Thanks for everyone's input and patience. > >>>> > >>>> Thanks to Brian for recommending the new CVS. I think it will be > >>>> great to > >>>> get some more Lucene contributors more directly involved if they > are > >>>> willing. > >>>> > >>>> --Peter > >>> > >>> Otis > >>> > >>> > >>> __________________________________________________ > >>> Do You Yahoo!? > >>> Yahoo! Tax Center - online filing with TurboTax > >>> http://taxes.yahoo.com/ > >>> > >>> -- > >>> To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > >>> For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > >>> > >>> > >> > >> > >> -- > >> To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > >> For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > >> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
