Skip to content

Latest commit

 

History

History
146 lines (113 loc) · 6.08 KB

community.md

File metadata and controls

146 lines (113 loc) · 6.08 KB
Raw
layout title description
article
Apache Arrow Community
Links and resources for participating in Apache Arrow

Apache Arrow Community

We welcome participation from everyone and encourage you to join us, ask questions, and get involved.

All participation in the Apache Arrow project is governed by the Apache Software Foundation's code of conduct.

Questions?

Mailing lists

These arrow.apache.org mailing lists are for project discussion:

  • user@ is for questions on using Apache Arrow libraries {% include mailing_list_links.html list="user" %}
  • dev@ is for discussions about contributing to the project development {% include mailing_list_links.html list="dev" %}

Tags

The mailing lists follow the convention of prefixing subjects with one or more tags in order to clarify the scope and purpose of messages. For example:

  • [ANNOUNCE] Apache Arrow 11.0.0 released
  • [DISCUSS][C++] C++ API as a user-facing API
  • [Java][Arrow IPC] Extreme memory usage when reading feather files

When emailing one of the lists, please prefix the subject line with one or more tags. Depending the topic of your email, tags may include one or more:

  • Supported Environments: e.g., [C++], [Java], [Python], etc.
  • Specifications and Protocols: e.g., [Format], [Flight RPC], [ADBC], etc.

You may also prefix your subject line with [DISCUSS] if your email is intended to prompt a discussion rather than get an answer to a specific question.

Voting

Votes are held periodically on the dev@ mailing list and are indicated by the [VOTE] prefix. These votes are part of the formal Apache Software Foundation voting process. Members of the community are encouraged to engage with these posts by replying with a body of "+1 (non-binding)" if they are in support of the respective proposal. The result of a vote will be posted back to the dev@ mailing list with the prefix [RESULT][VOTE].

Other Lists

You may also wish to subscribe to these lists, which capture some activity streams:

  • issues@ for the creation of GitHub issues {% include mailing_list_links.html list="issues" %}
  • commits@ for commits to the apache/arrow and apache/arrow-site repositories (typically to main only) {% include mailing_list_links.html list="commits" %}
  • builds@ for nightly build reports {% include mailing_list_links.html list="builds" %}

In addition, we have some "firehose" lists, which exist so that development activity is captured in email form for archival purposes.

  • github@ for all activity on the GitHub repositories {% include mailing_list_links.html list="github" %}

Stack Overflow

For questions on how to use Arrow libraries, you may want to use the Stack Overflow tag apache-arrow in addition to the programming language. Some languages and subprojects may have their own tags (for example, pyarrow).

GitHub issues

We use GitHub issues as a way to ask questions and engage with the Arrow developer community and for maintaining a queue of development work and as the public record of work on the project. We use the mailing lists for development discussions, where a lengthy discussions is required.

Meetings

We host online meetings to provide spaces for synchronous discussions about the Arrow project. These discussions usually focus on topics of interest to developers who are contributing to Arrow, but we welcome users of Arrow to join. Currently there are three series of regularly held meetings:

Meeting Frequency Notes
Arrow community meeting Biweekly Google Doc
Arrow R package development meeting Biweekly Google Doc
Arrow Rust sync meeting Varies Google Doc
PyArrow development meeting Every 4 weeks Google Doc

For information about how to attend these meetings, see the meeting notes and subscribe to the dev@ mailing list as described above. The hosts of some of these meetings send reminder emails to the mailing list prior to each meeting with information about how to join.

Contributing

As mentioned above, we use GitHub for our issue tracker and for source control. See the [contribution guidelines]({{ site.baseurl }}/docs/developers/index.html) for more.