Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mailing list descriptions to documentation #10284

Merged
merged 3 commits into from
Apr 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 29 additions & 12 deletions docs/source/contributor-guide/communication.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,18 +37,35 @@ We use the Slack and Discord platforms for informal discussions and coordination
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](https://s.apache.org/slack-invite) .
Unfortunately, due to spammers, the ASF Slack workspace requires an invitation to join. To get an invitation,
request one in the `Arrow Rust` channel of the [Arrow Rust Discord server](https://discord.gg/Qw5gKqHxUM).
Most of us use the `#datafusion` and `#arrow-rust` channels in the [ASF Slack
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also clarified the section on slack/discord to reflect the current reality

workspace](https://s.apache.org/slack-invite) and the [Arrow Rust Discord
server](https://discord.gg/Qw5gKqHxUM) for discussions.

## Mailing list
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.

We also use arrow.apache.org's `dev@` mailing list for release coordination and occasional design discussions. Other
than the release process, most DataFusion mailing list traffic will link to a GitHub issue or PR for discussion.
([subscribe](mailto:[email protected]),
[unsubscribe](mailto:[email protected]),
[archives](https://lists.apache.org/[email protected])).
## Mailing Lists

When emailing the dev list, please make sure to prefix the subject line with a
`[DataFusion]` tag, e.g. `"[DataFusion] New API for remote data sources"`, so
that the appropriate people in the Apache Arrow community notice the message.
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:

- [`[email protected]`](mailto:[email protected]): the main
mailing list for release coordination and other project-wide discussions. Links:
[archives](https://lists.apache.org/[email protected]),
[subscribe](mailto:[email protected]),
[unsubscribe](mailto:[email protected])
- `[email protected]`: read-only mailing list that receives all GitHub notifications for the project. Links:
[archives](https://lists.apache.org/[email protected])
- `[email protected]`: read-only mailing list that receives all GitHub commits for the project. Links:
[archives](https://lists.apache.org/[email protected])
- `[email protected]`: private mailing list for PMC members. This list has very little traffic, almost exclusively discussions on growing the committer and PMC membership. Links:
[archives](https://lists.apache.org/[email protected])

[mailing lists]: https://www.apache.org/foundation/mailinglists

```

```
Loading