Every week veteran KDE contributor Kevin Ottens posts a bunch of thought-provoking links on his blog, and last week’s post contained one that I found particularly enlightening: 40 years of pr…
Literal politics. Rarbg had project members volunteer to fight in the Russia-Ukraine war… For both the side of Russia, and the side of Ukraine
Drama. Contributing takes a lot of time and effort. People get attached to their ideas and contributions. When people start drifting apart and fighting, third parties have to play politics to keep people happy and working towards a common goal
Those are only secondary politics in software development. You missed the primary politics of software - the power struggle expressed through code itself. It comes in many forms. But perhaps the most obvious one is the attempt by software corporates to wrestle control and freedom away from the user using DRM, Trusted computing, locked down devices, dark patterns, etc and relegate the user to the status of a renter.
Imagine a country made up of flurbs and blorbs. Flurbs make up the majority of the government and don’t recognise the existence of blorbs.
You are writing open source census software, do you include blorbs?
If you do, you get labelled a blorb sympathiser and the government stops funding development. Maybe throws you in prison.
If you don’t, you get labelled a member of the Flurbian autocracy and are orchastrated from the hugely blorb open source community.
If you add a togglable option, you’re still seen as sympathetic to the Flurbs because you are participating in oppressive regimes. And also supporting a blorb uprising by making them think they have a voice. Staying “neutral” is still picking a side.
So basically, you are forced to pick from a number of options based on your political (or strategic) view.
Why is software development political ?
Everything is political
2 things:
Literal politics. Rarbg had project members volunteer to fight in the Russia-Ukraine war… For both the side of Russia, and the side of Ukraine
Drama. Contributing takes a lot of time and effort. People get attached to their ideas and contributions. When people start drifting apart and fighting, third parties have to play politics to keep people happy and working towards a common goal
Those are only secondary politics in software development. You missed the primary politics of software - the power struggle expressed through code itself. It comes in many forms. But perhaps the most obvious one is the attempt by software corporates to wrestle control and freedom away from the user using DRM, Trusted computing, locked down devices, dark patterns, etc and relegate the user to the status of a renter.
Imagine a country made up of flurbs and blorbs. Flurbs make up the majority of the government and don’t recognise the existence of blorbs.
You are writing open source census software, do you include blorbs?
If you do, you get labelled a blorb sympathiser and the government stops funding development. Maybe throws you in prison.
If you don’t, you get labelled a member of the Flurbian autocracy and are orchastrated from the hugely blorb open source community.
If you add a togglable option, you’re still seen as sympathetic to the Flurbs because you are participating in oppressive regimes. And also supporting a blorb uprising by making them think they have a voice. Staying “neutral” is still picking a side.
So basically, you are forced to pick from a number of options based on your political (or strategic) view.
It gives power over your users.
Because software controls so many aspects of our lives. If we dont keep it open and respecting of our privacy, lots of people suffer.