RE: Community over Code Glasgow 2026 Hackathon page

Hi Paul,

I think it make sense to combine, so there is more cross pollination 
between the teams.

On the Grails front, I think our main goal is to work on the Grails 
Forge and Grails Profiles intersection, either combination, deprecation 
of one, etc.

Specifically, we would like to have a single Grails application 
generator, if possible, instead of two.  And define the CLI command 
structure for the future.

There are several existing GitHub issues, these do not cover everything.

https://github.com/apache/grails-core/issues/15301
https://github.com/apache/grails-core/issues/14081
https://github.com/apache/grails-core/issues/14944

James

---------------

Hi Groovy and Grails folks,

Over the weekend, I was going to write a draft page(s?) for the
hackathon for Community over Code Glasgow. What is the hackathon?
There is dedicated space at the conference for folks to get together
and have chats (unconference style) or work on mini projects. This
lets us deep dive with other users of our projects and maybe even
advance them along the way.

Currently the hackathon main page is here:

https://events.apache.org/events/2026/community-over-code/hackathon.html

Once projects fill in their page, it is then linked from the main page
instead of the current temporary links which mostly are now pointing
to project home pages. Eventually, the page should resemble the one
for Tomcat:

https://events.apache.org/events/2026/community-over-code/tomcat.html

Source here:

https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/tomcat.md

First question, do we want a combined Groovy/Grails page or two separate 
pages?

Also, projects are putting together lists of potential topics to hack
on during the event, e.g. Tomcat has created a list on their wiki
here:

https://cwiki.apache.org/confluence/spaces/TOMCAT/pages/421958054/Hackathon+CoC+Glasgow+2026

Other projects are updating their "good first issue" labels in their
issue tracking systems and using those as potential topics.

If we keep separate list(s), our Hackathon page(s) themselves won't
need frequent updates, but I'll probably include a few indicative
topics on that page to entice folks to dive in further.

So, let me know any topics you think would be great to cover or if you
have a suggestion on where to create a list of topics.

Thanks, Paul.