Development#
Connection to the specific language development pages:
Contributing to Apache Arrow#
Thanks for your interest in the Apache Arrow project.
Arrow is a large project and may seem overwhelming when you’refirst getting involved. Contributing code is great, but that’sprobably not the first place to start. There are lots of ways tomake valuable contributions to the project and community.
This page provides some orientation for how to get involved. It also offerssome recommendations on how to get the best results when engaging with thecommunity.
Code of Conduct#
All participation in the Apache Arrow project is governed by the ASF’sCode of Conduct.
A good first step to getting involved in the Arrow project is to jointhe mailing lists and participate in discussions where you can.
Alerting us to unexpected behavior and missing features, evenif you can’t solve the problems yourself, help us understandand prioritize work to improve the libraries.
Communicating through the mailing lists
Projects in The Apache Software Foundation (“the ASF”) use public, archivedmailing lists to create a public record of each project’s developmentactivities and decision-making process.
While lacking the immediacy of chat or other forms of communication,the mailing lists give participants the opportunity to slow down and bethoughtful in their responses, and they help developers who are spread acrossmany timezones to participate more equally.
Read more on theApache Arrow Communitypage.
Improve documentation
A great way to contribute to the project is to improve documentation. If youfound some docs to be incomplete or inaccurate, share your hard-earned knowledgewith the rest of the community.
Documentation improvements are also a great way to gain some experience withour submission and review process, discussed below, without requiring a lotof local development environment setup. In fact, many documentation-only changescan be made directly in the GitHub web interface by clicking the “edit” button.This will handle making a fork and a pull request for you.
First time contributing?
The New Contributor’s Guide provides necessary information forcontributing to the Apache Arrow project.
A short overview of the contributing process we followand some additional information you might need if you are notnew to the contributing process in general.
Continuous Integration
Continuous Integration needs to run across different combinations of package managers, compilers, versions of multiplesoftware libraries, operating systems, and other potential sources of variation.
Read more on theContinuous Integration page.
Benchmarks
How to use the benchmark suite can be found on theBenchmarks page.
Release Guide
To learn about the detailed information on the steps followed to perform a release, seeRelease Management Guide.
Release Verification Process
To learn how to verify a release, seeRelease Verification Process.