diff options
| author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2025-05-03 12:38:39 +0200 |
|---|---|---|
| committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2025-06-15 01:30:32 +0200 |
| commit | 83d796eeb1c8db91b8a11f36eb00f91bce8173e0 (patch) | |
| tree | 1a01a7e04b5ea476588497c75c6de54db414d5a4 /markdown/2023_12_replicant-37c3.md | |
| parent | 48a8a5c2f392dea41bebcbf126cbb3a452e961b3 (diff) | |
| download | haunt-blog-83d796eeb1c8db91b8a11f36eb00f91bce8173e0.tar.gz haunt-blog-83d796eeb1c8db91b8a11f36eb00f91bce8173e0.tar.bz2 haunt-blog-83d796eeb1c8db91b8a11f36eb00f91bce8173e0.zip | |
Move blog posts to the posts/ directory.
We also have two other pages that are not generated from the blog posts
(reply.html and search.html).
It would be nice to be able to move them to markdown as well, but if we do
that it is necessary to differenciate between markdown files used to generate
blog posts, and the ones used to generate these pages.
In addition if the blog posts directory is named markdown, and that we have
other markdown files as well, it become confusing for contributors.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'markdown/2023_12_replicant-37c3.md')
| -rw-r--r-- | markdown/2023_12_replicant-37c3.md | 56 |
1 files changed, 0 insertions, 56 deletions
diff --git a/markdown/2023_12_replicant-37c3.md b/markdown/2023_12_replicant-37c3.md deleted file mode 100644 index 53b4b13..0000000 --- a/markdown/2023_12_replicant-37c3.md +++ /dev/null @@ -1,56 +0,0 @@ -date: 2023-12-28T22:40:17+00:00 -title: Replicant @ 37C3 -authors: dllud -tags: Replicant news, dllud -licenses: CC-BY-3.0 OR CC-BY-4.0 ---- -Since yesterday, December 27th, the [37th Chaos Communication Congress -(37C3)][1] is taking place in Hamburg. Replicant is present as part of the -[Critical Decentralization Cluster (CDC)][2]. - -[Replicant's assembly][3] is the place to come by if need help installing -Replicant or general advice regarding software freedom on smartphones and -tablets. You can also take the opportunity to verify the release signing PGP. - -Location: [G5, Hall 3, Level 0][4] -DECT: 8652 - -As Replicant is struggling with structural problems, first and foremost lack -of contributors on key areas (development, sysadmining, communication, -coordination, documentation), we are looking to onboard new people with fresh -ideas. Please drop by if you feel keen to help on any of these field. - -There will also be a few talks and gatherings about Replicant and related -topics in several spots around the congress: - -* [Short introduction to Replicant as part of the CDC][5] – December 27 - 16:30, Saal E - -* [Introduction to Replicant][6] – December 28 10:00, Saal D - -* [Replicant struggle: past and present successes and failures][7] – - December 28 14:00, Saal 3, CDC, Round Table - -* [Smartphones freedom status in 2023][8] – December 30 12:30, Saal E - -* [Replicant Meetup][9] – December 30 14:00, Saal 3, CDC, Round Table - - [1]: <https://events.ccc.de/congress/2023/wiki/index.php/Main_Page> - - [2]: <https://decentral.community/> - - [3]: <https://events.ccc.de/congress/2023/hub/en/assembly/replicant/> - - [4]: <https://37c3.c3nav.de/l/replicant/> - - [5]: <https://events.ccc.de/congress/2023/hub/en/event/cdc-introduction-to-critical-decentralization/> - - [6]: <https://events.ccc.de/congress/2023/hub/en/event/introduction-to-replicant/> - - [7]: <https://events.ccc.de/congress/2023/hub/en/event/replicant-struggle-past-and-present-successes-and-/> - - [8]: <https://events.ccc.de/congress/2023/hub/en/event/smartphones-freedom-status-in-2023/> - - [9]: <https://events.ccc.de/congress/2023/hub/en/event/replicant-meetup/> - - |