@someodd The main problem with GitHub to me is that the expectation (including from certain package repos) that all free software projects use it! And that many devs are clueless as to how to collaborate without it.
You should not feel pressured to use GitHub, but if you like it do use it! Just please document how others can report issues & contribute outside GitHub.
But given you disagree with them I'll vote "Stop using GitHub". Personally I self-host CGit with a rudimentary issue tracker.
A 2014 blog post on this, still relevant: https://nedbatchelder.com/blog/201405/github_monoculture.html
@someodd Depends on your goals and use cases.
If you're trying to promote a new project, GitHub is the most visible and its workflow most likely to be familiar to potential contributors.
Gitlab is my favorite alternative; good product, comparable feature set, good visibility, open source.
Bitbucket is fine if you don't mind Atlassian upsell.
Sourcehut is "public alpha" and not as featureful as the other three, but has a distinct philosophy and is the most Free Software oriented.
@someodd Alternatives? Publish your own repo with something simple like gogs or something more complex like gitea. Use gitlab on your own server. Use gitlab on their server. Use sourcehut.
GitHub invented the idea of "Pull Request" being something, whereas we all already had the idea of "send me a patch". It encourages you to fork a project on github (using a github account) before being able to engage with the upstream devs. Just a simple way to inflate their usercount and force people away from alternatives.
tldr; Self-host, or use (sourcehut|gitlab)
@someodd I'm paying for hosting on SourceHut, and using that for new repos as I slowly transition off of GitHub.
My long term plan is "hydra hosting", using multiple git remotes of equal status: https://seirdy.one/posts/2020/11/18/git-workflow-1/ I intend to use SourceHut, Codeberg, and self-hosting on my own server.
I think one advantage of GitHub's size and corporate backing is that it's unlikely to disappear suddenly. Hydra hosting means that even if one remote goes down, I can continue seamlessly with the others.
@someodd A top problem with this approach is figuring out how to handle issues in a decentralized way. The SourceHut approach is an email-based workflow, but this is pretty alien for people used to GitHub.
I'm planning to move my issues into my repo using git-bug, so I can take them with me wherever I go: https://github.com/MichaelMure/git-bug
But I'm waiting for the next release, which will include a fix for their GitHub bridge so I can easily export my issues. (It's already fixed in the latest dev version)
@someodd I think it's nice to support a diversity of services. I have been using Codeberg lightly for a couple of years, and I'm starting to lean on it more. My requirements are few and light, so YMMV.
I'd be very interested in other services based on Gitea, or even starting my own Gitea instance.
@someodd I have moved my repos from Github to https://codeberg.org. It's mostly a hosted Gitea with some additional features like hosting static pages. Berlin based non-profit, so I decided to pay them 48€/year for their wonderful service. I am keeping my GitHub account in case I want to do some fly-by fix for a repo that lives there.
@someodd I'm personally keeping my GitHub as a mirror because that's still where most developers are, but I'm starting all my new projects on Codeberg these days. GitLab has better features than Gitea (what Codeberg runs on) though.
I don't know the right answer at this point, but I know for certain most of the big projects aren't moving off GitHub anytime soon, so I'd rather have an account there so I can contribute when I need to 🤷♂️
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.