'It is fine not to like a piece of Free software' and other oft-unstated FOSS-related freedoms

“Free software”, according to the FSF’s definition, embodies four freedoms.

There are plenty more than that - or, at least, many freedoms which are inherent in, or arise from, those four freedoms - most of which go unstated most of the time.

This is far from a complete list, but rather my jottings based on ponderings and observations from the last few days, across a couple of different (intentionally unstated / unlinked here) things.

Users’ freedoms

A user has the freedom not to like a piece software, or some facet of it or its governance. Its UI. Its functionality. Its name. Its direction. Of course it is frustrating if something is a pain to use, whether that’s because one is used to a GUI and the software only offers a CLI, or whatever it might be. Of course it is problematic when a project persists in using a name which is an ableist slur.

A user has the freedom to grumble about the software, or how some facet of the software means that they are not going to use the software. (Well, freedom within the constraints of the rules of whatever system they are using to document that grumble; if they’re doing so on someone else’s computer, whoever runs that computer has the freedom not to permit that grumble…). And, IMHO, the expectation that they should be free to do so without harassment.

A user has the freedom not to fork, or submit a patch, for the software, or be expected to do so. Contributing back, in whatever ways, might help support the software, but it is not a requirement of Free software.

A user has the freedom not to use the software, or to use other software, not matter how their choice not to use it makes anyone else feel. Of course, it’s not massively helpful to tell a disgruntled user “well, you’re free not to use it” but, at that point, I suspect that the speaker is not genuinely trying to help the user.

Developers’ freedoms

A developer has the freedom not to listen to feedback, including grumbles, however it is phrased. Of course it can be frustrating if you’ve written something to scratch an itch, released it for Free in case it helps others, and now people are grumbling that it’s not good enough for their needs while contributing nothing back!

A developer has the freedom to choose which patches or third party contributions to accept (and thus which to decline or ignore). They might not have the time, expertise, or even simply the desire to consider them.

A developer has the freedom to refuse to do free work, or decline offers of paid work. Although I feel differently about companies benefiting from the commercial distribution but which do not fix accessibility or security issues.

A developer has the freedom to say “No more updates; this software does what I want, and that’s enough for me”.

Everyone’s freedoms

Everyone has the freedom to espouse views about what software other people should be using, or how they should be using it, again subject to the rules of the platform(s) on which they are posting. But not to the point of harassment.

Everyone has the freedom to mute and block others, for any reason or none. Muting, blocking, and other forms of filtering are self-care.

Everyone has the freedom to reflect on others’ opinions, feelings, and needs. And the freedom to ignore them.

Everyone has the freedom to hold their own views on this, including to disagree with anything I’ve said here.