Does anyone have any experience using Radicle (radicle.xyz) for a non-toy project? I ran across it in an HN comment the other day and have been playing with it, but am curious to hear from someone who's done more than that.
How and Why to Ditch GitHub
11–20 of 22 posts
Re: How and Why to Ditch GitHub
#12For a self hosting solution I'd recommend gitea: it's a single go binary that needs almost no installation (only a config file), it's very fast, updates work great (replace previous binary and restart), supports ldap and has all the features of GitHub your love and even various features that free GitHub does provide (ie branch protection for private repos).
For those who don't know, Forgejo is a fork of Gitea.
Re: How and Why to Ditch GitHub
#13There was very little "Why" in this article. It seems like: 1. Microsoft bad 2. USA bad 3. I had a gut feeling. I think the Actions support being so lacking is a deal breaker for us. I know we can bring our own. But I really don't want to manage infra here and take on that responsibility.
This is currently topical: https://www.businessinsider.com/github-ceo-developers-embrac...
[deleted]
Re: How and Why to Ditch GitHub
#14For a self hosting solution I'd recommend gitea: it's a single go binary that needs almost no installation (only a config file), it's very fast, updates work great (replace previous binary and restart), supports ldap and has all the features of GitHub your love and even various features that free GitHub does provide (ie branch protection for private repos).
I prefer cgit. It's used by the linux kernel and many others.
Re: How and Why to Ditch GitHub
#15> GitHub's use of everyone's code to train its language models Unless GitHub knowningly trains on code in private repositories (not that I am aware of), it does not matter where you host your code, or whether it's GPL or MIT licensed. Someone is training their models using your code. That's just a matter of life.
[deleted]
Re: How and Why to Ditch GitHub
#16> GitHub's use of everyone's code to train its language models Unless GitHub knowningly trains on code in private repositories (not that I am aware of), it does not matter where you host your code, or whether it's GPL or MIT licensed. Someone is training their models using your code. That's just a matter of life.
> Unless GitHub knowningly trains on code in private repositories (not that I am aware of) they absolutely have
Proof?
Re: How and Why to Ditch GitHub
#17Does anyone have any experience using Radicle (radicle.xyz) for a non-toy project? I ran across it in an HN comment the other day and have been playing with it, but am curious to hear from someone who's done more than that.
+1, interested in mirroring my repos to Radicle and running a node if it’s not too hard
Re: How and Why to Ditch GitHub
#18For a self hosting solution I'd recommend gitea: it's a single go binary that needs almost no installation (only a config file), it's very fast, updates work great (replace previous binary and restart), supports ldap and has all the features of GitHub your love and even various features that free GitHub does provide (ie branch protection for private repos).
I prefer cgit. It's used by the linux kernel and many others.
Same. gitolite + cgit, stable combo, less things to worry about.
Re: How and Why to Ditch GitHub
#19There was very little "Why" in this article. It seems like: 1. Microsoft bad 2. USA bad 3. I had a gut feeling. I think the Actions support being so lacking is a deal breaker for us. I know we can bring our own. But I really don't want to manage infra here and take on that responsibility.
The "why" was pretty clear in the article: the author thinks GitHub is doing unethical things with the code the author was putting there ( specific things, not "Microsoft bad"). Now you and I may not agree with those things being unethical, but the author does, and I'd say that's a pretty good reason to stop using them.
I would have loved to see that talked about more. I disagree that it's pretty clear. I just read it again and the "Why" (which again is in the title) is lacking for me. I didn't find this article particularly useful or informative. I'm glad you found it useful and informative and I think it's okay that we disagree on that.
Re: How and Why to Ditch GitHub
#20There was very little "Why" in this article. It seems like: 1. Microsoft bad 2. USA bad 3. I had a gut feeling. I think the Actions support being so lacking is a deal breaker for us. I know we can bring our own. But I really don't want to manage infra here and take on that responsibility.
This article pretty clearly seems like it is not focused on convincing you to switch, it is assuming you already want to get off of it and is explaining how to migrate.
The title says WHY to ditch github. There's maybe 2 sentences where that is discussed. That's really all I was interested in, "Why should I leave github to something with fewer features and less community support". This article did not justify that for me.
I'm glad you found it interesting and a good read!