meissa/federate-your-repos
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Support mirroring your federated repositories to common plattforms in order to get found.
17 commits 1 branch 0 tags 55 KiB
HCL 100%
Find a file
Michael Jerger fd66fa7df1 update repo mirror
2024-06-20 19:59:05 +02:00
doc update repo mirror 2024-06-17 17:25:49 +02:00
codeberg.tf move code in order to be usaable as tf module 2023-07-26 08:07:46 +02:00
github.tf move code in order to be usaable as tf module 2023-07-26 08:07:46 +02:00
gitlab.tf move code in order to be usaable as tf module 2023-07-26 08:07:46 +02:00
LICENSE Initial commit 2023-04-22 09:08:01 +00:00
provider.tf move code in order to be usaable as tf module 2023-07-26 08:07:46 +02:00
provider_registry.tf move code in order to be usaable as tf module 2023-07-26 08:07:46 +02:00
README.md update repo mirror 2024-06-20 19:59:05 +02:00
variables.tf move code in order to be usaable as tf module 2023-07-26 08:07:46 +02:00

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