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

fix: promote all the stuff to passed

Browse Source
This commit is contained in:
decentral1se
2025-03-13 22:45:31 +01:00
parent 97ba8b1a77
commit b9bff04773
6 changed files with 83 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

68
docs/federation/resolutions/in-progress/025.md
View File

@ -1,68 +0,0 @@
# Resolution 025 Maintainers Proposal
- Topic: Maintainers Proposal
- Date: 05-12-2024
- Deadline:
- Size: Large
## Summary
Create policies on recipe maintainence that meet industry standards, for example the designation of a recipe as stable or not if the recipe meets certain critera and having named maintainers.
## Details
Currently the CC recipes ecosystem is quite unclear. Some recipes are maintained really well and some are abandoned.
I propose that we adopt a "stable", "testing", "unstable" designation to help organise our recipes internally and present them in a clearer way externally.
We should take influence from the largest democratic software project [Debian](https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#) and implement a simplifier system of recipe maintainers to help build trust with our community and potential community members.
### Who are maintainers
Maintainers can be either fedi members, community collaborators or organisation collaborators (such as tech co-ops).
Maintainers will need to provide some way of contacting them e.g. and email address or Matrix handle.
Maintainers are welcome to use a handle/alias.
### Stable
"Stable" recipes must meet the following critera:
- Must have at least one named maintainer (handle is fine) with a matrix or email address and that infomation must be kept up to date in the README
- The upstream project must be considered active and able to respond to security issues
- Security issues in the recipe must be patched within one month of discovery
- Merge requests must be responded to with some form of aknowlegement or feedback within one month
- Has been upgraded in the last three months (if appropriate)
- The status score and README of the project should be kept up to date with relevant infomation
### Testing
"Testing" recipes must meet the following critera:
- Must have at least one named maintainer (handle is fine) with a matrix or email address and that infomation must be kept up to date in the README
- The upstream project must be considered active and able to respond to security issues
- Security issues in the recipe must be patched within one month of discovery
### Unstable
"Unstable" recipes must meet the following critera:
- Must have at least one named maintainer (handle is fine) with a matrix or email address and that infomation must be kept up to date in the README
### Unmaintained
If no one claims active responsibility for a recipe, its git repo will be archived and removed from the recipe catalouge.
## Implementation
- Docs updates to include explanations
- Ongoing coworks to add catergories to all recipes
- Package maintenance status will be added to the README metdata on all recipes. Rename existing "Status" to Features, use Status for this maintenance status.
- Add maintenance status to be visible on recipes.coopcloud.tech
- Every three months we go through the recipes and garden the status is and ping maintainers etc.
# Pre-Propose Feedback from community
* ~~Are maintainers community members or fedi members?~~
* ~~Should we add a requirement that stable recipe has to respond to issues and/or PRs within x amount of time?~~
* ~~will there be some form of automated check whether or not a recipe still fulfills a category's criteria?~~
* ~~What happens to recipes not fulfilling any criteria? e.g. having no maintainer. need for another category?~~

28
docs/federation/resolutions/in-progress/026.md
View File

@ -1,28 +0,0 @@
---
title: "Resolution 026"
---
- Topic: Budget 014: Backpay for `v0.10.x` abra release work
- Date: 08-01-2025
- Deadline: 22-01-2025
- Size: Large
### Summary
`@decentral1se` had spoons and cycles from roughly December 27th 2024 - January 5th January to make the final push of development work to get the new `abra` release out.
See the **WIP** [migration docs](https://docs.coopcloud.tech/abra/upgrade/#09x-beta-010x-beta) and [release blogpost](https://pad.local-it.org/G1TOcidEQtyArJU9gI0SDw?both#New-abra-release-candidate) for more information. TLDR; we have a release candidate that you can test today.
In this resolution, budget is being asked to *retroactively* cover this development work as "backpay".
### Details (Budget 014)
An [invoice was submitted already](https://opencollective.com/coop-cloud/expenses/234126) on our Open Collective based on a "fuzzy consensus" within the Co-op Cloud Federation chat. However, on reflection, concerns were raised that it would be better to follow our agreed decision making process and submit a resolution to vote.
There are 15 hours that are covered by [`R021`](https://docs.coopcloud.tech/federation/resolutions/passed/021/). However, the development of this work ran over by 3 hours. The remaining development work took 32 hours. The details of the specific tickets are on the [Open Collective invoice](https://opencollective.com/coop-cloud/expenses/234126). That brings the total amount of hours to 52.
#### Budget
`@decentral1se` has *already* carried out this work.
Proposed budget of 52 hrs * 20 EUR: 1040 EUR

22
docs/federation/resolutions/in-progress/027.md
View File

@ -1,22 +0,0 @@
---
title: "Resolution 027"
---
- Topic: MIR joins the Co-op Cloud Federation
- Date: 18-01-25
- Deadline: 31-01-25
- Size: Large
### Summary
[MIR](https://mirnet.org) would like to the join the Co-op Cloud Federation.
Several members of the project are involved in hacking recipes, there has been
personal contact via a call with `@decentral1se` (also several federation
members have expressed enthusiasm for them joining) and they have ambitions to
co-develop Co-op Cloud.
### Details
MIR can contribute fees at this time:
`@decentral1se` is happy to vouch 💖

15
docs/federation/resolutions/in-progress/028.md
View File

@ -1,15 +0,0 @@
# Resolution 028: Red Abya Yala joins the Co-op Cloud Federation
- Topic: Red Abya Yala joins the Co-op Cloud Federation
- Date: 16-01-2025
- Deadline: 30-01-2025
- Size: large
## Summary
Red Abya Yala is the network of Coopcloud nodes from Escuela Común. It has facilitated Coopcloud workshops during Escuela Común and some members have contributed to recipes.
Representative: `@fauno:sutty.nl`
* https://abyayala.sutty.nl/
* https://escuelacomun.yanapak.org/

79
docs/federation/resolutions/in-progress/030.md Normal file
View File

@ -0,0 +1,79 @@
---
title: Resolution 30 Budget 14: Federation Radmin
---
- Topic: Specify mandate & budget for federation radmin role
- Date: XX-XX-2025
- Deadline: XX-XX-2025
- Size: Large
## Summary
Experience shows that solid administration is the basis for effective self-organisation. We call this "radmin" (radical admin) because this admin work acts as a motor which boosts our self-organisation and coordination potential.
We are in a unique position to discuss and implement a financial model which can meet our vision of sustainability based on our democratic structure and decision making process.
We believe that it is more important than ever to make software project governance work without dictators. This role plays a critical role in making that possible.
Autonomic has been carrying out the financial administration so far but cannot continue to do this due to low capacity. No other federation member can pick up this work at this time.
To make progress, we propose to create a strict mandate for a paid radmin role which will be published as an open call. Anyone can fill this role, claim the budget and support the federation.
Federation members will decide on who fills the role based on an evaluation of the candidates. The open call draft will specify exact details once this decision is approved and will be presented to federation members. The open call will be agreed upon by discussion with fedi members feedback, not resolution.
## Details
### Term mandate
**IMPORTANT**: Extensions to this mandate can **only** be established through official decision making process.
* Up to 12 hours a month @ 20 GBP per hour based on the currently available federation membership dues
* Establishing a financial bookkeeping structure for the federation with associated documentation
* Instigating handover from Autonomic finance admin
* Leading a discussion which establishes a shared understanding of what financial sustainability means for the federation today with associated documentation
* Designing and implementing a new federation membership fees system which supports financial sustainability and is passed with a large decision
* Contribuiting to the Co-op Cloud wiki - https://docs.coopcloud.tech/ (training provided)
* Making sure invoices are submitted correctly and approving them via the Co-op Cloud Open Collective (OC)
* Managing budgets and faciliating timetracking against those budgets (e.g. https://kimai.coopcloud.tech)
* Herding cats
* Invoicing for your time each month to the Co-op Cloud OC
### Term duration
The term duration of this role is 1 year with a start date which will be decided in conversation with the contractor.
### Term revocation
The term of duration can be revoked by the federation via established decision making channels (large resolution) if issues cannot be reached through dialogue and constructive feedback.
In the event of revocation, there will be a collaborative feedback session between the federation and the contractor.
### Buddy system
Implementors of this resolution commit to a fixed monthly meeting, date/time to be determined, to check in and discuss challenges, progress, plans etc.
This is an important accountability structure which is not aimed to surveil the contractorp but ensure that both the federation and the radmin role are working well together and where things can be improved, take action together to resolve it.
### Open call
An open call is to be publised based on this proposal and shared openly. The open call will be presented as a draft to federation members before publishing. Exact details of the process, evaluation, start/end date etc. will be included in the text.
## Budget 014
The role is paid from the current membership fees, as decided on [R002](https://docs.coopcloud.tech/federation/resolutions/passed/002/). The hope is that by filling this role, we can increase this budget through the design and implementation of a more sustainable financial model for the federation.
Budget amount: GBP 250 per month
Who will implement this: decentral1se, kawaiipunk (Autonomic)
When will the money be spent: On an ongoing basis
What is the money for: Paying the working hours of whoever fills the role
## Legal
You will be a freelancer contractor and be responsible for your own invoices and taxes. Currently the Co-op Cloud project is stewarded by Autonomic Co-operative Limited and does not have it's own legal entity, so your freelance contract will be with Autonomic Co-operative Limited.
FEEDBACK
kawaiipunk - we have to setup a new bank account as the money is currently managed by Autonomic's WISE account (as a seperate "pot"). This might require registering as a co-op legal entity.
kawaiipunk - 20 EUR p/h is sooo loww. Maybe we can mention we are evaluating putting the wage up but we need the finance admin to do that.
fauno - we can talk with mayfirst folks about their experience with membership dues
fauno - thought it was going to be more project management. Will share with networks.
kawaiipunk: VeganVenom (Autonomic finance admin) is up for handover