Skip to content

Commit ed77d92

Browse files
committed
docs: Refine "communication" documentation to highlight Discord
1 parent 8ba4646 commit ed77d92

File tree

2 files changed

+36
-35
lines changed

2 files changed

+36
-35
lines changed

docs/source/contributor-guide/communication.md

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -17,56 +17,56 @@
1717
under the License.
1818
-->
1919

20-
# Communication
20+
# Community Communication
2121

2222
We welcome participation from everyone and encourage you to join us, ask
2323
questions, and get involved.
24-
2524
All participation in the Apache DataFusion project is governed by the
2625
Apache Software Foundation's [code of
2726
conduct](https://www.apache.org/foundation/policies/conduct.html).
2827

2928
## GitHub
3029

31-
The vast majority of communication occurs in the open on our
32-
[github repository](https://github.com/apache/datafusion) in the form of tickets, issues, discussions, and Pull Requests.
30+
The primary means of communication is the
31+
[GitHub repository](https://github.com/apache/datafusion) in the form of tickets, issues, discussions, and Pull Requests.
32+
Our repository is open to everyone. We encourage you to
33+
participate by reporting issues, asking questions, and contributing code.
3334

34-
## Slack and Discord
35+
## Chat
3536

36-
We use the Slack and Discord platforms for informal discussions and coordination. These are great places to
37-
meet other contributors and get guidance on where to contribute. It is important to note that any technical designs and
38-
decisions are made fully in the open, on GitHub.
37+
We also use the Discord and Slack platforms for lower latency, informal discussions and coordination.
38+
These are great places to
39+
meet other members of the community, ask questions, and brainstorm ideas.
40+
However, to ensure technical discussions are archived and accessible to everyone,
41+
all technical designs are recorded and formalized in GitHub issues.
3942

40-
Most of us use the [ASF Slack
41-
workspace](https://s.apache.org/slack-invite) and the [Arrow Rust Discord
42-
server][discord-link] for discussions.
43+
### Discord
4344

44-
There are specific channels for Arrow, DataFusion, and the DataFusion subprojects (Ballista, Comet, Python, etc).
45+
Historically, the most active discussion forum has been the [Arrow Rust Discord
46+
server][discord-link] which has specific channels for Arrow, DataFusion, and
47+
DataFusion subprojects such as Ballista, Comet, Python, etc.
48+
DataFusion specific channels are prefixed with the `#datafusion-` tag.
49+
We recommend new users join this server for real-time discussions with the community.
4550

46-
In Slack we use these channels:
51+
### Slack
4752

48-
- #arrow
49-
- #arrow-rust
50-
- #datafusion
51-
- #datafusion-ballista
52-
- #datafusion-comet
53-
- #datafusion-python
53+
Some of the community also uses the [ASF Slack workspace] for discussions. This
54+
has historically been much less active than the Discord server.
55+
Unfortunately, due to spammers, the ASF Slack workspace [requires an invitation]
56+
to join. We are happy to invite any community member -- please ask for an
57+
invitation in the Discord server.
5458

55-
In Discord we use these channels:
59+
[asf slack workspace]: https://the-asf.slack.com/
60+
[requires an invitation]: https://s.apache.org/slack-invite
5661

57-
- #ballista
58-
- #comet
59-
- #contrib-federation
60-
- #datafusion
61-
- #datafusion-python
62-
- #dolomite-optimizer
63-
- #general
64-
- #hiring
65-
- #incremental-materialized-views
62+
In Slack, we use these channels:
6663

67-
Unfortunately, due to spammers, the ASF Slack workspace requires an invitation
68-
to join. We are happy to invite you -- please ask for an invitation in the
69-
Discord server.
64+
- `#arrow`
65+
- `#arrow-rust`
66+
- `#datafusion`
67+
- `#datafusion-ballista`
68+
- `#datafusion-comet`
69+
- `#datafusion-python`
7070

7171
### Job Board
7272

@@ -77,8 +77,8 @@ Please feel free to post links to DataFusion related jobs there.
7777
## Mailing Lists
7878

7979
Like other Apache projects, we use [mailing lists] for certain purposes, most
80-
importantly release coordination. Other than the release process, most
81-
DataFusion mailing list traffic will simply link to a GitHub issue or PR where
80+
importantly release coordination and announcing new committers and PMC members.
81+
Other than these processes, most DataFusion mailing list traffic will link to a GitHub issue or PR where
8282
the actual discussion occurs. The project mailing lists are:
8383

8484
- [`dev@datafusion.apache.org`](mailto:dev@datafusion.apache.org): the main

docs/source/index.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The following related subprojects target end users and have separate documentati
6161
"Out of the box," DataFusion offers `SQL <https://datafusion.apache.org/user-guide/sql/index.html>`_
6262
and `Dataframe <https://docs.rs/datafusion/latest/datafusion/dataframe/struct.DataFrame.html>`_ APIs,
6363
excellent `performance <https://benchmark.clickhouse.com/>`_, built-in support for CSV, Parquet, JSON, and Avro,
64-
extensive customization, and a great community.
64+
extensive customization, and a great `community`_.
6565
`Python Bindings <https://github.com/apache/datafusion-python>`_ are also available.
6666
`Ballista <https://datafusion.apache.org/ballista/>`_ is Apache DataFusion extension enabling the parallelized execution of workloads across multiple nodes in a distributed environment.
6767

@@ -81,6 +81,7 @@ To get started, see
8181
.. _datafusion-examples: https://github.com/apache/datafusion/tree/main/datafusion-examples
8282
.. _developer’s guide: contributor-guide/index.html#developer-s-guide
8383
.. _library user guide: library-user-guide/index.html
84+
.. _community: contributor-guide/communication.html
8485
.. _communication: contributor-guide/communication.html
8586

8687
.. _toc.asf-links:

0 commit comments

Comments
 (0)