rix/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: update with uploaded content

Browse Source
This commit is contained in:
decentral1se
2026-11-04 11:48:06 +01:00
parent 91c93fb1b4
commit ea9d7e6786
1 changed files with 14 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/federation/funding/nlnet-restack.md
+14 -26
View File
@@ -22,16 +22,14 @@ Scaling the Co-op Cloud Software Commons.
- [coopcloud.tech](https://coopcloud.tech)
- [docs.coopcloud.tech](https://docs.coopcloud.tech)
- [recipes.coopcloud.tech](https://recipes.coopcloud.tech)
- [`git.coopcloud.tech/toolshed/abra`](https://git.coopcloud.tech/toolshed/abra)
- [`git.coopcloud.tech/toolshed/alakazam`](https://git.coopcloud.tech/toolshed/alakazam)
- [`toolshed/recipes-catalogue-json`](https://git.coopcloud.tech/toolshed/recipes-catalogue-json), [`toolshed/almanac`](https://git.coopcloud.tech/toolshed/almanac)
## Please summarise the proposed project and its expected results in a few lines. (max. 1000 characters)
Co-op Cloud is a software commons, international federation and broad solidarity network which works towards a vision of democratic technology for everyone.
We focus here on the software commons: a suite of tools and shared configs which simplify the deployment and maintenance of free software apps. Co-op Cloud implements a "pragmatic restack" where the daily needs of small-scale hosting collectives are the central driving force.
We focus here on the software commons: a suite of tools and shared configs which simplify the deployment and maintenance of free software apps. Co-op Cloud implements a "pragmatic restack" where the needs of small-scale hosting collectives are the central driving force.
This approach has lead to considerable decentralised growth and international adoption with an estimated 50-100 active operators, 20-40 hosting collectives, thousands of end-users, 21 federation members and successful commercial projects built on top of Co-op Cloud.
@@ -47,7 +45,7 @@ This growth pushes our implementation to its limits, revealing issues in impleme
We propose an hourly rate of 60 EUR per hour with a total of 798 dev hours (breakdown below per heading). We anticipate no expenses. Please see attached work.pdf for more.
**Maintenance & Technical Debt** (233 hours)
Maintenance & Technical Debt (233 hours)
- Fix the oustanding (as of Nov 2026) 21 bugs in Abra reported by operators. These issues represent daily friction for operators and make deployment, maintenance and collaboration work more difficult to carry out.
@@ -57,13 +55,13 @@ We propose an hourly rate of 60 EUR per hour with a total of 798 dev hours (brea
- Migrate to the new compose-go standard library in Abra so that we maintain parity with one of the central open standards which we rely on. This decouples our sole reliance on the Docker Swarm runtimes (out-of-date) implementation of the Compose Specification.
**Performance** (100 hours)
Performance (100 hours)
- The Co-op Cloud catalogue is a single JSON file which is becoming a performance bottleneck for Abra. We will convert catalogue generation and querying into a lightweight API service which always provides fast results regardless of quantity of app configs which integrates with Abra.
- Abra development follows the "make it work, make it right, make it fast" principle. We are now in the "make it fast" phase. Abra requires profiling to understand where it is doing double work and unecessary bookkeeping. The goal is to return to a high speed CLI experience.
**Distributed Collaboration & Operations** (450 hours)
Distributed Collaboration & Operations (450 hours)
- Co-op Cloud currently "takes over" an existing server, imposing a single web proxy choice. Operators need proxy agnosticism, supporting several popular proxies seamlessly (e.g. Traefik, Nginx, Caddy).
@@ -73,9 +71,9 @@ We propose an hourly rate of 60 EUR per hour with a total of 798 dev hours (brea
- With the development of the new Docker Secrets Engine, it is possible to decouple the secret injection of Abra from the Docker Swarm runtime. Implementing secret engine support in Abra would reduce our reliance on the Docker runtime overall due to its pluggable interface with independent secret management tools.
- Due to increasing numbers of app config maintainers, there are more pull request review workflows happening on git.coopcloud.tech. The Abra app config upgrade and release functionality does not conveniently support a pull request workflow. We will implement this workflow support in Abra by allowing Abra to produce and adapt to diffs which are designed for a review, approve and apply workflow.
- Due to increasing numbers of app config maintainers, there are more pull request review workflows. The Abra app config upgrade and release functionality does not conveniently support a pull request workflow. We will implement this workflow support in Abra by allowing Abra to produce and adapt to diffs which are designed for a review, approve and apply workflow.
- Co-op Cloud operators currently sync their app config changes manually using Git (e.g. deployment version). We will implement a peer-to-peer sync in Abra which allows operators to inform each other about deployment and maintenance operations directly on the command-line. We aim to implement this using p2panda-go (Iroh under the hood).
- Co-op Cloud operators sync their app config changes manually using Git (e.g. deployment version). We will implement a peer-to-peer sync in Abra which allows operators to inform each other about deployment and maintenance operations directly on the command-line. We aim to implement this using p2panda-go (Iroh underneath).
- Alakazam is a longrunning prototype used by KolliCloud (free software hosting platform built on Co-op Cloud) which implements a wrapper of Abra and supports the deployment of multiple apps in a single "stack" (e.g. deploy Nextcloud, BigBlueButton and Rauthy SSO with shared config). It has reached maturity and been adopted by the Co-op Cloud federation as an official community tool. There is a desire to bring the feature set of Alakazam back to Abra, ending the "wrapper of a wrapper" prototype implementation and giving all Co-op Cloud operators first-class support for seamless "stack" deployments without needing an additional tool.
@@ -97,7 +95,7 @@ We maintain a comparisons list (docs.coopcloud.tech/intro/comparisons) to establ
- We re-use upstream packaging efforts of free software developers and meet them where they are at: the compose standard. All app configs form our config commons which can be re-used by any tool which consumes the compose standard (e.g. Guix ports have been attempted).
- We realise real "should to shoulder" collaboration on free software app configs with the flexibility of the compose standard. A hosting collective of 2 hackers and another of 200 hackers can work in the same app config without crashing into each other with each deploying a config which is radically customised for their specific situation. Their respective app config maintenance work always contributes back to each other and the greater software commons.
- We realise real "should to shoulder" collaboration on free software app configs with the flexibility of the compose standard. A hosting collective of 2 hackers and another of 200 hackers can work in the same app config without crashing into each other with each deploying a config which is radically customised for their specific situation. Their respective maintenance work contributes back to each other and the greater software commons.
- One of the major strengths of Co-op Cloud is its relative familiarity and simplicity for (new) operators in comparison to other tools. Abra follows the Docker CLI design closely and there is limited indirection and abstraction: it's images and compose files underneath and that's it.
@@ -141,13 +139,9 @@ Based on a usage survey conducted in October 2026, over 70% of Co-op Cloud parti
## Does (or did) the project have other funding sources? (max. 1000 characters)
Co-op Cloud has received 32,986 EUR from the European Cultural Fund in 2022.
Co-op Cloud has received 32,986 EUR from the European Cultural Fund in 2022, 9,240 GBP from a private funder in 2023 and receives up to three years of financial support (~5000 USD) via The Sepal Fund since 2025.
Co-op Cloud received 9,240 GBP from a private funder in 2023.
Co-op Cloud receives up to three years of financial support (around 5000 USD) via The Sepal Fund since 2025 when the Abya Yala Network was accepted as a grantee. Sutty is a Co-op Cloud federation member and founding member of the Abya Yala Network.
Local-IT, a Co-op Cloud federation member based in Germany has received 540,000 EUR in public and civic funding to build KolliCloud, a free software hosting platform built on Co-op Cloud. This funding was managed and allocated by Local-IT themselves with the implementation benefitting the entire Co-op Cloud software commons.
Local-IT, a Co-op Cloud federation member based in Germany has received 540,000 EUR in public funding to build KolliCloud, a free software hosting platform built on Co-op Cloud.
The Co-op Cloud federation has developed a membership model which funds 5-10 hours of software development and maintenance work a month. Member fees have also funded social processes such as organising the community "walk-in" Kite-flying hours and a year long position for a financial administrator for the federation.
@@ -157,11 +151,9 @@ The Co-op Cloud federation receives donations via Open Collective for providing
## Attachments are not needed. Please ensure the proposal is self-contained. But in case you have supplementary material you wish to share (e.g. spreadsheets, diagrams, endorsements), you can do so here. (As HTML, PDF, ODF, images or plain text. Max 50 MB in total.)
### `work.pdf`
Links to specific work items, more context and a brief budget explanation.
#### Budget
## Budget
Estimation system used:
@@ -171,7 +163,7 @@ Estimation system used:
Times and totals are included below. Final totals are included at the end.
#### 1) Maintenance & Technical Debt
## 1) Maintenance & Technical Debt
> Fix the oustanding (as of Nov 2026) 21 bugs in Abra reported by operators. These issues represent daily friction for operators and make deployment, maintenance and collaboration work more difficult to carry out.
@@ -199,7 +191,7 @@ We estimate 30 hours, medium.
**TOTAL**: 248 hours
#### 2) Performance
## 2) Performance
> The Co-op Cloud catalogue is a single JSON file which is becoming a performance bottleneck for Abra. We will convert catalogue generation and querying into a lightweight API service which always provides fast results regardless of quantity of app configs which integrates with Abra.
@@ -215,7 +207,7 @@ We estimate 40 hours, medium.
**TOTAL**: 100 hours
#### 3) Distributed Collaboration and Operations
## 3) Distributed Collaboration and Operations
> Co-op Cloud currently "takes over" an existing server, imposing a single web proxy choice. Operators need proxy agnosticism, supporting several popular proxies seamlessly (e.g. Traefik, Nginx, Caddy).
@@ -261,15 +253,11 @@ We estimate 100 hours, large.
**TOTAL**: 450 hours
#### Final totals
## Final totals
* 248 + 100 + 450 = 798 total hours
* 798 * 60 EUR hourly rate = 47880 EUR
### `cv.pdf`
The CV of the submitter.
# AI disclosure
## Did you use generative AI in writing this proposal?