refactor: feedback worked in
continuous-integration/drone/push Build is passing

This commit is contained in:
2026-11-19 18:16:33 +01:00
parent 4c68961ade
commit 9eb0902682
+4 -4
View File
@@ -111,21 +111,21 @@ One concrete example is the development of the new Docker Secrets Engine which w
The Co-op Cloud federation represents a diverse spectrum of use cases, some demanding highly constrained deployments (offline-first, single-board computers, intermittent electricity) and others requiring high throughput (increasing userbases, heavier and more powerful free software apps, specialised deployments and collaboration features). The development of fixes and new features must pass through this collective consensus, improving and becoming the exact feature scope which benefits all participants, including end-users. This involves many technical discussions and redesigns to reach the final result.
Co-op Cloud faces a new technical challenge in recent times. The project was developed for small-scale hosting collectives that already "know what they're doing" but the pragmatic accessibility of our tools has increasingly attracted new system administrators and emerging hosting collectives, some of whom have never even used the command-line before. This is a new use case which we must bring into our design thinking and implementation of our tools and documentation writing.
Co-op Cloud faces a new technical challenge in recent times. The project was developed for small-scale hosting collectives that already "know what they're doing" but the pragmatic accessibility of our tools has increasingly attracted new system administrators and emerging hosting collectives, some of whom have never even used the command-line before. This is a new use case which we must bring into our technical design and implementation of our tools and documentation writing.
Co-op Cloud tools have also become "officially" international since the Sepal Fund application from the Abya Yala Network in which we delivered a Spanish translation for Abra with full command-line coverage (options, docs, command output, etc.) and integration with a self-hosted Weblate deployment.
Co-op Cloud tools have also become "officially" international since the Sepal Fund application from the Abya Yala Network in which we delivered a Spanish translation for Abra with full command-line coverage (options, docs, command output, etc.) and integration with a self-hosted Weblate deployment. As far as we know, Abra is one of the few fully translated command-line tools (including e.g. options and flags).
This has been a great success but demands more internationalisation. This process challenges the limits of most free software projects approach to internationalisation. We have been forced to rely on an incomplete implementation of xgettext which we must migrate away from and even one of the most popular CLI Golang libraries (spf13/cobra) requires patching to deliver translated option flags. This requires us to make upstream contributions which are often hard to implement and deliver due to how deep reaching they are in the upstream implementation (implementing i18n in a codebase touches nearly everything).
## What is the ecosystem around your own project, and how will you engage relevant actors? For example, does your project depend on other projects/people? And who would be the main users? (max. 2000 characters)
The Co-op Cloud federation and solidarity network remains the primary ecosystem in which our project takes place. We congregate online in our Matrix community, publish through the Fediverse, share community updates on the Co-op Cloud blog (coopcloud.tech/blog) and by participating at events, doing workshops and presentations. End-users are included through their interaction with federation members on the local level. Federation members are currently based in Latin America, Australia, North America and Europe.
The Co-op Cloud federation and solidarity network is primary ecosystem in which our project takes place. We meet in our Matrix community, publish on the Fediverse, share updates on our blog (coopcloud.tech/blog) and participate at events, doing workshops and presentations. End-users are included through their interaction with federation members on the local level. Federation members are currently based in Latin America, Australia, North America and Europe.
Based on a usage survey conducted in October 2026, over 70% of Co-op Cloud participants offer paid free software services to customers. 2/3 of those are "small", serving less than 10 customers and 1/3 are "medium to large", serving 101-1000 customers. Here are some highlights of the most significant federation member projects:
- KolliCloud, a free software hosting platform built by Local-IT on top of Co-op Cloud serves, amongst others, Germany’s largest queer youth support organisation queersupport.de.
- Escuela Común, a hands-on self-organised school for emerging indigenous hosting collectives based in Latin America has seen 21 instances of Co-op Cloud deployed and managed by communities themselves with the emergence of 2 public media networks based on Peertube in Argentina and El Salvador.
- Escuela Común is a self-organised school for emerging indigenous hosting collectives based in Latin America which has seen 21 instances of Co-op Cloud deployed and the emergence of 2 public media networks based on Peertube in Argentina and El Salvador. Using Co-op Cloud, they were the winners of the 2025 IEEE Connecting The Unconnected Challenge.
- Merri-bek Tech, recently featured in ABC News as "a grassroots plan to reclaim the internet from 'big tech'" approaches climate resiliency from a "neighbourhood first" approach, incorporating Co-op Cloud as it's foundation in LoRes Mesh while building resilience features alongisde with peer-to-peer systems such as p2panda.