docs: Improve main README.md and highlight community #9119
+32
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alamb
force-pushed
the
alamb/improved_comms_docs
branch
from
83cde1c to
a233332
Compare
alamb
commented
Jan 9, 2026
| ### Rust Version Compatibility Policy | ||
|
|
||
| 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. | ||
| 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. |
|
|
||
| You can find more details about each crate in their respective READMEs. | ||
|
|
||
| ## Arrow Rust Community |
Contributor
Author
There was a problem hiding this comment.
moved to the top and clarified
| # Native Rust implementation of Apache Arrow and Apache Parquet | ||
|
|
||
| Welcome to the [Rust][rust] implementation of [Apache Arrow], the popular in-memory columnar format. | ||
| Welcome to the [Rust][rust] implementation of [Apache Arrow], a popular |
Contributor
Author
There was a problem hiding this comment.
Also note this repo has the parquet implementation
Jefffrey
approved these changes
Jan 10, 2026
| conduct](https://www.apache.org/foundation/policies/conduct.html). | ||
|
|
||
| We use GitHub [issues] and [pull requests] for all technical discussions, reviews, | ||
| new features, bug fixes and release coordiation. This ensures that all communication |
Contributor
There was a problem hiding this comment.
Suggested change
| new features, bug fixes and release coordiation. This ensures that all communication | |
| new features, bug fixes and release coordination. This ensures that all communication |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
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
Are these changes tested?
CI
Are there any user-facing changes?