Skip to content

Choice of git forge #12528

@danielrainer

Description

@danielrainer

We currently use GitHub. In the context of #12526 it has been suggested to move to a different git forge and several people have expressed their support for such a change.

The main reasons to move off of GitHub as I see it are:

  • their push of LLM features without a way of disabling it
  • degradation/enshittification of the platform
  • reliance on proprietary software which could at any moment be taken away or modified in ways we don't like

In my view, an ideal replacement:

  • is fully based on Free Software
  • can reasonably be self-hosted
  • supports the features we want (we should define what those are)
  • can import the existing GitHub repo (issues, PRs, discussions)

This means we should decide on:

  • the forge technology
  • where to host it

It has been suggested in #12526 (comment) to use Codeberg-hosted Forgejo, which seems like a reasonable option to me.

Ideally, we have at least one mirror, such that forge availability is not tied to the availability of a single host.

One additional thing to consider is how CI would work. Right now we mostly use GitHub Actions, plus some Cirrus CI. Rewriting the GitHub Actions config should not be that much effort, but we still need to decide what to use as a replacement and how the hardware to run it on is provided.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions