Splice Machine is now open source! We have shared nearly all of our source code with the open source community. With the source you can build and deploy a fully functioning RDBMS.
We have adopted the Apache® v2.0 license model for our source code.
Contributing to the Project
The community is welcome and encouraged to jump in and make contributions. Here’s how you can help:
- Test the product, and file any issues you find. Our JIRA page for bug tracking is found at: https://splice.atlassian.net
- Work on bugs or enhancements for the product. Our open source repository can be found on GitHub at https://github.com/splicemachine/spliceengine. Instructions for building can be found in the README.md and GETTING-STARTED.md files at the root of the project. When ready to dive in, developers should Fork off of the codeline, make changes, run tests to validate fixes, and submit pull requests. We plan to shortly flag those JIRA issues that should be good starter tasks. Note: the Program Management Committee has final say in which code is accepted into the code line.
- Review/enhance the documentation. If you find issues or opportunities for improvement with the documentation, file a JIRA, and feel free recommended documentation changes yourself.
- Help others in the Community. Questions may come in from mailing lists, Slack channels, Stack Overflow, etc.
The project’s Program Management Committee (PMC) – the committee with general oversight over the project, includes:
- John Leach
- Monte Zweben
- Gene Davis
They can be reached at PMC@splicemachine.com.
Committers – Individuals with authority to check in code directly and approve Pull Requests – initially these are the development team at Splice Machine.
Release Schedule – Releases are defined using “major.minor.patch” numbering. A release “train” will go out approximately every 2 weeks as a patch, assuming the codeline passess all relevant QA tests. After an appropriate number of patches or improvements is checked in, minor and/or major release updates will be released through approval of the PMC.
Questions? Feedback? We want to hear from you!
We have multiple channels for community interaction: