Mert Gör
21c2096b85
---
Before touching code, articulate the **why** and **who**:
- **Federative Manifesto**: Write a short document outlining the principles—AGPLv3-or-later licensing, collective attribution, user sovereignty, cultural symbolism (if you want to weave in motifs like bunnies 🐇).
- **Core Modules**:
- **Auth & Identity**: Federated login, GECOS field integration, LDAP/SSO support.
- **Storage**: Object storage (MinIO, SeaweedFS), Git storage (Gitea, Forgejo), encrypted vaults.
- **Communication**: Matrix integration, IRC bridges, internal messaging.
- **Org Management**: Roles, permissions, dashboards, metadata schemas.
- **Monitoring & Logs**: Prometheus, Grafana, Loki, with federative visibility.
---
Choose tools that align with your federative ideals:
| Layer | Tech Options |
|--------------------|------------------------------------------------------------------------------|
| Frontend | SvelteKit, Vue 3, or SolidJS (modular, fast, open) |
| Backend | Go (for speed and federation), .NET Core (for orchestration), or Rust |
| Storage | MinIO, Forgejo, Gitolite, SeaweedFS |
| Communication | Matrix + Element, IRCd + TheLounge |
| Auth & Identity | Keycloak, Authelia, or custom federated shell scripts |
| Infra Orchestration| Docker Compose, Nomad, or Kubernetes (with ethical deployment constraints) |
---
Start with a **minimal viable federation**:
- Build a CLI tool to manage users, storage, and Git repos.
- Create a dashboard that visualizes org structure and metadata.
- Integrate one communication protocol (Matrix or IRC).
- Ensure everything is modular—each service can be swapped or extended.
---
- Write **modular docs**: architecture, setup, contribution guide.
- Include **cultural notes**: why federative design matters, how attribution works.
- Publish on Codeberg or Forgejo, not just GitHub.
- Invite contributors from Boğaziçi and the open source world.
---
Give it a name that reflects your federative vision. Something like:
- **Amassivus Panel** (if tying into your existing ecosystem)
- **BunnyCloud** (if you want to lean into cultural motifs)
- **FXBoard** (if it’s part of the FX framework)
---
Want help drafting the initial manifesto or scaffolding the repo structure? I’d love to co-create it with you.
|
||
|---|---|---|
| .gitignore | ||
| cloud.masscollabs.xyz.txt | ||
| forgejo.txt | ||
| LICENSE | ||
| README.md | ||
Cloud Roadmap
Cloud for Forgejo, Woodpecker CI/CD, and storage with GNU/Linux
We QB Networks and Masscollabs Services are leading to Software, Hardware and Science for the Internet Cyberspace with our own consciousness. We have our own roadmap and which is why we say we are a Free Software project. This is an open way to software and open infrastructures ...
License
Copyright (C) 2025 QB Networks
Copyright (C) 2025 Masscollabs Services
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see https://www.gnu.org/licenses/.