Skip to content

Community

Substrait is developed as a consensus-driven open source product under the Apache 2.0 license. Development is done in the open leveraging GitHub issues and PRs.

Get In Touch

Mailing List/Google Group
We use the mailing list to discuss questions, formulate plans and collaborate asynchronously.
Slack Channel
The developers of Substrait frequent the Slack channel. You can get an invite to the channel by following this link.
GitHub Issues
Substrait is developed via GitHub issues and pull requests. If you see a problem or want to enhance the product, we suggest you file a GitHub issue for developers to review.
Twitter
The @substrait_io account on Twitter is our official account. Follow-up to keep to date on what is happening with Substrait!
Docs
Our website is all maintained in our source repository. If there is something you think can be improved, feel free to fork our repository and post a pull request.
Meetings
Our community meets every other week on Wednesday.

Talks

Want to learn more about Substrait? Try the following presentations and slide decks.

  • Substrait: A Common Representation for Data Compute Plans (Jacques Nadeau, April 2022) [slides]

Citation

If you use Substrait in your research, please cite it using the following BibTeX entry:

@misc{substrait,
  author = {substrait-io},
  title = {Substrait: Cross-Language Serialization for Relational Algebra},
  year = {2021},
  month = {8},
  day = {31},
  publisher = {GitHub},
  journal = {GitHub repository},
  howpublished = {\url{https://github.com/substrait-io/substrait}}
}

Contribution

All contributors are welcome to Substrait. If you want to join the project, open a PR or get in touch with us as above.

AI Contribution Policy

The Substrait project is open to AI-assisted contributions.

We do ask that you disclose what AI tools are being used, and how they are being used. This allows reviewers to understand what areas may need additional focus, and helps us learn about useful patterns for using AI tooling.

Additionally, you should self-review any generated products before asking for reviewer time.

Principles

  • Be inclusive and open to all.
  • Ensure a diverse set of contributors that come from multiple data backgrounds to maximize general utility.
  • Build a specification based on open consensus.
  • Avoid over-reliance/coupling to any single technology.
  • Make the specification and all tools freely available on a permissive license (ApacheV2)