autonomic-cooperative
/
autonomic.zone
Archived
5
0
Fork 0
Code Issues 15 Pull Requests 2 Releases Activity

Additional changes

This commit is contained in:
KawaiiPunk 2021-02-23 18:27:11 +00:00 committed by Luke Murphy
parent d533b5988e
commit fe205e1ac1
No known key found for this signature in database
GPG Key ID: 5E2EF5A63E3718CC
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/_posts/2021-02-16-coop-cloud.md
View File

@ -39,17 +39,23 @@ So, around the end of 2019, we tried to map out a few core principles of a syste
- Co-op Cloud should 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.
- Co-op Cloud doesn't re-invent the wheel. We aim to 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.
- Co-op Cloud aims to 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.
- Co-op Cloud has democratic governance at the core of the project. We want to collaborate as much as possible with other co-operatives to build up good decision-making structures so we can all rely on this project into the future.
- Co-op Cloud is based on standardised technologies. Any new tools we write should only add a thin layer of usability on top of existing solutions.
- Co-op Cloud has democratic governance at the core of the project. We want to collaborate as much as possible with other co-operatives to build up effective decision-making structures so we can all rely on this project far into the future.
- Co-op Cloud is focussed on meeting the needs of small hosting providers with technical workers in order to provide a solid service for their clients.
- We encourage the creation of a configuration commons. Innovations based on Co-op can easily be shared and worked on collectively.
In our spare time (partly funded by income from working for our wonderful clients 😀) we've been putting the pieces together; and after a year of work (including two "back to the drawing board" moments), we're ready to launch an [alpha version](https://en.wikipedia.org/wiki/Software_release_life_cycle) of Co-op Cloud to the public.
## Co-op Cloud public alpha
co-op Cloud is a simple packaging format using existing [open standards] to build a catalogue of applications, and a command-line client to read the catalogue and deploy those applications.
Co-op Cloud is a simple packaging format using existing [open standards] to build a catalogue of applications, and a command-line client to read the catalogue and deploy those applications.
If you'd like to learn more about co-op Cloud, please read [our documentation], where we explain the decisions we've made so far in more depth. What technologies we're using, how we fit into the existing ecosystem, ways to contribute, what applications are available and so on.
If you'd like to learn more about Co-op Cloud, please read [our documentation], where we explain the decisions we've made so far in more depth. What technologies we're using, how we fit into the existing ecosystem, ways to contribute, what applications are available and so on.
We've already been deploying Co-op Cloud as part of "dual power" strategy. We use Co-op Cloud to run some of our own and our clients' infrastructure while continuing with Cloudron and other strategies for the time being. We're seeing promising stability and it's been a joy to work with.