Plan of action

Focus

In order to achieve quick wins in terms of maintenance and performance, the first goal is to attack the solrconfig.xml file, which has a better chance of being standardized. I think we can start discussing schema.xml, however that is something I feel will be more difficult to achieve consensus on.

Project Structure

I propose creating a "conf" directory inside of the project's root directory with subdirectories for the major versions of Solr, for example "1.4.x", "3.x", "4.x", etc. In cases where we need version specific files, we can do something like 3.6, but we should avoid this at all costs. The trick here is that we will need to be more closely aligned with what versions of Solr are being supported by the various modules and when to adopt the standard configs.

Alignment With Solr Default Configs

The Apache Solr Search Integration and Search APi Solr's configuration files are derived from an older version of Solr, so the comments and structure are not closely aligned with the latest defaults. In order to simplify the config file upgrade process and see where we differ from the defaults, I propose that we start with the standard configs, adopt the stuff that is already common, and then apply the things we agree to standardize on. That way we can more easily track changes against the default configs so that when versions change we can decide what to do.