Hi Rich, Thanks for reaching out to our Ozone project.
Looks like there are three Ozone sessions[1] ! Roland, Zita, Rakesh, Rishabh will be there. I'm not sure if there will be more Ozone contributors there. They can decide if any of them has the bandwidth to host a hackathon session or not. cc @Uma gangumalla <[email protected]> Bests, Sammi [1] https://communityovercode.org/schedule/ On Wed, 6 May 2026 at 03:32, <[email protected]> wrote: > > > Hi Ozone community, > > > > We're organizing a hackathon at Community Over Code Glasgow 2026 > (October 11–14) and Ozone 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 >
