Both paths have an appeal -- do contribs stay or move? I recommend not moving existing contribs there until we explore how we can maintain compatibility with new Solr releases. (what Houston & Tomas point to below). For example, *perhaps* a "git sub-module" pointing to Solr might be a key mechanism? Could CI automatically keep it up to date? Someone needs to try before we really know.
~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Wed, Jan 13, 2021 at 10:30 AM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Hi Devs, > > As we discussed over the last few months, there seems a need to move > non-core pieces away from the Solr core module. The contribs are presently > a good place, but it makes sense to have a separate git repository hosting > such modules. Some candidates that come to mind are the present day contrib > modules, upcoming HDFS support module (separated away from solr-core), > other first party packages. Along with that, there is also a need for a > repository for hosting WIP modules/sub-projects. > > I propose that we apply for the creation of two new git repositories: > 1. solr-extras (or lucene-solr-extras) > 2. solr-sandbox (or lucene-solr-sandbox) > > Well tested, well supported modules/sub-projects can be released straight > away from *solr-extras*. The first party packages can be built from this > location and shipped with Solr (or be available for install using the > package manager CLI). > > New, unproved, beta, unstable modules can be hosted on *solr-sandbox* > (and graduate to solr-extras once stable). > > Please let me know if there are any questions/concerns with this approach. > > Thanks and regards, > Ishan >
