Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Alternative git forge to GitHub #18

Open
avivace opened this issue Aug 4, 2024 · 4 comments
Open

RFC: Alternative git forge to GitHub #18

avivace opened this issue Aug 4, 2024 · 4 comments

Comments

@avivace
Copy link
Member

avivace commented Aug 4, 2024

GitHub is not open source. GitHub Actions run on proprietary runners and we're increasingly relying on CI/CD pipelines based on them.

We need to establish a reliable alternative solution which we can start adopting as a mirror/backup for the time being and, in case of service disruptions, policy or billing changes, easily migrate to it.

The features we're interested in are:

  • Plain git hosting
  • Releases/Binaries
  • CI/CD (GitHub Actions)
  • Static serving capabilities (GitHub Pages)
  • Issue trackers

Those features may be provided by different solutions, provided they can be integrated easily. Bonus points if the suggested products are open source and self-hostable themselves.

@ISSOtm
Copy link
Member

ISSOtm commented Aug 4, 2024

Alternatives:

  • GitLab
  • Self-hosted Gitea instance
  • SourceHut

I know SourceHut provides all of the requested features except for releases (in theory they can be shimmed by implementing that ourselves via the static site serving, but that's more effort on our side.)

I can't speak for GitLab or Gitea, as I've hardly used those.

@CasualPokePlayer
Copy link

proprietary runners

They're not really proprietary, creating the VM images used by the default runners can be done as the code for doing so is open source. Additionally, you are able to just use your own self hosted runner using whatever if you really want to (although in practice having this setup at all would just be a backup given how very very generous GitHub is with its free runners).

@avivace avivace mentioned this issue Aug 4, 2024
@pinobatch
Copy link
Member

How easy would it be for contributors to adapt to SourceHut's email-based workflow? From "Step 2" on git-send-email.com:

Your email provider should have instructions somewhere for SMTP access.

I wasn't aware the popular email providers (Gmail and Outlook) were still offering SMTP in a way that integrates well with command-line tools. It turns out the page gives instructions for Gmail but not Outlook (formerly Hotmail).

@aaaaaa123456789
Copy link
Member

Outlook supports SMTP (I'm currently using it).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants