I'd like access please to begin work on the application extensions. I am a Lucene committer.
Peter: As far as "contribution" versus "project" - thats some weird logic in distinguishing the two. Anyhow, a discussion on the semantics would be very boring for me. The application extensions are intended to be integrated back into the main lucene trunk once they are refactored/stable. Let me know what to qualify that as according to the seemingly decided upon semantics and where we should put this. Once the application extensions are complete as we previously discussed some months ago, we'll reintegrate them into the main CVS trunk. They'll be jar'd seperately from the core API so that those merely using the core API don't have to use the extensions. -Andy Erik Hatcher wrote: >How will committers to this new repository be selected? > >I would like to have commit access to contribute my Lucene indexing Ant task >as well as possibly a webapp that interfaces with an index. And I would, of >course, maintain as best I could. > > Erik > > >----- Original Message ----- >From: "Peter Carlson" <[EMAIL PROTECTED]> >To: "Lucene Developers List" <[EMAIL PROTECTED]> >Sent: Wednesday, April 03, 2002 6:07 PM >Subject: Lucene Sandbox now official > > >>Hi all, >> >>The jakarta-lucene-sandbox CVS repository is now official. >> >>Just so everyone is clear, this CVS is designed to hold contributions and >>sandbox projects. Both unsupported. >> >>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/... >> >jakarta-lucene-sandbox/contributions/[contribution]/xdocs/about[contribution > >>].xml >>jakarta-lucene-sandbox/contributions/[contribution]/build.xml >>jakarta-lucene-sandbox/contributions/[contribution]/readme.txt >>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, ...). >> >>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 >> >> >>-- >>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]>
