Boost this if you want to be part of an explicitly anticapitalist technology liberation movement.

I am drawn more and more towards simply "communal software". It is simple and to the point without needing to bring in a lot of loaded political baggage. Sure capitalists might fund some of it, but I think it would be significantly more difficult for capitalists to co-opt "communal software" than the nebulous "open source" which has had its meaning intentionally diluted and stretched to absurdity.

"Communal software" might not totally keep obnoxious libertarians away, but it I think it would do a pretty good job of preventing them from dominating the discourse.

@be "Software of the Commons" to directly invoke the Tragedy of the Commons? Doesn't exactly roll off the tongue though.

@splatt9990 I think "commons software" would be too easy for corporations to co-opt for precisely that reason.

@splatt9990 "Creative Commons" has been co-opted. @lightweight can tell you more about that if you're interested.

@lightweight @be @splatt9990 Yesterday, I went on a bit of a rant about this same topic (social.finkhaeuser.de/@jens/10 if you want)

I'm all for "communal software". What I'm more concerned with, though, is how we define that.

Problem is, I *like* the four freedoms, I just don't think they are enough. The "communal" term suggests the right direction.

I struggle a bit to define the necessary other communal aspects in a similarly concise form.

@lightweight @be @splatt9990 I figure the UNIX approach of one tool, one job is closely related to the "toolkits over frameworks" kind of thinking. To me, both enable freedoms because they allow much more varied re-use, being less prescriptive to users.

But it's hard to put them into a license - not that I particularly want to - this would have to be more of a manifesto. And then it's still a fuzzy enough thing that people can interpret it differently.

@jens @lightweight @splatt9990 I don't think it's a great idea to mix engineering best practices into a political philosophy.

@be @lightweight @splatt9990 @jens This comment is what prompted me to think about how good engineering practices would contribute to user freedom and that's why I wrote the maturity model draft libranet.de/display/0b6b25a8-3… basically just to see where I put them.

I put them last.

In Open Source, engineering practices basically come out on top, topped only by the licensing.

Little did I know you had already written your manifesto. I was shown to it after I finished my list and my chin fell to the floor. The zeitgeist is strong with this one.

I talked with a friend about these issues the other day just before I learned about the rms surprise.
Follow

@clacke @lightweight @splatt9990 @jens Yes, I think the zeitgeist is ripe for new terminology and philosophy to replace the old. I'm pleasantly encouraged how much support there is for this right now.

Sign in to participate in the conversation
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.