DAO-managed operational infrastructure

Open
#43 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, gitlab
Domain
devops, distributed-systems, infrastructure

Research direction

Start with the SaaS, self-hosted, and peer-to-peer comparison in the issue, then review the linked GitLab, Radicle, Fleek, Element, Jitsi, and Livepeer resources. Clarify which operational services are in scope and compare the listed alternatives against autonomy and decentralization. Done means an agreed migration plan with selected tools and documented next steps.

Written by the indexing model from the issue text.

Description

Tech

Consider migrating our Ops stack from admin-dependent 3rd party services to tools that are...

  1. Autonomous. Resilient to external interference (not reliant on closed-source corporate software)
  2. Decentralized. Resilient to internal malfeasance (not reliant on trusted admins)
SaaS 1. Self-Hosted (autonomous) 2. Peer-to-Peer (decentralized)
Code Github Gitlab? Radicle?
Email & Calendar Zoho Fleek Space Daemon?
Chat Keybase Element? Fleek Space Daemon?
Calls Jitsi Jitsi Self-Hosted Livepeer?
Website Netlify Fleek Hosting?
Database Airtable Fleek Database (coming soon)
Dominant language
No language data
Stars
17
Forks
12
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dOrgTech/docs

All issues in dOrgTech/docs

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.