GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — arrow-java/CONTRIBUTING.md at main · rluvaton/arrow-java

Expand file tree

/

CONTRIBUTING.md

Copy path
More file actions
More file actions

Latest commit

 

History

History
History
58 lines (41 loc) · 2.57 KB
/

CONTRIBUTING.md

Copy path

File metadata and controls

58 lines (41 loc) · 2.57 KB
Raw
Copy raw file
Download raw file
Outline
Edit and raw actions

How to contribute to Apache Arrow Java

Did you find a bug?

The Arrow Java project uses GitHub as a bug tracker. To report a bug, sign in to your GitHub account, navigate to GitHub issues and click on New issue .

Before you create a new bug entry, we recommend you first search among existing Arrow issues in GitHub.

Did you write a patch that fixes a bug or brings an improvement?

Create a GitHub issue and submit your changes as a GitHub Pull Request. Please make sure to reference the issue in your PR description.

Minor Fixes

Any functionality change should have a GitHub issue opened. For minor changes that affect documentation, you do not need to open up a GitHub issue. Instead you can prefix the title of your PR with "MINOR: " if it meets one of the following:

  • Grammar, usage and spelling fixes that affect no more than 2 files
  • Documentation updates affecting no more than 2 files and not more than 500 words.

Do you want to propose a significant new feature or an important refactoring?

We ask that all discussions about major changes in the codebase happen publicly on the arrow-dev mailing-list.

Do you have questions about the source code, the build procedure or the development process?

You can also ask on the mailing-list, see above.

Further information

Please read our development documentation or look through the New Contributor's Guide.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.