Hi Jarek, The idea sounds good, but won't this clash with the *other *sessions going on in parallel, which could lead to lower attendance?
I will be really happy to help with 3, if we decide to proceed. Thanks & Regards, Amogh Desai On Wed, May 6, 2026 at 10:32 AM Aritra Basu <[email protected]> wrote: > Over-all aligned with Jens' take. Onboard with the idea, and I should > probably have more time as well to help out. For 2, I'm not sure what the > scope is but I can volunteer. > > -- > Regards, > Aritra Basu > > On Wed, 6 May 2026, 12:52 am Jens Scheffler, <[email protected]> wrote: > > > Hi Jarek, > > > > to 1) sounds interesting but as I have personally never attended a CoC > > so far not sure whether the rest of panels/topics/stuff to be donw might > > be overwhelming. Still I'd think it would be useful between us as > > committers/contributors to align on certain topics. > > > > to 2-4) would raise my hand but recently my time went under the bus, so > > can not commit to contribute. > > > > Jens > > > > On 05.05.26 17:21, Jarek Potiuk wrote: > > > Hi folks, > > > > > > There's a hackathon 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 I've signed up to help coordinate > > > the outreach for a handful — ours included. > > > > > > Shape of it: a dedicated room and some conference time where Airflow > > > contributors and interested attendees can sit together and work on > > > things we actually want done — bug fixes, docs, small features, > > > whatever we put in front of them. Duration (one day, two days, …) is > > > TBD and will scale to interest, so this first year back at it is > > > effectively a pilot. Worst case the room sits empty; best case we get > > > a useful chunk of focused work plus some new contributors who stick > > > around afterwards. > > > > > > Four things I'd like to take back to the planners: > > > > > > 1. Are we in? > > > 2. Anyone want to be the point of contact between the planners and > > > our community? (Doesn't need to be a heavy lift — mostly relaying > > > messages and showing up on the day.) > > > 3. Closer to the date, can we put together a short hand-picked list > > > of bugs / good-first-issues / docs gaps / etc. for attendees to > > > pick from? The better that list is, the more we get out of the > > > day. > > > 4. Once dates and format are firmed up, will we promote it on dev@ > > > and users@? > > > > > > Reply on-list, or ping me directly. Even "yes in principle, details > > > later" is useful for sizing. > > > > > > Coordination is happening on the ApacheCon Slack #hackathon channel > > > (http://s.apache.org/apachecon-slack), with a tracking spreadsheet at > > > > > > https://docs.google.com/spreadsheets/d/1oz41kRqhUoRV3PhcHcAdQNorBiFUZHzpdguBbtKZcA4/edit?usp=sharing > > > . > > > > > > J. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
