Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 29a0fde98c |
418 changed files with 359 additions and 14485 deletions
|
|
@ -1,23 +0,0 @@
|
|||
on:
|
||||
pull_request:
|
||||
types:
|
||||
- closed
|
||||
|
||||
jobs:
|
||||
cleanup-staging:
|
||||
runs-on: docker
|
||||
container:
|
||||
image: code.forgejo.org/oci/node:22-bookworm
|
||||
steps:
|
||||
- name: Pipeline info PR
|
||||
run: |
|
||||
echo "Run triggered by ${{ github.event_name }} (${{ github.event.action }}) on ref ${{ github.ref_name }}"
|
||||
|
||||
- name: Staging Deployment - Prepare keys
|
||||
run: |
|
||||
echo "${{ secrets.SSH_DEPLOY_KEY }}" > deploykey.priv
|
||||
chmod 400 deploykey.priv
|
||||
echo "${{ secrets.SSH_KNOWN_HOSTS_FILE }}" > ./known_hosts
|
||||
- name: Staging Deployment - Remove PR from staging
|
||||
run: |
|
||||
ssh -i deploykey.priv -o 'UserKnownHostsFile ./known_hosts' ccchh-website-deploy@public-web-static.hosts.hamburg.ccc.de -t "rm -r /var/www/staging.hamburg.ccc.de/pr${{ github.event.pull_request.number }}/"
|
||||
|
|
@ -1,81 +0,0 @@
|
|||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
pull_request:
|
||||
schedule:
|
||||
- cron: "0,30 * * * *"
|
||||
|
||||
env:
|
||||
TZ: Europe/Berlin
|
||||
|
||||
jobs:
|
||||
build:
|
||||
runs-on: docker
|
||||
container:
|
||||
image: hugomods/hugo:exts-0.148.1
|
||||
steps:
|
||||
- name: Pipeline info
|
||||
run: |
|
||||
echo "Run triggered by ${{ github.event_name }} (${{ github.event.action }}) on ref ${{ github.ref_name }}"
|
||||
|
||||
- name: Install packages
|
||||
run: |
|
||||
apk update
|
||||
# For CI actions.
|
||||
apk add nodejs-current
|
||||
# For website build.
|
||||
apk add tzdata coreutils curl jq git
|
||||
# For uploading.
|
||||
apk add rsync openssh
|
||||
|
||||
- uses: actions/checkout@v7
|
||||
with:
|
||||
fetch-depth: 0 # pull full history for page lastmod by git commit date
|
||||
|
||||
- name: Build website - prod
|
||||
run: |
|
||||
./fetch-calendar.sh
|
||||
hugo
|
||||
|
||||
- name: Build website - staging
|
||||
if: github.ref_name != 'main'
|
||||
run: |
|
||||
sed -i "s#baseURL = 'https://hamburg.ccc.de/'#baseURL = 'https://staging.hamburg.ccc.de/pr${{ github.event.pull_request.number }}/'#" hugo.toml
|
||||
sed -i "s#index = true#index = false#" hugo.toml
|
||||
sed -i "s#follow = true#follow = false#" hugo.toml
|
||||
./fetch-calendar.sh
|
||||
hugo --buildFuture
|
||||
|
||||
- name: Deploy - Prepare keys
|
||||
if: github.event_name == 'push' || github.event_name == 'pull_request' || github.event_name == 'schedule'
|
||||
run: |
|
||||
echo "${{ secrets.SSH_DEPLOY_KEY }}" > deploykey.priv
|
||||
chmod 400 deploykey.priv
|
||||
echo "${{ vars.SSH_KNOWN_HOSTS }}" > ./known_hosts
|
||||
|
||||
- name: Deploy - Upload PR to staging
|
||||
if: github.event_name == 'pull_request'
|
||||
run: |
|
||||
echo "Deploying to staging.hamburg.ccc.de/pr${{ github.event.pull_request.number }}"
|
||||
rsync -v -r --delete -e "ssh -i deploykey.priv -o 'UserKnownHostsFile ./known_hosts'" public/ ccchh-website-deploy@public-web-static.hosts.hamburg.ccc.de:/var/www/staging.hamburg.ccc.de/pr${{ github.event.pull_request.number }}/
|
||||
- name: Deploy - Add comment to PR with staging URL
|
||||
if: github.event_name == 'pull_request' && github.event.action == 'opened'
|
||||
run: |
|
||||
curl \
|
||||
-X POST \
|
||||
${{ github.event.pull_request.base.repo.url }}/issues/${{ github.event.pull_request.number }}/comments \
|
||||
-H "Content-Type: application/json" \
|
||||
-H "Authorization: token $GITHUB_TOKEN" \
|
||||
--data '{ "body": "You can view your changes at https://staging.hamburg.ccc.de/pr${{ github.event.pull_request.number }}/" }'
|
||||
|
||||
- name: Deploy - Upload to prod
|
||||
if: (github.event_name == 'push' || github.event_name == 'schedule') && github.ref_name == 'main'
|
||||
run: |
|
||||
rsync -v -r --delete -e "ssh -i deploykey.priv -o 'UserKnownHostsFile ./known_hosts'" public/ ccchh-website-deploy@public-web-static.hosts.hamburg.ccc.de:/var/www/hamburg.ccc.de/
|
||||
|
||||
- uses: actions/upload-artifact@v3
|
||||
if: github.event_name == 'pull_request'
|
||||
with:
|
||||
name: website-build
|
||||
path: public/
|
||||
34
.gitlab-ci.yml
Normal file
34
.gitlab-ci.yml
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
stages:
|
||||
- build
|
||||
- deploy
|
||||
|
||||
build-website:
|
||||
stage: build
|
||||
image: alpine
|
||||
before_script:
|
||||
- apk update
|
||||
- apk add tzdata hugo coreutils curl jq git
|
||||
script:
|
||||
- ./fetch-calendar.sh
|
||||
- sed -i "s#baseURL = 'https://hamburg.ccc.de/'#baseURL = 'https://next.hamburg.ccc.de/'#" hugo.toml
|
||||
- hugo
|
||||
artifacts:
|
||||
expose_as: "website build"
|
||||
name: "website-build-$CI_COMMIT_REF_NAME-$CI_COMMIT_SHORT_SHA"
|
||||
paths:
|
||||
- public/
|
||||
expire_in: 1 month
|
||||
|
||||
deploy-website:
|
||||
stage: deploy
|
||||
image: alpine
|
||||
before_script:
|
||||
- apk update
|
||||
- apk add rsync openssh
|
||||
script:
|
||||
- chmod 400 $NEXT_SSH_DEPLOY_KEY
|
||||
- rsync -r --delete -e "ssh -i $NEXT_SSH_DEPLOY_KEY -o 'UserKnownHostsFile $SSH_KNOWN_HOSTS_FILE'" public/ ccchh-website-deploy@public-web-static-intern.hamburg.ccc.de:/var/www/next.hamburg.ccc.de/
|
||||
rules:
|
||||
- if: $CI_COMMIT_BRANCH == "main"
|
||||
when: on_success
|
||||
- when: never
|
||||
7
.vscode/settings.json
vendored
Normal file
7
.vscode/settings.json
vendored
Normal file
|
|
@ -0,0 +1,7 @@
|
|||
{
|
||||
"css.format.spaceAroundSelectorSeparator": true,
|
||||
"css.format.maxPreserveNewLines": 3,
|
||||
"scss.format.maxPreserveNewLines": 3,
|
||||
"scss.format.spaceAroundSelectorSeparator": true,
|
||||
"files.insertFinalNewline": true
|
||||
}
|
||||
2
LICENSE
2
LICENSE
|
|
@ -1,6 +1,6 @@
|
|||
BSD 3-Clause License
|
||||
|
||||
Copyright (c) 2023, CCC Hansestadt Hamburg e.V.
|
||||
Copyright (c) 2023, Chaos Computer Club Hansestadt Hamburg e.V.
|
||||
|
||||
Redistribution and use in source and binary forms, with or without
|
||||
modification, are permitted provided that the following conditions are met:
|
||||
|
|
|
|||
113
README.md
113
README.md
|
|
@ -11,8 +11,8 @@ All other information like details on groups, projects and recurring events shou
|
|||
- start page (onepager)
|
||||
* who we are
|
||||
* announcements aka current blog entry (if in the future)
|
||||
* event calendar
|
||||
* visit us -> open chaos + link to wiki for all recurring events
|
||||
* event calendar
|
||||
* groups, e.g. CTF team, CMS, freifunk, etc.
|
||||
* directions (map)
|
||||
- blog, split into:
|
||||
|
|
@ -24,123 +24,48 @@ All other information like details on groups, projects and recurring events shou
|
|||
|
||||
### Build and Deploy
|
||||
|
||||
To populate the calendar data, please run `./fetch-calendar.sh` before running hugo.
|
||||
To populate the calendar data, please run `fetch-calendar.sh` before running hugo.
|
||||
|
||||
Running the hugo command without and parameters will re-generate the site in the `public` directory.
|
||||
To deploy the website, just copy the whole folder to a directory which is servered by the webserver of your preference.
|
||||
|
||||
Please note that the website should be re-deployed at least daily to update the "announcement" section on the front page even if there were no changed to the content.
|
||||
See [Automated Deployment](#automated-deployment) for the way the deployment is set up on git.hamburg.ccc.de
|
||||
Please note, that the website should be re-deployed at least daily to update the "announcement" section on the front page even if there were no changed to the content.
|
||||
|
||||
### Previewing Changes Locally
|
||||
### Add Pages
|
||||
|
||||
To run a local version, just install HUGO by following the [instructions](https://gohugo.io/installation/) for your operating system.
|
||||
To build the website and run a development webserver, execute:
|
||||
```shell
|
||||
hugo server --buildFuture --buildDrafts
|
||||
hugo server
|
||||
```
|
||||
|
||||
Note: the flags `--buildFuture --buildDrafts` makes Hugo process all content, even if the `publishDate` is still in the future, or the content is marked as `draft: true` in the frontmatter.
|
||||
You usually want these flags, especially if you are preparing content that should only be shown after a certain date.
|
||||
|
||||
Also see [Submitting Your Content](#submitting-your-content) below.
|
||||
|
||||
### Adding Content
|
||||
|
||||
There are two basic types of posts: Events and blog posts.
|
||||
Hugo and the template set distinguish between these two types based on frontmatter information.
|
||||
When manually creating content, you need to take extra care to use the correct frontmatter data.
|
||||
See the link to the Hugo archetypes below for details.
|
||||
|
||||
**If at all possible, use `hugo new content` with the appropriate parameters to create the new content file correctly.**
|
||||
|
||||
You should always set these frontmatter fields:
|
||||
* `categories`: must be either `article` or `event`; see below.
|
||||
* `date`: the date displayed for this content.
|
||||
For events, that should be when the event takes place; for blog posts, it is when the post was written.
|
||||
* `publishDate`: the date and time the content should be published.
|
||||
Note that if you do not specify a `publishDate`, the value of `date` will be used.
|
||||
* `title`: the headline of your content.
|
||||
|
||||
#### Add a Blog Entry
|
||||
|
||||
Blog posts (the archetype is called `article`) should be used for information that will be relevant for a longer period, for example explanations about technical, political or cultural topics.
|
||||
Articles will be shown for a few days on the home page.
|
||||
The [blog page](https://hamburg.ccc.de/blog/) shows all posts, newest first.
|
||||
In addition, the `tags:` can be used to find blog posts about certain topics.
|
||||
|
||||
To create a new general blog post, run a command like this:
|
||||
To also build posts in the future or in draft state, run this instead:
|
||||
```shell
|
||||
hugo new content --kind article blog/yyyy/yyyy-mm-dd-your-article-title/index.md
|
||||
hugo server -D
|
||||
```
|
||||
|
||||
If you want to create a blog post from scratch, or convert an event into a blog post, see the frontmatter data in [themes/ccchh/archetypes/article.md](themes/ccchh/archetypes/article.md).
|
||||
In particular, you need to set `categories: article`.
|
||||
You do not need to specify an explicit `publishDate`, as the value of `date` will be used as a fallback.
|
||||
|
||||
#### Add an Event Announcement
|
||||
|
||||
Events will be shown on the home page from the frontmatter `publishDate:` until the `date:` (plus a few hours grace period).
|
||||
Use them for information that is relevant for a specific event, like a talk or a meeting.
|
||||
|
||||
This is not limited to events organized by the CCCHH, but can also be a hint to other events which we think are related to our activities.
|
||||
There are two basic types of posts: Events and articles.
|
||||
Events will be shown on the home page from their publishing date until they have happened.
|
||||
|
||||
To create a new event blog post, run a command like this:
|
||||
```shell
|
||||
hugo new content --kind event blog/yyyy/yyyy-mm-dd-your-event-title/index.md
|
||||
hugo new content --kind event blog/your-event-title.md
|
||||
```
|
||||
|
||||
If you want to create an event from scratch, or convert a blog post into an event, see the frontmatter data in [themes/ccchh/archetypes/event.md](themes/ccchh/archetypes/event.md).
|
||||
In particular, you need to set `categories: event`, `date:` for the date of the event, `publishDate:` for the date the content should be published, and `location:` to whereever your event takes place.
|
||||
#### Add a Blog Entry
|
||||
|
||||
#### Additional Notes on Events and Articles
|
||||
As mentioned before, you can also create blog posts for things which aren't events.
|
||||
They will only be shown in the "blog" section and posted to the RSS feeds.
|
||||
|
||||
To create a new general blog post, run a command like this:
|
||||
```shell
|
||||
hugo new content --kind article blog/your-article-title.md
|
||||
```
|
||||
|
||||
By default the first 70 words are shown as a summary on list pages.
|
||||
Please use `<!--more-->` (white space matters) to manually separate the summary from other post content.
|
||||
|
||||
Please prefix your folder name with a date to make browsing the content in the source code easier.
|
||||
The date in the URL will be taken from the `date` field in the front matter.
|
||||
|
||||
Blog posts from before 2024-01-22 were imported from the previous website and have additional front matter data which is not usually needed (e.g. the lastmod value).
|
||||
|
||||
#### Submitting Your Content
|
||||
|
||||
After creating the new content, or making changes to existing content please commit your changes with a meaningful commit message to a fresh branch.
|
||||
Name the branch in a way that makes it easy to understand what the changes are, for example, the title of your new blog post.
|
||||
|
||||
Push the branch to git.hamburg.ccc.de, and create a new pull request.
|
||||
Invite reviewers, or post the link to the PR to the [#infrastruktur:hamburg.ccc.de](https://matrix.to/#/#infrastruktur:hamburg.ccc.de) Matrix channel.
|
||||
|
||||
The changes you have made will be deployed to the staging website automatically (this might take a minute or two).
|
||||
See the comments in the PR for the link to your preview.
|
||||
You and the reviewers can use the link to preview the changes.
|
||||
|
||||
If you have set a `publishDate` to a date and time in the future, the preview will show the content as it would appear then.
|
||||
|
||||
Once at least one reviewer approves the PR, it will be merged and pushed to production.
|
||||
This usually takes less than five minutes.
|
||||
|
||||
### Automated Deployment
|
||||
|
||||
The website is automatically rebuilt and redeployed every 20 minutes. At each build and deploy:
|
||||
* The event calendar is fetched.
|
||||
* Hugo renders all pages.
|
||||
* All changed files are deployed to the production web server.
|
||||
|
||||
See [.forgejo/workflows/deploy.yaml](.forgejo/workflows/deploy.yaml) for all the details.
|
||||
|
||||
Additionally, for each pull request, a version of the website is deployed to the staging website under a unique URL.
|
||||
The pull request will be updated with the URL, so you and the reviewers can look at the changes as they will appear after merging.
|
||||
After the PR is closed, the staging URL will be removed.
|
||||
|
||||
#### Populate the Event Calendar
|
||||
|
||||
The event calendar table is filled from the Nextcloud iCal feed.
|
||||
To add a link on the title text, just add some link to the event's description field.
|
||||
The first link (something starting with `https://` or `http://`) from anywhere in the text will be taken.
|
||||
|
||||
(iCal has a link attribute, but that is not supported by the Nextcloud web UI. So we use the description instead.)
|
||||
|
||||
Please use `<!--more-->` to manually separate the summary from other post content.
|
||||
|
||||
### Icons
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
- {{< fa envelope >}} Mailingsliste Hamburg: [talk](https://lists.hamburg.ccc.de/postorius/lists/talk.lists.hamburg.ccc.de/)
|
||||
- {{< fa envelope >}} Mailingsliste Hamburg: [talk](https://www.hamburg.ccc.de/mailman/listinfo/talk)
|
||||
- {{< fa envelope >}} E-Mail an den CCC Hamburg: <mail@hamburg.ccc.de>
|
||||
- {{< fa envelope >}} Verwaltung des CCC Hamburg: <buero@hamburg.ccc.de>
|
||||
- {{< fa brands mastodon >}} Fediverse: <a rel="me" href="https://chaos.social/@ccchh">@ccchh@chaos.social</a>
|
||||
- {{< fa comments >}} Matrix CCCHH Chat: [#ccchh:hamburg.ccc.de](https://matrix.to/#/#ccchh:hamburg.ccc.de)
|
||||
- {{< fa comments >}} Matrix Space: [#ccchh-space:hamburg.ccc.de](https://matrix.to/#/#ccchh-space:hamburg.ccc.de)
|
||||
- {{< fa brands mastodon >}} Fediverse: [@ccchh@chaos.social](https://chaos.social/@ccchh)
|
||||
- {{< fa comments >}} Matrix Space: [#ccchh-space:hamburg.ccc.de](https://matrix.to/#/#ccchh-space:hamburg.ccc.de)
|
||||
- {{< fa comments >}} Internet Relay Chat: [hackint.eu](https://webirc.hackint.org/#irc://irc.hackint.org/#ccchh?nick=) [#ccchh](ircs://hackint.eu/ccchh)
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 338 KiB |
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
title: "38c3 Voucher"
|
||||
---
|
||||
|
||||
# Gugst du hier für 39C3 / 2025
|
||||
|
||||
Die Erklärungen für [Voucher für Hamburg für den 39C3 in 2025](../39c3-voucher). Diese Seite war mal für den 38C3.
|
||||
|
|
@ -1,23 +0,0 @@
|
|||
---
|
||||
title: "39C3 Voucher"
|
||||
---
|
||||
|
||||
# Voucher für Hamburg für den 39C3 in 2025
|
||||
|
||||
Die Voucher-Phase ist vorbei, es können keine Codes mehr eingelöst werden.
|
||||
|
||||
# Ticket-Klick-Party
|
||||
|
||||
Wenn ihr im **offenen Verkauf** Tickets klicken möchtet, kommt zu einem unserer Klick-Party-Termine in den Club!
|
||||
|
||||
Termine:
|
||||
* Samstag, 8. November, 11 Uhr
|
||||
* Montag, 17. November, 20 Uhr
|
||||
|
||||
An den zwei Verkaufsterminen treffen wir uns im Club im Zeiseweg und klicken gemeinsam im Shop.
|
||||
Das erhöht die Chancen, im richtigen Moment geklickt zu haben und somit ein Ticket kaufen zu können.
|
||||
|
||||
* Bitte tragt euch hier ein, damit wir eine Idee haben, wie viele Personen jeweils kommen möchten: [Umfrage Ticket-Klick-Party](https://cloud.hamburg.ccc.de/apps/polls/s/0O9QmA3K)
|
||||
* Seid rechtzeitig da! Für den Ticketverkauf muss man im genau richtigen Moment klicken, es lohnt sich, darauf vorbereitet zu sein. Seid deshalb mindestens eine halbe Stunde vor dem Beginn des Verkaufs [bei uns im Club](https://hamburg.ccc.de/#kontakt).
|
||||
* Bringt ein Laptop oder Tablet mit, mit dem ihr in den Shop gehen könnt. Ein Telefon geht grundsätzlich auch, ist aber erfahrungsgemäß etwas fummeliger.
|
||||
* Habt eine Email-Adresse parat, an die die Bestellbestätigung inkl. Zahlungsdaten geschickt werden kann, oder eure Kreditkarte, damit ihr sofort bezahlen könnt.
|
||||
|
|
@ -1,93 +0,0 @@
|
|||
---
|
||||
title: "40C3 Voucher"
|
||||
---
|
||||
|
||||
**[English below](#english)**
|
||||
|
||||
Der Congress findet jedes Jahr statt, und jedes Jahr möchten wir ihn gerne mit euch allen feiern!
|
||||
Damit das klappt, bekommt der CCCHH eine Anzahl an Voucher-Codes, damit wir die mit unseren wundervollen Freunden teilen können.
|
||||
|
||||
Allgemeine Informationen zu Ticket, Vorverkauf und zum Modus Operandi gibt es auf der [40C3-Ticket-Info-Seite](https://events.ccc.de/congress/2026/infos/tickets.de/).
|
||||
Diese Seite hier wird aber regelmäßig mit den neuesten Informationen rund um den Ticket-Prozess im CCCHH aktualisiert.
|
||||
|
||||
## Voucher-Liste
|
||||
|
||||
Wir haben eine Liste von Vouchern für unsere Gemeinschaft.
|
||||
Wenn du diese Seite gesendet bekommen hast, bist du herzlich eingeladen, dich in die Liste einzutragen, um hoffentlich einen Voucher zu bekommen.
|
||||
Fülle das Formular aus, **beachte die Anweisungen**, und wir melden uns mit einem Voucher-Code, sobald einer zur Verfügung steht.
|
||||
|
||||
#### Sehr volle Liste
|
||||
|
||||
Du kannst dich noch über das untenstehende Formular auf unserer Liste eintragen jedoch ist diese bereits stark gefüllt.
|
||||
Sei uns also nicht böse, wenn wir es bis zum Community-Verkaufsschluss nicht zu deinem Eintrag schaffen.
|
||||
|
||||
<details>
|
||||
<summary>Voucher Form (click to expand)</summary>
|
||||
<p>
|
||||
<a href="https://cloud.hamburg.ccc.de/apps/forms/embed/pKAY6YaJxTMZQg3WfEA7o2K5" target="_blank">Open in new Tab</a>
|
||||
</p>
|
||||
<iframe width="100%" height="800px" src="https://cloud.hamburg.ccc.de/apps/forms/embed/pKAY6YaJxTMZQg3WfEA7o2K5"></iframe>
|
||||
</details>
|
||||
|
||||
## Ticket-Klick-Party
|
||||
|
||||
In den sog. <q>Ticket-Klick-Parties</q> treffen wir uns in unserem Räumen und versuchen gemeinsam, während des öffentlichen Verkaufs im Ticket-Shop Tickets zu kaufen.
|
||||
Weil sich die Warteschlage zu Beginn des Verkaufstermins in Sekundenbruchteilen füllt, braucht es mehr Glück als sonst irgendwas, um an ein Ticket zu kommen.
|
||||
Deshalb hilft es, mit freundlichen Wesen zusammen zu sitzen, die einem nach Möglichkeit ein Ticket mit in den Warenkorb legen können, wenn sie selbst durchgekommen sind ;)
|
||||
|
||||
Die Ticket-Klick-Parties werden an den unten geannten Terminen bei uns im [Z9](https://wiki.hamburg.ccc.de/club:z9:start) stattfinden.
|
||||
|
||||
* <time datetime="2026-11-08T11:00+01:00">Sonntag, 8. November, 11:00 (CET)</time>
|
||||
* <time datetime="2026-11-11T18:00+01:00">Mittwoch, 11. November, 18:00 (CET)</time>
|
||||
* <time datetime="2026-11-19T20:00+01:00">Donnerstag, 19. November, 20:00 (CET)</time>
|
||||
|
||||
### Ein paar Regeln
|
||||
|
||||
* Wenn ihr zur Ticket-Klick-Party kommen wollt, tragt euch doch bitte in diese [TODO] Umfrage ein, damit wir den Andrang abschätzen können.
|
||||
* Kommt unbedingt pünktlich! Sobald die Uhr auf 0 springt, muss man bereit sein, im Browser zu klicken. Kommt min. **eine halbe Stunde vor Beginn des Verkaufs**.
|
||||
* Bringt ein eigenes Gerät mit, idealerweise einen Laptop. Mit einem Telefon oder Tablet geht es notfalls auch, ist aber erfahrungsgemäß schwieriger, denn man muss ein Captcha lösen, welches erfahrungsgemäß für Laptops ausgelegt ist.
|
||||
* Ihr braucht eine funktionierende Email-Adresse, um die Bestellung abschließen zu können. Habt diese zum Termin parat. Ihr braucht keine Kreditkarte zur unmittelbaren Bezahlung, aber die Zahlungsinformationen werden euch per Email gesendet.
|
||||
|
||||
# English
|
||||
|
||||
Every year congress happens and every year we want to celebrate it together with all of you.
|
||||
For this purpose, CCCHH is getting an amount of vouchers to share among all our wonderful friends.
|
||||
|
||||
For general information about congress tickets, presales, and modus operandi please visit the [40C3 Ticket Info Page](https://events.ccc.de/congress/2026/infos/tickets/).
|
||||
This page will be updated regularily with relevant information regarding ticket procedures around CCCHH though.
|
||||
|
||||
## Voucher-List
|
||||
|
||||
We maintain a voucher list for our community.
|
||||
If you were sent this page you are welcome to enter yourself in it and potentially receive a voucher from our pool.
|
||||
Fill in the form below, while **reading the instructions**, and we will get back to you with your voucher when it becomes available.
|
||||
|
||||
#### List quite full already
|
||||
|
||||
While you can still enter yourself via the form below the list is already quite full and your chances of getting a voucher are honestly quite slim.
|
||||
|
||||
<details>
|
||||
<summary>Voucher Form (click to expand)</summary>
|
||||
<p>
|
||||
<a href="https://cloud.hamburg.ccc.de/apps/forms/embed/pKAY6YaJxTMZQg3WfEA7o2K5" target="_blank">Open in new Tab</a>
|
||||
</p>
|
||||
<iframe width="100%" height="800px" src="https://cloud.hamburg.ccc.de/apps/forms/embed/pKAY6YaJxTMZQg3WfEA7o2K5"></iframe>
|
||||
</details>
|
||||
|
||||
## Ticket Click Party
|
||||
|
||||
In so called <q>Ticket Click Parties</q> we get together in our space to try and buy some tickets together during the public presales.
|
||||
As the queue during those public sales is usually ruthless and getting a ticket takes more luck than anything else, it helps to be around friendly creatues who might even put an additional ticket for you in their basket when they get through ;)
|
||||
|
||||
Ticket-Click-Parties are taking place on the below dates in [our rooms](https://wiki.hamburg.ccc.de/club:z9:start).
|
||||
|
||||
* <time datetime="2026-11-08T11:00+01:00">Sunday, 8th of November, 11:00 (CET)</time>
|
||||
* <time datetime="2026-11-11T18:00+01:00">Wednesday, 11th of November, 18:00 (CET)</time>
|
||||
* <time datetime="2026-11-19T20:00+01:00">Thursday, 19th of November, 20:00 (CET)</time>
|
||||
|
||||
### A few rules
|
||||
|
||||
* Please enter your intent to appear in our space in [TODO] poll. This is so we can know how many people to expect.
|
||||
* Be there on time! Timing is everything during the public sales to be fully ready once the clock hits 0. **At least half an hour early** is recommended.
|
||||
* Bring your own device, preferrably a laptop. While a smartphone is doable the ticket shop usually has a captcha that is not very mobile friendly so a laptop is recommended to be fast.
|
||||
* Have an EMail address on hand to finish ordering. While you do not need to pay with a creditcard or similar immediately during the order, you will need an EMail address to which the order confirmation and payment details will be sent.
|
||||
|
|
@ -4,4 +4,7 @@ date: 2022-11-20T09:03:20-08:00
|
|||
draft: false
|
||||
---
|
||||
|
||||
<!-- STATUS_CANARY_HAMBURG_CCC_DE_DO_NOT_TOUCH -->
|
||||
## Über uns
|
||||
Wir sind der Chaos Computer Club der Hansestadt Hamburg.
|
||||
Bei uns handelt es sich um eine Gruppe von Menschen, die ein Interesse am kreativen Umgang mit Technik teilen.
|
||||
Unsere Gesprächsthemen und Projekte reichen von Soft- und Hardware zu Datenschutz und Netzpolitik.
|
||||
|
|
|
|||
|
|
@ -1,19 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: article
|
||||
draft: false
|
||||
lastmod: '2001-05-20T19:27:59+02:00'
|
||||
publishDate: '2001-05-20T19:27:59+02:00'
|
||||
slug: cybercrime-konvention-index
|
||||
title: Cybercrime-Konvention
|
||||
---
|
||||
Schon im Juni soll die Cybercrime-Konvention des Europarates die letzte
|
||||
Hürde vor dem Inkrafttreten genommen haben. Aus diesem Anlaß haben wir
|
||||
eine [Informationsseite][1] erstellt, um schon mal einen Einblick in das
|
||||
zu geben, was uns in allzunaher Zukunft erwarten wird, wenn die Proteste
|
||||
keinen Erfolg haben.
|
||||
|
||||
|
||||
|
||||
[1]: http://www.ccc.de/cybercrime
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: article
|
||||
draft: false
|
||||
lastmod: '2001-07-29T19:28:59+02:00'
|
||||
publishDate: '2001-07-29T19:28:59+02:00'
|
||||
slug: wir-trauern-um-wau-index
|
||||
title: Wir trauern um Wau.
|
||||
---
|
||||
Wau Holland, Gründungsmitglied und Alterspräsident des CCC, starb am
|
||||
Morgen des 29.7.2001 an den Folgen eines Schlaganfalls. Kondolenzen auf
|
||||
http://www.digitalis.org/wau.
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: event
|
||||
draft: false
|
||||
lastmod: '2001-09-01T11:42:03+02:00'
|
||||
publishDate: '2001-09-01T11:42:03+02:00'
|
||||
slug: bildungswerk-mobile-mesh-und-andere-wireless-lan-ad-hoc-vernetzungsmethoden-index
|
||||
title: 'Bildungswerk: Mobile Mesh und andere Wireless LAN Ad-Hoc Vernetzungsmethoden?'
|
||||
---
|
||||
Nächsten Donnerstag, den 06.09.2001 findet ein Workshop im Rahmen des
|
||||
Chaos-Bildungswerks statt.
|
||||
|
||||
Thema sind Wireless LAN und wie man damit Ad-Hoc-Netzwerke aufbauen
|
||||
kann. Beginn ist um 19:00 Uhr in den Räumen des CCC Hamburg. Gäste sind
|
||||
herzlich eingeladen! Wenn vorhanden, bitte Notebooks und FunkLAN-Karten
|
||||
mitbringen. Weitere Infos auf den Bildungswerk-Seiten.
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: event
|
||||
draft: false
|
||||
lastmod: '2001-10-02T19:30:51+02:00'
|
||||
publishDate: '2001-10-02T19:30:51+02:00'
|
||||
slug: bildungswerk-bufferoverflow-workshop-index
|
||||
title: 'Bildungswerk: Bufferoverflow-Workshop'
|
||||
---
|
||||
Am Donnerstag, den 18.10.2001 ist Zeit für einen besonderen Workshop:
|
||||
Bufferoverflows.
|
||||
|
||||
Das Ziel des Workshops ist es, die Grundlagen zum Schreiben eines
|
||||
Bufferoverflow-Exploits durch \"learning by doing\" zu erlernen.
|
||||
Grundkenntnisse in C sind erforderlich, Kenntnisse in Assembler und Perl
|
||||
sind wünschenswert, aber nicht erforderlich.
|
||||
|
||||
Das dem Workshop zugrunde liegende Material gibt es unter:
|
||||
http://hamburg.ccc.de/ck/index.php?sectxt
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: article
|
||||
draft: false
|
||||
lastmod: '2002-01-30T11:43:30+01:00'
|
||||
publishDate: '2002-01-30T11:43:30+01:00'
|
||||
slug: e-mail-probleme-index
|
||||
title: E-Mail-Probleme
|
||||
---
|
||||
Bedauerlicherweise hatten wir in der letzten Woche einen Ausfall unseres
|
||||
E-Mail-Servers. Falls Sie uns eine E-Mail geschickt haben und keine
|
||||
Antwort erhalten, senden Sie diese bitte erneut.
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: event
|
||||
draft: false
|
||||
lastmod: '2002-02-12T11:44:01+01:00'
|
||||
publishDate: '2002-02-12T11:44:01+01:00'
|
||||
slug: neue-workshops-im-chaos-bildungswerk-index
|
||||
title: Neue Workshops im Chaos-Bildungswerk
|
||||
---
|
||||
Für Februar, März und April sind 3 Bildungswerk-Veranstaltungen geplant.
|
||||
|
||||
28.02.: Wie sicher sind ec-Karten?
|
||||
|
||||
14.03.: Videoüberwachung
|
||||
|
||||
18.04.: INPOL-neu (?)
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: article
|
||||
draft: false
|
||||
lastmod: '2002-03-05T01:13:56+01:00'
|
||||
publishDate: '2002-03-05T01:13:56+01:00'
|
||||
slug: chaos-cd-infos-wieder-erreichbar-beispiel-inhalte-aufrufbar-index
|
||||
title: Chaos-CD-Infos wieder erreichbar / Beispiel-Inhalte aufrufbar
|
||||
---
|
||||
Wer immer schon mal etwas mehr über die Chaos-CD erfahren wollte: über
|
||||
die obige Graphik kann ab sofort wieder [der Inhalt der Chaos-CD][1]
|
||||
getestet werden. Ausserdem sind die beschreibenden Texte und einige
|
||||
Zusatz-Infos verlinkt.
|
||||
|
||||
|
||||
|
||||
[1]: http://hamburg.ccc.de/chaoscd/chaoscd/index.html
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
authors:
|
||||
- desc
|
||||
categories: event
|
||||
draft: false
|
||||
lastmod: '2002-03-12T11:45:05+01:00'
|
||||
publishDate: '2002-03-12T11:45:05+01:00'
|
||||
slug: bildungswerk-am-donnerstag-videouberwachung-index
|
||||
title: "Bildungswerk am Donnerstag: Videoüberwachung"
|
||||
---
|
||||
Diesen Donnerstag, den 14.03.2002, wird uns padeluun besuchen und über
|
||||
Videoüberwachung referieren. Beginn: 19:30 Uhr. Weitere Infos auf den
|
||||
Bildungswerk-Seiten.
|
||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue