Yes, count me in. I’m happy to help line up Spark tasks ahead of the event and share the information on users@ as it gets closer.
Thanks, Huaxin On Wed, May 6, 2026 at 11:17 AM Anand Chinnakannan <[email protected]> wrote: > Yes. > > Thanks > Anand > > On Wed, May 6, 2026, 2:16 AM Sruti S <[email protected]> wrote: > >> Yes!!! >> >> On Wed, May 6, 2026, 01:02 <[email protected]> wrote: >> >>> >>> Hi Spark community, >>> >>> We're organizing a hackathon at Community Over Code Glasgow 2026 >>> (October 11–14) and Spark 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 >>> >>>
