Join the active community of Solr Operator contributors.


The Solr Operator community provides user support for free through the users mailing list and slack channels.

Mailing Lists & Chat

The Solr Operator shares mailing lists with its parent project, Apache Solr. Available lists can be found here.


Issue tracker

The Solr Operator uses Github issues in it's repository for issue tracking.

How To Contribute

Looking to contribute to the Solr Operator? Read the instructions on development and then submit a PR!

Code of Conduct

For a large and diverse community like ours to be friendly, welcoming and respectful, we recognize the need for some guidelines. The project follows Apache's Code of Conduct statement. Please take some time to read and understand it.

If you feel there has been a violation of this code, please point out your concerns publicly in a friendly and matter of fact manner. Nonverbal communication is prone to misinterpretation and misunderstanding. Everyone has bad days and sometimes says things they regret later. Someone else's communication style may clash with yours, but the difference can be amicably resolved. After pointing out your concerns please be generous upon receiving an apology.

Should there be repeated instances of code of conduct violations, or if there is an obvious and severe violation, the Solr PMC may become involved.

The Apache Way

As an Apache project we strive to follow The Apache Way. If you are new to the community or to open source in general, you may benefit from understanding our core values as a community, and why we operate the way we do.

Version Control

The Solr source code resides in the Apache GIT repository. Various GIT clients can be obtained from There are also GIT integrations for various IDEs. For Eclipse, look at EGit. IntelliJ has git support bundled, if you have installed the command line version.

Web Access (read-only)

The source code can be browsed at and also No GIT client software is required.

Cloning the repository

To work on the code locally, you may clone the git repository:

git clone

Then use GitHub's fork feature to obtain a personal fork from which you can later contribute your changes through a Pull Request

You may alternatively choose to clone apache's git mirror at