Hi Rich, Thanks for organising this. I’ll be at Community Over Code Glasgow and I’m also speaking about Fluss there, so I’d be happy to help coordinate Fluss participation in the hackathon.
My main area is the Rust client and the Python/C++/Elixir bindings, so I can help prepare tasks around client docs, examples, local setup, good first issues, and onboarding new contributors in that area. It would be great to also collect ideas from others for server/core, Flink integration, deployment, or general documentation tasks. If others are planning to attend or have ideas for suitable hackathon tasks, please add them to the thread. I’m happy to collect them into a small task list so we have something concrete to share before the event, and I can send a reminder closer to the date. -- Anton вт, 5 мая 2026 г. в 20:26, Rich Bowen <[email protected]>: > > Hi Fluss community, > > We're organizing a hackathon at Community Over Code Glasgow 2026 (October > 11–14) and Fluss 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 >
