Hi, I am also attending Community Over Code Glasgow 2026. Happy to help.
Regards, Raúl El jue, 7 may 2026 a las 14:30, Antoine Pitrou (<[email protected]>) escribió: > > > Hi, > > I'm interested in helping, withing the constraints of my own planning (I > participate in two talks). > > Regards > > Antoine. > > > Le 05/05/2026 à 17:21, Jarek Potiuk a écrit : > > 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 >
