Communication¶

We welcome participation from everyone and encourage you to join us, ask questions, and get involved.

All participation in the Apache DataFusion project is governed by the Apache Software Foundation’s code of conduct.

GitHub¶

The vast majority of communication occurs in the open on our github repository in the form of tickets, issues, discussions, and Pull Requests.

Slack and Discord¶

We use the Slack and Discord platforms for informal discussions and coordination. These are great places to meet other contributors and get guidance on where to contribute. It is important to note that any technical designs and decisions are made fully in the open, on GitHub.

Most of us use the #datafusion and #arrow-rust channels in the ASF Slack workspace and the Arrow Rust Discord server for discussions.

Unfortunately, due to spammers, the ASF Slack workspace requires an invitation to join. We are happy to invite you – please ask for an invitation in the Discord server.

Mailing Lists¶

Like other Apache projects, we use mailing lists for certain purposes, most importantly release coordination. Other than the release process, most DataFusion mailing list traffic will simply link to a GitHub issue or PR where the actual discussion occurs. The project mailing lists are:

dev@datafusion.apache.org: the main mailing list for release coordination and other project-wide discussions. Links: archives, subscribe, unsubscribe
github@datafusion.apache.org: read-only mailing list that receives all GitHub notifications for the project. Links: archives
commits@datafusion.apache.org: read-only mailing list that receives all GitHub commits for the project. Links: archives
private@datafusion.apache.org: private mailing list for PMC members. This list has very little traffic, almost exclusively discussions on growing the committer and PMC membership. Links: archives

Introduction

Architecture