Hey team, The time for the Hackathon is approaching. Following the guidelines in the last email by Rich [1] and based on some offline discussions with few Impala contributors I created a PR with an initial proposal [2] to get things started. I don't control when it will be merged but we can amend the pages anytime we want so there is no big time pressure.
There is an Impala talk on 12 October 2026 14:20-15:00GMT. To maximize the chances of attendance by folks interested in Impala I reserved an Hackathon slot right after (15:00–18:40). If you prefer another one let me know and I will modify the request. At the moment, very few projects have reserved slots so we have quite a bit of liberty on picking our own. Best, Stamatis [1] https://lists.apache.org/thread/c259sy0q50pzg4ol0vmttnxg8q7dbhq3 [2] https://github.com/apache/comdev-events-site/pull/36 [3] https://web.cvent.com/event/ac71ce47-2b5f-424c-abfe-5b48255315fb/summary?RefId=XSummary&session=cc8ad2f0-4e6c-40a5-a1a2-ffd2e8abe988 On 2026/05/07 08:49:46 Stamatis Zampetakis wrote: > Hey team, > > I am about a two-hour flight away from Glasgow so I could potentially > attend the conference and help with the Hackathon! > > I am rather new to Impala but have experience with Calcite so I could > help advance work in this area, such as tickets falling under: > * https://issues.apache.org/jira/browse/IMPALA-12871 > * https://issues.apache.org/jira/browse/IMPALA-14404 > > Since I am not an Impala committer it would be nice to have someone > alongside me that is more familiar with the project. If there is > interest I can try to confirm my availability for the conference. > > Best, > Stamatis > > On Wed, May 6, 2026 at 3:07 PM <[email protected]> wrote: > > > > > > > Hi Impala community, > > > > > > We're organizing a hackathon at Community Over Code Glasgow 2026 (October > > > 11–14) and Impala has sessions on the schedule. We'd love for your > > > community to participate. > > > > > > The idea is simple: dedicated time and space at the conference for > > > contributors (new and existing) to work together on real tasks — fixing > > > bugs, writing docs, tackling issues that need focused attention, or > > > onboarding new contributors. > > > > > > To participate, we'd need a few things from your project: > > > • A point of contact — someone we can coordinate with on logistics and > > > who'll be present at the event. > > > • A list of tasks — bugs, docs, features, good-first-issues, or > > > whatever your project wants to focus on. This helps people show up ready > > > to contribute rather than spending the first hour figuring out what to > > > work on. > > > • Promotion — a message to your dev@ and users@ lists letting people > > > know this is happening and encouraging them to attend. > > > > > > This is the first year we're bringing the hackathon back, so we're > > > treating it as a pilot — we want to gauge interest before committing to > > > scale. Even if only a few contributors from your project can participate, > > > that's a great start. > > > > > > If you're interested, please reply here or reach out to me directly. Even > > > a quick "yes, we're in" or "maybe, let's talk" is helpful as we figure > > > out how many projects to plan for. > > > > > > Also, please join us in the #hackathon channel on the ApacheCon Slack — > > > that's where we'll be coordinating as things come together: > > > http://s.apache.org/apachecon-slack > > > > > > Thanks, > > > Rich, on behalf of the Community Over Code planners > > > > > > — > > Rich Bowen > > [email protected] > > > > > > > > >
