add paused status rather than remove paused members

except d1 who is genuinely no longer a federation member
Update membership list
2026-10-01 15:29:17 +00:00 · 2026-09-23 14:54:55 +00:00
4 changed files with 0 additions and 81 deletions
@@ -1,18 +0,0 @@
---
-title: "Resolution 046: 3wc to join the federation as an individual member"
---
-
- Topic: Resolution 046: 3wc to join the federation as an individual member
- Date: 2026-09-30
- Deadline: 2026-10-15
- Size: large
-
-## Summary
-
-3wc to join the federation as an individual member
-
-## Details
-
-@3wc:autonomic.zone is an active member of our community and supports with some of the ongoing work. they were a member of one of our cooperative members (autonomic) but they are no longer part of the cooperative but would like to stay in the cooperative as an individual member.
-
-@ammaratef45:matrix.org from [RTM](https://resisttechmonopolies.online/) is happy to vouch.
@@ -1,28 +0,0 @@
---
-title: "Resolution 047: Kolektivo Sennacieca Cifereca to join the federation as a member"
---
-
- Topic: Resolution 047: Kolektivo Sennacieca Cifereca to join the federation as a member
- Date: 2026-10-06
- Deadline: 2026-10-20
- Size: large
-
-## Summary
-
-[Kolektivo Sennacieca Cifereca](https://sekuro.nl) is a security and organizational consultancy responsible for the proof of concept  [Hestia](https://git.coopcloud.tech/hex/hestia) build quality and security analyzer and [CCSATool](https://git.coopcloud.tech/hex/CCSATool) security advisory tool. KSC is focused on the improving the security of the platform. 
-
-## Details
-
-At Kolektivo Sennacieca Cifereca we provide security consulting, security reviews, security program guidance, and penetration testing services. We would like to use and recommend services provided by Co-op Cloud member organizations, and thus have a vested interest in driving security improvements within the federation.
-
-We have worked closely with eCommons, providing security guidance and identifying opportunities for improvement at the federation level (recipe scanning via Hestia, and security advisory announcement via CCSATool).
-
-We agree with eCommon's assessment:
-
-> Co-op Cloud's federated model, tooling maintained collectively by the co-ops that use it, matches how we think infrastructure should be built and sustained. 
-
-Further, we believe that distributed systems may present additional challenges related to pushing forward security initiatives, but they provide increased resilience against state-level threat actors with the goal of shutting down infrastructure by geographical region or ideological alignment. 
-
-@dannygroenewegen:matrix.org from eCommons has agreed to vouch for this organization. 
-
-Kolektivo Sennacieca Cifereca's representative to the federation will be hex. He can be reached at `@hex:matrix.org` on Matrix or `biz@sekuro.nl` by email.
@@ -1,33 +0,0 @@
---
-title: "Resolution 046: Restore servers.coop as a Coop Cloud project"
---
-
- Topic: Restore servers.coop as a Coop Cloud project
- Date: 2026-10-13
- Deadline: 2026-10-27
- Size: medium
-
-### History
-
-[servers.coop](https://servers.coop) was launched as a project of Coop Cloud, intended to cooperatise lower down the stack than the abra toolshed. Similarly to how abra gives small cooperatives the tools to easily and collaboratively deploy services on a cloud, servers.coop is meant to support small cooperatives in deploying VPSs on hardware owned or managed by them.
-
-The project was left on the backburner for some years. Recently, we were motivated by rising data center costs and concerns about digital sovereignty to start working on the project again. A working group of four-ish people from the Coop Cloud community is currently working on defining and deploying an MVP.
-
-Servers.coop goals are closely aligned with those of Coop Cloud as a whole, but its usecases and userbase may end up diverging from those of abra. In the long term, servers.coop ought to become an independent collective, with its own governance, membership, budget, and infrastructure - similarly to how Coop Cloud grew from an Autonomic project into a distinct federation. In the short term, servers.coop needs the support of the Coop Cloud federation.
-
-### Proposal
-
-Formally, we treat servers.coop as a project of the Coop cloud federation.
-
-This grants the servers.coop project access to Coop Cloud's resources. For instance:
-
- Coop Cloud server infrastructure can be used to organize and manage the project, including:
-   - conferencing or notetaking services provided by members for Coop Cloud use
-   - git.coopcloud.tech
-   - build.coopcloud.tech
-   - the servers.coop domain and subdomains
- Grants written on behalf of Coop Cloud can include servers.coop in their goals and budget.
- Coop Cloud federation members can propose and vote on resolutions regarding servers.coop governance, infrastructure, and budget.
- Coop Cloud budget can be allocated to servers.coop goals, through resolutions.
-
-This support is intended to be temporary. Over the course of several years, the group working on/with servers.coop ought to move its resources onto dedicated instances and establish its own structure of governance and financing. When this happens, a new resolution should be passed to formally establish the new collective and change how Coop Cloud participates in the project.
@@ -149,8 +149,6 @@ nav:
              - federation/resolutions/stalled/030.md
          - "In Progress":
              - federation/resolutions/in-progress/045.md
-              - federation/resolutions/in-progress/046.md
-              - federation/resolutions/in-progress/047.md
              - federation/resolutions/index.md
      - "Minutes":
          - federation/minutes/index.md