Capture all six Future City Hackathon 2026 challenges as OKF v0.2 concepts, with dataset and organizer concepts, indexes, and a log. Configure release-please with the simple strategy so the first release PR bumps the repository from 0.0.0 to 0.1.0.
20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
# Future City Hackathon 2026
|
|
|
|
All six partner challenges from the Future City Hackathon 2026 are captured as an [Open Knowledge Format (OKF) v0.2](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) bundle under [`knowledge/`](knowledge/index.md).
|
|
|
|
## Layout
|
|
|
|
| Path | Contents |
|
|
|---|---|
|
|
| `knowledge/index.md` | Bundle entry point and challenge overview. |
|
|
| `knowledge/challenges/` | One concept per challenge. |
|
|
| `knowledge/data/` | Dataset concepts for the supplied CSV and JSON files. |
|
|
| `knowledge/organizers/` | One concept per partner organization. |
|
|
| `knowledge/log.md` | Chronological update log. |
|
|
|
|
The original briefs, decks, and data files stay in their organizer folders at the repository root. The OKF concepts link to them instead of copying them. The 210 MB Stadt Heilbronn media export is kept locally and git-ignored because it exceeds common hosting limits.
|
|
|
|
## Releases
|
|
|
|
Commits follow [Conventional Commits](https://www.conventionalcommits.org/). [release-please](https://github.com/googleapis/release-please) is configured through `release-please-config.json`, `.release-please-manifest.json`, and `.github/workflows/release-please.yml`. On a push to `main`, the workflow opens a release PR that updates `version.txt` and `CHANGELOG.md`.
|