diff --git a/.gitea/workflows/hugo.yaml b/.gitea/workflows/hugo.yaml index d7f59cc..5ccc4b6 100644 --- a/.gitea/workflows/hugo.yaml +++ b/.gitea/workflows/hugo.yaml @@ -43,7 +43,7 @@ jobs: - name: Setup Hugo uses: https://github.com/peaceiris/actions-hugo@v3.0.0 with: - hugo-version: "latest" + hugo-version: "0.155.3" extended: true - name: Build website with Hugo diff --git a/archetypes/blog/index.md b/archetypes/blog/index.md new file mode 100644 index 0000000..7e7de91 --- /dev/null +++ b/archetypes/blog/index.md @@ -0,0 +1,28 @@ +--- +title: "{{ replace (replaceRE "^[0-9]{4}-[0-9]{2}-" "" .Name) "-" " " | title }}" +date: {{ now.Format "2006-01-02" }} +categories: + # Language + - english + # - deutsch + # - presentation + # - podcast + # - article +tags: + # - https://mehl.mx/tags/ +# headerimage: +# src: foo.jpg +# text: bar +# summary: Visible on the listing page, but not on the article page +# video: https://link.to/video +# slides: https://link.to/slides +# audio: https://link.to/audio +# article: +# name: Media Name +# href: https://link.to/article +# event: +# name: Event Name +# href: https://link.to/event +--- + +Content diff --git a/archetypes/default.md b/archetypes/default.md index 5ab9703..38dbcef 100644 --- a/archetypes/default.md +++ b/archetypes/default.md @@ -2,6 +2,7 @@ title: "{{ replace (replaceRE "^[0-9]{4}-[0-9]{2}-" "" .Name) "-" " " | title }}" date: {{ now.Format "2006-01-02" }} categories: + - blog - english - deutsch tags: diff --git a/config.toml b/config.toml index c2c2fc7..12a8b6b 100755 --- a/config.toml +++ b/config.toml @@ -2,10 +2,15 @@ baseurl = "https://mehl.mx/" languageCode = "en-GB" title = "Max Mehl" theme = [ "hugo-sustain", "hugo-cloak-email", "hugo-mastodon-comments", "hugo-snap-gallery" ] +summaryLength = 50 [markup.highlight] -codeFences = true -style = "emacs" + codeFences = true + style = "emacs" +# English quotation marks +[markup.goldmark.extensions.typographer] + leftDoubleQuote = '“' + rightDoubleQuote = '”' [permalinks] blog = "/blog/:year/:slug" @@ -20,16 +25,13 @@ style = "emacs" custom_css = ["comments/mastodon-comments.css"] custom_js = ["comments/getcomments.js"] -[params.blog] - headline = "Thoughts about tech, politics, and more" - [params.social] Github = "mxmehl" Git = "https://src.mehl.mx/mxmehl" Email = "" # Twitter = "mxmehl" LinkedIn = "mxmehl" - Stackoverflow = "users/4273755/mxmehl" + # Stackoverflow = "users/4273755/mxmehl" Mastodon = "mastodon.social/@mxmehl" # Diaspora = "diasp.eu/u/mxmehl" @@ -47,31 +49,36 @@ style = "emacs" ## Main Menu [[menu.main]] - name = "start" + name = "Start" weight = 100 identifier = "start" url = "/" [[menu.main]] - name = "blog" + name = "Updates" identifier = "blog" weight = 200 url = "/blog/" -[[menu.main]] - name = "links" - identifier = "links" - weight = 300 - url = "/links/" [[menu.main]] name = "IT Services" identifier = "it" - weight = 400 + weight = 300 url = "/it/" [[menu.main]] - name = "contact" + name = "Contact" identifier = "contact" - weight = 500 + weight = 400 url = "/contact/" [privacy.youtube] disable = false privacyEnhanced = true + +# Modules +[[module.mounts]] + # Make static images available as image assets by default + source = "static/img/" + target = "assets/images/" + +[imaging] + compression = 'lossy' + quality = 90 diff --git a/content/_index.md b/content/_index.md index 412bcea..554c43d 100644 --- a/content/_index.md +++ b/content/_index.md @@ -6,14 +6,12 @@ summary: Open Source expert with background in tech and policy. Focused on strat ## Hi, I'm **Max Mehl**. -Open Source has always been more than code to me. I deeply care about its principles such as collaboration, transparency, and pragmatic problem-solving. +Open Source is more than just code to me. I deeply care about its principles of collaboration, transparency, and pragmatic problem-solving. -I work at Deutsche Bahn on Open Source strategy, governance, and team enablement. The goal is to help the organisation use and contribute to Open Source effectively. This includes co-founding the OpenRail Association for sector-wide collaboration and advancing software supply chain practices, especially around SBOMs and Cyber Resilience Act compliance. +I work at **Deutsche Bahn**'s virtual Open Source Program Office (OSPO). I helped co-found the **OpenRail Association** to foster sector-wide collaboration. Another focus is on **software supply chain management** with an emphasis on SBOMs and CRA compliance. -With a background in political and administrative science and a strong technical foundation, my work often bridges technology and strategy. The focus is always on practical, long-term solutions that balance compliance, security, and efficiency. +Previously, I was with the **Free Software Foundation Europe** (FSFE), leading policy, public awareness, and legal initiatives such as *Public Money, Public Code* and *REUSE*. Before that, I founded a small, client-focused IT consultancy firm offering website development and system administration. -Previously, I was with the Free Software Foundation Europe, leading licensing and compliance initiatives such as *REUSE* and campaigns like *Public Money, Public Code*. Before that, I founded a small, client-focused [IT consultancy]({{< ref "it" >}}) offering website development and system administration. +Outside of work, I enjoy being with my family, bouldering, and maintaining some software projects. -Outside of work, most of my time goes into family life with two kids. As a self-taught software developer, some of the rest goes into maintaining Open Source projects — and a little less than I'd like into climbing walls without ropes. - -Once in a while [I blog]({{< ref "blog" >}}) about things that keep me busy. You can contact me via email, messenger, or any of the platforms listed below. See the [contact page]({{< ref "contact" >}}) for more details. +On this site, I regularly share [updates]({{< relref "blog" >}}) on my work and projects. Feel free to [reach out]({{< relref "contact" >}}). diff --git a/content/blog/2013-10-organising-micro-task-emails-in-thunderbird.md b/content/blog/2013-10-organising-micro-task-emails-in-thunderbird.md index 409ade9..4947fde 100644 --- a/content/blog/2013-10-organising-micro-task-emails-in-thunderbird.md +++ b/content/blog/2013-10-organising-micro-task-emails-in-thunderbird.md @@ -3,21 +3,20 @@ title: Organising micro task emails in Thunderbird date: 2013-10-27T23:12:55+00:00 aliases: organising-micro-task-emails-in-thunderbird categories: + - blog - english tags: - - email - - guide - - tools + - Communication --- The title of this post sounds very significant but to be honest, it’s a small thing. Everybody has her/his/its own workflow regarding emails. For example me: I LOVE folders! When it comes to the crunch I probably would be able to organise my whole life into folders. - + Well, at least this is what I thought until I began my internship at [FSFE](https://fsfe.org/). I was used to a high income rate (do you say so?) before but something changed: Normally I read my emails and if something’s important, I open a new task in my taskmanager or simply write it down. In the office I also read lot’s of emails and can put them easily in folders via filters (in Thunderbird and with qmail/maildrop on my mailserver), for example emails in mailing lists. But now it is more often the case that by reading those emails, there are beginning some mini-tasks: Commit this [translated](https://fsfe.org/contribute/translators/) file on the server, answer these emails, send out that package to a [fellow](https://fsfe.org/fellowship/) (but not today, do it next Monday), and most importantly, book some restaurants for the General Assembly. You see, these are all small tasks, but they exist. In dozens. And I’m quite sure they will increase. But creating for each micro task a new task in my task manager ([Getting Things Gnome](http://gtgnome.net/) by the way) is overload as well. - + For that I’m a forgetful technocrat sometimes, I wanted to pre-empt any mistakes and searched for methods to mark/tag those emails when reading them. Afterwards it should always be possible to find these marked/tagged with one click. In short, I needed a [Remembrall](http://harrypotter.wikia.com/wiki/Remembrall), that additionally tells me, what I exactly forgot. Dear ladies and gentlemen, here’s my odyssey of finding the perfect method for me: @@ -37,7 +36,7 @@ Dear ladies and gentlemen, here’s my odyssey of finding the perfect method for Each method has its advantages. The tags are quite nice because you can differentiate between (own) tags and you can simply press the corresponding number on the keyboard to tag the mail. The marking method does not have such features but on my mobile (K-9 Mail) I cannot tag an email but only mark it. So I’m able to save some mails for later work when I’m sitting in the train for example. No matter how you decide (I’m not quite sure as well what’s the best for me), it’s quite hard to find the emails if you have tagged them. Of course, if you look in the folder, you see colored mails or those with a star but to find them by hand in dozens of folder… good luck boy. - + I already mentioned virtual folders: You can open a virtual folder that lists all emails that match a (or more) special criteria which you can define. If you untag/unmark an email, it just disappears from the virtual folder, but still exists in the (now untagged/unmarked) way as before. {{< gallery >}} diff --git a/content/blog/2014-01-mounting-a-sftp-storage-in-gnu-linux.md b/content/blog/2014-01-mounting-a-sftp-storage-in-gnu-linux.md index dc385b7..f2689c0 100644 --- a/content/blog/2014-01-mounting-a-sftp-storage-in-gnu-linux.md +++ b/content/blog/2014-01-mounting-a-sftp-storage-in-gnu-linux.md @@ -3,13 +3,12 @@ title: Mounting a SFTP storage in GNU/Linux date: 2014-01-13T14:42:01+00:00 aliases: /blog/2014/mounting-a-sftp-storage-in-gnu-linux categories: + - blog - english tags: - - bash - - guide - - security - - server - - tools + - Code + - Security + - SystemAdministration --- This (longer than expected) post explains how to transfer files securely between your device and an external storage. The first part may be useful for you if you only have little knowledge of terms like (S)FTP(S) and want to learn something about widely used technologies. The second part will help you to mount an external storage so you can manage all files as if they are on your local device and the third, fourth and fifth part will concentrate on easing the mounting process by the help of hostnames, Private/Public Keys and a shell script. @@ -47,10 +46,10 @@ The only prerequisite: You need a server/webspace/storage with full SSH access. Now we come to the technical part. For this post, following data is used. Most likely, this will look different in your case. ``` -SSH-Server: server1.net -Username on server: client -Home directory of user on server: /home/client -Username local machine: user +SSH-Server: server1.net +Username on server: client +Home directory of user on server: /home/client +Username local machine: user Local mount directory: /home/user/remote/server1 ``` @@ -87,9 +86,9 @@ In the next step, we will make the connection and mounting more comfortable, eve Now that you know how (and that) the system works, we will make it easier. Of course it is quite annoying to type in the whole server-address and port each time. Instead of _sshfs -p 22 client@server1.net[…]_, you can simply type _sshfs server1_. How? Just open the SSH configuration file _/home/user/.ssh/config_ with you desired text editor and add: ``` -Host server1 - HostName server1.net - Port 22 +Host server1 + HostName server1.net + Port 22 User client ``` @@ -109,7 +108,7 @@ Let’s say, the public key is a chest that no one except the owner can open. In It is quite easy to make this system happen. Again we need a terminal to generate the two keys: ```bash -cd ~/.ssh/ +cd ~/.ssh/ ssh-keygen -t dsa ``` @@ -141,86 +140,86 @@ And these steps were quite important for the next section where we will write a Our setting is very smooth now, but it could still be improved. If you want to connect to many servers and don’t want to use your shell every time or don’t want to remember the HOSTs you used in your .ssh/config, you’re free to modify and use this shell script: ```bash -#!/bin/bash - -### VARIABLES TO BE CHANGED ### -# Preconfigured HOSTs in ~/.ssh/config that should be used -PRESSH[0]=server1 -PRESSH[1]=server2 -PRESSH[2]=server3 - -# Local directory where the remote storages should be mounted to -LOCALMOUNTDIR=/home/user/remote - -### THE SCRIPT BEGINS HERE ### - -# Add SSH key to local keyring if not already happened -function sshadd { - ssh-add -l > /dev/null || ssh-add -} - -# Choose preconfigured HOST to mount -function mount { - if ! SSH=$(zenity --list \ - --height=300 \ - --text="Please choose. Cancel to unmount drives." \ - --title="Choose SSH server" \ - --column "Preconfigured SSH servers" \ - ${PRESSH[*]}); then - unmountquestion # If you press cancel, it should ask you to unmount all drives - fi - - # If you double click on an entry, it gives 'server1|server1' as result instead of 'server1' - # This command cuts of everything after | - SSH=$(echo $SSH | awk -F\| '{ print $1 }') - - # Make a local directory if not available - if [ ! -e "$LOCALMOUNTDIR"/"$SSH" ]; then - mkdir -p "$LOCALMOUNTDIR"/"$SSH" - fi - - # Command to mount actually - sshfs "$SSH": "$LOCALMOUNTDIR"/"$SSH"/ -o follow_symlinks & - - quitquestion # one more ssh server or quit? - -} - -# Ask if all preconfigured SSHFS drives should be unmounted -function unmountquestion { - zenity --question --text="Unmount all preconfigured\nSSHFS drives now?" - if [ "$?" = "0" ]; then - unmount # unmount function - else - exit 0 - fi -} - -# Procedure to unmount all preconfigured SSHFS drives and exit program afterwards -function unmount { - for ((i = 0; i < ${#PRESSH[*]}; i++)) - do - fusermount -u "$LOCALMOUNTDIR"/"${PRESSH[$i]}" - echo ""${PRESSH[$i]}" unmounted." - done - exit 0 -} - -# Should another SSHFS storage be mounted? -function quitquestion { - zenity --question \ - --text="Mount another SSHFS storage?" - if [ "$?" = "1" ]; then - exit 0 - fi -} - -sshadd # sshadd function - -# Loop for endless mounts until stopped by unmount or unmountquestion -while : -do - mount # mount function +#!/bin/bash + +### VARIABLES TO BE CHANGED ### +# Preconfigured HOSTs in ~/.ssh/config that should be used +PRESSH[0]=server1 +PRESSH[1]=server2 +PRESSH[2]=server3 + +# Local directory where the remote storages should be mounted to +LOCALMOUNTDIR=/home/user/remote + +### THE SCRIPT BEGINS HERE ### + +# Add SSH key to local keyring if not already happened +function sshadd { + ssh-add -l > /dev/null || ssh-add +} + +# Choose preconfigured HOST to mount +function mount { + if ! SSH=$(zenity --list \ + --height=300 \ + --text="Please choose. Cancel to unmount drives." \ + --title="Choose SSH server" \ + --column "Preconfigured SSH servers" \ + ${PRESSH[*]}); then + unmountquestion # If you press cancel, it should ask you to unmount all drives + fi + + # If you double click on an entry, it gives 'server1|server1' as result instead of 'server1' + # This command cuts of everything after | + SSH=$(echo $SSH | awk -F\| '{ print $1 }') + + # Make a local directory if not available + if [ ! -e "$LOCALMOUNTDIR"/"$SSH" ]; then + mkdir -p "$LOCALMOUNTDIR"/"$SSH" + fi + + # Command to mount actually + sshfs "$SSH": "$LOCALMOUNTDIR"/"$SSH"/ -o follow_symlinks & + + quitquestion # one more ssh server or quit? + +} + +# Ask if all preconfigured SSHFS drives should be unmounted +function unmountquestion { + zenity --question --text="Unmount all preconfigured\nSSHFS drives now?" + if [ "$?" = "0" ]; then + unmount # unmount function + else + exit 0 + fi +} + +# Procedure to unmount all preconfigured SSHFS drives and exit program afterwards +function unmount { + for ((i = 0; i < ${#PRESSH[*]}; i++)) + do + fusermount -u "$LOCALMOUNTDIR"/"${PRESSH[$i]}" + echo ""${PRESSH[$i]}" unmounted." + done + exit 0 +} + +# Should another SSHFS storage be mounted? +function quitquestion { + zenity --question \ + --text="Mount another SSHFS storage?" + if [ "$?" = "1" ]; then + exit 0 + fi +} + +sshadd # sshadd function + +# Loop for endless mounts until stopped by unmount or unmountquestion +while : +do + mount # mount function done ``` diff --git a/content/blog/2014-01-why-free-choice-of-routers-is-an-unnegotiable-must.md b/content/blog/2014-01-why-free-choice-of-routers-is-an-unnegotiable-must.md index 8a039e3..8f19109 100644 --- a/content/blog/2014-01-why-free-choice-of-routers-is-an-unnegotiable-must.md +++ b/content/blog/2014-01-why-free-choice-of-routers-is-an-unnegotiable-must.md @@ -3,13 +3,13 @@ title: Why free choice of routers is a must date: 2014-01-14T17:47:43+00:00 aliases: why-free-choice-of-routers-is-an-unnegotiable-must categories: + - blog - english tags: - - routerfreedom - - fsfe - - germany - - security - - policy + - RouterFreedom + - FSFE + - Security + - Policy --- diff --git a/content/blog/2014-02-i-love-znc-because-ilovefs.md b/content/blog/2014-02-i-love-znc-because-ilovefs.md index 67de249..2233f58 100644 --- a/content/blog/2014-02-i-love-znc-because-ilovefs.md +++ b/content/blog/2014-02-i-love-znc-because-ilovefs.md @@ -3,12 +3,12 @@ title: 'I love ZNC because #ilovefs' date: 2014-02-14T05:00:14+00:00 url: /blog/2014/i-love-znc-because-ilovefs categories: + - blog - english tags: - - chat - - ilovefs - - server - - tools + - Communication + - ILoveFS + - SystemAdministration --- diff --git a/content/blog/2014-02-wirklich-sichere-whatsapp-alternativen.md b/content/blog/2014-02-wirklich-sichere-whatsapp-alternativen.md index e2407b5..3519f5f 100644 --- a/content/blog/2014-02-wirklich-sichere-whatsapp-alternativen.md +++ b/content/blog/2014-02-wirklich-sichere-whatsapp-alternativen.md @@ -3,10 +3,11 @@ title: Wirklich sichere WhatsApp Alternativen date: 2014-02-21T09:41:54+00:00 aliases: wirklich-sichere-whatsapp-alternativen categories: + - blog - deutsch tags: - - chat - - security + - Communication + - Security --- Nachdem diese Woche bekannt wurde, dass Facebook es endlich geschafft hat, WhatsApp-Gründer Jan Koum und Brian Acton mit einer stolzen Summe von rund 16 Milliarden US-Dollar [zum Verkauf ihrer Firma](http://www.sueddeutsche.de/wirtschaft/uebernahme-in-der-technikbranche-facebook-kauft-whatsapp-1.1893830) zu bewegen, fragen sich viele, was sich nun in Sachen Privatsphäre ändern wird – und wie man dem entgegenwirken kann. In diesme Artikel werde ich erläutern, was man bei der Wahl des richtigen Messengers beachten sollte, warum Threema nicht die Lösung ist und was wirklich sichere Alternativen sind. diff --git a/content/blog/2014-05-guter-e-mail-stil.md b/content/blog/2014-05-guter-e-mail-stil.md index 349fb74..f0aeb36 100644 --- a/content/blog/2014-05-guter-e-mail-stil.md +++ b/content/blog/2014-05-guter-e-mail-stil.md @@ -3,15 +3,14 @@ title: Guter E-Mail-Stil date: 2014-05-19T12:56:12+00:00 aliases: guter-e-mail-stil categories: + - blog - deutsch tags: - - chat - - email - - guide + - Communication --- Heutzutage ist schriftlicher Stil in E-Mails ebenso wichtig wie eine angemessene Sprechweise oder standardisierte Floskeln und Höflichkeiten in Briefen. E-Mails sind trotz Short Messaging wie per SMS, WhatsApp oder Facebook weiterhin die bedeutenste digitale Kommunikationsmöglichkeit. - + Das ist auch der Grund, weshalb ein guter E-Mail-Stil so enorm wichtig ist: Wir werden von E-Mails regelrecht bombardiert, auch wenn man den Spam nicht einmal mit einberechnet. Daher sollten wir uns und unseren Kommunikationspartnern die Sache erleichtern, indem wir einen guten, effizienten und dennoch freundlichen Umgang und Stil pflegen. ## Der Erstkontakt @@ -21,7 +20,7 @@ Sollte man derjenige sein, der eine E-Mail versendet, sind bereits einige Dinge ### Betreff Der Betreff ist das erste, was der Empfänger erhält und auch das, an was er sich bei weiterer Kommunikation erinnert. - + Betreffe wie "Echt wichtig!", "Das könnte dich interessieren", ":-)" oder "Es geht um die Webseite ``http://example.com`` zu der ich dich was fragen muss" sind entweder nicht informativ genug, zu kurz oder zu lang. Betreffe sollten das Thema präzise in nicht mehr als 5 Wörtern zusammenfassen, etwa "Fehlerhaftes Bild in Thunderbird-Artikel". ### Adressierung @@ -40,7 +39,7 @@ Viele E-Mail-Clients bieten an, E-Mails in HTML zu verfassen. HTML ermöglicht e ### Umbruch Wenn wie empfohlen Reintext verwendet wird, empfiehlt sich auch, dass man einen automatischen Umbruch aktiviert. Das bedeutet, dass nach 70-80 Zeichen automatisch eine neue Zeile begonnen wird. - + Dadurch wird verhindert, dass Leute mit sehr breiten Bildschirmen elends lange Zeilen haben, was den Lesefluss erschwert. ### Stil @@ -50,7 +49,7 @@ Sollte eigentlich selbstverständlich sein, aber leider sieht man viel zu oft E- ## Antworten Hat man eine neue E-Mail bekommen und möchte diese beantworten, gibt es auch wieder einige Dinge, die man beachten sollte, um seine Informationen möglichst leicht und übersichtlich unterzubringen und es dem entfernten Gegenüber leicht zu machen. - + Prinzipiell sollte man immer auf *Antworten* in seinem Mailprogramm drücken und nicht etwa eine neue E-Mail mit neuem Betreff verfassen. ### Betreff @@ -65,59 +64,59 @@ Beim Antworten gibt es in puncto Betreff nur zwei Regeln: Ganz wichtig bei längeren Unterhaltungen ist der richtige Zitierstil. Wenn wir mit Leuten reden, sind wir gewöhnt, meist immer unmittelbar auf ein Thema antworten zu können, womit dem Gegenüber klar wird, auf was wir anspielen. In E-Mails ist das meist nicht so einfach. Hier sollte man darauf achten, dass man den sogenannten Inlinequote benutzt und kein [TOFU](https://de.wikipedia.org/wiki/TOFU) (Text oben, Fullquote unten). Zwei aus der Wikipedia abgeleitete Beispiele, die das verdeutlichen: ``` -Lieber Oskar, - -das stimmt doch gar -nicht. Richtig ist 4. - -Ich hätte gerne einen Bierkrug. - -Gruß -Max - ---Ursprüngliche Nachricht-- -Von: Oskar -[mailto:oskar@example.net] -Gesendet: Sonntag, 24. -Dezember 2006 12:00 -An: Max -Betreff: (kein Betreff) - -Lieber Max, - -eines wollte ich Dir schon -immer einmal sagen - das -habe ich mich bisher bloß -nicht getraut. Es lässt -mir aber einfach keine -Ruhe, deshalb muss es nun -heraus: -2 + 2 = 5 -Wie jedermann weiß. - -Außerdem fahre ich bald nach Mallorca, -soll ich dir was mitbringen? - -Beste Grüße +Lieber Oskar, + +das stimmt doch gar +nicht. Richtig ist 4. + +Ich hätte gerne einen Bierkrug. + +Gruß +Max + +--Ursprüngliche Nachricht-- +Von: Oskar +[mailto:oskar@example.net] +Gesendet: Sonntag, 24. +Dezember 2006 12:00 +An: Max +Betreff: (kein Betreff) + +Lieber Max, + +eines wollte ich Dir schon +immer einmal sagen - das +habe ich mich bisher bloß +nicht getraut. Es lässt +mir aber einfach keine +Ruhe, deshalb muss es nun +heraus: +2 + 2 = 5 +Wie jedermann weiß. + +Außerdem fahre ich bald nach Mallorca, +soll ich dir was mitbringen? + +Beste Grüße Oskar ``` Wenn man diese Mail nach einigen Tagen öffnet, fragt man sich zurecht, was denn nun ein Bierkrug mit einer falschen Behauptung zu tun hat. Besser ist dabei der bereits erwähnte Inlinequote ("Zitat zwischen den Zeilen"): ``` -Lieber Oskar, - -Oskar schrieb: -> 2 + 2 = 5 - -das stimmt doch gar -nicht. Richtig ist 4. - -> Außerdem fahre ich bald nach Mallorca, -> soll ich dir was mitbringen? - -Ich hätte gerne einen Bierkrug. - +Lieber Oskar, + +Oskar schrieb: +> 2 + 2 = 5 + +das stimmt doch gar +nicht. Richtig ist 4. + +> Außerdem fahre ich bald nach Mallorca, +> soll ich dir was mitbringen? + +Ich hätte gerne einen Bierkrug. + Gruß Max ``` @@ -134,16 +133,16 @@ Auch Weiterleitungen sind ein wichtiger Bestandteil des E-Mail-Systems. Bekommt Jedoch sollte man darauf achten, es dem Empfänger so einfach wie möglich zu machen. Einfach nur Weiterleiten ist nicht gern gesehen, man sollte auch eine grobe Zusammenfassung hinzufügen, um was es denn überhaupt geht. In dem konkreten Beispiel sollte man also vorweg schreiben: ``` -Hallo Peter, - -anbei eine Einladung zu einem interessanten Vortrag über die Geschichte der E-Mail. Er findet nächste Woche statt und ich würde mich freuen, wenn Du auch dabei wärst. Lies Dir doch die Einladung durch und sag mir Bescheid. - -Gruß -Julian - ------ Weitergeleitete Nachricht ----- -... -... +Hallo Peter, + +anbei eine Einladung zu einem interessanten Vortrag über die Geschichte der E-Mail. Er findet nächste Woche statt und ich würde mich freuen, wenn Du auch dabei wärst. Lies Dir doch die Einladung durch und sag mir Bescheid. + +Gruß +Julian + +----- Weitergeleitete Nachricht ----- +... +... ``` ## Fazit diff --git a/content/blog/2014-09-birthday-calendar-with-owncloud-via-caldav.md b/content/blog/2014-09-birthday-calendar-with-owncloud-via-caldav.md index 5a86049..e01b6d3 100644 --- a/content/blog/2014-09-birthday-calendar-with-owncloud-via-caldav.md +++ b/content/blog/2014-09-birthday-calendar-with-owncloud-via-caldav.md @@ -3,12 +3,11 @@ title: Birthday Calendar with ownCloud via CalDAV date: 2014-09-17T22:56:46+00:00 aliases: birthday-calendar-with-owncloud-via-caldav categories: + - blog - english tags: - - email - - guide - - server - - tools + - Communication + - SystemAdministration --- diff --git a/content/blog/2014-09-setting-openstreetmap-as-default-in-thunderbird-contacts.md b/content/blog/2014-09-setting-openstreetmap-as-default-in-thunderbird-contacts.md index c8a50bb..90139a5 100644 --- a/content/blog/2014-09-setting-openstreetmap-as-default-in-thunderbird-contacts.md +++ b/content/blog/2014-09-setting-openstreetmap-as-default-in-thunderbird-contacts.md @@ -3,11 +3,10 @@ title: Setting Openstreetmap as default in Thunderbird’s contacts date: 2014-09-28T10:40:42+00:00 aliases: setting-openstreetmap-as-default-in-thunderbird-contacts categories: + - blog - english tags: - - email - - guide - - tools + - Communication --- If you use Thunderbird and its contact functionality, you might already have stumbled over the „show on map“ feature. If you add addresses to your contacts (no matter if directly in Thunderbird or via CalDAV) there appears a button which enabled you to open a map with the contact’s location. diff --git a/content/blog/2014-10-my-internship-at-fsfe.md b/content/blog/2014-10-my-internship-at-fsfe.md index 9130a8d..a44715c 100644 --- a/content/blog/2014-10-my-internship-at-fsfe.md +++ b/content/blog/2014-10-my-internship-at-fsfe.md @@ -3,14 +3,13 @@ title: My internship at FSFE date: 2014-10-24T10:39:54+00:00 aliases: my-internship-at-fsfe categories: + - blog - english tags: - - routerfreedom - - fsfe - - report - - germany - - ilovefs - - policy + - RouterFreedom + - FSFE + - ILoveFS + - Policy --- I recently saw that the Free Software Foundation Europe is offering [a new and very interesting internship position](https://fsfe.org/news/2014/news-20141017-01.html). That’s a great opportunity for every student interested in Free Software and political activism — and for me to write about my internship I completed from October 2013 until end of March 2014. Here’s a report I wrote some time ago: diff --git a/content/blog/2014-11-freie-kommunikation-ist-essenz-des-lebens.md b/content/blog/2014-11-freie-kommunikation-ist-essenz-des-lebens.md index bde2660..5094499 100644 --- a/content/blog/2014-11-freie-kommunikation-ist-essenz-des-lebens.md +++ b/content/blog/2014-11-freie-kommunikation-ist-essenz-des-lebens.md @@ -3,11 +3,12 @@ title: Freie Kommunikation ist die Essenz des Menschseins date: 2014-11-10T13:15:19+00:00 aliases: freie-kommunikation-ist-essenz-des-lebens categories: + - blog - deutsch tags: - - chat - - security - - policy + - Communication + - Security + - Policy --- *Im Folgenden werde ich – durch meinen Gemütszustand etwas angefeuert – darlegen, wieso digitale Kommunikationsüberwachung Gift für unsere Gesellschaft ist, weil sie nichts anderes als Millionen Abhörwanzen und Kameras in unseren privatesten Räumen ist.* diff --git a/content/blog/2014-11-sharing-is-caring-my-git-instance.md b/content/blog/2014-11-sharing-is-caring-my-git-instance.md index e50f907..978460a 100644 --- a/content/blog/2014-11-sharing-is-caring-my-git-instance.md +++ b/content/blog/2014-11-sharing-is-caring-my-git-instance.md @@ -3,18 +3,18 @@ title: Sharing is caring – my Git instance date: 2014-11-28T17:16:50+00:00 aliases: sharing-is-caring-my-git-instance categories: + - blog - english tags: - - server - - tools + - SystemAdministration --- Some days ago I noticed another time that I have far too little knowledge about Git. - + „Time to change that!“, I thought and set up [my own Git instance][1] and also installed gitweb for better usability. Upside 1: I can keep track of the many (mainly bash) scripts I wrote in the past and all the changes I will adopt in the future. - + Upside 2: You can hopefully benefit from using and reading my code. All code is licensed under GNU GPL v3 so please feel free to use, study, share and improve my work! Some noteworthy projects I’m (a bit) proud of: @@ -27,7 +27,7 @@ Some noteworthy projects I’m (a bit) proud of: Any questions, ideas or improvements? Please contact me! ### Update 26.02.2016 - + I washed away the quite basic gitweb instance and moved to Gogs. Here’s [why and how][6]. Links to the project may have changed because of that (and I’m too lazy to change them here). [1]: https://src.mehl.mx diff --git a/content/blog/2015-01-next-station-tanzania.md b/content/blog/2015-01-next-station-tanzania.md index c60dda6..8d54522 100644 --- a/content/blog/2015-01-next-station-tanzania.md +++ b/content/blog/2015-01-next-station-tanzania.md @@ -5,9 +5,10 @@ aliases: - next-station-tanzania - naechste-station-tansania categories: + - blog - english tags: - - tanzania + - Tanzania --- diff --git a/content/blog/2015-01-yourls-url-shortener-for-turpial.md b/content/blog/2015-01-yourls-url-shortener-for-turpial.md index 31ee924..b65fac2 100644 --- a/content/blog/2015-01-yourls-url-shortener-for-turpial.md +++ b/content/blog/2015-01-yourls-url-shortener-for-turpial.md @@ -3,10 +3,11 @@ title: Yourls URL Shortener for Turpial date: 2015-01-24T01:58:32+00:00 aliases: yourls-url-shortener-for-turpial categories: + - blog - english tags: - - chat - - server + - Communication + - SystemAdministration --- Maybe you know [Yourls][1], a pretty cool URL shortener which you can set up on your own server very easily. Link shorteners are nice to have because @@ -21,19 +22,19 @@ And maybe you also know [Turpial][2], a Twitter client for GNU/Linux systems (I Turpial already offers some link shorteners but not Yourls. But we can add it manually. To do so, open the file `/usr/lib/python2.7/dist-packages/libturpial/lib/services/url/shortypython/shorty.py` as root. Now add the following somewhere between the already existing shorteners ```py -# Yourls -class Yourls(Service): - - def shrink(self, bigurl): - resp = request('http://YOUR_DOMAIN/yourls-api.php', {'action': 'shorturl', 'format': 'xml', 'url': bigurl, 'signature': 'YOUR_SIGNATURE'}) - returned_data = resp.read() - matched_re = re.search('(http://YOUR_DOMAIN/[^"]+)', returned_data) - if matched_re: - return matched_re.group(1) - else: - raise ShortyError('Failed to shrink url') - -yourls = Yourls() +# Yourls +class Yourls(Service): + + def shrink(self, bigurl): + resp = request('http://YOUR_DOMAIN/yourls-api.php', {'action': 'shorturl', 'format': 'xml', 'url': bigurl, 'signature': 'YOUR_SIGNATURE'}) + returned_data = resp.read() + matched_re = re.search('(http://YOUR_DOMAIN/[^"]+)', returned_data) + if matched_re: + return matched_re.group(1) + else: + raise ShortyError('Failed to shrink url') + +yourls = Yourls() ``` Just replace `YOUR_DOMAIN` and `YOUR_SIGNATURE` accordingly. The usage of a signature enables you to hide your username and password when sending the shorten requests, like an API key and looks like `f51qw35w6` ([more about passwordlessAPI][4]). You can retrieve your signature on your Yourls‘ Admin page via *Tools*. diff --git a/content/blog/2015-02-i-love-taskwarrior-therefore-i-love-free-software.md b/content/blog/2015-02-i-love-taskwarrior-therefore-i-love-free-software.md index 2072a89..83dd078 100644 --- a/content/blog/2015-02-i-love-taskwarrior-therefore-i-love-free-software.md +++ b/content/blog/2015-02-i-love-taskwarrior-therefore-i-love-free-software.md @@ -3,14 +3,13 @@ title: I love Taskwarrior, therefore I love Free Software date: 2015-02-14T12:05:42+00:00 aliases: i-love-taskwarrior-therefore-i-love-free-software categories: + - blog - english tags: - - bash - - fsfe - - guide - - server - - tools - - ilovefs + - Code + - FSFE + - SystemAdministration + - ILoveFS --- diff --git a/content/blog/2015-02-in-the-end-freedom-is-what-matters.md b/content/blog/2015-02-in-the-end-freedom-is-what-matters.md index f10ab61..d095b94 100644 --- a/content/blog/2015-02-in-the-end-freedom-is-what-matters.md +++ b/content/blog/2015-02-in-the-end-freedom-is-what-matters.md @@ -3,12 +3,13 @@ title: In The End Freedom Is What Matters date: 2015-02-25T02:03:04+00:00 aliases: in-the-end-freedom-is-what-matters categories: + - blog - english tags: - - routerfreedom - - fsfe - - policy - - security + - RouterFreedom + - FSFE + - Policy + - Security --- Yesterday I’ve been asked by a good friend of mine why I am investing so much time in the [FSFE](https://fsfe.org) (Free Software¹ Foundation Europe) instead of putting more energy in other organisations with more focus on privacy issues. The background of his question is that I’m quite concerned about governmental and commercial surveillance and the lack of really private ways to communicate with each other and the impact this has on our online and offline behaviour. With Laura Poitras‘ recent movie „Citizenfour“ awarded with an Oscar, I use the media attention as an icebreaker to talk with my friends about these topics if the situation allows it. @@ -24,5 +25,5 @@ In these cases **software privacy is of little use**. It’s about regulations, This, dear friend, is the reason why I volunteer for the FSFE – and therefore also for privacy. --- - + ¹ Means software which you are allowed to use for every purpose, which everybody can inspect, modify and redistribute diff --git a/content/blog/2015-04-erste-eindruecke-aus-tansania.md b/content/blog/2015-04-erste-eindruecke-aus-tansania.md index 2ee946b..b8c3409 100644 --- a/content/blog/2015-04-erste-eindruecke-aus-tansania.md +++ b/content/blog/2015-04-erste-eindruecke-aus-tansania.md @@ -3,9 +3,10 @@ title: Erste Eindrücke aus Tansania date: 2015-04-14T08:05:07+00:00 aliases: erste-eindruecke-aus-tansania categories: + - blog - deutsch tags: - - tanzania + - Tanzania --- Pole pole – das ist die typisch tansanische Mentalität, alles etwas ruhiger und langsamer angehen zu lassen. Und wahrscheinlich ist das auch der Grund, warum ich erst einen Monat nach meiner Ankunft in Tansania dazu komme, einen ersten Blogeintrag über meine bisherigen Erfahrungen zu schreiben. Ich bin hier von Anfang März bis Ende Juli als Freiwilliger in einer Organisation tätig, die die Bildung von jungen Menschen und der ländlichen Bevölkerung durch Einsatz und Schulung von IT verbessern will. Im Folgenden möchte ich kurz einen Rundumblick über mein Leben hier und die Bedingungen geben, konkret über meinen Alltag, die Gefahren, meine Arbeit als Freiwilliger, die einheimische Bevölkerung und Kultur, Wetter und Natur sowie das liebe Geld: diff --git a/content/blog/2015-05-naechster-halt-endstation.md b/content/blog/2015-05-naechster-halt-endstation.md index a5c144d..13853be 100644 --- a/content/blog/2015-05-naechster-halt-endstation.md +++ b/content/blog/2015-05-naechster-halt-endstation.md @@ -3,12 +3,13 @@ title: 'Nächster Halt: Endstation.' date: 2015-05-20T08:04:10+00:00 aliases: naechster-halt-endstation categories: + - blog - deutsch tags: - - germany - - policy - - tanzania -headerimage: /blog/weselsky-putin.jpg + - Policy + - Tanzania +headerimage: + src: /blog/weselsky-putin.jpg --- diff --git a/content/blog/2015-05-technology-and-free-software-in-tz.md b/content/blog/2015-05-technology-and-free-software-in-tz.md index b6761f3..e9522e4 100644 --- a/content/blog/2015-05-technology-and-free-software-in-tz.md +++ b/content/blog/2015-05-technology-and-free-software-in-tz.md @@ -3,10 +3,11 @@ title: Technology and Free Software in Tanzania date: 2015-05-08T07:34:19+00:00 aliases: technology-and-free-software-in-tz categories: + - blog - english tags: - - tanzania - - policy + - Tanzania + - Policy --- @@ -39,7 +40,7 @@ However, I was able to convince my students that in the case of Free Software mo ## Misconception III I’ve been tinkering with computers and software since my youth when I reinstalled my operating systems at least once a month and started exploring the internet. I did this because I was interested in technology and wanted to explore its and my limits, but also because even back then I knew that IT will become more and more important and those who don’t understand it will rather be left behind. - + I thought in Tanzania it’s a similar situation but somehow easier for the population. I thought that they have very limited technology here but that they know about the importance of computers and software in the industrial countries – and it’s quite obvious that with several years delay they will reach the same level of IT-dependency than we have today. So I thought the people here would care about technology and will try to learn as much as possible about it to improve their career chances and catch up the industrial countries. ## Reality III diff --git a/content/blog/2015-06-splitdl-downloading-huge-files-from-slow-and-unstable-internet-connections.md b/content/blog/2015-06-splitdl-downloading-huge-files-from-slow-and-unstable-internet-connections.md index 73b0f69..184b5d9 100644 --- a/content/blog/2015-06-splitdl-downloading-huge-files-from-slow-and-unstable-internet-connections.md +++ b/content/blog/2015-06-splitdl-downloading-huge-files-from-slow-and-unstable-internet-connections.md @@ -3,13 +3,12 @@ title: splitDL – Downloading huge files from slow and unstable internet connec date: 2015-06-26T15:59:03+00:00 aliases: splitdl-downloading-huge-files-from-slow-and-unstable-internet-connections categories: + - blog - english tags: - - bash - - guide - - server - - tanzania - - tools + - Code + - SystemAdministration + - Tanzania --- Imagine you want install GNU/Linux but your bandwidth won’t let you… diff --git a/content/blog/2015-07-weiterer-teilerfolg-beim-routerzwang.md b/content/blog/2015-07-weiterer-teilerfolg-beim-routerzwang.md index dad8b70..9329fcb 100644 --- a/content/blog/2015-07-weiterer-teilerfolg-beim-routerzwang.md +++ b/content/blog/2015-07-weiterer-teilerfolg-beim-routerzwang.md @@ -3,12 +3,12 @@ title: Weiterer Teilerfolg beim Routerzwang date: 2015-07-22T06:48:01+00:00 aliases: weiterer-teilerfolg-beim-routerzwang categories: + - blog - deutsch tags: - - routerfreedom - - fsfe - - germany - - policy + - RouterFreedom + - FSFE + - Policy --- @@ -19,7 +19,7 @@ Die [Free Software Foundation Europe][1] und alle Freunde Freier Software, Verbr > **Kurzinfo: Was ist Routerzwang?** > > In unserer Gesellschaft sollte es selbstverständlich sein, sich für technische Geräte frei entscheiden zu können, die man in seinem Zuhause in Betrieb nehmen möchte, genauso wie wir entscheiden können, welches Mobiltelefon wir kaufen. Doch einige Internetanbieter widersprechen diesem Prinzip und schreiben ihren Kunden vor, welches Gerät sie zur Einwahl in das Internet nutzen müssen oder diskriminieren Besitzer alternativer Geräte. Diese Verletzung eigentlich selbstverständlicher Rechte wird Routerzwang genannt und wird von der Free Software Foundation Europe und vielen anderen Organisationen, Projekten und Individuen stark kritisiert. Routerzwang ist nicht nur ein Thema für Technikexperten, sondern betrifft uns alle. -> +> > Routerzwang beschäftigt die FSFE [seit dem Januar 2013][2], die öffentlich in vielen Anhörungen und im Hintergrund Stellung bezogen hat. Mehr Informationen über das Thema auf [unserer ausführlichen Übersichtsseite][3]. Passend zum Ende dieser Phase hat der Journalist Jan Rähm für den Deutschlandfunk einen Beitrag gesendet, der das Thema sehr differenziert betrachtet, den aktuellen Stand darlegt und sowohl Gegner als auch Befürworter des Routerzwangs zu Wort kommen lässt. Der Beitrag ist als [verkürzte Textversion][4] und in der [vollen Audioversion][5] (5:48) auf der Webseite des Deutschlandfunks zu finden. So sagt etwa der Pressesprecher von Tele Columbus, einer der wenigen Befürworter des Routerzwangs: diff --git a/content/blog/2015-08-netzpolitik-routerzwang-endgeraetefreiheit/index.md b/content/blog/2015-08-netzpolitik-routerzwang-endgeraetefreiheit/index.md new file mode 100644 index 0000000..2b9c4f4 --- /dev/null +++ b/content/blog/2015-08-netzpolitik-routerzwang-endgeraetefreiheit/index.md @@ -0,0 +1,28 @@ +--- +title: "Der lange Weg des Routerzwangs zur Endgerätefreiheit" +date: 2015-08-27 +categories: + - deutsch + - article +tags: + - RouterFreedom + - Policy + - FSFE +headerimage: + src: routercat.jpg + text: Bild via maxguru.blogspot.de + processes: + - fill 1000x440 bottom webp +summary: In einem Gastbeitrag für Netzpolitik.org dokumentiere ich den jahrelangen Kampf gegen den Routerzwang und den nahenden Erfolg für die Endgerätefreiheit. Seit Anfang 2013 begleite ich als Koordinator des deutschen FSFE-Teams die Auseinandersetzung um die freie Routerwahl, die enorme Auswirkungen auf Privatsphäre, Sicherheit und Wettbewerb hat. Der Artikel zeichnet nach, wie das Bundesministerium für Wirtschaft und Energie Ende 2014 die Sache von der zögerlichen Bundesnetzagentur übernahm und einen zufriedenstellenden Gesetzentwurf vorlegte, der nun auf die Zustimmung von Bundesrat und Bundestag wartet. +article: + name: Netzpolitik.org + href: https://netzpolitik.org/2015/der-lange-weg-des-routerzwangs-zur-endgeraetefreiheit/ +--- + +In einem Gastbeitrag für Netzpolitik.org dokumentiere ich den jahrelangen Kampf gegen den Routerzwang und den nahenden Erfolg für die Endgerätefreiheit. Seit Anfang 2013 begleite ich als Koordinator des deutschen FSFE-Teams die Auseinandersetzung um die freie Routerwahl, die enorme Auswirkungen auf Privatsphäre, Sicherheit und Wettbewerb hat. Der Artikel zeichnet nach, wie das Bundesministerium für Wirtschaft und Energie Ende 2014 die Sache von der zögerlichen Bundesnetzagentur übernahm und einen zufriedenstellenden Gesetzentwurf vorlegte, der nun auf die Zustimmung von Bundesrat und Bundestag wartet. + +Der Beitrag erklärt die Bedeutung des passiven Netzabschlusspunkts, die geplante Verpflichtung zur Herausgabe von Zugangsdaten und das vorgesehene Bußgeld von 10.000 Euro bei Verstößen. Zudem rufe ich dazu auf, Volksvertreter zu kontaktieren, damit das Gesetz ohne weitere Einschränkungen verabschiedet wird, um das Minimum an Endgerätefreiheit, Verbraucherschutz und Sicherheit zu sichern. Doch der Weg ist noch nicht zu Ende: + +> Doch auch danach wird es spannend. Stellen sich Internetanbieter bei der Verwendung eigener Geräte im Support quer? Können alle Geräte problemlos an alternativen Routern eingesetzt werden? Findet trotz Gesetz eine Diskriminierung irgendeiner Art statt? Ja, wir können uns über die bisherigen Erfolge freuen. Doch in diesem Thema steckt zu viel Geld, als dass wir uns in trügerischer Sicherheit wiegen dürften. + +Der [vollständige Gastbeitrag](https://netzpolitik.org/2015/der-lange-weg-des-routerzwangs-zur-endgeraetefreiheit/) ist auf Netzpolitik.org verfügbar. diff --git a/content/blog/2015-08-netzpolitik-routerzwang-endgeraetefreiheit/routercat.jpg b/content/blog/2015-08-netzpolitik-routerzwang-endgeraetefreiheit/routercat.jpg new file mode 100644 index 0000000..e39341c Binary files /dev/null and b/content/blog/2015-08-netzpolitik-routerzwang-endgeraetefreiheit/routercat.jpg differ diff --git a/content/blog/2015-09-german-government-wants-authorities-to-advertise-pdfreaders.md b/content/blog/2015-09-german-government-wants-authorities-to-advertise-pdfreaders.md index ef52523..59e921a 100644 --- a/content/blog/2015-09-german-government-wants-authorities-to-advertise-pdfreaders.md +++ b/content/blog/2015-09-german-government-wants-authorities-to-advertise-pdfreaders.md @@ -3,11 +3,11 @@ title: German Government wants authorities to advertise PDFreaders date: 2015-09-19T17:27:20+00:00 aliases: german-government-wants-authorities-to-advertise-pdfreaders categories: + - blog - english tags: - - fsfe - - germany - - policy + - FSFE + - Policy --- diff --git a/content/blog/2015-10-ct-sony-rootkit-kommentar/index.md b/content/blog/2015-10-ct-sony-rootkit-kommentar/index.md new file mode 100644 index 0000000..cb64771 --- /dev/null +++ b/content/blog/2015-10-ct-sony-rootkit-kommentar/index.md @@ -0,0 +1,29 @@ +--- +title: "Kommentar: 10 Jahre Sony-Rootkit – Why we should care (c't magazin)" +date: 2015-10-31 +categories: + - deutsch + - article +tags: + - DRM + - Security + - FSFE + - Privacy +# headerimage: +# src: foo.jpg +# text: bar +summary: Im c't magazin veröffentlichte ich einen Kommentar zum 10. Jahrestag des Sony-Rootkit-Skandals. Ich argumentiere, dass Digital Rights Management (DRM) nicht aus der Welt ist und seine langfristigen Folgen unsere Gesellschaft vor immense Probleme stellen – von verlorener Innovation über eingeschränkte Nutzerrechte bis zur Kriminalisierung hunderttausender Menschen. +article: + name: c't magazin + href: https://www.heise.de/ct/artikel/Kommentar-10-Jahre-Sony-Rootkit-Why-we-should-care-2865608.html +--- + +In meinem Kommentar zum 10. Jahrestag des Sony-Rootkit-Skandals warne ich vor den anhaltenden Gefahren durch Digitale Rechteminderung (DRM). Zehn Jahre nach dem Skandal, bei dem Sony Käufer:innen von Musik-CDs eine Schadsoftware unterjubelte, stehen wir heute vor wählerischen Kaffeemaschinen, spionierenden E-Book-Readern und Autos, die nur Ersatzteile bestimmter Hersteller akzeptieren. + +> Schlimmer noch ist aber der Verlust an Innovationspotenzial, den wir durch jedes weitere Produkt mit eingebauter Rechteminderung erleiden. Software oder Hardware der Zukunft wird immer auf der Benutzung und Modifikation der Geräte der Gegenwart aufbauen. Computer, in all ihren Erscheinungsformen, sind dabei die wichtigsten Geräte. Wenn diese essentiellen Werkzeuge künstlich beschränkt werden, schrumpfen die Möglichkeiten, mit ihnen Innovationen zu produzieren. Und anstatt Bestehendes weiterzuentwickeln, können wir es oft nicht einmal mehr selbst abändern oder reparieren. + +Ich fordere ein positives "Right to Tinker" – ein Recht auf uneingeschränkte Nutzung, Modifikation und Experimentieren mit allen Geräten, die wir kaufen: + +> Wir benötigen also ein positives Recht auf uneingeschränkte Nutzung, Modifikation und Experimentieren mit allen Geräten, die wir kaufen ("Right to Tinker"). Uns müssen die Geräte auch tatsächlich gehören, die wir erworben haben. Das wird noch elementarer in Hinsicht auf das aufblühende Internet der Dinge, in dem noch viel mehr Computer um uns herum sein werden. Ob sie dann unsere Werkzeuge für Innovation sein werden oder solche zu unserer Einschränkung, müssen wir bald entscheiden. (mho) + +Der [vollständige Kommentar](https://www.heise.de/hintergrund/Kommentar-10-Jahre-Sony-Rootkit-Noch-viel-zu-tun-2865608.html) mit weiteren Details zu den gesellschaftlichen Folgen von DRM ist im c't magazin verfügbar. diff --git a/content/blog/2015-10-heise-sony-rootkit-schadsoftware/broken-cd.webp b/content/blog/2015-10-heise-sony-rootkit-schadsoftware/broken-cd.webp new file mode 100644 index 0000000..e5d0a26 Binary files /dev/null and b/content/blog/2015-10-heise-sony-rootkit-schadsoftware/broken-cd.webp differ diff --git a/content/blog/2015-10-heise-sony-rootkit-schadsoftware/index.md b/content/blog/2015-10-heise-sony-rootkit-schadsoftware/index.md new file mode 100644 index 0000000..9b56db8 --- /dev/null +++ b/content/blog/2015-10-heise-sony-rootkit-schadsoftware/index.md @@ -0,0 +1,28 @@ +--- +title: "10 Jahre Sony-Rootkit: Schadsoftware vom Hersteller (heise online)" +date: 2015-10-31 +categories: + - deutsch + - article +tags: + - DRM + - Security + - FSFE + - Privacy +headerimage: + src: broken-cd.webp +summary: Auf heise online veröffentlichte ich einen Artikel zum 10. Jahrestag des Sony-Rootkit-Skandals. Ich schildere, wie Sony mit einem Kopierschutz-Rootkit etwa 22 Millionen Computer infizierte – darunter auch militärische Systeme – und dabei massive Sicherheitslücken aufriss, Datenverluste verursachte und Nutzer:innen ihrer Kontrolle beraubte. +article: + name: heise online + href: https://www.heise.de/newsticker/meldung/10-Jahre-Sony-Rootkit-Schadsoftware-vom-Hersteller-2865426.html +--- + +In meinem Artikel auf heise online erinnere ich an den bahnbrechenden Sony-Rootkit-Skandal von 2005. Vor zehn Jahren entdeckte Sicherheitsforscher Mark Russinovich zufällig, dass gekaufte Musik-CDs von Sony heimlich ein Schadprogramm auf Computern installierten. Das Extended Copy Protection-Rootkit sollte Kopiervorgänge verhindern, verursachte aber massive Probleme: + +> Doch durch den unsauber programmierten Treiber beklagten zahlreiche Käufer Datenverluste, Systemabstürze oder Performanceprobleme. Das Rootkit ließ sich nicht einfach deinstallieren. Löschte man die zugehörigen Dateien, sorgten veränderte Registrierungsschlüssel dafür, dass das CD-Laufwerk des Computers unbenutzbar wurde. + +Die Dimension des Skandals war enorm: + +> Etwa 22 Millionen Computer wurden von dieser bösartigen Software infiziert, darunter auch Tausende in militärischen Einrichtungen. Das bedeutete teilweise eine immense Gefahr, da die Software anderer Malware auf dem System ermöglichte, sich besser vor Virenscannern zu verstecken. Erst nach einigem Hin und Her und wegen des wachsenden Drucks bot Sony knapp zwei Monate später ein funktionierendes Removal Tool an und rief die CDs zurück. Etwas vergleichbares hat sich ein Unternehmen seitdem nicht mehr getraut. + +Der [vollständige Artikel](http://www.heise.de/newsticker/meldung/10-Jahre-Sony-Rootkit-Schadsoftware-vom-Hersteller-2865426.html) mit technischen Details zum Rootkit ist auf heise online verfügbar. diff --git a/content/blog/2016-02-i-love-free-software-apps.md b/content/blog/2016-02-i-love-free-software-apps.md index 636bb93..133692e 100644 --- a/content/blog/2016-02-i-love-free-software-apps.md +++ b/content/blog/2016-02-i-love-free-software-apps.md @@ -3,11 +3,12 @@ title: I love Free Software (Apps) date: 2016-02-14T09:00:18+00:00 aliases: i-love-free-software-apps categories: + - blog - english tags: - - chat - - ilovefs - - security + - Communication + - ILoveFS + - Security --- Do you know being in a restaurant and getting a menu which is longer than the average novel, and you cannot decide for a single meal because every single one sounds more delicious than the other? That’s similar to the problem I was having when writing this blog post… diff --git a/content/blog/2016-02-switching-my-code-from-gitweb-to-gogs.md b/content/blog/2016-02-switching-my-code-from-gitweb-to-gogs.md index 722c5b3..3e98e4b 100644 --- a/content/blog/2016-02-switching-my-code-from-gitweb-to-gogs.md +++ b/content/blog/2016-02-switching-my-code-from-gitweb-to-gogs.md @@ -3,10 +3,9 @@ title: Switching my code from gitweb to Gogs date: 2016-02-26T17:05:18+00:00 aliases: switching-my-code-from-gitweb-to-gogs categories: + - blog - english tags: - - tools - - guide --- diff --git a/content/blog/2016-03-chemnitzer-linuxtage-router-freedom/clt-2026.jpg b/content/blog/2016-03-chemnitzer-linuxtage-router-freedom/clt-2026.jpg new file mode 100644 index 0000000..5b51198 Binary files /dev/null and b/content/blog/2016-03-chemnitzer-linuxtage-router-freedom/clt-2026.jpg differ diff --git a/content/blog/2016-03-chemnitzer-linuxtage-router-freedom/index.md b/content/blog/2016-03-chemnitzer-linuxtage-router-freedom/index.md new file mode 100644 index 0000000..215a842 --- /dev/null +++ b/content/blog/2016-03-chemnitzer-linuxtage-router-freedom/index.md @@ -0,0 +1,24 @@ +--- +title: "Routerzwang und was Aktivisten daraus lernen können" +date: 2016-03-19 +categories: + - deutsch + - presentation +tags: + - RouterFreedom + - Policy + - FSFE +headerimage: + src: clt-2026.jpg + text: Foto von der Präsentation bei den Chemnitzer Linuxtagen 2016 +video: https://www.youtube.com/watch?v=P5EMZ8VFuME +event: + name: Chemnitzer Linuxtage 2016 + href: https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/177 +--- + +Bei den Chemnitzer Linuxtagen 2016 hielt ich einen Vortrag über die Routerzwang-Kampagne und die Lektionen, die Aktivisten daraus ziehen können. Zu diesem Zeitpunkt war der Kampf um Router-Freiheit in Deutschland noch in vollem Gange, aber erfolgversprechend – ein guter Moment, um sowohl über den bisherigen Verlauf zu berichten als auch über die Strategien, die sich als erfolgreich erwiesen hatten. Die Chemnitzer Linuxtage ziehen ein technisch versiertes Publikum an, das oft frustriert ist über politische Prozesse, aber auch das Potenzial hat, diese zu beeinflussen. + +Der Vortrag erklärte zunächst das Problem: Telekommunikationsanbieter zwangen Kunden, deren Router zu nutzen, was technische Einschränkungen, Sicherheitsrisiken und Lock-in bedeutete. Ich zeigte dann, wie es der FSFE und Partnern gelang, dieses Thema auf die politische Agenda zu bringen: durch technische Dokumentation der Probleme, Mobilisierung betroffener Nutzer, Zusammenarbeit mit Verbraucherschutzorganisationen, und direkte Arbeit mit Gesetzgebern. Besonders wichtig war die Erkenntnis, dass man nicht nur protestieren, sondern konkrete Lösungsvorschläge und Gesetzestexte liefern muss. + +Die Präsentation diente als Ermutigung für technische Communities, sich politisch einzumischen. Die Diskussion konzentrierte sich auf praktische Fragen: Wie findet man Zeit für Aktivismus neben Beruf und Familie? Wie arbeitet man mit Politikern zusammen, die die technischen Details nicht verstehen? Wie baut man Koalitionen mit Nicht-Tech-Organisationen? Der Vortrag zeigte, dass effektiver Technik-Aktivismus möglich ist, wenn man strategisch vorgeht und die richtigen Verbündeten findet. diff --git a/content/blog/2016-03-dvtm-eu-radio-directive-threats/index.md b/content/blog/2016-03-dvtm-eu-radio-directive-threats/index.md new file mode 100644 index 0000000..d84ffb7 --- /dev/null +++ b/content/blog/2016-03-dvtm-eu-radio-directive-threats/index.md @@ -0,0 +1,21 @@ +--- +title: "EU Radio Directive threatens competition and user rights" +date: 2016-03-01 +categories: + - deutsch + - article +tags: + - RadioLockdown + - Policy + - FSFE +summary: Im Newsletter des DVTM (Deutscher Verband für Telekommunikation und Medien) erschien mein Artikel über die Bedrohung durch die EU-Funkanlagenrichtlinie. Ich analysiere, wie die Richtlinie nicht nur Wettbewerb und Innovation gefährdet, sondern auch fundamentale Nutzerrechte einschränkt und kleinere Unternehmen vom Markt ausschließen könnte. +article: + name: DVTM Newsletter + href: https://www.dvtm.net +--- + +In meinem Artikel für den DVTM-Newsletter warne ich vor den weitreichenden Folgen der EU-Funkanlagenrichtlinie (Radio Equipment Directive, RED) für Wettbewerb und Nutzerrechte. Die Richtlinie droht, etablierte Geschäftsmodelle zu zerstören und Innovation im Funkbereich massiv zu behindern. Besonders problematisch: Kleinere Hersteller und innovative Startups können sich die aufwendigen Zertifizierungsverfahren oft nicht leisten, was zu einer Marktkonsolidierung zugunsten großer Konzerne führen würde. Gleichzeitig werden Nutzer:innen ihrer Freiheit beraubt, eigene Software auf ihren Geräten zu installieren oder Sicherheitslücken selbst zu schließen. + +Ich betone, dass die Richtlinie auch die Telekommunikationsbranche direkt betrifft: Router-Hersteller, die auf offene Ökosysteme setzen, Anbieter von Netzwerklösungen und der gesamte Markt für Funkgeräte stehen vor existenziellen Herausforderungen. Die Kombination aus technischen Anforderungen und rechtlichen Unsicherheiten schafft ein Klima, das Innovation verhindert und den Wettbewerb zugunsten etablierter Anbieter verzerrt. Der Artikel verdeutlicht die Dringlichkeit, diese unverhältnismäßige Regulierung auf europäischer Ebene zu korrigieren. + +Der vollständige Artikel war im DVTM-Newsletter verfügbar. diff --git a/content/blog/2016-03-getting-oldschool-oder-wie-ich-uncool-wurde.md b/content/blog/2016-03-getting-oldschool-oder-wie-ich-uncool-wurde.md index 59106ec..0a25141 100644 --- a/content/blog/2016-03-getting-oldschool-oder-wie-ich-uncool-wurde.md +++ b/content/blog/2016-03-getting-oldschool-oder-wie-ich-uncool-wurde.md @@ -3,9 +3,10 @@ title: 'Getting oldschool, oder: Wie ich uncool wurde' date: 2016-03-28T13:39:45+00:00 aliases: getting-oldschool-oder-wie-ich-uncool-wurde categories: + - blog - deutsch tags: - - chat + - Communication --- diff --git a/content/blog/2016-07-cio-german-router-freedom-law/index.md b/content/blog/2016-07-cio-german-router-freedom-law/index.md new file mode 100644 index 0000000..badf530 --- /dev/null +++ b/content/blog/2016-07-cio-german-router-freedom-law/index.md @@ -0,0 +1,28 @@ +--- +title: "New law lets German internet users connect with their own routers (CIO.com)" +date: 2016-07-28 +categories: + - english + - article +tags: + - RouterFreedom + - Policy + - FSFE +# headerimage: +# src: foo.jpg +# text: bar +summary: CIO.com reported on Germany's landmark router freedom law that ended compulsory routers. I was quoted on the significance of this success after years of FSFE advocacy, explaining how users can now freely choose and configure their own network equipment – a major victory for consumer rights and digital autonomy. +article: + name: CIO.com + href: https://web.archive.org/web/20190613105440/https://www.cio.com/article/3101864/new-law-lets-german-internet-users-connect-with-their-own-routers.html +--- + +CIO.com covered the implementation of Germany's groundbreaking router freedom law, which ended the practice of internet service providers forcing customers to use specific routers. I was quoted on this milestone achievement after years of advocacy by the FSFE and coalition partners. The new law establishes clear rules: ISPs must provide connection credentials to customers, allowing them to use routers of their choice, while ISPs remain responsible for the connection up to the network termination point. + +I explained the broader implications beyond just router choice: + +> This is about control over your own equipment, security updates, privacy, and the ability to customize your home network according to your needs rather than your ISP's limitations. It sets an important precedent for consumer rights in the digital age. + +The law particularly benefits technically savvy users who want to run alternative firmware like OpenWrt, configure advanced security settings, or simply use more powerful hardware than ISPs typically provide. + +The [full article](https://web.archive.org/web/20190613105440/https://www.cio.com/article/3101864/new-law-lets-german-internet-users-connect-with-their-own-routers.html) with details on the law's implementation timeline and industry reactions is available on CIO.com. diff --git a/content/blog/2016-07-der-routerzwang-faellt-was-bringt-mir-das.md b/content/blog/2016-07-der-routerzwang-faellt-was-bringt-mir-das.md index 6fc2237..95c0ccf 100644 --- a/content/blog/2016-07-der-routerzwang-faellt-was-bringt-mir-das.md +++ b/content/blog/2016-07-der-routerzwang-faellt-was-bringt-mir-das.md @@ -3,12 +3,12 @@ title: Der Routerzwang fällt – Und was bringt mir das? date: 2016-07-30T11:02:38+00:00 aliases: der-routerzwang-faellt-was-bringt-mir-das categories: + - blog - deutsch tags: - - routerfreedom - - fsfe - - policy - - germany + - RouterFreedom + - FSFE + - Policy --- _Diesen Artikel habe ich ursprünglich als [Gastbeitrag für Netzpolitik.org][1] geschrieben._ diff --git a/content/blog/2016-07-sz-routerzwang-ende/index.md b/content/blog/2016-07-sz-routerzwang-ende/index.md new file mode 100644 index 0000000..f92a5f8 --- /dev/null +++ b/content/blog/2016-07-sz-routerzwang-ende/index.md @@ -0,0 +1,26 @@ +--- +title: "Der Routerzwang endet - was Internetnutzer jetzt wissen müssen (Süddeutsche Zeitung)" +date: 2016-07-28 +categories: + - deutsch + - article +tags: + - RouterFreedom + - Policy + - FSFE +headerimage: + src: router.jpg + text: "Foto: Frank Rumpenhorst/dpa, Quelle: Süddeutsche Zeitung" +summary: Die Süddeutsche Zeitung veröffentlichte einen umfassenden Artikel zum Ende des Routerzwangs, in dem ich mehrfach zitiert werde. Ich erkläre die Probleme mit den Zwangsroutern -- von schlechter technischer Umsetzung über fehlende Sicherheitsupdates bis zu mangelnden Funktionen -- und gebe praktische Hinweise für Nutzer:innen zur Umstellung. +article: + name: Süddeutsche Zeitung + href: https://www.sueddeutsche.de/wirtschaft/internet-der-routerzwang-endet-was-internetnutzer-jetzt-wissen-muessen-1.3095231 +--- + +In der Süddeutschen Zeitung erkläre ich im Rahmen eines umfassenden FAQ-Artikels die Hintergründe zum Ende des Routerzwangs ab 1. August 2016. Auf die Frage, warum freie Routerwahl besser ist, antwortete ich: + +> Es waren oft Geräte, die technisch schlecht umgesetzt waren und kaum Sicherheitsfunktionen hatten. Internetanbieter haben Sicherheits-Updates der Hersteller oft nicht sofort eingespielt. Und nicht alle Router erfüllen alle Funktionen, die Kunden gerne hätten. Gewisse Telefone oder Fernseher können nicht an die vorgegebenen Router angeschlossen werden, weil diese bestimmte Funktionen nicht haben. + +Für die praktische Umsetzung rate ich zur Vorsicht: "In der Umbruchszeit sollte man sich bei Kabelanschlüssen informieren, ob ein Routermodell für einen Kabelanbieter funktioniert." Um anderen Nutzer:innen bei der Umstellung zu helfen, sammle ich Erfahrungsberichte zu möglichen Schwierigkeiten in einem Wiki. Der Artikel erklärt auch wichtige Details für Bestandskund:innen, die Unterschiede zwischen Kabel- und DSL-Anbietern, sowie was zu tun ist, wenn Anbieter die Zugangsdaten nicht herausrücken wollen: Beschwerden bei der Bundesnetzagentur oder Verbraucherzentralen. + +Der [vollständige FAQ-Artikel](https://www.sueddeutsche.de/wirtschaft/internet-der-routerzwang-endet-was-internetnutzer-jetzt-wissen-muessen-1.3095231) mit allen Details zur rechtlichen Situation und praktischen Umsetzung ist in der Süddeutschen Zeitung verfügbar. diff --git a/content/blog/2016-07-sz-routerzwang-ende/router.jpg b/content/blog/2016-07-sz-routerzwang-ende/router.jpg new file mode 100644 index 0000000..7f7b485 Binary files /dev/null and b/content/blog/2016-07-sz-routerzwang-ende/router.jpg differ diff --git a/content/blog/2016-08-erste-testgeraete-fuer-routerfreiheit-versendet.md b/content/blog/2016-08-erste-testgeraete-fuer-routerfreiheit-versendet.md index 01b0c2c..17cdc82 100644 --- a/content/blog/2016-08-erste-testgeraete-fuer-routerfreiheit-versendet.md +++ b/content/blog/2016-08-erste-testgeraete-fuer-routerfreiheit-versendet.md @@ -3,12 +3,11 @@ title: Erste Testgeräte für Routerfreiheit versendet date: 2016-08-08T09:11:51+00:00 aliases: erste-testgeraete-fuer-routerfreiheit-versendet categories: + - blog - deutsch tags: - - routerfreedom - - fsfe - - germany - - guide + - RouterFreedom + - FSFE --- Wie Ihr vielleicht schon mitbekommen habt, ist am 1. August die Welt etwas freier geworden. Nun nämlich ist das [Gesetz für Endgerätefreiheit][1] in Kraft, welches endlich erlaubt, dass Kunden deutscher Internetanbieter einen Router oder ein Modem ihrer Wahl an ihren Anschluss klemmen dürfen. Die [FSFE][2] hat sich von Anfang an für dieses Recht eingesetzt und schlussendlich haben wir diesen großen Erfolg errungen, der den [Routerzwang][3] endgültig abschaffen soll. diff --git a/content/blog/2016-08-froscon-2016-ein-rueckblick.md b/content/blog/2016-08-froscon-2016-ein-rueckblick.md index ebb3f81..33f6e63 100644 --- a/content/blog/2016-08-froscon-2016-ein-rueckblick.md +++ b/content/blog/2016-08-froscon-2016-ein-rueckblick.md @@ -3,14 +3,13 @@ title: FrOSCon 2016 – Ein Rückblick date: 2016-08-26T13:57:48+00:00 aliases: froscon-2016-ein-rueckblick categories: + - blog - deutsch tags: - - routerfreedom - - report - - fsfe - - germany - - radiolockdown - - policy + - RouterFreedom + - FSFE + - RadioLockdown + - Policy --- _For English readers: This is a short report about the last FrOSCon conference with some pictures and the talk recordings. Have a look at Polina’s talk (second video), it’s in English!_ diff --git a/content/blog/2016-08-froscon-routers-radio-lockdown/froscon-2016.jpg b/content/blog/2016-08-froscon-routers-radio-lockdown/froscon-2016.jpg new file mode 100644 index 0000000..68cccd1 Binary files /dev/null and b/content/blog/2016-08-froscon-routers-radio-lockdown/froscon-2016.jpg differ diff --git a/content/blog/2016-08-froscon-routers-radio-lockdown/index.md b/content/blog/2016-08-froscon-routers-radio-lockdown/index.md new file mode 100644 index 0000000..9412735 --- /dev/null +++ b/content/blog/2016-08-froscon-routers-radio-lockdown/index.md @@ -0,0 +1,27 @@ +--- +title: "Routerzwang und Funkabschottung - Was Aktivisten daraus lernen können" +date: 2016-08-20 +categories: + - deutsch + - presentation +tags: + - RadioLockdown + - RouterFreedom + - Policy + - FSFE +headerimage: + src: froscon-2016.jpg + text: Foto von der Präsentation bei der FrOSCon 2016 + processes: + - fill 1000x440 center webp +video: https://www.youtube.com/watch?v=CdRQtaePiIs +event: + name: FrOSCon 2016 + href: https://programm.froscon.de/2016/events/1738.html +--- + +Bei der FrOSCon 2016 in Sankt Augustin präsentierte ich zwei Fallstudien digitalen Aktivismus: den erfolgreichen Kampf gegen den Routerzwang in Deutschland und die laufende Kampagne gegen die EU-Funkabschottungs-Richtlinie. Die FrOSCon (Free and Open Source Software Conference) bringt vorwiegend deutschsprachige Free-Software-Enthusiasten zusammen, die sowohl technisch versiert sind als auch ein Interesse an den politischen Rahmenbedingungen für Freie Software haben. + +Der Vortrag analysierte den Erfolg der Routerfreiheits-Kampagne: Trotz massiven Widerstands der Telekommunikationsbranche war es gelungen, ein Gesetz durchzusetzen, das Verbrauchern die freie Wahl ihres Routers garantiert. Ich zeigte auf, welche Strategien erfolgreich waren – von der Mobilisierung breiter Unterstützung über die Zusammenarbeit mit Verbraucherschützern bis hin zur Lieferung technischer Expertise für politische Entscheidungsträger. Diese Lektionen wandte ich dann auf die drohende Funkabschottung an: Eine EU-Richtlinie, die unter dem Vorwand der Frequenzregulierung zu einem Lockdown aller funkfähigen Geräte führen könnte. + +Die Präsentation war als Aktivismus-Leitfaden konzipiert: Sie zeigte nicht nur Probleme auf, sondern auch konkrete Wege, wie technische Communities politischen Einfluss nehmen können. Die Diskussion drehte sich um praktische Fragen: Wie findet man Verbündete außerhalb der Tech-Szene? Wie kommuniziert man technische Themen an Politiker? Wie baut man Druck auf, ohne in reinem Protest stecken zu bleiben? Für das FrOSCon-Publikum war dies eine Ermutigung, dass technischer Aktivismus Wirkung zeigen kann. diff --git a/content/blog/2016-08-netzpolitik-interview-freie-software-vorteile/fsfe-summit-banner.jpg b/content/blog/2016-08-netzpolitik-interview-freie-software-vorteile/fsfe-summit-banner.jpg new file mode 100644 index 0000000..36130f2 Binary files /dev/null and b/content/blog/2016-08-netzpolitik-interview-freie-software-vorteile/fsfe-summit-banner.jpg differ diff --git a/content/blog/2016-08-netzpolitik-interview-freie-software-vorteile/index.md b/content/blog/2016-08-netzpolitik-interview-freie-software-vorteile/index.md new file mode 100644 index 0000000..3bbadb0 --- /dev/null +++ b/content/blog/2016-08-netzpolitik-interview-freie-software-vorteile/index.md @@ -0,0 +1,32 @@ +--- +title: "Über die Vorteile von Freier Software und Tech-Konferenzen, die keine sind (Netzpolitik.org)" +date: 2016-08-08 +categories: + - deutsch + - article +tags: + - Community + - FSFE +headerimage: + src: fsfe-summit-banner.jpg + processes: + - fill 1000x440 left webp +summary: Netzpolitik.org veröffentlichte ein ausführliches Interview mit mir über Freie Software, Tech-Aktivismus und den FSFE Summit 2016. Ich erläutere, warum die Kontrolle über Technik immer brennender wird, wie Freie Software gerade Entwicklungsländern hilft, und warum eine nicht rein technische Konferenz zum 15-jährigen FSFE-Jubiläum genau richtig ist. +article: + name: Netzpolitik.org + href: https://netzpolitik.org/2016/interview-mit-max-mehl-ueber-die-vorteile-von-freier-software-und-tech-konferenzen-die-keine-sind/ +--- + +Im Interview mit Netzpolitik.org erkläre ich anlässlich des 15-jährigen FSFE-Jubiläums und des bevorstehenden FSFE Summit, warum Freie Software weit über technische Aspekte hinausgeht. Die drängendsten Themen sehe ich im Internet of Things – den vielen kleinen Geräten in unseren Wohnungen – und der Frage nach Kontrolle über unsere Daten. Zur Ausrichtung des Summit als "keine Tech-Konferenz" betone ich: + +> Es geht bei unserem Summit eher um die Gestaltung der Welt der Technik, nicht rein um Software an sich. [...] Wir arbeiten seit fünfzehn Jahren daran, die Bedingungen für Freie Software zu verbessern und damit elementare Rechte für alle Menschen in Europa zu schützen. + +Ich schilde außerdem meine Erfahrungen aus Tansania, wo ich die Vorteile von Freier Software für Entwicklungsländer kennengelernt habe: + +> Viele Lizenzkosten sind gerade für Bildungseinrichtungen in Entwicklungsländern exorbitant teuer. Der Vendor-Lock-in [...] versetzt Schulen gerne mal den finanziellen Todesstoß. Gleichzeitig ermöglicht Freie Software, dass etwa lokale Anbieter für ein Unternehmen oder eine Uni Anpassungen an der Software vornehmen können, und zwar in einem Finanzrahmen, der den dortigen Verhältnissen entspricht. + +Warum ich mich für Freie Software einsetze? + +> Ich habe gemerkt, dass Software ein elementarer Bestandteil unseres heutigen Lebens ist. [...] Dabei stellt sich mir die Frage, ob wir zulassen möchten, dass Software uns kontrolliert und nicht andersrum. + +Das [vollständige Interview](https://netzpolitik.org/2016/interview-mit-max-mehl-ueber-die-vorteile-von-freier-software-und-tech-konferenzen-die-keine-sind/) mit weiteren Details zur FSFE-Strategie, europäischem Aktivismus und dem Summit-Programm ist auf Netzpolitik.org verfügbar. diff --git a/content/blog/2016-09-deutschlandfunk-router-freedom/dlf-studio.jpg b/content/blog/2016-09-deutschlandfunk-router-freedom/dlf-studio.jpg new file mode 100644 index 0000000..5845d1f Binary files /dev/null and b/content/blog/2016-09-deutschlandfunk-router-freedom/dlf-studio.jpg differ diff --git a/content/blog/2016-09-deutschlandfunk-router-freedom/index.md b/content/blog/2016-09-deutschlandfunk-router-freedom/index.md new file mode 100644 index 0000000..00f847f --- /dev/null +++ b/content/blog/2016-09-deutschlandfunk-router-freedom/index.md @@ -0,0 +1,27 @@ +--- +title: "Schluss mit dem Routerzwang - Deutschlandfunk" +date: 2016-09-01 +categories: + - deutsch + - podcast +tags: + - RouterFreedom + - Policy + - FSFE +audio: https://up.mehl.mx/audio/20160901-dlf-routerzwang.ogg +summary: Im Deutschlandfunk-Magazin "Computer und Kommunikation" sprach ich über das Ende des Routerzwangs in Deutschland und was die neue Regelung für Verbraucher bedeutet. Nach jahrelangem Kampf war es gelungen, ein Gesetz durchzusetzen, das Kunden die freie Wahl ihres Routers garantiert – ein wichtiger Sieg für Verbraucherrechte und technische Selbstbestimmung. Der Deutschlandfunk erreicht ein breites, auch nicht-technisches Publikum, dem ich erklären konnte, warum dieses scheinbar technische Thema für jeden relevant ist. +headerimage: + src: dlf-studio.jpg + text: Die Gästerunde mit Moderator Stefan Römermann in der Sendung Marktplatz. (Deutschlandradio/ Stefan Römermann) + processes: + - fill 1000x440 top webp +event: + name: Deutschlandfunk Computer und Kommunikation + href: https://www.deutschlandfunk.de/dsl-modem-und-kabelrouter-schluss-mit-dem-routerzwang.772.de.html?dram:article_id=362214 +--- + +Im Deutschlandfunk-Magazin "Computer und Kommunikation" sprach ich über das Ende des Routerzwangs in Deutschland und was die neue Regelung für Verbraucher bedeutet. Nach jahrelangem Kampf war es gelungen, ein Gesetz durchzusetzen, das Kunden die freie Wahl ihres Routers garantiert – ein wichtiger Sieg für Verbraucherrechte und technische Selbstbestimmung. Der Deutschlandfunk erreicht ein breites, auch nicht-technisches Publikum, dem ich erklären konnte, warum dieses scheinbar technische Thema für jeden relevant ist. + +Ich erläuterte, warum Telekommunikationsanbieter jahrelang versucht hatten, Kunden auf ihre eigenen Router zu zwingen: Kontrolle über die Heimnetzwerke, zusätzliche Einnahmequellen durch Router-Miete, und die Möglichkeit, Features zu beschränken oder zu überwachen. Die neue Regelung bedeutete nicht nur mehr Auswahl, sondern auch bessere Sicherheit (weil Kunden Updates selbst kontrollieren können), mehr Funktionalität (durch Firmware wie OpenWRT), und echte Kontrolle über das eigene Netzwerk. Für technisch Versierte war das selbstverständlich – für viele Hörer war es eine Überraschung, dass sie bisher diese Freiheit nicht hatten. + +Das Interview half, ein komplexes technisches und rechtliches Thema einem Massenpublikum zugänglich zu machen und zu erklären, warum diese Regulierung ein Erfolg für digitale Selbstbestimmung war. Es zeigte auch, dass scheinbar aussichtslose Kämpfe gegen Telekommunikationsanbieter gewonnen werden können, wenn technische Expertise, Verbraucherinteressen und politischer Wille zusammenkommen. diff --git a/content/blog/2016-09-endgeraetefreiheit-testen-es-sind-wieder-router-verfuegbar.md b/content/blog/2016-09-endgeraetefreiheit-testen-es-sind-wieder-router-verfuegbar.md index 806c08c..623a29a 100644 --- a/content/blog/2016-09-endgeraetefreiheit-testen-es-sind-wieder-router-verfuegbar.md +++ b/content/blog/2016-09-endgeraetefreiheit-testen-es-sind-wieder-router-verfuegbar.md @@ -3,12 +3,12 @@ title: Endgerätefreiheit testen – Es sind wieder Router verfügbar! date: 2016-09-23T09:23:09+00:00 aliases: endgeraetefreiheit-testen-es-sind-wieder-router-verfuegbar categories: + - blog - deutsch tags: - - routerfreedom - - fsfe - - germany - - policy + - RouterFreedom + - FSFE + - Policy --- Seit dem 1. August herrscht – auch dank der langfristigen Arbeit der FSFE – gesetzlich [Endgerätefreiheit][1] in Deutschland, sprich alle Kundinnen und Kunden eines DSL- oder Kabelanbieters sollen die Freiheit haben, ein Modem oder Router ihrer Wahl anzuschließen, ohne systematisch benachteiligt zu werden. Doch halten die Anbieter das wirklich ein? Die FSFE testet das mit Hilfe großartiger Freiwilliger, denen wir alternative Testgeräte zuschicken. Und davon sind aktuell wieder ein paar verfügbar und warten auf neue Tester! diff --git a/content/blog/2016-09-ispa-radio-lockdown-directive/index.md b/content/blog/2016-09-ispa-radio-lockdown-directive/index.md new file mode 100644 index 0000000..97b4fc2 --- /dev/null +++ b/content/blog/2016-09-ispa-radio-lockdown-directive/index.md @@ -0,0 +1,24 @@ +--- +title: "Funkabschottungsrichtlinie - Gefahr für Nutzerrechte und Unternehmen (ISPA News)" +date: 2016-09-01 +categories: + - deutsch + - article +tags: + - RadioLockdown + - Policy + - FSFE + - FSFE +headerimage: + src: radio-cage.jpg +summary: In den ISPA News erschien mein Artikel über die Bedrohung durch die EU-Funkanlagenrichtlinie. Ich erläutere, wie Artikel 3(3)(i) der RED nicht nur Nutzerrechte gefährdet, sondern auch für technologieorientierte Unternehmen und die Open-Source-Community existenzielle Risiken birgt – von Router-Herstellern über Funkgeräte bis hin zu IoT-Produkten. +article: + name: ISPA News + href: https://up.mehl.mx/docs/2016-03-ISPA-News.pdf +--- + +In meinem Artikel für die ISPA News (Internet Service Providers Austria) analysiere ich die weitreichenden Folgen der EU-Funkanlagenrichtlinie (Radio Equipment Directive, RED) für Nutzerrechte und Unternehmen. Artikel 3(3)(i) der Richtlinie verlangt, dass Hersteller sicherstellen müssen, dass nur konforme Software auf Funkgeräten läuft -- ein Regelwerk, das in der Praxis einem vollständigen Lockdown gleichkommt. Ich zeige auf, wie dies Nutzer:innen daran hindern würde, alternative Firmware auf ihren Routern, Smartphones oder anderen Funkgeräten zu installieren, und damit fundamentale Freiheitsrechte beschneidet. + +Besonders problematisch: Die Richtlinie trifft nicht nur Endnutzer:innen, sondern bedroht auch zahlreiche Unternehmen und Projekte in ihrer Existenz. Router-Hersteller, die auf OpenWrt setzen, innovative Startups im IoT-Bereich, Forschungseinrichtungen und die gesamte Open-Source-Community im Funkbereich stehen vor unüberwindlichen Hürden. Die Kosten für Compliance-Verfahren würden insbesondere kleine und mittlere Unternehmen sowie Non-Profit-Projekte ausschließen. Der Artikel verdeutlicht die Notwendigkeit, diese unverhältnismäßige Regulierung zu verhindern. + +Der vollständige Artikel ist in den [ISPA News](https://www.ispa.at/wissenspool/ispa-news/) 03/2026 erschienen. diff --git a/content/blog/2016-09-ispa-radio-lockdown-directive/radio-cage.jpg b/content/blog/2016-09-ispa-radio-lockdown-directive/radio-cage.jpg new file mode 100644 index 0000000..0168695 Binary files /dev/null and b/content/blog/2016-09-ispa-radio-lockdown-directive/radio-cage.jpg differ diff --git a/content/blog/2016-09-schluss-mit-dem-routerzwang-radiosendung-im-deutschlandfunk.md b/content/blog/2016-09-schluss-mit-dem-routerzwang-radiosendung-im-deutschlandfunk.md index 714b312..33c9c6f 100644 --- a/content/blog/2016-09-schluss-mit-dem-routerzwang-radiosendung-im-deutschlandfunk.md +++ b/content/blog/2016-09-schluss-mit-dem-routerzwang-radiosendung-im-deutschlandfunk.md @@ -3,13 +3,13 @@ title: „Schluss mit dem Routerzwang“ – Radiosendung im Deutschlandfunk date: 2016-09-01T16:44:26+00:00 aliases: schluss-mit-dem-routerzwang-radiosendung-im-deutschlandfunk categories: + - blog - deutsch tags: - - routerfreedom - - fsfe - - germany - - security - - policy + - RouterFreedom + - FSFE + - Security + - Policy --- Heute war ich beim Deutschlandfunk zu einer [Radiosendung über den Routerzwang][1] eingeladen. Wir haben etwa eine Stunde lang darüber geredet, warum es so wichtig ist, dass wir seit dem 1. August endlich [Routerfreiheit][2] in Deutschland haben, was das für Verbraucher bringt und welche Fragen noch ungeklärt sind. diff --git a/content/blog/2016-10-freie-software-definition-in-dortmund.md b/content/blog/2016-10-freie-software-definition-in-dortmund.md index 6f00307..3c98ee0 100644 --- a/content/blog/2016-10-freie-software-definition-in-dortmund.md +++ b/content/blog/2016-10-freie-software-definition-in-dortmund.md @@ -3,12 +3,12 @@ title: Freie Software – Definition in Dortmund date: 2016-10-13T17:22:16+00:00 aliases: freie-software-definition-in-dortmund categories: + - blog - deutsch tags: - - fsfe - - germany - - policy - - security + - FSFE + - Policy + - Security --- diff --git a/content/blog/2016-11-build-fsfe-websites-locally.md b/content/blog/2016-11-build-fsfe-websites-locally.md index 86d44ed..32b8989 100644 --- a/content/blog/2016-11-build-fsfe-websites-locally.md +++ b/content/blog/2016-11-build-fsfe-websites-locally.md @@ -3,12 +3,11 @@ title: Build FSFE websites locally date: 2016-11-13T23:00:44+00:00 aliases: build-fsfe-websites-locally categories: + - blog - english tags: - - bash - - fsfe - - guide - - tools + - Code + - FSFE --- _Note: This guide is also available [in FSFE’s wiki][1] now, and it will be the only version maintained. So please head over to the wiki if you’re planning to follow this guide._ diff --git a/content/blog/2016-11-openrheinruhr-2016-a-report-of-iron-and-freedom.md b/content/blog/2016-11-openrheinruhr-2016-a-report-of-iron-and-freedom.md index a767ebc..6f30f2a 100644 --- a/content/blog/2016-11-openrheinruhr-2016-a-report-of-iron-and-freedom.md +++ b/content/blog/2016-11-openrheinruhr-2016-a-report-of-iron-and-freedom.md @@ -3,13 +3,12 @@ title: OpenRheinRuhr 2016 – A report of iron and freedom date: 2016-11-09T21:55:53+00:00 aliases: openrheinruhr-2016-a-report-of-iron-and-freedom categories: + - blog - english tags: - - report - - fsfe - - germany - - routerfreedom - - radiolockdown + - FSFE + - RouterFreedom + - RadioLockdown --- Last weekend, I visited Oberhausen to participate in [OpenRheinRuhr][1], a well-known Free Software event in north-western Germany. Over two days I was part of [FSFE][2]’s booth team, gave a talk, and enjoyed talking to tons of like-minded people about politics, technology and other stuff. In the next few minutes you will learn what coat hangers have to do with flat irons and which hotel you shouldn’t book if you plan to visit Oberhausen. diff --git a/content/blog/2016-12-33c3-routers-radio-lockdown/33c3-2016.jpg b/content/blog/2016-12-33c3-routers-radio-lockdown/33c3-2016.jpg new file mode 100644 index 0000000..5d89a27 Binary files /dev/null and b/content/blog/2016-12-33c3-routers-radio-lockdown/33c3-2016.jpg differ diff --git a/content/blog/2016-12-33c3-routers-radio-lockdown/index.md b/content/blog/2016-12-33c3-routers-radio-lockdown/index.md new file mode 100644 index 0000000..2b2bfaf --- /dev/null +++ b/content/blog/2016-12-33c3-routers-radio-lockdown/index.md @@ -0,0 +1,26 @@ +--- +title: "Routerzwang und Funkabschottung - Was Aktivisten daraus lernen können" +date: 2016-12-27 +categories: + - deutsch + - presentation +tags: + - RouterFreedom + - RadioLockdown + - Policy + - FSFE +headerimage: + src: 33c3-2016.jpg +summary: "Beim 33. Chaos Communication Congress (33c3) in Hamburg präsentierte ich zwei erfolgreiche Aktivismuskampagnen und was andere daraus lernen können: den Kampf gegen den Routerzwang in Deutschland und die laufende Kampagne gegen die EU-Funkabschottungs-Richtlinie. Der CCC bringt tausende Hacker, Aktivisten und technisch Versierte zusammen – genau die Zielgruppe, die sowohl von diesen Themen betroffen ist als auch die Fähigkeiten hat, effektiv gegen diese und ähnliche Missstände einzutreten." +video: https://media.ccc.de/v/33c3-8024-routerzwang_und_funkabschottung +slides: https://download.fsfe.org/presentations/20161227-mm-33C3-Radio+Router.de.pdf +event: + name: 33c3 + href: https://fahrplan.events.ccc.de/congress/2016/Fahrplan/events/8024.html +--- + +Beim 33. Chaos Communication Congress (33c3) in Hamburg präsentierte ich zwei erfolgreiche Aktivismuskampagnen und was andere daraus lernen können: den Kampf gegen den Routerzwang in Deutschland und die laufende Kampagne gegen die EU-Funkabschottungs-Richtlinie. Der CCC bringt tausende Hacker, Aktivisten und technisch Versierte zusammen – genau die Zielgruppe, die sowohl von diesen Themen betroffen ist als auch die Fähigkeiten hat, effektiv gegen diese und ähnliche Missstände einzutreten. + +Der Vortrag erzählte zuerst die Erfolgsgeschichte der Routerfreiheit: Wie es der FSFE und Verbündeten gelang, gegen massive Lobbying-Anstrengungen der Telekommunikationsanbieter ein Gesetz durchzusetzen, das Kunden die freie Wahl ihres Routers garantiert. Ich analysierte, welche Strategien funktionierten -- breite Koalitionen, technische Expertise trifft Politik, öffentlicher Druck -- und was weniger erfolgreich war. Dann wendete ich diese Lektionen auf die aktuell drohende Funkabschottung durch die EU Radio Equipment Directive an: eine noch größere Bedrohung, die aber mit ähnlichen Taktiken angegangen werden könnte. + +Der Vortrag war bewusst als Aktivismus-Workshop konzipiert. Die Diskussion fokussierte sich darauf, wie technische Communities ihre Expertise nutzen können, um politische Prozesse zu beeinflussen, wie man effektive Koalitionen bildet, und warum es wichtig ist, nicht nur zu protestieren, sondern konstruktive Lösungsvorschläge zu entwickeln. Für das CCC-Publikum, das oft skeptisch gegenüber "Politik" ist, zeigte der Vortrag, dass technischer Einfluss auf Regulierung möglich und notwendig ist. diff --git a/content/blog/2016-12-zurichglobalist-free-software-free-society/free-software-free-society.jpg b/content/blog/2016-12-zurichglobalist-free-software-free-society/free-software-free-society.jpg new file mode 100644 index 0000000..d3141c9 Binary files /dev/null and b/content/blog/2016-12-zurichglobalist-free-software-free-society/free-software-free-society.jpg differ diff --git a/content/blog/2016-12-zurichglobalist-free-software-free-society/index.md b/content/blog/2016-12-zurichglobalist-free-software-free-society/index.md new file mode 100644 index 0000000..9b13788 --- /dev/null +++ b/content/blog/2016-12-zurichglobalist-free-software-free-society/index.md @@ -0,0 +1,23 @@ +--- +title: "Freie Software, Freie Gesellschaft. Warum analoge Freiheit nicht mehr ohne digitale Freiheit gedacht werden kann (Zurich Globalist)" +date: 2016-12-07 +categories: + - deutsch + - article +tags: + - Policy + - Privacy +headerimage: + src: free-software-free-society.jpg + text: Free Software, Free Society +summary: Im Zurich Globalist erschien mein Artikel über die Untrennbarkeit von analoger und digitaler Freiheit. Ich argumentiere, dass Freie Software nicht nur ein technisches Thema ist, sondern fundamentale demokratische Grundrechte in der digitalen Gesellschaft schützt -- von Meinungsfreiheit über Privatsphäre bis hin zu Selbstbestimmung. +article: + name: Zurich Globalist + href: http://www.zurichglobalist.uzh.ch/dam/jcr:3576081b-18a9-4d80-95a9-fcc13071974c/Zurich%20Globalist_Freedom.pdf +--- + +In meinem Artikel für den Zurich Globalist argumentiere ich, dass digitale und analoge Freiheiten heute untrennbar miteinander verbunden sind. In einer Welt, in der nahezu alle Lebensbereiche von Software durchdrungen sind -- von Kommunikation über Arbeit bis hin zu staatlichen Dienstleistungen -- ist die Freiheit der Software zur Grundvoraussetzung für individuelle Freiheit geworden. Ohne die Möglichkeit, Software zu verstehen, zu teilen und zu verändern, werden fundamentale Grundrechte wie Meinungsfreiheit, Versammlungsfreiheit und das Recht auf Privatsphäre faktisch eingeschränkt. + +Ich zeige auf, dass proprietäre Software uns in Abhängigkeiten zwingt und demokratische Kontrolle unmöglich macht. Freie Software hingegen ermöglicht Transparenz, Selbstbestimmung und Innovation. Sie ist nicht nur eine technische Präferenz, sondern eine politische Notwendigkeit für eine freie Gesellschaft im digitalen Zeitalter. Der Artikel verdeutlicht, warum wir analoge Freiheiten nicht mehr ohne digitale Freiheiten denken können -- und umgekehrt. + +Der vollständige Artikel erschien erstmals im [Zurich Globalist #7](http://www.zurichglobalist.uzh.ch/dam/jcr:3576081b-18a9-4d80-95a9-fcc13071974c/Zurich%20Globalist_Freedom.pdf). diff --git a/content/blog/2017-02-fosdem-radio-lockdown/firstslide.jpg b/content/blog/2017-02-fosdem-radio-lockdown/firstslide.jpg new file mode 100644 index 0000000..dd672e9 Binary files /dev/null and b/content/blog/2017-02-fosdem-radio-lockdown/firstslide.jpg differ diff --git a/content/blog/2017-02-fosdem-radio-lockdown/index.md b/content/blog/2017-02-fosdem-radio-lockdown/index.md new file mode 100644 index 0000000..9208d60 --- /dev/null +++ b/content/blog/2017-02-fosdem-radio-lockdown/index.md @@ -0,0 +1,24 @@ +--- +title: "Radio Lockdown Directive - Major Threat for Free Software on Radio Devices" +date: 2017-02-04 +categories: + - english + - presentation +tags: + - RadioLockdown + - Policy + - FSFE +headerimage: + src: firstslide.jpg +video: https://archive.fosdem.org/2017/schedule/event/radio_lockdown_directive/ +slides: https://download.fsfe.org/presentations/20170204-mm-FOSDEM-Radiolockdown.en.pdf +event: + name: FOSDEM 2017 + href: https://archive.fosdem.org/2017/schedule/event/radio_lockdown_directive/ +--- + +At FOSDEM 2017, I presented on the EU Radio Equipment Directive and its potential to become a major threat for Free Software on radio-capable devices. This talk was part of raising awareness in the Free Software community about an emerging regulatory threat that could fundamentally undermine software freedom on billions of devices. The Radio Equipment Directive (RED), ostensibly designed to ensure radio equipment compliance, contained provisions that could be interpreted to require device lockdown preventing any software modifications. + +The presentation explained the technical and legal mechanisms by which this directive could be used to lock down devices containing radio hardware – essentially everything from smartphones to laptops to IoT devices. I detailed how manufacturers might interpret compliance requirements as necessitating complete software control, preventing users from installing alternative operating systems, modifying firmware, or running Free Software they choose. The talk outlined the threat not just to hobbyists and tinkerers, but to the entire Free Software ecosystem that depends on users' ability to control their computing devices. + +The FOSDEM audience, as one of the largest gatherings of Free Software developers in Europe, was a critical venue for this message. Especially the discussions after the presentation focused on strategies for engaging with EU regulators, building coalitions with other affected communities (security researchers, hardware hackers, consumer rights advocates), and ensuring that compliance mechanisms preserve rather than eliminate software freedom. This talk was part of a sustained FSFE campaign that ran for more than 10 years. diff --git a/content/blog/2017-02-i-love-astroid-ilovefs.md b/content/blog/2017-02-i-love-astroid-ilovefs.md index cffb9df..d7b3059 100644 --- a/content/blog/2017-02-i-love-astroid-ilovefs.md +++ b/content/blog/2017-02-i-love-astroid-ilovefs.md @@ -5,12 +5,12 @@ type: post date: 2017-02-14T07:30:51+00:00 url: /blog/2017/i-love-astroid-ilovefs categories: + - blog - english tags: - - email - - fsfe - - ilovefs - - tools + - Communication + - FSFE + - ILoveFS --- You cannot imagine how long I’ve waited to write this blog post. Normally I’m not the bragging kind of guy but for this year’s edition of my „[I love Free Software][1]“ declaration articles (after [2014][2], [2015][3] and [2016][4]) I just want to shout out to the world: I have the world’s best mail client: [astroid][5]! diff --git a/content/blog/2017-03-chemnitzer-linuxtage-radio-lockdown/firstslide.jpg b/content/blog/2017-03-chemnitzer-linuxtage-radio-lockdown/firstslide.jpg new file mode 100644 index 0000000..8a55ce6 Binary files /dev/null and b/content/blog/2017-03-chemnitzer-linuxtage-radio-lockdown/firstslide.jpg differ diff --git a/content/blog/2017-03-chemnitzer-linuxtage-radio-lockdown/index.md b/content/blog/2017-03-chemnitzer-linuxtage-radio-lockdown/index.md new file mode 100644 index 0000000..9dfbd67 --- /dev/null +++ b/content/blog/2017-03-chemnitzer-linuxtage-radio-lockdown/index.md @@ -0,0 +1,24 @@ +--- +title: "Funkabschottung - Unsere Geräte in Gefahr" +date: 2017-03-11 +categories: + - deutsch + - presentation +tags: + - RadioLockdown + - Policy + - FSFE +headerimage: + src: firstslide.jpg +video: https://chemnitzer.linux-tage.de/2017/en/programm/beitrag/266 +slides: https://download.fsfe.org/presentations/20170311-mm-CLT-RadioLockdown.de.pdf +event: + name: Chemnitzer Linuxtage 2017 + href: https://chemnitzer.linux-tage.de/2017/en/programm/beitrag/266 +--- + +Bei den Chemnitzer Linuxtagen 2017 warnte ich vor der EU-Funkabschottungs-Richtlinie und ihren Auswirkungen auf die Freiheit unserer Geräte. Die Chemnitzer Linuxtage ziehen ein technisch versiertes Publikum an, das oft alternative Betriebssysteme nutzt, Router selbst konfiguriert und Wert auf Kontrolle über die eigene Hardware legt – genau die Praktiken, die durch diese Richtlinie gefährdet wurden. Der Vortrag machte deutlich, dass scheinbar abstrakte EU-Regulierung sehr konkrete Auswirkungen auf alltägliche technische Freiheiten haben kann. + +Ich erklärte, wie die Radio Equipment Directive (RED) unter dem Vorwand der Frequenzregulierung genutzt werden könnte, um Geräte komplett abzuschotten. Das würde bedeuten: keine alternativen Router-Firmwares mehr, keine Custom ROMs auf Smartphones, keine Modifikation von Software auf allem, was WLAN oder Mobilfunk nutzt. Die Präsentation zeigte technische Details, wie solche Lockdowns implementiert werden könnten, welche Geräte betroffen wären, und warum die Argumente für diese Einschränkungen nicht überzeugend waren – echte Compliance ließe sich auch ohne komplette Gerätesperre erreichen. + +Das Publikum reagierte mit berechtigter Sorge, denn viele Anwesende nutzen genau die Freiheiten, die bedroht waren. Die Diskussion fokussierte sich auf konkrete Schritte: wie man sich politisch engagieren kann, welche Rolle Hersteller spielen könnten, und welche technischen Gegenmaßnahmen möglich wären. Der Vortrag war Teil einer breiteren Kampagne der FSFE, um Bewusstsein für diese Bedrohung zu schaffen und politischen Druck aufzubauen. diff --git a/content/blog/2017-04-llw-radio-lockdown/firstslide.jpg b/content/blog/2017-04-llw-radio-lockdown/firstslide.jpg new file mode 100644 index 0000000..ea2c4b3 Binary files /dev/null and b/content/blog/2017-04-llw-radio-lockdown/firstslide.jpg differ diff --git a/content/blog/2017-04-llw-radio-lockdown/index.md b/content/blog/2017-04-llw-radio-lockdown/index.md new file mode 100644 index 0000000..5a74a6e --- /dev/null +++ b/content/blog/2017-04-llw-radio-lockdown/index.md @@ -0,0 +1,26 @@ +--- +title: "EU Radio Equipment Directive: Extensive Device Lockdown" +date: 2017-04-27 +categories: + - english + - presentation +tags: + - RadioLockdown + - Policy + - FSFE + - FSFE +headerimage: + src: firstslide.jpg + processes: + - fill 1000x440 center webp +slides: https://download.fsfe.org/presentations/20170427-mm-LLW-RadioLockdown_verbose.en.pdf +event: + name: Legal and Licensing Workshop 2017 + href: https://fsfe.org/news/2017/news-20170619-01.html +--- + +At the exclusive Legal and Licensing Workshop 2017, I presented on the EU Radio Equipment Directive and its potential for extensive device lockdown. The Legal and Licensing Workshop brings together legal professionals, compliance officers, and policy experts working on Free Software issues, making it the right audience for a detailed legal and technical analysis of this directive's implications. The talk warned about how seemingly well-intentioned radio equipment regulations could be implemented in ways that fundamentally threaten software freedom on radio-capable devices. + +The Radio Equipment Directive (RED) aimed to ensure that radio equipment doesn't interfere with networks or use spectrum inappropriately. However, the way manufacturers could implement compliance – by locking down devices to prevent any software modifications – posed serious threats. I explained how this could affect everything from WiFi routers to smartphones, preventing users from installing alternative operating systems or modifying software on devices they own. The presentation detailed the legal framework, showed how different implementation approaches would affect Free Software, and discussed what the Free Software community needed to advocate for. + +The workshop audience's legal expertise was crucial for developing strategies to address this issue. The discussion explored how to engage with regulators to ensure compliance mechanisms that preserve software freedom and what legal arguments could be made for user rights to modify their own devices diff --git a/content/blog/2017-05-idee-wiki-zu-gesellschaftspolitischen-positionen-von-prominenten.md b/content/blog/2017-05-idee-wiki-zu-gesellschaftspolitischen-positionen-von-prominenten.md index 9e91829..003433e 100644 --- a/content/blog/2017-05-idee-wiki-zu-gesellschaftspolitischen-positionen-von-prominenten.md +++ b/content/blog/2017-05-idee-wiki-zu-gesellschaftspolitischen-positionen-von-prominenten.md @@ -3,11 +3,13 @@ title: 'Idee: Wiki zu gesellschaftspolitischen Positionen von Prominenten' date: 2017-05-29T10:15:45+00:00 aliases: idee-wiki-zu-gesellschaftspolitischen-positionen-von-prominenten categories: + - blog - deutsch tags: - - policy -headerimage: /blog/maiziere-lehmann.jpg -headercredits: CC-BY-SA 3.0 Sandro Halank / CC-BY 2.0 Ronnie Macdonald + - Policy +headerimage: + src: /blog/maiziere-lehmann.jpg + text: CC-BY-SA 3.0 Sandro Halank / CC-BY 2.0 Ronnie Macdonald --- _Alles begann, als mein Mitbewohner Lars und ich uns eines morgens fragten: „Mit wem würden wir lieber ein Bier trinken gehen, Thomas de Maizière oder Jens Lehmann?“._ diff --git a/content/blog/2017-05-lwn-radio-lockdown-concerns/index.md b/content/blog/2017-05-lwn-radio-lockdown-concerns/index.md new file mode 100644 index 0000000..ef1e627 --- /dev/null +++ b/content/blog/2017-05-lwn-radio-lockdown-concerns/index.md @@ -0,0 +1,20 @@ +--- +title: "Free-software concerns with Europe's radio directive (LWN.net)" +date: 2017-05-10 +categories: + - english + - article +tags: + - RadioLockdown + - FSFE + - FSFE +article: + name: LWN.net + href: https://lwn.net/Articles/722197/ +--- + +Jake Edge from LWN.net wrote a comprehensive article covering my presentation at the 2017 Free Software Legal and Licensing Workshop about the EU Radio Equipment Directive (RED). The article detailed the concerns around Article 3(3)(i) of the directive, which requires manufacturers to ensure that only "compliant" software can be loaded onto radio equipment. This seemingly technical requirement threatened to mandate device lockdown across a huge range of consumer electronics containing radio transmitters. + +The LWN article explained how RED could affect everything from WiFi-enabled laptops to smartphones, routers, and IoT devices. It outlined the various actors involved -- from the European Commission and ETSI (responsible for updating standards) to EU member states tasked with implementation -- and the unclear timeline for when these requirements would actually take effect. The piece also covered the FSFE's response, including our Joint Statement against Radio Lockdown signed by 48 organizations and our efforts to join the expert group on reconfigurable radio systems to help shape device classifications. + +The article sparked significant discussion in the comments, with readers debating whether the directive's goals (preventing radio interference) justified the means (potential complete software lockdown), whether manufacturers or users should bear responsibility for compliance, and how the requirements compared to other safety regulations. The coverage helped raise awareness beyond the immediate Free and Open Source Software community about how radio regulations could fundamentally impact users' ability to control their own computing devices. diff --git a/content/blog/2018-05-shareable-public-money-public-code/index.md b/content/blog/2018-05-shareable-public-money-public-code/index.md new file mode 100644 index 0000000..78b7dd8 --- /dev/null +++ b/content/blog/2018-05-shareable-public-money-public-code/index.md @@ -0,0 +1,30 @@ +--- +title: "Public Money, Public Code pushes for governments to switch to open-source software (Sharable)" +date: 2018-05-09 +categories: + - english + - article +tags: + - PublicCode + - OSPO + - Policy + - FSFE +headerimage: + src: pmpc.jpg +summary: Shareable published an extensive interview with me about the FSFE's Public Money, Public Code campaign. I explained why publicly funded software should be released as Open Source, the benefits for transparency, security and collaboration, and how cities like Barcelona are leading with 70% of their software budget spent on Open Source. +article: + name: Shareable + href: https://www.shareable.net/blog/public-money-public-code-pushes-for-governments-to-switch-to-open-source-software +--- + +In an extensive interview with Shareable, I explained the goals of the FSFE's "Public Money, Public Code" campaign: All publicly funded software should be released under Free Software licenses so governments and citizens can use, study, share and improve it. Addressing technical challenges like proprietary document formats and interoperability, I emphasized: + +> The more Free Software there is, the easier it gets to create and use it. It's just a matter of starting that process. + +The benefits are manifold: saving time, reducing costs, more collaboration, transparency, interoperability, innovation, and independence from software vendors. On the often-cited security concerns, I explained: + +> It's actually better for security if software is transparent and the source code is published, because it's easier for security experts to see what's going wrong in the software. Malicious people will figure it out anyway, but more people can review the code. We've seen this with Linux. It is stable, secure and transparent, and we don't see a disadvantage in the fact that it's Open Source. + +I highlighted Barcelona as a role model, spending 70% of its software budget on Open Source and understanding it's not just about using Free Software, but procuring it in ways that allow regional and smaller vendors to participate. + +The [full interview](https://www.shareable.net/blog/public-money-public-code-pushes-for-governments-to-switch-to-open-source-software) with more details on transparency, collaboration and international examples is available on Shareable. diff --git a/content/blog/2018-05-shareable-public-money-public-code/pmpc.jpg b/content/blog/2018-05-shareable-public-money-public-code/pmpc.jpg new file mode 100644 index 0000000..e224501 Binary files /dev/null and b/content/blog/2018-05-shareable-public-money-public-code/pmpc.jpg differ diff --git a/content/blog/2018-06-ow2con-public-code-keynote/index.md b/content/blog/2018-06-ow2con-public-code-keynote/index.md new file mode 100644 index 0000000..a3bdc18 --- /dev/null +++ b/content/blog/2018-06-ow2con-public-code-keynote/index.md @@ -0,0 +1,27 @@ +--- +title: "Keynote: Public Code with Free Software - Modernising Public Digital Infrastructure" +date: 2018-06-07 +categories: + - english + - presentation +tags: + - PublicCode + - Policy + - FSFE +headerimage: + src: ow2con-2018.jpg + text: Picture of me giving the keynote at OW2con 2018 in Paris + processes: + - fill 1000x440 top webp +video: https://www.youtube.com/watch?v=kQGw25xG_5c +slides: https://download.fsfe.org/presentations/20180607-mm-OW2Con-PMPC.en.pdf +event: + name: OW2con 2018 + href: https://ow2con18.sched.com/event/EcdE/keynote-public-code-with-free-software-modernising-public-digital-infrastructure +--- + +I delivered the opening keynote at OW2con 2018 in Paris, presenting the "Public Money, Public Code" vision to a conference focused on Open Source middleware and enterprise solutions. OW2 is a European association fostering Open Source infrastructure software, with strong connections to both industry and public sector organizations. The keynote position reflected the growing recognition that making publicly funded code freely available isn't just an activist demand -- it's a pragmatic approach to building better public digital infrastructure. + +The keynote argued that the current model, where public administrations pay vendors to develop software but then cannot share it with other public bodies, is economically inefficient and technologically counterproductive. I presented the FSFE's "Public Money, Public Code" campaign as a policy framework to address this: require that code developed with public funds be released as Free Software. The benefits extend beyond cost savings to include improved security (through transparency and auditability), reduced vendor lock-in, and the ability to build on each other's work rather than repeatedly reinventing similar solutions. + +For the OW2 community, which works on exactly the kind of collaborative Open Source development that Public Code envisions at scale, the message resonated strongly. The discussion explored how policy changes could accelerate adoption of Open Source infrastructure, how public procurement could be restructured to favor Free Software, and what role organizations like OW2 could play in providing professional-grade Open Source alternatives to proprietary public sector software. diff --git a/content/blog/2018-06-ow2con-public-code-keynote/ow2con-2018.jpg b/content/blog/2018-06-ow2con-public-code-keynote/ow2con-2018.jpg new file mode 100644 index 0000000..d42370a Binary files /dev/null and b/content/blog/2018-06-ow2con-public-code-keynote/ow2con-2018.jpg differ diff --git a/content/blog/2018-07-armed-forces-sovereignty/firstslide.jpg b/content/blog/2018-07-armed-forces-sovereignty/firstslide.jpg new file mode 100644 index 0000000..7e20640 Binary files /dev/null and b/content/blog/2018-07-armed-forces-sovereignty/firstslide.jpg differ diff --git a/content/blog/2018-07-armed-forces-sovereignty/index.md b/content/blog/2018-07-armed-forces-sovereignty/index.md new file mode 100644 index 0000000..d0c52ae --- /dev/null +++ b/content/blog/2018-07-armed-forces-sovereignty/index.md @@ -0,0 +1,21 @@ +--- +title: "Souveränität durch Freie Software (Bundeswehr)" +date: 2018-07-03 +categories: + - deutsch + - presentation +tags: + - PublicCode + - Sovereignty + - Policy + - FSFE +headerimage: + src: firstslide.jpg +slides: https://download.fsfe.org/presentations/20180703-mm-Jugendoffiziere-PMPC.de.pdf +--- + +Bei einem internen Vortrag für die deutsche Bundeswehr sprach ich über digitale Souveränität durch Freie Software. Dieser ungewöhnliche Kontext – eine Präsentation vor militärischem Personal – bot die Möglichkeit, die Bedeutung von Softwarefreiheit aus der Perspektive von IT-Sicherheit, strategischer Unabhängigkeit und operationaler Kontrolle zu beleuchten. Für Organisationen, die mit hochsensiblen Daten arbeiten und nationale Sicherheitsinteressen berücksichtigen müssen, sind die Fragen nach Souveränität und Kontrolle über die eigene IT-Infrastruktur besonders dringend. + +Der Vortrag betonte, wie Abhängigkeit von proprietärer Software strategische Risiken schafft: Auslandsabhängigkeit bei kritischer Infrastruktur, mangelnde Möglichkeit zur Überprüfung auf Backdoors oder Schwachstellen, und fehlende Kontrolle über Updates und Funktionsänderungen. Freie Software bietet hingegen die Möglichkeit, Code zu auditieren, Sicherheitslücken selbst zu schließen, und unabhängig von kommerziellen Anbietern langfristige Supportstrukturen aufzubauen. Diese Argumente gelten nicht nur für militärische Organisationen, sondern für alle Bereiche der öffentlichen Verwaltung und kritischen Infrastruktur. + +Die Diskussion zeigte, dass das Bewusstsein für diese Themen in der Bundeswehr durchaus vorhanden war, aber oft praktische Hürden – von Procurement-Strukturen bis zu fehlender Expertise – die Umstellung auf Freie Software erschwerten. Der Vortrag half, die strategische Bedeutung dieser Entscheidungen zu unterstreichen und Argumente zu liefern, warum Software-Souveränität eine langfristige Investition in Sicherheit und Unabhängigkeit darstellt. diff --git a/content/blog/2018-07-rmll-lsm-public-code/index.md b/content/blog/2018-07-rmll-lsm-public-code/index.md new file mode 100644 index 0000000..b12509e --- /dev/null +++ b/content/blog/2018-07-rmll-lsm-public-code/index.md @@ -0,0 +1,27 @@ +--- +title: "Public Money? Public Code! - Modernising Digital Public Infrastructure" +date: 2018-07-07 +categories: + - english + - presentation +tags: + - PublicCode + - Policy + - FSFE +headerimage: + src: rmll-2018.jpg + text: Picture of me giving the presentation at RMLL 2018 in Strasbourg + processes: + - fill 1000x440 center webp +slides: https://download.fsfe.org/presentations/20180707-mm-RMLL-PMPC.en.pdf +video: https://www.canalc2.tv/video/15191 +event: + name: RMLL/LSM 2018 + href: https://rmll2018.info +--- + +At RMLL/Libre Software Meeting 2018 in Strasbourg, I presented the "Public Money, Public Code" campaign to one of Europe's longest-running Free Software conferences. The RMLL/LSM brings together activists, developers, and public sector stakeholders who have been advocating for Free Software since the late 1990s, making it an ideal audience for discussing how to systematically transform public digital infrastructure. The talk built on decades of Free Software advocacy to argue for a new policy paradigm. + +The presentation made the case that when public money pays for software development, the resulting code should be publicly available as Free Software. This isn't just good principle – it's good economics and good governance. I showed how current practices lead to wasteful redundancy, with multiple public bodies independently funding development of similar solutions while being unable to share code. The talk outlined concrete policy changes needed at European, national, and municipal levels to make Public Code the default for publicly funded software development. + +For the RMLL audience, being strong FOSS advocates, the Public Money, Public Code campaign provided a rallying point and policy framework for their efforts. The discussion explored successful examples of public code initiatives, strategies for changing procurement regulations, and how to build coalitions between technical communities and policy makers to drive systemic change. diff --git a/content/blog/2018-07-rmll-lsm-public-code/rmll-2018.jpg b/content/blog/2018-07-rmll-lsm-public-code/rmll-2018.jpg new file mode 100644 index 0000000..f22edf7 Binary files /dev/null and b/content/blog/2018-07-rmll-lsm-public-code/rmll-2018.jpg differ diff --git a/content/blog/2018-08-welt-android-google-zurueckdraengen/android-phone.jpg b/content/blog/2018-08-welt-android-google-zurueckdraengen/android-phone.jpg new file mode 100644 index 0000000..68efe53 Binary files /dev/null and b/content/blog/2018-08-welt-android-google-zurueckdraengen/android-phone.jpg differ diff --git a/content/blog/2018-08-welt-android-google-zurueckdraengen/index.md b/content/blog/2018-08-welt-android-google-zurueckdraengen/index.md new file mode 100644 index 0000000..4392115 --- /dev/null +++ b/content/blog/2018-08-welt-android-google-zurueckdraengen/index.md @@ -0,0 +1,25 @@ +--- +title: "Android-Kontrolle: So verbannen Sie Google vom Smartphone (WELT.de)" +date: 2018-08-20 +categories: + - deutsch + - article +tags: + - Android + - Privacy +headerimage: + src: android-phone.jpg + text: "Quelle: dpa-tmn, welt.de" +summary: WELT veröffentlichte einen Ratgeber, wie Android-Nutzer:innen Google-Dienste von ihren Smartphones zurückdrängen oder entfernen können. Der Artikel richtet sich an Menschen, die mehr Kontrolle über ihre Daten haben möchten, und behandelt alternative App Stores wie F-Droid, freie Android-Distributionen wie LineageOS sowie datenschutzfreundliche Alternativen zu Google-Apps. +article: + name: WELT.de + href: https://www.welt.de/wirtschaft/webwelt/article181237140/Android-Kontrolle-So-verbannen-Sie-Google-vom-Smartphone.html +--- + +WELT veröffentlichte einen praktischen Leitfaden für Nutzer:innen, die mehr digitale Souveränität über ihre Android-Geräte erlangen möchten. Der Artikel erklärt, wie man Google-Dienste zurückdrängen oder ganz entfernen kann – von der Nutzung alternativer App Stores wie F-Droid bis zum Einsatz freier Android-Distributionen wie LineageOS. Dabei werden auch datenschutzfreundliche Alternativen für gängige Google-Apps vorgestellt, etwa für E-Mail, Kalender und Navigation. + +Ich werde im Artikel zitiert und erkläre, dass die Kontrolle über die Software auf unseren Geräten unter anderem entscheidend für den Schutz unserer Privatsphäre ist: + +> Google ist gut darin, vieles Grundsätzliches anzubieten, was wir machen wollen, und das auch noch sehr komfortabel. Das Problem ist aber, dass es Google immer auch darum geht, Daten für Werbung zu sammeln. Das kann man einfach in den Nutzungsbedingungen nachschauen. Eine Umstellung passiert nicht über Nacht, das ist ein schrittweiser Prozess. Der erste Schritt ist, sich bewusst zu machen, was man bereits nutzt und was davon unerwünscht ist. Der zweite Schritt ist das Ersetzen nicht gewollter Dienste und Apps. Der dritte Schritt wäre die Installation eines Betriebssystems ganz ohne Google. + +Der vollständige Artikel mit allen praktischen Anleitungen ist auf [WELT online](https://www.welt.de/wirtschaft/webwelt/article181237140/Android-Kontrolle-So-verbannen-Sie-Google-vom-Smartphone.html) verfügbar. diff --git a/content/blog/2018-09-balccon-public-code/balccon-2018.jpg b/content/blog/2018-09-balccon-public-code/balccon-2018.jpg new file mode 100644 index 0000000..cf345cf Binary files /dev/null and b/content/blog/2018-09-balccon-public-code/balccon-2018.jpg differ diff --git a/content/blog/2018-09-balccon-public-code/index.md b/content/blog/2018-09-balccon-public-code/index.md new file mode 100644 index 0000000..b5f7be1 --- /dev/null +++ b/content/blog/2018-09-balccon-public-code/index.md @@ -0,0 +1,25 @@ +--- +title: "Public Code with Free Software: Modernising Public Digital Infrastructure" +date: 2018-09-15 +categories: + - english + - presentation +tags: + - PublicCode + - Policy + - FSFE +headerimage: + src: balccon-2018.jpg + text: Picture of me giving the presentation at BalCCon 2018 +video: https://www.youtube.com/watch?v=tEkCnCtoQ60 +slides: https://download.fsfe.org/presentations/20180915-mm-BalCCon-PMPC.en.pdf +event: + name: BalCCon 2018 + href: https://2k18.balccon.org/events/235.html +--- + +At BalCCon 2018 in Novi Sad (Serbia), I presented the FSFE's "Public Money, Public Code" campaign and its vision for modernising public digital infrastructure through Free Software. This was during the early, energetic phase of the campaign when we were building momentum across Europe for the principle that software developed with taxpayer money should be made available as Free Software. BalCCon's technically sophisticated audience with a focus on IT security was an interesting context to discuss how public code can enhance security, transparency, and local technological capacity. + +The talk explained why public administrations' current approach -- paying for proprietary software development and then paying again for licenses to use it, while no one else can benefit from the investment -- makes no sense. I outlined how Free Software enables code reuse across municipalities and countries, reduces vendor lock-in, improves security through transparency, and turns software from a cost center into a shared resource. The presentation showcased early successes of public code initiatives and addressed common objections about support, security, and feasibility. + +For the BalCCon audience, many of whom work with technology in contexts across the Balkans, the message was particularly relevant. The region faces challenges of limited IT budgets, dependency on foreign vendors, and the need to build local technological capacity – all problems that "Public Money, Public Code" directly addresses. The discussion explored how these principles could be adapted to different political and economic contexts while maintaining their core benefits. diff --git a/content/blog/2018-09-drupaleurope-public-code/index.md b/content/blog/2018-09-drupaleurope-public-code/index.md new file mode 100644 index 0000000..a60b5df --- /dev/null +++ b/content/blog/2018-09-drupaleurope-public-code/index.md @@ -0,0 +1,21 @@ +--- +title: "Public Code with Free Software: Modernising Digital Public Infrastructure" +date: 2018-09-11 +categories: + - english + - presentation +tags: + - PublicCode + - Policy + - FSFE +slides: https://download.fsfe.org/presentations/20180911-mm-DrupalEurope-PMPC.en.pdf +event: + name: DrupalEurope 2018 + href: https://www.drupaleurope.org/index.php/session/public-code-free-software-modernising-digital-public-infrastructure.html +--- + +At DrupalEurope 2018 in Darmstadt, I presented the "Public Money, Public Code" initiative to an audience of Drupal developers, site builders, and digital agencies. This was a particularly relevant venue because Drupal itself is Free Software, and many in the audience work on public sector projects where the principles of Public Code directly apply. The talk connected the FSFE's campaign to the practical realities of building public digital infrastructure with content management systems like Drupal. + +The presentation explained why software developed for public administrations with taxpayer money should be released as Free Software. I outlined the benefits: code reuse across different public bodies, reduced vendor lock-in, improved security through transparency, and the ability to customize solutions to local needs. For the Drupal community, which already embraces Open Source principles, the message resonated strongly – many attendees had experienced first-hand the frustration of proprietary systems or custom Drupal modules that couldn't be shared because of licensing restrictions. + +The discussion explored how Drupal agencies could advocate for Public Code principles in their client relationships, how public administrations could structure procurement to require Free Software, and what role the Drupal community could play in building shared public infrastructure. This talk helped connect the broader political campaign to concrete technical communities already working in the public sector. diff --git a/content/blog/2018-10-linuxinsider-open-source-innovation/index.md b/content/blog/2018-10-linuxinsider-open-source-innovation/index.md new file mode 100644 index 0000000..c4ec7e5 --- /dev/null +++ b/content/blog/2018-10-linuxinsider-open-source-innovation/index.md @@ -0,0 +1,29 @@ +--- +title: "Open Source Software: 20-Plus Years of Innovation (LinuxInsider)" +date: 2018-10-29 +categories: + - english + - article +tags: + - Community +headerimage: + src: open-source-blocks.jpg +summary: LinuxInsider published an article about 20+ years of innovation in the Open Source movement, featuring my perspectives on how collaborative development has transformed the technology landscape and the continuing influence of Open Source across industries – from operating systems to enterprise software and cloud infrastructure. +article: + name: LinuxInsider + href: https://www.linuxinsider.com/story/85646.html +--- + +LinuxInsider published a retrospective on over two decades of innovation through Open Source software, featuring my insights on how collaborative development has fundamentally changed the technology industry – from the early days of GNU and Linux through mainstream adoption in enterprise environments to modern success stories like Android, Kubernetes and other transformative projects. + +The article covers key themes including the increasing participation of major corporations as active contributors to Open Source projects, the economic value of Open Source through services and ecosystems, and the outlook on new areas like AI/ML frameworks, IoT, Edge Computing and blockchain technologies where Open Source continues to drive innovation. + +> The Free and Open Source movement has achieved successes probably no one dared to dream of when the free software movement began to take shape in the 1980s, noted Max Mehl, program manager of Free Software Foundation Europe. +> +> “Today, Free Software and Open Source are synonyms that are being used in almost every device — from remotes to washing machines, mobile phones to aircraft, and the International Space Station,” he told LinuxInsider. +> +> Large enterprises, even self-declared enemies of FOSS in the past, now recognize that the power of the community and the transparent processes benefit end users and encourage innovation, noted Mehl. +> +> “The concept of Free Software licenses and copyleft, once a legal hack, is universally accepted and legally confirmed, he added. + +The full article offers a comprehensive perspective on the 2018 Open Source landscape and is available on [LinuxInsider](https://www.linuxinsider.com/story/85646.html). diff --git a/content/blog/2018-10-linuxinsider-open-source-innovation/open-source-blocks.jpg b/content/blog/2018-10-linuxinsider-open-source-innovation/open-source-blocks.jpg new file mode 100644 index 0000000..f01b61a Binary files /dev/null and b/content/blog/2018-10-linuxinsider-open-source-innovation/open-source-blocks.jpg differ diff --git a/content/blog/2019-02-fsfe-planet-has-been-refurbished.md b/content/blog/2019-02-fsfe-planet-has-been-refurbished.md index 4c6b6ab..228c3b4 100644 --- a/content/blog/2019-02-fsfe-planet-has-been-refurbished.md +++ b/content/blog/2019-02-fsfe-planet-has-been-refurbished.md @@ -3,11 +3,11 @@ title: FSFE Planet has been refurbished date: 2019-02-11T10:33:11+00:00 aliases: fsfe-planet-has-been-refurbished categories: + - blog - english tags: - - fsfe - - server - - report + - FSFE + - SystemAdministration --- If you are reading these lines, you are already accessing the brand-new planet of the FSFE. While Björn, Coordinator of Team Germany, has largely improved the design in late 2017, we tackled many underlying issues this time. diff --git a/content/blog/2019-03-protect-freedom-on-radio-devices-raise-your-voice-today.md b/content/blog/2019-03-protect-freedom-on-radio-devices-raise-your-voice-today.md index f18797d..53a5b01 100644 --- a/content/blog/2019-03-protect-freedom-on-radio-devices-raise-your-voice-today.md +++ b/content/blog/2019-03-protect-freedom-on-radio-devices-raise-your-voice-today.md @@ -3,13 +3,14 @@ title: 'Protect freedom on radio devices: raise your voice today!' date: 2019-03-01T15:09:56+00:00 aliases: protect-freedom-on-radio-devices-raise-your-voice-today categories: + - blog - english tags: - - fsfe - - radiolockdown - - routerfreedom - - security - - policy + - FSFE + - RadioLockdown + - RouterFreedom + - Security + - Policy --- diff --git a/content/blog/2019-03-theregister-radio-gaga-eu-directive/index.md b/content/blog/2019-03-theregister-radio-gaga-eu-directive/index.md new file mode 100644 index 0000000..b4ac142 --- /dev/null +++ b/content/blog/2019-03-theregister-radio-gaga-eu-directive/index.md @@ -0,0 +1,25 @@ +--- +title: "Radio gaga: Techies fear EU directive to stop RF device tinkering will do more harm than good (The Register)" +date: 2019-03-11 +categories: + - english + - article +tags: + - RadioLockdown + - Policy + - FSFE + - FSFE +# headerimage: +# src: foo.jpg +# text: bar +summary: The Register reported on the controversy surrounding the EU Radio Equipment Directive (RED) that could ban installing alternative firmware on routers and other radio devices. I was quoted alongside my FSFE colleague Hauke Mehrtens, highlighting how the FSFE was excluded from the implementation working group despite our attempts to participate. +article: + name: The Register + href: https://www.theregister.com/2019/03/11/eu_directive_ban_rf_radio_firmware_tinkering/ +--- + +The Register quoted me and my FSFE colleague Hauke Mehrtens on the growing controversy around Article 3(3)(i) of the EU Radio Equipment Directive. Hauke explained the far-reaching consequences: The ban would severely harm the OpenWrt project, wireless community networks, innovative startups, and network researchers. It would increase electronic waste, make it impossible for users to fix security vulnerabilities themselves or with the help of the community, and block research that could improve the Internet in the EU. + +I was quoted on FSFE's exclusion from the implementation process: FSFE had applied to participate in the working group on implementing the law but was rejected. The article also shows that not only civil society, but also industry associations and manufacturers like Shure opposed a complete ban, arguing instead for industry self-regulation. + +The [full article](https://www.theregister.com/2019/03/11/eu_directive_ban_rf_radio_firmware_tinkering/) with industry statements and further technical details is available on The Register. diff --git a/content/blog/2019-04-grazer-linuxtage-it-security-keynote/glt-2019.jpg b/content/blog/2019-04-grazer-linuxtage-it-security-keynote/glt-2019.jpg new file mode 100644 index 0000000..eb711f2 Binary files /dev/null and b/content/blog/2019-04-grazer-linuxtage-it-security-keynote/glt-2019.jpg differ diff --git a/content/blog/2019-04-grazer-linuxtage-it-security-keynote/index.md b/content/blog/2019-04-grazer-linuxtage-it-security-keynote/index.md new file mode 100644 index 0000000..85bafa5 --- /dev/null +++ b/content/blog/2019-04-grazer-linuxtage-it-security-keynote/index.md @@ -0,0 +1,27 @@ +--- +title: "IT-Sicherheit? Freie Software!" +date: 2019-04-27 +categories: + - deutsch + - presentation +tags: + - Security + - FSFE +headerimage: + src: glt-2019.jpg + text: Bild von mir bei der Keynote auf den Grazer Linuxtagen 2019 + alt: Max Mehl während seiner Keynote auf den Grazer Linuxtagen 2019 + processes: + - fill 1000x440 center webp +video: https://www.youtube.com/watch?v=DOv_5ZPcFZ8 +slides: https://download.fsfe.org/presentations/20190427-mm-Graz-ITSec.de.pdf +event: + name: Grazer Linuxtage 2019 + href: https://pretalx.linuxtage.at/glt19/talk/K9YDDN/ +--- + +Bei den Grazer Linuxtagen 2019 hielt ich die Keynote über den Zusammenhang zwischen IT-Sicherheit und Freier Software. Die Grazer Linuxtage sind eine der wichtigsten deutschsprachigen Veranstaltungen für GNU/Linux und Freie Software, und die Keynote bot die Möglichkeit, dem gesamten Publikum -- von Einsteigern bis zu erfahrenen Entwicklern -- zu erläutern, warum Freie und Open Source Software keine Option, sondern eine Voraussetzung für echte IT-Sicherheit ist. + +Der Vortrag beleuchtete, warum proprietäre Software strukturelle Sicherheitsprobleme mit sich bringt: fehlende Transparenz verhindert unabhängige Sicherheitsanalysen, Nutzer haben keine Kontrolle darüber, was ihre Software tatsächlich macht, und Vendor-Lock-in führt dazu, dass Sicherheitsupdates von Geschäftsinteressen abhängen statt von tatsächlichen Bedrohungen. Im Gegensatz dazu ermöglicht Freie Software Überprüfbarkeit, Community-betriebene Sicherheitsforschung, und stellt sicher, dass Nutzer die Hoheit über ihre IT-Systeme behalten. + +Als Keynote war der Vortrag bewusst breit angelegt, um verschiedene Aspekte des Themas zu beleuchten: von konkreten technischen Sicherheitsvorteilen über die Bedeutung offener Standards bis hin zu gesellschaftlichen Fragen digitaler Souveränität. Die Botschaft war klar: Wer IT-Sicherheit ernst nimmt, kommt an Freier Software nicht vorbei. diff --git a/content/blog/2019-07-pass-the-salt-it-security/index.md b/content/blog/2019-07-pass-the-salt-it-security/index.md new file mode 100644 index 0000000..1a7c874 --- /dev/null +++ b/content/blog/2019-07-pass-the-salt-it-security/index.md @@ -0,0 +1,25 @@ +--- +title: "No IT security without Free Software" +date: 2019-07-03 +categories: + - english + - presentation +tags: + - Security + - FSFE +headerimage: + src: pass-the-salt-2019.jpg + text: Picture of me giving the presentation at Pass the SALT 2019 in Lille + alt: Max Mehl during his presentation at Pass the SALT 2019 in Lille +video: https://www.youtube.com/watch?v=B0qxm331Q8Q +slides: https://download.fsfe.org/presentations/20190703-mm-SALT-ITSec.en.pdf +event: + name: Pass the SALT 2019 + href: https://2019.pass-the-salt.org/talks/102.html +--- + +At Pass the SALT 2019 in Lille, France, I presented on the essential connection between IT security and Free Software. Pass the SALT (Security And Libre Talks) is a security conference with a specific focus on Free and Open Source Software security tools and practices, making it the ideal venue for this topic. The conference brings together security professionals who both develop and use Free Software security tools, and understand the value of transparency in security work. + +The talk examined why proprietary software creates fundamental security problems that cannot be solved through patches or better practices alone. Without access to source code, security researchers cannot fully audit systems, users cannot verify what their software actually does, and the community cannot collaborate on security improvements. I presented case studies of security issues that persisted in proprietary systems precisely because of their closed nature, contrasted with Free Software projects where transparency enabled rapid community response to vulnerabilities. + +The presentation also addressed common misconceptions: that disclosure of source code helps attackers (when research shows the opposite), that commercial vendors provide better security than community projects (when evidence suggests otherwise), and that security and usability require proprietary approaches (when Free Software demonstrates both are achievable). For the Pass the SALT audience, this reinforced their work developing and promoting Free Software security tools as not just technically sound, but philosophically necessary for genuine security. diff --git a/content/blog/2019-07-pass-the-salt-it-security/pass-the-salt-2019.jpg b/content/blog/2019-07-pass-the-salt-it-security/pass-the-salt-2019.jpg new file mode 100644 index 0000000..81856af Binary files /dev/null and b/content/blog/2019-07-pass-the-salt-it-security/pass-the-salt-2019.jpg differ diff --git a/content/blog/2019-09-balccon-it-security/balccon-2019.jpg b/content/blog/2019-09-balccon-it-security/balccon-2019.jpg new file mode 100644 index 0000000..a1febf7 Binary files /dev/null and b/content/blog/2019-09-balccon-it-security/balccon-2019.jpg differ diff --git a/content/blog/2019-09-balccon-it-security/index.md b/content/blog/2019-09-balccon-it-security/index.md new file mode 100644 index 0000000..cb3da0c --- /dev/null +++ b/content/blog/2019-09-balccon-it-security/index.md @@ -0,0 +1,27 @@ +--- +title: "No IT security without Free Software" +date: 2019-09-14 +categories: + - english + - presentation +tags: + - Security + - FSFE +headerimage: + src: balccon-2019.jpg + text: Picture of me giving the presentation at BalCCon 2019 in Novi Sad + alt: Max Mehl during his presentation at BalCCon 2019 in Novi Sad, Serbia + processes: + - fill 1000x440 bottom webp +video: https://www.youtube.com/watch?v=8SWijSFbMhg +slides: https://download.fsfe.org/presentations/20190914-mm-BalCCon-ITSec.en.pdf +event: + name: BalCCon 2019 + href: https://2k19.balccon.org/events/325.html +--- + +At BalCCon 2019 in Novi Sad, Serbia, I delivered a talk arguing that real IT security is fundamentally impossible without Free and Open Source Software. BalCCon (Balkan Computer Congress) brings together security researchers, hackers, and technology enthusiasts from across the Balkans and beyond, making it a perfect audience for examining the deep connections between software freedom and security. The talk challenged the common assumption that security and openness are somehow in tension, arguing instead that transparency is a prerequisite for trustworthy security. + +The presentation examined multiple dimensions of this argument: the security benefits of source code transparency, the danger of security through obscurity in proprietary systems, the importance of independent security audits, the problem of backdoors and undisclosed vulnerabilities, and the critical role of user control over their computing environment. I showed concrete examples where Open Source can resolve an ongoing tension between economic incentives and security needs without sacrificing either. + +For the BalCCon audience, many of whom work directly in information security, this argument resonated strongly. The discussion explored how Open Source principles align with security best practices like defense in depth, least privilege, and verifiable trust. The talk reinforced that advocating for Free Software isn't just about philosophy or licensing -- it's about building secure systems in a fundamentally insecure world. diff --git a/content/blog/2019-10-osseu-reuse-licensing/firstslide.jpg b/content/blog/2019-10-osseu-reuse-licensing/firstslide.jpg new file mode 100644 index 0000000..2ee3a31 Binary files /dev/null and b/content/blog/2019-10-osseu-reuse-licensing/firstslide.jpg differ diff --git a/content/blog/2019-10-osseu-reuse-licensing/index.md b/content/blog/2019-10-osseu-reuse-licensing/index.md new file mode 100644 index 0000000..f9646a5 --- /dev/null +++ b/content/blog/2019-10-osseu-reuse-licensing/index.md @@ -0,0 +1,25 @@ +--- +title: "REUSE: Make licensing easy for everyone" +date: 2019-10-28 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: firstslide.jpg + alt: Title slide of my presentation at Open Source Summit Europe 2019 in Lyon + processes: + - fill 1000x440 center webp +slides: https://download.fsfe.org/presentations/20191028-mm-OSSEU-REUSE.en.pdf +event: + name: Open Source Summit Europe 2019 + href: https://osseu19.sched.com/event/05a3272287d3def1bcb0a62ace00b730 +--- + +At the Open Source Summit Europe 2019 in Lyon, I presented REUSE to an audience of enterprise Open Source professionals, developers, and decision-makers. The Open Source Summit, organized by the Linux Foundation, brings together the commercial and community sides of Open Source, making it an ideal venue to discuss how REUSE addresses licensing challenges that affect both worlds. The talk emphasized how REUSE makes licensing straightforward for everyone: from individual contributors to large organizations managing complex Open Source portfolios. + +The presentation focused on the practical solutions to typical problems with licensing information: unclear licensing and copyright of individual files, conflicting best practices, and loss of such information during use and re-use of files and components. I explained the three core REUSE rules and showed how the tooling integrates with existing development workflows and CI/CD pipelines. For the enterprise-focused audience, I highlighted how REUSE helps organizations that both consume and contribute to Open Source software, providing clear documentation that satisfies legal teams while remaining developer-friendly. + +The discussion revealed strong interest from companies dealing with complex multi-license scenarios and those seeking to improve their Open Source practices. REUSE offered a solution that bridges the gap between legal requirements and development realities -- exactly what many organizations were looking for as Open Source became increasingly central to their technology stacks. diff --git a/content/blog/2019-10-system-hackers-meeting-report.md b/content/blog/2019-10-system-hackers-meeting-report.md index d762a2a..9a88b79 100644 --- a/content/blog/2019-10-system-hackers-meeting-report.md +++ b/content/blog/2019-10-system-hackers-meeting-report.md @@ -2,13 +2,14 @@ title: The 3rd FSFE System Hackers hackathon date: 2019-10-22 categories: + - blog - english tags: - - fsfe - - report - - server -headerimage: /blog/system-chaos.jpg -headercredits: Fortunately not how the FSFE's infrastructure looks like + - FSFE + - SystemAdministration +headerimage: + src: /blog/system-chaos.jpg + text: Fortunately not how the FSFE's infrastructure looks like --- diff --git a/content/blog/2020-02-fosdem-reuse-license-your-code/fosdem-2020.jpg b/content/blog/2020-02-fosdem-reuse-license-your-code/fosdem-2020.jpg new file mode 100644 index 0000000..2b154bf Binary files /dev/null and b/content/blog/2020-02-fosdem-reuse-license-your-code/fosdem-2020.jpg differ diff --git a/content/blog/2020-02-fosdem-reuse-license-your-code/index.md b/content/blog/2020-02-fosdem-reuse-license-your-code/index.md new file mode 100644 index 0000000..9caff31 --- /dev/null +++ b/content/blog/2020-02-fosdem-reuse-license-your-code/index.md @@ -0,0 +1,27 @@ +--- +title: "Go REUSE to license your code" +date: 2020-02-02 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: fosdem-2020.jpg + text: Picture of me giving the presentation at FOSDEM 2020 in Brussels + alt: Max Mehl during his presentation at FOSDEM 2020 in Brussels + processes: + - fill 1000x440 bottom webp +video: https://www.youtube.com/watch?v=vyAYKROvTO8 +slides: https://download.fsfe.org/presentations/20200202-mm-FOSDEM-REUSE.en.pdf +event: + name: FOSDEM 2020 + href: https://fosdem.org/2020/schedule/event/reuse_code_licensing/ +--- + +At FOSDEM 2020, I presented "Go REUSE to license your code" in the Legal and Policy Issues Devroom. This talk marked an important milestone in the REUSE initiative's evolution, as we were seeing increasing adoption across diverse projects and growing recognition of licensing clarity as a critical aspect of software quality. The presentation encouraged developers to adopt REUSE practices for their own projects, showing that proper licensing doesn't have to be complicated or time-consuming. + +The talk walked through the three simple REUSE rules and demonstrated hands-on how developers could implement them in their projects. I showcased the REUSE helper tool which automates compliance checking, the REUSE API for displaying compliance badges, and showed real examples from projects that had successfully adopted REUSE. A key message was that REUSE is not only about legal compliance but respect for maintainers, clarity for users, and building a sustainable Free Software ecosystem where licensing information is always clear and accessible. + +The discussion after the talk focused on practical questions about edge cases, integration with existing workflows, and how to gradually improve licensing in legacy codebases. This was exactly the kind of community-driven conversation that helps initiatives like REUSE evolve to meet real-world needs. diff --git a/content/blog/2020-02-ilovefs-2020.md b/content/blog/2020-02-ilovefs-2020.md index 72d00b8..56a9661 100644 --- a/content/blog/2020-02-ilovefs-2020.md +++ b/content/blog/2020-02-ilovefs-2020.md @@ -2,13 +2,15 @@ title: I love the hidden champions date: 2020-02-14 categories: + - blog - english tags: - - ilovefs - - fsfe - - bash -headerimage: /blog/hidden-street.jpg -headercredits: The unknown Free Software contributors. Photo by Kaique Rocha + - ILoveFS + - FSFE + - Code +headerimage: + src: /blog/hidden-street.jpg + text: The unknown Free Software contributors. Photo by Kaique Rocha --- diff --git a/content/blog/2020-02-winterkongress-it-security/index.md b/content/blog/2020-02-winterkongress-it-security/index.md new file mode 100644 index 0000000..e5df62c --- /dev/null +++ b/content/blog/2020-02-winterkongress-it-security/index.md @@ -0,0 +1,23 @@ +--- +title: "Keine IT-Sicherheit ohne Freie Software" +date: 2020-02-22 +categories: + - deutsch + - presentation +tags: + - Security + - FSFE +headerimage: + src: winterkongress-2020.jpg + text: Bild von mir bei der Präsentation auf dem Winterkongress Digitale Gesellschaft Schweiz + alt: Max Mehl während seiner Präsentation auf dem Winterkongress Digitale Gesellschaft Schweiz 2020 +video: https://www.youtube.com/watch?v=6MW9a5fPX-k +slides: https://download.fsfe.org/presentations/20200222-mm-Winterkongress-ITSec.de.pdf +event: + name: Winterkongress Digitale Gesellschaft CH + href: https://www.winterkongress.ch/2020/talks/keine_it-sicherheit_ohne_freie_software/ +--- + +Beim Winterkongress der Digitalen Gesellschaft Schweiz hielt ich einen Vortrag über den fundamentalen Zusammenhang zwischen IT-Sicherheit und Freier Software/Open Source. Die Kernthese war provokant formuliert, aber technisch begründet: Echte IT-Sicherheit ist ohne Freie Software nicht möglich. In einer Zeit, in der Cybersecurity zunehmend als kritisches Thema für Gesellschaft, Wirtschaft und Staat wahrgenommen wurde, argumentierte ich, dass proprietäre Software strukturelle Sicherheitsprobleme mit sich bringt, die nicht einfach durch bessere Praktiken gelöst werden können. + +Der Vortrag beleuchtete mehrere Dimensionen dieses Arguments: Transparenz als Voraussetzung für Vertrauen, die Notwendigkeit unabhängiger Sicherheitsüberprüfungen, das Problem von Hintertüren und nicht offengelegten Schwachstellen in Closed-Source-Software, sowie die Bedeutung von Vendor-Unabhängigkeit für langfristige Sicherheitsupdates. Für das Publikum beim Winterkongress, das sich für digitale Bürgerrechte und eine demokratische digitale Gesellschaft einsetzt, war diese Verbindung zwischen Freiheit und Sicherheit besonders relevant. Der Vortrag zeigte, dass es kein Widerspruch ist, gleichzeitig für Softwarefreiheit und für Sicherheit einzutreten. Ganz im Gegenteil: das eine setzt das andere voraus. diff --git a/content/blog/2020-02-winterkongress-it-security/winterkongress-2020.jpg b/content/blog/2020-02-winterkongress-it-security/winterkongress-2020.jpg new file mode 100644 index 0000000..6b9a67f Binary files /dev/null and b/content/blog/2020-02-winterkongress-it-security/winterkongress-2020.jpg differ diff --git a/content/blog/2020-03-system-hackers-report-lyon.md b/content/blog/2020-03-system-hackers-report-lyon.md index d6c1cd5..1ea17a2 100644 --- a/content/blog/2020-03-system-hackers-report-lyon.md +++ b/content/blog/2020-03-system-hackers-report-lyon.md @@ -2,13 +2,14 @@ title: System Hackers meeting - Lyon edition date: 2020-03-31 categories: + - blog - english tags: - - fsfe - - report - - server -headerimage: /blog/syshackers-group-hacking.jpg -headercredits: Hackers in their natural working environment. For the picture we took off the black ski masks and gloves. + - FSFE + - SystemAdministration +headerimage: + src: /blog/syshackers-group-hacking.jpg + text: Hackers in their natural working environment. For the picture we took off the black ski masks and gloves. --- diff --git a/content/blog/2020-04-librezoom-freedom-security-podcast/index.md b/content/blog/2020-04-librezoom-freedom-security-podcast/index.md new file mode 100644 index 0000000..7a36c99 --- /dev/null +++ b/content/blog/2020-04-librezoom-freedom-security-podcast/index.md @@ -0,0 +1,22 @@ +--- +title: "Führt mehr Freiheit zu mehr Sicherheit?" +date: 2020-04-01 +categories: + - deutsch + - podcast +tags: + - Security + - FSFE +headerimage: + src: librezoom.jpg +audio: https://up.mehl.mx/audio/20200401-librezoom-itsec.mp3 +event: + name: Librezoom Podcast + href: http://web.archive.org/web/20230603153954/https://librezoom.net/lz20-paradox/ +--- + +Im Librezoom-Podcast LZ20 mit dem Host Ralf Hersel gab ich ein Interview zur Frage, ob mehr Freiheit zu mehr Sicherheit führt – ein scheinbares Paradoxon in der IT-Sicherheitsdebatte. Viele Menschen assoziieren Sicherheit mit Kontrolle und Einschränkungen, während Freie und Open Source Software auf Offenheit setzt. In diesem Gespräch ging ich der Frage nach, warum diese scheinbare Dichotomie in der Realität keine ist und wie Freie Software tatsächlich fundamentale Voraussetzungen für echte IT-Sicherheit schafft. + +Wir diskutierten über verschiedene Aspekte: Transparenz durch Quellcode-Offenheit, die Möglichkeit unabhängiger Sicherheitsaudits, die Bedeutung von Kontrolle über die eigene Software-Infrastruktur, und warum proprietäre "Sicherheit by Obscurity" ein gefährlicher Trugschluss ist. Das Interview beleuchtete auch praktische Beispiele, wo Closed-Source-Software zu Sicherheitsproblemen führte, während Freie Software Alternativen robustere Lösungen bot. + +Diese Diskussion war besonders relevant in einer Zeit, in der IT-Sicherheit zunehmend als Begründung für mehr Überwachung und weniger digitale Freiheiten herangezogen wurde. Das Interview argumentierte, dass echter Schutz nicht durch Einschränkung von Freiheit, sondern durch deren Ermöglichung erreicht wird. diff --git a/content/blog/2020-04-librezoom-freedom-security-podcast/librezoom.jpg b/content/blog/2020-04-librezoom-freedom-security-podcast/librezoom.jpg new file mode 100644 index 0000000..a11b2f0 Binary files /dev/null and b/content/blog/2020-04-librezoom-freedom-security-podcast/librezoom.jpg differ diff --git a/content/blog/2020-07-the-power-of-git-sed.md b/content/blog/2020-07-the-power-of-git-sed.md index 118f109..4074ad3 100644 --- a/content/blog/2020-07-the-power-of-git-sed.md +++ b/content/blog/2020-07-the-power-of-git-sed.md @@ -2,13 +2,14 @@ title: "The power of git-sed" date: 2020-07-28 categories: + - blog - english tags: - - tools - - bash - - fsfe -headerimage: /blog/git-sed.png -headercredits: Replacing content in thousands of files? No problem! + - Code + - FSFE +headerimage: + src: /blog/git-sed.png + text: Replacing content in thousands of files? No problem! --- In the recent weeks and months, the [FSFE Web Team](https://fsfe.org/contribute/web/) has been doing some heavy work on the [FSFE website](https://fsfe.org). We moved and replaced thousands of files and their respective links to improve the structure of a historically grown website (19+ years, 23243 files, almost 39k commits). But how to do that most efficiently in a version controlled system like Git? diff --git a/content/blog/2020-11-netzpolitik-youtube-dl-musikindustrie/index.md b/content/blog/2020-11-netzpolitik-youtube-dl-musikindustrie/index.md new file mode 100644 index 0000000..d3d4e99 --- /dev/null +++ b/content/blog/2020-11-netzpolitik-youtube-dl-musikindustrie/index.md @@ -0,0 +1,23 @@ +--- +title: "youtube-dl: Musikindustrie schießt mit der Schrotflinte auf Open Source (Netzpolitik)" +date: 2020-11-06 +categories: + - deutsch + - article +tags: + - DRM +headerimage: + src: schrotflinte.jpg +summary: Ich wurde von Netzpolitik.org zum aggressiven Vorgehen der Musikindustrie gegen youtube-dl befragt. Als FSFE-Programm-Manager erklärte ich, dass Multifunktionswerkzeuge wie youtube-dl für zahlreiche legale Zwecke genutzt werden – von Journalist:innen über Wissenschaftler:innen bis zu Menschenrechtsorganisationen wie Amnesty International. Das Problem ist, dass Freie-Software-Projekte sich teure Rechtsstreite oft nicht leisten können. +article: + name: Netzpolitik.org + href: https://netzpolitik.org/2020/youtube-dl-musikindustrie-schiesst-mit-der-schrotflinte-auf-open-source/ +--- + +Ich wurde von Netzpolitik.org zur DMCA-Abmahnung der Musikindustrie gegen youtube-dl befragt und erklärte die Problematik von Multifunktionswerkzeugen: „Genau wie mit Webbrowsern, Verschlüsselungstools und zahlreichen anderen Programmen kann man damit legale und illegale Dinge tun." Die Software wird nicht nur zum Download von Musik genutzt, sondern ist auch bei Journalist:innen, Wissenschaftler:innen und Aktivist:innen beliebt. Amnesty International empfiehlt das Tool etwa, um Beweise zu sichern, und die FSFE nutzt es, um eigene Videos von diversen Plattformen zu spiegeln. + +Zum Vorgehen der RIAA äußerte ich: + +> Freie-Software-Projekte und unabhängige Hosting-Plattformen können sich teure Rechtsstreite oft nicht leisten, auch wenn Multifunktionswerkzeuge wie youtube-dl für legale Zwecke konzipiert werden. Deren illegale Verwendung sollte sanktioniert werden, nicht die Bereitstellung und legale Nutzung. + +Es werden auch die rechtlichen Grauzonen um YouTubes "Rolling Cipher" und die Kollateralschäden für Webhoster und Fork-Entwickler beleuchtet. Der [vollständige Artikel](https://netzpolitik.org/2020/youtube-dl-musikindustrie-schiesst-mit-der-schrotflinte-auf-open-source/) mit allen rechtlichen Details ist auf Netzpolitik.org verfügbar. diff --git a/content/blog/2020-11-netzpolitik-youtube-dl-musikindustrie/schrotflinte.jpg b/content/blog/2020-11-netzpolitik-youtube-dl-musikindustrie/schrotflinte.jpg new file mode 100644 index 0000000..a1d156e Binary files /dev/null and b/content/blog/2020-11-netzpolitik-youtube-dl-musikindustrie/schrotflinte.jpg differ diff --git a/content/blog/2021-01-gnulinuxnews-podcast/gnulinux-podcast.jpg b/content/blog/2021-01-gnulinuxnews-podcast/gnulinux-podcast.jpg new file mode 100644 index 0000000..6cdd5cb Binary files /dev/null and b/content/blog/2021-01-gnulinuxnews-podcast/gnulinux-podcast.jpg differ diff --git a/content/blog/2021-01-gnulinuxnews-podcast/index.md b/content/blog/2021-01-gnulinuxnews-podcast/index.md new file mode 100644 index 0000000..0f89499 --- /dev/null +++ b/content/blog/2021-01-gnulinuxnews-podcast/index.md @@ -0,0 +1,28 @@ +--- +title: "Zu Gast beim GNU/Linux-Podcast #6 - Android und Public Money, Public Code" +slug: zu-gast-beim-gnu-linux-podcast-6-android-und-public-money-public-code +date: 2021-01-02 +categories: + - deutsch + - podcast +tags: + - Android + - PublicCode + - Policy + - FSFE +headerimage: + src: gnulinux-podcast.jpg + alt: Illustration of the Gnu and Linux Penguin mascots. Below the text "Podcast" + processes: + - fill 1000x440 center webp +audio: https://gnulinux.ch/podcast/GLN_006.mp3 +event: + name: GnuLinuxNews Podcast \#6 + href: https://gnulinux.ch/gln006-podcast +--- + +Ich war als Gast bei der sechsten Ausgabe des GnuLinuxNews-Podcasts zu Gast, wo wir über verschiedene Themen aus der Welt von Free and Open Source Software sprachen. Der GnuLinuxNews-Podcast richtet sich an die deutschsprachige Linux- und Freie-Software-Community und behandelt aktuelle Entwicklungen, Projekte und politische Themen rund um Freie Software. In dieser Ausgabe diskutierten wir insbesondere über Android und dessen Beziehung zu Freier Software sowie über "Public Money, Public Code". + +Ein Schwerpunkt lag auf dem Android-Ökosystem und den Herausforderungen und Chancen für Freie Software in diesem Bereich. Wir sprachen über die Unterschiede zwischen dem AOSP (Android Open Source Project) und den proprietären Google-Diensten, über alternative App-Stores wie F-Droid, und wie Nutzer mehr Kontrolle über ihre Android-Geräte erlangen können. Außerdem beleuchteten wir die "Public Money, Public Code"-Kampagne der FSFE und warum es wichtig ist, dass öffentlich finanzierte Software als Freie Software veröffentlicht wird. + +Der Podcast bot eine gute Gelegenheit, diese Themen in einem lockeren, aber informativen Format für ein deutschsprachiges Publikum aufzubereiten und praktische Tipps mit politischen Diskussionen zu verbinden. diff --git a/content/blog/2021-02-fosdem-legal-policy-devroom-organizers/fosdem-2021.jpg b/content/blog/2021-02-fosdem-legal-policy-devroom-organizers/fosdem-2021.jpg new file mode 100644 index 0000000..ce2e910 Binary files /dev/null and b/content/blog/2021-02-fosdem-legal-policy-devroom-organizers/fosdem-2021.jpg differ diff --git a/content/blog/2021-02-fosdem-legal-policy-devroom-organizers/index.md b/content/blog/2021-02-fosdem-legal-policy-devroom-organizers/index.md new file mode 100644 index 0000000..8419c85 --- /dev/null +++ b/content/blog/2021-02-fosdem-legal-policy-devroom-organizers/index.md @@ -0,0 +1,22 @@ +--- +title: "Panel: Hot Topics - Organizers of the Legal & Policy DevRoom" +date: 2021-02-07 +categories: + - english + - presentation +tags: + - Community +headerimage: + src: fosdem-2021.jpg + alt: Title slide of the panel with the session title and the names of the organizers, in the FOSDEM 2021 style +video: https://www.youtube.com/watch?v=WgnDGpJhlAI +event: + name: FOSDEM 2021 + href: https://archive.fosdem.org/2021/schedule/event/organizerslegalpolicy/ +--- + +At FOSDEM 2021, I participated in the annual panel of Legal & Policy DevRoom organizers where we discussed the hot topics from the track's presentations that year. This panel tradition brings together the organizers to reflect on the most pressing legal and policy issues facing Free and Open Source Software, based on the talks and discussions throughout the day. It provided an opportunity to synthesize the diverse perspectives presented in the DevRoom and look ahead to emerging challenges. + +As one of the organizers, I joined my co-organizers Bradley Kuhn, Karen Sandler, Richard Fontana, and Alexander Sander to discuss topics ranging from licensing compliance and governance models to emerging regulatory frameworks affecting FOSS. The panel format allowed us to draw connections between different presentations, highlight recurring themes, and engage with questions from the community about how legal and policy matters would evolve in the coming year. + +This type of meta-discussion is valuable because it helps the FOSS community understand not just individual legal or policy issues, but how these challenges interconnect and what broader trends we should be watching. The Legal & Policy Devroom continues to be a crucial space for these conversations at FOSDEM. diff --git a/content/blog/2021-02-fosdem-reuse-best-practices/fosdem-2021-reuse.jpg b/content/blog/2021-02-fosdem-reuse-best-practices/fosdem-2021-reuse.jpg new file mode 100644 index 0000000..1ebab5b Binary files /dev/null and b/content/blog/2021-02-fosdem-reuse-best-practices/fosdem-2021-reuse.jpg differ diff --git a/content/blog/2021-02-fosdem-reuse-best-practices/index.md b/content/blog/2021-02-fosdem-reuse-best-practices/index.md new file mode 100644 index 0000000..8642b22 --- /dev/null +++ b/content/blog/2021-02-fosdem-reuse-best-practices/index.md @@ -0,0 +1,27 @@ +--- +title: "REUSE: Best practices for declaring copyright and licenses" +date: 2021-02-06 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: fosdem-2021-reuse.jpg + text: Me giving the remote presentation at FOSDEM 2021 - it's been Covid times! + alt: Max Mehl during his online presentation at FOSDEM 2021 + processes: + - fill 1000x440 bottom webp +video: https://www.youtube.com/watch?v=JXwHgPfR9UQ +slides: https://download.fsfe.org/presentations/20210206-mm-FOSDEM-REUSE.en.pdf +event: + name: FOSDEM 2021 + href: https://archive.fosdem.org/2021/schedule/event/reuse/ +--- + +At FOSDEM 2021, I delivered a presentation on REUSE best practices for declaring copyright and licenses in Free and Open Source Software projects. The talk was part of FOSDEM's OpenChain track, where developers and legal professionals gather to discuss these critical topics. I focused on how REUSE provides a practical, standardized approach to one of the most common yet frustrating problems in FOSS development: maintaining clear licensing information. + +The presentation walked through the three simple steps that comprise REUSE: adding copyright and licensing information to each file, providing full license texts in a standard location, and confirming complete REUSE adoption. I demonstrated the REUSE helper tool which automates compliance checking and can be integrated into CI/CD pipelines. Real-world examples showed how projects of various sizes have successfully adopted REUSE, and I addressed common questions about legacy codebases, third-party dependencies, and multi-license projects. + +The timing was significant as more organizations were recognizing the importance of licensing clarity for compliance, security auditing, and supply chain management. REUSE provides a solution that's both developer-friendly and meets the requirements of legal and compliance teams, making it increasingly relevant as FOSS becomes critical infrastructure. diff --git a/content/blog/2021-03-libreplanet-reuse/index.md b/content/blog/2021-03-libreplanet-reuse/index.md new file mode 100644 index 0000000..03f537c --- /dev/null +++ b/content/blog/2021-03-libreplanet-reuse/index.md @@ -0,0 +1,27 @@ +--- +title: "REUSE: Best practices for declaring copyright and licenses" +date: 2021-03-21 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: libreplanet-2021.jpg + text: Me giving the presentation at LibrePlanet 2021 + alt: Max Mehl during his presentation at LibrePlanet 2021 + processes: + - fill 1000x440 center webp +video: https://framatube.org/w/beb7ce0c-635f-4f54-b1c5-3f620276e54b +slides: https://download.fsfe.org/presentations/20210321-mm-LibrePlanet-REUSE.en.pdf +event: + name: LibrePlanet 2021 + href: https://libreplanet.org/2021/speakers/#4663 +--- + +At LibrePlanet 2021, I presented the REUSE initiative as a set of best practices for declaring copyright and licenses in Free Software projects. LibrePlanet is the Free Software Foundation's annual conference celebrating software freedom, making it an ideal venue to discuss how REUSE helps uphold the principles that the community values most. The talk focused on how clear licensing and copyright information benefits both developers and users of Free Software. + +I explained the three core REUSE rules: including copyright and licensing information in each file, providing full license texts, and confirming full REUSE adoption by running an easy check. The presentation showed practical examples of how projects can implement these practices incrementally, demonstrated the REUSE helper tool for automated compliance checking, and discussed how REUSE aligns with Free Software philosophy by ensuring that software freedom is clearly documented and easily verifiable. + +The talk resonated especially well with the LibrePlanet audience, as many attendees work on software freedom advocacy and understand first-hand how licensing ambiguity can undermine the goals of Free Software. diff --git a/content/blog/2021-03-libreplanet-reuse/libreplanet-2021.jpg b/content/blog/2021-03-libreplanet-reuse/libreplanet-2021.jpg new file mode 100644 index 0000000..74f2878 Binary files /dev/null and b/content/blog/2021-03-libreplanet-reuse/libreplanet-2021.jpg differ diff --git a/content/blog/2021-04-europe-direct-digital-sovereignty/europedirect-digital-sovereignty.jpg b/content/blog/2021-04-europe-direct-digital-sovereignty/europedirect-digital-sovereignty.jpg new file mode 100644 index 0000000..bfc2ab1 Binary files /dev/null and b/content/blog/2021-04-europe-direct-digital-sovereignty/europedirect-digital-sovereignty.jpg differ diff --git a/content/blog/2021-04-europe-direct-digital-sovereignty/index.md b/content/blog/2021-04-europe-direct-digital-sovereignty/index.md new file mode 100644 index 0000000..b96cba1 --- /dev/null +++ b/content/blog/2021-04-europe-direct-digital-sovereignty/index.md @@ -0,0 +1,22 @@ +--- +title: "Digitale Souveränität in Europa - Freie und Open Source Software als Schlüssel" +date: 2021-04-15 +categories: + - deutsch + - presentation +tags: + - Sovereignty +headerimage: + src: europedirect-digital-sovereignty.jpg + alt: Teaserbild der Veranstaltung von Europe Direct Dortmund zum Thema digitale Souveränität in Europa +slides: https://download.fsfe.org/presentations/20210415-mm-EuropeDirect-DigiSouv.de.pdf +event: + name: Europe Direct Dortmund + href: https://www.europe-direct-dortmund.de/event/digitale-souveraenitaet-in-europa-freie-und-open-source-software-als-schluessel/ +--- + +Bei Europe Direct Dortmund hielt ich einen Vortrag über digitale Souveränität in Europa und die zentrale Rolle, die Freie und Open Source Software dabei spielt. Der Vortrag beleuchtete, wie abhängig Europa von proprietären Softwarelösungen geworden ist und welche Risiken diese Abhängigkeit für demokratische Institutionen, wirtschaftliche Wettbewerbsfähigkeit und technologische Selbstbestimmung mit sich bringt. Ich argumentierte, dass echte digitale Souveränität nur durch den strategischen Einsatz und die Förderung Freier Software erreicht werden kann. + +Die Präsentation zeigte konkrete Beispiele, wie Freie Software Europa mehr Kontrolle über seine digitale Infrastruktur geben kann – von öffentlichen Verwaltungen über Bildungseinrichtungen bis hin zu kritischen Infrastrukturen. Ich diskutierte die Bedeutung offener Standards, die Wichtigkeit von Transparenz und Überprüfbarkeit in Software, und wie die Prinzipien von "Public Money, Public Code" dazu beitragen können, eine nachhaltige und souveräne digitale Zukunft für Europa aufzubauen. + +Der Vortrag betonte, dass digitale Souveränität nicht bedeutet, Europa von der Welt abzuschotten, sondern vielmehr die Fähigkeit zu entwickeln, eigene technologische Entscheidungen zu treffen und an offenen, internationalen Entwicklungsmodellen auf Augenhöhe teilzunehmen. diff --git a/content/blog/2021-06-ow2con-reuse-easy/index.md b/content/blog/2021-06-ow2con-reuse-easy/index.md new file mode 100644 index 0000000..9ed26be --- /dev/null +++ b/content/blog/2021-06-ow2con-reuse-easy/index.md @@ -0,0 +1,26 @@ +--- +title: "REUSE - Make licensing easy for everyone" +date: 2021-06-23 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: ow2con-2021.jpg + alt: Intro slide of my presentation at OW2con 2021, showing the title "REUSE - Make licensing easy for everyone" and the OW2con 2021 branding + processes: + - fill 1000x440 top webp +video: https://www.youtube.com/watch?v=O5lgD01dc-c +slides: https://download.fsfe.org/presentations/20210623-mm-OW2Con-REUSE.en.pdf +event: + name: OW2con 2021 + href: https://www.ow2con.org/view/2021/Videos#H21REUSE-Makelicensingeasyforeveryone2CMaxMehl40FreeSoftwareFoundationEurope28FSFE29 +--- + +At OW2con 2021, I presented REUSE to an audience deeply involved in Open Source infrastructure projects and close to public authorities and French businesses. The talk emphasized how REUSE makes Free Software licensing accessible and manageable for everyone – from individual developers to large organizations managing complex codebases. This was particularly relevant for the OW2 community, where projects often involve multiple contributors, dependencies, and licensing considerations across international boundaries. + +The presentation walked through the core REUSE principles and showed how they address common licensing pain points: unclear copyright holders, ambiguous license terms, and missing attribution. I demonstrated the REUSE tools and workflow, showing how projects can verify their compliance status and incrementally improve their licensing documentation. The talk also covered how REUSE integrates with continuous integration systems and can become part of a project's regular quality assurance process. + +For the OW2 community, known for its focus on collaborative Open Source development and professional-grade software, REUSE offered a pragmatic path to licensing clarity that reduces legal uncertainty while maintaining development velocity. The discussion highlighted how proper licensing documentation becomes even more critical as projects scale and are used in production environments. diff --git a/content/blog/2021-06-ow2con-reuse-easy/ow2con-2021.jpg b/content/blog/2021-06-ow2con-reuse-easy/ow2con-2021.jpg new file mode 100644 index 0000000..f3f6c4d Binary files /dev/null and b/content/blog/2021-06-ow2con-reuse-easy/ow2con-2021.jpg differ diff --git a/content/blog/2021-07-bild-nina-flop-warning-app/bild-godzilla-nina.jpg b/content/blog/2021-07-bild-nina-flop-warning-app/bild-godzilla-nina.jpg new file mode 100644 index 0000000..880fd30 Binary files /dev/null and b/content/blog/2021-07-bild-nina-flop-warning-app/bild-godzilla-nina.jpg differ diff --git a/content/blog/2021-07-bild-nina-flop-warning-app/index.md b/content/blog/2021-07-bild-nina-flop-warning-app/index.md new file mode 100644 index 0000000..4d83498 --- /dev/null +++ b/content/blog/2021-07-bild-nina-flop-warning-app/index.md @@ -0,0 +1,30 @@ +--- +title: "Der große NINA-Flop (BILD)" +date: 2021-07-22 +categories: + - deutsch + - article +tags: + - CellBroadcast + - FSFE +headerimage: + src: bild-godzilla-nina.jpg +summary: Nach der verheerenden Flutkatastrophe in Deutschland im Juli 2021 veröffentlichte BILD einen Artikel, der das Versagen der NINA-Warn-App kritisierte. Ich wurde zu den technischen Grenzen des zentralisierten Warnsystems und zu resilienteren Alternativen wie Cell Broadcast befragt, die alle Menschen erreichen können, ohne dass eine App installiert werden muss. +article: + name: BILD + href: https://web.archive.org/web/20210722020854/https://www.bild.de/politik/inland/politik-inland/der-grosse-nina-flop-app-warnte-vor-monster-angriff-77153478.bild.html +--- + +Nach der verheerenden Flutkatastrophe in Deutschland im Juli 2021 veröffentlichte BILD einen Artikel, der das Versagen der NINA-Warn-App kritisierte, nicht genug Menschen während der Katastrophe zu erreichen. Der Artikel hebt hervor, dass die App trotz rund 9 Millionen Downloads nur etwa ein Zehntel der Bevölkerung erreichte und viele Menschen nicht ausreichend vor den Fluten gewarnt wurden. + +Ich wurde im Artikel zu den technischen Problemen mit NINA und dem zentralisierten Warnsystem zitiert: + +> Kritik an NINA kommt auch von Max Mehl (Free Software Foundation Europe): Da NINA keine freie Software sei, könne sie auch nicht durch die Öffentlichkeit oder unabhängige Experten überprüft werden. Am bundesweiten Warntag 2020 versagte NINA schließlich komplett. +> +> Der Flaschenhals des Systems laut Mehl: das zentrale Warnsystem, durch das auch NINA mit Infos gefüttert wird. Damals sei die App förmlich verstopft worden mit Informationen und habe die Warnungen „nur zeitversetzt oder gar nicht" abgesetzt. Im echten Katastrophenfall fatal! +> +> Der Experte zu BILD: „Wenn Sie die Bewohner einer Straße informieren wollen, ist es mit Sicherheit schneller, laute Durchsagen mit Megafonen zu machen, als an jeder Haustür einzeln zu klopfen und die Nachricht zu überbringen." Genauso wie das Haustür-Verfahren funktioniere aber die Warnung per App. + +Der Artikel diskutiert, wie Warnungen Menschen automatisch erreichen müssen und nicht davon abhängig sein dürfen, dass sie eine App installieren. + +Der vollständige Artikel kann auf der archivierten BILD-Seite gelesen werden (siehe Link oben). diff --git a/content/blog/2021-07-fsfe-podcast-reuse-booster/index.md b/content/blog/2021-07-fsfe-podcast-reuse-booster/index.md new file mode 100644 index 0000000..e29495e --- /dev/null +++ b/content/blog/2021-07-fsfe-podcast-reuse-booster/index.md @@ -0,0 +1,25 @@ +--- +title: "REUSE Booster and update on REUSE - FSFE Podcast" +date: 2021-07-02 +categories: + - english + - podcast +tags: + - REUSE + - FSFE +headerimage: + src: software-freedom-podcast.jpg + alt: Logo of the FSFE Software Freedom Podcast + processes: + - fill 1000x440 center webp +audio: https://download.fsfe.org/audio/podcast/SFP011.mp3 +event: + name: FSFE Software Freedom Podcast + href: https://fsfe.org/news/podcast/2021/episode-11.html +--- + +In the 11th episode of the FSFE Software Freedom Podcast, I joined my colleague Bonnie Mehring to discuss the [REUSE initiative](https://reuse.software) and the newly launched REUSE Booster programme. This marked the first time that an FSFE staff member appeared on the podcast, and it was a great opportunity to provide an accessible introduction to REUSE for listeners who might find software licensing complex and intimidating. As the FSFE programme manager responsible for REUSE and one of the REUSE tool's maintainers, I shared insights into how REUSE makes licensing easier for both developers and users. + +The conversation covered the fundamentals of REUSE, a standard for modern licensing of Free Software projects that has been widely adopted by Open Source communities like KDE and a number of companies. I explained how REUSE's three simple steps remove the ambiguity and friction from Free Software licensing. We discussed the development of the community around REUSE, the tools we've built to automate compliance checking, and how major projects have successfully implemented REUSE practices. + +A key focus was the newly launched REUSE Booster programme, which we announced just weeks before this podcast episode. This activity offers hands-on support to Free Software projects wanting to adopt REUSE, providing direct assistance from our team to make the transition as smooth as possible. The podcast positioned REUSE Booster as the perfect entry point for projects that understood the value of clear licensing but weren't sure where to start. By making licensing best practices accessible and practical, REUSE helps the entire Free Software ecosystem build more sustainable, legally clear projects. diff --git a/content/blog/2021-07-fsfe-podcast-reuse-booster/software-freedom-podcast.jpg b/content/blog/2021-07-fsfe-podcast-reuse-booster/software-freedom-podcast.jpg new file mode 100644 index 0000000..6a02502 Binary files /dev/null and b/content/blog/2021-07-fsfe-podcast-reuse-booster/software-freedom-podcast.jpg differ diff --git a/content/blog/2021-07-heise-red-open-source-radio-lockdown/index.md b/content/blog/2021-07-heise-red-open-source-radio-lockdown/index.md new file mode 100644 index 0000000..193cf80 --- /dev/null +++ b/content/blog/2021-07-heise-red-open-source-radio-lockdown/index.md @@ -0,0 +1,29 @@ +--- +title: "RED-Umsetzung: Open-Source-Szene droht Ausschluss aus der Funktechnik (heise online)" +date: 2021-07-06 +categories: + - deutsch + - article +tags: + - RadioLockdown + - Policy + - FSFE + - FSFE +headerimage: + src: router-in-ketten.webp + text: "Quelle: c't" +summary: Heise/c't magazin berichtete über die Pläne der EU-Kommission, die Funkanlagenrichtlinie (RED) mit Vorschriften umzusetzen, die effektiv alle Funkgeräte sperren könnten. Als Programm-Manager der FSFE wurde ich zitiert und warnte vor der Bedrohung für Open-Source-Projekte wie Freifunk, OpenWrt und das gesamte Internet-der-Dinge-Ökosystem, da die Anforderungen es nahezu unmöglich machen würden, alternative Software auf Geräten mit Funkmodulen zu installieren. +article: + name: heise online + href: https://www.heise.de/news/RED-Umsetzung-Open-Source-Szene-droht-Ausschluss-aus-der-Funktechnik-6129525.html?seite=all +--- + +Im Juli 2021 veröffentlichte Heise/c't magazin einen ausführlichen Artikel über die Pläne der EU-Kommission, die Funkanlagenrichtlinie (RED) mit neuen Standards und delegierten Rechtsakten umzusetzen. Die Richtlinie enthält Artikel 3(3)i, der verlangt, dass Funkanlagen nur Software laden können, deren Konformität nachgewiesen wurde - was effektiv einen Sperrmechanismus für alle Geräte mit Funkmodulen schafft. + +Der Artikel erklärt, wie dies die Open-Source- und Maker-Community bedroht, insbesondere Projekte wie Freifunk (Community-Drahtlosnetzwerke), Osmocom (freier Mobilfunk) und OpenWrt (Linux-Distribution für eingebettete Systeme). Es betrifft auch das gesamte Internet-der-Dinge-Ökosystem, da die meisten modernen Geräte Funkfunktionalität enthalten. + +Ich wurde als Programm-Manager der FSFE zu den ernsten Auswirkungen zitiert: + +> Auch die FSFE rechnet nach wie vor mit dem Schlimmsten. Expertentreffen hätten gezeigt, dass die Kommission die Tragweite des Problems nicht erkenne, moniert Programm-Manager Max Mehl. Mit einem delegierten Akt drohten noch weiter einschneidende Regeln. Dabei habe die Brüsseler Institution schon bei ihrer ersten Konsultation zu dem Thema viele kritische Kommentare bekommen. Darin werde etwa zu bedenken gegeben, dass Funk-Hardware künftig nur noch im Paket mit einer unveränderbaren proprietären Software der Hersteller verkauft werde. Die Freiheit zum Nutzen und Reparieren der Geräte wäre so massiv eingeschränkt. + +Der vollständige deutsche Artikel bietet umfangreiche technische Details und ist auf der Website von Heise verfügbar (siehe Link oben). diff --git a/content/blog/2021-07-heise-red-open-source-radio-lockdown/router-in-ketten.webp b/content/blog/2021-07-heise-red-open-source-radio-lockdown/router-in-ketten.webp new file mode 100644 index 0000000..74e4e8b Binary files /dev/null and b/content/blog/2021-07-heise-red-open-source-radio-lockdown/router-in-ketten.webp differ diff --git a/content/blog/2021-07-the-local-germany-disaster-warning-system/index.md b/content/blog/2021-07-the-local-germany-disaster-warning-system/index.md new file mode 100644 index 0000000..3d90270 --- /dev/null +++ b/content/blog/2021-07-the-local-germany-disaster-warning-system/index.md @@ -0,0 +1,30 @@ +--- +title: "Germany knew its disaster warning system wasn't good enough – why wasn't it improved? (The Local)" +date: 2021-07-30 +categories: + - english + - article +tags: + - CellBroadcast + - FSFE +summary: In the scope of my work with the FSFE regarding Cell Broadcast, I have been interviewed by The Local about the disaster warning system in Germany and whether a more open and resilient system could have prevented some damage during the Ahrtal floods in July 2021. The article discusses the known deficiencies of the existing system and explores why improvements were not made in time. +headerimage: + src: red-phone.jpg + processes: + - fill 1000x440 center webp +article: + name: The Local + href: https://www.thelocal.de/20210730/germany-knew-its-disaster-warning-system-wasnt-good-enough-why-wasnt-it-improved-2/ +--- + +In the scope of my work with the FSFE regarding Cell Broadcast, I have been interviewed by The Local about the disaster warning system in Germany and whether a more open and resilient system could have prevented some damage during the Ahrtal floods in July 2021. The article discusses the known deficiencies of the existing system and explores why improvements were not made in time. + +> Max Mehl of the association, Free Software Foundation Europe (FSFE), analysed Germany’s warning system along with experts in civil protection and mobile networking after the "Warntag" flop. +> +> They wanted to figure out why the apps failed, and what a more "resilient and open system" can look like. +> +> "Most prominently we found that the system architecture was not appropriate for the actual task,” he told The Local. "The warning day last year was quite realistic in this regard: a number of authorities issue warnings to parts of the population. However, everything goes via a central system and that was overloaded." +> +> Mehl said this caused the breakdown in issuing alerts through the app on the ‘warning day’. + +The article can be read in full on The Local's website, see above. It's behind a paywall, but you may find it on archive pages, e.g. [this one](https://archive.ph/Rcvm5). diff --git a/content/blog/2021-07-the-local-germany-disaster-warning-system/red-phone.jpg b/content/blog/2021-07-the-local-germany-disaster-warning-system/red-phone.jpg new file mode 100644 index 0000000..a835a86 Binary files /dev/null and b/content/blog/2021-07-the-local-germany-disaster-warning-system/red-phone.jpg differ diff --git a/content/blog/2021-09-eurobsdcon-reuse-simplify/eurobsdcon-2021.jpg b/content/blog/2021-09-eurobsdcon-reuse-simplify/eurobsdcon-2021.jpg new file mode 100644 index 0000000..a58b70a Binary files /dev/null and b/content/blog/2021-09-eurobsdcon-reuse-simplify/eurobsdcon-2021.jpg differ diff --git a/content/blog/2021-09-eurobsdcon-reuse-simplify/index.md b/content/blog/2021-09-eurobsdcon-reuse-simplify/index.md new file mode 100644 index 0000000..085afaa --- /dev/null +++ b/content/blog/2021-09-eurobsdcon-reuse-simplify/index.md @@ -0,0 +1,26 @@ +--- +title: "Simplify Licensing Code with REUSE" +date: 2021-09-17 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: eurobsdcon-2021.jpg + alt: Intro slide of my presentation at EuroBSDCon 2021, showing the title "Simplify Licensing Code with REUSE" and the EuroBSDCon 2021 branding + processes: + - fill 1000x440 top webp +video: https://www.youtube.com/watch?v=06aJomRgzFA +slides: https://download.fsfe.org/presentations/20210919-mm-EuroBSDcon-REUSE.en.pdf +event: + name: EuroBSDCon 2021 + href: https://2021.eurobsdcon.org/home/speakers/#simplify +--- + +At EuroBSDCon 2021, I introduced the REUSE initiative to the OpenBSD community, demonstrating how this approach can simplify licensing practices for Free and Open Source Software communities like theirs. The talk focused on the practical challenges developers face when trying to properly license their code and how REUSE's three simple rules can solve these problems. This presentation was particularly relevant for the OpenBSD ecosystem, where licensing clarity and permissive licenses play a central role in the community's values. + +I walked through real-world examples of licensing ambiguity and its consequences, then showed how REUSE's straightforward approach – adding licensing information to each file, including license texts in a standard location, and confirming full adoption – removes these pain points. The talk covered the REUSE helper tool, which automates much of the compliance work, and demonstrated how projects can adopt REUSE gradually without disrupting their existing workflows. + +The OpenBSD community's focus on permissive licensing and clear legal status made this an ideal audience for REUSE principles. The discussion highlighted how REUSE complements OpenBSD's licensing philosophy by making it easier for developers to properly attribute work and maintain clear licensing information throughout long lifecycles. diff --git a/content/blog/2021-11-sfscon-reuse-gold-standard/index.md b/content/blog/2021-11-sfscon-reuse-gold-standard/index.md new file mode 100644 index 0000000..95b233c --- /dev/null +++ b/content/blog/2021-11-sfscon-reuse-gold-standard/index.md @@ -0,0 +1,27 @@ +--- +title: "REUSE - Gold standard for Free Software licensing" +date: 2021-11-12 +categories: + - english + - presentation +tags: + - REUSE + - FSFE +headerimage: + src: sfscon-2021.jpg + text: Me giving the presentation at SFScon 2021 in Bolzano, Italy + alt: Max Mehl during his presentation at SFScon 2021 in Bolzano, Italy + processes: + - fill 1000x440 center webp +video: https://vimeo.com/649976840 +slides: https://download.fsfe.org/presentations/20211112-mm-SFScon-REUSE.en.pdf +event: + name: SFScon 2021 + href: https://www.sfscon.it/talks/reuse/ +--- + +At SFScon 2021 in Bolzano (Italy), I presented REUSE as a gold standard approach for Free and Open Source Software licensing. The REUSE initiative, launched by the Free Software Foundation Europe, provides best practices and tools that make licensing Free Software projects straightforward and unambiguous. By following three simple steps – providing license and copyright information in every file, including license texts, and confirming REUSE compliance with the tool – projects can achieve clarity that benefits both developers and users. + +The talk demonstrated how REUSE addresses common licensing challenges in Free Software development: unclear provenance, missing copyright information, and ambiguous licensing terms. I showed practical examples of how projects can adopt REUSE incrementally, explained the supporting tools available (including the REUSE helper tool and API), and discussed how REUSE is being adopted by major projects and organizations. The approach helps projects be compliant with requirements like the FSFE's "Public Money, Public Code" campaign and prepares them for emerging regulations. + +REUSE has become increasingly recognized as a best practice standard, with adoption by major organizations and integration into compliance toolchains. The talk highlighted how this simple yet effective approach removes friction from Open Source licensing. diff --git a/content/blog/2021-11-sfscon-reuse-gold-standard/sfscon-2021.jpg b/content/blog/2021-11-sfscon-reuse-gold-standard/sfscon-2021.jpg new file mode 100644 index 0000000..d2f76a7 Binary files /dev/null and b/content/blog/2021-11-sfscon-reuse-gold-standard/sfscon-2021.jpg differ diff --git a/content/blog/2022-01-digital-public-goods-podcast/index.md b/content/blog/2022-01-digital-public-goods-podcast/index.md new file mode 100644 index 0000000..7442ede --- /dev/null +++ b/content/blog/2022-01-digital-public-goods-podcast/index.md @@ -0,0 +1,26 @@ +--- +title: "Open Source, meet Digital Public Goods" +date: 2022-01-31 +categories: + - english + - podcast +tags: + - PublicCode + - Policy + - FSFE +headerimage: + src: pulse-on-the-principles.jpg + alt: The cover image for the "Pulse on the Principles" podcast + processes: + - fill 1000x440 center webp +audio: https://podcasts.apple.com/us/podcast/open-source-meet-digital-public-goods/id1525949555?i=1000549567898 +event: + name: Pulse on the Principles Podcast + href: https://podcasts.apple.com/us/podcast/pulse-on-the-principles/id1525949555 +--- + +I was invited to join the Digital Impact Alliance's "Pulse on the Principles" podcast for a conversation about the intersection of Open Source software and Digital Public Goods. Alongside Lucy Harris from the Digital Public Goods Alliance and Bernhard Kowatsch from the World Food Program Innovation Accelerator, we explored how Open Source principles can unlock digital cooperation and help achieve the UN's Sustainable Development Goals. As lead of FSFE's "Public Money, Public Code" initiative, I shared perspectives on how Free Software thinking applies to the digital public goods space. + +The episode built on the previous discussion about Open Source licenses and digital cooperation, diving deeper into practical applications. We discussed how the "open principle" can be applied to innovation ideas, what clear definitions and checklists exist for better achieving SDGs through public goods, and how this concept both helps and challenges innovation startups. The conversation highlighted the importance of Open Source not just as a development model, but as a foundational approach for creating truly public digital infrastructure. + +You can listen to the full 77-minute episode on [Apple Podcasts](https://podcasts.apple.com/us/podcast/open-source-meet-digital-public-goods/id1525949555?i=1000549567898). diff --git a/content/blog/2022-01-digital-public-goods-podcast/pulse-on-the-principles.jpg b/content/blog/2022-01-digital-public-goods-podcast/pulse-on-the-principles.jpg new file mode 100644 index 0000000..5c4396f Binary files /dev/null and b/content/blog/2022-01-digital-public-goods-podcast/pulse-on-the-principles.jpg differ diff --git a/content/blog/2022-02-fosdem-legal-policy-devroom-organizers/fosdem-2022.jpg b/content/blog/2022-02-fosdem-legal-policy-devroom-organizers/fosdem-2022.jpg new file mode 100644 index 0000000..65db8a0 Binary files /dev/null and b/content/blog/2022-02-fosdem-legal-policy-devroom-organizers/fosdem-2022.jpg differ diff --git a/content/blog/2022-02-fosdem-legal-policy-devroom-organizers/index.md b/content/blog/2022-02-fosdem-legal-policy-devroom-organizers/index.md new file mode 100644 index 0000000..302ec24 --- /dev/null +++ b/content/blog/2022-02-fosdem-legal-policy-devroom-organizers/index.md @@ -0,0 +1,23 @@ +--- +title: "Panel: Hot Topics - Organizers of the Legal & Policy DevRoom" +date: 2022-02-05 +categories: + - english + - presentation +tags: + - Community + - FSFE +headerimage: + src: fosdem-2022.jpg + alt: The title slide of the panel discussion at FOSDEM 2022, showing the title "Hot Topics - Organizers of the Legal & Policy DevRoom" and the FOSDEM 2022 branding +video: https://www.youtube.com/watch?v=1mujkaFZA2c +event: + name: FOSDEM 2022 + href: https://archive.fosdem.org/2022/schedule/event/organizerslegalpolicy/ +--- + +At FOSDEM 2022, I again joined my fellow organizers of the Legal & Policy DevRoom for a panel discussion on the hot topics we observed over the past year in Free and Open Source Software. Together with Bradley Kuhn, Karen Sandler and Alexander Sander, we reflected on the presentations from the day's track and looked forward to the future of FOSS policy. This panel provided an opportunity to discuss the pressing issues facing the FOSS community from legal and policy perspectives. + +The discussion touched on the lessons learned from the various presentations throughout the DevRoom, considering how legal and policy challenges were evolving as FOSS became increasingly central to digital infrastructure worldwide. As organizers, we shared our perspectives on emerging trends, regulatory developments, and the ongoing work needed to protect software freedom while ensuring compliance and sustainable community practices. + +This panel was part of FOSDEM's Legal and Policy Issues devroom, which continues to serve as an important forum for addressing the intersection of law, policy, and Free Software. diff --git a/content/blog/2022-04-docker2caddy-reverse-proxy.md b/content/blog/2022-04-docker2caddy-reverse-proxy.md index 95a7405..cfe2b20 100644 --- a/content/blog/2022-04-docker2caddy-reverse-proxy.md +++ b/content/blog/2022-04-docker2caddy-reverse-proxy.md @@ -2,14 +2,15 @@ title: "Docker2Caddy - An automatic Reverse Proxy for Docker containers" date: 2022-04-25 categories: + - blog - english tags: - - tools - - fsfe - - server - - python -headerimage: /blog/docker.jpg -headercredits: Shipping a load of containers requires a reliable infrastructure + - FSFE + - SystemAdministration + - Code +headerimage: + src: /blog/docker.jpg + text: Shipping a load of containers requires a reliable infrastructure --- So you have a number of Docker containers running web services which you would diff --git a/content/blog/2023-06-upstream-hardware-bom-fireside/index.md b/content/blog/2023-06-upstream-hardware-bom-fireside/index.md new file mode 100644 index 0000000..36b5cc9 --- /dev/null +++ b/content/blog/2023-06-upstream-hardware-bom-fireside/index.md @@ -0,0 +1,21 @@ +--- +title: "Hardware Bills of Material with Deutsche Bahn" +date: 2023-06-07 +categories: + - english + - presentation +tags: + - SupplyChain + - Security + - DeutscheBahn +video: https://www.youtube.com/watch?v=59WQeWXFmNw +event: + name: Upstream 2023 + href: https://upstream.live/ +--- + +At Upstream 2023, I participated in a fireside chat with Luis Villa (Tidelift) and my colleague Erik Schaufuss exploring the fascinating intersection between Software Bills of Materials (SBOMs) and Hardware Bills of Materials (HBOMs) within Deutsche Bahn's complex supply chain. As Germany's national railway company with hundreds of federated subsidiaries, we face unique challenges in managing both rolling stock hardware and the increasingly software-driven assets within trains. The discussion centered on how learnings from the software supply chain transparency movement – particularly around standards like CycloneDX – can inform and improve hardware supply chain management. + +The conversation explored Deutsche Bahn's federated corporate structure and how this complexity makes supply chain management particularly challenging yet critical. We discussed the need for standards to communicate information across organizational boundaries, the clash between traditional hardware procurement and modern software practices, and how tracking components in both domains presents parallel challenges. The fireside chat highlighted practical experiences in bridging the gap between software and hardware supply chain transparency, and the importance of ISO standards and industry collaboration in this evolving space. + +This session demonstrated that whether dealing with software packages or physical train components, the fundamental challenges of transparency, traceability, and security have more in common than one might initially expect. diff --git a/content/blog/2023-09-bitkom-forum-open-source-maintainers/firstslide.jpg b/content/blog/2023-09-bitkom-forum-open-source-maintainers/firstslide.jpg new file mode 100644 index 0000000..c5807ea Binary files /dev/null and b/content/blog/2023-09-bitkom-forum-open-source-maintainers/firstslide.jpg differ diff --git a/content/blog/2023-09-bitkom-forum-open-source-maintainers/index.md b/content/blog/2023-09-bitkom-forum-open-source-maintainers/index.md new file mode 100644 index 0000000..8aa028d --- /dev/null +++ b/content/blog/2023-09-bitkom-forum-open-source-maintainers/index.md @@ -0,0 +1,24 @@ +--- +title: "Was machen eigentlich Open-Source-Maintainer?" +date: 2023-09-27 +categories: + - deutsch + - presentation +tags: + - OSPO + - Community + - DeutscheBahn + - Maintainers +headerimage: + src: firstslide.jpg +slides: https://www.bitkom.org/sites/main/files/2023-10/BFOSS23-Praesentation-Schumacher-Mehl-Was-machen-eigentlich-Open-Source-Maintainer.pdf +event: + name: Bitkom Forum Open Source 2023 + href: https://www.bitkom.org/bfoss23 +--- + +Auf dem 9. Bitkom Forum Open Source in Erfurt präsentierten Cornelius Schumacher und ich eine Erzählung über das Leben von Open-Source-Maintainern, strukturiert als Drama mit Happy End. Durch die Geschichte von "Alex", einer fiktiven Entwicklerin, beleuchteten wir, was Maintainer wirklich antreibt, was sie jenseits des Programmierens tun und welchen Herausforderungen sie sich stellen müssen. Der Vortrag führte von der anfänglichen Motivation, ein neues Tool aus Leidenschaft und eigenem Bedarf zu schaffen, über das Wachstum zur respektierten Maintainerin mit Community-Building-Verantwortung bis hin zum Übergang der Rolle für die Nachhaltigkeit des Projekts. + +Die Präsentation hob die oft übersehenen Aspekte der Maintainership hervor: Beantwortung von Issues und Pull Requests, Moderation von Diskussionen, Sicherstellung der Einhaltung des Code of Conduct, Mentoring von Neulingen, Gestaltung von Roadmaps und strategische Entscheidungen. Wir thematisierten auch die kulturellen und prozessualen Unterschiede zwischen Unternehmen und Open-Source-Communities – von hierarchischen versus Peer-Production-Modellen bis hin zu unterschiedlicher Ressourcenverfügbarkeit und Commitment-Strukturen. Die Kernbotschaft: Maintainer sind keine Chefs, sondern Diener ihrer Communities, und das wahre Kapital eines Open-Source-Projekts liegt nicht im Code, sondern in den Menschen und der Community, die es am Leben halten. + +Der Vortrag betonte, dass Maintainer zwar in Motivation, Finanzierungsmodellen und Governance-Strukturen unterschiedlich sind, aber Kerncharakteristika teilen: hohes Verantwortungsbewusstsein, autonomes Handeln, Interessenausgleich und Servant Leadership. diff --git a/content/blog/2023-09-seafile-mirror.md b/content/blog/2023-09-seafile-mirror.md index 4ebd198..f12f0a0 100644 --- a/content/blog/2023-09-seafile-mirror.md +++ b/content/blog/2023-09-seafile-mirror.md @@ -2,13 +2,14 @@ title: "Seafile Mirror - Simple automatic backup of your Seafile libraries" date: 2023-09-22 categories: + - blog - english tags: - - python - - server - - tools -headerimage: /blog/library.jpg -headercredits: Wouldn't it be a shame if your library were to be destroyed? + - Code + - SystemAdministration +headerimage: + src: /blog/library.jpg + text: Wouldn't it be a shame if your library were to be destroyed? --- I have been using [Seafile](https://www.seafile.com/) for years to host and diff --git a/content/blog/2023-10-ospology-sbom-introduction/firstslide.jpg b/content/blog/2023-10-ospology-sbom-introduction/firstslide.jpg new file mode 100644 index 0000000..ab6d95b Binary files /dev/null and b/content/blog/2023-10-ospology-sbom-introduction/firstslide.jpg differ diff --git a/content/blog/2023-10-ospology-sbom-introduction/index.md b/content/blog/2023-10-ospology-sbom-introduction/index.md new file mode 100644 index 0000000..108bd5f --- /dev/null +++ b/content/blog/2023-10-ospology-sbom-introduction/index.md @@ -0,0 +1,24 @@ +--- +title: "SBOMs – A Short Introduction" +date: 2023-10-10 +categories: + - english + - presentation +tags: + - SupplyChain + - OSPO + - Security + - DeutscheBahn +headerimage: + src: firstslide.jpg +slides: https://up.mehl.mx/slides/2023-10-10-SBOMs-A-Short-Introduction-OSPOlogy.pdf +event: + name: OSPOlogy Live Frankfurt + href: https://community.linuxfoundation.org/events/details/lfhq-ospology-european-chapter-presents-ospologylive-frankfurt/ +--- + +At OSPOlogy Live Frankfurt in October 2023, I gave an introduction to Software Bills of Materials (SBOMs) for the OSPO community. Everyone had heard of SBOMs by then – they seemed ubiquitous, with shiny tools sprouting up everywhere. But what were they actually all about? What were the real use cases? And what often caused practical applications to fail? This talk aimed to provide a common understanding without the marketing-speak. + +The session covered the fundamental concepts of SBOMs, explored concrete use cases where they add value, and discussed the challenges organizations face when trying to implement them in practice. Drawing from my experience working with software supply chain transparency at Deutsche Bahn, I highlighted common pitfalls and offered practical insights for OSPOs looking to make sense of the SBOM landscape. + +This was part of a two-day event hosted by SAP's OSPO and co-organized with TODO Group, InnerSource Commons, LF Energy, OpenChain, SPDX, CHAOSS, and OpenSSF projects. diff --git a/content/blog/2023-11-captain-its-wednesday-deutsche-bahn/ciw.jpg b/content/blog/2023-11-captain-its-wednesday-deutsche-bahn/ciw.jpg new file mode 100644 index 0000000..8f84d64 Binary files /dev/null and b/content/blog/2023-11-captain-its-wednesday-deutsche-bahn/ciw.jpg differ diff --git a/content/blog/2023-11-captain-its-wednesday-deutsche-bahn/index.md b/content/blog/2023-11-captain-its-wednesday-deutsche-bahn/index.md new file mode 100644 index 0000000..87abb32 --- /dev/null +++ b/content/blog/2023-11-captain-its-wednesday-deutsche-bahn/index.md @@ -0,0 +1,27 @@ +--- +title: "Freie Software bei der Deutschen Bahn" +date: 2023-11-15 +categories: + - deutsch + - podcast +tags: + - OSPO + - Community + - OpenRail + - DeutscheBahn +headerimage: + src: ciw.jpg + alt: The famous "Captain it's Wednesday" comic + processes: + - fill 1000x440 center webp +audio: https://gnulinux.ch/podcast/CIW062.mp3 +event: + name: Captain it's Wednesday Podcast + href: https://gnulinux.ch/ciw062-podcast +--- + +Im "Captain it's Wednesday" Podcast von GNU/Linux.ch sprach ich mit Ralf Hersel über Freie Software bei der Deutschen Bahn. Das Gespräch fand rund ein Jahr nach meinem Wechsel von der FSFE zur DB Systel statt und bot eine gute Gelegenheit, über meine neue Rolle zu sprechen und zu reflektieren, wie ein großer Konzern wie die Deutsche Bahn mit Open Source umgeht. Der CIW-Podcast richtet sich an die deutschsprachige GNU/Linux- und Freie-Software-Community und behandelt regelmäßig technische und gesellschaftliche Themen rund um Freie Software. + +Im Gespräch erzählte ich von meinem Werdegang – über 10 Jahre im FOSS-Umfeld, lange Zeit bei der FSFE mit politischer Arbeit, Öffentlichkeitskampagnen wie "Public Money, Public Code" und technischen Themen wie REUSE, und dann der Wechsel zur DB Systel im Herbst 2022. Ich beschrieb meine Rolle als Teil des virtuellen "Open Source Program Office" der Bahn, wo wir uns um alles rund um Open Source kümmern: von Einsatz und Contributions über Richtlinien und Beratung bis hin zur strategischen Ausrichtung mit dem Open Source Manifest der DB. Ein besonderer Schwerpunkt war die Gründung der [OpenRail Association](https://openrailassociation.org) – eine Kollaboration mit anderen europäischen Bahnen zur gemeinsamen Entwicklung von Open Source für den Eisenbahnsektor. + +Die Diskussion beleuchtete, wie die DB enorm viel Open Source einsetzt, in vielen Projekten als Contributor aktiv ist, eigene Software veröffentlicht und Mitglied in verschiedenen Foundations ist. Wir sprachen auch über die Herausforderungen eines so großen, föderierten Konzerns mit über 300.000 Mitarbeitenden und wie man versucht, Open-Source-Prinzipien in dieser Struktur zu verankern. Das Gespräch endete mit einem Aufruf an die Community: Contributions zu unseren Open-Source-Projekten sind willkommen, und wir suchen immer mehr Freie-Software-Enthusiasten, die bei der Bahn mitarbeiten möchten. diff --git a/content/blog/2023-11-sap-podcast-growing-importance-sboms/index.md b/content/blog/2023-11-sap-podcast-growing-importance-sboms/index.md new file mode 100644 index 0000000..206e1b2 --- /dev/null +++ b/content/blog/2023-11-sap-podcast-growing-importance-sboms/index.md @@ -0,0 +1,24 @@ +--- +title: "The Growing Importance of Software Bills of Materials (SBOM)" +date: 2023-11-29 +categories: + - english + - podcast +tags: + - SupplyChain + - OSPO + - Security + - DeutscheBahn +headerimage: + src: sap-open-source-way.png +audio: https://podcasts.apple.com/us/podcast/the-growing-importance-of-software-bills-of-materials-sbom/id1535460646?i=1000636913792 +event: + name: SAP's Open Source Way Podcast + href: https://podcasts.apple.com/us/podcast/the-open-source-way/id1535460646 +--- + +I have been invited to talk about Software Bills of Materials (SBOM) in SAP's Open Source Way Podcast, hosted by Karsten Hohage and with SAP's Sebastian Wolf as co-guest. We had an interesting conversation about the growing importance of SBOMs in the software industry and their role within Deutsche Bahn. We also discussed the limits of SBOMs and how they can be complemented with other approaches to better understand and manage risks. + +> In this episode, our host Karsten Hohage talks to Max Mehl and Sebastian Wolf about Software Bills of Materials or SBOMs. An SBOM is a detailed record of all components within a software application, including Open Source libraries, third-party dependencies and licenses. Max and Sebastian discuss the importance of SBOMs as well as some challenges and unanswered questions of the state of the art. They also speak with Karsten about SBOMs within SAP and Deutsche Bahn and the importance of SBOMs when it comes to Open Source. + +You can listen to the episode on [Apple Podcasts](https://podcasts.apple.com/us/podcast/the-growing-importance-of-software-bills-of-materials-sbom/id1535460646?i=1000636913792) or on [Spotify](https://creators.spotify.com/pod/profile/the-open-source-way/episodes/The-Growing-Importance-of-Software-Bills-of-Materials-SBOM-e3c8qn2). diff --git a/content/blog/2023-11-sap-podcast-growing-importance-sboms/sap-open-source-way.png b/content/blog/2023-11-sap-podcast-growing-importance-sboms/sap-open-source-way.png new file mode 100644 index 0000000..a93a052 Binary files /dev/null and b/content/blog/2023-11-sap-podcast-growing-importance-sboms/sap-open-source-way.png differ diff --git a/content/blog/2024-05-siemens-open-source-maintainers/firstslide.jpg b/content/blog/2024-05-siemens-open-source-maintainers/firstslide.jpg new file mode 100644 index 0000000..1c38f1e Binary files /dev/null and b/content/blog/2024-05-siemens-open-source-maintainers/firstslide.jpg differ diff --git a/content/blog/2024-05-siemens-open-source-maintainers/index.md b/content/blog/2024-05-siemens-open-source-maintainers/index.md new file mode 100644 index 0000000..f9b79c3 --- /dev/null +++ b/content/blog/2024-05-siemens-open-source-maintainers/index.md @@ -0,0 +1,26 @@ +--- +title: "Who are these Open Source maintainers, actually?" +date: 2024-05-14 +categories: + - english + - presentation +tags: + - OSPO + - Community + - SupplyChain + - DeutscheBahn + - Maintainers +headerimage: + src: firstslide.jpg +video: https://www.youtube.com/watch?v=rJL3sGD5EkU +slides: https://opensource.siemens.com/events/2024/slides/Max_Mehl_Who_are_these_Open_Source_maintainers_actually.pdf +event: + name: Siemens Open Source 2024 + href: https://opensource.siemens.com/events/2024/#may-14th +--- + +At Siemens Open Source 2024, I presented a narrative journey through the life of an Open Source maintainer, structured as a five-act drama with a happy ending. Through the story of "Alex", a fictional developer, I explored what really drives maintainers, what they actually do beyond writing code, and the challenges they face when interacting with corporate structures. The talk moved from the initial motivation of creating a new tool driven by passion and intrinsic needs, through the growth into respected maintainership with community building responsibilities, to the eventual transition of passing on the role to ensure project sustainability. + +The presentation highlighted the often-overlooked aspects of maintainership: responding to issues and pull requests, moderating discussions, ensuring code of conduct compliance, mentoring newcomers, designing roadmaps, and making strategic decisions. I also addressed the cultural and process differences between companies and Open Source communities – from hierarchical versus peer production models to the different resource availability and commitment structures. The key message: maintainers are not bosses but servants of their communities, and the true capital of an Open Source project lies not in the code, but in the people and community that keep it alive. + +This talk emphasized that while maintainers differ in motivation, funding models, and governance structures, they share core characteristics: a high sense of responsibility, autonomous action, balance of interests, and servant leadership. diff --git a/content/blog/2024-09-dbsystel-open-source-strategic-collaboration/index.md b/content/blog/2024-09-dbsystel-open-source-strategic-collaboration/index.md new file mode 100644 index 0000000..f6137fa --- /dev/null +++ b/content/blog/2024-09-dbsystel-open-source-strategic-collaboration/index.md @@ -0,0 +1,24 @@ +--- +title: "Why DB Systel relies on Open Source for strategic collaboration" +date: 2024-09-01 +categories: + - english + - article +tags: + - OSPO + - Community + - OpenRail + - DeutscheBahn +summary: In this article, I explain why DB Systel relies on Open Source for strategic collaboration and how we approach Open Source at Deutsche Bahn. An essential tool for that is the OpenRail Association, a neutral platform for the railway industry to share and collaborate on Open Source software. The article also highlights the importance of community involvement and how DB Systel fosters a culture of openness and collaboration within the company. +headerimage: + src: systel-header.jpg +article: + name: DB Systel + href: https://www.dbsystel.de/dbsystel-en/Digital-Stories-en/why-dbsystel-relies-on-opensource-13072158 +--- + +In this article, I explain why DB Systel relies on Open Source for strategic collaboration and how we approach Open Source at Deutsche Bahn. An essential tool for that is the OpenRail Association, a neutral platform for the railway industry to share and collaborate on Open Source software. The article also highlights the importance of community involvement and how DB Systel fosters a culture of openness and collaboration within the company. + +> Open Source software has become a must for any modern company. Anyone who operates a website, offers an app or even just uses servers is most likely using software components under Open Source licences. Many years ago, therefore, DB Systel decided to professionalise its use of Open Source. + +You can read the full article on DB Systel's website, see above. diff --git a/content/blog/2024-09-dbsystel-open-source-strategic-collaboration/systel-header.jpg b/content/blog/2024-09-dbsystel-open-source-strategic-collaboration/systel-header.jpg new file mode 100644 index 0000000..ba4cc60 Binary files /dev/null and b/content/blog/2024-09-dbsystel-open-source-strategic-collaboration/systel-header.jpg differ diff --git a/content/blog/2024-11-inwx-dns-recordmaster.md b/content/blog/2024-11-inwx-dns-recordmaster.md index 7bcdf6d..32f122e 100644 --- a/content/blog/2024-11-inwx-dns-recordmaster.md +++ b/content/blog/2024-11-inwx-dns-recordmaster.md @@ -2,12 +2,14 @@ title: "INWX DNS Recordmaster - Manage your DNS nameserver records via files in Git" date: 2024-11-07 categories: + - blog - english tags: - - python - - tools -headerimage: /blog/file-cabinet.jpg -headercredits: Neatly organise your records + - Code + - SystemAdministration +headerimage: + src: /blog/file-cabinet.jpg + text: Neatly organise your records --- I own and manage 30+ domains at [INWX](https://www.inwx.com/), a large and professional domain registrar. Although INWX has a somewhat decent web interface, it became a burden for me to keep an overview of each domain's sometimes dozens of records. Especially when e.g. changing an IP address for more than one domain, it caused multiple error-prone clicks and copy/pastes that couldn't be reverted in the worst case. This is why I created [**INWX DNS Recordmaster**](https://github.com/mxmehl/inwx-dns-recordmaster) which I will shortly present here. diff --git a/content/blog/2025-03-foss-backstage-burden-knowledge/firstslide.jpg b/content/blog/2025-03-foss-backstage-burden-knowledge/firstslide.jpg new file mode 100644 index 0000000..08c60d9 Binary files /dev/null and b/content/blog/2025-03-foss-backstage-burden-knowledge/firstslide.jpg differ diff --git a/content/blog/2025-03-foss-backstage-burden-knowledge/index.md b/content/blog/2025-03-foss-backstage-burden-knowledge/index.md new file mode 100644 index 0000000..858272b --- /dev/null +++ b/content/blog/2025-03-foss-backstage-burden-knowledge/index.md @@ -0,0 +1,26 @@ +--- +title: "The Burden of Knowledge: Dealing With Open Source Risks" +date: 2025-03-10 +categories: + - english + - presentation +tags: + - OSPO + - Community + - SupplyChain + - Security + - DeutscheBahn +headerimage: + src: firstslide.jpg +video: https://www.youtube.com/watch?v=cMHPLeb5QW0 +slides: /docs/2025-03-Managing-Open-Source-Risks.pdf +event: + name: FOSS Backstage 2025 + href: https://25.foss-backstage.de/session/the-burden-of-knowledge-dealing-with-open-source-risks/ +--- + +At FOSS Backstage 2025 in Berlin, I explored a critical challenge facing OSPOs and development teams: as we increase analysis of our software supply chains, tools and scorecards reveal potential risks in Open Source projects like low maintenance, lack of community, or poor security practices. But this data alone doesn't help if it merely points out potential problems without offering solutions. The question is: how should we handle this burden of knowledge? Through manual reviews? Questionnaires? Funding? Or should we look away? + +In this session, I focused on the strategic decisions organizations need to make when assessing risk in Open Source dependencies. Drawing from my experience at an organization using a six-digit number of Open Source packages, I explored the options between the extremes of "Let's measure everything", "Let's avoid all risky Open Source", and "Let's not look at the data because it might scare off management". I discussed how to decide whether to use a project, invest resources to support it, or move away from a dependency, and when it makes sense to actively engage with or withdraw from an Open Source project. + +This talk provided an overview of feasible options and the foundation for a more informed discussion on managing Open Source risks strategically – without ignorance or fear. diff --git a/content/blog/2025-03-lwn-burden-of-knowledge/index.md b/content/blog/2025-03-lwn-burden-of-knowledge/index.md new file mode 100644 index 0000000..5363e41 --- /dev/null +++ b/content/blog/2025-03-lwn-burden-of-knowledge/index.md @@ -0,0 +1,25 @@ +--- +title: "The burden of knowledge: dealing with open-source risks (LWN.net)" +date: 2025-03-10 +categories: + - english + - article +tags: + - OSPO + - Community + - SupplyChain + - Security + - DeutscheBahn +summary: "My talk at FOSS Backstage (see earlier update) was covered by LWN.net, in an article by Joe Brockmeier. It's an extensive summary of the talk, so if the video recording isn't your thing, you can read the article instead." +article: + name: LWN.net + href: https://lwn.net/SubscriberLink/1013614/b3743b7875dc41ae/ +--- + +My talk at FOSS Backstage (see earlier post) was also covered by LWN.net, in an article by Joe Brockmeier. It's an extensive summary of the talk. + +> Organizations relying on open-source software have a wide range of tools, scorecards, and methodologies to try to assess security, legal, and other risks inherent in their so-called supply chain. However, Max Mehl argued recently in a short talk at FOSS Backstage in Berlin (and online) that all of this objective information and data is insufficient to truly understand and address risk. Worse, this information doesn't provide options to improve the situation and encourages a passive mindset. Mehl, who works as part of the CTO group at DB Systel, encouraged better risk assessment using qualitative data and direct participation in Open Source. +> +> [...] + +You're invited to read the [full article](https://lwn.net/SubscriberLink/1013614/b3743b7875dc41ae/). diff --git a/content/blog/2025-12-openrailday-moderation/index.md b/content/blog/2025-12-openrailday-moderation/index.md new file mode 100644 index 0000000..9453f72 --- /dev/null +++ b/content/blog/2025-12-openrailday-moderation/index.md @@ -0,0 +1,26 @@ +--- +title: "OpenRail Day 2025 Moderation" +date: 2025-12-17 +categories: + - english + - presentation +tags: + - OpenRail + - OSPO + - Community + - DeutscheBahn +headerimage: + src: openrailday-stage.jpg + text: My amazing co-moderator Kira Correll and I on stage +video: https://clip.place/w/p/gZ1HFxLxHri8mDABzqpGHC +summary: I had the pleasure to moderate the OpenRail Day 2025 in Paris, organised by the OpenRail Association to share knowledge and experiences about Open Source software in the railway industry. This event brought together railway operators, digital experts, and Open Source communities from across Europe for a day dedicated to showcasing concrete Open Source projects already at work in the railway sector. +event: + name: OpenRail Day 2025 @ Paris + href: https://day.openrailassociation.org +--- + +I had the pleasure to moderate the OpenRail Day 2025 in Paris, organised by the [OpenRail Association](https://openrailassociation.org) to share knowledge and experiences about Open Source software in the railway industry. This event brought together railway operators, digital experts, and Open Source communities from across Europe for a day dedicated to showcasing concrete Open Source projects already at work in the railway sector. The conference featured demonstrations, presentations, and workshops around projects like OSRD (Open Source Railway Designer), RCM OSS, LibLRS, and the Netzgrafik-Editor, all hosted by the OpenRail Association. + +The event created a space for dialogue between technical, institutional, and industrial stakeholders around key topics such as interoperability, open standards, and international collaboration. Speakers included leaders from major European railway companies like SBB, SNCF, Infrabel, and ONCF, as well as representatives from the European Commission's Open Source Programme Office. This first edition laid the foundation for a format designed to evolve and establish itself over time, in service of a more open and collaborative digital railway ecosystem. + +All session recordings, presentations, and photos are available in the [event replay section](https://day.openrailassociation.org). diff --git a/content/blog/2025-12-openrailday-moderation/openrailday-stage.jpg b/content/blog/2025-12-openrailday-moderation/openrailday-stage.jpg new file mode 100644 index 0000000..45112b4 Binary files /dev/null and b/content/blog/2025-12-openrailday-moderation/openrailday-stage.jpg differ diff --git a/content/blog/2026-01-fosdem-supply-chain-strategy/fosdem-2026-sbom-cra.jpg b/content/blog/2026-01-fosdem-supply-chain-strategy/fosdem-2026-sbom-cra.jpg new file mode 100644 index 0000000..ae7d95d Binary files /dev/null and b/content/blog/2026-01-fosdem-supply-chain-strategy/fosdem-2026-sbom-cra.jpg differ diff --git a/content/blog/2026-01-fosdem-supply-chain-strategy/index.md b/content/blog/2026-01-fosdem-supply-chain-strategy/index.md new file mode 100644 index 0000000..0dde3eb --- /dev/null +++ b/content/blog/2026-01-fosdem-supply-chain-strategy/index.md @@ -0,0 +1,30 @@ +--- +title: "Software Supply Chain Strategy at Deutsche Bahn" +date: 2026-01-31 +categories: + - english + - presentation +tags: + - OSPO + - SupplyChain + - Security + - DeutscheBahn +headerimage: + src: fosdem-2026-sbom-cra.jpg + alt: Max Mehl giving the presentation at FOSDEM 2026. The image contains the title slide in large, and a small picture of Max Mehl in the corner. + processes: + - fill 1000x440 bottom webp +video: https://video.fosdem.org/2026/ua2114/ZSWH3N-deutsche-bahn-supply-chain-cra-strategy.av1.webm +slides: https://fosdem.org/2026/events/attachments/ZSWH3N-deutsche-bahn-supply-chain-cra-strategy/slides/266949/2026-01-3_7kstxwl.pdf +event: + name: FOSDEM 2026 + href: https://fosdem.org/2026/schedule/event/ZSWH3N-deutsche-bahn-supply-chain-cra-strategy/ +--- + +At FOSDEM 2026, I presented Deutsche Bahn's software supply chain strategy in the context of the EU Cyber Resilience Act (CRA), but made clear from the start that CRA was the context, not the trigger. We didn't adopt SBOMs because of regulation – regulation validated the direction we were already taking based on operational needs. The presentation positioned our work at the intersection of CRA compliance requirements, IT operation best practices, and the practical realities of running IT infrastructure for an organization with 220,000+ employees, 7,000+ IT applications, and 100,000+ Open Source components. + +I outlined how we understand CRA as consisting of four activity areas: general principles of secure software (which we already do), professional handling of vulnerabilities (also already doing), transparency of software supply chains with SBOMs (the new challenge and focus of this talk), and information to users plus conformity assessments (out of scope but interesting). Deutsche Bahn's challenge is particularly complex because we take on different roles – customer, manufacturer, and indirectly even steward – across our diverse operations. We build software for ourselves and external customers (ranging from operating systems in train displays to mobile apps), we buy software (local, on-premise, SaaS, bundled in hardware like trains), and we operate everything across multiple environments (on-premise, cloud, edge/embedded). + +The strategy presentation emphasized how we created an SBOM architecture from scratch to handle this complexity. Working with a small interdisciplinary volunteer group, we focused on iterating quickly, gathering continuous feedback, and thinking in capabilities rather than specific tools. Our technical principles centered on modularity, open standards and interfaces, central SBOM storage with decentral sourcing and analysis – providing the flexibility needed to adapt to varying stakeholder needs and evolving regulations. The key message was that at DB's scale and diversity, you cannot implement a one-size-fits-all solution overnight. Instead, we prioritize based on identified risks and external requirements, document everything publicly, and connect the concrete CRA compliance requirements with our broader effort to bring transparency to software supply chains. This transparency forms the basis not just for regulatory compliance, but for security processes, license compliance, and proactively shaping the Open Source ecosystems we depend on. + +The day after, I gave a [follow-up presentation on our large-scale SBOM collection and use]({{< relref "2026-02-fosdem-sbom-collection" >}}), which dove deeper into the technical architecture and practical lessons learned from our initial implementation. The two talks together provided a comprehensive overview of how Deutsche Bahn is approaching software supply chain strategy in the context of CRA and beyond. diff --git a/content/blog/2026-01-fsfe-podcast-radio-equipment-directive/index.md b/content/blog/2026-01-fsfe-podcast-radio-equipment-directive/index.md new file mode 100644 index 0000000..fbbfffa --- /dev/null +++ b/content/blog/2026-01-fsfe-podcast-radio-equipment-directive/index.md @@ -0,0 +1,26 @@ +--- +title: "The final chapter of the EU Radio Equipment Directive" +date: 2026-01-29 +categories: + - english + - podcast +tags: + - RadioLockdown + - Policy + - FSFE +headerimage: + src: software-freedom-podcast.jpg + alt: Logo of the FSFE Software Freedom Podcast + processes: + - fill 1000x440 center webp +audio: https://download.fsfe.org/audio/podcast/SFP045.mp3 +event: + name: FSFE Software Freedom Podcast + href: https://fsfe.org/news/podcast/2026/episode-45.html +--- + +In the 45th episode of the FSFE Software Freedom Podcast, I joined Alexander Sander and Bonnie Mehring to discuss what is hopefully the final chapter of the EU Radio Equipment Directive (RED). This was a fitting conversation on the way to FOSDEM 2026, reflecting on nearly a decade of work to protect Free Software on radio devices. The discussion traced the complete arc of this campaign, from my initial discovery of the problematic Article 3(3)(i) back in 2015 to the final stages of (non-)implementation in 2025. + +I shared the origin story of the FSFE's involvement: as a working student in 2015, I printed out the entire Radio Equipment Directive at the university printer and read through it word by word, marking Article 3(3)(i) as problematic because it threatened to effectively mandate device lockdown that would prevent users from installing Free and Open Source Software on routers, smart home devices, and other radio equipment. What followed was years of advocacy work, legal analysis, coalition building with 48 organizations through our Joint Statement, and continuous engagement with the European Commission and ETSI. When I moved to Deutsche Bahn in 2022, Alex took over the campaign leadership and continued the work with my ongoing support and insights. + +The podcast provided an opportunity to discuss the latest developments in 2025 as the delegated act for Article 3(3)(i) reached its final stage, and to reflect on what this decade-long campaign taught us about effective policy work: the importance of early detection of problematic regulations, building broad coalitions beyond the immediate Open Source community, providing constructive technical solutions rather than just criticism, and maintaining persistent engagement across political cycles. Whether this truly marks the "final chapter" remains to be seen, but the podcast captured an important moment in an activity that has been central to my work for most of my professional life at the FSFE. diff --git a/content/blog/2026-01-fsfe-podcast-radio-equipment-directive/software-freedom-podcast.jpg b/content/blog/2026-01-fsfe-podcast-radio-equipment-directive/software-freedom-podcast.jpg new file mode 100644 index 0000000..6a02502 Binary files /dev/null and b/content/blog/2026-01-fsfe-podcast-radio-equipment-directive/software-freedom-podcast.jpg differ diff --git a/content/blog/2026-01-policy-summit-ospos-sovereignty/index.md b/content/blog/2026-01-policy-summit-ospos-sovereignty/index.md new file mode 100644 index 0000000..4e0912e --- /dev/null +++ b/content/blog/2026-01-policy-summit-ospos-sovereignty/index.md @@ -0,0 +1,34 @@ +--- +title: "OSPOs as Sovereignty Engines" +date: 2026-01-30 +categories: + # Language + - english + # - deutsch + - presentation + # - podcast + # - article +tags: + - OSPO + - Sovereignty + - Policy + - DeutscheBahn +headerimage: + src: panel.jpeg + text: The panelists at the Open Source EU Policy Summit 2026 +summary: At the EU Open Source Policy Summit 2026, I participated in a panel discussion on how Open Source Programme Offices (OSPOs) can serve as engines of digital sovereignty for large organizations. Alongside experts from the European Commission, RTE, IKEA Group, and Research Institutes of Sweden, we explored how OSPOs can build institutional capability for open collaboration and governance, and how EU policy can accelerate this transformation across critical sectors. +video: https://www.youtube.com/watch?v=qcxaBetVrLc +event: + name: EU Open Source Policy Summit 2026 + href: https://summit.openforumeurope.org/ +--- + +Delivering digital sovereignty requires more than regulation and investment -- it depends on institutional capability. I've been invited to join a panel at the EU Open Source Policy Summit focusing on how large organisations, both public and private, are building the structures needed to adopt and sustain open approaches. We discussed the role of Open Source Programme Offices (OSPOs) as engines of institutional learning, collaboration, and governance, and the potential for a EU policy to accelerate this transformation. Drawing on examples from critical sectors -- including energy, transport, and public administration -- the discussion explored how organisational capacity can strengthen Europe’s digital resilience and enable openness at scale. + +My main arguments were: + +1. OSPOs are more than just a team for managing Open Source software -- they are a strategic function that can drive cultural change, cross-functional collaboration, and ecosystem engagement across an organisation. They act as vertical and horizontal enablers. +2. In the debate around Digital Sovereignty, Open Source is a highly relevant option on the table, and goes far beyond "Buy European". OSPOs can help organisations navigate the complex landscape of Open Source, build internal expertise, and foster partnerships that enhance sovereignty through openness. +3. OSPOs cannot drive this change alone. External support in the form of strategy, incentives and regulation is needed, especially for organizations under high regulatory pressure or with limited resources. This needs to be coherent vertically across the EU and horizontally across sectors. + +It was a pleasure to elaborate this with my co-panelistzs Manuel Mateo Goyet (Acting Head of Unit CNECT.E.2, European Commission), Lucian Balea (Deputy Director of R&D and Open Source Director, RTE), Supriya Chitale (Open Source Program Office Manager, IKEA Group) and moderator Johan Linåker (Senior Researcher, Research Institutes of Sweden). diff --git a/content/blog/2026-01-policy-summit-ospos-sovereignty/panel.jpeg b/content/blog/2026-01-policy-summit-ospos-sovereignty/panel.jpeg new file mode 100644 index 0000000..4bc18df Binary files /dev/null and b/content/blog/2026-01-policy-summit-ospos-sovereignty/panel.jpeg differ diff --git a/content/blog/2026-02-fosdem-sbom-collection/fosdem-2026-sbom-approach.jpg b/content/blog/2026-02-fosdem-sbom-collection/fosdem-2026-sbom-approach.jpg new file mode 100644 index 0000000..95f9935 Binary files /dev/null and b/content/blog/2026-02-fosdem-sbom-collection/fosdem-2026-sbom-approach.jpg differ diff --git a/content/blog/2026-02-fosdem-sbom-collection/index.md b/content/blog/2026-02-fosdem-sbom-collection/index.md new file mode 100644 index 0000000..81211e6 --- /dev/null +++ b/content/blog/2026-02-fosdem-sbom-collection/index.md @@ -0,0 +1,30 @@ +--- +title: "Deutsche Bahn's Approach to Large-Scale SBOM Collection and Use" +date: 2026-02-01 +categories: + - english + - presentation +tags: + - OSPO + - SupplyChain + - Security + - DeutscheBahn +headerimage: + src: fosdem-2026-sbom-approach.jpg + alt: Max Mehl giving the presentation at FOSDEM 2026. The image contains the title slide in large, and a small picture of Max Mehl in the corner. + processes: + - fill 1000x440 bottom webp +video: https://video.fosdem.org/2026/ud2208/7EYTRJ-deutsche-bahn-large-scale-sbom-approach.av1.webm +slides: https://fosdem.org/2026/events/attachments/7EYTRJ-deutsche-bahn-large-scale-sbom-approach/slides/267417/2026-02-0_wtntumx.pdf +event: + name: FOSDEM 2026 + href: https://fosdem.org/2026/schedule/event/7EYTRJ-deutsche-bahn-large-scale-sbom-approach/ +--- + +At FOSDEM 2026, I presented Deutsche Bahn's journey from operational need to concrete implementation of large-scale SBOM collection and use. The scale is staggering: approximately 500,000 SBOMs across our software supply chain expected, covering 7,000+ IT applications, 100,000+ Open Source components, and diverse sourcing streams from software we build ourselves to what we buy and operate. The talk focused on how we moved from understanding that "we need to know, in real-time, which exact component is used where and how" to actually making this happen in an organization with 220,000+ employees and hundreds of subsidiaries. + +I explained our approach to treating SBOMs as shared infrastructure rather than a goal in itself. SBOMs support multiple use cases: Open Source license compliance, security vulnerability checking, understanding component distribution, assessing quality, satisfying governance requirements, and supporting strategic decisions about ecosystem engagement. We heavily rely on FOSS tools enriched with our own logic to fit DB's enterprise architecture. A key insight was the integration of VEX (Vulnerability Exploitability eXchange) with SBOMs – allowing us to track vulnerability status throughout processes and enabling manufacturers to communicate their assessments to us directly. + +The presentation detailed our SBOM strategy and architecture built from scratch: starting with a small interdisciplinary volunteer group, iterating quickly with continuous feedback, focusing on existing organizational needs rather than abstract best practices, and documenting everything publicly. Our technical principles emphasized modularity, open standards, central SBOM storage with decentral sourcing and analysis. The SBOM Blueprint serves as our guiding star, implemented through prioritized increments. We started by focusing on Source/Build SBOMs for in-house developed software, creating low-threshold drop-in solutions for CI pipelines. But as I emphasized throughout: tools and clever ideas aren't enough – we need people to integrate them, continuous quality monitoring, cooperation from related service operators, and support from governance stakeholders. + +This presentation was a follow-up to my talk the day before on [Deutsche Bahn's overall software supply chain strategy in the context of the EU Cyber Resilience Act (CRA)]({{< relref "2026-01-fosdem-supply-chain-strategy" >}}) – while that talk focused on the strategic rationale and high-level approach, this one dove into the technical architecture and practical lessons learned from our initial implementation. Together, they provided a comprehensive overview of how Deutsche Bahn is approaching software supply chain strategy in the context of CRA and beyond. diff --git a/content/blog/_index.md b/content/blog/_index.md new file mode 100644 index 0000000..514569b --- /dev/null +++ b/content/blog/_index.md @@ -0,0 +1,5 @@ +--- +title: Updates and Thoughts +aliases: + - /links +--- diff --git a/content/links.md b/content/links.md deleted file mode 100644 index 3e00b45..0000000 --- a/content/links.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Links -page: true -summary: A selection of audio/video recordings, articles, papers, and engagements I appear and am involved in. ---- - -A selection of links to [audio and video recordings](#av), [journalistic articles](#media) I wrote or have been quoted in, some of my [scientific papers](#science), and [organisations I volunteer for](#volunteer). - -You can click on the buttons to select only links with the given language or topic. - -{{< tags >}} - -## Audio/Video Recordings {#av} - -A selection of my presentations and radio shows I participated in. By clicking on the respective icons you can watch the video recording, access the slides and listen to the audio recording. - -{{< links type="av" >}} - -## Appearance in Media {#media} - -{{< links type="media" >}} - -## Scientific Papers {#science} - -{{< links type="science" >}} - -## Volunteering {#volunteer} - -{{< links type="volunteer" >}} diff --git a/data/links.yml b/data/links.yml deleted file mode 100644 index 35151d5..0000000 --- a/data/links.yml +++ /dev/null @@ -1,618 +0,0 @@ -# MEDIA - -- desc: '"The burden of knowledge: dealing with open-source risks"' - type: media - date: 2025-03 - links: - - href: https://lwn.net/SubscriberLink/1013614/b3743b7875dc41ae/ - text: "News @ LWN.net" - lang: ["EN"] - tags: ["OSPO", "Community", "SupplyChain", "Security"] - -- desc: '"Why DB Systel relies on Open Source for strategic collaboration"' - type: media - date: 2024-09 - links: - - href: https://www.dbsystel.de/dbsystel-en/Digital-Stories-en/why-dbsystel-relies-on-opensource-13072158 - text: "Digital Story @ DB Systel" - lang: ["EN"] - tags: ["OSPO", "Community", "OpenRail"] - -- desc: '"Germany knew its disaster warning system wasn’t good enough – why wasn’t it improved?"' - type: media - date: 2021-07 - links: - - href: https://www.thelocal.de/20210730/germany-knew-its-disaster-warning-system-wasnt-good-enough-why-wasnt-it-improved-2/ - text: "News @ The Local" - lang: ["EN"] - tags: ["CellBroadcast"] - -- desc: '"The big NINA flop"' - type: media - date: 2021-07 - links: - - href: https://web.archive.org/web/20210722020854/https://www.bild.de/politik/inland/politik-inland/der-grosse-nina-flop-app-warnte-vor-monster-angriff-77153478.bild.html - text: "News @ BILD" - lang: ["DE"] - tags: ["CellBroadcast"] - -- desc: '"RED Implementation: Open Source scene threatened by radio technology exclusion"' - type: media - date: 2021-07 - links: - - href: https://www.heise.de/news/RED-Umsetzung-Open-Source-Szene-droht-Ausschluss-aus-der-Funktechnik-6129525.html?seite=all - text: "News @ c't magazin" - lang: ["DE"] - tags: ["RadioLockdown"] - -- desc: '"youtube-dl: music industry fires shotgun at Open Source"' - type: media - date: 2020-10 - links: - - href: https://netzpolitik.org/2020/youtube-dl-musikindustrie-schiesst-mit-der-schrotflinte-auf-open-source/ - text: "News @ Netzpolitik.org" - lang: ["DE"] - -- desc: '"Radio gaga: Techies fear EU directive to stop RF device tinkering will do more harm than good"' - type: media - date: 2019-03 - links: - - href: https://www.theregister.co.uk/2019/03/11/eu_directive_ban_rf_radio_firmware_tinkering/ - text: "News @ The Register" - lang: ["EN"] - tags: ["RadioLockdown"] - -- desc: '"Open Source Software: 20-Plus Years of Innovation"' - type: media - date: 2018-10 - links: - - href: https://www.linuxinsider.com/story/85646.html - text: "News @ LinuxInsider" - lang: ["EN"] - -- desc: '"How to push back Google - and optimise Android"' - type: media - date: 2018-08 - links: - - href: https://www.welt.de/wirtschaft/webwelt/article181237140/Android-Kontrolle-So-verbannen-Sie-Google-vom-Smartphone.html - text: "News @ WELT" - lang: ["DE"] - tags: ["Android"] - -- desc: '"Public Money, Public Code pushes for governments to switch to open-source software"' - type: media - date: 2018-05 - links: - - href: https://www.shareable.net/blog/public-money-public-code-pushes-for-governments-to-switch-to-open-source-software - text: "News @ Shareable" - lang: ["EN"] - tags: ["PublicCode"] - -- desc: '"Free Software, Free Society. Why analogue freedom can no longer be thought without digital freedom"' - type: media - date: 2016-12 - links: - - href: http://www.zurichglobalist.uzh.ch/dam/jcr:3576081b-18a9-4d80-95a9-fcc13071974c/Zurich%20Globalist_Freedom.pdf - text: "Article @ Zurich Globalist" - lang: ["DE"] - -- desc: '"Radio Lockdown Directive - Threat for user rights and companies"' - type: media - date: 2016-09 - links: - - href: https://www.ispa.at/wissenspool/ispa-news.html - text: Article @ ISPA News - lang: ["DE"] - tags: ["RadioLockdown"] - -- desc: '"About advantages of Free Software and non-techy tech conferences"' - type: media - date: 2016-08 - links: - - href: https://netzpolitik.org/2016/interview-mit-max-mehl-ueber-die-vorteile-von-freier-software-und-tech-konferenzen-die-keine-sind/ - text: Interview @ Netzpolitik.org - lang: ["DE"] - -- desc: '"New law lets German internet users connect with their own routers"' - type: media - date: 2016-07 - links: - - href: https://www.cio.com/article/3101864/new-law-lets-german-internet-users-connect-with-their-own-routers.html - text: News @ CIO.com - lang: ["EN"] - tags: ["RouterFreedom"] - -- desc: '"Compulsory Routers abolished - what internet users have to know"' - type: media - date: 2016-07 - links: - - href: https://www.sueddeutsche.de/wirtschaft/internet-der-routerzwang-endet-was-internetnutzer-jetzt-wissen-muessen-1.3095231 - text: News @ Süddeutsche Zeitung - lang: ["DE"] - tags: ["RouterFreedom"] - -- desc: '"EU Radio Directive threatens competition and user rights"' - type: media - date: 2016-03 - links: - - href: https://www.dvtm.net - text: Article @ DVTM Newsletter - lang: ["DE"] - tags: ["RadioLockdown"] - -- desc: '"Commentary: 10 years Sony Rootkit – Why we should care"' - type: media - date: 2015-10 - links: - - href: https://www.heise.de/ct/artikel/Kommentar-10-Jahre-Sony-Rootkit-Why-we-should-care-2865608.html - text: Commentary @ c't magazin - lang: ["DE"] - tags: ["DRM"] - -- desc: '"10 years Sony Rootkit: malware by manufacturer"' - type: media - date: 2015-10 - links: - - href: http://www.heise.de/newsticker/meldung/10-Jahre-Sony-Rootkit-Schadsoftware-vom-Hersteller-2865426.html - text: Commentary @ heise online - lang: ["DE"] - tags: ["DRM"] - -- desc: '"The long road from Compulsory Routers to freedom of choice"' - type: media - date: 2015-08 - links: - - href: https://netzpolitik.org/2015/der-lange-weg-des-routerzwangs-zur-endgeraetefreiheit/ - text: Article @ Netzpolitik.org - lang: ["DE"] - tags: ["RouterFreedom"] - -# AUDIO/VIDEO - -- desc: 'Moderation of the OpenRail Day Conference' - type: av - date: 2025-12 - links: - - href: https://day.openrailassociation.org - text: OpenRail Day 2025 @ Paris - video: https://clip.place/w/p/gZ1HFxLxHri8mDABzqpGHC - lang: ["EN"] - tags: ["OpenRail", "OSPO", "Community"] - -- desc: '"Burden of Knowledge - Dealing with Risks in Open Source"' - type: av - date: 2025-03 - links: - - href: https://25.foss-backstage.de/session/the-burden-of-knowledge-dealing-with-open-source-risks/ - text: Talk @ FOSS Backstage 2025 - video: https://www.youtube.com/watch?v=cMHPLeb5QW0 - slides: /docs/2025-03-Managing-Open-Source-Risks.pdf - lang: ["EN"] - tags: ["OSPO", "Community", "SupplyChain", "Security"] - -- desc: '"Who are these Open Source maintainers, actually?"' - type: av - date: 2024-05 - links: - - href: https://opensource.siemens.com/events/2024/#may-14th - text: Talk @ Siemens Open Source 2024 - video: https://www.youtube.com/watch?v=rJL3sGD5EkU - slides: https://opensource.siemens.com/events/2024/slides/Max_Mehl_Who_are_these_Open_Source_maintainers_actually.pdf - lang: ["EN"] - tags: ["OSPO", "Community", "SupplyChain"] - -- desc: '"The Growing Importance of Software Bills of Materials (SBOM)"' - type: av - date: 2023-11 - links: - - href: https://podcast.opensap.info/open-source-way/2023/11/29/the-growing-importance-of-software-bills-of-materials-sbom/ - text: Guest @ SAP's Open Source Way Podcast - audio: https://podcast.opensap.info/open-source-way/2023/11/29/the-growing-importance-of-software-bills-of-materials-sbom/ - lang: ["EN"] - tags: ["SupplyChain", "OSPO", "Security"] - -- desc: '"SBOMs - A Short Introduction"' - type: av - date: 2023-10 - links: - - href: https://community.linuxfoundation.org/events/details/lfhq-ospology-european-chapter-presents-ospologylive-frankfurt/ - text: Talk @ OSPOlogy Live - slides: https://up.mehl.mx/slides/2023-10-10-SBOMs-A-Short-Introduction-OSPOlogy.pdf - lang: ["EN"] - tags: ["SupplyChain", "OSPO", "Security"] - -- desc: '"What are Open Source maintainers actually doing?"' - type: av - date: 2023-09 - links: - - href: https://www.bitkom.org/bfoss23 - text: Talk @ Bitkom Forum Open Source - slides: https://www.bitkom.org/sites/main/files/2023-10/BFOSS23-Praesentation-Schumacher-Mehl-Was-machen-eigentlich-Open-Source-Maintainer.pdf - lang: ["DE"] - tags: ["OSPO", "Community"] - -- desc: '"Hardware bills of material with Deutsche Bahn"' - type: av - date: 2023-06 - links: - - href: https://upstream.live/ - text: Fireside Chat @ Upstream 2023 - video: https://www.youtube.com/watch?v=59WQeWXFmNw - lang: ["EN"] - tags: ["SupplyChain", "Security"] - -- desc: '"Organizers of the Legal & Policy DevRoom"' - type: av - date: 2022-02 - links: - - href: https://fosdem.org/2022/schedule/event/organizerslegalpolicy/ - text: Panel @ FOSDEM - video: https://www.youtube.com/watch?v=1mujkaFZA2c - lang: ["EN"] - -- desc: '"Digital Public Goods"' - type: av - date: 2022-01 - links: - - href: https://podcasts.apple.com/us/podcast/open-source-meet-digital-public-goods/id1525949555?i=1000549567898 - text: Guest @ Digital Impact Alliance Podcast - audio: https://pulseontheprinciples.libsyn.com/s6-e2-open-source-meet-digital-public-goods - lang: ["EN"] - tags: ["PublicCode"] - -- desc: '"REUSE - Gold standard for Free Software licensing"' - type: av - date: 2021-11 - links: - - href: https://www.sfscon.it/talks/reuse/ - text: Talk @ SFScon - video: https://vimeo.com/649976840 - slides: https://download.fsfe.org/presentations/20211112-mm-SFScon-REUSE.en.pdf - lang: ["EN"] - tags: ["REUSE"] - -- desc: '"Simplify Licensing Code with REUSE"' - type: av - date: 2021-09 - links: - - href: https://2021.eurobsdcon.org/home/speakers/#simplify - text: Talk @ EuroBSDCon 2021 - video: https://www.youtube.com/watch?v=06aJomRgzFA - lang: ["EN"] - tags: ["REUSE"] - -- desc: '"REUSE - Make licensing easy for everyone"' - type: av - date: 2021-06 - links: - - href: https://www.ow2con.org/view/2021/Abstract_Community_Day#23061545 - text: Talk @ OW2con - video: https://www.youtube.com/watch?v=O5lgD01dc-c - slides: https://download.fsfe.org/presentations/20210623-mm-OW2Con-REUSE.en.pdf - lang: ["EN"] - tags: ["REUSE"] - -- desc: '"Digital Sovereignty in Europe - Free and Open Source Software as key"' - type: av - date: 2021-04 - links: - - href: https://www.europe-direct-dortmund.de/event/digitale-souveraenitaet-in-europa-freie-und-open-source-software-als-schluessel/ - text: Talk @ Europe Direct Dortmund - slides: https://download.fsfe.org/presentations/20210415-mm-EuropeDirect-DigiSouv.de.pdf - lang: ["DE"] - -- desc: '"REUSE: Simple steps to declare your copyright and licenses"' - type: av - date: 2021-03 - links: - - href: https://libreplanet.org/2021/speakers/#4663 - text: Talk @ LibrePlanet - video: https://framatube.org/w/beb7ce0c-635f-4f54-b1c5-3f620276e54b - slides: https://download.fsfe.org/presentations/20210321-mm-LibrePlanet-REUSE.en.pdf - lang: ["EN"] - tags: ["REUSE"] - -- desc: '"Organizers of the Legal & Policy DevRoom"' - type: av - date: 2021-02 - links: - - href: https://fosdem.org/2021/schedule/event/organizerslegalpolicy/ - text: Panel @ FOSDEM - video: https://www.youtube.com/watch?v=WgnDGpJhlAI - lang: ["EN"] - -- desc: '"REUSE: Best practices for declaring copyright and licenses"' - type: av - date: 2021-02 - links: - - href: https://fosdem.org/2021/schedule/event/reuse/ - text: Talk @ FOSDEM - video: https://www.youtube.com/watch?v=JXwHgPfR9UQ - slides: https://download.fsfe.org/presentations/20210206-mm-FOSDEM-REUSE.en.pdf - lang: ["EN"] - tags: ["REUSE"] - -- desc: 'Co-Host of GnuLinuxNews Podcast' - type: av - date: 2021-01 - links: - - href: https://gnulinux.ch/gln006-podcast - text: GLN006 - audio: https://gnulinux.ch/podcast/GLN_006.mp3 - lang: ["DE"] - tags: ["Android", "PublicCode"] - -- desc: '"Does more freedom lead to more security?"' - type: av - date: 2020-04 - links: - - href: http://web.archive.org/web/20230603153954/https://librezoom.net/lz20-paradox/ - text: Podcast Interview @ Librezoom - audio: https://up.mehl.mx/audio/20200401-librezoom-itsec.mp3 - lang: ["DE"] - tags: ["Security"] - -- desc: '"No IT security without Free Software"' - type: av - date: 2020-02 - links: - - href: https://www.digitale-gesellschaft.ch/kongress/2020/talks/keine_it-sicherheit_ohne_freie_software/ - text: Talk @ Winterkongress DigiGes CH - video: https://www.youtube.com/watch?v=6MW9a5fPX-k - slides: https://download.fsfe.org/presentations/20200222-mm-Winterkongress-ITSec.de.pdf - lang: ["DE"] - tags: ["Security"] - -- desc: '"Go REUSE to license your code"' - type: av - date: 2020-02 - links: - - href: https://fosdem.org/2020/schedule/event/reuse_code_licensing/ - text: Talk @ FOSDEM - video: https://www.youtube.com/watch?v=vyAYKROvTO8 - slides: https://download.fsfe.org/presentations/20200202-mm-FOSDEM-REUSE.en.pdf - lang: ["EN"] - tags: ["REUSE"] - -- desc: '"REUSE: Make licensing easy for everyone"' - type: av - date: 2019-10 - links: - - href: https://osseu19.sched.com/event/05a3272287d3def1bcb0a62ace00b730 - text: Talk @ Open Source Summit Europe - slides: https://download.fsfe.org/presentations/20191028-mm-OSSEU-REUSE.en.pdf - lang: ["EN"] - tags: ["REUSE"] - -- desc: '"No IT security without Free Software"' - type: av - date: 2019-09 - links: - - href: https://2k19.balccon.org/events/325.html - text: Talk @ BalCCon - video: https://www.youtube.com/watch?v=8SWijSFbMhg - slides: https://download.fsfe.org/presentations/20190914-mm-BalCCon-ITSec.en.pdf - lang: ["EN"] - tags: ["Security"] - -- desc: '"No IT security without Free Software"' - type: av - date: 2019-07 - links: - - href: https://2019.pass-the-salt.org/talks/102.html - text: Talk @ Pass the SALT - video: https://www.youtube.com/watch?v=B0qxm331Q8Q - slides: https://download.fsfe.org/presentations/20190703-mm-SALT-ITSec.en.pdf - lang: ["EN"] - tags: ["Security"] - -- desc: '"IT Security? Free Software!"' - type: av - date: 2019-04 - links: - - href: https://pretalx.linuxtage.at/glt19/talk/K9YDDN/ - text: Keynote @ Grazer Linuxtage - video: https://www.youtube.com/watch?v=DOv_5ZPcFZ8 - slides: https://download.fsfe.org/presentations/20190427-mm-Graz-ITSec.de.pdf - lang: ["DE"] - tags: ["Security"] - -- desc: '"Public Code with Free Software: Modernising Public Digital Infrastructure"' - type: av - date: 2018-09 - links: - - href: https://2k18.balccon.org/events/235.html - text: Talk @ BalCCon - video: https://www.youtube.com/watch?v=tEkCnCtoQ60 - slides: https://download.fsfe.org/presentations/20180915-mm-BalCCon-PMPC.en.pdf - lang: ["EN"] - tags: ["PublicCode"] - -- desc: '"Public Money? Public Code! - Modernising Digital Public Infrastructure"' - type: av - date: 2018-09 - links: - - href: https://www.drupaleurope.org/session/public-code-free-software-modernising-digital-public-infrastructure - text: Talk @ DrupalEurope - slides: https://download.fsfe.org/presentations/20180911-mm-DrupalEurope-PMPC.en.pdf - lang: ["EN"] - tags: ["PublicCode"] - -- desc: '"Public Money? Public Code! - Modernising Digital Public Infrastructure"' - type: av - date: 2018-07 - links: - - href: - text: Talk @ RMLL/LSM - slides: https://download.fsfe.org/presentations/20180707-mm-RMLL-PMPC.en.pdf - lang: ["EN"] - tags: ["PublicCode"] - -- desc: '"Sovereignty by Free Software"' - type: av - date: 2018-07 - links: - - href: - text: Talk @ German Armed Forces - lang: ["DE"] - tags: ["PublicCode"] - -- desc: '"Public Code with Free Software: Modernising Public Digital Infrastructure"' - type: av - date: 2018-06 - links: - - href: https://ow2con18.sched.com/event/EcdE/keynote-public-code-with-free-software-modernising-public-digital-infrastructure - text: Keynote @ OW2Con - video: https://www.youtube.com/watch?v=kQGw25xG_5c - slides: https://download.fsfe.org/presentations/20180607-mm-OW2Con-PMPC.en.pdf - lang: ["EN"] - tags: ["PublicCode"] - -- desc: '"EU Radio Equipment Directive: Extensive Device Lockdown"' - type: av - date: 2017-04 - links: - - href: https://fsfe.org/news/2017/news-20170619-01.html - text: Talk @ Legal and Licensing Workshop - slides: https://download.fsfe.org/presentations/20170427-mm-LLW-RadioLockdown_verbose.en.pdf - lang: ["EN"] - tags: ["RadioLockdown"] - -- desc: '"Radio Lockdown Directive - Our devices are engangered"' - type: av - date: 2017-03 - links: - - href: https://chemnitzer.linux-tage.de/2017/en/programm/beitrag/266 - text: Talk @ Chemnitzer Linuxtage - video: https://chemnitzer.linux-tage.de/2017/en/programm/beitrag/266 - slides: https://download.fsfe.org/presentations/20170311-mm-CLT-RadioLockdown.de.pdf - lang: ["DE"] - tags: ["RadioLockdown"] - -- desc: '"Radio Lockdown Directive - Major Threat for Free Software on Radio Devices"' - type: av - date: 2017-02 - links: - - href: https://archive.fosdem.org/2017/schedule/event/radio_lockdown_directive/ - text: Talk @ FOSDEM - video: https://archive.fosdem.org/2017/schedule/event/radio_lockdown_directive/ - slides: https://download.fsfe.org/presentations/20170204-mm-FOSDEM-Radiolockdown.en.pdf - lang: ["EN"] - tags: ["RadioLockdown"] - -- desc: '"Compulsory Routers and Radio Lockdown – What activists can learn from it"' - type: av - date: 2016-12 - links: - - href: https://fahrplan.events.ccc.de/congress/2016/Fahrplan/events/8024.html - text: Talk @ 33. Chaos Communication Congress - video: https://media.ccc.de/v/33c3-8024-routerzwang_und_funkabschottung - slides: https://download.fsfe.org/presentations/20161227-mm-33C3-Radio+Router.de.pdf - lang: ["EN", "DE"] - tags: ["RouterFreedom", "RadioLockdown"] - -- desc: '"No more Compulsory Routers – Free choice of DSL modem and cable modem"' - type: av - date: 2016-09 - links: - - href: https://www.deutschlandfunk.de/dsl-modem-und-kabelrouter-schluss-mit-dem-routerzwang.772.de.html?dram:article_id=362214 - text: Radio Show @ Deutschlandfunk - audio: https://up.mehl.mx/audio/20160901-dlf-routerzwang.ogg - lang: ["DE"] - tags: ["RouterFreedom"] - -- desc: '"Compulsory Routers and Radio Lockdown – What activists can learn from it"' - type: av - date: 2016-08 - links: - - href: https://programm.froscon.de/2016/events/1738.html - text: Talk @ FrOSCon - video: https://www.youtube.com/watch?v=CdRQtaePiIs - lang: ["DE"] - tags: ["RadioLockdown", "RouterFreedom"] - -- desc: '"The FSFE uncut"' - type: av - date: 2016-04 - links: - - href: - text: Podcast @ Living Linux - lang: ["DE"] - -- desc: '"Compulsory Routers and what activists can learn from it"' - type: av - date: 2016-03 - links: - - href: https://chemnitzer.linux-tage.de/2016/de/programm/beitrag/177 - text: Chemnitzer Linuxtage - video: https://www.youtube.com/watch?v=P5EMZ8VFuME - lang: ["DE"] - tags: ["RouterFreedom"] - -# SCIENCE - -- desc: '"Echo Chambers in the German Bundestag Election Campaign 2017. The Ambivalent Role of Prominence"' - type: science - date: 2018 - links: - - href: https://doi.org/10.5771/0340-1758-2018-3-586 - text: Article @ Zeitschrift für Parlamentsfragen - lang: ["DE"] - -- desc: '"The influence of sensational issues on the political agenda setting in social media"' - type: science - date: 2015 - links: - - href: https://up.mehl.mx/ba/ba-mehl.pdf - text: B.A. Thesis - - href: https://up.mehl.mx/ba/ba-mehl.zip - text: Data & Code - lang: ["DE"] - -- desc: '"Once again a surpising crisis?" - Quantitative study of clustering news' - type: science - date: 2014 - links: - - href: https://up.mehl.mx/uni/2014-suprisingnews.zip - text: Paper & Code - lang: ["DE"] - -- desc: '"The imprint is still not taken for granted" - Analysis of compliance with the German imprint requirement' - type: science - date: 2014 - links: - - href: https://up.mehl.mx/uni/2014-impressum.zip - text: Paper & Code - lang: ["DE"] - -# VOLUNTEER - -- desc: General Assembly member - type: volunteer - links: - - href: https://fsfe.org - text: FSFE - -- desc: Board member - type: volunteer - links: - - href: https://f-droid.org - text: F-Droid - -- desc: Guide & Local Group Commissioner - type: volunteer - links: - - href: https://pfadfinder-konstanz.de - text: DPSG Scouts Konstanz - -- desc: Former scouts guide - type: volunteer - links: - - href: https://helder-camara.de - text: DPSG Scouts Köln - -- desc: Volunteer - type: volunteer - links: - - href: https://tareo-tz.org - text: TAREO (Tanzania Rural Empowerment Organization) diff --git a/themes/hugo-sustain/assets/scss/default.scss b/themes/hugo-sustain/assets/scss/default.scss index 7c033e4..bd092e9 100755 --- a/themes/hugo-sustain/assets/scss/default.scss +++ b/themes/hugo-sustain/assets/scss/default.scss @@ -3,9 +3,11 @@ --primary-color: #0D76EC; --hover-color: #12437A; --light-bg: #fff; + --light-bg-card: #f5f5f5; --primary-color-dark: #4da3ff; --hover-color-dark: #91c9ff; - --dark-bg: #222; + --dark-bg: #14161e; + --dark-bg-card: #1c212d; --dark-font-color: #eee; --dark-nav-color: #ddd; } @@ -16,6 +18,7 @@ html, body { background-color: var(--light-bg); font-family: 'Source Sans Pro', sans-serif; border-top: 3px solid var(--primary-color); + font-size: 18px; } #wrap { @@ -32,12 +35,15 @@ html, body { .container { width: auto; max-width: 800px; - text-align: center; .text-muted { margin: 20px 0; } + h1 { + text-align: center; + } + a { color: var(--primary-color); @@ -55,14 +61,13 @@ html, body { } } - .label-success { - background-color: rgba(92, 139, 184, 0.6); - color: #fff; + p { + margin-bottom: 20px; + } - &:hover, - &.active { - background-color: rgba(92, 139, 184, 0.9); - color: #fff; + h1, h2, h3, h4, h5, h6 { + span { + cursor: default; } } @@ -71,11 +76,33 @@ html, body { color: var(--primary-color); } - h4 a { - color: var(--primary-color); + h2 { + a { + color: var(--primary-color); - &:hover { - color: var(--hover-color); + &:hover { + color: var(--hover-color); + } + } + } +} + +/* Labels */ +.label { + &.label-success { + background-color: rgba(92, 139, 184, 0.6); + color: #fff; + + &.label-lg { + font-size: 1em; + padding: 0.5em 1em; + } + + &:hover, + &:focus, + &.active { + background-color: rgba(92, 139, 184, 0.9); + color: #fff; } } } @@ -101,22 +128,22 @@ html, body { } &-default { - h4, h5 { + h2, h3, h4, h5 { text-align: left; } - h4 { + h2 { + font-size: 1.25rem; line-height: 24px; - font-size: 22px; } h5 { line-height: 30px; - font-size: 18px; + font-size: 1rem; } h6 { - font-size: 15px; + font-size: 0.9rem; } } } @@ -199,10 +226,11 @@ html, body { font-size: 18px; .header-image { + margin-bottom: 0.5em; + img { width: 100%; height: auto; - padding-bottom: 2px; } p { @@ -210,7 +238,20 @@ html, body { font-size: 0.8em; text-align: center; line-height: 1em; - margin-bottom: 1.5em; + margin-top: .5em; + margin-bottom: 0; + } + } + + .blog-links { + display: flex; + gap: 0.5rem; + flex-wrap: wrap; + margin-bottom: .5em; + justify-content: center; + + .label { + margin-bottom: 0; } } } @@ -227,7 +268,7 @@ html, body { } .metadata-summary { - font-size: 0.8em; + font-size: 0.8rem; opacity: 0.7; } @@ -264,13 +305,18 @@ a.learn-more { } /* Pagination */ -.pagination { - li.page-item:not(.active) { - a { - color: var(--primary-color); +#pagination { + display: flex; + justify-content: center; - &:hover { - color: var(--hover-color); + .pagination { + li.page-item:not(.active) { + a { + color: var(--primary-color); + + &:hover { + color: var(--hover-color); + } } } } @@ -279,17 +325,21 @@ a.learn-more { /* Footer */ footer { border-bottom: 5px solid var(--primary-color); + text-align: center; text-decoration: none !important; .text-muted { color: #6b6b6b; } + + p { + font-size: 0.8rem; + } } /* Site specific */ -section#about p { - font-size: 18px; - margin-bottom: 20px; +div#index-content { + text-align: center; } div.contact p { @@ -297,6 +347,24 @@ div.contact p { margin-bottom: 30px; } +/* Recent posts */ +#recent-posts { + padding: 0 1rem; + .card { + // Box + padding: 1rem; + background-color: var(--light-bg-card); + border-radius: 0 1rem; + margin-bottom: .3rem; + text-align: left; + + .card-title { + font-size: 1.1rem; + margin-top: 0; + } + } +} + /* Helpers */ .vertical-align { display: flex; @@ -337,7 +405,7 @@ pre code { } h1, - h4 a { + h2 a { color: var(--primary-color-dark); &:hover { @@ -359,6 +427,10 @@ pre code { } } + #recent-posts .card { + background-color: var(--dark-bg-card); + } + // Pagination .pagination { li.page-item { diff --git a/themes/hugo-sustain/assets/scss/luxbar.scss b/themes/hugo-sustain/assets/scss/luxbar.scss index 13fccd2..de3a426 100644 --- a/themes/hugo-sustain/assets/scss/luxbar.scss +++ b/themes/hugo-sustain/assets/scss/luxbar.scss @@ -104,6 +104,7 @@ color: #6b6b6b; cursor: pointer; font-size: 16px; + text-transform: uppercase; } .luxbar-item { diff --git a/themes/hugo-sustain/layouts/_default/list.html b/themes/hugo-sustain/layouts/_default/list.html index 85ccab2..df99306 100644 --- a/themes/hugo-sustain/layouts/_default/list.html +++ b/themes/hugo-sustain/layouts/_default/list.html @@ -9,39 +9,54 @@ {{- $selection = true -}} {{- end -}}
-

{{ .Site.Params.Blog.Headline }} - {{- if $selection -}} -
({{ .Data.Singular | humanize }}: {{lower .Title}}) - {{- end -}} -

+ + {{- if $selection }} +

{{ (printf "Everything from %s \"%s\"" (.Data.Singular | humanize) .Title) | markdownify }}

+ {{- else }} +

{{ .Title }}

+ {{- end }} {{ if .Site.Params.Social.CommentsProvider }}

Subscribe to my Blog via Diaspora, Mastodon, Friendica or GNU Social. Never miss a article! Reshare, like and discuss it!

{{ end }}
- Languages: + Type:
All - {{ range $name, $taxonomy := .Site.Taxonomies.categories }} + {{- range $name, $taxonomy := .Site.Taxonomies.categories }} + {{- if in (slice "english" "deutsch") $name }}{{ continue }}{{ end }} {{- humanize $name -}} - {{- end -}} + {{- end }}
- Tags: + Language:
All - {{ range $name, $taxonomy := .Site.Taxonomies.tags }} - + {{- range $name, $taxonomy := .Site.Taxonomies.categories }} + {{- if not (in (slice "english" "deutsch") $name) }}{{ continue }}{{ end }} + {{- humanize $name -}} - {{- end -}} + {{- end }} +
+
+
+
+ Tag: +
+
+ All + {{ $tags := site.GetPage "/tags" }} + {{ range sort $tags.Pages "Title" "asc"}} + {{ .LinkTitle }} + {{ end }}
@@ -62,12 +77,18 @@
{{ range .Paginator.Pages.ByPublishDate.Reverse }}
-

{{ .Title | markdownify }}

-
Posted on {{ .Date.Format "2 January 2006" }} - Tagged with {{ range $i, $tag := .Params.tags }}{{ if $i }}, {{ end }}{{ $tag }}{{ end }}
+

+ {{ partial "blog/pre-headline.html" . -}} + {{ .Title | markdownify }} +

+
+ {{- partial "blog/verb.html" . }} + on {{ .Date.Format "2 January 2006" }} - Tagged with {{ range $i, $tag := .Params.tags }}{{ if $i }}, {{ end }}{{ $tag }}{{ end }} +
{{ .Summary }}
{{ end }} - {{ template "_internal/pagination.html" . }} +
diff --git a/themes/hugo-sustain/layouts/_default/single.html b/themes/hugo-sustain/layouts/_default/single.html index 24b4467..80cda3e 100644 --- a/themes/hugo-sustain/layouts/_default/single.html +++ b/themes/hugo-sustain/layouts/_default/single.html @@ -6,7 +6,7 @@ {{ partial "header" . }}
-

{{ .Title }}

+

{{ .Title | markdownify }}

{{ if ne .Params.page true }}
@@ -17,14 +17,25 @@ {{ .Date.Format "2 January 2006" }}
+
+
+ Type: +
+
+ {{- range .Params.categories }} + {{- if in (slice "english" "deutsch") . }}{{ continue }}{{ end }} + {{ title . }} + {{- end }} +
+
Tags:
- {{ range .Params.tags }} - {{ . }} - {{- end -}} + {{- range .Params.tags }} + {{ title . }} + {{- end }}
@@ -40,12 +51,8 @@
- {{ if isset .Params "headerimage" }} -
- -

{{ with .Params.headercredits }}{{ . | markdownify }}{{ end }}

-
- {{ end }} + {{- partial "blog/headerimage" . }} + {{- partial "blog/links" . }} {{ .Content }} {{ if or (eq .Params.related true) (ne .Params.page true) }} @@ -85,6 +92,6 @@ {{ partial "matomo" . }} - + diff --git a/themes/hugo-sustain/layouts/index.html b/themes/hugo-sustain/layouts/index.html index 9447ba1..76aa7b3 100644 --- a/themes/hugo-sustain/layouts/index.html +++ b/themes/hugo-sustain/layouts/index.html @@ -2,19 +2,20 @@
{{ partial "header" . }} -
+
-
- Responsive image -
- - {{ .Content }} +
+
+ Responsive image +
- {{ partial "comments" . }} - {{ partial "social" . }} + {{ .Content }}
-
-
+ {{ partial "recent" . }} +
+ +
+ {{ partial "social" . }} {{ partial "footer" . }} {{ partial "js" . }} {{ partial "matomo" . }} diff --git a/themes/hugo-sustain/layouts/partials/blog/headerimage.html b/themes/hugo-sustain/layouts/partials/blog/headerimage.html new file mode 100644 index 0000000..03fa041 --- /dev/null +++ b/themes/hugo-sustain/layouts/partials/blog/headerimage.html @@ -0,0 +1,28 @@ +{{- $page := . -}} +{{- $image := "" }} +{{- with $page.Params.headerimage }} +
+ {{- if eq $page.BundleType "leaf" }} + {{- with $page.Resources.GetMatch .src }} + {{- $image = . }} + {{- end }} + {{- else }} + {{- with resources.GetMatch (printf "**/%s" .src) }} + {{- $image = . }} + {{- end }} + {{- end }} + {{- $processes := .processes | default (slice "fill 1000x440 webp" )}} + {{- $filter := .filter }} + {{- if not $image }} + {{- warnf "Header image '%s' not found for page %s" .src $page.RelPermalink }} + {{- else }} + {{- $image = partial "image-processing" (dict "image" $image "processes" $processes "filter" $filter) -}} + {{ . }} + {{- with .text }}

{{ . | markdownify }}

{{ end }} + {{- end }} +
+{{- end }} diff --git a/themes/hugo-sustain/layouts/partials/blog/links.html b/themes/hugo-sustain/layouts/partials/blog/links.html new file mode 100644 index 0000000..2f96590 --- /dev/null +++ b/themes/hugo-sustain/layouts/partials/blog/links.html @@ -0,0 +1,27 @@ +
+ {{- with .Params.audio }} + +   Listen to Recording + + {{- end }} + {{- with .Params.article }} + +   Read Article at {{ .name | markdownify }} + + {{- end }} + {{- with .Params.video }} + +   Watch Recording + + {{- end }} + {{- with .Params.slides }} + +   View Slides + + {{- end }} + {{- with .Params.event }} + +   {{ .name | markdownify }} + + {{- end }} +
diff --git a/themes/hugo-sustain/layouts/partials/blog/pre-headline.html b/themes/hugo-sustain/layouts/partials/blog/pre-headline.html new file mode 100644 index 0000000..b76c19a --- /dev/null +++ b/themes/hugo-sustain/layouts/partials/blog/pre-headline.html @@ -0,0 +1,13 @@ +{{- $cats := .Page.Params.categories }} +{{- $symbols := dict "article" "🗞️" "presentation" "🎤" "podcast" "🎧" }} +{{- $icon := "" }} +{{- $title := "" }} +{{- range $cat := $cats }} + {{- with index $symbols $cat }} + {{- $icon = . }} + {{- $title = $cat | humanize }} + {{- end }} +{{- end }} +{{- with $icon }} +{{ $icon }}   +{{- end -}} diff --git a/themes/hugo-sustain/layouts/partials/blog/verb.html b/themes/hugo-sustain/layouts/partials/blog/verb.html new file mode 100644 index 0000000..917f3ff --- /dev/null +++ b/themes/hugo-sustain/layouts/partials/blog/verb.html @@ -0,0 +1,12 @@ +{{- $cats := .Page.Params.categories }} +{{- $symbols := dict "article" "Article published" "presentation" "Presentation given" "podcast" "Podcast released" }} +{{- $selection := "" }} +{{- range $cat := $cats }} + {{- with index $symbols $cat }} + {{- $selection = . }} + {{- end }} +{{- end }} +{{- if not $selection }} + {{- $selection = "Blogged" }} +{{- end }} +{{- return $selection }} diff --git a/themes/hugo-sustain/layouts/partials/head.html b/themes/hugo-sustain/layouts/partials/head.html index 57bda9c..95fa156 100644 --- a/themes/hugo-sustain/layouts/partials/head.html +++ b/themes/hugo-sustain/layouts/partials/head.html @@ -12,8 +12,6 @@ {{- $title = print .Site.Title " | " .Title -}} {{- end -}} {{- end -}} - {{- $image := path.Join "/img" .Site.Params.avatar -}} - {{- if isset .Params "headerimage" }} {{ $image = print "img/" .Params.headerimage }} {{ end -}} @@ -29,18 +27,32 @@ {{- partialCached "head/css.html" . }} - {{ "" | safeHTML }} - - - - + + {{- $image := "" -}} + {{- $imagesrc := (.Page.Params.headerimage.src | default .Site.Params.avatar) -}} + {{- if eq .Page.BundleType "leaf" }} + {{- with .Page.Resources.GetMatch $imagesrc }} + {{- $image = . -}} + {{- end }} + {{- else }} + {{- with resources.GetMatch (printf "**/%s" $imagesrc) }} + {{- $image = . -}} + {{- end }} + {{- end }} + {{- if $image }} + {{- $image = $image.Fill "1200x630 jpg" -}} + {{- end }} - {{ "" | safeHTML }} - - - - - - - + + + + + + + {{- with $image }} + + + + + {{- end }} diff --git a/themes/hugo-sustain/layouts/partials/header.html b/themes/hugo-sustain/layouts/partials/header.html index 9cf818d..9653775 100644 --- a/themes/hugo-sustain/layouts/partials/header.html +++ b/themes/hugo-sustain/layouts/partials/header.html @@ -10,7 +10,7 @@ {{- if .Site.Menus.main -}} {{- range sort .Site.Menus.main -}} -
  • {{ .Name | upper }}
    • +
  • {{ .Name }}
    • {{- end -}} {{ end }} diff --git a/themes/hugo-sustain/layouts/partials/image-processing.html b/themes/hugo-sustain/layouts/partials/image-processing.html new file mode 100644 index 0000000..0203632 --- /dev/null +++ b/themes/hugo-sustain/layouts/partials/image-processing.html @@ -0,0 +1,32 @@ +{{- /* Expects .image (resolved image resource), optionally .processes and .filter */}} +{{- $image := .image }} +{{- range .processes }} + {{- $image = $image.Process . }} +{{- end }} +{{- with .filter }} + {{- $filters := slice }} + {{- range . }} + {{- range $method, $args := . }} + {{/* No, this cannot be generalised, as strings cannot be converted to functions... */}} + {{- if eq $method "GaussianBlur" }} + {{- $filters = $filters | append (images.GaussianBlur $args) }} + {{- else if eq $method "Brightness" }} + {{- $filters = $filters | append (images.Brightness $args) }} + {{- else if eq $method "Opacity" }} + {{- $filters = $filters | append (images.Opacity $args) }} + {{- else if eq $method "Pixelate" }} + {{- $filters = $filters | append (images.Pixelate $args) }} + {{- else if eq $method "Saturation" }} + {{- $filters = $filters | append (images.Saturation $args) }} + {{- else if eq $method "Sepia" }} + {{- $filters = $filters | append (images.Sepia $args) }} + {{- else if eq $method "Grayscale" }} + {{- $filters = $filters | append images.Grayscale }} + {{- else }} + {{- warnf "Unsupported filter: %s" $method }} + {{- end }} + {{- end }} + {{- end }} + {{- $image = $image.Filter $filters }} +{{- end }} +{{- return $image }} diff --git a/themes/hugo-sustain/layouts/partials/recent.html b/themes/hugo-sustain/layouts/partials/recent.html new file mode 100644 index 0000000..0d1dbca --- /dev/null +++ b/themes/hugo-sustain/layouts/partials/recent.html @@ -0,0 +1,21 @@ +{{- $lastno := 3 }} +{{- $size := sub 12 $lastno -1 }} +{{- $id := 0 }} +{{- $pages := .Site.RegularPages.ByDate.Reverse | first $lastno }} +
    + {{- range $pages }} +
    +
    +

    + {{ partial "blog/pre-headline.html" . -}} + {{ .Title | markdownify }} +

    +
    + {{- partial "blog/verb.html" . }} + on {{ .Date.Format "2 January 2006" }} - {{ range $i, $tag := .Params.tags }}{{ if $i }}, {{ end }}#{{ $tag }}{{ end }} +
    +
    +
    + {{- $id = add $id 1 -}} + {{- end }} +
    diff --git a/themes/hugo-sustain/layouts/shortcodes/links.html b/themes/hugo-sustain/layouts/shortcodes/links.html deleted file mode 100644 index b3b6010..0000000 --- a/themes/hugo-sustain/layouts/shortcodes/links.html +++ /dev/null @@ -1,26 +0,0 @@ -{{- $type := .Get "type" -}} -{{- $data := .Site.Data.links -}} -{{- if $type -}} - {{- $data = where $data "type" $type -}} -{{ end }} -
      -{{- range sort $data "date" "desc" }} - {{- $tags := slice -}} - {{- range .lang }}{{ $tags = $tags | append . }}{{ end -}} - {{- range .tags }}{{ $tags = $tags | append . }}{{ end -}} -
    • - {{ .desc -}} –  - {{- $len := (len .links) -}} - {{- range $index, $element := .links -}} - {{- with .href }}{{ end }}{{.text}}{{ with .href }}{{end}} - {{- if ne (add $index 1) $len -}}, {{- end -}} - {{- end -}} - {{- if or (.video) (.audio) (.slides) }},{{ end -}} - {{ with .video }} {{ end }} - {{- with .audio }} {{ end }} - {{ with .slides }} {{ end -}} - {{- with .date }} ({{.}}){{ end -}} - {{ range $tags }} {{ . }}{{ end -}} -
      • -{{ end }} -
    diff --git a/themes/hugo-sustain/layouts/shortcodes/tags.html b/themes/hugo-sustain/layouts/shortcodes/tags.html deleted file mode 100644 index bb16824..0000000 --- a/themes/hugo-sustain/layouts/shortcodes/tags.html +++ /dev/null @@ -1,34 +0,0 @@ -{{- $data := .Site.Data.links -}} -{{ $scratch := newScratch -}} -{{- range $data -}} - {{- range .tags -}} - {{- $scratch.Add "tags" (slice .) -}} - {{- end -}} - {{- range .lang -}} - {{- $scratch.Add "lang" (slice .) -}} - {{- end -}} -{{- end -}} -
    -
    -
    - Languages: -
    -
    - All - {{- range sort ($scratch.Get "lang") | uniq }} - {{ . }} - {{- end -}} -
    -
    -
    -
    - Topics: -
    -
    - All - {{- range sort ($scratch.Get "tags") | uniq }} - {{ . }} - {{- end -}} -
    -
    -