@@ -37,18 +37,31 @@ We use the Slack and Discord platforms for informal discussions and coordination
37
37
meet other contributors and get guidance on where to contribute. It is important to note that any technical designs and
38
38
decisions are made fully in the open, on GitHub.
39
39
40
- Most of us use the ` #datafusion ` and ` #arrow-rust ` channels in the [ ASF Slack workspace ] ( https://s.apache.org/slack-invite ) .
41
- Unfortunately, due to spammers, the ASF Slack workspace requires an invitation to join. To get an invitation,
42
- request one in the ` Arrow Rust ` channel of the [ Arrow Rust Discord server] ( https://discord.gg/Qw5gKqHxUM ) .
40
+ Most of us use the ` #datafusion ` and ` #arrow-rust ` channels in the [ ASF Slack
41
+ workspace] ( https://s.apache.org/slack-invite ) and the [ Arrow Rust Discord
42
+ server] ( https://discord.gg/Qw5gKqHxUM ) for discussions .
43
43
44
- ## Mailing list
44
+ Unfortunately, due to spammers, the ASF Slack workspace requires an invitation
45
+ to join. We are happy to invite you -- please ask for an invitation in the
46
+ Discord server.
45
47
46
- We also use arrow.apache.org's ` dev@ ` mailing list for release coordination and occasional design discussions. Other
47
- than the release process, most DataFusion mailing list traffic will link to a GitHub issue or PR for discussion.
48
- (
[ subscribe
] ( mailto:[email protected] ) ,
49
- [ unsubscribe
] ( mailto:[email protected] ) ,
50
- [ archives
] ( https://lists.apache.org/[email protected] ) ).
48
+ ## Mailing Lists
51
49
52
- When emailing the dev list, please make sure to prefix the subject line with a
53
- ` [DataFusion] ` tag, e.g. ` "[DataFusion] New API for remote data sources" ` , so
54
- that the appropriate people in the Apache Arrow community notice the message.
50
+ Like other Apache projects, we use [ mailing lists] for certain purposes, most
51
+ importantly release coordination. Other than the release process, most
52
+ DataFusion mailing list traffic will simply link to a GitHub issue or PR where
53
+ the actual discussion occurs. The project mailing lists are:
54
+
55
+
56
+ mailing list for release coordination and other project-wide discussions. Links:
57
+ [ archives
] ( https://lists.apache.org/[email protected] ) ,
58
+ [ subscribe
] ( mailto:[email protected] ) ,
59
+ [ unsubscribe
] ( mailto:[email protected] )
60
+ - ` [email protected] ` : read-only mailing list that receives all GitHub notifications for the project. Links:
61
+ [ archives
] ( https://lists.apache.org/[email protected] )
62
+ - ` [email protected] ` : read-only mailing list that receives all GitHub commits for the project. Links:
63
+ [ archives
] ( https://lists.apache.org/[email protected] )
64
+ - ` [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:
65
+ [ archives
] ( https://lists.apache.org/[email protected] )
66
+
67
+ [ mailing lists ] : https://www.apache.org/foundation/mailinglists
0 commit comments