Why are so many Linux projects on Microsoft GitHub? Shouldn't they all move to Codeberg?

Sure, I know a lot of projects have been on GH since before MS bought it, but they've owned it for quite a while now, so we really should be seeing better migration out by now, no?

Codeberg is nonprofit which seems more in the spirit of the Linux ecosystem overall. GH is for-profit...

EDIT: All right, all right, I've gotten schooled. Thank you, O wise ones; I didn't realize how much Microsoft literally depends on Linux, among other things. I will proceed to shut up.

340 points · 116 comments · view on lemmy.world

116 Comments

9point6@lemmy.world · 97 pts · 47d (10 replies)

GitHub has been around for nearly 2 decades and was largely considered a mostly good thing until maybe the past couple of years. Also important to add that Microsoft seems to mostly have left it alone for the first couple of years (possibly with the exception of Atom, which it left very alone)

In addition to people just generally being slow to change, changing can take quite a bit of effort for some projects for varying reasons. Many of those same projects struggle to keep up with the maintenance workload, so they're not going to jump at the chance to add more work to their plates.

Finally, some people just don't care. For instance, the MIT license being popular is pretty hard evidence that FOSS doesn't necessarily mean anti-corporate, and for many users GitHub still more or less does what it says on the tin.

Though I will say if the service disruptions and ad-injection bullshit continue you'll only see GitHub competitors grow. GitLab seems to be going after their enterprise customers with some success.

KssioAug@lemmy.dbzer0.com · 26 pts · 47d (8 replies)

For instance, the MIT license being popular is pretty hard evidence that FOSS doesn’t necessarily mean anti-corporate, and for many users GitHub still more or less does what it says on the tin.

I'm pretty sure that MIT license is that popular out of ignorance, instead of an informed decision to allow corporate to steal and make money out of their code.

tabular@lemmy.world · 22 pts · 47d (4 replies)

I'd like to think that is so but some here will argue non-copyleft licenses are "more free". Ime they don't reply after I point out that's the freedom to deny others freedom.

Viceversa@lemmy.world · 1 pts · 46d (3 replies)

It's freedom nonetheless.

tabular@lemmy.world · 1 pts · 46d (2 replies)

Widen the scope to consider downsteam users (the dev's user's users and beyond) and now the potential lack of any software freedom makes it freedom muchtheless.

Viceversa@lemmy.world · 1 pts · 46d (1 reply)

So you want to restrict dev's freedom to choose whichever license they want?

tabular@lemmy.world · 1 pts · 46d

I prevent others from relicensing my works under less-free licenses or making them non-free by using Copyleft/share-a-like licenses.

doubtingtammy@lemmy.ml · 15 pts · 47d (1 reply)

I've known people IRL who talk about the GPL like it's a virus infecting your code

MonkeMischief@lemmy.today · 10 pts · 47d

I remember this confusion a LOT back when main-branch Blender had its own game engine built in.

Forums were full of people saying crap like :

"Don't use that, because since you used Blender which is GPL it means you have to provide the source code to your incredible GOTY contender and then everybody will beat you at life!!!"

CoryCoolguy@lemmy.myserv.one · 9 pts · 47d

Respectfully disagree. I can only speculate why other developers choose MIT. But for small and medium-sized projects, a more restrictive license is unlikely to protect them from this scenario anyway. And if that's true, one could argue it's better to go down a road where corporate sponsorships are potentially more likely.

Personally, I often choose MIT because I don't care who uses my code and for what, and I'd prefer that it be easy to borrow from. I used to be concerned about how my code was used, but over the years I've developed a strong dislike for copyright as a concept in general so I fight it how I can. Some of my projects are so simple that even MIT seems like overkill. In those cases I use the Unlicense.

gwl@lemmy.blahaj.zone · 6 pts · 47d

Atom is back to life, kinda, there's a fork of it called Pulsar that's actually really pretty good

BartyDeCanter@piefed.social · 63 pts · 47d (8 replies)

Two main reasons: history and network effects.

GitHub was an independent company for a decade that provided a vastly superior service to what it replaced, primarily SourceForge. And it was free for FOSS projects, while charging for closed ones.

The improvements paid for by the closed source customers trickled out to everyone. So, it became the best place for FOSS developers, large and small. And as more people moved to GH, the more reason there was to move to it.

Of course, it was constantly bleeding money and eventually had to do something. That ended up being selling to MS.

There was a lot of trepidation about this, but for the first few years they not only kept their promise about supporting FOSS, but actually made it better by allowing small private repos to get many of the services that were previously gated for open FOSS or paid repos.

And the alternatives were stil not as good, and just as importantly didn’t have the user networking that GH does.

Now, some FOSS people are starting to look elsewhere, Codeberg, self-hosted Forgejo, and others. They have come a long way and are nearing feature parity, particularly for smallish projects. But the network effects of discovery and reputation are strong, and GH still provides a few more useful features.

I’ve moved my private repos to self hosted Forgejo, but my public ones are still on GH as push mirrors. I’m not ready to give up the discoverability and Mac/Windows CI runners that I can get from GH for free. I hope to be able to some day, but not yet.

MonkeMischief@lemmy.today · 7 pts · 47d (5 replies)

There was a lot of trepidation about this, but for the first few years they not only kept their promise about supporting FOSS, but actually made it better by allowing small private repos to get many of the services that were previously gated for open FOSS or paid repos.

  • They embraced! :D
  • They extended! :D
  • . . .aw, shit. :/

I've only a basic understanding of using Git myself, but I think I'm gonna learn it with a self-hosted Forgejo for my Godot projects too.

Then for the parts that don't have feature parity, I won't know what I'm missing, and I have no need for "iNdUsTrY sTaNdArD LeAdiNg oPtiMiZeD sYnErGyStiC wOrKfLoWs" or whatever hahaha.

It does definitely present a conundrum if you want people to see your open source software though. Damn network effect. =\

BartyDeCanter@piefed.social · 9 pts · 47d (4 replies)

The number one thing to remember about git is that you don't need a full hosting service around it for basic functionality. If it's just you, a single local repo will probably serve you just fine, maybe use a bare repo on your main machine or a Pi-level device if you like as a remote/backup. Just git init or git init --bare and you're good to go. GitHub, Codeberg, Forgejo, and all the others exist to serve multi-contributor and/or public project-level needs.

The number two thing to remember is that it is based around graph theory.

MonkeMischief@lemmy.today · 2 pts · 46d (3 replies)

That's some really helpful advice, thank you! 😃 I actually didn't know you could just make any local folder a repo like that.

Would a Forgejo instance still be helpful if I wanted to have "one point of truth" between multiple machines even if I'm the only dev? I already use Syncthing, but for some reason I feel like there'd be a lot of sync conflicts and stuff.

The other main reason for wanting to learn Git, of course, is because it's otherwise more difficult to try out changes to scripts and experiment, without finding yourself lost in the weeds and forgetting what worked last.

My current "version control" is "copy the entire project folder before you do anything major." 😂

BartyDeCanter@piefed.social · 2 pts · 46d (2 replies)

If you just want one point of truth, the minimal version is to create a bare repo somewhere that you have ssh access to or your local machine. Then you can clone/pull/push from it.

A bare repo is a special kind of repo meant for exactly this, but can be a bit confusing at first. A normal repo contains all of your current working files and a special .git directory that holds all the files/blobs/history that git needs to work. A bare repo is just the .git as a top directory with bare=true in its config. So you can use it as a remote, but it never has a working set. They are usually named something like my_repo.git.

Edit:

Here’s a basic example for setting it all up in a fully local way:

mkdir ~/bares  
git init --bare ~/bares/my_repo.git  
mkdir ~/code  
git clone ~/bares/my_repo.git ~/code/my_repo  

And then you have remotes as your main source of truth in ~/bares and your working copies in ~/code. If you want to access from another machine that has ssh access to the first, you can do:

mkdir ~/code  
git clone user@host:~/bares/my_repo.git ~/code/my_repo  

And then use git pull/push to keep it all in sync. Don’t use Syncthing on a git repo, it eventually goes badly.

MonkeMischief@lemmy.today · 2 pts · 45d (1 reply)

This was really informative, thank you so much for taking the time! Definitely bookmarking this. :)

I was looking up further why you'd use a bare repo over a standard one. Somebody said for just sharing a repo between users, "snapshots just take up unnecessary space."

...But would that mean you can't roll back history? Maybe I'm ignorant on the term snapshot in Git context lol.

But yeah, I really appreciate the post and I think that'll get me on the right foot, to actually developing games instead of setting up yet another tool and procrastinating what I want to actually be doing anyway. 😂

Glad my instinct was correct about not using Syncthing for this purpose. XD

BartyDeCanter@piefed.social · 2 pts · 45d

Happy to help! And yes, I have no idea what they’re talking about. If you don’t have snapshots (commits) you don’t have version control.

Let me know when you get your game going, I’d love to check it out. I’m working on a few myself.

gwl@lemmy.blahaj.zone · 3 pts · 47d

Btw, there are some CI runners on Codeberg, but they're not well advertised, and not as feature-rich

Bogus007@lemmy.zip · 2 pts · 47d

Just to give some relevant information: Git, the major program behind GitHub, has been developed by Linus Torvals. The license allowed the free use of git until today. Some people took git and built a web application around - GitHub was born. Sure they added some features, but the engine was git! In 2018 these “creators” of GitHub sold their product to Microsoft. They gave a s**t on the community and what may happen afterwards.

just_another_person@lemmy.world · 46 pts · 47d (4 replies)

Open Source projects get lots of free features for being on GitHub. Nobody else is beating that offering at current.

highbank@lemmy.zip · 6 pts · 47d (3 replies)

What are those free features? Why doesn't Codeberg have it?

stsquad@lemmy.ml · 28 pts · 47d

Because running servers costs money. The project I work on gets donations towards it's CI costs and it's not insignificant.

BartyDeCanter@piefed.social · 15 pts · 47d
  1. CI runners - GH offers free CI runners for a variety of OSs. I can automatically test my code on Linux/Mac/Windows for free on GH. No one else offers that because it is very expensive. You need windows licenses and Apple hardware. And Codeberg only offers it on Linux after a back and forth discussion. Plus, while simple GH CI Actions move to Forgejo Actions pretty easily, more complex ones require a complete rewrite.
  2. Better issue tracking - FJ's issue tracking is pretty good, and perfetcly fine for small projects, but GH's is better.
  3. Better CLI - fj is decent and improving, but gh is better
  4. Better project pages - Codeberg Pages is decent and improving, but GH Pages are better.
  5. Lots of other small things - Codeberg is decent and improving, GH is better.

For most people, myself included, the only thing that really matters are the CI runners. But that is also the one thing that costs the most to support.

lemongarlic@lemmy.world · 15 pts · 47d

Free github actions

Xanthrax@lemmy.world · 41 pts · 47d (13 replies)

Why aren't all the reddit users over here yet? Consolidation and ease of use. Big number make brain happy.

trilobite@lemmy.ml · 16 pts · 47d (10 replies)

Lazyness? Its why Amazon is such a success. Too difficult to do online search. Amazon is convinient.

mattyroses@lemmy.today · 13 pts · 47d (9 replies)

It's generally not the search, it's the payment and shipping

utopiah@lemmy.ml · 4 pts · 47d (2 replies)

Doubt it, most other online stores with the same coverage do offer similar conditions.

sonstwas@sh.itjust.works · 4 pts · 47d (1 reply)

The difference is the wide range of products available on Amazon. I can buy 5 products from widely different areas and only pay shipping once (or maybe twice depending on availability).

If I were to order these 5 products on 5 different stores I'd pay 5 times shipping.

mattyroses@lemmy.today · 3 pts · 46d

And most Amazon customers have prime, meaning they've prepaid shipping already.

Bogus007@lemmy.zip · 2 pts · 47d (3 replies)

Your local or regional provider can and will send you books in the same time - perhaps not in 24h, but this may be rarely the case that somebody is in a such dearly need of a book.

I am buying books from my local provider, though more expensive, but I want people to have jobs - considering how many bookstores closed due to Amazon - and the possibility to go there, have a book in my hand and read it a bit.

logi@lemmy.world · 5 pts · 47d

It's been a while since I've seen Amazon talked about as a book store.

mattyroses@lemmy.today · 1 pts · 46d (1 reply)

It's not just books. Amazon offers many more goods, and locks people in with Prime.

I don't like it, but just claiming it as a sign of virtue won't change that.

Bogus007@lemmy.zip · 2 pts · 45d

True. And although some studies reported a positive effect on companies, I have my doubts based on what I have seen with my eyes in my city. A study issues further concerns:

https://www.economicliberties.us/our-work/the-local-harms-of-amazon/

Dymonika@lemmy.ml · 2 pts · 45d (1 reply)

It's not the shipping; it's the return policy. Amazon's is almost impossible to beat apart from certain in-person stores like Costco or perhaps ALDI.

mattyroses@lemmy.today · 1 pts · 44d

Yeah - now, the downsides of this are well covered, especially by Corey Doctrow, in that once the users are locked into the platform, Amazon decreases the actual benefits - and then starts chisling the sellers as well.

But to fix that, you do need to do something besides just scold the customers.

liking625@lemmy.world · 4 pts · 47d (1 reply)

You are mistaken, they all are, what's left is bots talking between them

Dymonika@lemmy.ml · 1 pts · 45d

Ha, if only that were the truth. I keep preaching over there and telling people to check out /r/RedditAlternatives, at least, so I like to think that I've moved at least one person over, which makes it all worthwhile.

flamingo_pinyata@sopuli.xyz · 32 pts · 47d

Inertia. And GitHub was actually good, despite MS ownership. Until recently.

plutopos@lemmy.zip · 28 pts · 47d (11 replies)

Arguably the biggest contributor to the Linux ecosystem is Red Hat, a for-profit company that offers its technologies to the Israeli military among other things. The biggest contributor to the Linux kernel is Red Hat, while the second biggest is Meta. The Linux ecosystem is not inherently nonprofit!

Kirk@startrek.website · 15 pts · 47d (3 replies)

Wow I went to fact check that claim and it's actually no exaggeration. Here is the AP article.

Google and Amazon provide cloud computing and AI services to the Israeli military under “Project Nimbus,” a $1.2 billion contract signed in 2021, when Israel first tested out its in-house AI-powered targeting systems. The IDF has used Cisco and Dell server farms or data centers. Red Hat, an independent IBM subsidiary, also has provided cloud computing technologies to the Israeli military, while Palantir Technologies, a Microsoft partner in U.S. defense contracts, has a “strategic partnership” providing AI systems to help Israel’s war efforts.

Crazy to see Palantir, Google, Microsoft mentioned alongside ...Red Hat.

Hawke@lemmy.world · 11 pts · 47d (1 reply)

If it helps to explain it, Red Hat is owned by IBM.

Kirk@startrek.website · 3 pts · 47d

No love lost for IBM but I still wouldn't expect to see casually mentioned alongside Palantir.

doubtingtammy@lemmy.ml · 2 pts · 47d

It's red from all the blood? well, fuck

Dreamer@lemmy.ml · 10 pts · 47d (4 replies)

Why do you make the argument that Red Hat is the biggest contributor?

Searching Linux contributor breakdown by organization puts them tied for 3rd at ~7%.

https://insights.linuxfoundation.org/project/korg/contributors?timeRange=past365days&start=2025-06-19&end=2026-06-19

https://commandlinux.com/statistics/linux-kernel-contributors-lines-of-code-statistics/

Don't get me wrong. Intel leading the corporate contributions is worse. lol

All-time contributions are led by Red Hat at 15%. Many top organizational contributors guilty of profiting from the genocidal industrial complex. Maybe TempleOS was the true alternative.

sorter_plainview@lemmy.today · 10 pts · 47d (1 reply)

In the first link, look at the parameters in the link. It is for last 365 days. If you take all time, it is Red Hat.

To be explicit: I don't like Red Hat.

Dreamer@lemmy.ml · 1 pts · 47d

I see. Ty

plutopos@lemmy.zip · 1 pts · 47d (1 reply)

Pardon, I remembered it so from a graph I saw a few months ago. Perhaps I misremembered, or perhaps things changed since then

Dreamer@lemmy.ml · 1 pts · 47d

You were right. Red Hat leads all time.

All the major organizational contributors are guilty of profiting from genocide. TempleOS might be the one true alternative.

Dymonika@lemmy.ml · 6 pts · 47d

Oh... shoot... TIL, thanks!

Bogus007@lemmy.zip · 1 pts · 45d

This is also a reason why some are against RedHat distributions (eg Fedora) or products (systemd, pulse audio). If you don’t like to support the company and have an alternative, take the alternative.

stratself@lemdro.id · 26 pts · 46d (3 replies)

The case of free CI/CD, visibility, and network effects are already said. So I wanna offer an anectode: someone I know is a graphic designer, who maintains a project that curate icons. Moving to Codeberg means he has to interact with PRs using the CLI, which he really does not have familiarity with. GitHub OTOH has a simple desktop client that allows natively switching across PRs, approving then in the UI, etc. It's really, really convenient for someone who's not a developer.

I think Forgejo-based platforms will need to work on a very good GUI client, in order to attract less technical contributors.

crmsnbleyd@sopuli.xyz · 7 pts · 46d (2 replies)

Why doesn't the web client fit their needs?

stratself@lemdro.id · 6 pts · 46d (1 reply)

The idea is to download the "project" down to a local machine, switch to the contributors' PRs, and have those new files natively show up in their directories. Then they can use local software i.e. Inkscape/Illustrator/etc to edit those SVGs and commit the appropriate changes. This is really not feasible with a forge's web UI.

CommanderCloon@lemmy.ml · 1 pts · 46d
[ removed ]
Eggymatrix@sh.itjust.works · 24 pts · 47d (5 replies)

You seem to think that the idea is that linux and most FOSS projects are some carebear nonprofit charity organization. You are wrong.

In most cases the idea is that open source work is there because it is easier to share technological progress if multiple companies work at it. And because of this it is just better than the alternative. The linux kernel is worked on by multiple large corporations that are in the business of making money using servers. If these servers run better then they make more money. To make them run better for them they need to implement their features and because of the licence and the ecosystem they need to publish these modifications back to the upstream.

All this works so good because a lot of companies make a lot of money with it.

Github will be used as long as it does not interfere with the workflow or with the legal aspects, nobody cares about the spirit nearly as much as you think

Dymonika@lemmy.ml · 8 pts · 47d (4 replies)

Fair, but what about the Copilot-pockmarking? And they're always one step away from a paywall... Why wait until it gets that bad versus at least duplicating elsewhere now?

festus@lemmy.ca · 13 pts · 47d (1 reply)

Worth noting that the Linux source is updated and collaborated with via email, not GitHub. The Linux repo on GitHub is a read-only mirror.

gwl@lemmy.blahaj.zone · 1 pts · 47d

Aye, but that's not true of the Linux OS's based on it

Eggymatrix@sh.itjust.works · 1 pts · 47d

All these projects for sure are cloned on multiple backups, if something happens and github is no longer viable it is a minimal effort to clone the source code and bug tracking and move it somewhere else. Serious projects will have contingenties in place for this, lesser projects will do what the big guys do

lemongarlic@lemmy.world · 1 pts · 47d

Plenty of companies are quite happy to pay for github licenses

jollyrogue@lemmy.ml · 23 pts · 47d (1 reply)

For some people, they don't actually care about the politics of FOSS; they want a portfolio for employers.

MangoCats@feddit.it · 3 pts · 46d

I use both (why not?, they're both free and it's trivial to add a remote) - I find github is a little quicker to respond, a little easier to work with, and much more well known when you ask someone to go there they're not queasy about what they might be connecting to...

gwl@lemmy.blahaj.zone · 23 pts · 47d (5 replies)

Momentum and time and effort to migrate.

And there's automated workflows such as GitHub Actions and ci/cd integrations that don't have 1-to-1 replacements, which would mean extra work (for quite strained teams of volunteers)

matdave@lemmy.ml · 6 pts · 47d (2 replies)

Additionally, as a developer on a large open source project, the community is already established on GitHub. It would be incredibly risky to move it and hope everyone comes along.

undrwater@lemmy.world · 4 pts · 47d (1 reply)
gwl@lemmy.blahaj.zone · 3 pts · 47d

Good for them, still, it's risky, they just decided it was worth the risk

Evotech@lemmy.world · 2 pts · 47d (1 reply)

I moved my projects and yes I had to make new runners and pipelines for forgejo but it's pretty much feature parity

gwl@lemmy.blahaj.zone · 0 pts · 47d

Good for you, guess your setup is less complicated then.

There's still plenty of stuff that is not a 1-to-1 drop in replacement, e.g. plenty use build previews from netlify, they have no drop-in for other providers so to get those you have to directly interact with the API instead, in a runner

gravitas_deficiency@sh.itjust.works · 20 pts · 47d

Serious answer: technical inertia and legacy reasons and most people don’t want to bother migrating established projects.

utopiah@lemmy.ml · 20 pts · 47d

It's disappointing yet unsurprising to read the recurring answers, namely :

  • cost
  • incumbency

precisely because it's absolutely avoidable and a well known strategy. It's so well known that it's precisely why Micro$lop bought Github in the first place. People are there and the free tiers is enough to get the long tail.

Meanwhile since that strategy happened people who consider smart enough should know the genuine cost behind this : it's a TRAP. Plain and simple, you get there and you get STUCK there.

So... yes it takes some sweat and even some money to leave the trap ... but if you care about freedom, as most free software or open-source developers might, then it's aligned with your value.

thejml@sh.itjust.works · 18 pts · 47d

It was independent (not under Microsoft) until late 2018, and moving is hard. Even after MS bought it, they tried to keep it independent. It's really only been the last few years where it's gone downhill.

It's also kinda the defacto standard for git hosting due to being a solid early player in the space. I assume that view will change as Codeberg and other rivals get more ingrained in the open source stack.

libffi@lemmy.zip · 18 pts · 46d (2 replies)

Dymonika@lemmy.ml · 1 pts · 43d (1 reply)

I must've missed this meme if this is some sort of repeat.

libffi@lemmy.zip · 1 pts · 41d

no, thats just what a friend of mine said genuinely. unfortunately, gh (or rather it's features) is necessary in some cases. such as free ci, bandwidth and storage.

p03locke@lemmy.dbzer0.com · 17 pts · 47d (1 reply)

Did you download the source code? It's on GitHub. It's literally on GitLab. It's on Bitbucket with ads. It's literally on SourceForge. You can probably find it on Savannah. Dude it's on Azure DevOps. It's a Codeberg project. It's on Gitea. You can download it on Gitea. You can go to Gitea and download it. Log into Gitea right now. Go to Gitea. Dive into Gitea. You can Gitea it. It's on Gitea. Gitea has it for you. Gitea has it for you.

diaphragmwp@discuss.tchncs.de · 5 pts · 47d

That's kind of the point of git

garbage_world@lemmy.world · 17 pts · 47d
[ removed ]
crystalwalrus@programming.dev · 13 pts · 47d (1 reply)

Like many other social media sites it's partially network effects.

gndagreborn@lemmy.world · 5 pts · 47d

It's probably majority network effects. If you compare Instagram to 5, 10 years ago on the dot, you see an atrocious drop off on quality and usability. The change was so insidious, majority of people didn't notice or care all that much. And yet, Instagram is still one of the largest platforms in the US, despite how objectively horrendous it is to users.

eager_eagle@lemmy.world · 11 pts · 47d (3 replies)

I don't move mine because of the hard limits at 100 repos and 100 MB of private storage. I wouldn't mind paying to have more, but that's not an option.

edit: it seems one can request limit increases, but I have no idea what's their approval criteria.

cadekat@pawb.social · 5 pts · 47d (2 replies)

It's hopefully common knowledge, but just in case, Codeberg is running Forgejo. You can host a compatible instance yourself! It's not that painful.

qprimed@lemmy.ml · 5 pts · 47d

just installed forgejo on a locally hosted lxc instance on a spare qemu VM. will use primarily for my own projects and external devs who collaborate on client projects.

doing my part to give an nvidia sized/shaped "torvalds" to ms.

edit: love it. glad I finally pulled the trigger on this.

eager_eagle@lemmy.world · 4 pts · 47d

I know, but the main use i have for github is collaboration, and I don't want to expose a forgejo instance I'm hosting myself.

quick_snail@feddit.nl · 10 pts · 47d (2 replies)

Codeberg doesn't offer CI runners* for macOS for free.

It's important if you have cross platform apps

neclimdul@lemmy.world · 13 pts · 47d (1 reply)

Runners? If MS is providing free dinners I might have to rethink my thoughts on github.

myrmidex@belgae.social · 1 pts · 47d
[ removed ]
chrash0@lemmy.world · 10 pts · 47d (3 replies)

people have tried.

people predicted the enshittification of GitHub as soon as the acquisition was announced, as you can imagine. now, picture yourself as a dev in that month where a small vocal userbase is reading tea leaves based on Microsoft’s past behavior telling you to move your project, where the best outcome is nothing changes, to a new platform. you have a hundred issues and a dozen PRs in review, and those won’t stop coming in while you are migrating. now you need to mirror your project on GitHub, unless you want to immediately fade into obscurity, because while you’re spending your valuable time making sure everything is setup as it was but now on GitLab (the only realistic alt at the time), issues and PRs are still coming in, and you have to keep your releases updated in GitHub for a while during the migration. you also need to figure out CI/CD on your new platform.

so the ideal—that you can migrate and nothing changes—is a pipe dream. your packaging is now likely totally different; you’re now that snowflake project in the config where i had to figure out how to point to something other than GitHub and waste 30min questioning whether i need your tool at all. you still continue to get PRs and issues through GitHub because of course they didn’t read the README. and there’s tiny friction everywhere. the UI is different, how OAuth is handled is different, the plug and play you got from GitHub Actions is gone, etc etc.

meanwhile for 6 years things are chugging along fine at GitHub: Actions is getting better, Treesitter support, better UI for PRs.

it’s the AI stuff that’s ruining GitHub no doubt. not the AI itself but the culture around it with the “what is our team doing with AI?” nonsense corporate policy. it’s all happened really quickly, and isn’t the “boiled frog” scenario at all really.

Linux was around before GitHub, and wherever we end up as long as we still have our Unix tools like git it’ll be fine.

ideals are great. the perfect is the enemy of the good

iocase@lemmy.zip · 8 pts · 47d (2 replies)

Embrace, extend, extinguish.

Microsoft embraced github by buying it. They extended the features and ease of use to where it's the primary website people use for sharing and collaborating on code. Now it extinguishes any alternative.

Cawifre@lemmy.world · 3 pts · 47d (1 reply)

It already was the primary code sharing place though... that's why they bought it.

iocase@lemmy.zip · 4 pts · 47d

Embrace extend extinguish is a well known pattern microslop uses to kill open source alternatives. You're right it was already big which is why they embraced it (we're both agreeing here) all I'm saying is they make sure it's impossible to develop an alternative due to network effects and vendor default lock in. "Embrace extend extinguish" is From their own internal communications found during discovery.

dwt@feddit.org · 9 pts · 47d (1 reply)

A friend of mine sees using GitHub as microslop paying reparations to open source.

utopiah@lemmy.ml · 13 pts · 47d

Right, like how Micro$lop :

  • blocked repository search without login (while it worked before the acquisition)
  • pushed in the most traditional Micro$lop fashion for its own product, e.g. Copilot, with in product ads
  • use repositories as ways to feed its own set of products, e.g. Azure for OpenAI, in order to push for code generation while ignoring licenses

and all the other things (please feel free to make this list more comprehensive) as "reparations"?

It's the same old "Embrace, extend, and extinguish " (EEE) scheme they've been (sadly successfully) running for decades now.

KssioAug@lemmy.dbzer0.com · 7 pts · 47d (2 replies)

I believe the core reason is that, when MS bought it, and while they make it worse day by day, the number of projects in Github was already huge and it just keeps growing. That being said, it is still the main platform to find FOSS projects, and to have your project be found.

A lot of people are migrating though. The good thing about the FOSS community and philosophy is that they don't really need to rely on shitty companies like Microsoft. They can (and many actually do) just move on, at least regarding their own personal projects.

Telorand@reddthat.com · 3 pts · 47d (1 reply)

Yep. For example, Gnome migrated to Gitlab some time ago. Obviously it's not as ethical as Codeberg, but maybe it offers certain features that Codeberg doesn't (yet) have that they require. PikaOS is (was?) on Gitea.

For my part, I've left Github and will only do development on Codeberg. I'll still make pull requests to upstream projects that only exist on Github, but I have no control where those parent projects are hosted, and improving those projects is still a net benefit to everyone.

Bogus007@lemmy.zip · 1 pts · 45d

Gentoo and Guix moved their projects to Codeberg. The programming language Zig did it as well. I have heard from few others, which moved to Gitea (Fedora).

LovableSidekick@lemmy.world · 6 pts · 47d (1 reply)

Github was around for a long time before MS bought it.

Dymonika@lemmy.ml · 1 pts · 43d

I know, but more people left Twitter after it became X, for example, so migration is totally possible.

DFX4509B@lemmy.wtf · 6 pts · 47d (1 reply)

Also, what if MS or the government starts getting hostile and taking down Linux and other FOSS repos they don't like?

BartyDeCanter@piefed.social · 8 pts · 47d

Remember that Git is a distributed VCS, so no git repo is dependent on a central server. Everything else about the project might be heavily dependent on GH, but any active developer is going to have a full copy of the code with history on their main workstation.

That being said, it highly depends on the project, but I'd put it into a few buckets.

  1. Un/barely maintained projects - This is by far the largest number of repos, and many of them are used as dependencies by all sorts of projects. The truly unmaintained ones would vanish, and I bet most of the barely maintained ones would as well. The most important of these would probably be resurrected since their code will be sitting on all sorts of drives, but it will be a mess. Take a look at https://nesbitt.io/2026/05/08/weekend-at-bernies.html for an idea.
  2. Small individually actively maintained projects - There are a lot of these and many of them could continue to be just fine, depending on how much of the full GH feature set they use. They would lose all the PRs, wiki spaces, discussions, issues, and maybe even the project page itself that are hosted on GH. For most projects it would be an annoyance to have lost all that, but if it's a small enough project that one person is maintaining it, it's probably small enough to pull over to something else reasonably easily depending on how all in they are on GH tools and their use of type 1repos. And a project with only one main contributor is unlikely to fragment.
  3. Mid-sized active projects - Probably the hardest hit. A lot of these are all-in on the GH tools, particularly issues and CI. Losing that would hurt a lot because the project is big enough to really need those tools and uses them at a volume that they can't just host on the leads laptop. These are also going to take a lot of work to set up the project infrastructure elsewhere. And this would probably be the sort of thing to push and simmering tensions to erupt, leading to fragmentation.
  4. The big projects - Probably the least hardest hit. Most of these are just using GH as a push mirror. The core team probably has a functioning private communication and governance system, their own issue tracker (even if it pulls from GH), documentation, and public discussion groups. Most of these run their own private CI. And they are the ones most likely for another host to step in and offer to help.

So the little stuff? Probably going to be annoyed or not care a lot. The big stuff? Same thing. But that middle group would be hurt.

leftascenter@jlai.lu · 5 pts · 47d

It's really for the copilot integration. ,/s

Mangoholic@lemmy.ml · 5 pts · 46d (1 reply)

Amuy new projects are codeberg. But github has a default 10gb repo space. Imagine everyone suddenly wants that on codeberg, the cost alone would force them to shut down or have other forms of income than donations.

Dymonika@lemmy.ml · 1 pts · 43d

I didn't know the repo space was that different. That does play a factor in all this...

ian@feddit.uk · 5 pts · 47d (1 reply)

I joined Github and others, years ago to report bugs in software. But now I rage quit Github. No more bugs from me unless you move your application to a more acceptable platform. I suggest every bug reporter user do likewise. Screw Microsoft.

Dymonika@lemmy.ml · 1 pts · 43d

Hmm, good point... I am an avid bug reporter...

juh@lemmy.ml · 2 pts · 46d

They all want to make America great again.

adarza@piefed.ca · 2 pts · 47d (1 reply)

many were there first, long before microsoft bought the site. but now? yea. why tf are people still using it.

eager_eagle@lemmy.world · 2 pts · 47d

GitHub is good enough to people keep using it. With the exception of the AI-induced downtimes last month, other platforms have as many problems as GH does, but GH gets the bad rep because it's the one everyone uses and has an opinion about.

Despite old problems that still annoy me, they actually have an impressive and unmatched set of features too, so one can't move away without some compromise. For the most part, you might find Forgejo/Codeberg and others to meet your needs, but it's going to take a long time to match GitHub's maturity in some things like code search.

anon_8675309@lemmy.world · 0 pts · 47d
[ removed ]
Evotech@lemmy.world · -1 pts · 47d (3 replies)

If you think github is unstable you haven't tried codeberg. It's down multiple times every day.

Bogus007@lemmy.zip · 3 pts · 47d (2 replies)

I have no troubles. Perhaps check your WiFi.

Evotech@lemmy.world · -1 pts · 46d (1 reply)

Cope

Dymonika@lemmy.ml · 1 pts · 45d

Wait, is "cope" some kind of new insult?

diabetic_porcupine@lemmy.world · -1 pts · 46d

Did you literally just post this to say Microsoft GitHub

Sxan@piefed.zip · -3 pts · 47d

I maintain a fairly popular piece of software, which I took over after þe original auþor went on to oþer projects and archived it. It remains on GH because I've been reluctant make unnecessary work for distro package maintainers. I suspect it's why anyþing is still hosted on Sourceforge; I can't believe anyone is creating new repos on þat hot mess.

diaphragmwp@discuss.tchncs.de · -4 pts · 46d (3 replies)

Been on this post before but just noticed you mentioned "Linux project" as if everything open source (or even source available) is Linux. Quite the ignorance...

Dymonika@lemmy.ml · 1 pts · 45d (2 replies)

Huh? I am aware; I didn't say "all Linux projects," did I? Of course I already know that there are already some on Codeberg and elsewhere, but I still wanted to address the behemoth.

diaphragmwp@discuss.tchncs.de · 1 pts · 45d (1 reply)

I am not talking about the git provider, I am talking about "Linux project". I know we are kind of on "@linux@lemmy.ml", but how many tools you use do you think are truly Linux specific? Even some long time linuxisms like libinput and DRM have been ported over to BSDs for example.

Dymonika@lemmy.ml · 1 pts · 43d

True, I always look for cross-platform ones whenever possible...