You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: Improve main README.md and highlight community (apache#9119)
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax.
-->
- Closes #NNN.
# Rationale for this change
One of my new years resolutions is to try and encourage / build the
arrow-rs community more. Part of doing so is to lower the barrier for
new contributors with clear communication and documentation.
Thus I would like to improve the main readme
# What changes are included in this PR?
Update the README. See rendered preview here:
https://github.com/alamb/arrow-rs/blob/alamb/improved_comms_docs/README.md
1. Move community section to the top of the README file
2. Clarify that most communication happens on github
<img width="1348" height="775" alt="Screenshot 2026-01-09 at 9 33 06 AM"
src="https://github.com/user-attachments/assets/fc3f6041-478d-4170-bb40-3956764a9b8d"
/>
# Are these changes tested?
CI
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
If there are any breaking changes to public APIs, please call them out.
-->
---------
Co-authored-by: Jeffrey Vo <jeffrey.vo.australia@gmail.com>
We use GitHub [issues] and [pull requests] for all technical discussions, reviews,
34
+
new features, bug fixes and release coordination. This ensures that all communication
35
+
is public and archived for future reference.
36
+
37
+
The `dev@arrow.apache.org` mailing list is the communication channel for the overall Apache Arrow community.
38
+
Instructions for signing up and links to the archives can be found on the [Arrow Community](https://arrow.apache.org/community/) page.
39
+
40
+
Some community members also use the [Arrow Rust Discord Server](https://discord.gg/YAb2TdazKQ) and the official [ASF Slack](https://s.apache.org/slack-invite) server for informal discussions and coordination.
41
+
This is a great place to meet other contributors and get guidance on where to contribute.
42
+
However, all technical designs should also be recorded and formalized in GitHub issues, so that they are accessible to everyone.
43
+
In Slack, find us in the `#arrow-rust` channel and feel free to ask for an invite via Discord, GitHub issues, or other means.
44
+
45
+
There is more information in the [contributing] guide.
|[`arrow-flight`]| Support for Arrow-Flight IPC protocol |[docs.rs](https://docs.rs/arrow-flight/latest)|[(README)][flight-readme]|
30
-
|[`parquet`]| Support for Parquet columnar file format|[docs.rs](https://docs.rs/parquet/latest)|[(README)][parquet-readme]|
55
+
|[`parquet`]| Support for the [Apache Parquet] columnar file format |[docs.rs](https://docs.rs/parquet/latest)|[(README)][parquet-readme]|
31
56
|[`parquet_derive`]| A crate for deriving RecordWriter/RecordReader for arbitrary, simple structs |[docs.rs](https://docs.rs/parquet-derive/latest)|[(README)][parquet-derive-readme]|
32
57
33
-
The current development version the API documentation in this repo can be found [here](https://arrow.apache.org/rust).
58
+
The current development version the API documentation can be found [here](https://arrow.apache.org/rust).
34
59
35
60
Note: previously the [`object_store`] crate was also part of this repository,
36
61
but it has been moved to the [arrow-rs-object-store repository]
Due to available maintainer and testing bandwidth, [`arrow`] crates ([`arrow`],
51
77
[`arrow-flight`], etc.) are released on the same schedule with the same versions
52
-
as the [`parquet`] and [`parquet-derive`] crates.
78
+
as the [`parquet`] and [`parquet_derive`] crates.
53
79
54
80
This crate releases every month. We release new major versions (with potentially
55
81
breaking API changes) at most once a quarter, and release incremental minor
@@ -81,7 +107,7 @@ Planned Release Schedule
81
107
82
108
### Rust Version Compatibility Policy
83
109
84
-
arrow-rs and parquet are built and tested with stable Rust, and will keep a rolling MSRV (minimum supported Rust version) that can only be updated in major releases on a need by basis (e.g. project dependencies bump their MSRV or a particular Rust feature is useful for us etc.). The new MSRV if selected will be at least 6 months old. The minor releases are guaranteed to have the same MSRV.
110
+
arrow-rs and parquet are built and tested with stable Rust, and will keep a rolling MSRV (minimum supported Rust version) that can only be updated in major releases on an as needed basis (e.g. project dependencies bump their MSRV or a particular Rust feature is useful for us etc.). The new MSRV if selected will be at least 6 months old. The minor releases are guaranteed to have the same MSRV.
85
111
86
112
Note: If a Rust hotfix is released for the current MSRV, the MSRV will be updated to the specific minor version that includes all applicable hotfixes preceding other policies.
87
113
@@ -152,24 +178,6 @@ including `join`s and window functions.
152
178
153
179
You can find more details about each crate in their respective READMEs.
154
180
155
-
## Arrow Rust Community
156
-
157
-
The `dev@arrow.apache.org` mailing list serves as the core communication channel for the Arrow community. Instructions for signing up and links to the archives can be found on the [Arrow Community](https://arrow.apache.org/community/) page. All major announcements and communications happen there.
158
-
159
-
The Rust Arrow community also uses the official [ASF Slack](https://s.apache.org/slack-invite) for informal discussions and coordination. This is
160
-
a great place to meet other contributors and get guidance on where to contribute. Join us in the `#arrow-rust` channel and feel free to ask for an invite via:
161
-
162
-
1. the `dev@arrow.apache.org` mailing list
163
-
2. the [GitHub Discussions][discussions]
164
-
3. the [Discord channel](https://discord.gg/YAb2TdazKQ)
165
-
166
-
The Rust implementation uses [GitHub issues][issues] as the system of record for new features and bug fixes and
167
-
this plays a critical role in the release process.
168
-
169
-
For design discussions we generally use GitHub issues.
170
-
171
-
There is more information in the [contributing] guide.
0 commit comments