Go librepunk

src/_posts/2021-02-16-coop-cloud.md

@@ -1,17 +1,17 @@
 ---
 layout: post
 title: The Co-operative Cloud
-description: Free software infrastructure without re-inventing the wheel
+description: Libre software infrastructure without re-inventing the wheel
 image: coop-cloud.png
-category: coop, co-op, cloud, docker, swarm, free-software, hosting,
+category: coop, co-op, cloud, docker, swarm, libre-software, hosting,
 date: 2021-02-16
 ---
 
-Running [free software] apps and infrastructure for ourselves and our clients is central to what we do at Autonomic. Now, after a year of work, we're stoked to share our "Co-op Cloud" project with the world. We want to make it easier for others to join the party, ditch corporate spyware, and make their tools [sustainable, transparent and private].
+Running [libre software] apps and infrastructure for ourselves and our clients is central to what we do at Autonomic. Now, after a year of work, we're stoked to share our "Co-op Cloud" project with the world. We want to make it easier for others to join the party, ditch corporate spyware, and make their tools [sustainable, transparent and private].
 
 ## Why a new tool?
 
-We started out using [Cloudron], which provides a very simple-to-use web interface for deploying free software apps like Nextcloud, Mediawiki, and Rocket.chat with only a few clicks.
+We started out using [Cloudron], which provides a very simple-to-use web interface for deploying libre software apps like Nextcloud, Mediawiki, and Rocket.chat with only a few clicks.
 
 Cloudron allowed us to radically reduce our initial and ongoing server costs. We didn't need to maintain a separate server for each service and clients apps could share computing resources whilst containerisation was still allowing us meeting their data privacy needs. Consequently, we've been able to take on many more "solidarity clients", people doing important work, but on a shoestring budget.
 
@@ -19,7 +19,7 @@ As time has gone on, though, we've had a few moments when we questioned our reli
 
 - Core parts of the system officially [became proprietary] software. This rang alarm bells for us about its long-term future.
 
-- The work to package the available apps is done [entirely by the Cloudron team itself] and doesn't re-use the existing rich ecosystem of free software packaging work that's already being done. This seems like a big risk. If Cloudron UG, the company goes under, someone or some entity would need to take on that laborious, technically specific and non-transferable packaging work or we'd quickly be leaving ourselves and our clients running outdated and unmaintained software.
+- The work to package the available apps is done [entirely by the Cloudron team itself] and doesn't re-use the existing rich ecosystem of libre software packaging work that's already being done. This seems like a big risk. If Cloudron UG, the company goes under, someone or some entity would need to take on that laborious, technically specific and non-transferable packaging work or we'd quickly be leaving ourselves and our clients running outdated and unmaintained software.
 
 - Some aspects of Cloudron's architecture were causing problems. Requiring each app to be a single Docker image makes common application deployment configurations impossible (as far as we know, nobody has yet managed to get Mediawiki's visual editor working in Cloudron, for example).
 
@@ -39,7 +39,7 @@ So, around the end of 2019, we tried to map out a few core principles of a syste
 
 - Always be available under [copyleft licenses] to retain the shared work as part of the [commons](https://en.wikipedia.org/wiki/Commons). We shouldn't rely on creating [artificial scarcity](https://en.wikipedia.org/wiki/Artificial_scarcity) as a business model.
 
-- Work with existing free software communities who are already packaging and publishing their software (Nextcloud, Gitea, Mediawiki, Rocket.chat, the list goes on and on...). We want to be involved in their community spaces and build bridges between infrastructure, software development and end-users.
+- Work with existing libre software communities who are already packaging and publishing their software (Nextcloud, Gitea, Mediawiki, Rocket.chat, the list goes on and on...). We want to be involved in their community spaces and build bridges between infrastructure, software development and end-users.
 
 - Based on standardised technologies. Any new tools we write should only add a thin layer of usability on top of existing solutions.
 
@@ -71,11 +71,11 @@ Apps deployed via Co-op Cloud have automatic SSL certificates, and many come wit
 
 Packaging new apps for Co-op Cloud is straightforward in most cases: you can re-use an application's own Docker image (or even `docker-compose.yml` file) with minimal changes. We managed to [make a Co-op Cloud version of the Matomo web analytics platform in about 20 minutes]. This standardised architecture also means that nobody using Co-op Cloud is dependent on Autonomic for updates. When a new Wordpress update comes out, you can easily install it yourself or automatically without waiting for us to update some arcane custom Docker image.
 
-At this point, we'd like to invite other worker co-operatives or democratic collectives to take a look at what we're working on and have a chat with us. We have a public matrix room at `#coopcloud:autonomic.zone`. We think a common platform for hosting free software infrastructure could make a big difference in terms of what we're able to offer as a movement.
+At this point, we'd like to invite other worker co-operatives or democratic collectives to take a look at what we're working on and have a chat with us. We have a public matrix room at `#coopcloud:autonomic.zone`. We think a common platform for hosting libre software infrastructure could make a big difference in terms of what we're able to offer as a movement.
 
 If you're interested in getting involved with Co-op Cloud development, or if you'd like help trying out Co-op Cloud hosted services for yourself or your organisation, please [get in touch].
 
-[free software]: http://wikieducator.org/Libre
+[libre software]: http://wikieducator.org/Libre
 [sustainable, transparent and private]: /#core-values
 [cloudron]: https://cloudron.io/
 [became proprietary]: https://forum.cloudron.io/topic/2862/why-not-make-cloudron-fully-open-source-again