This is an automated email from the ASF dual-hosted git repository.
rbowen pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/comdev-events-site.git
The following commit(s) were added to refs/heads/main by this push:
new 6b192fd Open signup for hackathon sessions.
6b192fd is described below
commit 6b192fd490dcf6e6040e7083d2ced39faaa2009f
Author: Rich Bowen <[email protected]>
AuthorDate: Wed Aug 12 10:07:16 2026 -0400
Open signup for hackathon sessions.
---
.../events/2026/community-over-code/hackathon.md | 195 ++++++---------------
1 file changed, 53 insertions(+), 142 deletions(-)
diff --git a/source/events/2026/community-over-code/hackathon.md
b/source/events/2026/community-over-code/hackathon.md
index aa3599f..d57dc4e 100644
--- a/source/events/2026/community-over-code/hackathon.md
+++ b/source/events/2026/community-over-code/hackathon.md
@@ -1,110 +1,45 @@
---
-title: Hackathon at Community over Code Glasgow 2026
----
-<img src="/images/apache-oak-leaf.svg" alt="Apache" style="height:1.4em;
vertical-align:middle;"> **[Community over Code
2026](https://communityovercode.org) — Glasgow, UK, October 11–14**
-<style>
- .hackathon-banner{
- display: flex;
- align-items: center;
- justify-content: center;
- gap: 2rem;
- padding: 1.5rem;
- margin: 1rem 0 2rem;
- background:
- radial-gradient(circle at 85% 20%, rgba(70, 90, 200, 0.35), transparent
32%),
- radial-gradient(circle at 15% 75%, rgba(180, 45, 145, 0.24), transparent
30%),
- linear-gradient(135deg, #02091d 0%, #07132d 48%, #111944 75%, #210f3f
100%);
- border-radius: 16px;
- color: #ffffff;
- overflow: hidden;
- }
- .hackathon-banner-text {
- flex: 1;
- }
- .hackathon-banner-text h1 {
- margin: 0.8rem 0 0.5rem;
- color: #ffffff;
- }
- .hackathon-banner-text a {
- color: #ff9852;
- }
- .hackathon-banner-text p {
- margin: 0.4rem 0 0;
- color: #e9eaf2;
- }
- .hackathon-banner-poster {
- width: 100%;
- max-width: 320px;
- height: auto;
- border: 4px solid #ffffff;
- border-radius: 10px;
- box-shadow: 0 14px 35px rgba(0, 0, 0, 0.45);
- }
- @media (max-width: 760px) {
- .hackathon-banner {
- flex-direction: column;
- align-items: flex-start;
- }
- .hackathon-banner-poster {
- max-width: 100%;
- }
- }
-</style>
-
-<div class="hackathon-banner">
-
- <div class="hackathon-banner-text">
- <img
- src="/images/apache-oak-leaf.svg"
- alt="Apache"
- style="height:1.4em; vertical-align:middle;"
- >
- <strong>
- <a href="https://communityovercode.org";>
- Community over Code 2026
- </a>
- — Glasgow, UK, October 11–14
- </strong>
- <h1>Hackathon</h1>
-
- </div>
- <a href="/images/hackathon-poster.png">
- <img
- class="hackathon-banner-poster"
- src="/images/hackathon-poster.png"
- alt="Community over Code Glasgow 2026 Hackathon poster"></a>
-</div>
+## title: Hackathon at Community over Code Glasgow 2026
+
+
+
+
+
+**[Community over Code 2026](https://communityovercode.org)**** — Glasgow, UK,
October 11–14**
+
+
+
+
+
+**[Community over Code 2026 ](https://communityovercode.org)********— Glasgow,
UK, October 11–14**
+# Hackathon
+
+
+
+
## Hackathon
-We're bringing back the hackathon! Community over Code Glasgow will
-include dedicated time and space for contributors — new and experienced
-— to sit together and work on real tasks: fixing bugs, writing docs,
-tackling issues that need focused attention, and onboarding new
-contributors.
+We're bringing back the hackathon! Community over Code Glasgow will include
dedicated time and space for contributors — new and experienced — to sit
together and work on real tasks: fixing bugs, writing docs, tackling issues
that need focused attention, and onboarding new contributors.
### How it works
Each participating project provides:
-* A **point of contact** — someone present at the event to coordinate
-* A **task list** — bugs, docs, features, good-first-issues, or
- whatever the project wants to focus on
-* **Promotion** — letting their community know this is happening
+- A **point of contact** — someone present at the event to coordinate
+- A **task list** — bugs, docs, features, good-first-issues, or whatever the
project wants to focus on
+- **Promotion** — letting their community know this is happening
-During the event, a dedicated room will be available for contributors
-to gather, collaborate, and get things done.
+During the event, a dedicated room will be available for contributors to
gather, collaborate, and get things done.
### Participating Projects
-The following Apache projects have confirmed participation. Follow the
-thread links to see the conversation and find out how to get involved
-with each project's hackathon effort.
+The following Apache projects have confirmed participation. Follow the thread
links to see the conversation and find out how to get involved with each
project's hackathon effort.
| Project | Discussion |
-|---------|-----------|
+| --- | --- |
| [Airflow](https://airflow.apache.org/) | [dev@
thread](https://lists.apache.org/thread/c0fnphvb1bs5wbd454x7qclzcqj4wp1o) |
| [Arrow](https://arrow.apache.org/) | [dev@
thread](https://lists.apache.org/thread/j63qwqrbosthf1ml3q7yxho89xhx5hoj) |
| [Camel](https://camel.apache.org/) | [dev@
thread](https://lists.apache.org/thread/5ws6zdfofxd6typhz7fg1np8j7fn77ho) |
@@ -124,86 +59,62 @@ with each project's hackathon effort.
| [Ozone](https://ozone.apache.org/) *(tentative)* | [dev@
thread](https://lists.apache.org/thread/wmj56tsd6m0w9fk7oz2rsfqjzfg765vf) |
| [Pekko](https://pekko.apache.org/) | [dev@
thread](https://lists.apache.org/thread/pkgkjq3748blo1g9znvrh556s488sox2) |
| [SIS](https://sis.apache.org/) | [dev@
thread](https://lists.apache.org/thread/x5pyd9cwjhyc8lpgsgfnvpy8g72l91c9) |
-| [Solr](solr.html/) | [dev@
thread](https://lists.apache.org/thread/f8bjyy06c0v2lddol6vvv5n8tzd3y9vl) |
+| Solr | [dev@
thread](https://lists.apache.org/thread/f8bjyy06c0v2lddol6vvv5n8tzd3y9vl) |
| [Spark](https://spark.apache.org/) | [dev@
thread](https://lists.apache.org/thread/711z5rcx7pb2wrwm0t41l6ffx21jxyr9) |
| [StreamPipes](https://streampipes.apache.org/) | [dev@
thread](https://lists.apache.org/thread/yko4ypzx2r3dw1glkwpylc3kqgkhoqhc) |
| [Superset](https://superset.apache.org/) | [dev@
thread](https://lists.apache.org/thread/f2bs0tfbmfmhl3r3zgf69p27mkfq7n68) |
| [Tomcat](tomcat.html) | [dev@
thread](https://lists.apache.org/thread/ox1q1wvtzcf6ko3xv2z5m1nz5dnjv6h2) |
| [Wayang](https://wayang.apache.org/) | [dev@
thread](https://lists.apache.org/thread/nstct4k069v748rq622tt5vx2c66objf) |
-*Eventually each project will have a dedicated page with hackathon
-task ideas and contributor guidance.*
-
-<!--
+*Eventually each project will have a dedicated page with hackathon task ideas
and contributor guidance.*
### Hackathon Room Schedule
-The hackathon room is available throughout the conference (Sunday
-through Wednesday) in the Wee Dram Room.
-Up to **5 projects** can use the room during each half-day slot.
+The hackathon room is available throughout the conference (Sunday through
Wednesday) in the Wee Dram Room. Up to **5 projects** can use the room during
each half-day slot.
-**Please claim only one slot initially**, so every project gets a
-chance. Once all projects have signed up, unclaimed slots will open
-for seconds.
+**Please claim only one slot initially**, so every project gets a chance. Once
all projects have signed up, unclaimed slots will open for seconds.
-To claim a slot, submit a PR adding your project name to the table
-below. Link to your [project hackathon page](hackathon.html) if you
-have one.
+**To sign up, open a PR** against the [comdev-events-site
repository](https://github.com/apache/comdev-events-site) adding your project
name to an open slot in the table below. Link to your [project hackathon
page](hackathon.html) if you have one.
-#### Sunday, 11 October
+Monday, 12 October
| Slot | Project 1 | Project 2 | Project 3 | Project 4 | Project 5 |
-|------|-----------|-----------|-----------|-----------|-----------|
-| Morning (11:20–15:00) | | | | | |
-| Afternoon (15:00–18:40) | | | | | |
+| --- | --- | --- | --- | --- | --- |
+| Morning (11:20–15:00) | | | | | |
+| Afternoon (15:00–18:40) | *Security* | *Security* | *Security* | *Security*
| *Security* |
-#### Monday, 12 October
+Tuesday, 13 October
| Slot | Project 1 | Project 2 | Project 3 | Project 4 | Project 5 |
-|------|-----------|-----------|-----------|-----------|-----------|
-| Morning (11:20–15:00) | | | | | |
-| Afternoon (15:00–18:40) | [Impala](impala.html) | | | | |
+| --- | --- | --- | --- | --- | --- |
+| Morning (11:20–15:00) | | | | | |
+| Afternoon (15:00–18:40) | | | | | |
-#### Tuesday, 13 October
+Wednesday, 14 October
| Slot | Project 1 | Project 2 | Project 3 | Project 4 | Project 5 |
-|------|-----------|-----------|-----------|-----------|-----------|
-| Morning (11:20–15:00) | | | | | |
-| Afternoon (15:00–18:40) | | | | | |
-
-#### Wednesday, 14 October
-
-| Slot | Project 1 | Project 2 | Project 3 | Project 4 | Project 5 |
-|------|-----------|-----------|-----------|-----------|-----------|
-| Morning (11:20–15:00) | | | | | |
-| Afternoon (15:00–18:40) | | | | | |
-
--->
+| --- | --- | --- | --- | --- | --- |
+| Morning (11:20–15:00) | | | | | |
+| Afternoon (15:00–18:40) | *Security* | *Security* | *Security* | *Security*
| *Security* |
### Want your project to participate?
-If your project has content at Community over Code Glasgow and you'd
-like to take part in the hackathon, reach out:
+If your project has content at Community over Code Glasgow and you'd like to
take part in the hackathon, reach out:
-* Email [[email protected]](mailto:[email protected])
-* Join **#hackathon** on
[apachecon.slack.com](http://s.apache.org/apachecon-slack)
+- Email [[email protected]](mailto:[email protected])
+- Join **#hackathon** on
[apachecon.slack.com](http://s.apache.org/apachecon-slack)
-We need a point of contact, a list of tasks for contributors to work on,
-and a message to your dev@ and users@ lists letting people know it's
-happening.
+We need a point of contact, a list of tasks for contributors to work on, and a
message to your dev@ and users@ lists letting people know it's happening.
### Coordination
-General hackathon coordination happens on the
-[[email protected]](mailto:[email protected]) mailing list and
-in the **#hackathon** channel on
-[apachecon.slack.com](http://s.apache.org/apachecon-slack).
+General hackathon coordination happens on the
[[email protected]](mailto:[email protected]) mailing list and in the
**#hackathon** channel on
[apachecon.slack.com](http://s.apache.org/apachecon-slack).
---
-* Looking for other ways to help? See [more volunteer
opportunities](volunteer-outreach-calendar.html).
-* Help spread the word: [Social Media Promotion
page](glasgow-social-media.html).
-* See the [Hackathon Outreach Calendar](hackathon-outreach-calendar.html) for
publicity tasks that need an owner.
-* Learn more about [what's involved in hackathon
coordination](/volunteer/hackathon.html).
-* Projects can update this page by submitting a PR to the
- [comdev-events-site
repository](https://github.com/apache/comdev-events-site).
+- Looking for other ways to help? See [more volunteer
opportunities](volunteer-outreach-calendar.html).
+- Help spread the word: [Social Media Promotion
page](glasgow-social-media.html).
+- See the [Hackathon Outreach Calendar](hackathon-outreach-calendar.html) for
publicity tasks that need an owner.
+- Learn more about [what's involved in hackathon
coordination](/volunteer/hackathon.html).
+- Projects can update this page by submitting a PR to the [comdev-events-site
repository](https://github.com/apache/comdev-events-site).
+
