Add Arrow Hackathon page #49
+66
−1
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,65 @@ | ||
| --- | ||
| title: "Apache Arrow — Hackathon at Community over Code Glasgow 2026" | ||
| --- | ||
|
|
||
| <img src="/images/apache-oak-leaf.svg" alt="Apache" style="height:1.4em; vertical-align:middle;"> **[Community over Code 2026](https://communityovercode.org) — Glasgow, UK, October 11–14** | ||
|
|
||
| **[Register now](https://communityovercode.apache.org/events/glasgow-2026/register)** | [Event website](https://communityovercode.org) | [Hackathon overview](hackathon.html) | ||
|
|
||
| ## Apache Arrow — Hackathon | ||
|
|
||
| <!-- Copy this file to yourproject.md (lowercase, no spaces) and fill | ||
| in the sections below. Then add a link to your page from the table | ||
| in hackathon.md. Submit both changes as a single PR. --> | ||
|
|
||
| ### Coordinator | ||
|
|
||
| <!-- Who is the point of contact for your project at the hackathon? | ||
| This person should be present at the event and available to help | ||
| participants get started. --> | ||
|
|
||
| * **Nic Crane** — thisisnic@apache.org | ||
| * **Matt Topol** — zeroshade@apache.org | ||
|
|
||
| ### What We're Working On | ||
|
|
||
| <!-- Describe the kinds of tasks participants can expect. Be as specific | ||
| as you like — or link to a curated issue list. Indicate difficulty | ||
| levels where possible so participants can self-select. --> | ||
|
|
||
| We're focusing on: | ||
|
|
||
| * **Good first issues** — small, well-scoped tasks suitable for new | ||
| contributors: [GitHub issues labeled "good first issue"](https://github.com/apache/arrow/issues?q=label%3A%22good+first+issue%22) | ||
|
Member
There was a problem hiding this comment. same comment as above, can we add the link for the "good first issue" label for arrow-go issues as well? |
||
| * **Documentation improvements** — help us improve our getting-started | ||
| guides and API docs | ||
| * **Bug fixes** — a curated set of bugs that are approachable with | ||
| mentoring support | ||
|
|
||
| ### Resources | ||
|
|
||
| <!-- Link to anything that helps participants prepare or find their way | ||
| in — issue trackers, mailing list threads, discussion forums, chat | ||
| channels, contribution guides, dev environment setup docs, etc. --> | ||
|
|
||
| * [Contribution guide and dev setup](https://arrow.apache.org/docs/developers/guide/index.html) | ||
| * [Dev mailing list thread about the hackathon](https://lists.apache.org/thread/zc9bkh7o4mmg5lzsfdy5v30fn634hyn0) | ||
| * [GitHub issues](https://github.com/apache/arrow/issues) | ||
|
Member
There was a problem hiding this comment. can we add github.com/apache/arrow-go/issues as well?
Member
There was a problem hiding this comment. Let's add the AI usage guidelines section here too? |
||
| * [Zulip](https://arrow-dev.zulipchat.com/) | ||
|
|
||
| ### Getting Started Before the Event | ||
|
|
||
| <!-- Optional — if there's anything participants should do ahead of | ||
| time (clone a repo, set up a dev environment, read a doc), mention | ||
| it here so they can hit the ground running. --> | ||
|
|
||
| To make the most of hackathon time, we recommend: | ||
|
|
||
| 1. Clone the repo and get the build working: [setup instructions](https://arrow.apache.org/docs/developers/index.html) | ||
|
Member
There was a problem hiding this comment. Possibly also link to |
||
| 2. Browse the issue list and pick one that interests you | ||
| 3. Introduce yourself on the dev@ list or chat channel | ||
|
|
||
| --- | ||
|
|
||
| * Back to the [Hackathon overview](hackathon.html) | ||
| * Questions? Join **#hackathon** on [apachecon.slack.com](http://s.apache.org/apachecon-slack) | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we mention that by virtue of the repo's we'll be working in, that contributors could also end up contributing to Parquet as well (since those libraries live in the Arrow repos) and that we're dealing with Arrow C++, PyArrow, AND Arrow Go as potential areas for people to contribute to?