Sounds like a great initiative. I'm interested in being involved with this; I've been curating a list of issues that want attention but nobody's working on [1], and happy to group these and wrangle other committers to add more detail etc to the relevant tickets where needed.
Also happy to be involved with coordination and promotion. Nic [1] https://github.com/apache/arrow/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Status%3A%20needs%20champion%22 On Tue, 5 May 2026 at 11:22, Jarek Potiuk <[email protected]> wrote: > Hi all, > > A hackathon is being planned for Community Over Code Glasgow > (October 11–14, 2026). Many of the projects with content at the event > are being invited to take part, and Arrow is one of them. I'm > helping coordinate the outreach. > > The basic shape: a dedicated room and a chunk of conference time > where Arrow contributors and interested attendees can sit together > and work on tasks the project wants done — bug fixes, docs, small > features, anything you'd like to put in front of motivated visitors. > Duration (one day, two days, …) is still being figured out — this > first year back at it is effectively a pilot to gauge interest, and > the worst-case scenario is that we block off the room and it sits > unused. Responses from the projects will help size it appropriately. > > Four questions I'd like to take back to the planners: > > 1. Is there interest in Arrow participating in the hackathon? > 2. Could the project designate one person as a point of contact for > coordination with the planners? > 3. Would the project be willing to put together a short list of > priorities / tasks / bugs / topics that hackathon attendees could > pick from? > 4. Once the date and format are firmed up, would Arrow be willing > to promote the hackathon on dev@ and users@ to drum up interest > and attendance? > > Coordination is happening on the ApacheCon Slack #hackathon channel > (http://s.apache.org/apachecon-slack); there's a tracking spreadsheet > at > > https://docs.google.com/spreadsheets/d/1oz41kRqhUoRV3PhcHcAdQNorBiFUZHzpdguBbtKZcA4/edit?usp=sharing > . > > Replies on-list (or directly to me) very welcome — even a "yes in > principle, details later" helps with sizing. > > Thanks, > Jarek Potiuk >
