Hi, I'm definitely interested too. Will this allow remote participation as well?
Fatima On Thu, May 7, 2026 at 7:56 PM Mark Thomas <[email protected]> wrote: > Hi, > > The barrier can seem a little high at times. That is largely a > consequence of us reducing the backlog of open bugs to zero. > > I'm sure we'll be able to find some tasks that will be suitable for the > hackathon - watch this space. > > Mark > > > On 07/05/2026 03:51, 박종하 wrote: > > I'm interested as well. > > > > So far, I've only worked on beginner-friendly issues, and I haven't been > > able to contribute actively to the community because the barrier to entry > > felt quite high at times. However, I'd really like to use this > opportunity > > to get more involved, participate more seriously, and become someone who > > can contribute consistently to the Tomcat community. > > > > Jongha > > > > > > 2026년 5월 6일 (수) 오후 9:00, Mark Thomas <[email protected]>님이 작성: > > > >> Dropping Rich for now while we discuss internally. > >> > >> I'm +1 on supporting the hackathon. I am happy to be the point person > >> but equally happy if someone else wants to do it. > >> > >> I have various things on my TODO list at least some of which could be > >> suitable for someone new to Tomcat. Shall we start a list of ideas on a > >> Wiki page? > >> > >> Promoting on the users and dev list is easy. > >> > >> Is anyone else interested in a hackathon? > >> > >> Mark > >> > >> > >> On 06/05/2026 12:05, Rich Bowen wrote: > >>> It will be alongside the event. What's not clear at this point is if > it's > >>> one or two days or the whole time. Depends on the response that this > >>> message receives. Because of course you wouldn't want it to compete > with > >>> your track/content, but I don't know yet how much time/space we can get > >> for > >>> it. > >>> > >>> Rich > >>> > >>> On Wed, May 6, 2026, 03:06 Mark Thomas <[email protected]> wrote: > >>> > >>>> Rich, > >>>> > >>>> Is this going to run alongside the conference or is it planned as a > >>>> before/after event? > >>>> > >>>> Mark > >>>> > >>>> > >>>> On 05/05/2026 20:32, [email protected] wrote: > >>>>> > >>>>>> Hi Tomcat community, > >>>>>> > >>>>>> We're organizing a hackathon at Community Over Code Glasgow 2026 > >>>> (October 11–14) and Tomcat 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 > >>>>> > >>>> > >>>> > >>> > >> > >> > >> --------------------------------------------------------------------- > >> 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] > >
