We have a table! Unfortunantly, we only can have a table on the morning of Monday, as Search Track is Tuesday and Wednesday.
I tried for a table in the afternoon, or even a afternoon + morning, but apparently "Security" has taken up ALL five of the tables on Monday afternoon. SLightly annoyed at this but apparently "it is what it is". https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/hackathon.md So, we can do the hackathon thing Monday morning, and I'll have a powerstrip and extension cord with me, and then in the afternoon we find a space to continue. Oh, and if the Security hackathon isn't full using all five tables, I am going to give them the stink eye for booting us! On 2026/08/06 13:41:13 Eric Pugh wrote: > Thanks for spotting that…. I’ve followed up on the slack channel, and will > ask for Monday, since Search Track is Tuesday and Wednesday. > > Although if we have enough interest… I’d be down for hacking on both Sunday > afternoon and Monday. > > > On Aug 4, 2026, at 5:44 AM, Jan Høydahl <[email protected]> wrote: > > > > Thanks for organizing Eric, > > > > I just bought my conference ticket yesterday, YEY. > > > > There is an HTML comment in the hackaton.md > > <https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/hackathon.md?plain=1#L139-L179 > > > > <https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/hackathon.md?plain=1#L139-L179>> > > file that says the room is available all days, but projects will book > > half-day "slots" of their choosing. > > > > Jan > > > > > 4. aug. 2026 kl. 02:02 skrev Eric Pugh <[email protected]>: > > > > > > I opened https://github.com/apache/comdev-events-site/pull/33 > > > <https://github.com/apache/comdev-events-site/pull/33> to get us > > > started…. I’d love to hear what others want to work on, and of course, > > > who else will be there. > > > > > > One thing I am fuzzy on: is the hackathon all four days? 1 day? > > > > > >> On Aug 3, 2026, at 3:53 PM, Eric Pugh <[email protected]> wrote: > > >> > > >> I'm planning on being at this: > > >> https://events.apache.org/events/2026/community-over-code/hackathon.html > > >> <https://events.apache.org/events/2026/community-over-code/hackathon.html> > > >> > > >> <https://events.apache.org/events/2026/community-over-code/hackathon.html > > >> > > >> <https://events.apache.org/events/2026/community-over-code/hackathon.html>>, > > >> and we apparent;ly need to fill in > > >> > > >> https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/sampleproject.md > > >> > > >> <https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/sampleproject.md> > > >> > > >> <https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/sampleproject.md > > >> > > >> <https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/sampleproject.md>> > > >> > > >> So, any thoughts on what folks are interested in? I've got my own list, > > >> but maybe more interested in pairing with what others want to do since > > >> we have this opportunity to work togetehr! > > >> > > >> I can start a PR to get us moving... > > >> > > >> Eric > > >> > > >> On 2026/05/05 20:12:33 Anshum Gupta wrote: > > >>> Hi Rich, > > >>> > > >>> Yes, we're in! > > >>> > > >>> > > >>> On Tue, May 5, 2026 at 12:33 PM <[email protected]> wrote: > > >>> > > >>>> > > >>>>> Hi Solr community, > > >>>>> > > >>>>> We're organizing a hackathon at Community Over Code Glasgow 2026 > > >>>> (October 11–14) and Solr 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 > > >>>> <http://s.apache.org/apachecon-slack> > > >>>> <http://s.apache.org/apachecon-slack > > >>>> <http://s.apache.org/apachecon-slack>> > > >>>>> > > >>>>> Thanks, > > >>>>> Rich, on behalf of the Community Over Code planners > > >>>> > > >>> > > >>> > > >>> -- > > >>> Anshum Gupta > > >>> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > > > > > Disclaimer > > > > > > The information contained in this communication from the sender is > > > confidential. It is intended solely for use by the recipient and others > > > authorized to receive it. If you are not the recipient, you are hereby > > > notified that any disclosure, copying, distribution or taking action in > > > relation of the contents of this information is strictly prohibited and > > > may be unlawful. > > > > > > This email has been scanned for viruses and malware, and may have been > > > automatically archived by Mimecast, a leader in email security and cyber > > > resilience. Mimecast integrates email defenses with brand protection, > > > security awareness training, web security, compliance and other essential > > > capabilities. Mimecast helps protect large and small organizations from > > > malicious activity, human error and technology failure; and to lead the > > > movement toward building a more resilient world. To find out more, visit > > > our website. > > > > Disclaimer > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by Mimecast, a leader in email security and cyber > resilience. Mimecast integrates email defenses with brand protection, > security awareness training, web security, compliance and other essential > capabilities. Mimecast helps protect large and small organizations from > malicious activity, human error and technology failure; and to lead the > movement toward building a more resilient world. To find out more, visit our > website. > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
