Support mirroring your federated repositories to common plattforms in order to get found.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Michael Jerger fd66fa7df1 update repo mirror 4 weeks ago
doc update repo mirror 1 month ago
LICENSE Initial commit 1 year ago
README.md update repo mirror 4 weeks ago
codeberg.tf move code in order to be usaable as tf module 12 months ago
github.tf move code in order to be usaable as tf module 12 months ago
gitlab.tf move code in order to be usaable as tf module 12 months ago
provider.tf move code in order to be usaable as tf module 12 months ago
provider_registry.tf move code in order to be usaable as tf module 12 months ago
variables.tf move code in order to be usaable as tf module 12 months ago

README.md

federate-your-repos

Support mirroring your federated repositories to common plattforms in order to get found.

Contents

Rationale

It is always the same - it's about regaining digital sovereignty.

With OpenSource, the story is absolutely comparable to the situation on Twitter, Facebook or Youtube. You have invested countless hours to realize your idea and building a community. The big platforms profit from this.

We advocate that the fruits of our investment end up with us and not with Microsoft, Facebook, Twitter or Gitlab.

So we will no longer propagate links to Github, Gitlab or any other non OSS platform. Our ideal world is fully federated.

But we don't live in this perfect world yet. That is why we present our model to handle this intermediate time. Here are some principles:

  1. Any marketing invest (links in blogs, mblogs, toots, ...) will link to our own repository.
  2. In order to enable interaction with our community we accept issues & PR on the most relevant and the least unappealing platform.
  3. We interact primarily with the platform our CI is running on.
  4. We mirror our repository to the remaining bunch of platforms in order to get found if someone is searching for our OpenSource solution.
  5. Every repository has a section where we accept Issues & PRs and where mirrors exist.

Concept

Mirroring

At the moment our CI is running on gitlab, so thats our current model

flowchart LR
    m[Maintainer]
    co[Community]
    o[Origin at our repo server]
    gh[mirror at GitHub]
    gl[mirror at GitLab for CI]
    cb[mirror at codeberg for federation test]
    m -->|interact| o
    o -->|mirror on push| gh
    o -->|mirror on push| gl
    gl -->|artefacts from ci| o
    o -->|mirror on push| cb
    co -->|issues & PR| cb
    cb -->|PR manual with git| o

Artifacts & CI

Development & mirrors

Development happens at: https://repo.prod.meissa.de/meissa/federate-your-repos

Mirrors are:

For more details about our repository model see: https://repo.prod.meissa.de/meissa/federate-your-repos