Skip to content

Latest commit



186 lines (127 loc) · 6.75 KB

File metadata and controls

186 lines (127 loc) · 6.75 KB

Contribution Guidelines

Thank you for your interest in!

This project welcomes contributions and suggestions.

Contributions come in many forms: submitting issues, writing code, participating in discussions and community calls.

This document provides the guidelines for how to contribute to the project.


This section describes the guidelines for submitting issues

Issue Types

There are 4 types of issues:

  • Issue/Bug: You've found a bug with the code, and want to report it, or create an issue to track the bug.
  • Issue/Discussion: You have something on your mind, which requires input from others in a discussion, before it eventually manifests as a proposal.
  • Issue/Proposal: Used for items that propose a new idea or functionality. This allows feedback from others before code is written.
  • Issue/Question: Use this issue type, if you need help or have a question.

Before You File

Before you file an issue, make sure you've checked the following:

  1. Check for existing issues
    • Before you create a new issue, please do a search in open issues to see if the issue or feature request has already been filed.
    • If you find your issue already exists, make relevant comments and add your reaction. Use a reaction:
      • 👍 up-vote
      • 👎 down-vote
  2. For bugs
    • You have as much data as possible. This usually comes in the form of logs and/or stacktraces. Screenshots or screen recordings of the buggy behavior are very helpful.

Contributing to

This section describes the guidelines for contributing code / docs to

Follow principles and guidelines

Pull Requests

All contributions come through pull requests. To submit a proposed change, we recommend following this workflow:

  1. Make sure there's an issue (bug or proposal) raised, which sets the expectations for the contribution you are about to make.
  2. Fork the repo and create a new branch
  3. Create your change
    • Code changes require tests
  4. Update relevant documentation for the change
  5. Commit and open a PR
  6. Wait for the CI process to finish and make sure all checks are green
  7. A maintainer of the project will be assigned, and you can expect a review within a few days

Use work-in-progress PRs for early feedback

A good way to communicate before investing too much time is to create a "Work-in-progress" PR and share it with your reviewers. The standard way of doing this is to add a "[WIP]" prefix in your PR's title and assign the do-not-merge label. This will let people looking at your PR know that it is not well baked yet.

Security Vulnerability Reporting takes security and our users' trust very seriously. If you believe you have found a security issue in any of our open source projects, please responsibly disclose it by contacting

Use of Third-party code

  • Third-party code must include licenses.


spiceai consists of two main binaries. spiced is the runtime daemon written in Rust. spice is the command line interface for end users written in go. All targets can be built from Makefiles.

Setting up your development environment


# Install Xcode Command Line Tools
xcode-select --install

# Install Homebrew
# Note: Be sure to follow the steps in the Homebrew installation output to add Homebrew to your PATH.
/bin/bash -c "$(curl -fsSL"

# Install dependencies
brew install rust
brew install go

# Cmake/Protobuf are only required for building the databricks connector
brew install cmake
brew install protobuf

# Clone SpiceAI OSS Repo
git clone
cd spiceai

# Build and install OSS project in release mode
make install

# Build and install OSS project in dev mode
make install-dev

# Also you can specify specific features
SPICED_CUSTOM_FEATURES="postgres sqlite" make install

# Run the following to temporarily add spice to your PATH.
# Add it to the end of your .bashrc or .zshrc to permanently add spice to your PATH.
export PATH="$PATH:$HOME/.spice/bin"

# Initialize and run a test app to ensure everything is working
cd ../
mkdir test-app
cd test-app
spice init test-app
spice run

VSCode Configuration

To configure VSCode to automatically apply the rustfmt style on save and to use the same Clippy rules we enforce in our CI as the default, add the following in your User Settings JSON file:

  "[rust]": {
    "editor.defaultFormatter": "rust-lang.rust-analyzer",
    "editor.formatOnSave": true,
  "rust-analyzer.check.command": "clippy",
  "rust-analyzer.check.features": "all",
  "rust-analyzer.check.extraArgs": ["--", "-Dclippy::pedantic", "-Dclippy::unwrap_used", "-Dclippy::clone_on_ref_ptr"]

By default, rust-analyzer will attempt to rebuild all dependencies when a change is made to a cargo.toml file. To prevent this and only rebuild what has changed, add the following in your User Settings JSON file, setting the value to your architecture:

   "": "aarch64-apple-darwin",

To see all valid values use rustc --print target-list.

Build Options

spiced is the default-member of the Cargo workspace crate. Its manifests should allow custom builds where heavy dependencies are optional.

Other workspace crates shouldn't include large features by default. This makes excluding features less error prone. Alternatively, crates that depend on those workspace crates need to set default-features = false.

For example, to support a newly popular database called newdb, add it by default to bin/Cargo.toml:

-default = ["duckdb", "postgres", "sqlite", "mysql"]
+default = ["duckdb", "postgres", "sqlite", "mysql", "newdb"]

Next, create the same feature in crates that implement a newdb connector or dataset:

newdb = ["runtime/newdb", "spicepod/newdb", "app/newdb"]

Include external dependencies optionally and with dep: prefix in features:

newdb = [

Finally, tag code and module imports with #[cfg(feature = "newdb")]. To build spiced with only newdb and some other desired features:

SPICED_CUSTOM_FEATURES="newdb postgres" make build-runtime

Ideally none or few unused code warnings should be emitted. If not, consider refactorings.

Thank You! - Your contributions to open source, large or small, make projects like this possible. Thank you for taking the time to contribute.