Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move to a free git hosting platform

Open
#9 6 comments 18 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github, gitlab
Domain
devops, tooling

Research direction

Review the six-comment discussion and compare the hosting alternatives named in the issue: Codeberg, Gitea, sourcehut, and GitLab. Done would require a decided replacement platform and an agreed migration plan; the issue does not name files, tests, or implementation entry points.

Written by the indexing model from the issue text.

Description

Community is important.

Linux community is often aligned towards free and open-source initiatives; unfortunately, Github is not one of them. Not only it being a proprietary platform, it is also run by a huge unethical company that has a history of using copyleft-licensed code hosted on Github in their own proprietary products such as Copilot.

There is a lot of reasons why this decision can harm an open-source community and a lot of people who will be kept away from contributing to this project. This is a request to reconsider current hosting platform before it's too late.

There are currently a lot of great alternatives, such as Codeberg, Gitea and sourcehut.
Gitlab might also be a good choice for the sake of close collaboration with original wayland-protocols.

Thank you for your initiative and I hope it will shed a light on wayland future.
Let's not turn this place into a froggy pot for all of us 🐸.

Dominant language
Meson
Stars
434
Forks
5
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 misyltoad/frog-protocols

All issues in misyltoad/frog-protocols

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.